stm32mp135 boot stuck

[sangjulee]

NOTICE: CPU: STM32MP135F Rev.Y
NOTICE: Model: STMicroelectronics STM32MP135F-DK STM32CubeMX board - openstlinux-6.1-yocto-mickledore-mp1-v23.06.21
NOTICE: BL2: v2.8-stm32mp1-r1.0(release):custom()
NOTICE: BL2: Built : 15:38:01, Jul 2 2025
NOTICE: BL2: Booting BL32
I/TC: Early console on UART#4
I/TC:
I/TC: Embedded DTB found
I/TC: OP-TEE version: Unknown_3.19 (gcc version 12.2.0 (Buildroot 2021.11-4428-g6b6741b)) #1 Wed Jul 2 06:15:25 UTC 2025 arm
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: Platform stm32mp1: flavor PLATFORM_FLAVOR - DT stm32mp135f-dk-mx.dts
I/TC: DTB enables console (non-secure)
▒_▒▒z`@`@▒▒ÿ▒▒▒▒▒▒▒▒▒▒▒zc`x@▒▒▒]▒▒▒▒▒▒▒▒▒▒▒@▒▒▒▒@▒▒▒@▒▒@▒▒▒▒▒z@xeeyybcb@\@▒▒▒▒@bac▒_▒▒z`@`@▒▒ÿ▒▒▒▒▒▒▒▒▒▒▒zc`x@▒▒▒]▒▒▒▒▒▒▒▒▒▒▒@▒▒▒▒@▒▒▒@▒▒@▒▒▒▒▒z@efdga`d@\@▒▒▒▒@a`c▒_▒▒z@▒▒▒▒▒▒▒@▒▒▒@▒▒▒▒▒▒▒▒▒@▒▒@▒▒▒▒▒▒@▒▒▒▒▒@▒▒▒▒▒▒▒▒▒@▒▒▒▒▒z@▒▒]▒▒▒z@▒▒▒▒▒▒▒▒@c^ay▒▒ۿ▒▒▒▒▒▒▒▒z@▒▒▒▒▒▒@▒▒@▒▒▒@▒ۿ▒▒▒߿dx▒@▒▒▒▒▒▒@X▒▒▒▒▒▒@▒▒@▒▒▒߿▒Y▒]▒▒▒▒@b`bb^a`]▒▒▒cb▒▒]▒a^a@X▒▒▒@`b@b`be@]@aezcxz``@[`y``Y▒▒▒z@▒▒▒cb▒▒ace▒@▒▒▒^▒▒▒▒▒▒z@▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒@▒▒▒cb▒▒ace▒]▒▒@▒▒▒cb▒▒▒ŝ▒@▒▒▒▒▒@]@▒▒▒▒▒▒▒▒▒▒▒]f^a]▒▒▒▒▒]▒▒▒▒▒▒▒▒▒▒]▒▒a]▒bc^`f^ba▒▒▒▒▒z@▒▒▒cb▒▒a@▒▒@▒▒▒▒▒▒▒@▒▒▒▒@X▒▒\▒▒▒cb▒▒ace▒]▒▒]▒▒Y▒▒▒▒z@@eab@▒ق▒▒▒▒▒@▒▒▒▒▒z@▒▒]▒▒▒z@▒▒▒▒▒▒▒▒@c^ay▒▒ۿ▒▒▒▒▒▒▒▒z@▒▒▒▒▒▒@▒▒@▒▒▒@▒ۿ▒▒▒߿dx▒@▒▒▒▒▒▒@X▒▒▒▒▒▒@▒▒@▒▒▒߿▒Y▒▒▒▒▒▒z]@▒▒▒@z@a```@▒▒▒]@▒▒▒@z@bff^e``@▒▒▒]@▒▒▒@z@bd@▒▒▒]@▒▒▒@z@ecc@▒▒▒▒▒▒▒z@@afc@▒▒▒▒▒▒▒\@be@▒▒▒▒▒▒▒▒\@▒▒▒▒▒▒▒▒▒▒z@▒▒▒▒▒▒▒▒z@@@▒▒▒▒▒▒▒@▒▒▒▒▒▒▒▒@▒▒▒▒@▒▒▒▒▒▒▒▒▒@Xcb▒@▒▒▒▒▒▒▒Y▒▒▒▒z@@`@▒ق▒▒▒z@@@▒▒▒cb@▒▒_▒▒▒z@`▒▒▒▒▒▒▒@▒▒▒▒▒▒▒▒▒▒▒@▒▒▒▒@▒▒▒^^^@▒▒▒▒z@@@@▒▒▒▒▒▒▒▒▒z@@@▒▒▒▒▒▒▒▒▒z@@@▒▒▒▒▒▒▒▒▒▒▒▒▒@▒▒▒@▒▒▒▒▒▒▒@`@▒▒@▒▒▒@``z``z``z``z``z``▒▒▒G▒@▒▒▒@▒▒▒@▒▒▒▒▒▒X]ayY▒▒▒z@@@▒▒@▒▒▒▒▒▒▒▒@▒▒▒▒▒^▒▒▒@▒▒▒@▒▒▒@▒▒@▒▒▒▒@▒▒▒▒▒▒▒▒z@@a@@`▒▒▒cb▒▒~@

What is the problem? At first, data comes out of the serial, but then breaks in the middle. How do I fix this?

[PatrickF]

Hi @sangjulee 

this sound like a UART baud rate issue (issue on root clock frequencies).

At that time there is maybe optee reprogramming clocks differently than the one done by TF-A without re-init UARTs (that's my assumption, but I'm not expert on this).

You should check Device Tree consistencies in between all modules (tf-a, optee-os, u-boot and kernel) as any differences on same node declaration might create strange behavior.

Are you using a STM32MP135F-DK  board with custom SW ? Does it work with Starter Package ?

Maybe have a look to https://wiki.st.com/stm32mpu/wiki/How_to_compile_the_device_tree_with_the_Developer_Package 

Regards.