Re: [Buildroot] [Help] How to bump a package, e.g., OpenSBI?

[Julien Olivain <ju.o@free.fr>]

Hi Kilian,

On 27/12/2024 19:31, Kilian Zinnecker via buildroot wrote:
> 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 was able to reproduce this issue.

I was also able to work around it by replacing "fw_jump.elf" by
"fw_jump.bin" in [1]. See also [2].

So, to summarize: it is OK to bump the default opensbi version to 1.6
in a commit (without touching the defconfigs) since we are able to
make it work in qemu with a workaround. IT might be a good idea to
add a reference to [2] in the commit log.

Since we learned that opensbi 1.6 no longer start our qemu defconfigs,
we could update those qemu_riscv{32,64}_virt_defconfigin in separate 
commits
to use opensbi 1.6, and also the corresponding
updating board/qemu/riscv{32,64}-virt/readme.txt which is used to 
generate
the output/images/start_qemu.sh script.

> 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.

This is a known issue. See [3] for some details.

> Thanks and best regards,
> Kilian

Best regards,

Julien.

[1] 
https://gitlab.com/buildroot.org/buildroot/-/blob/2024.11/board/qemu/riscv64-virt/readme.txt?ref_type=tags&plain=1#L3
[2] https://github.com/riscv-software-src/opensbi/issues/372
[3] 
https://gitlab.com/buildroot.org/buildroot/-/commit/47fc9e5509837260310cd7e41335fade29b587b1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot