From: Kilian Zinnecker via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org, mark@dibsco.co.uk, alistair@alistair23.me
Subject: Re: [Buildroot] [Help] How to bump a package, e.g., OpenSBI?
Date: Fri, 27 Dec 2024 19:31:19 +0100 [thread overview]
Message-ID: <2761179.mvXUDI8C0e@kilian-laptop> (raw)
In-Reply-To: <3f1890a6dce4859431fb9b8d0e4747e9@free.fr>
Hello Julien, hello Mark, hello Alistair,
Mark and Alistair, I added you, because you are listed in the DEVELOPERS file
for qemu_riscv64_virt_defconfig / OpenSBI - hope its ok ;)
[--SNIP--]
> This is correct. You can have a look how the previous versions
> were updated, for details. For example, see [3].
> This will update only the default "latest" OpenSBI version. Usually,
> defconfigs in Buildroot are using a specific, fixed custom version.
Thanks Julien! I locally adjusted the OpenSBI version number and the package's
hash. Then I adjusted the used version of OpenSBI in the
qemu_riscv64_virt_defconfig and started a build: The build was successfull,
hence also the build of OpenSBI v1.6 worked. However, when I try to run
output/images/start_qemu.sh I get the error, that ROM regions do overlap:
The following two regions overlap (in the memory address space):
fw_jump.elf ELF program header segment 1 (addresses 0x0000000000000000 -
0x00000000000271e0)
mrom.reset (addresses 0x0000000000001000 - 0x0000000000001028)
I guess, that the OpenSBI image had a different starting address in the past,
leaving some space for mrom.reset? I double checked, and when building
qemu_riscv64_virt_defconfig without modifying its OpenSBI version, it still
works, so the problem must come from my changes. I am not so familiar with
OpenSBI and also not with Qemu and hence was not able to find a solution to the
problem yet.
I also tried building qemu_riscv64_virt_efi_defconfig, but that board seems to
need a github login to fetch some package. I didn't look into this in much
detail yet (e.g., whether it was my fault for some reason), but I am planning
to have another look at that and then maybe sent a separate email for this
issue.
Thanks and best regards,
Kilian
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-12-27 18:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-26 21:19 [Buildroot] [Help] How to bump a package, e.g., OpenSBI? Kilian Zinnecker via buildroot
2024-12-26 22:16 ` Julien Olivain
2024-12-27 18:31 ` Kilian Zinnecker via buildroot [this message]
2024-12-28 18:33 ` Julien Olivain
2024-12-28 19:28 ` Kilian Zinnecker via buildroot
2024-12-29 11:40 ` Kilian Zinnecker via buildroot
2024-12-29 12:44 ` Julien Olivain
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=2761179.mvXUDI8C0e@kilian-laptop \
--to=buildroot@buildroot.org \
--cc=alistair@alistair23.me \
--cc=ju.o@free.fr \
--cc=kilian.zinnecker@mail.de \
--cc=mark@dibsco.co.uk \
/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