cancel
Showing results for 
Search instead for 
Did you mean: 

First Upload/flash STM32 F0 works than Error: No STM32 target found! If your product embeds

Gamma5922
Associate II

Hi STM Devs.

I'm currently testing the: STM 32F030F4P6 and STM32 F030K6T6

With the STM32CubeProgrammer and ST-Link v2 I could flash the MCUs the first time, but than all other trys run into the following Error Message

"Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication"

This behaviour i had on the two mentioned MCUs.

I've tried so far:

Switching the Modes and Reset Modes in STM32CubeProgrammer - but no success

Any other Ideas?

Thanks for your help

 

ps.: UART gives me this error
Error: Activating device: KO. Please, verify the boot mode configuration and check the serial port configuration. Reset your device then try again..

12 REPLIES 12

@TDK wrote:

If you want to develop, use an actual programmer with an SWD connection, otherwise you end up debugging stuff like this for hours on end.


On page 39 of UM3345:

Note: With the BLE_p2pserver demo programmed in the NUCLEO-WB09KE, the low‑power mode is enabled to
offer the best low‑power performances. Therefore, on STM32WB09KE, the SWD lines are OFF and the tool
cannot connect with the device anymore.
To reconnect or reprogram the Nucleo board, it is necessary to enter the Bootloader mode. To do this, the JP1
jumper on the MB2032 MCU RF board must connect 2 and 1

 

When I connect CN3 on ST-Link V3SET to [CN3-35] and [CN3-37] on MB1801D, it was prompted in Prog:

13:40:46 : UR connection mode is defined with the HWrst reset mode
13:40:46 : RTS low
13:40:46 : DTR low
13:40:46 : Serial Port COM6 is successfully opened.
13:40:46 : Port configuration: parity = none, baudrate = 9600, data-bit = 8, stop-bit = 1.0, flow-control = off
13:40:50 : Timeout error occured while waiting for acknowledgement.
13:40:50 : Error: Activating device: KO. Please, verify the boot mode configuration and check the serial port configuration. Reset your device then try again...

 

What's the correct "the boot mode configuration and check the serial port configuration" ?

@MQi.1 It sounds like you have a different issue than what was being discussed here. Please start a new thread with the relevant information.

If you feel a post has answered your question, please click "Accept as Solution".