Since the FPGA runner can load multiple ELFs/binaries before jumping into DRAM, we do not need to build OpenSBI wrapping a U-Boot or other payload binary in FW_PAYLOAD mode, and instead can just build an OpenSBI image in FW_JUMP mode, U-Boot, and any OpenSBI tests separately, and load both. This has some advantages:
- Reduce the number of OpenSBI builds to one - currently there is one to wrap U-Boot, and another to wrap a binary that tests some OpenSBI functionality.
- Less inter-dependencies in the build system - OpenSBI, Linux, and U-Boot would be built separately.
Since the FPGA runner can load multiple ELFs/binaries before jumping into DRAM, we do not need to build OpenSBI wrapping a U-Boot or other payload binary in
FW_PAYLOADmode, and instead can just build an OpenSBI image inFW_JUMPmode, U-Boot, and any OpenSBI tests separately, and load both. This has some advantages: