HI All, In case somebody is looking for it, I successfully ported meta-xilinx to hardknott [1]: tested with custom hardware based on ZynqMPSoC.
Of course, I don't provide any support. Regards, Adrian [1] https://github.com/adrianf0/meta-xilinx On 20.08.2021 18:50, Adrian Fiergolski wrote: > Hi Mark, > > I have resolved all the compilation issues. > > However, booting stops at the level of SPL: > > U-Boot SPL 2021.01 (Jun 01 2021 - 11:54:06 +0000) > PMUFW: v1.1 > Loading new PMUFW cfg obj (2216 bytes) > Silicon version: 3 > EL Level: EL3 > Chip ID: zu6eg > Multiboot: 0 > Trying to boot from MMC2 > > I see you worked on adding EFI/Secure boot support. You also enabled the > secure boot by default in xilinx_zynqmp_virt_defconfig. Could this be > the problem? Have you tested it and does it run smoothly with SD card? > Do changes between u-boot-xlnx 2020.2 and 2021.1 require any > modification in other recipes? For example, I see that wic I still > creating a regular image, without a dedicated EFI partition. For secure > boot I imagine that certificates would be involved as well, though I > don't see anything regarding this in the master branch of meta-xilinx. > > Regards, > > Adrian > > On 16.08.2021 20:12, Adrian Fiergolski wrote: >> Hi Sai and Mark, >> >> Sai, your commit [1] introduces error, as patches do not apply. Have you >> tried to run it before the commit? >> >> In fact, most of the patches are not needed anymore and I have cleaned >> the recipes accordingly [2]. >> >> Anyway Mike, with the latest version of the pmu-firmware I am getting >> linking error: >> >> git/lib/sw_apps/zynqmp_pmufw/src/xpfw_core.c:192: undefined reference to >> `XIpiPsu_TriggerIpi' >> collect2: error: ld returned 1 exit status >> >> Does it ring a bell? As I assume xlnx_rel_v2021.1 to be stable in >> embeddedsw [3] (is it?), do I need to enable extra libraries in the >> pmu-firmware recipes? If so which one and how? Have you tried to run it >> recently? >> >> Regards, >> >> Adrian >> >> [1] 4218e11363ffb41799a89794a0a8fe6d36b86417 >> [2] https://github.com/adrianf0/meta-xilinx/tree/hardknott >> [3] https://github.com/Xilinx/embeddedsw >> >> On 16.08.2021 19:14, Adrian Fiergolski wrote: >>> Hi, >>> >>> As explained by Daniel in other thread, "the master branch has bumped >>> gcc to v11 already, but Yocto hardknott uses v10. Commit 21f495ec08 >>> ("Upgrade newlib, libgloss >>> 3.3 -> 4.1") (just before the gcc bump) fails to build as the binutils >>> patches don't apply." Thus I forked [1] from that commit and started to >>> make it work with hardknott. I have already aligned microblaze binutils >>> patches so they apply and compile properly. However, I see that there >>> are still some issues with other recipes which need to be addressed. >>> Feel free to contribute. >>> >>> Xilinx maintainers: feel free to pull to branch from my repository as a >>> base of hardknott branch in the official repository. >>> >>> Regards, >>> >>> Adrian >>> >>> [1] https://github.com/adrianf0/meta-xilinx/tree/hardknott >>>
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4928): https://lists.yoctoproject.org/g/meta-xilinx/message/4928 Mute This Topic: https://lists.yoctoproject.org/mt/84928826/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
