date:20171211

[meta-xilinx] [PATCH v3] meta-xilinx: Restructuring meta-xilinx to support multiple layers

2017-12-11 Thread Manjukumar Matha

As discussed previously on mailing list, we are proceeding with layer
restructuring. For rocko release we will have the following layers

meta-xilinx
->meta-xilinx-bsp (current meta-xilinx)
->meta-xilinx-contrib

In the subsequent releases we will add other layers from Xilinx
meta-xilinx
->meta-xilinx-bsp (current meta-xilinx)
->meta-petalinux
->meta-xilinx-tools
->meta-xilinx-contrib

This will provide one clone to get all the required meta layers from
Xilinx for a complete solution, and the users can blacklist any layer
which they don't want to use using bblayer.conf.
This will enables us to help our vendors/partners to add their reference
designs, board definitions etc.

Changes v2:
 * Move reference design zybo-linux-bd.bb to meta-xilinx-contrib
 * Move kernel patches realted to zybo-linux-bd-zynq7 board to
   meta-xilinx-contrib

Changes v3:
 * Update README

Signed-off-by: Manjukumar Matha 
---
 README.md  | 84 +
 meta-xilinx-bsp/COPYING.MIT| 17 +
 .../README.booting.md  |  0
 .../README.building.md |  0
 meta-xilinx-bsp/README.md  | 86 ++
 README.qemu.md => meta-xilinx-bsp/README.qemu.md   |  0
 .../classes}/image-types-xilinx-qemu.bbclass   |  0
 .../classes}/qemuboot-xilinx.bbclass   |  0
 .../classes}/xilinx-fetch-restricted.bbclass   |  0
 .../classes}/xilinx-platform-init.bbclass  |  0
 .../classes}/zynqmp-pmu.bbclass|  0
 {conf => meta-xilinx-bsp/conf}/layer.conf  |  0
 .../conf}/machine/include/machine-xilinx-board.inc |  0
 .../machine/include/machine-xilinx-default.inc |  0
 .../conf}/machine/include/machine-xilinx-qemu.inc  |  0
 .../machine/include/microblaze/arch-microblaze.inc |  0
 .../include/microblaze/feature-microblaze-math.inc |  0
 .../microblaze/feature-microblaze-versions.inc |  0
 .../conf}/machine/include/tune-microblaze.inc  |  0
 .../conf}/machine/include/tune-zynq.inc|  0
 .../conf}/machine/include/tune-zynqmp.inc  |  0
 .../conf}/machine/include/zynqmp-pmu-config.inc|  0
 .../conf}/machine/kc705-microblazeel.conf  |  0
 .../conf}/machine/microzed-zynq7.conf  |  0
 .../conf}/machine/ml605-qemu-microblazeel.conf |  0
 .../conf}/machine/picozed-zynq7.conf   |  0
 .../conf}/machine/qemu-zynq7.conf  |  0
 .../machine/s3adsp1800-qemu-microblazeeb.conf  |  0
 .../conf}/machine/zc702-zynq7.conf |  0
 .../conf}/machine/zc706-zynq7.conf |  0
 .../conf}/machine/zcu102-zynqmp.conf   |  0
 .../conf}/machine/zedboard-zynq7.conf  |  0
 .../conf}/machine/zybo-linux-bd-zynq7.conf |  0
 .../conf}/machine/zybo-zynq7.conf  |  0
 .../arm-trusted-firmware/arm-trusted-firmware.inc  |  0
 .../arm-trusted-firmware_2017.3.bb |  0
 .../recipes-bsp}/device-tree/device-tree.bb|  0
 .../recipes-bsp}/device-tree/device-tree.bbappend  |  0
 .../kc705-microblazeel/kc705-microblazeel.dts  |  0
 .../device-tree/files/kc705-microblazeel/pl.dtsi   |  0
 .../files/kc705-microblazeel/system-conf.dtsi  |  0
 .../device-tree/files/microzed-zynq7.dts   |  0
 .../device-tree/files/picozed-zynq7.dts|  0
 .../recipes-bsp}/device-tree/files/qemu-zynq7.dts  |  0
 .../device-tree/files/zybo-linux-bd-zynq7/pcw.dtsi |  0
 .../device-tree/files/zybo-linux-bd-zynq7/pl.dtsi  |  0
 .../zybo-linux-bd-zynq7/zybo-linux-bd-zynq7.dts|  0
 .../device-tree/files/zynq-7000-qspi-dummy.dtsi|  0
 .../recipes-bsp}/platform-init/platform-init.bb|  0
 .../platform-init/picozed-zynq7/ps7_init_gpl.c |  0
 .../platform-init/picozed-zynq7/ps7_init_gpl.h |  0
 .../pmu-firmware/pmu-firmware_2017.3.bb|  0
 .../recipes-bsp}/pmu-firmware/pmu-rom_2017.3.bb|  0
 .../reference-design/kc705-bitstream_2017.3.bb |  0
 .../recipes-bsp}/u-boot/u-boot-spl-zynq-init.inc   |  0
 .../recipes-bsp}/u-boot/u-boot-xlnx-dev.bb |  0
 .../recipes-bsp}/u-boot/u-boot-xlnx.inc|  0
 ...mp-Setup-partid-for-QEMU-to-match-silicon.patch |  0
 .../recipes-bsp}/u-boot/u-boot-xlnx_2017.3.bb  |  0
 .../recipes-bsp}/u-boot/u-boot-zynq-uenv.bb|  0
 .../recipes-bsp}/u-boot/u-boot_%.bbappend  |  0
 .../recipes-core}/newlib/libgloss_2.5.0.bb |  0
 .../recipes-core}/newlib/newlib.inc|  0
 .../recipes-core}/newlib/newlib_2.5.0.bb   |  0
 .../qemu/files/qemu-system-aarch64-multiarch   |  0
 .../recipes-devtools}/qemu/qemu-devicetrees.inc|  0
 .../qemu/qemu-devicetrees_2017.3.bb|  0
 .../qemu/qemu-xilinx-helper-native_1.0.bb  |  0
 .../qemu-xilinx-multiarch-helper-native_1.0.bb |  0

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

