Re: [meta-xilinx] Xilinx, why are you breaking the meta-xilinx-bsp layer?

Ditto on all Martin said. We also wish to move away from bloated, slow and buggy meta-xilinx-tools. Sent from my iPhone > On May 15, 2018, at 10:55, Peter Smith wrote: > > I shall second this -- ___ meta-xilinx mailing list

Re: [meta-xilinx] Provider of pmu-firmware [rel-v2018.1]

On 15 May 2018 at 20:54, Martin Siegumfeldt wrote: > Hi, > > Based on > https://github.com/Xilinx/meta-xilinx-tools/commit/a516c3a4a8b29e07233b5f2ecf91a2a3e63a1ff7 > I would like to switch from building the pmu-firmware using the XSDK (i.e. > through meta-xilinx-tools) to

[meta-xilinx] Provider of pmu-firmware [rel-v2018.1]

Hi, Based on https://github.com/Xilinx/meta-xilinx-tools/commit/a516c3a4a8b29e07233b5f2ecf91a2a3e63a1ff7 I would like to switch from building the pmu-firmware using the XSDK (i.e. through meta-xilinx-tools) to the generated toolchain (i.e. through meta-xilinx). However the latter layer seems

Re: [meta-xilinx] rel-v2018.1 / zcu102-zynqmp: U-boot crashes with error "fdt_root: FDT_ERR_BADMAGIC"

Hi, I've been debugging some more and I can confirm that it jumps successfully to the ATF but the ATF crashes before it writes anything to the uart, such as its usual version notice information. Debugging the ATF I've found that it crashes trying to retrieve the chip id via the