2024-09-12 07:47 AM - edited 2024-09-12 07:53 AM
Hello, I have been using the same cubeIDE debugger options for several months and have not had any major issues. However i recently updated to the latest macOS 15.0 release (not necessarily the cause, but it's the only change that comes to mind) and since then i've been getting the following error:
I have reinstalled the stlink server as recommended in:
https://community.st.com/t5/stm32cubeide-mcus/st-link-server-is-required-to-launch-the-debug-session/td-p/69617
and
https://community.st.com/t5/stm32-mcus-boards-and-hardware/cubeide-does-not-see-st-link-server/td-p/149158
This has not fixed it and the stlink-server appears to be installed properly as i can use it via the CLI. I have also tried reinstalling the cubeIDE and used different versions of the cubeIDE.
Has anyone encountered something similar or have any idea on what this could be?
EDIT:
I can also host a server from the CLI and connect to it from the cubeIDE via the "Connect to remote GDB server" option.
Solved! Go to Solution.
2024-09-13 02:56 AM
Apparently launching the app from the terminal with sudo solves this, so it appears to be a permissions issue.
2024-09-13 02:56 AM
Apparently launching the app from the terminal with sudo solves this, so it appears to be a permissions issue.
2024-09-18 06:09 AM
Got the same identical problem on macOS sequoia 15, thanks for the solution
2024-09-19 03:19 PM
Hi Carl,
I had the same issue. I think the guilty one is the upgrade to Sequoia 15, as CubeIDE and stlink-server are not fully supported.
For the moment, the way to get around it is to launch your IDE from a Terminal:
sudo /Applications/STM32CubeIDE.app/Contents/MacOS/STM32CubeIDE
It worked great for me.
2024-09-20 10:37 AM
Actually its the PATH available to GUI app. There's no need to use sudo.
Much more information is available at