[meta-xilinx] Support for PicoZed 7030 and FMC V2 Carrier

[Thomas Goodwin]

Thanks for confirming. I ended up doing something similar to the kernel
too. Hopefully Xilinx does upstream the patch!

On Tue, Jul 31, 2018 at 4:38 PM Andreas Galauner <andreas at galauner.de>
wrote:

> 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.
>
> You find the patch attached. Maybe Xilinx should upstream that. The
> u-boot is just broken on Picozeds without this.
>
> - Andy
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20180731/cd6bcd18/attachment.html>