STLink Server with MacOS 15

[jdw]

 

Hello,

I updated to Mac15 (MacOS Sonoma Public Beta), which was probably a mistake. Now I get an error from STMCubeIDE when I try to run indicating "ST-Link Server is required to launch the debug session" and to Please download it on www.st.com.  

I figured something changed in the OS that no longer makes the ST-Link Server run any more.

However when I try to download it, I get essentially a broken link, or at least it simply wont download. Even worse, the web page with Safari seems entirely broken and I cant even get a download to start after accepting the license, but with FireFox I get further, I get but still wont download and the link seems broke.

I can still flash using the STM32CubeProgrammer fortunately (using 2.13.1).

Can anyone tell me how to download this ST-Link Server? Or if there is an issue with the last MacOS and this and there is no fix?

 

[TDK]

STMCubeIDE should be self-contained, everything it needs is installed alongside it. You shouldn't need to download anything else.

Did you try to reinstall?

[jdw]

I have not tried to reinstalled STMCubeIDE as yet. I find it a bit odd that ST offers a download page for the STLink-Server (even if it does not seem to work for me) - https://www.st.com/en/development-tools/st-link-server.html

and further seems to put a message in the STMCubeIDE to download it. But, maybe that happens because somehow the server binary is not compatible with MacOS 15 Sonoma and it STMCubeIDE acts like it simply does not see the server running, and cant find it. Therefore, it makes me wonder if there is some overall issue with the server and MacOS 15. I can try to re-install STMCubeIDE 16.0.

 

 

[jdw]

I have now been able to both download the server, which after installing did not fix my issue. So I downloaded and reinstalled STMCubeIDE16.0, and that did not help either. I would say there is some new incompatibility with MacOS 15 Sonoma, which is is going to break a bunch of folks at some point. I am happy to help ST work how what is going on with my case if anyone wants to.

 

[jdw]

One thing I want to correct, is the naming of MacOS above - 15.0 is Sequoia.

[TDK]

Per the release notes, MacOS 15 isn't officially supported yet. No doubt it will be eventually, but you'll probably have to wait.

[jdw]

Yep that makes perfect sense. I think I did get a bit aggressive on the update. Thanks for responding to that. At least I can still compile and flash with the command line programmer so I’m not blocked. 

[fsteiner]

Hi there, the sudo command doesn't work for me, have you found another solution?

[Patrick Chwalek]

I have the same issue after updating last night to macOS 15.0.

[Rohdea]

Using "sudo" can temporarily solve this issue

sudo /Applications/STM32CubeIDE.app/Contents/MacOS/STM32CubeIDE

 

[ydzulyns]

Rohdea, I made an ST account specifically to thank you. You saved me such a hassle. Thanks!!!

[tdunn]

Thank you Rohdea! Using sudo to launch the app solved the issue for me as well.

[Bouzid-s]

macOS 15 not yet supported.

possible solution :

run the following command in the external terminal, the GDB server starts properly, and I'm able to debug the application. I use then remote GDB server (localhost with default port)

 

/Applications/STM32CubeIDE.app/Contents/Eclipse/plugins/com.st.stm32cube.ide.mcu.externaltools.stlink-gdb-server.macos64_2.1.400.202404281720/tools/bin/ST-LINK_gdbserver -cp/Applications/STMicroelectronics/STM32Cube/STM32CubeProgrammer/STM32CubeProgrammer.app/Contents/MacOs/bin/STM32_Programmer_CLI youpath_to_project_debug_project.elf

 

or copy it from the debug configuration.

This starts the GDB server and loads my application without any issues.

[Andrei Chichak]

Yeah, that gets around the immediate issue, but not the long term.

Since sudo gets around the issue, it's a permissions issue. For me it showed up after I updated to 15.1

Oh, that's weird. I launched 1.16.1 from the command line, without the sudo, and the ST-Link server starts properly.

 

WAT????

[QuantumStudent]

Hi everyone. I did a bit of research on this issue and found that the debugger fails to launch due to the missing environment variable /usr/local/bin. The problem is that when the program is started from Launchpad or from the terminal, the set of environment variables available to the program is different. When launched from the terminal, /usr/local/bin is included in the PATH, but it’s missing when launched from the shortcut.

 

I couldn’t find an easy way to add an environment variable to Launchpad, and I don’t think that’s the best approach anyway. A temporary solution is to create a shell script through Automator, as shown in the screenshot.

[JG_it]

Thank you Rohdea! Using sudo works for me as well, but strangely it changes the keyboard language.

[fsteiner]

Exactly the same here - I cannot revert to my French keyboard.