Failed to execute MI command after update to IDE

[pretoriandave]

Hi All,

I know the dreaded 'Failed to load MI command' error has been much discussed on the forum but I can't find any posts which match this set of circumstances, so hoping somebody can help.

My project was working perfectly on STM32G0 but I need to port it to STM32C0. My IDE was at version 1.13.2 (I don't like updating unless I'm forced to and this is a good example of why) but C0 is a new part so I had no choice. It updated to 1.17.0 and of course that also forced an update to ST-LINK.

Now nothing works. I can neither debug nor run my previously working code on the target board, which I know is just fine. I've tried swapping the ST-LINK to a different USB port and also changing the port number in Debug Configurations to no avail.

Note that I elected not to migrate the project across to 1.17.0 when it was offered as I thought changing the least amount possible would be the best approach. Maybe that's the issue but I don't know how to take up the offer now.

The new C0 project which was built using 1.17.0 in the first place exhibits the same problem.

I'm relatively new to this ecosystem (and wish I could say I was enjoying the experience) so have no clue what to do next. Thanks for any help anyone can provide.

 

 

[Pavel A.]

Usually caused by debug or run configurations remaining from the older IDE version.

Try to create a new debug config from scratch.

#bugreport CubeIDE team, can you consider to fix tools paths in old configs automatically?

 

[pretoriandave]

Thanks @Pavel A. How does one go about that? I tried cleaning the project but it made no difference. Thanks

[Pavel A.]

@pretoriandave So you have created a 100% new debug config "ToFFEE2 Debug" and get the same error?

 

Though ...

> The new C0 project which was built using 1.17.0 in the first place exhibits the same problem.

This should create a new configuration for sure, so it hints to a different problem...

If you have a Windows 11 PC, you can request somebody from here to help, via the Quick Assist app

 

 

[AScha.3]

Try with setting: connection mode: software reset.

[pretoriandave]

@Pavel A. yes I came to the same conclusion. Not on Win 11 unfortunately.

Is this anything to go by?....

It keeps popping up so I think it may be.

 

Thanks