2024-10-06 11:29 PM - edited 2024-10-07 10:27 AM
I'm trying to debug a STM32 project on an STM32 IoT Discovery Node Board (B-L475E-IOT01A1) from my MacBook Pro (M1 Max running Sonoma 14.5). Every time I build and start a debug session, the process gets stuck on "Launching : Performing pre-launch check..." as shown in the figure below.
When it get's stuck like this, it can't be canceled and the only way to clear the process is to restart the IDE. I am new to this kind of debugging, but I have a feeling this is a problem with the USB connection and drivers because when I restart my computer, it usually works (without changing any of the project settings or configurations).
ST-link server is running on my machine, and seems to have connected properly as shown in the output for the following commands.
Is there any known way to resolve this error? Restart the drivers or reconnect ST-link? Restarting my computer every time is not really a long-term solution. I'm sorry if this is a dumb question, I am new to CubeIDE.
edit: added board number
edit: added MacOS version
Solved! Go to Solution.
2024-10-28 05:25 PM
Just to wrap this issue up, the problem appears to have gone away without necessitating a complete reinstall of the system. I am not sure what solved it, but for now it is solved. I will post updates if further issues arise.
2024-10-07 03:39 AM - edited 2024-10-07 11:27 AM
Hello @klaytonme,
First let me thank you for posting and welcome to the ST Community.
For more investigation, I suggest please that you provide the Mac OS version.
Thanks.
Mahmoud
2024-10-07 10:28 AM
Ahh yes thank you, I'd forgotten that. It's Sonoma 14.5 and I've added it to the original question.
Thanks!
2024-10-08 03:19 AM
Hello @klaytonme ,
Further to your comment, I suggest that you reinstall STM32CubeIDE and ST Link Server.
You can take a look at UM2563 Section 5 STM32CubeIDE installation (macOS®) .
Thanks.
Mahmoud
2024-10-28 05:25 PM
Just to wrap this issue up, the problem appears to have gone away without necessitating a complete reinstall of the system. I am not sure what solved it, but for now it is solved. I will post updates if further issues arise.