2017-12-11 Thread Martin Siegumfeldt

Ok, thx


From: Manjukumar Harthikote Matha 
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 patches for meta-xilinx-tools to use SOC_FAMLIY instead of 
KMACHINE.



Thanks,

Manju



From: Martin Siegumfeldt [mailto:m...@gomspace.com]
Sent: Monday, December 11, 2017 11:18 AM
To: Manjukumar Harthikote Matha ; 
meta-xilinx@yoctoproject.org
Subject: Re: Device tree generation failure (2017.3)



I am using 'master' of meta-xilinx and meta-xilinx-tools but 'rocko' of poky 
and meta-openembedded combined with XSDK 2017.3. It is my intention to switch 
to all 'rocko' when Xilinx releases 'rocko'.



Thanks,

Martin



From: Manjukumar Harthikote Matha 
>
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.
https://github.com/Xilinx/meta-xilinx-tools/blob/master/classes/xilinx-bootbin.bbclass#L77

Change to SOC_FAMILY instead of KMACHINE.

Thanks,
Manju

> -Original Message-
> From: Martin Siegumfeldt [mailto:m...@gomspace.com]
> Sent: Monday, December 11, 2017 1:50 AM
> To: Manjukumar Harthikote Matha 
> >; meta-
> xil...@yoctoproject.org
> Subject: Re: Device tree generation failure (2017.3)
>
> Hmm, next obstacle seems to be the boot.bin generation:
>
> ERROR: core-image-minimal-1.0-r0 do_xilinx_bootbin: Function failed:
> do_xilinx_bootbin (log file is located at
> /home/martin/work/tmp/build/tmp/work/zcu102_zynqmp-poky-linux/core-
> image-minimal/1.0-r0/temp/log.do_xilinx_bootbin.14057)
> ERROR: Logfile of failure stored in:
> /home/martin/work/tmp/build/tmp/work/zcu102_zynqmp-poky-linux/core-
> image-minimal/1.0-r0/temp/log.do_xilinx_bootbin.14057
> Log data follows:
> | DEBUG: Executing shell function do_xilinx_bootbin
> | ERROR: syntax error
> | ... bif -arch -w -o BOOT.bin
> |   ^^
> |
> | [ERROR]  : Command line parsing failed with code 1
> | WARNING: exit code 1 from a shell command.
> | ERROR: Function failed: do_xilinx_bootbin (log file is located at
> /home/martin/work/tmp/build/tmp/work/zcu102_zynqmp-poky-linux/core-
> image-minimal/1.0-r0/temp/log.do_xilinx_bootbin.14057)
>
>
> the logfile contains no more information.
>
>
>
>
> It looks like bootgen is complaining about missing the 'arch' parameter. 
> Forcing this
> into 'zynqmp' rather than '${KMACHINE}' from the recipe enables BOOT.bin to be
> generated.
>
>
>
>
> AFAICS, it occurs also for the zcu102 machine - any ideas?
>
>
>
>
> Cheers,
>
> Martin
>
>
>
> 
>
> From: 
> meta-xilinx-boun...@yoctoproject.org
>   boun...@yoctoproject.org> on behalf of 
> Martin Siegumfeldt
> >
> Sent: Friday, December 8, 2017 22:11
> To: Manjukumar Harthikote Matha; 
> meta-xilinx@yoctoproject.org
> Subject: Re: [meta-xilinx] Device tree generation failure (2017.3)
>
>This sender failed our fraud detection checks and may not be who they
> appear to be. Learn about spoofing 
> Feedback 
>
> Ok sounds good - looking forwards to it...
>
>
>
>
> Cheers,
>
> Martin
>
> 
>
> From: Manjukumar Harthikote Matha 
> >
> Sent: Friday, December 8, 2017 10:02:18 PM
> To: Martin Siegumfeldt; 
> meta-xilinx@yoctoproject.org
> Subject: RE: Device tree generation failure (2017.3)
>
>
> Hi Martin,
>
>
>
> Yes we are looking into it actively, including possible changes to xsct tool 
> itself.
>
>
>
> One patch which includes /usr/bin also works, we are more leaning towards this
> patch.
>
> https://lists.yoctoproject.org/pipermail/meta-xilinx/2017-July/003027.html
> 
>
>
>
> I am thinking to limit the path append to places where xsct is being invoked 
> instead
> of it being append by the layer completely.
>
>
>
> Please let me know your feedback.
>
>
>
> Thanks,
>
> Manju
>
>
>
>
>
> From: Martin Siegumfeldt [mailto:m...@gomspace.com]
> Sent: Friday, December 08, 2017 12:57 PM
> To: Manjukumar Harthikote Matha 
> >; meta-
> xil...@yoctoproject.org
> Subject: Re: Device tree generation failure

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

