From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Ross Burton <ross.burton@arm.com>
Cc: "poky@lists.yoctoproject.org" <poky@lists.yoctoproject.org>,
michael.opdenacker@rootcommit.com
Subject: runqemu on genericarm64: "u-boot.bin not found" error
Date: Mon, 27 Jan 2025 11:27:36 +0000 (UTC) [thread overview]
Message-ID: <30b7ea7f-6793-4150-8551-ddc9b093255a@rootcommit.com> (raw)
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.
Cheers
Michael.
--
Michael Opdenacker
Root Commit
Yocto Project and OpenEmbedded Training course - Learn by doing:
https://rootcommit.com/training/yocto/
next reply other threads:[~2025-01-27 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 11:27 Michael Opdenacker [this message]
2025-01-27 11:47 ` [poky] runqemu on genericarm64: "u-boot.bin not found" error Ross Burton
2025-01-27 12:13 ` Michael Opdenacker
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=30b7ea7f-6793-4150-8551-ddc9b093255a@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=poky@lists.yoctoproject.org \
--cc=ross.burton@arm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox