• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 79 subscribers
  • Views 129 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LaunchPad no longer works?

Xuan Xing
Prodigy 100 points


Today I found one of my two launchpads doesn't work. I'm stepping through the following code using CCS5:

void Setup()
{
// Stop watchdog timer
WDTCTL = WDTHOLD | WDTPW;

// Setup main clock to 1MHZ
BCSCTL1 = CALBC1_1MHZ;
DCOCTL = CALDCO_1MHZ;


// Enable interrupt
__bis_SR_register(GIE);


P1DIR |= LED_PIN; 
P1OUT |= LED_PIN;

It's working until the line P1DIR, all I got is the following message in CCS console:

MSP430: Trouble Reading Memory Block at 0x3fc on Page 0 of Length 0x2: Could not determine device state

I unplug the the same chip and put onto another board, and things are working without any issues. Does this mean any hardware issue with the debugger board?

Thanks

  • 0
    Guru 227245 points

    It is possible that the timing constants have been erased and you're configuring the clock system to an invalid frequency. As a result, the CPU will crash and give the debugger trouble. The usual demo code uses atrap that enters an endless loop when CALDCO_x or CALBC1_x are 0xff (= erased)

**Attention** This is a public forum