cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
gmarinkovic
Explorer
Explorer
615 Views
Registered: ‎01-09-2012

RFSoC Petaliniux 2019.1

Jump to solution

Trying to run the Xilinx reference design on my petalinux I get the error message that the libmetal failed for whatever reason... however MPSoC chips do compile correctly can someone point me to the right track?

[marinkovic@PC10512 rfsoc_petalinux_bsp]$ petalinux-build
[INFO] building project
[INFO] sourcing bitbake
[INFO] generating user layers
INFO: bitbake petalinux-user-image
WARNING: Host distribution "fedora-30" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.
Loading cache: 100% |###########################################################################################################################################################################################| Time: 0:00:01
Loaded 3814 entries from dependency cache.
Parsing recipes: 100% |#########################################################################################################################################################################################| Time: 0:00:05
Parsing of 2780 .bb files complete (2779 cached, 1 parsed). 3815 targets, 175 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
WARNING: Your host glibc verson (2.29) is newer than that in uninative (2.28). Disabling uninative so that sstate is not corrupted.
Initialising tasks: 100% |######################################################################################################################################################################################| Time: 0:00:05
Checking sstate mirror object availability: 100% |##############################################################################################################################################################| Time: 0:00:42
Sstate summary: Wanted 417 Found 4 Missed 826 Current 756 (0% match, 64% complete)
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: pmu-firmware-2019.1+gitAUTOINC+26c14d9861-r0 do_configure: Function failed: do_configure (log file is located at /opt/Xilinx/petalinux/rdf0476-zcu111-rf-dc-eval-tool-2019-1/apu/rfsoc_petalinux_bsp/build/tmp/work/zcu111_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/temp/log.do_configure.6206)
ERROR: Logfile of failure stored in: /opt/Xilinx/petalinux/rdf0476-zcu111-rf-dc-eval-tool-2019-1/apu/rfsoc_petalinux_bsp/build/tmp/work/zcu111_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/temp/log.do_configure.6206
Log data follows:
| DEBUG: Executing shell function do_configure
| MISC_ARG is -yamlconf /opt/Xilinx/petalinux/rdf0476-zcu111-rf-dc-eval-tool-2019-1/apu/rfsoc_petalinux_bsp/build/tmp/work/zcu111_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/pmu-firmware.yaml -lib libmetal
| APP_ARG is -app "ZynqMP PMU Firmware"
| Using xsct from: /opt/Xilinx/petalinux/tools/xsct/bin/xsct
| cmd is: xsct -sdx -nodisp /opt/Xilinx/petalinux/rdf0476-zcu111-rf-dc-eval-tool-2019-1/apu/rfsoc_petalinux_bsp/build/tmp/work/zcu111_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/app.tcl -ws /opt/Xilinx/petalinux/rdf0476-zcu111-rf-dc-eval-tool-2019-1/apu/rfsoc_petalinux_bsp/build/tmp/work/zcu111_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/build -pname pmu-firmware -rp /opt/Xilinx/petalinux/rdf0476-zcu111-rf-dc-eval-tool-2019-1/apu/rfsoc_petalinux_bsp/build/tmp/work/zcu111_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/git -processor psu_pmu_0 -hdf /opt/Xilinx/petalinux/rdf0476-zcu111-rf-dc-eval-tool-2019-1/apu/rfsoc_petalinux_bsp/build/tmp/deploy/images/zcu111-zynqmp/Xilinx-zcu111-zynqmp.hdf -arch 32 -app "ZynqMP PMU Firmware" -yamlconf /opt/Xilinx/petalinux/rdf0476-zcu111-rf-dc-eval-tool-2019-1/apu/rfsoc_petalinux_bsp/build/tmp/work/zcu111_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/pmu-firmware.yaml -lib libmetal
| INFO: [Hsi 55-1698] elapsed time for repository loading 0 seconds
| Opening the hardware design, this may take few seconds.
| App name
| Description
| ERROR:set_bsp_conf set dt_overlay TRUE: Cannot set Property "dt_overlay" with TRUE
|
| ERROR: Could not find the bsp config parameter.
| to get the list of valida parameters on "os" run "bsp listparams -os"
| to get the list of valida parameters on "processor" instance run "bsp listparams -proc"
| to get the list of valida parameters on "library" run "bsp listparams -lib <libraryname>"
| /opt/Xilinx/petalinux/tools/xsct/gnu/microblaze/lin
| /opt/Xilinx/petalinux/tools/xsct/tps/lnx64/cmake-3.3.2/bin/cmake: error while loading shared libraries: libidn.so.11: cannot open shared object file: No such file or directory
| child process exited abnormally
| Failed to generate cmake files.
| ERROR: [Hsi 55-1545] Problem running tcl command ::sw_libmetal_v2_0::generate : Failed to generate cmake files.
| while executing
| "error "Failed to generate cmake files.""
| (procedure "::sw_libmetal_v2_0::generate" line 74)
| invoked from within
| "::sw_libmetal_v2_0::generate libmetal"
| ERROR: [Hsi 55-1442] Error(s) while running TCL procedure generate()
| Failed to generate the platform.
| Reason: Failed to generate the bsp sources for domain.pmu-firmware_domain
| while executing
| "builtin_platform -generate quick"
| (procedure "platform" line 221)
| invoked from within
| "platform generate -quick"
| invoked from within
| "if { $params(ws) ne "" } {
| #Local Work Space available
| if { $params(pname) ne "" } {
| # hwpname/bspname is empty then default it to pname+_hwproj/b..."
| (file "/opt/Xilinx/petalinux/rdf0476-zcu111-rf-dc-eval-tool-2019-1/apu/rfsoc_petalinux_bsp/build/tmp/work/zcu111_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitA..." line 139)
| WARNING: /opt/Xilinx/petalinux/rdf0476-zcu111-rf-dc-eval-tool-2019-1/apu/rfsoc_petalinux_bsp/build/tmp/work/zcu111_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/temp/run.do_configure.6206:1 exit 1 from 'eval xsct -sdx -nodisp /opt/Xilinx/petalinux/rdf0476-zcu111-rf-dc-eval-tool-2019-1/apu/rfsoc_petalinux_bsp/build/tmp/work/zcu111_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/app.tcl -ws /opt/Xilinx/petalinux/rdf0476-zcu111-rf-dc-eval-tool-2019-1/apu/rfsoc_petalinux_bsp/build/tmp/work/zcu111_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/build -pname pmu-firmware -rp /opt/Xilinx/petalinux/rdf0476-zcu111-rf-dc-eval-tool-2019-1/apu/rfsoc_petalinux_bsp/build/tmp/work/zcu111_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/git -processor psu_pmu_0 -hdf /opt/Xilinx/petalinux/rdf0476-zcu111-rf-dc-eval-tool-2019-1/apu/rfsoc_petalinux_bsp/build/tmp/deploy/images/zcu111-zynqmp/Xilinx-zcu111-zynqmp.hdf -arch 32 ${APP_ARG} ${MISC_ARG}'
| ERROR: Function failed: do_configure (log file is located at /opt/Xilinx/petalinux/rdf0476-zcu111-rf-dc-eval-tool-2019-1/apu/rfsoc_petalinux_bsp/build/tmp/work/zcu111_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/temp/log.do_configure.6206)
ERROR: Task (/opt/Xilinx/petalinux/components/yocto/source/aarch64/layers/meta-xilinx-tools/recipes-bsp/pmu-firmware/pmu-firmware_git.bb:do_configure) failed with exit code '1'

Second Keyboard Interrupt, stopping...


Summary: 1 task failed:
/opt/Xilinx/petalinux/components/yocto/source/aarch64/layers/meta-xilinx-tools/recipes-bsp/pmu-firmware/pmu-firmware_git.bb:do_configure
Summary: There were 2 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
ERROR: Failed to build project
[marinkovic@PC10512 rfsoc_petalinux_bsp]$

0 Kudos
1 Solution

Accepted Solutions
gmarinkovic
Explorer
Explorer
510 Views
Registered: ‎01-09-2012

I found the problem reading the entry https://forums.xilinx.com/t5/Embedded-Development-Tools/XSDK-cmake-error-building-libmetal-on-Fedora-31/td-p/1104745

Since the problem is a little bit hidden in the message: "...loading shared libraries: libidn.so.11: cannot open shared object file...". The solution is simply: Setting a symbolic link to my newer version libidn.so.12, as @patocarr was proposing, did the job and I was able to compile.

I guess I was too much distracted by the ERROR messages guiding me into a wrong direction and hence missing the subtle message stating the cause of the problem.

 

Cheers

Goran

 

View solution in original post

5 Replies
stephenm
Xilinx Employee
Xilinx Employee
598 Views
Registered: ‎09-12-2007

Are you setting the dt_overlay option to true in the petalinux-config -> DTG Settings?

0 Kudos
shabbirk
Moderator
Moderator
555 Views
Registered: ‎12-04-2016

Hi @gmarinkovic 

Atleast from this page, it looks like some host environment issue, although not sure at this point if it is the same case at your end. However I would suggest cleaning up and project using petalinux-build -x mrproper -f and then try rebuilding it to see how this goes

https://forums.xilinx.com/t5/Embedded-Linux/Pynq-for-Ultra96-Can-t-build-pmu-firmware/td-p/1062801

 

 

Best Regards

Shabbir

0 Kudos
gmarinkovic
Explorer
Explorer
516 Views
Registered: ‎01-09-2012

@shabbirk 

 

Since I know about the problems of petalinux, this is always the first thing I try. But in my case this did not help.

 

Cheers

Goran

0 Kudos
gmarinkovic
Explorer
Explorer
514 Views
Registered: ‎01-09-2012

@stephenm 

 

No, Device Tree Overlay is not what I need and hence did not set this option. Setting this did not help either.

 

Cheers

Goran

0 Kudos
gmarinkovic
Explorer
Explorer
511 Views
Registered: ‎01-09-2012

I found the problem reading the entry https://forums.xilinx.com/t5/Embedded-Development-Tools/XSDK-cmake-error-building-libmetal-on-Fedora-31/td-p/1104745

Since the problem is a little bit hidden in the message: "...loading shared libraries: libidn.so.11: cannot open shared object file...". The solution is simply: Setting a symbolic link to my newer version libidn.so.12, as @patocarr was proposing, did the job and I was able to compile.

I guess I was too much distracted by the ERROR messages guiding me into a wrong direction and hence missing the subtle message stating the cause of the problem.

 

Cheers

Goran

 

View solution in original post