Hi ST Team,
1. I have followed the steps mentioned in link to build the yocto for stm32mp25-eval machine and can successfully flash the eMMC tsv file .
2. Started to explore on creating a custom machine configuration file and custom layer in the yocto( openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06 distribution package.),and build the package using the steps mentioned below.
CUSTOM LAYER AND MACHINE CREATION STEPS
==========================================
1) I have created a layer outside meta-st , because I wanted to create a custom layer without disturbing the actual openst yocto layers
i) bitbake-layers create-layer layers/<custom_layer_name>
ii) bitbake-layers add-layer layers/<custom_layer_name>
iii) mkdir conf/machine
iv) cp layers/meta-st/meta-st-stm32mp/conf/machine/stm32mp25-eval.conf nameof_custom_machine.conf
v) DISTRO=openstlinux-weston MACHINE=nameof_custom_machine source layers/meta-st/scripts/envsetup.sh
vi) Due to layer dependency issue , added the dependent layer in bblayers.conf as highlighted below.
# add BSP layer
BBLAYERS += " \
${BASELAYERS} \
${BSPLAYER} \
${ADDONSLAYERS} \
${FRAMEWORKLAYERS} \
${@'${OPENEMBEDDED}' \
if \
os.path.isfile('${OEROOT}/layers/openembedded-core/meta/conf/layer.conf') else '${POKY}'} \
/home/<path>/openst_yocto_bsp/layers/meta-st/<layer-name> \
"
# BSP dependencies
BBLAYERS =+ "/home/<path>/openst_yocto_bsp/layers/meta-openembedded/meta-oe"
BBLAYERS =+ "/home/<path>/openst_yocto_bsp/layers/meta-openembedded/meta-python"
BBLAYERS =+ "/home/<path>/openst_yocto_bsp/layers/meta-st/meta-st-stm32mp-addons"
vii) bitbake st-image-weston
2.Once build,Flashed the generated eMMC tsv file with the below command.
$ ~/projects/STM_APPLICATION/STM32CubeProgrammer/bin/STM32_Programmer_CLI -c port=usb1 -w ./flashlayout_st-image-weston/optee/FlashLayout_emmc_stm32mp257f-ev1-optee.tsv
3. After booting ,could see the error log saying
E/TC:0 0 Panic at /usr/src/debug/optee-os-stm32mp/4.0.0-stm32mp-r1/core/drivers/clk/clk-stm32mp25.c:1976 <clk_stm32_pll_init>
Attached the complete error log for reference.
Kindly check and suggest the steps to resolve the issue.
