2023-12-11 06:21 AM
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:
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?
2023-12-11 07:08 AM
Hello Nikita,
I'm not sure this is your problem, but the STM32H5 needs to communicate via Access Port 1, make sure this is correct in the Run/Debug settings.
It is a common misconfiguration when using H5.
The STM32CubeProgrammer switches automatically to Access Port 1, but I'm not sure for STM32CubeIDE.
For the H723 board, I have no clue.
2023-12-11 07:51 AM
Yes the IDE selected the access port 1:
It's the only choice.
2023-12-12 08:13 AM
Hello @Nikita91 ,
Could you, please, connect the target and try to:
- Erase the Flash memory using STM32Cubeprogrammer
- Disconnect the target from STM32CubeProgrammer
- Start the GDB server, preferably using a different port number
- Debug the program using ST-LINK_gdbserver
Thanks,
Rim
2023-12-12 10:30 AM
Hello,
I spent my day testing on 2 Windows 10 systems:
On the 1st I was able to have a few debug sessions by applying a sequence close to yours:
=> works 1 time out of 3
On this system I just tried your sequence by changing the GDB port number each time
=> about the same thing: 1 time out of 3
On the second system I was never able to launch a debug session.
2023-12-12 10:43 AM
It seems like you are encountering issues with programming the Nucleo-H563ZI and Nucleo-H723 boards using STM32CubeIDE. The error messages indicate a connection timeout problem with the ST-LINK GDB server. Here are some steps you can take to troubleshoot and resolve the issue:
Check Connection:
Restart STM32CubeIDE:
Check ST-LINK Firmware:
Update STM32CubeIDE:
Check Debug Configurations:
Reinstall Drivers:
Check Firewall and Antivirus:
Verify USB Port:
Check Board Jumpers:
Check ST-LINK Connection:
Alternative IDE:
STMicroelectronics Support:
Remember to document any error messages or specific details you encounter during the troubleshooting process, as these can be helpful in identifying the root cause of the problem.
2023-12-13 02:09 AM
Thanks for your advices.
As I already said, the physical connection is good, as well as the USB port since everything works with CubeProgrammer.
As already said, the Nucleo's IDE and firmware are at the latest version and they have been re-installed recently.
As for using an alternative IDE, I have so far been using TrueSTUDIO with some adjustments to use recent MCUs and updated GCC. But with the H5 using DP 1 instead of DP 0 for debugging, I don't know how to do it yet.
So I have to manage to have a working STM32CubeIDE, which doesn't seem easy.
2023-12-13 02:17 AM
Hello,
Thank you for your feedback.
Could you, also, try these points as well :
2023-12-13 03:26 AM
Thank you.
How I check if STLinkServer and STLink usb drivers are installed?
Il did the standard CubeIDE install.
The device manager shows:
The CubeIDE V1.14.0 required the STLINK firmware upgrade to:
Version: V3J13M4
Build: Jun 16 2023 16:43:25
I think the USB cable is OK because I use it for a long time, and CubeProgrammer works flawlessly with it.
Do CubeIDE and CubeProgrammer use different drivers?
2023-12-20 07:58 AM - edited 2023-12-20 08:14 AM
Hello,
The SLINK server folder is located in the STM32CubeIDE installation path, as is the SLINK USB driver, which is located in the Drivers folder C:\ST\STM32CubeIDE_1.14.0\STM32CubeIDE\drivers.
Could you also enable the GDB server traces to get more information, that would be helpful.