2025-03-02 2:39 PM
I was just debugging earlier today on my STM32H7B3I-EVAL board from my Mac (Sequoia 15.3.1), which I have been doing for weeks. Note, the eval board has a built in ST-link. Things were going great. I figured it was a good time to install github integration.
After I installed eGit from the Eclipse Marketplace, I saw the indication that I can update from 1.17 to 1.18 and clicked on it. Everything appears to go smooth on both the git stuff and the upgrate of the IDE. Unfortunately 1 problem was found after installation.
Projects in the workspace that were working minutes before the upgrade, and have NOT been modified after the upgrade, have all now consistently failed to debug. The message is the same, that no ST-link was detected.
My suspicion was that this was a problem with the STM32CubeIDE. I tried out the STM32CubeProgrammer and it works wonderfully still. I assume that is enough to show that the ST link is fully operational.
I went back to debugging the issue in the STM32CubeIDE. In the configuration for the debugging, I usually leave the S/N (serial number) for the ST-link unselected, but tried both unselected and selected, and saw no change in behavior. Oddly enough, when I select the S/N, the scan button is enabled and clicking it allows me to scan and see my ST-link serial number showing up in the box.
I even saw some other post in this community that some older issues were addressed by starting the STM32CubeIDE via sudo. I have tried that but it did not work for me.
I feel pretty confident this is related to the upgrade of the IDE. Any questions or suggestions are welcome!