From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: michael.opdenacker@rootcommit.com,
"poky@lists.yoctoproject.org" <poky@lists.yoctoproject.org>
Subject: Re: [poky] runqemu on genericarm64: "u-boot.bin not found" error
Date: Mon, 27 Jan 2025 12:13:47 +0000 (UTC) [thread overview]
Message-ID: <9d6991b5-368f-4870-93c6-35e7e4c6fade@rootcommit.com> (raw)
In-Reply-To: <EFE01A51-DF3E-422C-AE1D-4F66EF1AA916@arm.com>
Hi Ross,
Thanks for these details!
On 1/27/25 12:47, Ross Burton wrote:
> On 27 Jan 2025, at 11:27, Michael Opdenacker via lists.yoctoproject.org <michael.opdenacker=rootcommit.com@lists.yoctoproject.org> wrote:
>> Ross, all,
>>
>> Probably not a surprise for some of you, but I figured it's good to report this somewhere:
>>
>> I generated an image for the "genericarm64" machine, and when trying to use the "runqemu" command, I get this error:
>>
>> $ runqemu nographic slirp
>> runqemu - INFO - Running bitbake -e ...
>> runqemu - ERROR - BIOS /home/mike/work/yocto/master/poky/build-genericarm64/tmp/deploy/images/genericarm64/u-boot.bin not found
>> runqemu - INFO - Cleaning up
>> runqemu - INFO - Host uptime: 670446.07
>>
>> That's not a surprise, as the bootloader for this image is based on grub.
>>
>> I tried to modify meta-yocto-bsp/conf/machine/genericarm64.conf to use the "grub-efi-bootaa64.efi" file instead. However, while runqemu doesn't complain any more, the virtual machine doesn't seem to boot.
>>
>> Any workaround for testing the "genericarm64" machine through the "runqemu" script?
>>
>> In the long run, it would be great if the normal "runqemu" command worked out of the box.
> From the genericarm64 README:
>
> There is also limited support for booting a genericarm64 image inside QEMU. When
> building the image also build the `u-boot` recipe to build the required
> firmware (note that this firmware will _not_ boot on real hardware), then use
> `runqemu` as usual.
>
> That uboot will then chainload into grub.
>
> I don’t think it’s appropriate to always build the uboot because there’s a risk that people will think it’s suitable for the target hardware, when it’s only useful with a qemu.
Understood! Indeed the following does the trick:
IMAGE_INSTALL:append = " u-boot"
Thanks again
Michael.
--
Michael Opdenacker
Root Commit
Yocto Project and OpenEmbedded Training course - Learn by doing:
https://rootcommit.com/training/yocto/
prev parent reply other threads:[~2025-01-27 12:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 11:27 runqemu on genericarm64: "u-boot.bin not found" error Michael Opdenacker
2025-01-27 11:47 ` [poky] " Ross Burton
2025-01-27 12:13 ` Michael Opdenacker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9d6991b5-368f-4870-93c6-35e7e4c6fade@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=Ross.Burton@arm.com \
--cc=poky@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.