[meta-xilinx] trying to build core-image-zynq with yocto exposes conflicting patch files

[John Williams]

Hi Mike,

> -----Original Message-----
> From: meta-xilinx-bounces at yoctoproject.org [mailto:meta-xilinx-
> bounces at yoctoproject.org] On Behalf Of Mike Looijmans
> Sent: Wednesday, 3 April 2013 11:36 PM
> To: meta-xilinx at yoctoproject.org
> Subject: Re: [meta-xilinx] trying to build core-image-zynq with yocto exposes
> conflicting patch files
> 
> On 04/03/2013 02:52 PM, Robert P. J. Day wrote:
> > On Tue, 2 Apr 2013, Philip Balister wrote:
> >
> >> On 04/02/2013 02:45 AM, Mike Looijmans wrote:
> >>> On 04/01/2013 05:02 PM, Robert P. J. Day wrote:
> >>>>>>    (aside: hoping this is the right place for this. i just
> >>>>>> purchased a zedboard and i want to build bootable images for it
> >>>>>> both from scratch, and using oe/yocto. would those approaches
> >>>>>> represent two separate forums i should be using?)
> >>>>>>
> >>>>>>    with fully-updated oe-core and meta-zynq yocto layers, i tried
> >>>>>> to build "core-image-zynq" and got:
> >>>>>>
> >>>>>> ERROR: Command Error: exit status: 1  Output:
> >>>>>> Applying patch no-gtk.patch
> >>>>>> patching file Makefile
> >>>>>> Hunk #1 FAILED at 1.
> >>>>>> 1 out of 1 hunk FAILED -- rejects in file Makefile Patch
> >>>>>> no-gtk.patch does not apply (enforce with -f)
> >>>>>> ERROR: Function failed: patch_do_patch
> >>>
> >>> At the last count, there were five.
> >>>
> >>> As far as I know, "mine" is the only one that also properly targets
> >>> the zedboard. It's a fork of Philip's.
> >>>
> >>> https://github.com/milosoftware/meta-zynq
> >>
> >> What can we do to get some basic support for (say) zc702 and the
> >> zedboard into the "official" Xilinx layer so we can all tell new
> >> people where to start?
> >
> >    +1.  again, all i want to do with my new zedboard is (ideally)
> > build a bootable, SD-based system from scratch with OE. the board came
> > with a functioning SD card so i have a baseline to work from, in the
> > sense that i can at least see what i'm trying to reproduce.
> >
> >    based on what i've read, it now appears that my best bet is to
> > start with mike's layer here:
> >
> >    http://layers.openembedded.org/layerindex/layer/meta-zynq-milo/
> >
> > since it has explicit zedboard support. with that layer, i'd select a
> > MACHINE of "zedboard" and, since i see no zedboard-specific image, i
> > guess i'd just try to build a core-image-minimal, unless i've
> > overlooked something.
> 
> The layer provides an image that's obscurely named "my-image", which will boot
> from SD but will also fit in the on-board flash.
> 
> >    the README in that layer states:
> >
> > "Build BOOT.bin using Xilinx tools (which you'll need to install for
> > this) from within OE. u-boot will be built by OE, you'll need to
> > create a FSBL and optionally a logic bit file and point OE variables
> > to their location."
> >
> >    so ... i need to install additional xilinx tools? is that
> > documented in more detail somewhere? i can see from philip's README:
> 
> OE will build a u-boot based bootloader, but you cannot use it directly on the
> zynq boards. You need to build a first stage bootloader (FSBL) using Xilinx's tools,
> and (optionally, so skip it for now) a bitfile image for the FPGA.
> 
> For this, you need to install the Xilinx XPS tools, which will require a few dozen
> gigabytes of diskspace.
> 
> I seriously considered providing a standard bitfile and FSBL binary to help people
> get started much faster, but I did not dare because I do not understand the
> licensing.
> 

This is precisely the plan.  We (Xilinx) are consolidating a meta-xilinx layer that will include BSP support for our popular boards - ZC702, 706, ZedBoard etc.  The plan for now is that these BSPs will include prebuilt FSBL images so that a user can boot something without a Xilinx tool install etc.

This is underway right now - we will be pushing the work-in-progress git repos public in the next few days.

Rgds,

John