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 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 <manju...@xilinx.com>; 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 <manju...@xilinx.com<mailto:manju...@xilinx.com>> Sent: Monday, December 11, 2017 6:18:04 PM To: Martin Siegumfeldt; meta-xilinx@yoctoproject.org<mailto: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 > <manju...@xilinx.com<mailto:manju...@xilinx.com>>; meta- > xil...@yoctoproject.org<mailto: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<mailto:meta-xilinx-boun...@yoctoproject.org> > <meta-xilinx- > boun...@yoctoproject.org<mailto:boun...@yoctoproject.org>> on behalf of > Martin Siegumfeldt > <m...@gomspace.com<mailto:m...@gomspace.com>> > Sent: Friday, December 8, 2017 22:11 > To: Manjukumar Harthikote Matha; > meta-xilinx@yoctoproject.org<mailto: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 <http://aka.ms/LearnAboutSpoofing> > Feedback <http://aka.ms/SafetyTipsFeedback> > > Ok sounds good - looking forwards to it... > > > > > Cheers, > > Martin > > ________________________________ > > From: Manjukumar Harthikote Matha > <manju...@xilinx.com<mailto:manju...@xilinx.com>> > Sent: Friday, December 8, 2017 10:02:18 PM > To: Martin Siegumfeldt; > meta-xilinx@yoctoproject.org<mailto: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 > <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 > <manju...@xilinx.com<mailto:manju...@xilinx.com>>; meta- > xil...@yoctoproject.org<mailto: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 > <https://lists.yoctoproject.org/pipermail/meta-xilinx/2017- <https://lists.yoctoproject.org/pipermail/meta-xilinx/2017-%0b>> 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 <manju...@xilinx.com <mailto:manju...@xilinx.com%0b>> <mailto:manju...@xilinx.com> > > Sent: Friday, December 8, 2017 8:40:02 PM > To: Martin Siegumfeldt; > meta-xilinx@yoctoproject.org<mailto:meta-xilinx@yoctoproject.org> > <mailto:meta- <mailto:meta-%0b>> xil...@yoctoproject.org<mailto: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 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://github.com/Xilinx/meta- <https://github.com/Xilinx/meta-%0b>> xilinx-tools/blob/master/recipes-bsp/device-tree/device-tree- > generation_git.bb#L24-L25> > > <https://github.com/Xilinx/meta-xilinx-tools/blob/master/recipes-bsp/device- <https://github.com/Xilinx/meta-xilinx-tools/blob/master/recipes-bsp/device-%0b>> tree/device-tree-generation_git.bb#L24-L25> > > Xilinx/meta-xilinx-tools <https://github.com/Xilinx/meta-xilinx- <https://github.com/Xilinx/meta-xilinx-%0b>> tools/blob/master/recipes-bsp/device-tree/device-tree-generation_git.bb#L24- > L25> > > 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> > <mailto:meta-xilinx- <mailto:meta-xilinx-%0b>> boun...@yoctoproject.org<mailto:boun...@yoctoproject.org>> [mailto: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<mailto:meta-xilinx@yoctoproject.org> > <mailto:meta-xilinx@yoctoproject.org> > Subject: [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 = > "/opt/Xilinx/SDK/2017.3/gnu/microblaze/linux_toolchain/lin64_le" > > XILINX_SDK_TOOLCHAIN = "/opt/Xilinx/SDK/${XILINX_VER_MAIN}" > > > > HDF_BASE = "file://" > > HDF_PATH = "${TOPDIR}/../meta-z7000/recipes-bsp/system.hdf" > > > > Please consider below error: > > > > martin@martin-Precision-5510:~/work/rocko/build$ MACHINE="nanomind- > zcu102" bitbake device-tree-generation > > Loading cache: 100% > |############################################################### > ################################################################ > ################################################################ > #################################################| Time: 0:00:00 > > Loaded 261 entries from dependency cache. > > ##################################| Time: 0:00:36 > > Parsing of 1961 .bb files complete (160 cached, 1801 parsed). 2777 targets, > 309 > skipped, 0 masked, 0 errors. > > NOTE: Resolving any missing task queue dependencies > > > > Build Configuration: > > BB_VERSION = "1.36.0" > > BUILD_SYS = "x86_64-linux" > > NATIVELSBSTRING = "ubuntu-17.04" > > TARGET_SYS = "aarch64-oe-linux" > > MACHINE = "nanomind-zcu102" > > DISTRO = "gomspace" > > DISTRO_VERSION = "2.0" > > TUNE_FEATURES = "aarch64" > > TARGET_FPU = "" > > meta > > meta-poky = "rocko:f7b90ab3eaf832bd81f3efc1dab4dcf6863ac284" > > meta-xilinx = "master:eb16f4088bf2043501abcea6d2beea91349574b3" > > meta-xilinx-tools = "master:1063db48e44d5098590d39fe0018be5bb21a0a6d" > > meta-oe > > meta-filesystems > > meta-networking > > meta-python = "rocko:6e3fc5b8d904d06e3aa77e9ec9968ab37a798188" > > meta-z7000 = "rocko:f2c81712c48725820ed2600a669d1614095445d5" > > > > Initialising tasks: 100% > |############################################################### > ################################################################ > ################################################################ > ############################################| Time: 0:00:00 > > NOTE: Executing SetScene Tasks > > NOTE: Executing RunQueue Tasks > > ERROR: device-tree-generation-xilinx+gitAUTOINC+5b21302249-r0 do_configure: > Function failed: do_configure (log file is located at > /home/martin/work/rocko/build/tmp-glibc/work/nanomind_zcu102-oe- > linux/device-tree-generation/xilinx+gitAUTOINC+5b21302249- > r0/temp/log.do_configure.30813) > > ERROR: Logfile of failure stored in: /home/martin/work/rocko/build/tmp- > glibc/work/nanomind_zcu102-oe-linux/device-tree- > generation/xilinx+gitAUTOINC+5b21302249-r0/temp/log.do_configure.30813 > > Log data follows: > > | DEBUG: Executing shell function do_configure > > | MISC_ARG is -yamlconf /home/martin/work/rocko/build/tmp- > glibc/work/nanomind_zcu102-oe-linux/device-tree- > generation/xilinx+gitAUTOINC+5b21302249-r0/device-tree-generation.yaml > > | APP_ARG is -app "device-tree" > > | cmd is: xsct /home/martin/work/rocko/build/tmp-glibc/work/nanomind_zcu102- > oe-linux/device-tree-generation/xilinx+gitAUTOINC+5b21302249-r0/dtgen.tcl -ws > /home/martin/work/rocko/build/tmp-glibc/work/nanomind_zcu102-oe- > linux/device-tree-generation/xilinx+gitAUTOINC+5b21302249-r0/build -pname > device-tree-generation -rp /home/martin/work/rocko/build/tmp- > glibc/work/nanomind_zcu102-oe-linux/device-tree- > generation/xilinx+gitAUTOINC+5b21302249-r0/git -processor psu_cortexa53_0 - > hdf /home/martin/work/rocko/build/tmp-glibc/deploy/images/nanomind- > zcu102/Xilinx-nanomind-zcu102.hdf -arch 64 -app "device-tree" -yamlconf > /home/martin/work/rocko/build/tmp-glibc/work/nanomind_zcu102-oe- > linux/device-tree-generation/xilinx+gitAUTOINC+5b21302249-r0/device-tree- > generation.yaml > > | WARNING: [Hsi 55-1434] Error > /opt/Xilinx/SDK/2017.3/data/embeddedsw/XilinxProcessorIPLib/drivers/rfdc_v2_1 > /data/rfdc.mdd:49 Unrecognized Option name. List of possible Option names > are : > DRC, DESC, COPYFILES, DEPENDS, SUPPORTED_PERIPHERALS, DRIVER_STATE, > DEFAULT_OS, NAME, VERSION > > | > > | INFO: [Hsi 55-1698] elapsed time for repository loading 0 seconds > > | hsi::open_hw_design: Time (s): cpu = 00:00:06 ; elapsed = 00:00:06 . Memory > (MB): peak = 475.559 ; gain = 136.270 ; free physical = 10766 ; free virtual > = 51512 > > | {} is not a huddle. > > | while executing > > | "error "\{$src\} is not a huddle."" > > | (procedure "checkHuddle" line 3) > > | invoked from within > > | "checkHuddle $src" > > | (procedure "::huddle::type" line 2) > > | invoked from within > > | "::huddle::type {}" > > | ("eval" body line 1) > > | invoked from within > > | "eval ::huddle::$command $args" > > | (procedure "huddle" line 19) > > | invoked from within > > | "huddle type $value" > > | (procedure "_composePlain" line 2) > > | invoked from within > > | "_composePlain $result" > > | (procedure "_parseBlockNode" line 118) > > | invoked from within > > | "_parseBlockNode" > > | (procedure "::yaml::yaml2dict" line 4) > > | invoked from within > > | "::yaml::yaml2dict -file $yamlconf" > > | (procedure "set_properties" line 4) > > | invoked from within > > | "set_properties $params(yamlconf)" > > | (file "/home/martin/work/rocko/build/tmp-glibc/work/nanomind_zcu102-oe- > linux/device-tree-generation/xilinx+gitAUTOINC+5b21302249-r0/dtgen.tcl" line > 32) > > | WARNING: exit code 1 from a shell command. > > | ERROR: Function failed: do_configure (log file is located at > /home/martin/work/rocko/build/tmp-glibc/work/nanomind_zcu102-oe- > linux/device-tree-generation/xilinx+gitAUTOINC+5b21302249- > r0/temp/log.do_configure.30813) > > ERROR: Task (/home/martin/work/rocko/poky/../meta-xilinx-tools/recipes- > bsp/device-tree/device-tree-generation_git.bb:do_configure) failed with exit > code > '1' > > NOTE: Tasks Summary: Attempted 692 tasks of which 678 didn't need to be rerun > and 1 failed. > > > > invoking the xsct command outside bitbake context yields the exact same error. > > > > The exact reason for the failure is not ver clear to me - 'Unrecognized > Option name' > seems like a known issue: https://forums.xilinx.com/t5/Embedded-Development- > Tools/createhw-warning-in-2017-3-that-was-not-present-in-2017-2/td-p/801498 > <https://forums.xilinx.com/t5/Embedded-Development-Tools/createhw-warning- <https://forums.xilinx.com/t5/Embedded-Development-Tools/createhw-warning-%0b>> in-2017-3-that-was-not-present-in-2017-2/td-p/801498> - don't know if it causes > bitbake to not finish the recipe though? Or is it the ' "error "\{$src\} is > not a > huddle.""'? I am not very familiar with debugging tcl scripts. > > > > I am puzzled since the same HDF file is used in both cases and the machine > configuration is almost identical. > > > > Any ideas? > > > > Thanks, > > Martin
-- _______________________________________________ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
