cancel
Showing results for 
Search instead for 
Did you mean: 

BUG: STM32CubeIDE Won't connect to ST-LINK v2 debugger on macOS 15.0

KMill
Senior

My setup is macOS 15.0 Sequoia

STM32CubeIDE 1.16.1

STLink-Server v2.1.1

When trying to program or debug a device the following error is shown:

Screenshot 2024-09-19 at 13.00.10.png

Even after re-installing ST-Link server

I have rebooted and re-installed ST-Link Server, but the issue persists.

It's not a show stopper as I can use STM32CubeProgrammer to program the device, on the same machine.

18 REPLIES 18

@pdmazariegos Thanks for the link to that solution on stackoverflow.

I find that it does indeed work. It's a better workaround than the one I came up with!

Hopefully the dev's at ST will be able to get to the bottom of it and push out a compatibiliy release in the near future. I have to keep my macOS up to date for other reasons, so I had no choice but to update to macOS 15.0

@mƎALLEm Do you know if ST run a beta programme? I'd be happy to help with beta testing.

*edit* Spelling.

another one with the same problem:

https://community.st.com/t5/stm32cubeide-mcus/debugging-works-manually-but-not-from-stm32cubeide-st-link-gdb/m-p/722683

 

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

I started ide with the sudo command and it works fine with st-link, macOS 15.1 Intel CPU.

 

This post has been translated from Chinese to comply with the ST Community guidelines.

I am getting 'source not found' in MAC OS 15 on an M2 PRO

@rclar.6 What version of STM32CubeIDE are you running?

@rclar.6 Is this actually related to the original Topic from 2024,  "BUG: STM32CubeIDE Won't connect to ST-LINK v2 debugger on macOS 15.0" ?

That was marked as solved, with the solution being: macOS15 is not supported yet.

Have you confirmed that MacOS 15 should now be supported?

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

1.1.18 I think. I downloaded the latest version (from 1.1.14) in the hope it would fix it.

So does its readme claim that MacOS 15 should now be supported?

 

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

OK. I was too hasty to upgrade. hopefully a newer version will fix this soon.