Showing results for 
Search instead for 
Did you mean: 

Boot failure of image built using copied distro, machine, image recipe from ST's meta.


I have a custom board based on stm32mp157f-ev1 and stm32mp157f-dk2 board.

In my custom layer:

  • meta-st/meta-st-openstlinux/conf/distro/* copied and a new distro created based openstlinux-weston.conf
  • meta-st/meta-st-stm32mp/conf/machine/* copied and a new machine created based stm32mp15-eval.conf
  • a new image recipe created based meta-st/meta-st-openstlinux/recipes-st/images/

linux-stm32mp, u-boot-stm32mp, tf-a-stm32mp DTS files tuned using openembedded devtool.

Image built using:

$ DISTRO=mydistro MACHINE=mymachine META_LAYER_ROOT=layers/mylayer layers/meta-st/scripts/

bitbake-layers add-layer ../layers/mylayer

$ bitbake myimage

Flashed on sdcard and try to boot, but stucked after RAMDISK error message:

[    2.714949] hub 2-0:1.0: USB hub found

[    2.717446] hub 2-0:1.0: 2 ports detected

[    2.726168] RAMDISK: Couldn't find valid RAM disk image starting at 0.

[    2.731801] Waiting for root device PARTUUID=491f6117-415d-4f53-88c9-6e0de54deac6...

[    3.007728] usb 2-1: new high-speed USB device number 2 using ehci-platform

[    3.210055] hub 2-1:1.0: USB hub found

[    3.212707] hub 2-1:1.0: 4 ports detected

[    3.537716] usb 2-1.1: new high-speed USB device number 3 using ehci-platform

Any tunning required after copying ST meta ?

Best Regards,

YoungSuk Kim

ST Employee

Hello @bandifly ,
I just would like to target the right problem location. Can you please tell me if updating components in a standalone way (with Developer Package and SDK) give you the same bad status ? 

We need to identify if you are facing a Yocto issue or a SW component modification issue.

Kind regards,

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.