Ditto on all Martin said. We also wish to move away from bloated, slow and
buggy meta-xilinx-tools.
Sent from my iPhone
> On May 15, 2018, at 10:55, Peter Smith wrote:
>
> I shall second this
--
___
meta-xilinx mailing list
meta-xilinx@yoctoproject
On 15 May 2018 at 20:54, Martin Siegumfeldt wrote:
> Hi,
>
> Based on
> https://github.com/Xilinx/meta-xilinx-tools/commit/a516c3a4a8b29e07233b5f2ecf91a2a3e63a1ff7
> I would like to switch from building the pmu-firmware using the XSDK (i.e.
> through meta-xilinx-tools) to the generated toolchai
Hi Martin,
> -Original Message-
> From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx-
> boun...@yoctoproject.org] On Behalf Of Martin Lund
> Sent: Tuesday, May 15, 2018 7:31 AM
> To: meta-xilinx@yoctoproject.org
> Subject: [meta-xilinx] Xilinx, why are you breaking the meta-xil
Hi,
Based on
https://github.com/Xilinx/meta-xilinx-tools/commit/a516c3a4a8b29e07233b5f2ecf91a2a3e63a1ff7
I would like to switch from building the pmu-firmware using the XSDK (i.e.
through meta-xilinx-tools) to the generated toolchain (i.e. through
meta-xilinx). However the latter layer seems n
I shall second this as I will very soon face the same issue. I help to
maintain a custom distribution (using a lot of the functionality provided
by the by Yocto project). Currently I am using Yocto pyro and the
meat-xilinx and I am able to take advantage of the independence of this
layer. We will n
Hi Xilinx and friends,
What is going on with the meta-xilinx-bsp layer in the v2018.1 release?
We are trying to put together a system built on top of the meta-xilinx-bsp
layer and we have done so successfully up until the v2017.4 release with a few
helpful patches from this excellent communi
Hi,
I've been debugging some more and I can confirm that it jumps successfully to
the ATF but the ATF crashes before it writes anything to the uart, such as its
usual version notice information.
Debugging the ATF I've found that it crashes trying to retrieve the chip id via
the pm_get_chipid