Hello together, to close this topic off, I have found the reason why my linux doesn't boot, it's the dtb included in boot.bin. As a workaround, I figured out that my system can boot when I build the petalinux-image-minimal with my custom XSA using petalinux-tools following UG1144.
By retrieving bootgen.bif from the yocto build output, then replacing
<machine>-system.dtb with the system.dtb output from
petalinux-tools, and then generating a new boot.bin (using bootgen, see UG1283)
I can now boot my linux kernel generated with yocto.
Running a diff on the autogenerated system-top.dts between yocto and
petalinux-tools, I see only trivial changes in uart aliases.
Why these happen, although both build systems use the same Xilinx tools in the
background to autogenerate the dts, I don't
understand yet.
--diff--
aliases {
ethernet0 = &gem3;
i2c0 = &hdmi_ctl_iic;
i2c1 = &i2c0;
i2c2 = &i2c1;
- serial0 = &axi_uart16550_0;
+ serial0 = &uart0;
serial1 = &axi_uart16550_1;
- serial2 = &uart0;
+ serial2 = &axi_uart16550_0;
serial3 = &uart1;
spi0 = &qspi;
};
--------
I am now planning on using my own dts and to skip the dts autogeneration
completely.
Best regards and thanks to your support,
Martin
smime.p7s
Description: S/MIME cryptographic signature
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4735): https://lists.yoctoproject.org/g/meta-xilinx/message/4735 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]] -=-=-=-=-=-=-=-=-=-=-=-
