pmic panic & can't generate dts for stm32mp135f custom board

[lisa3]

Hi, I have made a custom board with stm32mp135f and I have encountered some problems:
1. It seems like the stm32cubemx software is not generating .dts file when generating code, and I don't know the syntax for editing the stm32mp135f-dk dts file.
2. I looked at the reference tutorial: bootlin embeded-linux-labs, and tried to follow their tutorial but for stm32mp135f-dk evb board but got stuck on:
"We can now generate the bl32, dtb, and fip targets with a single command line:
$ make ARM_ARCH_MAJOR=7 ARCH=aarch32 PLAT=stm32mp1 AARCH32_SP=sp_min \
DTB_FILE_NAME=stm32mp157a-dk1.dtb BL33=../u-boot/u-boot-nodtb.bin \
BL33_CFG=../u-boot/u-boot.dtb STM32MP_SDMMC=1 fip all"

I tried to change some things that it will work on for stm32mp135f-dk but i got :
Makefile:1702: *** "Platform 'stm32mp1' requires BL32. Please set BL32 to point to the right file". Stop.

3. When I tried to boot up with yocto linux project i got "error: i2c device not ready" in the pmic check stage because there isn't a pmic in my board.

Can you help me in the bring up of my board?

[GatienC]

Hello,

I deduce you're compiling TF-A.

First of all, sp_min was never supported on stm32mp13x platforms, only stm32mp15x.

Then, in your command line, you're compiling a stm32mp157a-dk1 board, that does not relate to your stm32mp13x board?

On what version of Open ST Linux (OSTL) are you working, if you're working with OSTL? sp_min version is not supported since OSTLV5.x but may still be without any certainty with upstream code.

Do you have a reason not to include OP-TEE in your bootchain?

Please clarify your setup and what you're trying to achieve.

Regards,

Gatien