Re: [meta-xilinx] meta-xilinx-tools fails on "device-tree-generation" script
> On Aug 31, 2017, at 22:21, Manjukumar Harthikote Matha > wrote: > > Something in upstream has changed causing DISPLAY variable not being passed > from environment. They all fail saying Xvfb is not available. You can see the > log.do_configure or log.do_compile Yocto builds can be run in environment which do not have DISPLAY set. e.g. a server, or a docker container. The tools should not expect this variable to be set. I had to install Xvfb in my yocto builder docker image and add /usr/bin to the PATH env variable at the top of classes/xsct-tc.bbclass since xvfb is not provided in the yocto staging sysroot (I don't have X11 in my DISTRO_FEATURES). Using /usr/bin is not so clean, but building it inside yocto without "x11" in DISTRO_FEATURES seemed way more complicated. I figured hacking xsct-tc.bbclass was a low-impact compromise. Has been working great in my production environment for months now. I've submitted the patch in the past but it was deferred for obvious reasons. The problem is not going to go away so this may be the time to reconsider my previous patch. https://www.mail-archive.com/meta-xilinx@yoctoproject.org/msg01662.html Cheers! -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
Re: [meta-xilinx] [meta-xilinx-tools]Nothing PROVIDES 'python3-pyyaml-native'.
Hi Brett, > -Original Message- > From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx- > boun...@yoctoproject.org] On Behalf Of Manjukumar Harthikote Matha > Sent: Thursday, August 31, 2017 10:08 AM > To: Brett R. Nicholas ; meta- > xil...@yoctoproject.org > Subject: Re: [meta-xilinx] [meta-xilinx-tools]Nothing PROVIDES > 'python3-pyyaml- > native'. > > [This sender failed our fraud detection checks and may not be who they appear > to > be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing] > > Hi Brett, > > > -Original Message- > > From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx- > > boun...@yoctoproject.org] On Behalf Of Brett R. Nicholas > > Sent: Wednesday, August 30, 2017 7:51 PM > > To: meta-xilinx@yoctoproject.org > > Subject: [meta-xilinx] [meta-xilinx-tools]Nothing PROVIDES 'python3-pyyaml- > native'. > > > > Hi there, > > > > > > I'm trying to build a (once working) Yocto distribution for the > > Zedboard. When I went back to the project, and attempted to build > > core-image- > minimal I get this error: > > > > brett: build $ bitbake core-image-minimal Loading cache: 100% > > > |### > > #| Time: 0:00:00 Loaded 2616 entries > > from dependency cache. > > Parsing recipes: 100% > > > |### > > ###| Time: 0:00:00 Parsing of 1923 .bb > > files complete (1918 cached, 5 parsed). 2621 targets, 153 skipped, 0 > > masked, 0 > errors. > > NOTE: Resolving any missing task queue dependencies > > ERROR: Nothing PROVIDES 'python3-pyyaml-native'. Close matches: > > python-pyyaml-native > > python3-py-native > > python-py-native > > ERROR: Required build target 'core-image-minimal' has no buildable > > providers. > > Missing or unbuildable dependency chain was: ['core-image-minimal', > > 'virtual/bootloader', 'virtual/dtb', 'python3-pyyaml-native'] > > > > Summary: There were 2 ERROR messages shown, returning a non-zero exit code. > > > > > > > > I've seen this post here > > (https://lists.yoctoproject.org/pipermail/meta-xilinx/2017- > > April/002717.html). Can I still apply this patch if I am not using the > > meta-petalinux layer? Please let me know how I can patch it. > > > > Use http://cgit.openembedded.org/meta-openembedded/tree/meta-python layer, > it should get the pyyaml dependency > Please see https://lists.yoctoproject.org/pipermail/meta-xilinx/2017-September/003162.html I posted some instructions on how to include meta-xilinx-tools and build bootable images Thanks, Manju -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
Re: [meta-xilinx] meta-xilinx-tools fails on "device-tree-generation" script
Hi Martin, > -Original Message- > From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx- > boun...@yoctoproject.org] On Behalf Of Martin Siegumfeldt > Sent: Thursday, August 31, 2017 5:02 PM > To: meta-xilinx@yoctoproject.org > Subject: [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% > |### > > > ###| Time: 0:00:51 > Parsing of 1799 .bb files complete (0 cached, 1799 parsed). 2597 targets, 167 > skipped, 0 masked, 0 errors. > NOTE: Resolving any missing task queue dependencies > > Build Configuration: > BB_VERSION = "1.35.0" > BUILD_SYS = "x86_64-linux" > NATIVELSBSTRING = "ubuntu-17.04" > TARGET_SYS = "aarch64-poky-linux" > MACHINE = "zcu102-zynqmp" > DISTRO = "poky" > DISTRO_VERSION = "2.3+snapshot-20170831" > TUNE_FEATURES = "aarch64" > TARGET_FPU = "" > meta > meta-poky = "master:489e2e3243d7acdcb9c1f9de110139b6636d5594" > meta-oe > meta-python = "master:28d2c9b4474844516a9e8328bb497cdf3bec88ef" > meta-xilinx = "master:74a0d90e52cca346d05a69bbd628c6ec9e49fbcb" > meta-xilinx-tools = "master:34e96ca0dfd2cfe101d07bc6db06fc9ae1629ce4" > > NOTE: Fetching uninative binary shim from > http://downloads.yoctoproject.org/releases/uninative/1.7/x86_64-nativesdk- > libc.tar.bz2;sha256sum=ed033c868b87852b07957a4400f3b744c00aef5d6470346ea1 > a59b6d3e03075e > > [10]+ Stopped bitbake core-image-minimal > martin@martin-Precision-5510:~/work/zcu102_os/build$ vim ../meta- > xilinx/conf/machine/include/machine-xilinx-default.inc > martin@martin-Precision-5510:~/work/zcu102_os/build$ fg > bitbake core-image-minimal > Initialising tasks: 100% > |### > > > | Time: 0:00:02 > NOTE: Executing SetScene Tasks > NOTE: Executing RunQueue Tasks > Currently 2 rCurrently 2 running tasks (1514 of 2461) 61% > |### > > > ERROR: device-tree-generation-xilinx+gitAUTOINC+43551819a1-r0 do_compile: > Function failed: do_compile (log file is located at > /home/martin/work/zcu102_os/build/tmp/work/zcu102_zynqmp-poky-linux/device- > tree-generation/xilinx+gitAUTOINC+43551819a1-r0/temp/log.do_compile.18302) > ERROR: Logfile of failure stored in: > /home/martin/work/zcu102_os/build/tmp/work/zcu102_zynqmp-poky-linux/device- > tree-generation/xilinx+gitAUTOINC+43551819a1-r0/temp/log.do_compile.18302 > Log data follows: > | DEBUG: Executing shell function do_compile > | gcc: error: /home/martin/work/zcu102_os/build/tmp/work/zcu102_zynqmp-poky- > linux/device-tree-generation/xilinx+gitAUTOINC+43551819a1-r0/build/device-tree- > generation/system-top.dts: No such file or directory > | gcc: warning: '-x assembler-with-cpp' after last input file has no effect > | gcc: fatal error: no input files > | compilation terminated. > | WARNING: exit code 1 from a shell command. > | ERROR: Function failed: do_compile (log file is located at > /home/martin/work/zcu102_os/build/tmp/work/zcu102_zynqmp-poky-linux/device- > tree-generation/xilinx+gitAUTOINC+43551819a1-r0/temp/log.do_compile.18302) > ERROR: Task (/home/martin/work/zcu102_os/poky/../meta-xilinx-tools/recipes- > bsp/device-tree/device-tree-generation_git.bb:do_compile) failed with exit > code '1' > NOTE: Tasks Summary: Attempted 1719 tasks of which 6 didn't need to be rerun > and > 1 failed. > > Summary: 1 task failed: > /home/martin/work/zcu102_os/poky/../meta-xilinx-tools/recipes-bsp/device- > tree/device-tree-generation_git.bb:do_compile > Summary: There was 1 ERROR message shown, returning a non-zero exit code. > > martin@martin-Precision-5510:~/work/zcu102_os/build$ cat > /home/martin/work/zcu102_os/build/tmp/work/zcu102_zynqmp-poky-linux/device- > tree-generation/xilinx+gitAUTOINC+43551819a1-r0/temp/log.do_configure > DEBUG: Executing shell function do_configure > MISC_ARG is -yamlconf > /home/martin/work/zcu102_os/build/tmp/work/zcu102_zynqmp-poky-linux/device- > tree-generation/xilinx+gitAUTOINC+43551819a1-r0/device-tree-generation.yaml > APP_ARG is -app "device-tree" > cmd is: xsct /home/martin/work/zcu102_os/build/tmp/work/zcu102_zynqmp-poky- > linux/device-tree-generation/xilinx+gitAUTOINC+43551819a1-r0/dtgen.tcl
Re: [meta-xilinx] How to boot the ZynqMP?
Hi All, Sorry for writing on top. I wanted to summarize the flow which worked for me without meta-petalinux layer. I have poky, meta-xilinx, meta-openembedded and meta-xilinx-tools (all on master branch) If you have a build, please make sure to cleansstate fsbl,pmu-firmware, device-tree-generation, bitstream-extraction recipes before you start 1) Make sure you have meta-oe and meta-python in bblayers.conf (Will apply Mike's patch on meta-xilinx-tools) 2)Either copy https://github.com/Xilinx/meta-xilinx-tools/blob/master/conf/machine/include/machine-xilinx-zynqmp.inc to local.conf or include this file from your custom machine 3) Provide the HDF file using a) Local path: HDF_BASE = "file://" HDF_PATH = "/system.hdf" b) Or using git https://github.com/Xilinx/meta-xilinx-tools/blob/master/recipes-bsp/hdf/external-hdf.bb#L9-L10 4) Provide the path to the installed XSDK in local.conf XILINX_SDK_TOOLCHAIN = "" 5) I had to add export DISPLAY=:1 before this line here https://github.com/Xilinx/meta-xilinx-tools/blob/master/classes/xsctbase.bbclass#L48 and https://github.com/Xilinx/meta-xilinx-tools/blob/master/classes/xsctbase.bbclass#L56 We did not observe this issue in Morty, seems to have changed in Pyro or master. I am still checking how to make a patch using WHITELIST rather than above approach. Any suggestions? 6) there are two device-tree recipes one in meta-xilinx and one meta-xilinx-tools, set the preferred provider to one in meta-xilinx-tools in local.conf PREFERRED_PROVIDER_virtual/dtb ?= "device-tree-generation" 7) bitbake the image Once the image builds you see the following BOOT.bin (this will contain fsbl, pmu, atf, bitstream and u-boot) fsbl-.elf pmu-firmware-.elf -system.dts (DTG generated dts using the HDF provided) -system.dtb (DTG generated dtb using the HDF provided) Other images pmu- is from meta-xilinx recipe Thanks, Manju > -Original Message- > From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx- > boun...@yoctoproject.org] On Behalf Of Manjukumar Harthikote Matha > Sent: Thursday, August 31, 2017 2:33 PM > To: Mike Looijmans ; Brian Hutchinson > > Cc: meta-xilinx@yoctoproject.org > Subject: Re: [meta-xilinx] How to boot the ZynqMP? > > [This sender failed our fraud detection checks and may not be who they appear > to > be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing] > > Hi Mike, > > > -Original Message- > > From: Mike Looijmans [mailto:mike.looijm...@topic.nl] > > Sent: Thursday, August 31, 2017 10:52 AM > > To: Brian Hutchinson ; Manjukumar Harthikote > > Matha > > Cc: Giordon Stark ; Jean-Francois Dagenais > > ; meta-xilinx@yoctoproject.org > > Subject: Re: [meta-xilinx] How to boot the ZynqMP? > > > > On 30-08-17 22:20, Brian Hutchinson wrote: > > > I too have been wrestling with generating the required images to > > > boot the > > > ZCU102 from SD Card using the Yocto + meta-xilinx + meta-xilinx-tools > > > method. > > > > > > I'm totally striking out. And I'm working with a Xilinx FAE and > > > striking out! No problem at all doing this kind of thing for ZCU107 > > > or Zedboard but > > > ZCU102 is different beast for sure. > > > > > > I have Ubuntu 16.04 box, I've tried yocto 2.2.1 (morty) and 2.3 > > > (pyro) and I get the same result ... my builds die with: > > > > > ... > > > | DEBUG: Executing shell function do_deploy > > > | install: cannot stat > > > '/home/hutch/yocto_2.2.1- > > morty_zcu102/layers/poky/build/tmp/work/zcu102_zynqmp-poky-linux/pmu- > > firmware/2017.1+gitAUTOINC+122565ec40-r0/build/pmu-firmware/Release/pm > > u- > > firmware.elf': > > > No such file or directory > > > > > > Most likely the problem is that the "Release" directory was not > > created yet. I have seen this race condition several times in makefiles. > > As a workaround, add a do_compile_prepend with "mkdir Release" or so. > > > > However, this seems to happen in the "do_install" phase, so that's > > probably not the case here. > > > > Another issue can be that actually the "compile" failed. Most of > > Xilinx' tools don't return error codes, so bitbake thinks everything > > went fine but it didn't actually produce outputs. And since do_compile > > was okay, it won't run again and install keeps failing. > > > > Add a do_compile_append() that contains something like: > > test -e Release/pmu-firmware.elf > > and that would cause do_compile to fail if there's no output. > > > > I think this patch fixes the issue you are mentioning > https://github.com/Xilinx/meta-xilinx- > tools/commit/ecb804aeb5f23156e36e32085a229883944b0b47 > > Thanks, > Manju > -- > ___ > meta-xilinx mailing list > meta-xilinx@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-xilinx -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
Re: [meta-xilinx] How to boot the ZynqMP?
On Thu, Aug 31, 2017 at 5:02 AM, Manjukumar Harthikote Matha < manju...@xilinx.com> wrote: > > > I think this patch fixes the issue you are mentioning > https://github.com/Xilinx/meta-xilinx-tools/commit/ > ecb804aeb5f23156e36e32085a229883944b0b47 > > Thanks, > Manju > Thank you and Mike Looijmans for this clue! After applying that patch I discovered my problem was: | Building '/pmu-firmware' | 13:07:38 Build of configuration Release for project pmu-firmware | make all | Building file: ../src/idle_hooks.c | Invoking: MicroBlaze gcc compiler | mb-gcc -Wall -O2 -c -fmessage-length=0 -MT"src/idle_hooks.o" -Os -flto -ffat-lto-objects -I../../pmu-firmware_bsp/psu_pmu_0/include -mlittle-endian -mxl-barrel-shift -mxl-pattern-compare -mcpu=v9.2 -mxl-soft-mul -Wl,--no-relax -ffunction-sections -fdata-sections -MMD -MP -MF"src/idle_hooks.d" -MT"src/idle_hooks.o" -o "src/idle_hooks.o" "../src/idle_hooks.c" | /home/hutch/Xilinx/SDK/2017.1/gnu/microblaze/lin/bin/../lib/gcc/microblaze-xilinx-elf/6.2.0/../../../../microblaze-xilinx-elf/bin/as: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory | src/subdir.mk:181: recipe for target 'src/idle_hooks.o' failed | make: *** [src/idle_hooks.o] Error 1 So I added sudo dpkg --add-architecture i386 and installed the i386 libs but still initially missed one. The one I needed to get past the error was: sudo apt-get install lib32z1 Build completed and I see BOOT.bin now so I'm happy. Regards, Brian -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
