cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
cb_cross
Adventurer
Adventurer
1,176 Views
Registered: ‎08-10-2018

[Petalinux 2019.1] pmu-firmware fails to build

I have extensive experience with Petalinux 2018.2.  This is my first project with 2019.1.

I installed 2019.1 in parallel with 2018.2:

cpb@roswell:/opt/pkg
12:49:58 $ ls -l
total 12
drwxr-xr-x 5 cpb cpb 4096 Jun 15  2018 petalinux
drwxr-xr-x 6 cpb cpb 4096 May 23  2019 petalinux_2019.1
-rw-rw-r-- 1 cpb cpb 3797 Feb  3 14:06 petalinux_installation_log

I initially created the petalinux project based upon the 2019.1 BSP:

petalinux-create -t project -s ~/Documents/xilinx/BSPs/xilinx-zcu104-v2019.1-final.bsp

I source the 2019.1 config with the following command:

. /opt/pkg/petalinux_2019.1/settings.sh

I then configured the project based upon my Vivado design:

petalinux-config --get-hw-description=../dma_send/dma_send.sdk

I didn't change anything other than to set the default boot to QSPI and changed the host and product names.

When I try to build, it fails on the pmu-firmware.  I tried:

petalinux-build -x mrproper
petalinux-config -c pmufw

but it fails the same way:

[INFO] generating Kconfig for project
[INFO] sourcing bitbake
[INFO] generating plnxtool conf
[INFO] generating meta-plnx-generated layer
[INFO] generating user layers
[INFO] configuring: pmufw
[INFO] generating source for pmufw 
[INFO] bitbake virtual/pmu-firmware -c configure
Loading cache: 100% |###################################################################################################| Time: 0:00:00
Loaded 3812 entries from dependency cache.
Parsing recipes: 100% |#################################################################################################| Time: 0:00:03
Parsing of 2778 .bb files complete (2769 cached, 9 parsed). 3813 targets, 150 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
Initialising tasks: 100% |##############################################################################################| Time: 0:00:00
Checking sstate mirror object availability: 100% |######################################################################| Time: 0:00:00
Sstate summary: Wanted 48 Found 43 Missed 10 Current 0 (89% match, 0% 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/projects/xilinx/2019.1/metal_plx/build/tmp/work/zcu104_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/temp/log.do_configure.8610)
ERROR: Logfile of failure stored in: /opt/projects/xilinx/2019.1/metal_plx/build/tmp/work/zcu104_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/temp/log.do_configure.8610
Log data follows:
| DEBUG: Executing shell function do_configure
| MISC_ARG is  -yamlconf /opt/projects/xilinx/2019.1/metal_plx/build/tmp/work/zcu104_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/pmu-firmware.yaml
| APP_ARG is  -app "ZynqMP PMU Firmware"
| Using xsct from: /opt/pkg/petalinux_2019.1/tools/xsct/bin/xsct
| cmd is: xsct -sdx -nodisp /opt/projects/xilinx/2019.1/metal_plx/build/tmp/work/zcu104_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/app.tcl -ws /opt/projects/xilinx/2019.1/metal_plx/build/tmp/work/zcu104_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/build -pname pmu-firmware -rp /opt/projects/xilinx/2019.1/metal_plx/build/tmp/work/zcu104_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/git -processor psu_pmu_0 -hdf /opt/projects/xilinx/2019.1/metal_plx/build/tmp/deploy/images/zcu104-zynqmp/Xilinx-zcu104-zynqmp.hdf -arch 32  -app "ZynqMP PMU Firmware"  -yamlconf /opt/projects/xilinx/2019.1/metal_plx/build/tmp/work/zcu104_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/pmu-firmware.yaml
| INFO: [Hsi 55-1698] elapsed time for repository loading 0 seconds
| Opening the hardware design, this may take few seconds.
| App name
| Description
| Error in copy exception raised, while copying /opt/pkg/2019.1/tools/xsct/scripts/xsct/data/scw/generic.readme To /opt/projects/xilinx/2019.1/metal_plx/build/tmp/work/zcu104_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/build/pmu-firmware_plat/export/pmu-firmware_plat/sw/sysconfig1/boot
|  Exception Message boost::filesystem::copy_file: No such file or directory: "/opt/pkg/2019.1/tools/xsct/scripts/xsct/data/scw/generic.readme", "/opt/projects/xilinx/2019.1/metal_plx/build/tmp/work/zcu104_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/build/pmu-firmware_plat/export/pmu-firmware_plat/sw/sysconfig1/boot/generic.readme"
| /opt/pkg/2019.1/tools/xsct/gnu/microblaze/lin
| Couldn't figure out compiler's library directory
| ERROR: [Hsi 55-1545] Problem running tcl command ::sw_cpu_v2_9::generate : Couldn't figure out compiler's library directory
|     while executing
| "error "Couldn't figure out compiler's library directory" "" "hsi_error""
|     (procedure "::sw_cpu_v2_9::generate" line 147)
|     invoked from within
| "::sw_cpu_v2_9::generate psu_pmu_0"
| 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/projects/xilinx/2019.1/metal_plx/build/tmp/work/zcu104_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/app.tcl" line 139)
| WARNING: /opt/projects/xilinx/2019.1/metal_plx/build/tmp/work/zcu104_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/temp/run.do_configure.8610:1 exit 1 from 'eval xsct -sdx -nodisp /opt/projects/xilinx/2019.1/metal_plx/build/tmp/work/zcu104_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/app.tcl -ws /opt/projects/xilinx/2019.1/metal_plx/build/tmp/work/zcu104_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/build -pname pmu-firmware -rp /opt/projects/xilinx/2019.1/metal_plx/build/tmp/work/zcu104_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/git -processor psu_pmu_0 -hdf /opt/projects/xilinx/2019.1/metal_plx/build/tmp/deploy/images/zcu104-zynqmp/Xilinx-zcu104-zynqmp.hdf -arch 32 ${APP_ARG} ${MISC_ARG}'
| ERROR: Function failed: do_configure (log file is located at /opt/projects/xilinx/2019.1/metal_plx/build/tmp/work/zcu104_zynqmp-xilinx-linux/pmu-firmware/2019.1+gitAUTOINC+26c14d9861-r0/temp/log.do_configure.8610)
ERROR: Task (/opt/pkg/petalinux_2019.1/components/yocto/source/aarch64/layers/meta-xilinx-tools/recipes-bsp/pmu-firmware/pmu-firmware_git.bb:do_configure) failed with exit code '1'
NOTE: Tasks Summary: Attempted 362 tasks of which 348 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /opt/pkg/petalinux_2019.1/components/yocto/source/aarch64/layers/meta-xilinx-tools/recipes-bsp/pmu-firmware/pmu-firmware_git.bb:do_configure
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
ERROR: Failed to config pmufw.