2017-12-11 Thread Manjukumar Harthikote Matha

Hi Martin,

We will send out the patches for meta-xilinx-tools to use SOC_FAMLIY instead of 
KMACHINE.

Thanks,
Manju

From: Martin Siegumfeldt [mailto:m...@gomspace.com]
Sent: Monday, December 11, 2017 11:18 AM
To: Manjukumar Harthikote Matha ; 
meta-xilinx@yoctoproject.org
Subject: Re: Device tree generation failure (2017.3)


I am using 'master' of meta-xilinx and meta-xilinx-tools but 'rocko' of poky 
and meta-openembedded combined with XSDK 2017.3. It is my intention to switch 
to all 'rocko' when Xilinx releases 'rocko'.



Thanks,

Martin


From: Manjukumar Harthikote Matha 
>
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.
https://github.com/Xilinx/meta-xilinx-tools/blob/master/classes/xilinx-bootbin.bbclass#L77

Change to SOC_FAMILY instead of KMACHINE.

Thanks,
Manju

> -Original Message-
> From: Martin Siegumfeldt [mailto:m...@gomspace.com]
> Sent: Monday, December 11, 2017 1:50 AM
> To: Manjukumar Harthikote Matha 
> >; meta-
> xil...@yoctoproject.org
> Subject: Re: Device tree generation failure (2017.3)
>
> Hmm, next obstacle seems to be the boot.bin generation:
>
> ERROR: core-image-minimal-1.0-r0 do_xilinx_bootbin: Function failed:
> do_xilinx_bootbin (log file is located at
> /home/martin/work/tmp/build/tmp/work/zcu102_zynqmp-poky-linux/core-
> image-minimal/1.0-r0/temp/log.do_xilinx_bootbin.14057)
> ERROR: Logfile of failure stored in:
> /home/martin/work/tmp/build/tmp/work/zcu102_zynqmp-poky-linux/core-
> image-minimal/1.0-r0/temp/log.do_xilinx_bootbin.14057
> Log data follows:
> | DEBUG: Executing shell function do_xilinx_bootbin
> | ERROR: syntax error
> | ... bif -arch -w -o BOOT.bin
> |   ^^
> |
> | [ERROR]  : Command line parsing failed with code 1
> | WARNING: exit code 1 from a shell command.
> | ERROR: Function failed: do_xilinx_bootbin (log file is located at
> /home/martin/work/tmp/build/tmp/work/zcu102_zynqmp-poky-linux/core-
> image-minimal/1.0-r0/temp/log.do_xilinx_bootbin.14057)
>
>
> the logfile contains no more information.
>
>
>
>
> It looks like bootgen is complaining about missing the 'arch' parameter. 
> Forcing this
> into 'zynqmp' rather than '${KMACHINE}' from the recipe enables BOOT.bin to be
> generated.
>
>
>
>
> AFAICS, it occurs also for the zcu102 machine - any ideas?
>
>
>
>
> Cheers,
>
> Martin
>
>
>
> 
>
> From: 
> meta-xilinx-boun...@yoctoproject.org
>   boun...@yoctoproject.org> on behalf of 
> Martin Siegumfeldt
> >
> Sent: Friday, December 8, 2017 22:11
> To: Manjukumar Harthikote Matha; 
> meta-xilinx@yoctoproject.org
> Subject: Re: [meta-xilinx] Device tree generation failure (2017.3)
>
>This sender failed our fraud detection checks and may not be who they
> appear to be. Learn about spoofing 
> Feedback 
>
> Ok sounds good - looking forwards to it...
>
>
>
>
> Cheers,
>
> Martin
>
> 
>
> From: Manjukumar Harthikote Matha 
> >
> Sent: Friday, December 8, 2017 10:02:18 PM
> To: Martin Siegumfeldt; 
> meta-xilinx@yoctoproject.org
> Subject: RE: Device tree generation failure (2017.3)
>
>
> Hi Martin,
>
>
>
> Yes we are looking into it actively, including possible changes to xsct tool 
> itself.
>
>
>
> One patch which includes /usr/bin also works, we are more leaning towards this
> patch.
>
> https://lists.yoctoproject.org/pipermail/meta-xilinx/2017-July/003027.html
> 
>
>
>
> I am thinking to limit the path append to places where xsct is being invoked 
> instead
> of it being append by the layer completely.
>
>
>
> Please let me know your feedback.
>
>
>
> Thanks,
>
> Manju
>
>
>
>
>
> From: Martin Siegumfeldt [mailto:m...@gomspace.com]
> Sent: Friday, December 08, 2017 12:57 PM
> To: Manjukumar Harthikote Matha 
> >; meta-
> xil...@yoctoproject.org
> Subject: Re: Device tree generation failure (2017.3)
>
>
>
> Hi Manju,
>
>
>
> It is (almost) empty:
>
>
>
> martin@martin-Precision-5510:~/work/rocko/build$ cat
> /home/martin/work/rocko/build/tmp-glibc/work/nanomind_zcu102-oe-
> linux/device-tree-generation/xilinx+gitAUTOINC+5b21302249-r0/device-tree-
>

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

