Yes, I have these all files at var/run/log/boot/image.elf.gz, bender, and grub. when I execute the image.elf (*qemu-system-aarch64 -s -display gtk -nographic -serial null -serial mon:stdio -kernel var/run/log/boot/image.elf -M raspi3 -m 1024)*I got the following messages in the terminal. But when I run log.img it got stuck at the kernel loading. I think during the build process of log.img it creates an image.elf at var/run/log/boot/image.elf.gz.
I hope I cleared my query, If is there anything missing please let me know.
Also, would you give some explanation about run/log and run/sculpt and why you suggested me to go for run/log instead of run/sculpt?
On Sun, Feb 5, 2023 at 10:57 PM Michael Grunditz michael.grunditz@gmail.com wrote:
On Sun, 5 Feb 2023 at 15:37, DHIRAJ PRAJAPATI dhirajprajapati96@gmail.com wrote:
Thanks, Michael for suggesting the uboot tools.
I generated the uImage successfully. Now to boot the image on QEMU I first tried to get the log.img using make run/log KERNEL=hw BOARD=rpi3 VERBOSE= by adding QEMU_RUN_OPT := --include image/disk But could not figure out to resolve the problem that the kernel is not
getting loaded.
Also, guide me if I can do something with
uImage(var/run/log/boot/uImage) to get the GUI in QEMU.
Reading your error log. Do you have a var/run/log/boot/image.elf?
When it works qemu should print messages in your terminal.
Michael
Genode users mailing list users@lists.genode.org https://lists.genode.org/listinfo/users