I've tried searching/googling for answers to this error:

ERROR: [Hsi 55-1545] Problem running tcl command ::sw_cpu_v2_9::generate : Couldn't figure out compiler's library directory

The only answer I found which is specific to my exact error was to build up a fresh Ubuntu install - which is totally unacceptable.

Frankly, it does not surprise me that there is an issue with having 2 versions of Petalinux installed in parallel, but there shouldn't be, their directory trees are separate and the settings.sh script correctly sets up the 2019.1 environment.

I have attached my HDF file, since that seems to be a common request.

Any help is appreciated.

 

0 Kudos
6 Replies
cb_cross
Adventurer
Adventurer
1,173 Views
Registered: ‎08-10-2018

I should add...

I forgot that I tried a petalinux-build before I re-configured the hardware - I got the same pmu-firmware failure then too.

 

0 Kudos
cb_cross
Adventurer
Adventurer
1,125 Views
Registered: ‎08-10-2018

I am using a workaround that I build the pmufw and the fsbl both from within the SDK, and turn them off in the Petalinux config.

I shouldn't have to use this workaround.  It worked fine in 2018.2.

 

0 Kudos
pawelzz
Contributor
Contributor
1,056 Views
Registered: ‎05-16-2018

Hi! Do you have any updates?

I have also the same error and can not find any solution. For me it works with Petalinux 2018.3, but not with 2019.1. I have tried to build project with using Xilinx BSPs for ZCU102, ZCU104 and also my own design. Everytime I get an error:

| ERROR: [Hsi 55-1545] Problem running tcl command ::sw_cpu_v2_9::generate : Couldn't figure out compiler's library directory
| while executing
| "error "Couldn't figure out compiler's library directory" "" "hsi_error""

I have tried to build projects on machines with Ubuntu 16.04 and CentOS 7.7. Both failed on building PMU firmware.

Paweł

0 Kudos
cb_cross
Adventurer
Adventurer
1,049 Views
Registered: ‎08-10-2018

no, no more info is available for 2019.1

The workaround of building fsbl and pmufw in the SDK and turning them off in the petalinux-config is still what I'm doing.

I even opened a support ticket, got a reply from Xilinx saying they can replicate the error and they would reply again with more info, but they never have.

 

0 Kudos
SirBearington
Visitor
Visitor
105 Views
Registered: ‎05-03-2021

Hi, I know this is an old thread, but on the chance you see this I was hoping you could answer a question for me. I'm new to the xilinx board and ran into the issue that you're mentioning here (I'm on v2020.2). I downloaded and installed the sdk -- rebranded as vitis -- so that I could generate the fsbl and pmufw components like you mentioned in your comments. However, I only found the Zynq MP FSBL template (no PMUFW template) in the application projects. I built a release version of fsbl, and have no idea what to do next. Are you copying files into your petalinux project directory before building? Are you adding files to the image after building? Sorry if the answer seems obvious (new to this), but a list of instructions for your workaround would be amazing since this bug hasn't been addressed by xilinx yet.

0 Kudos
watari
Teacher
Teacher
40 Views
Registered: ‎06-16-2013

Hi @SirBearington 

 

Would you post your question as a new thread ?

 

Best regards,

0 Kudos