QEMU: Check cause of failure starting from U-Boot
Closed, ResolvedPublic


Emulator does not show any progress. Program counter remains at 0x0.

BAndiT1983 updated the task description. (Show Details)
BAndiT1983 raised the priority of this task from to Needs Triage.
BAndiT1983 claimed this task.
BAndiT1983 moved this task to Backlog on the AXIOM Beta Software board.
BAndiT1983 added a subscriber: BAndiT1983.
BAndiT1983 added a comment.EditedFeb 19 2017, 1:19 PM

Started through setting U-Boot as kernel manually. I suppose QEMU is not replicating the search for boot.bin on first partition, as the hardware does (needs verification). Built newest U-Boot (2017) from Xilinx to check if there would be less problems, than with one from 2014 from apertus°.


./qemu/aarch64-softmmu/qemu-system-aarch64 \
-M arm-generic-fdt-7series -m 4GB -machine linux=on \
-serial null -serial mon:stdio -nographic -boot mode=3 \
-dtb $target_dir/$dtb \
-kernel $target_dir/$kernel \
-drive file=$target_dir/$image,if=sd,format=raw,index=0

Still does not run fully automatically, "run sdboot" has to be called, afterwards the system boots. Someone has to check the state of emulation, if important parts of hardware are initialized.

sebastian closed this task as Resolved.Jun 21 2017, 2:54 PM
sebastian added a subscriber: sebastian.

fixed with latest from https://lab.apertus.org/T737 ?