cancel
Showing results for 
Search instead for 
Did you mean: 

"Failed to execute MI command load"

BRobb.1
Associate III

Error from the debugger. It compiles fine.

3 REPLIES 3
Markus GIRDLAND
ST Employee

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
Associate III

How do I do that?

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