I am using poky not oe-core and I need this change for u-boot to build reliably.
"Manjukumar Harthikote Matha" <[email protected]> said: > Hi Richard, > >> -----Original Message----- >> From: [email protected] <[email protected]> >> On Behalf Of Scott Ellis via Lists.Yoctoproject.Org >> Sent: Saturday, December 7, 2019 7:02 AM >> To: Richard Cagley <[email protected]> >> Cc: [email protected] >> Subject: Re: [meta-xilinx] instructions for building basic warrior image for >> zcu104 >> >> u-boot SPL depends on pmu-firmware. >> >> The recommendation for this line in local.conf >> >> do_image[mcdepends] = "multiconfig::pmu:pmu-firmware:do_deploy" >> >> >> Doesn't tell bitbake to pull in the requirement in time. >> >> >> I put the following in a u-boot bbappend >> >> $ cat meta-<myproject>/recipes-bsp/u-boot/u-boot-xlnx_2019.1.bbappend >> do_compile[mcdepends] = "multiconfig::pmu:pmu-firmware:do_deploy" >> > > This was a workaround due to a issue in OE-Core, I believe this got fixed. > > We had this in the readme and later removed it for Warrior release > https://github.com/Xilinx/meta-xilinx/blob/c42016e2e6ca13e133fdb877785ec8aa2bd82f16/meta-xilinx-bsp/README.building.md > > Thanks, > Manju > >> >> This way the u-boot recipe itself makes sure that pmu-firmware is built >> first. >> >> >> >> To manually verify this is the problem you are seeing, first build the pmu- >> firmware >> >> bitbake multiconfig:pmu:pmu-firmware >> >> >> Then see if u-boot builds successfully >> >> bitbake virtual/bootloader >> >> or >> >> bitbake u-boot-xlnx >> >> >> If that works, then that was the issue. >> >> >> >> "Richard Cagley" <[email protected]> said: >> >> > -=-=-=-=-=-=-=-=-=-=-=- >> > Links: You receive all messages sent to this group. >> > >> > View/Reply Online (#4575): >> > https://lists.yoctoproject.org/g/meta-xilinx/message/4575 >> > Mute This Topic: https://lists.yoctoproject.org/mt/67565968/3618554 >> > Group Owner: [email protected] >> > Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub >> > [[email protected]] >> > -=-=-=-=-=-=-=-=-=-=-=- >> > This is a very noob question, but can someone point me to what I'm doing >> > wrong. >> > >> > When I try to build core-image-minimal (or my derived layer) I get this >> > error >> > >> > | >> > /yocto/warrior-zcu104/tmp/work/zcu104_zynqmp-poky-linux/u-boot- >> xlnx/v2019.01 >> > -xilinx-v2019.1+gitAUTOINC+d895ac5e94-r0/git/Makefile:1653: recipe for >> > target 'spl/u-boot-spl' failed >> > | make[1]: *** [spl/u-boot-spl] Error 2 >> > >> > I've read there are multiple flows and I'm trying to follow the standard >> > yocto/non meta-xilinx-tools flow. >> > >> > In my local.conf I have overwritten or added these settings: >> > MACHINE ??= "zcu104-zynqmp" >> > LICENSE_FLAGS_WHITELIST += "xilinx" >> > BBMULTICONFIG ?= "pmu" >> > >> > In conf/multiconfig/pmu.conf I have: >> > MACHINE="zynqmp-pmu" >> > DISTRO="xilinx-standalone" >> > TMPDIR="${TOPDIR}/pmutmp" >> > >> > In my bblayers.conf I have: >> > BBLAYERS ?= " \ >> > /opt/oe/warrior/poky/meta \ >> > /opt/oe/warrior/poky/meta-poky \ >> > /opt/oe/warrior/poky/meta-yocto-bsp \ >> > /opt/oe/warrior/meta-xilinx/meta-xilinx-bsp \ >> > /opt/oe/warrior/meta-xilinx/meta-xilinx-standalone \ >> > /opt/oe/warrior/meta-zcu104 \ >> > " >> > >> > Where my layer meta-zcu104 has my own core-image-zcu104.bb with: >> > DESCRIPTION = "Extend core-image by adding stuff we want" >> > inherit core-image >> > do_image[mcdepends] = "multiconfig::pmu:pmu-firmware:do_deploy" >> > >> > any ideas? >> > >> > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4581): https://lists.yoctoproject.org/g/meta-xilinx/message/4581 Mute This Topic: https://lists.yoctoproject.org/mt/67565968/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
