Skip to main content
BMano
Associate II
January 23, 2020
Question

Error! Failed to read target status

  • January 23, 2020
  • 2 replies
  • 1920 views

Hello everyone, I am trying to run a program on my board. I could use the same method to debug the program on a different chip but now it is not working on this board. I am using the st-link v2 programmer. but I get this error:

******************************************************************************

STMicroelectronics ST-LINK GDB server. Version 5.2.3

Copyright (c) 2019, STMicroelectronics. All rights reserved.

Starting server with the following options:

    Persistent Mode      : Disabled

    Logging Level       : 1

    Listen Port Number     : 61235

    Status Refresh Delay    : 15s

    Verbose Mode        : Disabled

    SWD Debug         : Enabled

Waiting for debugger connection...

Debugger connected

   -------------------------------------------------------------------

            STM32CubeProgrammer v2.1.0          

   -------------------------------------------------------------------

Log output file:  C:\Users\BMANOU~1\AppData\Local\Temp\STM32CubeProgrammer_a10724.log

ST-LINK SN : 56FF6D064883535246222487

ST-LINK FW : V2J34S7

Voltage   : 3.23V

SWD freq  : 4000 KHz

Connect mode: Under Reset

Reset mode : Hardware reset

Device ID  : 0x448

Device name : STM32F07x

Flash size : 128 KBytes

Device type : MCU

Device CPU : Cortex-M0

Memory Programming ...

Opening and parsing file: ST-LINK_GDB_server_a10724.srec

 File     : ST-LINK_GDB_server_a10724.srec

 Size     : 49964 Bytes

 Address    : 0x08000000 

Erasing memory corresponding to segment 0:

Erasing internal memory sectors [0 24]

Download in Progress:

File download complete

Time elapsed during download operation: 00:00:02.525

Verifying ...

Download verified successfully 

Error! Failed to read target status 

Debugger connection lost.

Shutting down...

******************************************************************************

Any help is appreciated. Thanks

    This topic has been closed for replies.

    2 replies

    Tesla DeLorean
    Guru
    January 23, 2020

    Yes, if you reconfigure the debugger pins, or Cube whatever disables them, or you powerdown/sleep the device, the debug interface will cease to work.

    You can't "Connect under Reset" if you didn't connect the NRST pin.

    Pull BOOT0 HIGH to stop your own code running, the System Loader is a relatively safe harbour to gain control again and erase/program the part.

    Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
    ANaga.2
    Associate III
    June 17, 2020

    How can we pull BOOT0 to High for SBSFU example project?