Re: [meta-xilinx] [PATCH 9/9] zynqmp-pmu: Remove class that uses a multilib hack to build standalone components

: Thursday, December 13, 2018 2:31:30 PM To: Martin Siegumfeldt Cc: Alejandro Enedino Hernandez Samaniego; meta-xilinx@yoctoproject.org Subject: Re: [meta-xilinx] [PATCH 9/9] zynqmp-pmu: Remove class that uses a multilib hack to build standalone components On Dec 12, 2018, at 3:21 AM, Martin Siegumfeldt

Re: [meta-xilinx] [PATCH 9/9] zynqmp-pmu: Remove class that uses a multilib hack to build standalone components

From: meta-xilinx-boun...@yoctoproject.org on behalf of Jean-Francois Dagenais Sent: Saturday, December 8, 2018 4:11 AM To: Alejandro Enedino Hernandez Samaniego Cc: meta-xilinx@yoctoproject.org Subject: Re: [meta-xilinx] [PATCH 9/9] zynqmp-pmu:

Re: [meta-xilinx] [[meta-xilinx-bsp][PATCH v2]] device-tree.bb: add missing include path

Ping? Manju? From: Martin Siegumfeldt Sent: Thursday, June 21, 2018 2:36 PM To: meta-xilinx@yoctoproject.org Cc: Martin Siegumfeldt Subject: [[meta-xilinx][meta-xilinx-bsp][PATCH v2]] device-tree.bb: add missing include path This patch adds a missing

[meta-xilinx] [[meta-xilinx-bsp][PATCH v2]] device-tree.bb: add missing include path

This patch adds a missing include path for generic kernel DTC includes. Signed-off-by: Martin Siegumfeldt Reviewed-by: Nathan Rossi --- meta-xilinx-bsp/recipes-bsp/device-tree/device-tree.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta-xilinx-bsp/recipes-bsp/device-tree/device

Re: [meta-xilinx] [PATCH] device-tree.bb: add missing include path

On 20 June 2018 at 21:14, Martin Siegumfeldt wrote: > This patch add a missing include path for dt-bindings header-files > (i.e. gpio, pinctrl etc.) > > Signed-off-by: Martin Siegumfeldt > --- >  meta-xilinx-bsp/recipes-bsp/device-tree/device-tree.bb | 1 + >  1 file

Re: [meta-xilinx] Generation of psu_init files

/zynqmp-zcu102-rev1.0/psu_init_gpl.h' and overwriting the associated existing 'psu_init_gpl.c' yields the SPL generation to succeed. Thanks, Martin From: Luca Ceresoli Sent: Thursday, June 14, 2018 11:16:21 PM To: Martin Siegumfeldt; meta-xilinx@yoctoproject.org

Re: [meta-xilinx] Generation of psu_init files

as exported by any current Vivado version. Is this new structure exported by an upcoming Vivado release, or how do you expect us to handle this? Thanks, Martin From: Luca Ceresoli Sent: Thursday, June 7, 2018 6:10:38 PM To: Martin Siegumfeldt; meta-xilinx

Re: [meta-xilinx] Generation of psu_init files

Hi Manju, any clues here? The newly pushed 2018.2 release of https://github.com/Xilinx/hdf-examples still seems to describe the init code in the "old format"? Br, Martin From: meta-xilinx-boun...@yoctoproject.org on behalf of Martin Siegumfeldt Se

[meta-xilinx] Generation of psu_init files

Hi, Since  https://github.com/Xilinx/u-boot-xlnx/commit/a38ad86e46b940dd53cb328ed19761dbb084d6e5#diff-ff33c47fd7e88097b7ebeba1d14fe072 / https://github.com/Xilinx/u-boot-xlnx/commit/9fd6056f5329d2d1178ef675f53641461c2e183d#diff-7f268ae597d9cb8d64ad0d46931fdb1b  the psu_init files have changed

