cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Explorer
Explorer
1,538 Views
Registered: ‎11-28-2011

Petalinux 2017.2 build error do_deploy

NOTE: Executing RunQueue Tasks
ERROR: external-hdf-1.0-r0 do_deploy: Function failed: do_deploy (log file is located at /tmp/mbp_petalinux-2017.10.06-10.05.51/work/cortexa9hf-neon-xilinx-linux-gnueabi/external-hdf/1.0-r0/temp/log.do_deploy.32715)
ERROR: Logfile of failure stored in: /tmp/mbp_petalinux-2017.10.06-10.05.51/work/cortexa9hf-neon-xilinx-linux-gnueabi/external-hdf/1.0-r0/temp/log.do_deploy.32715
Log data follows:
| DEBUG: Executing python function sstate_task_prefunc
| DEBUG: Python function sstate_task_prefunc finished
| DEBUG: Executing shell function do_deploy
| install: cannot stat `/tmp/mbp_petalinux-2017.10.06-10.05.51/work/cortexa9hf-neon-xilinx-linux-gnueabi/external-hdf/1.0-r0/git/plnx_arm/system.hdf': No such file or directory
| WARNING: /tmp/mbp_petalinux-2017.10.06-10.05.51/work/cortexa9hf-neon-xilinx-linux-gnueabi/external-hdf/1.0-r0/temp/run.do_deploy.32715:1 exit 1 from 'install -m 0644 /tmp/mbp_petalinux-2017.10.06-10.05.51/work/cortexa9hf-neon-xilinx-linux-gnueabi/external-hdf/1.0-r0/git/plnx_arm/system.hdf /tmp/mbp_petalinux-2017.10.06-10.05.51/work/cortexa9hf-neon-xilinx-linux-gnueabi/external-hdf/1.0-r0/deploy-external-hdf/Xilinx-plnx_arm.hdf'
| ERROR: Function failed: do_deploy (log file is located at /tmp/mbp_petalinux-2017.10.06-10.05.51/work/cortexa9hf-neon-xilinx-linux-gnueabi/external-hdf/1.0-r0/temp/log.do_deploy.32715)
ERROR: Task (/home/e296015/dev_tools/opt/pkg/petalinux/components/yocto/source/arm/layers/meta-xilinx-tools/recipes-bsp/hdf/external-hdf.bb:do_deploy) failed with exit code '1'

 

 

The error correct as there is not system.hdf located there. My system.hdf is located in a exported sdk path

 

 

 

Using RHEL 6.9

 

 

0 Kudos
3 Replies
Highlighted
Explorer
Explorer
1,536 Views
Registered: ‎11-28-2011

It looks like do_deploy is doing this

 

do_deploy() {
install -d /tmp/mbp_petalinux-2017.10.06-10.05.51/work/cortexa9hf-neon-xilinx-linux-gnueabi/external-hdf/1.0-r0/deploy-external-hdf
if [ "git://" = "git://" ]; then
install -m 0644 /tmp/mbp_petalinux-2017.10.06-10.05.51/work/cortexa9hf-neon-xilinx-linux-gnueabi/external-hdf/1.0-r0/git/plnx_arm/system.hdf /tmp/mbp_petalinux-2017.10.06-10.05.51/work/cortexa9hf-neon-xilinx-linux-gnueabi/external-hdf/1.0-r0/deploy-external-hdf/Xilinx-plnx_arm.hdf
else
install -m 0644 /tmp/mbp_petalinux-2017.10.06-10.05.51/work/cortexa9hf-neon-xilinx-linux-gnueabi/external-hdf/1.0-r0/github.com/Xilinx/hdf-examples.git /tmp/mbp_petalinux-2017.10.06-10.05.51/work/cortexa9hf-neon-xilinx-linux-gnueabi/external-hdf/1.0-r0/deploy-external-hdf/Xilinx-plnx_arm.hdf
fi
}

 

So is the build process not putting the file there? I suppose I can circumvent this by copying my system.hdf to that location or modifying the run.do_deploy script

0 Kudos
Highlighted
Moderator
Moderator
1,506 Views
Registered: ‎09-12-2007

Are you using petalinux-config --get-hw-description=<path to hdf>

By default yocto will use the external-hdf if this isn't used
0 Kudos
Highlighted
Explorer
Explorer
1,504 Views
Registered: ‎11-28-2011

For some reason I couldn't do it from outside of the directory where the hdf was located, so I called petalinux-config from the same directory as the hdf

0 Kudos