I am following the Yocto "community flow". I am learning as we go. See
below for my further analysis.
I think a *lot* of things currently are still wrong, here are my
finding of today. Please if I am on a completely misguided track, let
me know, I am coming back to ZCU102 board from rev. A to rev 1.1 after
four years or so.
- I think SPL without ATF is currently broken on the actual ZynqMP
boards. The DTB and/or kernel expect PSCI/ATF.
QEMU boots a ZCU102 only because it does not follow the SPL boot but
loads the ATF.
- SPL w/ ATF requires "bl31.bin" (ARM Trusted Firmware) to reside in
the U-Boot ${B}/
- This is not performed in some automated manner.
- U-Boot will then generate "u-boot.itb" which is a FIT with BL31,
DTBs, kernel(s) and a configuration to select one DTB.
- We will not deploy u-boot.itb, but this is the only accepted approach...
- ...as the legacy .ub files are not accepted by SPL, due to:
260:CONFIG_LEGACY_IMAGE_FORMAT=y
368:# CONFIG_SPL_LEGACY_IMAGE_SUPPORT is not set
- Somehow CONFIG_PMUFW_INIT_FILE does not propagate into ${B}/.config,
even if we supply it via EXTRA_OEMAKE arguments.
- CONFIG_ZYNQMP_SPL_PM_CFG_OBJ_FILE is currently not cared for (and
must be manually set). This is a known issue.
- meta-xilinx/meta-xilinx-bsp/recipes-bsp/u-boot/u-boot-zynq-scr.bb is
not compatible with the above.
(I think, it uses ARCH=arm for mkimage even for zynqmp which is
arm64/AArch64). Even then U-Boot will not accept it.
With manual entry of boot.scr into the U-Boot console, I could boot
the linux-xlnx kernel.
Regards,
Leon.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4838):
https://lists.yoctoproject.org/g/meta-xilinx/message/4838
Mute This Topic: https://lists.yoctoproject.org/mt/80282679/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
