Skip to main content
BRobb.1
Associate II
December 1, 2021
Question

"Failed to execute MI command load"

  • December 1, 2021
  • 2 replies
  • 769 views

Error from the debugger. It compiles fine.

This topic has been closed for replies.

2 replies

Markus GIRDLAND
ST Employee
December 2, 2021

Hello there!

To get more information about why it fails you could try to activate the gdb server log in your debug configuration.

It will tell you some additional information about why it can't load.

BRobb.1
BRobb.1Author
Associate II
December 6, 2021

How do I do that?

BRobb.1
BRobb.1Author
Associate II
December 6, 2021

Does this mean that I am having problems opening a port during a build?

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

[8.316] run(): GDB session terminated: Client connection lost

[8.316] handleSessionEvent(): GdbSessionManager, session terminated: 2

[8.327] updateState(): SwvSrv state change: 2 -> 1

[8.327] handleSession(): SwvSrv session thread disposed

[8.327] WaitConnection(): Waiting for connection on port 61235...

[8.342] WaitConnection(): Received stop for port 61234, not accepting new connections.

[8.342] deInit(): GdbSrv, deInit entry.

[8.342] deInit(): GdbSessionManager, deInit entry.

[8.390] ~GdbSession(): GDB session disposed: 2

[8.390] ~GdbSession(): GDB session disposed: 1

[8.390] deInit(): GdbSessionManager, deInit exit

[8.390] deInit(): SwvSrv deInit entry

[8.390] stop(): Stopping port 61235

[8.437] WaitConnection(): Received stop for port 61235, not accepting new connections.

[8.437] deInit(): SwvSrv deInit exit

[8.437] closeDevice(): Stm32Device, closeDevice() entry