2023-10-11 06:55 AM
This is the second time that I came in the morning to a device and greeted with this message upon upload:
Info : Remote address: 127.0.0.1
Info : stlinkserver already running, exit
Target no device found
Error in initializing ST-LINK device.
Reason: No device found on target.
It has happened already and I just grabbed a new device as I could not debug it myself.
There was no difference in the program that I tried uploading (same build). The only thing that changed between the two tries was me unplugging the USB at the end of the day and plugging it back in in the morning.
The jumper is still on the ST-LINK position and the ST-LINK itself is visible and I can upgrade it without any difficulties.
I am using STM32CubeIDE.
What can I do to reverse this?
Solved! Go to Solution.
2023-10-11 08:00 AM
Hello @rbcarlos ,
Using STM32CubeProgrammer.
On the ST-LINK configuration area:
try to connect asap when power your board. When you connect you can do "full chip erase".
It suppose to be ready for next usage.
I hope it helps
Foued
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2023-10-11 08:00 AM
Hello @rbcarlos ,
Using STM32CubeProgrammer.
On the ST-LINK configuration area:
try to connect asap when power your board. When you connect you can do "full chip erase".
It suppose to be ready for next usage.
I hope it helps
Foued
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2023-10-11 08:06 AM
The H7's can get into an unusable state if the LDO/SMPS settings are wrong. Easiest way to recover this state is to jumper BOOT0 HIGH/VDD, and power cycle the board a couple of times (remove all power sources/cables). An then when you can connect erase your application code. Use STM32 Cube Programmer.
2023-10-19 01:20 AM
Just an update, I have found multiple mentions of @Tesla DeLorean 's solution on the internet, but this unfortunately made no difference in my case.
@Foued_KH 's solution worked reliably, also on STM32L476.
Thanks to both of you!