2017-12-11 Thread Manjukumar Harthikote Matha

Hi Martin,

Are you using rel-v2017.3 branches from Xilinx? 

If not, I think the issue is having KMACHINE instead of SOC_FAMILY. 
https://github.com/Xilinx/meta-xilinx-tools/blob/master/classes/xilinx-bootbin.bbclass#L77

Change to SOC_FAMILY instead of KMACHINE.

Thanks,
Manju

> -Original Message-
> From: Martin Siegumfeldt [mailto:m...@gomspace.com]
> Sent: Monday, December 11, 2017 1:50 AM
> To: Manjukumar Harthikote Matha ; meta-
> xil...@yoctoproject.org
> Subject: Re: Device tree generation failure (2017.3)
> 
> Hmm, next obstacle seems to be the boot.bin generation:
> 
> ERROR: core-image-minimal-1.0-r0 do_xilinx_bootbin: Function failed:
> do_xilinx_bootbin (log file is located at
> /home/martin/work/tmp/build/tmp/work/zcu102_zynqmp-poky-linux/core-
> image-minimal/1.0-r0/temp/log.do_xilinx_bootbin.14057)
> ERROR: Logfile of failure stored in:
> /home/martin/work/tmp/build/tmp/work/zcu102_zynqmp-poky-linux/core-
> image-minimal/1.0-r0/temp/log.do_xilinx_bootbin.14057
> Log data follows:
> | DEBUG: Executing shell function do_xilinx_bootbin
> | ERROR: syntax error
> | ... bif -arch -w -o BOOT.bin
> |   ^^
> |
> | [ERROR]  : Command line parsing failed with code 1
> | WARNING: exit code 1 from a shell command.
> | ERROR: Function failed: do_xilinx_bootbin (log file is located at
> /home/martin/work/tmp/build/tmp/work/zcu102_zynqmp-poky-linux/core-
> image-minimal/1.0-r0/temp/log.do_xilinx_bootbin.14057)
> 
> 
> the logfile contains no more information.
> 
> 
> 
> 
> It looks like bootgen is complaining about missing the 'arch' parameter. 
> Forcing this
> into 'zynqmp' rather than '${KMACHINE}' from the recipe enables BOOT.bin to be
> generated.
> 
> 
> 
> 
> AFAICS, it occurs also for the zcu102 machine - any ideas?
> 
> 
> 
> 
> Cheers,
> 
> Martin
> 
> 
> 
> 
> 
> From: meta-xilinx-boun...@yoctoproject.org  boun...@yoctoproject.org> on behalf of Martin Siegumfeldt
> 
> Sent: Friday, December 8, 2017 22:11
> To: Manjukumar Harthikote Matha; meta-xilinx@yoctoproject.org
> Subject: Re: [meta-xilinx] Device tree generation failure (2017.3)
> 
>   This sender failed our fraud detection checks and may not be who they
> appear to be. Learn about spoofing 
> Feedback 
> 
> Ok sounds good - looking forwards to it...
> 
> 
> 
> 
> Cheers,
> 
> Martin
> 
> 
> 
> From: Manjukumar Harthikote Matha 
> Sent: Friday, December 8, 2017 10:02:18 PM
> To: Martin Siegumfeldt; meta-xilinx@yoctoproject.org
> Subject: RE: Device tree generation failure (2017.3)
> 
> 
> Hi Martin,
> 
> 
> 
> Yes we are looking into it actively, including possible changes to xsct tool 
> itself.
> 
> 
> 
> One patch which includes /usr/bin also works, we are more leaning towards this
> patch.
> 
> https://lists.yoctoproject.org/pipermail/meta-xilinx/2017-July/003027.html
> 
> 
> 
> 
> I am thinking to limit the path append to places where xsct is being invoked 
> instead
> of it being append by the layer completely.
> 
> 
> 
> Please let me know your feedback.
> 
> 
> 
> Thanks,
> 
> Manju
> 
> 
> 
> 
> 
> From: Martin Siegumfeldt [mailto:m...@gomspace.com]
> Sent: Friday, December 08, 2017 12:57 PM
> To: Manjukumar Harthikote Matha ; meta-
> xil...@yoctoproject.org
> Subject: Re: Device tree generation failure (2017.3)
> 
> 
> 
> Hi Manju,
> 
> 
> 
> It is (almost) empty:
> 
> 
> 
> martin@martin-Precision-5510:~/work/rocko/build$ cat
> /home/martin/work/rocko/build/tmp-glibc/work/nanomind_zcu102-oe-
> linux/device-tree-generation/xilinx+gitAUTOINC+5b21302249-r0/device-tree-
> generation.yaml
> {}
> 
> 
> 
> Setting 'YAML_MAIN_MEMORY_CONFIG' seems to enable the DTG to succeed -
> thanks.
> 
> 
> 
> Btw., are there any intentions of a proper fix for the missing DISPLAY 
> variable from
> https://lists.yoctoproject.org/pipermail/meta-xilinx/2017-September/003162.html
>  September/003162.html>  (5) ? Your proposal worked for me, however soon there
> will be a larger team within my organization working on this particular 
> baseline and
> an "upstream" fix is thus highly appreciated.
> 
> 
> 
> Thanks,
> 
> Martin
> 
> 
> 
> From: Manjukumar Harthikote Matha   >
> Sent: Friday, December 8, 2017 8:40:02 PM
> To: Martin Siegumfeldt; meta-xilinx@yoctoproject.org  xil...@yoctoproject.org>
> Subject: RE: Device tree generation failure (2017.3)
> 
> 
> 
> Hi Martin,
> 
> 
> 
> Can you check if this is empty? /home/martin/work/rocko/build/tmp-
> glibc/work/nanomind_zcu102-oe-linux/device-tree-
> generation/xilinx+gitAUTOINC+5b21302249-r0/device-tree-generation.yaml
> 
> 
> 
> We have

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

