STM32CubeIDE 'Could not determine GDB version using command: arm-none-eabi-gdb --version'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-07-01 02:34 PM - last edited on ‎2024-07-01 02:58 PM by Peter BENSCH
Hello,
I am using STM32CubeIDE Version: 1.15.1 Build: 21094_20240412_1041 (UTC). I am using windows 10 Version 22H2 (OS Build 19045.4412).
I have recently started receiving this error message when launching the debugger "Could not determine GDB version using command: arm-none-eabi-gdb --version". I'm not sure what changed from one day to the next where I started getting this message and I've asked my IT department if anything changed on our side but it doesn't seem that was the case. Has anyone else started getting this error, or figured out a way to resolve it?
thanks!
- Labels:
-
STM32CubeIDE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-07-09 08:00 AM
Same here. It seems that Cube can not keep the default toolchain info.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-07-10 01:14 AM - edited ‎2024-07-10 01:15 AM
"Could not determine GDB version using command: arm-none-eabi-gdb --version"
STM32CubeIDE
Version: 1.12.0
Build: 14980_20230301_1550 (UTC)
(C) 2023 STMicroelectronics ALL RIGHTS RESERVED
I tried a fresh install, no updates.
Was working fine until some weeks ago.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-07-11 12:57 AM
Hello again.
I installed
Version: 1.13.2
Build: 18220_20230914_1601 (UTC)
because my projects were build using this version.
The error happens starting the second debugging session: the first session after starting STM32CUbe IDE is always successful.
This is the error window:
I tried forcing the path for the tools, the problem persists:
 
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-07-11 08:42 AM
I am still having this problem off and on. The only insight I have into it is that I think it might be because of the security software that we run on our PC's as well blocking the call to the command prompt when the gdb server is launching. I disabled our security software which made the gdb_server work again. I'd look into that angle if you haven't already.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-09-27 02:41 AM - edited ‎2024-09-27 02:42 AM
Thanks. The problem has been solved here by the ICT guys in my company, the security software now does not intrude anymore during STM32CubeIde and related processes running. The result is that building/compiling is again very fast and debugging is working well again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-09-27 02:44 AM
@Adriano Melis wrote:the security software now does not intrude anymore
What do you mean by that - anti-virus? firewall?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-10-01 02:00 AM
I would be interested to know how you did this.
What processes or web domains have you whitelabelled in the security software?
I have the same problem and in addition I cannot log in properly to myST account via the CubeIDE 16.1 version.