Re: [meta-xilinx] Provider of pmu-firmware [rel-v2018.1]

Hi Nathan, From: Nathan Rossi <nat...@nathanrossi.com> Sent: Wednesday, May 16, 2018 13:20 To: Martin Siegumfeldt Cc: meta-xilinx@yoctoproject.org Subject: Re: [meta-xilinx] Provider of pmu-firmware [rel-v2018.1] On 16 May 2018 at 18:24, Martin Siegumfe

Re: [meta-xilinx] Provider of pmu-firmware [rel-v2018.1]

Hmm, thanks for your input Nathan... Br, Martin From: Nathan Rossi <nat...@nathanrossi.com> Sent: Wednesday, May 16, 2018 3:01:02 PM To: Martin Siegumfeldt Cc: meta-xilinx@yoctoproject.org Subject: Re: [meta-xilinx] Provider of pmu-firmware [rel-v2018.1]

Re: [meta-xilinx] Provider of pmu-firmware [rel-v2018.1]

r, Martin From: Nathan Rossi <nat...@nathanrossi.com> Sent: Wednesday, May 16, 2018 2:21:03 PM To: Martin Siegumfeldt Cc: meta-xilinx@yoctoproject.org Subject: Re: [meta-xilinx] Provider of pmu-firmware [rel-v2018.1] On 16 May 2018 at 22:01, Martin Siegumfeldt <m...@gomspace.com&g

Re: [meta-xilinx] Provider of pmu-firmware [rel-v2018.1]

6:19:43 PM To: Martin Siegumfeldt Cc: meta-xilinx@yoctoproject.org Subject: Re: [meta-xilinx] Provider of pmu-firmware [rel-v2018.1] On 15 May 2018 at 20:54, Martin Siegumfeldt <m...@gomspace.com> wrote: > Hi, > > Based on > https://github.com/Xilinx/meta-xilinx-tools/commit/a516c3a4a8b

[meta-xilinx] Provider of pmu-firmware [rel-v2018.1]

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

Re: [meta-xilinx] qemuboot.conf

:19 PM To: Martin Siegumfeldt Cc: Alistair Francis; meta-xilinx@yoctoproject.org Subject: Re: [meta-xilinx] qemuboot.conf On 29 January 2018 at 05:51, Martin Siegumfeldt <m...@gomspace.com> wrote: > > > > > From: Nathan Rossi <nat...@nathanrossi.c

[meta-xilinx] Ethernet functionality of QEMU (zcu102-zynqmp)

Hi, Are there any limitations regarding the ethernet capabilities of the QEMU instance of the zcu102-zynqmp machine? runqemu seems to allocate IP address to the tap interface, no obvious errors are present from the kernel log, however no IP address is assigned to eth0. I have manually tried to

Re: [meta-xilinx] qemuboot.conf

From: Nathan Rossi <nat...@nathanrossi.com> Sent: Sunday, January 28, 2018 13:44 To: Alistair Francis Cc: Martin Siegumfeldt; meta-xilinx@yoctoproject.org Subject: Re: [meta-xilinx] qemuboot.conf On 24 January 2018 at 09:04, Alistair Francis &l

[meta-xilinx] qemuboot.conf

Hi, We are rendering a custom piece of HW based on Ultrascale+, and have the Xilinx QEMU successfully running. An extensible SDK (eSDK) is delivered to the  application developers and to close the loop we would like to be capable of delivering also the QEMU instance. The machine image- and

Re: [meta-xilinx] Device tree generation failure (2017.3)

nju...@xilinx.com> Sent: Monday, December 11, 2017 6:18:04 PM To: Martin Siegumfeldt; meta-xilinx@yoctoproject.org Subject: RE: Device tree generation failure (2017.3) Hi Martin, Are you using rel-v2017.3 branches from Xilinx? If not, I think the issue is having KMACHINE instead of SOC_FAMILY.

Re: [meta-xilinx] Device tree generation failure (2017.3)