2017-12-11 Thread Martin Siegumfeldt

Hmm, next obstacle seems to be the boot.bin generation:

ERROR: core-image-minimal-1.0-r0 do_xilinx_bootbin: Function failed: 
do_xilinx_bootbin (log file is located at 
/home/martin/work/tmp/build/tmp/work/zcu102_zynqmp-poky-linux/core-image-minimal/1.0-r0/temp/log.do_xilinx_bootbin.14057)
ERROR: Logfile of failure stored in: 
/home/martin/work/tmp/build/tmp/work/zcu102_zynqmp-poky-linux/core-image-minimal/1.0-r0/temp/log.do_xilinx_bootbin.14057
Log data follows:
| DEBUG: Executing shell function do_xilinx_bootbin
| ERROR: syntax error
| ... bif -arch -w -o BOOT.bin
|   ^^
|
| [ERROR]  : Command line parsing failed with code 1
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_xilinx_bootbin (log file is located at 
/home/martin/work/tmp/build/tmp/work/zcu102_zynqmp-poky-linux/core-image-minimal/1.0-r0/temp/log.do_xilinx_bootbin.14057)


the logfile contains no more information.


It looks like bootgen is complaining about missing the 'arch' parameter. 
Forcing this into 'zynqmp' rather than '${KMACHINE}' from the recipe enables 
BOOT.bin to be generated.


