[meta-xilinx] [yocto] TUNE_PKGARCH for Microblaze
Sipke Vriend
sipke.vriend at xilinx.com
Tue Apr 2 23:14:21 PDT 2013
Hi Elvis,
Please check git.xilinx.com in the next couple of days for a yocto folder
containing a few git repos containing our yocto development.
Once they are there, start by looking at
yocto/meta-workarounds.git:README.yocto file (among others).
As the README's indicate this is work in progress and is targeted
at Poky 1.3/Danny.
The Zync setup is minimal at this stage.
The Microblazeel tune setup (as per previous emails regards this on
yocto at yoctoproject.org) is reasonable and what we propose to
proceed with (pending any further feedback). There is still some minor
work we intend to do there, but mainly to improve sanity checking etc.
Microblazeel.conf in meta-xilinx is the 'default' machine and can be used
as a template or alternatively it can be used and features can be supplied
in the local.conf file:
TUNE_FEATURES_tune-microblaze += "barrel-shift multiply-high multiply-low
pattern-compare reorder divide-hard fpu-hard fpu-hard-extended"
The architecture layer will then take care of creating the relevant ccflags
and package names.
We are layering using this 'bottom rung architecture layer' to encapsulate all
architecture features, on top of which relevant machine/bsps can be
constructed by simply defining any of the allowed features (and 'versions').
Right now only this 'architecture layer' exists (expect a slight restructure of
directories in future to allow for bsps etc).
Studying your tar file it seems that you may be able to leverage off this
'architecture layer'.
As John mentioned building tool chains from within yocto is a to-do for us,
so you're a step (or two) ahead of us there. We're using tarred tool chains
from Xilinx tool installs (or from git.xilinx.com).
Regards
Sipke
>From: Elvis Dowson [mailto:elvis.dowson at gmail.com]
>Sent: Saturday, 30 March 2013 11:48 PM
>To: Sipke Vriend
>Cc: meta-xilinx Mailing List; John Williams
>Subject: Re: [meta-xilinx] [yocto] TUNE_PKGARCH for Microblaze
>
>Hi,
> I'm attached a tarball overlay which contains work-in-progress tune
> files for MicroBlaze, for the current meta-xilinx master branch.
>
>
>It contains just the basic definitions
>hard-float
>soft-float
>big-endian
>little-endian
>
>and assumes, as a baseline MicroBlaze cpu v6.00.a.
>
>gcc-4.8 pre-release from 4 weeks ago gave an error saying that it did not
>support microblaze cpu v8.40.b. The online docs currently list v3.00.a,
>v4.00.b, v5.00a, v5.00b and v6.00a as example values.
>
>We could try to use this as a bare minimum, to try and get gcc-4.8 recipes to
>build from within yocto.
>
>I haven't had much success with this, for both gcc-4.8 release, as well as the
>current gcc-4.9 experimental version, from within yocto.
>
>You can use Khem Raj's recipes to get gcc-4.8 to build with yocto.
>
>http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gcc-4.8
>
>To enable gcc 4.8, set the following variable in local.conf
>
>GCCVERSION = "4.8%"
>
>
>Elvis Dowson
>
>
>>
>-----Original Message-----
>From: Elvis Dowson [mailto:elvis.dowson at gmail.com]
>Sent: Friday, 29 March 2013 7:30 PM
>To: Sipke Vriend
>Cc: meta-xilinx Mailing List
>Subject: Re: [meta-xilinx] [yocto] TUNE_PKGARCH for Microblaze
>
>Hi Sipke,
>Do you have an updated tune file for microblazeel available,
>in some form? I'd like to test it out. I'm getting my VC709 board in a
>few days.
>
>Best regards,
>
>Elvis Dowson
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20130403/8fee5dbd/attachment.html>
More information about the meta-xilinx
mailing list