Hi Andy, > -----Original Message----- > From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx- > boun...@yoctoproject.org] On Behalf Of Andreas Galauner > Sent: Tuesday, July 31, 2018 1:39 PM > To: meta-xilinx@yoctoproject.org; Thomas Goodwin > <btgood...@geontech.com> > Subject: Re: [meta-xilinx] Support for PicoZed 7030 and FMC V2 Carrier > > On 10.07.2018 17:05, Thomas Goodwin wrote: > > Hello, > > > > I'm attempting to build the picozed-zynq7 machine using meta-xilinx > > with Poky 2.4.2. I've tried using the /rocko/ branch as well as > > /rel-v2018.2/. For the latter, I had to patch the machine definition > > since it was missing /require > > /(PR: https://github.com/Xilinx/meta-xilinx/pull/9). My layer > > configuration is: > > > > BBLAYERS ?= " \ > > /ssd/yocto_projects/picozed/poky/meta \ > > /ssd/yocto_projects/picozed/poky/meta-poky \ > > /ssd/yocto_projects/picozed/poky/meta-xilinx/meta-xilinx-bsp \ > > " > > > > In each case, I can build /core-image-minimal/, however there is no > > console output on boot over the UART. The D10 and D11 PS LEDs on the > > FMC carrier card are flashing in sync. > > > > Has anyone else successfully built for this target recently? > > Yes, the u-boot device tree is broken for the Picozed. There is no console > defined > (the chosen/stdout-path node is missing) and because of that u-boot panics and > the board resets. That's why the LEDs are "blinking" > > I stepped through the code using JTAG and found out what's causing this after > a > longer debugging session. I fixed the device tree and it started to work. I > also > added some more stuff to it like USB, QSPI and the Ethernet MAC. In theory > that > should make them work as well, but I'm not sure if I ever tested that.
Can you submit the patch to u-boot mainline? Thanks, Manju -- _______________________________________________ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
