Cortex M33 not detecting in STM32MP257F-DK using ST-link

partha_sarathi1000 · ‎2025-04-22

Hi

I am trying to program the Cortex M33 of STM32MP257F-DK dev board using CubeIDE. I have generated the code in Cube IDE. The debugger failing to program as the board not responding.

Following are my debug settings:

Again I tried using STM32 Cube Programmer, no luck.

But its able to detect Cortex A35 using USB DFU mode and able to flash Linux into sd card.

But the MCU is unable to detect.

I tried boot settings in Development Mode 0011. Also tried 0001 and 0000. Same issue.

Can anybody let me know where I am going wrong?

partha_sarathi1000 · ‎2025-04-24

@Olivier GALLIEN

I solved the problem by changing the Debug name from OpenAMP_TTY_echo_CM33_NonSecure CA35TDCID_m33_ns_sign_Run to OpenAMP_TTY_echo_CM33_NonSecure CA35TDCID_m33_ns_sign_Debug.

Wasn't aware of the fact that _Debug naming convention matters in the script.

Thanks.

View solution in original post

Olivier GALLIEN · ‎2025-04-23

Hi @partha_sarathi1000 ,

It's not possible to debug the CM33 of STM32MP25 in standalone mode using the "development boot" mode. (engineering mode in CubeIDE)

It's mandatory to use the "production mode" (flash boot mode) where OpenSTLinux running on CA35 setup the system.

STM32CubeIDE has a complete and seamless integration of "production mode" allowing a satisfactory debug experience of the CM33 with low constraint vs CM33 standalone.

See our Wiki for reference :

Develop on Arm® Cortex®-M33 - stm32mpu

Olivier

Olivier GALLIEN
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.

partha_sarathi1000 · ‎2025-04-24

Thanks @Olivier GALLIEN
Can it be done in Windows, or Linux environment is mandatory, as per as CM33 development is concerned.

Olivier GALLIEN · ‎2025-04-24

Hi @partha_sarathi1000 ,

It can be done in Windows

Olivier

Olivier GALLIEN
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.

partha_sarathi1000 · ‎2025-04-24

@Olivier GALLIEN

I followed all the steps in the development guide, it build successfully on my Windows PC, and st-link debugger able to attach. But its not coming to main. It stuck in infinite loop on startup.

Following are my Run configuration:

Even the MPU console is fine:

The boot config is 0001.

What I am doing wrong?

partha_sarathi1000 · ‎2025-04-24

@Olivier GALLIEN

I solved the problem by changing the Debug name from OpenAMP_TTY_echo_CM33_NonSecure CA35TDCID_m33_ns_sign_Run to OpenAMP_TTY_echo_CM33_NonSecure CA35TDCID_m33_ns_sign_Debug.

Wasn't aware of the fact that _Debug naming convention matters in the script.

Thanks.