Upgraded STM32CubeIDE to 1.18.0, no st-link detected

[MF1]

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!

[Souhaib MAZHOUD]

Hello @MF1 

Could you please provide a log or screenshot so that we can proceed with the investigation?

KR,

Souhaib

[FilipKremen · Accepted solution]

Hello,

please try to reinstall ST-Link Server, it should solve the issue.

Best regards,

Filip Kremen

[MF1]

Thanks @Souhaib MAZHOUD and @FilipKremen .  I had been traveling for a few days.  I will try that tonight.  I expect it will work too.  Thanks so much!

[MF1]

Reinstalling the ST-Link Server ended up solving the problem, but it was not as straight forward as I thought it was going to be.

Installing it went smooth and quiet.  Restarted STM32CubeIDE, then I was a little surprised by running the project.  I just expected it to work, but I was presented with a "firmware version mismatch" dialog.  It said the firmware on the ST-Link hardware on the evaluation board was older than what the IDE expected.

So at this point, I was relieved.  I think the advice from @FilipKremen  was correct, but they could have explained the following:

1. Reinstall the ST-Link Server, this will make STM32CubeIDE check the ST-Link firmware

2. When using ST-Link within STM32CubeIDE the next time, a firmware check will indicate the firmware is the wrong version.  Proceed with the firmware update.  Accept all default settings.

This is the upgrade window upon completion of my ST-Link firmware upgrade.

The ST-link now works a it used to work prior to the STM32CubeIDE update.  Thanks so much!

However, I am wondering if there is another way I could have checked firmware on the ST-Link without reinstalling the ST-Link Server.

[MF1]

The dialog the popped up in STM32CubeIDE was the same one that you would get if one were to install the STLink Upgrade application found at the following location.

https://www.st.com/en/development-tools/stsw-link007.html

I hunted around and could not find how to launch the ST-Link upgrade process from within the STM32CubeIDE.  So, two recommendations for ST folks.

1. Please add a menu item somewhere to launch the ST-Link upgrade, and

2. MORE IMPORTANT, when there is "no st-link detected", if it is due to firmware mismatch, please provide a better message, or offer to start the ST-Link upgrade.

[FilipKremen]

Hello,

you can check the ST-Link firmware in STM32CubeProgrammer by clicking on "Firmware upgrade" button.

Best regards,

Filip Kremen