2019-06-21 05:37 AM
Hi,
I get an error when trying to program nucleo board with the STM32H743 and STMCubeIDE with any of the example projects. They compile OK but I get an error while programming the board.
It works with IAR,
the error message is
STMicroelectronics ST-LINK GDB server. Version 5.2.3
Copyright (c) 2019, STMicroelectronics. All rights reserved.
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\smith\AppData\Local\Temp\STM32CubeProgrammer_a01452.log
ST-LINK SN : 0672FF383930434B43184445
ST-LINK FW : V2J31M21
Voltage : 3.24V
SWD freq : 4000 KHz
Connect mode: Under Reset
Reset mode : Hardware reset
Device ID : 0x450
Device name : STM32H7xx
Flash size : 2 MBytes
Device type : MCU
Device CPU : Cortex-M7
Memory Programming ...
Opening and parsing file: ST-LINK_GDB_server_a01452.srec
File : ST-LINK_GDB_server_a01452.srec
Size : 136080 Bytes
Address : 0x08000000
Erasing memory corresponding to segment 0:
Erasing internal memory sectors [0 1]
Download in Progress:
File download complete
Time elapsed during download operation: 00:00:03.253
Verifying ...
Download verified successfully
Target unknown error 19
Error in initializing ST-LINK device.
Reason: Unknown. Please check power and cabling to target.
Failed to restart ST-LINK connection
Error in STM32CubeProgrammer
Target is not responding, retrying...
2019-06-25 01:58 AM
Could you enable to gdbserver log and paste it? It's located in the Debugger tab of the debug configuration, a box at "Log to file:".
2019-06-26 02:17 AM
2019-06-26 08:12 AM
This looks a bit strange. The error seems to get generated as soon as CubeProgrammers flash has been completed.
If you first start a debug session as usual (or try to) and then after the first time where it supposedly flashed OK you go into your debug configuration and then into your "Startup" tab and uncheck the "Load image" box and hit "Debug". Can you start a debug session then?
Also, what happens if you choose OpenOCD as the debug probe? (In the Debugger tab)
2019-06-27 02:56 AM
OpenOCD did not work
Unchecking "Load Image" it starts a debug session OK.