Fail to debug Nucleo STM32F429ZI

Cedric Boudinet · ‎2020-07-09

Hi I cannot connect to my Nucleo STM32F429ZI using STM32CubeIDE, the error message is:

STMicroelectronics ST-LINK GDB server. Version 5.2.3

Starting server with the following options:

Persistent Mode : Disabled

Logging Level : 1

Listen Port Number : 61234

Status Refresh Delay : 15s

Verbose Mode : Disabled

SWD Debug : Enabled

Waiting for debugger connection...

Debugger connected

-------------------------------------------------------------------

STM32CubeProgrammer v2.1.0

-------------------------------------------------------------------

Log output file: C:\Users\boubou\AppData\Local\Temp\STM32CubeProgrammer_a01060.log

ST-LINK SN : 0666FF343135485043172431

ST-LINK FW : V2J31M21

Voltage : 3.24V

SWD freq : 4000 KHz

Connect mode: Under Reset

Reset mode : Hardware reset

Device ID : 0x419

Device name : STM32F42xxx/F43xxx

Flash size : 63.999 MBytes

Device type : MCU

Device CPU : Cortex-M4

Memory Programming ...

Opening and parsing file: ST-LINK_GDB_server_a01060.srec

File : ST-LINK_GDB_server_a01060.srec

Size : 33940 Bytes

Address : 0x08000000

Erasing memory corresponding to segment 0:

Erasing internal memory sectors [0 2]

Error: failed to erase memory

Encountered Error when opening C:\ST\STM32CubeIDE_1.0.1\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_1.0.0.201904021149\tools\bin\STM32_Programmer_CLI.exe

Error in STM32CubeProgrammer

Error! Failed to read target status

Debugger connection lost.

Shutting down...

Does anybody has an idea about what is wrong ?

waclawek.jan · ‎2020-07-09

And can you find that exefile at given location?

JW

Pavel A. · ‎2020-07-09

IIRC this error occurs if you import a project from other computer where CubeIDE (or other Eclipse) is installed in different path.

The path is captured in the debug configuration and the IDE is not smart enough to fix it.

Try to delete the debug config and create new.

-- pa

Cedric Boudinet · ‎2020-07-22

Hello, thanks for your answers.

I don't think it comes from the exe file because it works with another card.

I tried directly to connect with the CLI. With the card that is working, the result is:

C:\ST\STM32CubeIDE_1.0.1\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_1.0.0.201904021149\tools\bin>STM32_Programmer_CLI.exe -c port=swd

-------------------------------------------------------------------

STM32CubeProgrammer v2.1.0

-------------------------------------------------------------------

ST-LINK SN : 066AFF363336485043072516

ST-LINK FW : V2J31M21

Voltage : 3.22V

SWD freq : 4000 KHz

Connect mode: Normal

Reset mode : Software reset

Device ID : 0x419

Device name : STM32F42xxx/F43xxx

Flash size : 2 MBytes

Device type : MCU

Device CPU : Cortex-M4

With the card that is not working, the result is:

C:\ST\STM32CubeIDE_1.0.1\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_1.0.0.201904021149\tools\bin>STM32_Programmer_CLI.exe -c port=swd

-------------------------------------------------------------------

STM32CubeProgrammer v2.1.0

-------------------------------------------------------------------

ST-LINK SN : 0666FF343135485043172431

ST-LINK FW : V2J31M21

Voltage : 3.23V

SWD freq : 4000 KHz

Connect mode: Normal

Reset mode : Software reset

Device ID : 0x419

Device name : STM32F42xxx/F43xxx

Flash size : 63.999 MBytes

Device type : MCU

Device CPU : Cortex-M4

=> the CLI says my STM32F429ZI has 64 MBytes flash! I am not sure it can be a software issue.

Do you think MCU is damaged?

Cedric