FAQs
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Cube IDE 1.1 - debugger fails to connect under reset to erased H7 MCU

Pavel A.
Evangelist III

‎2019-11-28 10:08 PM

After full chip erase in Cube Programmer, the CubeIDE debugger cannot connect with any reset option : connect under reset or software system reset.

Says: "Error message from debugger back end:

Error finishing flash operation

Failed to execute MI command:

load xxxxx.elf.

Cube Programmer can connect to it with options:

  • Under reset
  • Core reset

Other options: hardware reset, software reset - both fail with "DEV_TARGET_NOT_HALTED"

Why Cube IDE debugger does not have this "Core reset" option? Can it be added, please?

The chip is STM32H750 with external ST-LINK/v2.

-- pa

1 REPLY 1
Pavel A.
Evangelist III

‎2019-11-29 02:53 PM

This wasn't the end of the story, not yet ((

I could not connect to the H750 and program the flash, neither in CubeIDE 1.1 or Atollic.

Their GDB server-based debuggers behave very similar: either "Failed to execute MI command: load xxxxx.elf" or "target not halted".

Have not tried the OpenOCD option.

The following procedure recovered the debugger:

  1. Flash the program using CubeProgrammer, disconnect, power off, on.
  2. Connect with CubeIDE debugger in "hotplug" mode (no reset, no download). This succeeded after few attempts.
  3. Break in the debugger, do few steps.
  4. Terminate session. Restore the debugger settings back to connect under reset, download and verify.

Now the debugger again can connect and write the flash.

Very annoying and slow.

Unfortunately I cannot use Keil IDE for this project: customer demands gcc and free IDE.

-- pa

0 Kudos
Top