2024-07-26 02:47 AM - edited 2024-07-26 03:43 AM
This sort of thing is a way of life with these ST tools (been using Cube IDE for 6 years on this project) but this one I am unable to fix. Is there some special setting needed under Debug (under project/properties)?
STMicroelectronics ST-LINK GDB server. Version 7.8.0
Copyright (c) 2024, 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
ST-LINK device status: UNKNOWN
Waiting for debugger connection...
Debugger connected
Waiting for debugger connection...
Debugger connected
Waiting for debugger connection...
Encountered Error when opening C:\ST\STM32CubeIDE_1.16.0\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.1.400.202404281720\tools\bin\STM32_Programmer_CLI.exe
Error in STM32CubeProgrammer
Shutting down...
Exit.
I've tried 2 x STLINK ISOL V3 and a STLINK ISOL v2. No success.
2024-07-31 11:51 PM
Zero replies.
Is there really no way to debug this very common scenario?
2024-08-01 12:59 AM
zero + 1 . 🙂
So you had it working for years...what you changed, to stop it ?
see my setting :
Try...(software reset ! )
2024-08-01 01:05 AM
No; my point is that 1.16.0 broke it. I had been working with Cube IDE for several years, all the various versions.
I see you are using OpenOCD. I've always used GDB Server mode. The others didn't seem to work. Which STLINK are you running?
2024-08-01 01:25 AM
Here i am on IDE V 1.14.1 . (working fine - so why i should risk any "update" to unknown state ?? 🙂 )
+ blocking all online/update search etc. -> offline mode seems helping a to keep stable workset .
(If v 16... dont work, just use older Version and see next update for V16.. , maybe then ok again)
+
ST-links i use : V3-miniE , V3-mods , V2 (the "clones" , but all with STM chips..) ;
and also GDB and OCD ...sometimes one not working, so i choose the other. ...and back.
2024-08-01 02:04 AM
Right - I too froze updates on 1.14.1 and disabled looking for updates.
Not really a solution though 😁
2024-08-01 02:31 AM
I have the same problem. I use STM32 CUBE IDE V1.16 and ST-LINK/V2. I could not solve the problem.
2024-08-19 11:16 AM
I have the same problem with both the V1.14 and V1.16 versions.
I use the STLINK-V3MINI and my OS is Windows 11.
I should point out that everything was working 4 months ago.....
I couldn't solve the problem !
MESSAGE:
STM32 CubeIDE:
I really need a solution to move my project forward!
2024-08-19 12:39 PM
What you set for connecting mode?
Try: hardware reset, + under reset.
That's helpful, if you did anything to set the chip to a mode, that not allows normal access, maybe not set debug in Cube or using a debug pin for any other way, as I/o pin or so.
2024-08-20 12:26 AM
Hi @AScha.3 , thank you for your reply.
I'm not sure I understand your question.
My hardware connection mode is configured like this:
Then I use a basic USB cable.
This setup has always worked correctly.
The BOOT0 pin is connected to GND.
My DEBUG configuration is done like this:
I also updated the STLINK-V3MINI and did a ‘clean’ of the project.
I also want to say that I managed to flash the MCU the very first time with my programme, but then it wasn't possible any more.