Hi Brian, all, I noticed you add some stuff in local.conf to specify the types of images being built, e.g.
# add Boot.bin dependency IMAGE_CLASSES += " xilinx-bootbin" Where are these defined? How can I see a list of possible choices for this? Giordon On Fri, Sep 1, 2017 at 9:40 AM Martin Siegumfeldt <[email protected]> wrote: > Thanks Manju, I now have it building and it also seems to boot the > artifacts. The missing display-variable exporting and the potentially also > the missing reference to the tools-variant of the device-tree-generation > seems to be the culprit. > > Br, > Martin > > > From: Manjukumar Harthikote Matha <[email protected]> > Sent: Friday, September 1, 2017 04:40 > To: Manjukumar Harthikote Matha; Mike Looijmans; Brian Hutchinson; Martin > Siegumfeldt > Cc: [email protected] > Subject: 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 = "<location>/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 = "<path-to-xsdk>" > > 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 > > https://avatars0.githubusercontent.com/u/3189299?v=4&s=400 > > Xilinx/meta-xilinx-tools > github.com > Contribute to meta-xilinx-tools development by creating an account on > GitHub. > > > 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-<machine>.elf > pmu-firmware-<machine>.elf > <machine>-system.dts (DTG generated dts using the HDF provided) > <machine>-system.dtb (DTG generated dtb using the HDF provided) > > Other images > pmu-<machine> is from meta-xilinx recipe > > Thanks, > Manju > > > > -----Original Message----- > > From: [email protected] [mailto:meta-xilinx- > > [email protected]] On Behalf Of Manjukumar Harthikote Matha > > Sent: Thursday, August 31, 2017 2:33 PM > > To: Mike Looijmans <[email protected]>; Brian Hutchinson > > <[email protected]> > > Cc: [email protected] > > 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:[email protected]] > > > Sent: Thursday, August 31, 2017 10:52 AM > > > To: Brian Hutchinson <[email protected]>; Manjukumar Harthikote > > > Matha <[email protected]> > > > Cc: Giordon Stark <[email protected]>; Jean-Francois Dagenais > > > <[email protected]>; [email protected] > > > 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 > > [email protected] > > https://lists.yoctoproject.org/listinfo/meta-xilinx > > -- > _______________________________________________ > meta-xilinx mailing list > [email protected] > https://lists.yoctoproject.org/listinfo/meta-xilinx >
-- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