AFAICS, it occurs also for the zcu102 machine - any ideas?


Cheers,

Martin



From: meta-xilinx-boun...@yoctoproject.org 
 on behalf of Martin Siegumfeldt 

Sent: Friday, December 8, 2017 22:11
To: Manjukumar Harthikote Matha; meta-xilinx@yoctoproject.org
Subject: Re: [meta-xilinx] Device tree generation failure (2017.3)


This sender failed our fraud detection checks and may not be who they appear to 
be. Learn about spoofing
Feedback

Ok sounds good - looking forwards to it...


Cheers,

Martin


From: Manjukumar Harthikote Matha 
Sent: Friday, December 8, 2017 10:02:18 PM
To: Martin Siegumfeldt; meta-xilinx@yoctoproject.org
Subject: RE: Device tree generation failure (2017.3)


Hi Martin,



Yes we are looking into it actively, including possible changes to xsct tool 
itself.



One patch which includes /usr/bin also works, we are more leaning towards this 
patch.

https://lists.yoctoproject.org/pipermail/meta-xilinx/2017-July/003027.html



I am thinking to limit the path append to places where xsct is being invoked 
instead of it being append by the layer completely.



Please let me know your feedback.



Thanks,

Manju





From: Martin Siegumfeldt [mailto:m...@gomspace.com]
Sent: Friday, December 08, 2017 12:57 PM
To: Manjukumar Harthikote Matha ; 
meta-xilinx@yoctoproject.org
Subject: Re: Device tree generation failure (2017.3)



