Reputation: 1
I have a hard problem with a STM32. After uploading my own code to the STM32 it is not possible to reconnect with them.
The error feedback:
17:18:34 : Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication
I'm working with the STM32H735VGT6, connected with ST-link V2, software **STM32CUBEIDE **and STM32CubeProgrammer.
What can cause this problem? How do I reconnect to the STM32?
I have tried:
Option that I will try with new STM32:
Upvotes: 0
Views: 2641
Reputation: 1
If at any time a deadlock situation is faced due to a mismatch between the target’s hardware power configuration and firmware setting, you can recover the board by doing the following: Step 1. Power off the board Step 2. Locate the BOOT0 pin and connect the BOOT0 pin to VDD using a wire. This pulls the BOOT0 pin to HIGH, which changes the device’s boot address to start the bootloader in system memory instead of booting from the target’s flash memory (which currently houses the firmware that is setting the incorrect SMPS/LDO configuration). Step 3. Power on the board and connect to the target using STM32CubeProgrammer. Step 4. Perform a mass erase. Step 5. Power off the board and remove the wire between BOOT0 and VDD. Step 6. The recovery is now completed; you can once again connect to the target using the STLINK and use the board as normal. For additional information on this warning, please refer to UM2408, in specific the section concerning Internal SMPS / LDO Configuration.
Please try this. It may be helps you.
Upvotes: 0
Reputation: 67820
You probably have reprogrammed the SWD pins and they are not available for debugging (PA13 & PA14). You need to *connect under reset in STM cube programming or STMCubeIDE. Sometimes it is needed to keep NRST line manually low when the probe connects to ther uC.
Upvotes: 1