From: Philip Balister <philip@balister.org>
To: Edward Vidal <vidal.develone@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: toolchain
Date: Fri, 03 Jan 2014 17:48:18 -0500 [thread overview]
Message-ID: <52C73E32.4030208@balister.org> (raw)
In-Reply-To: <CANwz6nyQW9br6znzmLWLAM52n4UpQA1pbu9JBR0ZvT8UO8NQQw@mail.gmail.com>
Please post meta-xilinx questions to the meta-xilinx list.
On 01/03/2014 11:46 AM, Edward Vidal wrote:
> Hello all,
> I am currently working with the zedboard using a rootfs generated with a
> dylan branch of yocto (gsl, gnuplot, gnuradio, java, vlc, v4l-utils, and
> openCV with C920 camera). My zImage and devicetree.dtb were built with
> yocto sdk. My BOOT.BIN (FSBL system.bit and u-boot) were built with 14.4
> of Xilinx Tools. This requires dual booting a CentOS 6.4 x86_64 (Xilinx
> Tools) and Fedora19 x86_64 (Yocto). I have not been able to run Yocto on
> CentOS since the need for higher version of python.
>
> Is it possible to generate a BOOT.BIN with the files generated with
> Yocto?
See:
https://github.com/balister/meta-xilinx/tree/working-branch/recipes-bsp/u-boot
Basically, I use a pre-compiled fsbl.elf. This only needs the bootgen
command (from ISE) in the path. U-boot builds fine with the toolchain
built in OE. (Also, you can build the fsbl with an OE toolchain last
time I checked.
Philip
>
> This requires 2 toolchains. I was checking the difference between the 2
> see the attached files.
> Should the difference between the toolchains be of concern going forward?
>
> My Xilinx tools are node locked and I can only use on a single system.
> Is there a method to run Yocto on CentOS6.4 x86_64?
> Any and all help will be appreciated.
>
> Thanks
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
next prev parent reply other threads:[~2014-01-03 22:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 16:46 toolchain Edward Vidal
2014-01-03 22:48 ` Philip Balister [this message]
2014-01-03 23:00 ` toolchain Gary Thomas
-- strict thread matches above, loose matches on Subject: below --
2015-11-24 10:50 Toolchain Virgilia Eigner
2014-03-03 1:58 Toolchain Michael Gloff
2014-03-03 18:52 ` Toolchain Paul Eggleton
2014-03-05 17:00 ` Toolchain Michael Gloff
2014-03-05 17:45 ` Toolchain Paul Eggleton
2014-03-05 19:56 ` Toolchain Michael Gloff
2014-03-05 21:14 ` Toolchain Khem Raj
2014-03-06 12:57 ` Toolchain Paul Barker
2009-08-31 3:28 bogl: don't know screen type 1 mike
2009-08-31 12:06 ` Stephen R Marenka
2009-08-31 12:58 ` mike
2009-08-31 22:11 ` mike
2009-08-31 22:16 ` mike
2009-09-01 15:17 ` Stephen R Marenka
2009-09-04 15:43 ` toolchain, was " Finn Thain
2009-09-05 13:31 ` Maxim Kuvyrkov
2009-09-06 2:37 ` toolchain Finn Thain
2009-09-06 23:09 ` toolchain Stephen R Marenka
2009-09-06 5:20 ` toolchain Finn Thain
2009-09-08 13:07 ` toolchain Finn Thain
2008-07-03 14:17 qt4x11 vs. uicmoc4-native vs. qmake2-native Geoffrey Wossum
2008-07-04 6:54 ` Toolchain Stefano Regno
2008-07-04 12:56 ` Toolchain Leon Woestenberg
2008-07-23 15:09 ` Toolchain Stefano Regno
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52C73E32.4030208@balister.org \
--to=philip@balister.org \
--cc=vidal.develone@gmail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.