Ok, thx From: Manjukumar Harthikote Matha <manju...@xilinx.com> Sent: Monday, December 11, 2017 8:25:43 PM To: Martin Siegumfeldt; meta-xilinx@yoctoproject.org Subject: RE: Device tree generation failure (2017.3) Hi Martin, We will send out the p

Re: [meta-xilinx] Device tree generation failure (2017.3)

From: meta-xilinx-boun...@yoctoproject.org <meta-xilinx-boun...@yoctoproject.org> on behalf of Martin Siegumfeldt <m...@gomspace.com> Sent: Friday, December 8, 2017 22:11 To: Manjukumar Harthikote Matha; meta-xilinx@yoctoproject.org Subject: Re: [meta-xilinx]

Re: [meta-xilinx] Device tree generation failure (2017.3)

working on this particular baseline and an "upstream" fix is thus highly appreciated. Thanks, Martin From: Manjukumar Harthikote Matha <manju...@xilinx.com> Sent: Friday, December 8, 2017 8:40:02 PM To: Martin Siegumfeldt; meta-xilinx@yoctoproject

Re: [meta-xilinx] Device tree generation failure (2017.3)

Ok sounds good - looking forwards to it... Cheers, Martin From: Manjukumar Harthikote Matha <manju...@xilinx.com> Sent: Friday, December 8, 2017 10:02:18 PM To: Martin Siegumfeldt; meta-xilinx@yoctoproject.org Subject: RE: Device tree generation failure (

[meta-xilinx] Device tree generation failure (2017.3)

Hi, I am struggling with device tree generation (using meta-xilinx-tools) of a custom machine pretty much replicating zcu102, which in turn generates device tree successfully. local.conf defines version 2017.3 and a local HDF file: XILINX_VER_MAIN = "2017.3" EXTERNAL_TOOLCHAIN_microblaze =

[meta-xilinx] QSPI Issues related to Linux 4.9

Hi, I recently updated the Linux kernel for a custom board based on z7k from Xilinx version 4.6 to 4.9, and spend a few days debugging issues related to the QSPI flash (n25q512a13). By coincidence I stumbled upon 

Re: [meta-xilinx] Build error with latest pyro (Could not inherit file classes/image_types_uboot.bbclass)

From: meta-xilinx-boun...@yoctoproject.org on behalf of Peter Smith Sent: Tuesday, November 14, 2017 10:04:30 AM To: meta-xilinx@yoctoproject.org Subject: [meta-xilinx] Build error with latest pyro (Could not inherit file

Re: [meta-xilinx] Rocko Release of meta-xilinx

From: Nathan Rossi <nat...@nathanrossi.com> Sent: Monday, November 6, 2017 17:36 To: Martin Siegumfeldt Cc: meta-xilinx@yoctoproject.org Subject: Re: [meta-xilinx] Rocko Release of meta-xilinx   On 6 November 2017 at 22:15, Martin Siegumfeldt <m...@gomspace.com> wrote: > Hi, >

[meta-xilinx] Rocko Release of meta-xilinx

Hi, Is there a time schedule of when the Rocko release of meta-xilinx will be available? Thanks, Martin -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx

Re: [meta-xilinx] How to boot the ZynqMP?

nju...@xilinx.com> Sent: Friday, September 1, 2017 04:40 To: Manjukumar Harthikote Matha; Mike Looijmans; Brian Hutchinson; Martin Siegumfeldt Cc: meta-xilinx@yoctoproject.org Subject: RE: [meta-xilinx] How to boot the ZynqMP?   Hi All, Sorry for writing on top. I wanted to summarize the flow

[meta-xilinx] meta-xilinx-tools fails on "device-tree-generation" script

Hi, I am seeing the same issue, despite xvfb being installed. I am able run xsdb/xsdk outside the build context. martin@martin-Precision-5510:~/work/zcu102_os/build$ bitbake core-image-minimal Parsing recipes: 100%