cancel
Showing results for 
Search instead for 
Did you mean: 

Yocto busybox post install failure

nielsenni101
Associate

I am creating a custom yocto image on a STM32MP157F-DK2. I am using the meta-stm32mp layer as apart of the bitbake build. 

Yocto version : Scarthgap

 

When I run bitbake I get this failure 

 

ERROR: hydra-image-1.0-r0 do_rootfs: Postinstall scriptlets of ['busybox'] have failed. If the intention is to defer them to first boot,
then please place them into pkg_postinst_ontarget:${PN} ().
Deferring to first boot via 'exit 1' is no longer supported.
Details of the failure are in /home/hydra/yocto/build/tmp/work/stm32mp1_brady-hydra-linux-gnueabi/hydra-image/1.0/temp/log.do_rootfs.
ERROR: Logfile of failure stored in: /home/hydra/yocto/build/tmp/work/stm32mp1_brady-hydra-linux-gnueabi/hydra-image/1.0/temp/log.do_rootfs.661419
ERROR: Task (/home/hydra/yocto/layers/poky/../meta-brady/recipes-core/images/hydra-image.bb:do_rootfs) failed with exit code '1'

 

Log file  

 

update-alternatives: Linking /home/hydra/yocto/build/tmp/work/stm32mp1_brady-hydra-linux-gnueabi/hydra-image/1.0/rootfs/usr/sbin/sysctl to /usr/bin/busybox.nosuid
update-alternatives: Linking /home/hydra/yocto/build/tmp/work/stm32mp1_brady-hydra-linux-gnueabi/hydra-image/1.0/rootfs/usr/sbin/udhcpc to /usr/bin/busybox.nosuid
update-alternatives: Error: not linking /home/hydra/yocto/build/tmp/work/stm32mp1_brady-hydra-linux-gnueabi/hydra-image/1.0/rootfs/usr/sbin/watchdog to /usr/bin/busybox.nosuid since /home/hydra/yocto/build/tmp/work/stm32mp1_brady-hydra-linux-gnueabi/hydra-image/1.0/rootfs/usr/sbin/watchdog exists and is not a link
update-alternatives: Linking /home/hydra/yocto/build/tmp/work/stm32mp1_brady-hydra-linux-gnueabi/hydra-image/1.0/rootfs/usr/sbin/klogd to /usr/bin/busybox.nosuid
update-alternatives: Linking /home/hydra/yocto/build/tmp/work/stm32mp1_brady-hydra-linux-gnueabi/hydra-image/1.0/rootfs/usr/sbin/syslogd to /usr/bin/busybox.nosuid

 

 

I do not understand why I am getting this error. If I append the busybox recipe in my custom layer and set the CONFIG_WATCHDOG variable to 'n' then the image with build with no failure and boot on the board. I am assuming that some other layer is creating this .../user/sbin/watchdog directory, but I have been unsuccessful in finding that.

Any help would be appreciated, thanks.

1 REPLY 1
Olivier GALLIEN
ST Employee

Hi @nielsenni101 ,

 

Seems you are using Scarthgap wich is not yet supported by ST delivery.  ( plan in next DV6 by end of year)

For time being we recommend to stick on Mickledore DV5.1 delivery.

 

Olivier 

Olivier GALLIEN
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.