doc/board/starfive/jh7110_common.rst: Documentation doesn't mention OpenSBI text start address
Yao Zi
me at ziyao.cc
Thu Apr 16 22:59:42 CEST 2026
On Thu, Apr 16, 2026 at 03:11:42PM +0000, Johannes Krottmayer wrote:
> Hello,
>
>
> I have used the U-Boot documentation for building OpenSBI and
> U-Boot for the Starfive VisionFive 2 board.
>
> Unfortunately there is a important definition missing (will be not
> mentioned in the current documentation) in the build step for
> OpenSBI.
>
> FW_TEXT_START from OpenSBI defaults to address 0x0, this raises
> an exception. FW_TEXT_START should be set to the correct address
> 0x40000000 and then it works.
Which component raises the exception, and which OpenSBI/U-Boot
versions are you using?
For OpenSBI, it supports being loaded on arbitrary addresses since
at least commit 0f20e8adcf42 (firmware: Support position independent
execution, 2021-03-17), which is much earlirer than the minimum version
than support for JH7110 in OpenSBI. Currently OpenSBI should be built as
position-independent code by default, FW_TEXT_START only helps debuggers
and etc. to correctly resolve symbols, while makes no constraint on
OpenSBI loading.
For U-Boot, the address to load OpenSBI is determined by
CONFJG_SPL_OPENSBI_LOAD_ADDR, which is 0x40000000 in
starfive_visionfive2_defconfig, and has nothing to do with FW_TEXT_START
configured in OpenSBI side.
>
> So therefore the correct build step should be:
> $ make PLATFORM=generic FW_TEXT_START=0x40000000
Thus I think probably the root cause of your failure has nothing to do
FW_TEXT_START. Might you check it further?
> Should I create a patch for the documentation to add this?
>
> --
> Kind regards,
>
> Johannes K.
>
Regards,
Yao Zi
More information about the U-Boot
mailing list