B-G431B-ESC1 Not Detected by STM32CubeProgrammer After Failed Connection

[Ankitesh]

I am using the B-G431B-ESC1 board, which connects to my laptop via a micro-USB to USB-A cable. After a failed connection attempt, the board is no longer detected by STM32CubeProgrammer. Additionally, a file named "File.txt" is created on the MCU after the failed attempt.

The contents of the file are:
"The interface firmware FAILED to reset/halt the target MCU."

This file appears to be causing issues with the connection to STM32CubeProgrammer.

Could anyone please help me resolve this issue?

 

[Ankitesh]

it is FAIL.TXT not File.txt

[STuser2]

You can try flashing with CubeIde.

[Ankitesh]

Same issue with STM32CubeIDE.

[GMA]

Hello @Ankitesh,

Has the board been modified around SWD signal path?
Refer to the STM32CubeProgrammer user manual and try using Connect under reset mode.

This usually happens when the ST-LINK can’t reset or halt the MCU after a failed flash/debug attempt — the File.txt is just a log, not the actual problem.

Try this:

• In STM32CubeProgrammer, select “Connect Under Reset”

• Lower the SWD frequency (e.g., 100 kHz)

• Fully power cycle the board and try again

• Also check for ST-LINK firmware updates

In most cases, connecting under reset with a lower SWD speed fixes it.

[Ankitesh]

Answer:

• In STM32CubeProgrammer, select “Connect Under Reset”

• Lower the SWD frequency - tried on different frequencies i.e. 100kHz, 50kHz, 25kHz, 15kHz. 

• Fully power cycle the board and try again - done during test

• Also updated ST-LINK firmware updates

 

But same result occurs again.