cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to flash Nucleo-H563ZI with STM32CubeIDE V1.14

Nikita91
Lead II

I wanted to use a Nucleo-H563ZI but I can’t program it:

STMicroelectronics ST-LINK GDB server. Version 7.5.0
Copyright (c) 2023, 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
        InitWhile                  : Enabled

Waiting for debugger connection...
Debugger connected
Waiting for debugger connection...
Shutting down...
Exit.



Error in final launch sequence:

Failed to execute MI command:
target remote localhost:61234

Error message from debugger back end:
localhost:61234: Connection timed out.
Failed to execute MI command:
target remote localhost:61234

Error message from debugger back end:
localhost:61234: Connection timed out.
localhost:61234: Connection timed out.

STLINK firmware version: V3J13M4

But with STM32CubeProgrammer it works. So it seems to me that the board and the STLINK are in working order.

After several tests with my application, I made a cleaning:

  • Uninstall STM32CubeProgrammer and STM32CubeIDE
  • Install STM32CubeIDE 1.14
  • Install STM32CubeProgrammer 2.15
  • Create a new workspace
  • Import a simple example of the H5 package: GPIO_IOToggle

Compilation OK, but flash download impossible.

But STM32CubeProgrammer  works and the LEDs blinks.

 

I also have a Nucleo-H723 board with a STLINK V3 (but seems to be a different version than that of the H563 board) => Doesn't work either (With the same version of STLINK firmware: V3J13M4)

But download and debug work on the H723 board with TrueSTUDIO. So the board works.

 

What's stopping me from using these boards with STM32CubeIDE?

 

10 REPLIES 10
Nikita91
Lead II

Hello,

Attached are the gdbserver log I get. This log makes me think that the drivers are installed and working, at least a little.

To get this log I used a Nucleo board as STLINK bridge.

I get exactly the same trace wit a STLINK_V3MODS.

The connection fails (accept after timeout!):

[0.186] WaitConnection():  Waiting for connection on port 61234...
[0.193] WaitConnection():  Waiting for connection on port 61235...
[18.327] WaitConnection():  Accepted connection on port 61234...
[18.329] WaitConnection():  Waiting for connection on port 61234...