Hi Manju,



It is (almost) empty:



martin@martin-Precision-5510:~/work/rocko/build$ cat 
/home/martin/work/rocko/build/tmp-glibc/work/nanomind_zcu102-oe-linux/device-tree-generation/xilinx+gitAUTOINC+5b21302249-r0/device-tree-generation.yaml
{}



Setting 'YAML_MAIN_MEMORY_CONFIG' seems to enable the DTG to succeed - thanks.



Btw., are there any intentions of a proper fix for the missing DISPLAY variable 
from 
https://lists.yoctoproject.org/pipermail/meta-xilinx/2017-September/003162.html 
(5) ? Your proposal worked for me, however soon there will be a larger team 
within my organization working on this particular baseline and an "upstream" 
fix is thus highly appreciated.



Thanks,

Martin



From: Manjukumar Harthikote Matha 
>
Sent: Friday, December 8, 2017 8:40:02 PM
To: Martin Siegumfeldt; 
meta-xilinx@yoctoproject.org
Subject: RE: Device tree generation failure (2017.3)



Hi Martin,



Can you check if this is empty? 
/home/martin/work/rocko/build/tmp-glibc/work/nanomind_zcu102-oe-linux/device-tree-generation/xilinx+gitAUTOINC+5b21302249-r0/device-tree-generation.yaml



We have a bug when this file is empty it causes DTG recipe to fail, I will send 
out a patch soon



You can set either YAML_MAIN_MEMORY_CONFIG or YAML_CONSOLE_DEVICE_CONFIG as a 
workaround



For example:

https://github.com/Xilinx/meta-xilinx-tools/blob/master/recipes-bsp/device-tree/device-tree-generation_git.bb#L24-L25

[https://avatars0.githubusercontent.com/u/3189299?s=400=4]


Xilinx/meta-xilinx-tools

github.com

Contribute to meta-xilinx-tools development by creating an account on GitHub.






Thanks,

Manju



From: 
meta-xilinx-boun...@yoctoproject.org
 [mailto:meta-xilinx-boun...@yoctoproject.org] On Behalf Of Martin Siegumfeldt
Sent: Friday, December 08, 2017 7:07 AM
To: meta-xilinx@yoctoproject.org
Subject: [meta-xilinx]

[meta-xilinx] [PATCH v3] meta-xilinx: Restructuring meta-xilinx to support multiple layers

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

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

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

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

5 matches

Site Navigation

Mail list logo

Footer information