[meta-xilinx] Building boot.bin for zc702 from meta-xilinx

Joe MacDonald Joe_MacDonald at mentor.com
Mon Jul 14 08:26:52 PDT 2014


[Re: [meta-xilinx] Building boot.bin for zc702 from meta-xilinx] On 14.07.14 (Mon 17:04) Mike Looijmans wrote:

> I just discovered that the "ps7_init.tcl" file exported has no
> license header. It contains the same settings though.
> 
> It should be easy to write a python script that takes the TCL code
> and turns it into C code suitable for u-boot-spl (which would look
> suspiciously much like ps7_init.c)
> 
> Would that work around the license issue or is there something I missed here?

It might, it might not.  That's a question of copyright, I think, and
not something I'd approach at all.  :-)

-J.

> 
> Mike.
> 
> 
> On 06/26/2014 07:32 AM, Mike Looijmans wrote:
> >Good point.
> >
> >So far, I've been exporting the ps7_init files from the FPGA build (in an
> >OpenEmbedded recipe) into the sysroot where u-boot-spl imports it.
> >
> >I thought that this might violate Xilinx's license, but it the other way
> >around indeed - the Xilinx license just says "do whatever you like with this,
> >as long as it's for our devices", which is challenging to violate (I can't
> >imaging anyone wanting to run the Zynq boot code on an Altera device). But the
> >other way around is clearly not right - the Xilinx license is not GPL compatible.
> >
> >They're actually just a bunch of register settings. So indeed we should use an
> >alternative.
> >
> >Mike.
> >
> >
> >On 06/26/2014 01:18 AM, andrey wrote:
> >>Hello Joe,
> >>
> >>this is a legitimate concern, because when you add ps7_init to your sources,
> >>you can not distribute the generated binary as it would violate the GNU GPL
> >>license of U-Boot.
> >>
> >>This is why we developed ezynq project that does not depend on any proprietary
> >>licensed files:
> >>
> >>http://sourceforge.net/p/elphel/ezynq/ ,
> >>http://sourceforge.net/p/elphel/meta-ezynq/
> >>
> >>It is also part of the distro for Elphel camera
> >>http://sourceforge.net/p/elphel/meta-elphel393
> >>
> >>Andrey
> >>
> >>---- On Wed, 25 Jun 2014 15:52:31 -0700 *Joe MacDonald
> >><Joe_MacDonald at mentor.com>* wrote ----
> >>
> >>    I'm kind of confused about what I'm seeing here and I hope someone can
> >>    set me straight.
> >>
> >>    I have a ZC702 that I'm trying to boot (from SD) Yocto master on right
> >>    now and it seems that no matter what approach I take, the boot.bin that
> >>    gets built is garbage. I've reduced the configuration to the simplest
> >>    possible, I think:
> >>
> >>    BBLAYERS ?= " \
> >>    /build/jjm/external/yocto/meta \
> >>    /build/jjm/external/yocto/meta-yocto \
> >>    /build/jjm/external/yocto/meta-yocto-bsp \
> >>    /build/jjm/external/meta-xilinx \
> >>    "
> >>    BBLAYERS_NON_REMOVABLE ?= " \
> >>    /build/jjm/external/yocto/meta \
> >>    /build/jjm/external/yocto/meta-yocto \
> >>    "
> >>
> >>    I've set the MACHINE to zc702-zynq7 and I'm building core-image-minimal
> >>    (and, later, u-boot-xlnx) and everything appears good. Except the
> >>    boot.bin that gets generated as part of the build is obviously unhappy:
> >>
> >>    -rw-r--r-- 1 jjm jjm 44K Jun 25 10:28
> >>
> >>./tmp/work/zc702_zynq7-poky-linux-gnueabi/u-boot-xlnx/master-next-xilinx+git-r0/git/boot.bin
> >>
> >>
> >>
> >>    (FWIW, identical results if I build 2014.1 instead of master-next, this
> >>    just happened to be the first build I switched to for the example.)
> >>
> >>    If I put this boot.bin on my SD card, nothing ever appears on the serial
> >>    console and it never boots. No big surprise there, I imagine. Anyway,
> >>    if I take the boot.bin from the 2014.1 release from:
> >>
> >>
> >>http://www.wiki.xilinx.com/file/view/2014.1-release.tar.xz/511741638/2014.1-release.tar.xz
> >>
> >>
> >>
> >>    and use the remainder of the components from my own build (kernel and
> >>    filesystem image) I can boot fine. I also happen to have the 2014.2
> >>    Xilinx toolchain and petalinux installed and that seems okay, but I
> >>    thought, looking at meta-xilinx and the mailing list archives, that I
> >>    should be able to build a functional boot.bin using only Yocto project
> >>    tools today. Am I just mistaken on this and I still need to use some
> >>    Xilinx toolchain to create a usable boot.bin? Is that what everyone
> >>    else is doing?
> >>
> >>    --
> >>    -Joe MacDonald.
> >>    :wq
> >>    --
> >
> >Met vriendelijke groet / kind regards,
> >
> >Mike Looijmans
> >
> >TOPIC Embedded Systems
> >Eindhovenseweg 32-C, NL-5683 KH Best
> >Postbus 440, NL-5680 AK Best
> >Telefoon: (+31) (0) 499 33 69 79
> >Telefax:  (+31) (0) 499 33 69 70
> >E-mail: mike.looijmans at topic.nl
> >Website: www.topic.nl
> >
> >Please consider the environment before printing this e-mail
> >
> >Topic zoekt FPGA experts
> >http://topic.nl/vacatures/word-jij-onze-nieuwe-fpga-expert/
> >
> >
> 
> Met vriendelijke groet / kind regards,
> 
> Mike Looijmans
> 
> TOPIC Embedded Systems
> Eindhovenseweg 32-C, NL-5683 KH Best
> Postbus 440, NL-5680 AK Best
> Telefoon: (+31) (0) 499 33 69 79
> Telefax:  (+31) (0) 499 33 69 70
> E-mail: mike.looijmans at topic.nl
> Website: www.topic.nl
> 
> Please consider the environment before printing this e-mail
> 
> Topic zoekt FPGA experts
> http://topic.nl/vacatures/word-jij-onze-nieuwe-fpga-expert/
> 
> _______________________________________________
> >>    meta-xilinx mailing list
> >>    meta-xilinx at yoctoproject.org <mailto:meta-xilinx at yoctoproject.org>
> >>    https://lists.yoctoproject.org/listinfo/meta-xilinx
> >>
> >>
> >>
> >>
> >
> 
-- 
-Joe MacDonald.
:wq
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20140714/bc3ab97d/attachment.pgp>


More information about the meta-xilinx mailing list