Poke! Anyone at Xilinx get a chance to look into this? Am I the only one getting this problem? Anyone using meta-xilinx-tools 2019.1 on a custom board?
> On Jun 25, 2019, at 12:50, Jean-Francois Dagenais <jeff.dagen...@gmail.com> > wrote: > > So, this is following my previous misadventure with booting without u-boot. > FYI, we have our own board with a zynqmp on it. So not using the pre-defined > boards. > > The culprit being that the PMU firmware was overwriting my kernel because of > this: > > 2019.1+gitAUTOINC+26c14d9861-r0/build/pmu-firmware/zynqmp_pmufw_bsp/psu_pmu_0/include/xparameters.h:#define > XPAR_MICROBLAZE_DDR_RESERVE_SA 0 > > This is a BSP auto-created from xsctbase.bbclass (I believe) using the > handoff file as reference. As you can see, 0 is wrong here as it then means > > #define FSBL_STORE_ADDR > (XPAR_MICROBLAZE_DDR_RESERVE_SA + 0x80000U) > > from xpfw_restart.h means the FSBL is copied over the kernel's default > loading address. > > I have aligned my handoff with meta-xilinx-tools. 2019.1 everywhere, still, > XPAR_MICROBLAZE_DDR_RESERVE_SA is zero. > > This means I will most likely not be the only one with this problem. > > Am I missing something? Should one edit xparameters.h? If so, how? Because I > gathered it was auto-generated, correct? > -- _______________________________________________ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
