[meta-xilinx] ZC702 support in Xilinx meta-xilinx

Mike Looijmans mike.looijmans at topic.nl
Tue Apr 23 23:10:31 PDT 2013


> Yes it is our intention at this point to have a layer per board. I think
> there is an advantage in layering because it will help distinguish between
> architecture and bsp (i.e. Zynq and Microblaze vs Board/BSP 'configuration')

What would be the advantage of having a BSP per board?

I can mostly only find disadvantages. Many of the OpenEmbedded projects 
I work with are designed to build on multiple targets. Usually a single 
environment builds two or three different machines, and often this 
number increases when there are newer (or prototype) versions of 
products. One project now builds for 22 machine configurations.

I can see a case for a "microblaze" and a "zynq" layer, but I really 
don't see the advantage of having a zc702, zedboard, and various other 
separate layers that must be versioned and managed separately.

A EVM is usually a starting point for a project. It usually evolves from 
there, first just adding hardware to the board, and later with product 
prototypes based on similar hardware. When problems arise, we usually 
evaluate if the other board showed the same symptoms, so we can find out 
whether it's the hardware or software to blame. That makes it very 
important to always have access to multiple machines. If we need to add 
or switch layers to be able to target other machines, we can no longer 
be sure that we are using the same software on both, and we would have 
to thoroughly investigate the changes that each layer brings.

I hope these stories help you gain some perspective on how OE is being 
used in the wild.

Mike.



More information about the meta-xilinx mailing list