A/B partitions using scarthgap on stm32mp25

[BGurnett]

We have a custom stm32mp25 board. On Mickledore we were able to create a/b partitions in our machine conf doing the following:

PARTITIONS_IMAGES += "tc-appfs-a tc-appfs-b"

STM32MP_TCFS_IMAGE ?= "ti-tc-appfs"
STM32MP_TCFS_LABEL_A ?= "tc-appfs-a"
STM32MP_TCFS_LABEL_B ?= "tc-appfs-b"
STM32MP_TCFS_MOUNTPOINT ?= "/tc-apps"
# Proposed value for tc-appfs is 150MB
STM32MP_TCFS_SIZE ?= "153600"



PARTITIONS_IMAGES[tc-appfs-a] ?= "${STM32MP_TCFS_IMAGE},${STM32MP_TCFS_LABEL_A},${STM32MP_TCFS_MOUNTPOINT},${STM32MP_TCFS_SIZE},FileSystem"

PARTITIONS_IMAGES[tc-appfs-b] ?= "${STM32MP_TCFS_IMAGE},${STM32MP_TCFS_LABEL_B},${STM32MP_TCFS_MOUNTPOINT},${STM32MP_TCFS_SIZE},FileSystem"



PARTITIONS_LIST += "tc-appfs-a tc-appfs-b"

However, in scarthgap this no longer works. We are getting the following error:

Cannot generate FlashLayout_emmc_stm32mp257f-m670-optee.tsv file: the ti-tc-appfs-ti-linux-stm32mp25-m670.tc-appfs-a.ext4 binary for tc-appfs-a partition is missing in deploy folder.

What we observe is that the relevant file is being renamed as

ti-tc-appfs-ti-linux-stm32mp25-m670.tc-appfs-bfs.ext4

Is this a bug, or do we need to proceed in a different way when using scarthgap.

Thanks

P.S I have seen mentioned an meta-st-ota layer on the board. I have, however, been unable to find it. So if someone could point out it's location I would be grateful.

[Christophe Guibout]

Hello @BGurnett,

As mentionned in my previous previous message, I would recommand to check why altbootcmd is not called in u-boot.
BR,

Christophe