Hello together,
Sandeep, thank you for your input! With this info I was able to build and boot
petalinux-image-minimal using the zcu104 example XSA from xilinx github as HDF
file. As recommended I created my own meta layer and machine.conf using my own
MACHINE name to specify the HDF_xxx variables. For details see
https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/57836605/Creating+a+Custom+Xilinx+Yocto+Layer
and
https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/59605045/Adding+an+HDF+to+a+Xilinx+Yocto+Layer
However, as soon as I use my own XSA during compilation, u-boot hangs at
"Starting kernel".
---
Found U-Boot script /boot.scr
229 bytes read in 12 ms (18.6 KiB/s)
## Executing script at 20000000
17138176 bytes read in 1142 ms (14.3 MiB/s)
## Flattened Device Tree blob at 00100000
Booting using the fdt blob at 0x100000
Loading Device Tree to 000000000fff3000, end 000000000ffffd60 ... OK
Starting kernel ...
---
So my first step was to investigate u-boot boot commands. I noticed that
comparing boot.scr and uEnv (per my knowledge two different boot approaches by
u-boot) they use different memory addresses for loading kernel and dtb, as well
as two different dtb files (which are both present in the bitbake generated
image files).
boot.scr (shortened, and doesn't referr to any dtb):
booti 0x200000 - 0x100000
uEnv (shortened):
kernel_load_address=0x80000
devicetree_image=zynqmp-zcu104-revC.dtb
devicetree_load_address=0x4000000
booti ${kernel_load_address} - ${devicetree_load_address}
Can anyone comment on the differences in dtb and load addresses?
Any recommendations how to approach debugging the starting kernel freeze?
Thanks and regards,
Martin
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4734):
https://lists.yoctoproject.org/g/meta-xilinx/message/4734
Mute This Topic: https://lists.yoctoproject.org/mt/76101270/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
