The two recipes are different for sure, I noticed this only yesterday and yes you need xsct for m-x-t
On Thu, 19 Jul 2018, 14:58 Giordon Stark, <[email protected]> wrote: > Hi JF, > > No, but I am on rocko so it's got the two different layers under > meta-xilinx and I'm using the meta-xilinx-bsp version. Is meta-xilinx-tools > completely different? The main reason I'm not using meta-xilinx-tools right > now is that my understanding is I need the SDK installed on the machine and > point m-x-t at it, and I'm just trying to get things in a way that doesn't > depend on something external to yocto... > > Giordon > > On Thu, Jul 19, 2018 at 8:55 AM Jean-Francois Dagenais < > [email protected]> wrote: > >> Hi Giordon, >> >> > On Jul 19, 2018, at 8:58 AM, Giordon Stark <[email protected]> wrote: >> > >> > However, when recompiling and re-running -- I do not see extra debug >> information from the PMUFW -- so I'm patching the kernel >> drivers/clk/zynqmp/pll.c to get more information about the PLL hang itself >> in the meantime. >> > >> > Any ideas? Did I do something wrong in enabling the debug flags? >> >> Are you using the meta-xilinx-tools pmu_firmware recipe? >> >> I ask because, coincidently, I am discussing a patch in >> xsctbase:do_configure about cleaning the xsct workspace on do_configure >> start to avoid these kinds of behaviour. See >> https://lists.yoctoproject.org/pipermail/meta-xilinx/2018-June/003916.html >> and >> https://lists.yoctoproject.org/pipermail/meta-xilinx/2018-July/003986.html >> >> Turns out I had the manual "rm" in my local repo only, but the point >> remains. >> >> Hope this helps! > > -- > Giordon Stark > -- > _______________________________________________ > meta-xilinx mailing list > [email protected] > https://lists.yoctoproject.org/listinfo/meta-xilinx >
-- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
