cancel
Showing results for 
Search instead for 
Did you mean: 

The interface firmware FAILED to reset/halt the target MCU with STM32F401RE

marti3110
Associate II

 

When I connect my STM32F401RE board to the PC via USB cable, a FAIL.txt file appears with the message 'The interface firmware FAILED to reset/halt the target MCU.' I tried following the tutorial https://www.youtube.com/watch?v=Ib0KMuv6cxA&t=192s, but I don't have the MDK-ARM software (I use CubeIDE or CubeMX). None of the discussions in this community have helped.

I also followed these steps https://embetronicx.com/tutorials/microcontrollers/stm32/fixed-the-interface-firmware-failed-to-reset-halt-the-target-mcu-stm32/ but the problem persists (I can see the serial number in STM32CubeProgrammer).

Immagine 2024-09-11 122817.png

WhatsApp Image 2024-09-11 at 12.18.21 PM.jpeg

6 REPLIES 6
Andrew Neil
Evangelist III

@marti3110 wrote:

I can see the serial number in STM32CubeProgrammer


So the connection from the PC to the ST-Link is working - it's just the  connection from the ST-Link to the Target Microcontroller (the STM32F401RE) that's not working.

Has this board ever worked?

Is the board brand-new, as-shipped - or has it been "previously enjoyed"?

Are all the links & solder-bridges at default settings?

Does your software go into low-power mode and/or reconfigure the SWD pins?

https://community.st.com/t5/stm32-mcus-boards-and-hardware/unable-to-connect-stm32f072rbt6-via-stlink-usb-cable/m-p/716736/highlight/true#M21164

https://community.st.com/t5/stm32-mcus/how-to-solve-debugger-connection-issues/ta-p/49693

 

I have been using the board for about 10 days and it has never had any problems.

I opened this link https://community.st.com/t5/stm32-mcus-boards-and-hardware/unable-to-connect-stm32f072rbt6-via-stlink-usb-cable/m-p/716736/highlight/true#M21164' and then this one https://community.st.com/t5/stm32-mcus/how-to-solve-debugger-connection-issues/ta-p/49693, I followed the guide but I get this message 'Starting server with the following options: Persistent Mode : Disabled Logging Level : 1 Listen Port Number : 61234 Status Refresh Delay : 15s Verbose Mode : Disabled SWD Debug : Enabled InitWhile : Enabled

Target no device found

Error in initializing ST-LINK device. Reason: No device found on target.' in CubeIDE.

In STM32CubeProgrammer I have '13:05:18 : Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication'.

On Windows, the Device Manager show both an 'ST-Link Debug' device and an ST-Link Virtual COM Port


@marti3110 wrote:

I have been using the board for about 10 days and it has never had any problems.


So have you recently changed any of the jumper or solder-bridge settings?

Check to see that no jumpers have "fallen off".

Does your software go into low-power mode and/or reconfigure the SWD pins?

 


@marti3110 wrote:

I followed the guide but I get this message 'Starting server with the following options: Persistent Mode : Disabled Logging Level : 1 Listen Port Number : 61234 Status Refresh Delay : 15s Verbose Mode : Disabled SWD Debug : Enabled InitWhile : Enabled


Where & when, exactly, do you get that message?

 

marti3110
Associate II

I haven’t made any modifications. How can I check if the software is entering low-power mode and/or reconfiguring the SWD pins?


@marti3110 wrote:

How can I check if the software is entering low-power mode and/or reconfiguring the SWD pins?


It's your software - you should know if it's doing any of those things?

marti3110
Associate II

marti3110_0-1726054927231.png

Given these imports, I generated the code; I haven't added anything else