Added Custom Board from CubeMx, but an error occour

[Niklas Voi]

Hi St-Community,

im hanging around with the following Problem:

I build up a yocto environment and build sucessfully images. No its time to add a custom devicetree to the linux.

So i followed the instructions on:

https://wiki.st.com/stm32mpu/wiki/How_to_create_your_own_machine

But i get the following error when i start to build a image with bitbake image-base-minimal.

ERROR: u-boot-stm32mp-extlinux-2.0-r0 do_create_multiextlinux_config: No UBOOT_EXTLINUX_CONFIG_FLAGS list defined, nothing to do
ERROR: u-boot-stm32mp-extlinux-2.0-r0 do_create_multiextlinux_config: Function failed: update_extlinuxconf_targets
ERROR: Logfile of failure stored in: /opt/build/tmp/work/stm32mp1_mustera-poky-linux-gnueabi/u-boot-stm32mp-extlinux/2.0-r0/temp/log.do_create_multiextlinux_config.5058
ERROR: Task (/opt/yocto/meta-st-stm32mp/recipes-bsp/u-boot/u-boot-stm32mp-extlinux.bb:do_create_multiextlinux_config) failed with exit code '1'

Have you any hints to me where i can debug. I dont know wehere these variables are defined.

Best regards and many thanks

Niklas

[Olivier GALLIEN]

Hi @Niklas Voi​ 

There is no recipe image-base-minimal, do you mean st-image-core or core-image-minimal ?

May you share your stm32mp1-<ProjectName>.conf for further help ?

Thanks

Olivier

[Niklas Voi]

Hi Oliver,

here is my machine:

#@TYPE: Machine
#@NAME: stm32mp1-mustera
#@DESCRIPTION: Configuration for STM32CubeMX generated project
#@NEEDED_BSPLAYERS: layers/meta-openembedded/meta-oe layers/meta-openembedded/meta-python
 
include conf/machine/include/st-machine-common-stm32mp.inc
include conf/machine/include/stm32mp1-mx-config.inc
include conf/machine/include/stm32mp1-mx-extlinux-config.inc
include conf/machine/include/stm32mp1-mx-common.inc
 
# =========================================================================
# CubeMX extra config
# =========================================================================
# Set specific path by components for DT file location
CUBEMX_DTB_PATH_TFA = "${STM32MP_MX_BASE}/mx/${CUBEMX_PROJECT}/tf-a"
CUBEMX_DTB_PATH_UBOOT = "${STM32MP_MX_BASE}/mx/${CUBEMX_PROJECT}/u-boot"
CUBEMX_DTB_PATH_LINUX = "${STM32MP_MX_BASE}/mx/${CUBEMX_PROJECT}/kernel"
CUBEMX_DTB_PATH_OPTEEOS = "${STM32MP_MX_BASE}/mx/${CUBEMX_PROJECT}/optee-os"
 
# =========================================================================
# User customizing sections
# =========================================================================
 
# Boot Scheme
# =========================================================================
# DISCO / EVAL : basic, trusted or optee
# =========================================================================
#BOOTSCHEME_LABELS += "basic"
BOOTSCHEME_LABELS += "trusted"
#BOOTSCHEME_LABELS += "optee"
 
# Boot Device Choice
# =========================================================================
# DISCO : sdcard
# EVAL : sdcard, emmc, nand-4-256, nor-sdcard, nor-emmc or nor-nand-4-256
# =========================================================================
# Define the boot device supported
BOOTDEVICE_LABELS += "sdcard"
 
# WARNING: configs below are only available with EVAL board
#BOOTDEVICE_LABELS += "emmc"
#BOOTDEVICE_LABELS += "nand-4-256"
#BOOTDEVICE_LABELS += "nor-emmc"
#BOOTDEVICE_LABELS += "nor-nand-4-256"
#BOOTDEVICE_LABELS += "nor-sdcard"
 
# Board Type Choice
# =========================================================================
# DISCO : stm32mp157a-dk1 or stm32mp157c-dk2
# EVAL : stm32mp157c-ev1
# =========================================================================
# Define the board reference devicetree name
# WARNING: only one setting allowed
#CUBEMX_BOARD_REFERENCE = "stm32mp157a-dk1"
CUBEMX_BOARD_REFERENCE = "stm32mp157c-dk2"
#CUBEMX_BOARD_REFERENCE = "stm32mp157c-ev1"
 
# CubeMX Project Config
# =========================================================================
# Assign CubeMX Board devicetree and project path name
CUBEMX_DTB = "stm32mp157c-cube-project-for-muster-a-mx"
CUBEMX_PROJECT = "MusterA"

I mean core-image-minimal to build. I have started with a blank yocto and than added the layers:

/opt/yocto/
├── clean_repos.sh
├── meta-openembedded
├── meta-squirrel # Here is our company stuff, so ignore this
├── meta-st-stm32mp
├── meta-st-stm32mp-addons
└── poky

Builduing for the DK2 works fine.

Thanks for your help :)

Niklas