Re: [meta-xilinx] Xilinx SDK toolchain

[Manjukumar Harthikote Matha]

Hi Ed,

> -Original Message-
> From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx-
> boun...@yoctoproject.org] On Behalf Of Edward Wingate
> Sent: Thursday, May 17, 2018 9:14 AM
> To: meta-xilinx@yoctoproject.org
> Subject: [meta-xilinx] Xilinx SDK toolchain
> 
> I've been using a jethro build on a Zynq-7000 system.  When I create/build a 
> Linux
> Application hello world project on Xilinx SDK
> 2016.3 and try executing it, I get "-sh: ./test.elf: No such file or
> directory".   I think this is because of a toolchain or rootfs library
> mismatch between the Xilinx SDK and the Linux distro.  The Xilinx SDK is 
> currently
> using toolchain "Xilinx ARM v7 GNU/Linux Toolchain"
> 
> How would I set up the Xilinx SDK to be able to use the proper toolchain or
> libraries? I am running Xilinx SDK on a Windows7 machine, while the jethro 
> Yocto
> build is running on a Ubuntu Linux machine.  Do I need to point the Xilinx 
> SDK to
> something that Yocto produces on the Linux machine?
> 
> Thanks for your help.
>

Can you check with Xilinx forum on this issue as well?
https://forums.xilinx.com/t5/Embedded-Development-Tools/bd-p/EDK
 
Thanks,
Manju
-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

[meta-xilinx] Xilinx SDK toolchain

[Edward Wingate]

I've been using a jethro build on a Zynq-7000 system.  When I
create/build a Linux Application hello world project on Xilinx SDK
2016.3 and try executing it, I get "-sh: ./test.elf: No such file or
directory".   I think this is because of a toolchain or rootfs library
mismatch between the Xilinx SDK and the Linux distro.  The Xilinx SDK
is currently using toolchain "Xilinx ARM v7 GNU/Linux Toolchain"

How would I set up the Xilinx SDK to be able to use the proper
toolchain or libraries? I am running Xilinx SDK on a Windows7 machine,
while the jethro Yocto build is running on a Ubuntu Linux machine.  Do
I need to point the Xilinx SDK to something that Yocto produces on the
Linux machine?

Thanks for your help.

Ed
-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

Re: [meta-xilinx] [PATCH] bootbin: fix race condition in create_bif

[Jean-Francois Dagenais]

Hi Manju!

> On May 16, 2018, at 12:36 PM, Manjukumar Harthikote Matha 
>  wrote:
> 
> Will change python code to add  
> bootbindeps = bootbindeps + " " + attrdepends[cfg] + ":do_deploy" 
> instead of do_deploy in BIF_PARTITION_DEPENDS and apply it.

See the last part of my commit message. The reason I chose to do it like this is
explained. Essentially, when xilinx-bootbin.bb adds the "do_deploy" it assumes
that the source of BIF_ATTRIBUTE_xyz used a "DEPLOY_DIR" file. This creates an
unhealthy assumption, tightly couples xilinx-bootbin.bb and the BIF_ATTRIBUTE
assignments and makes the recipe more fragile.

If I were to use a file found in say ${STAGING_DIR_HOST}, then xilinx-bootbin.bb
would incorrectly add ":do_deploy" when in fact, ":do_populate_sysroot" should 
be
appended.

Putting the ":do_deploy" in xilinx-bootbin.bb sure means less characters 
overall, but
that doesn't mean it's objectively "better". ;)

I recommend leaving my patch as-is, i.e.  as I it was "signed-off".-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

Re: [meta-xilinx] Yoctoproject vs Github

[richard-bailey]

Hi Luca,

Thanks for the information. It was very helpful.

Regards,

Richard.

-Original Message-
From: Luca Ceresoli [mailto:l...@lucaceresoli.net]
Sent: 16 May 2018 15:19
To: Richard Bailey; meta-xilinx@yoctoproject.org
Subject: Re: [meta-xilinx] Yoctoproject vs Github

Hi Richard,

On 16/05/2018 14:38, richard-bai...@sti-limited.com wrote:
> Hi,
>
>
>
> I was just wondering how the yoctoproject.org meta-xilinx relates to the
> github hosted version.
>
> Is it a mirror or are there some changes? Is it updated immediately? Are
> there any advantages to using either?

The repo on yoctoproject.org contains development done by the open
source community and is developed as close as possible to the yocto
standards.

The github repo is a fork by Xilinx. The branches on that repo start
from a commit from yoctoproject.org and add some features. But in the
practice it will work in a different workflow involving Petalinux, xsct
and other Xilinx proprietary tools. The branches there are not supposed
to be merged into yoctoproject.org, they will keep on diverging.

Thus you should first choose your workflow:

 * The Community workflow: use yoctoproject.org, standard open source
   tools, boot using U-Boot SPL
 * The Xilinx workflow: use the github xilinx fork, follow the Xilinx
   procedures, boot with Xilinx FSBL etc.

A few more details on the two approaches in this talk:
https://fosdem.org/2018/schedule/event/arm64_and_fpga/

Hope that helps,
--
Luca

The information contained in this communication, and any attachments, may be 
confidential and/or privileged. It is intended only for the use of the named 
recipient.

If you are not the intended recipient please contact us.
Tel: +44 (0)1256 768070
Fax: +44 (0)1256 760718
Email: postmas...@sti-limited.com.

In such an event you should not access any attachments, nor should you disclose 
the contents of this communication or any attachments to any other person, nor 
copy, print, store or use the same in any manner whatsoever.

Thank you for your co-operation.

-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx