"The interface firmware FAILED to reset/halt the target MCU"

[JLiao.3]

Once I connect st-link v2-1 to STM32G473VBT6, there is a disk added into my PC, and there are 2 files in the disk. One is DETAILS.TXT(Version: V2J37M26 Build:  May 13 2020 17:07:43), another is FAIL.TXT (The interface firmware FAILED to reset/halt the target MCU).

If I try to debug in STM32CubeIDE, it shows

"Target unknown error 32

Error in initializing ST-LINK device.

Reason: Unknown. Please check power and cabling to target."

I tryied to tie Boot0 to high or low, but it did not resolved the problem.

[Igor Cesko]

Hi JLiao.3 ,

The message "The interface firmware FAILED to reset/halt the target MCU" means that the MCU cannot be accessed by the STlink. This message appears for example if there is no MCU on the Nucleo board or MCU is not connected by SWD wires to SWD interface. Please check the correct MCU connection to STlink - this is hardware problem.

Regards

Igor

[jab_el]

Hello,i have had same problem but when i see the current consumption i see 0,00 . any suggestions ??!

[Nick van IJzendoorn]

I'm pretty sure it can also be a software problem. I had the same problem with the NUCLEO-U575ZI-Q when trying to debug (I received error code 32 as well). Changing from the ST-Link to OpenOCD however solved the problem in my case.

[Lep]

I have the same issues.Can you tell me the derails to fix it?:loudly_crying_face:

[Igor Cesko]

Hi,

The reason to not connect to MCU can be also in MCU firmware - the firmware can disable SWD functions on pins and then external debugger cannot connect there (of firmware can put MCU into some low power mode - Stop, Standby - where SWD functions are not supported on pins).

Solution is to configure the software to be able to connect to device under reset. The best way is to connect to MCU in STM32CubeProgrammer (connection under reset) and erase the firmware which is blocking SWD wires. Instead of STM32CubeProgrammer we can use also some another programming tools (IAR, ... ).

The OpenOCD connects probably to MCU under reset.

Regards

Igor

[MDabo.1]

Hi, How can i do that​?

[Tesla DeLorean]

Which part?

Please be specific about your exact situation, this is an 18 month old thread

[kannastra]

No H745ZI-Q , voltou ao normal ao carregar o codico com o botão de reset e usuários acionados ao mesmo tempo

[DK.7]

After my experiments with Flash, I got an identical problem. How I fixed it is, see screen

[wegi01]

I had this same problem on the STM32H735G-DK and reason of this was a wrong firmware uploaded which blocked SWDIO. All the time ST-LINK-V3E put file named "FAIL.TXT" in the mass storage device entries.

Solution: 

Change BOOT switch (showed on the picture below) to SYS MEM possition, plug ST-LINK to USB (now on MSC device doesn't exist "FAIL.TXT" file), run STM32CubeProgrammer and do full erase of MCU flash. Now change BOOT switch to FLASH mark and everything is all right after reset.