STM32MP157D-DK1 yocto build problem of scarthgap problem

Marzarsh · ‎2026-05-01

Hi, I'm new to yocto project, I'm trying to bitbake core-image-minimal image in yocto in stm32mp157d-dk1(scarthgap) ,by editing the bblayers.conf and local.conf in image, its successfully build and flashed into SD card , but I'm trying to boot device then it failed. I found in bootfs sector there was no files in it. I tried to build with kirkstone branch and it worked well, and then I tried to bitbake with scarthgap again and again. I used Ubuntu 24.04 and Linux mint 22.03, but scarthgap branch had the same problems.I wanna know the reason. BIG THX.

Marzarsh · ‎2026-05-01

my bblayers file

gol · ‎2026-05-07

I have also built core-image-minimal according to the instructions and without making any changes at all to the default files, and I’m getting exactly the same error as you: no files in boot partition. I’ve tested on both boards 215F-DK and 257F-DK, and flashed using STM32_Programmer_CLI and raw mode. I’ve also tried many different TSV files, but nothing helps. So it seems to be a general issue in the Distribution-Package build environment.
I’d appreciate it if anyone has a suggestion for a solution.

gol · ‎2026-05-07

Here is my boot log:

STM32MP> NOTICE:  CPU: STM32MP215FAN Rev.Z
NOTICE:  Model: STMicroelectronics STM32MP215F-DK Discovery Board
NOTICE:  Board: MB2059 Var1.0 Rev.B-02
NOTICE:  Reset reason: Pin reset from NRST (0x2034)
INFO:    PMIC2 version = 0x12
INFO:    PMIC2 product ID = 0x31
INFO:    FCONF: Reading TB_FW firmware configuration file from: 0xe011000
INFO:    FCONF: Reading firmware configuration information for: stm32mp_io
INFO:    FCONF: Reading firmware configuration information for: stm32mp_fuse
INFO:    Using SDMMC
INFO:      Instance 1
INFO:    Boot used partition fsbl1
NOTICE:  BL2: v2.10-stm32mp2-r2.0(debug):lts-v2.10.24-dirty(a07367a1)
NOTICE:  BL2: Built : 16:16:36, Oct  3 2025
INFO:    BL2: Loading image id 26
INFO:    Loading image id=26 at address 0xe061000
INFO:    Image id=26 loaded: 0xe061000 - 0xe069650
INFO:    BL2: Doing platform setup
INFO:    RAM: LPDDR4 1x16Gbits 1x16bits 800MHz
INFO:    Memory size = 0x80000000 (2048 MB)
INFO:    BL2: Loading image id 1
INFO:    Loading image id=1 at address 0xe000000
INFO:    Image id=1 loaded: 0xe000000 - 0xe000326
INFO:    FCONF: Reading FW_CONFIG firmware configuration file from: 0xe000000
INFO:    FCONF: Reading firmware configuration information for: dyn_cfg
INFO:    FCONF: Reading firmware configuration information for: risaf_config
INFO:    RISAF2: No configuration in DT, use default
INFO:    BL31 max size = 0x17000 (94208B)
INFO:    BL2: Loading image id 3
INFO:    Loading image id=3 at address 0xe000000
INFO:    Image id=3 loaded: 0xe000000 - 0xe015978
INFO:    BL2: Loading image id 19
INFO:    Loading image id=19 at address 0x81fc0000
INFO:    Image id=19 loaded: 0x81fc0000 - 0x81fc330a
INFO:    BL2: Loading image id 4
INFO:    Loading image id=4 at address 0x82000000
INFO:    Image id=4 loaded: 0x82000000 - 0x8200001c
INFO:    OPTEE ep=0x82000000
INFO:    OPTEE header info:
INFO:          magic=0x4554504f
INFO:          version=0x2
INFO:          arch=0x1
INFO:          flags=0x0
INFO:          nb_images=0x1
INFO:    BL2: Loading image id 8
INFO:    Loading image id=8 at address 0x82000000
INFO:    Image id=8 loaded: 0x82000000 - 0x820fa008
INFO:    BL2: Loading image id 2
INFO:    Loading image id=2 at address 0x84400000
INFO:    Image id=2 loaded: 0x84400000 - 0x84416470
INFO:    BL2: Loading image id 5
INFO:    Loading image id=5 at address 0x84000000
INFO:    Image id=5 loaded: 0x84000000 - 0x841b3600
NOTICE:  BL2: Booting BL31
INFO:    Entry point address = 0xe000000
INFO:    SPSR = 0x3cd
INFO:    ARM GICv2 driver initialized
NOTICE:  BL31: v2.10-stm32mp2-r2.0(debug):lts-v2.10.24-dirty(a07367a1)
NOTICE:  BL31: Built : 16:16:36, Oct  3 2025
INFO:    BL31: Initializing runtime services
INFO:    BL31: Initializing BL32
I/TC: Early console on UART#2
I/TC:
I/TC: Embedded DTB found
I/TC: OP-TEE version: 4.0.0-dev (gcc version 13.4.0 (GCC)) #1 Fri Oct 20 18:29:31 UTC 2023 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
I/TC: Primary CPU initializing
I/TC: WARNING: All debug access are allowed
I/TC: Override the OTP 124: 0 to 0x8db6
I/TC: WARNING: Embeds insecure stm32mp_provisioning driver
I/TC: PMIC STPMIC REFID:3.A V1.2
I/TC: Platform stm32mp2: flavor PLATFORM_FLAVOR - DT stm32mp215f-dk.dts
I/TC: OP-TEE ST profile: secure_and_system_services
I/TC: DBGMCU Authenticated Debug Mailbox online
[    0.000000] SCP-firmware 2.13.0-intree-optee-os-4.0.0-dev
[    0.000000]
[    0.000000] [FWK] Module initialization complete!
I/TC: Primary CPU switching to normal world boot
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x84000000
INFO:    SPSR = 0x3c9
I/TC: Reserved shared memory is disabled
I/TC: Dynamic shared memory is enabled
I/TC: Normal World virtualization support is disabled
I/TC: Asynchronous notifications are enabled


