Re: [Qemu-devel] boot arm fedora via u-boot in qemu

[Hans de Goede]

Hi Gerd,

On 10/21/2014 03:33 PM, Gerd Hoffmann wrote:
>   Hi,
> 
> Played around with u-boot a bit, trying to get it work in qemu, so you
> don't have to hop through loops copying the kernel+initrd from the disk
> image to pass it to qemu on the command line.
> 
> Guess why I'm asking here?  No so success so far :(
> 
> What I did:  Started with the fedora uboot-tools package, then tried to
> adapt vexpress.  Look here:
> 
> https://www.kraxel.org/cgit/jenkins/u-boot/tree/
> 
> Patches 1-7 come straight from the fedora package.
> Patch #8 is a bugfix.
> Patch #9 is a debug patch (send logs to console).
> Patch #10 adapts vexpress to the distro patches.
> Patch #11 makes u-boot pick up the fdt from qemu.
> 
> All looks fine, uboot finds the virtual sdcard, loads kernel + initrd,
> passes on the fdt.  kernel doesn't boot though, without printing any
> helpful clues to the serial console.
> 
> Any ideas what this might be?
> Any hints how to go on with debugging?
> 
> thanks,
>   Gerd
> 
> --------- [ cut here: log from a boot attempt ] -------------
> + exec qemu-system-arm -nographic -M vexpress-a9 -m 1G \
>   -kernel build-vexpress_ca9x4/u-boot \
>   -dtb /path/to/vexpress-v2p-ca9.dtb -sd f21.img
> 
> 
> U-Boot 2014.10-rc3-00275-g30ed9a4 (Oct 21 2014 - 12:49:54)
> 
> DRAM:  1 GiB
> WARNING: Caches not enabled
> Flash: 128 MiB
> MMC:   MMC: 0
> *** Warning - bad CRC, using default environment
> 
> In:    serial
> Out:   serial
> Err:   serial
> QEMU: fdt found at 60000000, using it.
> Net:   smc911x-0
> Warning: smc911x-0 using MAC address from net device
> 
> Warning: Your board does not use generic board. Please read
> doc/README.generic-board and take action. Boards not
> upgraded by the late 2014 may break or be removed.
> Hit any key to stop autoboot:  0 
> switch to partitions #0, OK
> mmc0 is current device
> Scanning mmc 0:1...
> Found /extlinux/extlinux.conf
> Retrieving file: /extlinux/extlinux.conf
> 528 bytes read in 34 ms (14.6 KiB/s)
> Ignoring unknown command: ui
> Ignoring malformed menu command:  autoboot
> Ignoring malformed menu command:  hidden
> Ignoring unknown command: totaltimeout
> Fedora-Minimal-armhfp-21-20140905 Boot Options.
> 1:      Fedora-Minimal-armhfp-21-20140905 (3.16.1-301.fc21.armv7hl)
> Enter choice: 1
> 1:      Fedora-Minimal-armhfp-21-20140905 (3.16.1-301.fc21.armv7hl)
> Retrieving file: /initramfs-3.16.1-301.fc21.armv7hl.img
> 29202689 bytes read in 3788 ms (7.4 MiB/s)
> Retrieving file: /vmlinuz-3.16.1-301.fc21.armv7hl
> 5460688 bytes read in 762 ms (6.8 MiB/s)
> append: ro root=UUID=55c3c475-37c8-41f8-ac34-3c153cde02a2
> console=ttyAMA0,115200n8
> Kernel image @ 0x80008000 [ 0x000000 - 0x5352d0 ]
> ## Flattened Device Tree blob at 60000000
>    Booting using the fdt blob at 0x60000000
>    Loading Ramdisk to 7e307000, end 7fee0901 ... OK
>    Loading Device Tree to 7e2f8000, end 7e306339 ... OK
> 
> Starting kernel ...

Here is what a working boot on an Allwinner board looks like:

Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
769 bytes read in 100 ms (6.8 KiB/s)
Ignoring unknown command: ui
Ignoring malformed menu command:  autoboot
Ignoring malformed menu command:  hidden
Ignoring unknown command: totaltimeout
Fedora-Minimal-armhfp-rawhide-20140731 Boot Options.
1:      Fedora-Minimal-armhfp-rawhide-20140731 (zImage)
2:      Fedora-Minimal-armhfp-rawhide-20140731 
(3.16.0-0.rc7.git1.1.fc22.armv7hl)
Enter choice: 2
2:      Fedora-Minimal-armhfp-rawhide-20140731 
(3.16.0-0.rc7.git1.1.fc22.armv7hl)
Retrieving file: /initramfs-3.16.0-0.rc7.git1.1.fc22.armv7hl.img
29519929 bytes read in 1724 ms (16.3 MiB/s)
Retrieving file: /vmlinuz-3.16.0-0.rc7.git1.1.fc22.armv7hl
5932608 bytes read in 456 ms (12.4 MiB/s)
append: ro root=UUID=a6446dcb-320d-421f-9b71-725b68e5a41b console=ttyS0,115200
Retrieving file: /dtb-3.16.0-0.rc7.git1.1.fc22.armv7hl/sun7i-a20-bananapi.dtb
22335 bytes read in 2312 ms (8.8 KiB/s)
Kernel image @ 0x42000000 [ 0x000000 - 0x5a8640 ]
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
   Loading Ramdisk to 4e3d8000, end 4ffff039 ... OK
   Loading Device Tree to 4e3cf000, end 4e3d773e ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.16.0-0.rc7.git1.1.fc22.armv7hl (address@hidden) 
(gcc version 4.9.1 20140717 (Red Hat 4.9.1-2) (GCC) ) #1 SMP Tue Jul 29 
17:20:28 UTC 2014

Note how it is also actually reading the dtb from disk, where as in your case
it is not, so that seems to be the culprit.

Regards,

Hans