Error: Unable to get core ID. Error: ST-LINK error (DEV_TARGET CMD ERROR)

[yangtom0516]

Hi,

I’m working with an STM32MP157D-DK1 board and attempting to connect to it using STM32CubeProgrammer. The board is powered properly (measured voltage: 3.23V) and ST-LINK is recognized by the software.

However, the debugger is unable to detect the Cortex-M4 core. I suspect the issue is that Linux is still holding the M4 core in reset, preventing the debug probe from halting or accessing it.

Does that sound like a reasonable cause? If so, could you please advise on the correct steps to release the M4 from reset and enable debugging access?

For context, I’ve already tried multiple combinations of ST-LINK connection settings (mode, reset mode, frequency), but none were successful.

Thank you for your help!

[Olivier GALLIEN]

Hi @yangtom0516 

Accessing M4 with STLINK through CubeProgrammer is not supported on STM32MPx product

You can program the OpenSTLinux using USB port. 

STLINK can be used for debugging with STM32CubeIDE. 

Refer to our wiki  to get Start with you DK board: 

STM32MP157x-DK2 - stm32mpu 

Olivier