MSP430F2274 Not Working After Debug

Ben Leavitt

This is kind of a two part issue.

Firstly, in trying to upload new code to my chip it suddenly did not respond as it should, and has not responded since. I reverted the code, and issue is the same. I tried to run it with the debugger, and that's where the second problem comes in.

The debugger stops at the first executable line:

DCOCTL = CALDCO_8MHZ;

It gives the error: Error: cannot load from non-primative location.

I know that there are other places on this forum where that particular issue has been solved, however none of them were able to help me in solving my specific problem.

over 10 years ago

0 old_cow_yellow over 10 years ago

Guru 58965 points

Instead of trying to run or single step the code, could you disassemble and inspect the machine code that correspond to the first executable line?
Is it something like "42D2 10FC 0056"?

0 old_cow_yellow over 10 years ago in reply to old_cow_yellow

Guru 58965 points

And also, could you inspect the contents of locations 0x10F8 to 10FF of the Info-A flash?

0 Ben Leavitt over 10 years ago in reply to old_cow_yellow

Prodigy 40 points

That is exactly what it is
42D2 10FC 0056 MOV.B &Calibration_Data_CALDCO_8MHZ,&System_Clock_DCOCTL

0 Ben Leavitt over 10 years ago

Prodigy 40 points

I've also found out that if I comment out the line that is giving me problems, the next line then gives me the exact same problem.

0 Ben Leavitt over 10 years ago in reply to old_cow_yellow

Prodigy 40 points

Do you know what could be causing this issue?

0 Bruce McKenney over 10 years ago in reply to Ben Leavitt

Guru 102575 points

Running the CPU too fast for Vcc (above the curve in Figure 1 of slas504g) will produce "goofy" (pardon the jargon) results -- the debugger will jump around, and/or appear to execute instructions other than the one you're looking at.

As OCY suggested, an easy way to get into this state is to erase (0xFF) the DCO calibration constants in InfoA, and then use them. The BSL is particularly good at accomplishing this; it's also possible to do this by incorrect settings in your debugger (mass erase with "erase Info segments", or some such). Looking at 0x10F8-10FF should tell you whether this has happened.

There is a program in the sample suite to re-generate the calibration constants, but as I recall it requires an external clock/crystal.

**Attention** This is a public forum

MSP low-power microcontrollers

MSP low-power microcontroller forum

MSP430F2274 Not Working After Debug