On 3/14/23 11:40 PM, David Babich wrote:
Brutal... I figured out the problem. I assumed that the default u-boot
environment with my config fragment changes would be packaged in 'u-boot.bin'.
So while debugging this issue I only swapped u-boot.bin on my SD card. I just
now thought, "Hmm maybe its in boot.bin???". So I replaced my boot.bin on the
SD card and the default environment reflects my changes. I was confused because
in petalinux I always package u-boot into the boot.bin. But with meta-xilinx,
u-boot.bin is loaded separately with the default environment for u-boot packaged
with boot.bin. I learned many things about u-boot, but sadly this was largely
chasing red herrings.
boot.bin is constructed of everything needed to boot your board:
https://github.com/Xilinx/meta-xilinx/tree/rel-v2022.2/meta-xilinx-core/recipes-bsp/bootbin
https://github.com/Xilinx/meta-xilinx/blob/rel-v2022.2/meta-xilinx-core/recipes-bsp/bootbin/machine-xilinx-zynqmp.inc
So for zynqmp, it contains "fsbl", "pmufw", "atf", "u-boot", "device-tree" and
"bitstream".
The items can't (in a normal boot) be loaded without being part of the overall
boot.bin. There are alternative (not officially supported) flows that do allow
certain individual items to be loaded differently, but generally speaking each
of these needs to be in memory to get through the boot process and into u-boot.
(Once into u-boot, then everything can run off of mtd, mmc or a more traditional
disk.)
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5181):
https://lists.yoctoproject.org/g/meta-xilinx/message/5181
Mute This Topic: https://lists.yoctoproject.org/mt/97532410/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