U-Boot 2023.10-stm32mp-r3 (Oct 02 2023 - 14:39:59 +0000)

CPU: STM32MP215FAN Rev.Z
Model: STMicroelectronics STM32MP215F-DK Discovery Board
Board: stm32mp2 (st,stm32mp215f-dk)
Board: MB2059 Var1.0 Rev.B-02
DRAM:  2 GiB
optee optee: OP-TEE: revision 4.0 (2a5b1d12)
I/TC: Reserved shared memory is disabled
I/TC: Dynamic shared memory is enabled
I/TC: Normal World virtualization support is disabled
I/TC: Asynchronous notifications are enabled
Core:  322 devices, 37 uclasses, devicetree: board
WDT:   Started watchdog with servicing every 1000ms (32s timeout)
NAND:  0 MiB
MMC:   STM32 SD/MMC: 0
Loading Environment from MMC... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: eth1@482c0000
No EFI system partition
No EFI system partition
Failed to persist EFI variables
Hit any key to stop autoboot:  0
Boot over mmc0!
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:8...
BootOrder not defined
EFI boot manager: Cannot load any image
STM32MP> ext4ls mmc 0:8 /
<DIR>       1024 .
<DIR>       1024 ..
<DIR>      12288 lost+found
STM32MP>

Marzarsh · ‎2026-05-07

Use kirkstone branch will solve this problem but it is not newest branch.

gol · ‎2026-05-07

@Marzarsh Thanks for the tip. But by using the boot image file from the starter package I’ve now managed to boot. It would still be nice to know how to officially get Bitbake to generate the boot image file for the core-image-minimal..

Marzarsh · ‎2026-05-07

I also wanna konw that. The reason is the building file "bootfs.ext4" has nothing in it with scarthgap branch. I tried mount it with loop command then found it showed "lost+found" in it. Nothing else. The kirkstone is also from "meta-st" official github. It is just an old version.