'Internal Command Error' after MSI range 0

kohchengsing · ‎2011-10-11

Posted on October 11, 2011 at 09:54

I was using uV4.21 with STM32L-Discovery.

I changed the MSI speed to range 0 (around 65.536 kHz), debugged and ran the program.

The program ran slowly, as expected.

Then I coded to change the MSI speed to another range.

However, whenever I clicked 'debug', the 'internal command error' appeared.

The program (MSI range 0) downloaded previous could still run on the board.

But the uV4 IDE always gave the same error.

I tried with IAR and it said that the CPUID is not valid or things like that.

What error did I make ?

How can I recover the board ?

komarek.milan · ‎2011-10-11

Posted on October 11, 2011 at 13:58

Hello,

try the ''Connect: under Reset'' option in uVision. It may happen that due to the too slow CPU clock the debug tool is not able to connect. By the system reset the CPU clock is reconfigured to the default state MSI at 2MHz. Or you can try to press the reset button and try to release it just before entering the debug session. I hope it helps.

kohchengsing · ‎2011-10-11

Posted on October 12, 2011 at 02:27

Thank you.

I cannot find the ''Connect: under Reset'' option.

I tried ''the press the reset button'' before, it did not work. Perhaps I was not even as quick as 65.536 kHz.

From: eM Ko

Posted: Tuesday, October 11, 2011 1:58 PM

Subject: 'Internal Command Error' after MSI range 0

Hello,

try the ''Connect: under Reset'' option in uVision. It may happen that due to the too slow CPU clock the debug tool is not able to connect. By the system reset the CPU clock is reconfigured to the default state MSI at 2MHz. Or you can try to press the reset button and try to release it just before entering the debug session. I hope it helps.

kohchengsing · ‎2011-10-11

Posted on October 12, 2011 at 05:01

The board had been recovered, using the suggestion by Donald Becker in a STM32VL-Discovery Forum post.