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 just stopped working.

Other Parts Discussed in Thread: MSP430G2231

Hello all.

I was just developing an application for my launchpad, using the msp430g2231 and it just sttoped working as the title says.

I have no idea what caused this to happen. I'll explain you what I did and why I know its the launchpad what is broken.

I have two launchpad sets, each one with its own two chips and stuff. I uploaded my application to one of them, and it wasn't working. I did just a small change to my app (no extra peripherals used, I think i only changed a variable.) and as i said it wasn't working, and the debugger gave me an error. I was disappointed, the change I did shouldn't produce what happened, so I ctrl-z'd the changes and tried to upload the working version. Same thing happened. I was starting to think the launchpad broke in my face, and thats exactly what happened. I connected the other launchpad, and everything was working fine, the version with changes worked as it was supposed to.

Any idea why this launchpad died? This is really hopeless. Hopefully I'll be able to develop my application with the other launchpad before it dies.

Any help is really appreciated.

Thanks in advance.

 

PS: Some extra info: My application uses the USI in SPI mode, sets the internal oscillator at 16MHz. I'm using MSPGCC as the compiler and MSPDEBUG as the debugger. All this in Ubuntu 11.11. The output of mspdebug is:

 

rafa@rafa-AOA110:~/launchpad/ds2e$ make && make upload
msp430-gcc -Os -Wall -g -mmcu=msp430g2231 -o main.elf main.o
mspdebug rf2500 "prog main.elf"
MSPDebug version 0.16 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2011 Daniel Beer <dlbeer@gmail.com>
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Trying to open interface 1 on 016
Initializing FET...
FET protocol version is 30066536
Configured for Spy-Bi-Wire
Set Vcc: 3000 mV
fet: FET returned error code 4 (Could not find device (or device not supported))
fet: command C_IDENT1 failed
fet: identify failed
Trying again...
Initializing FET...
FET protocol version is 30066536
Configured for Spy-Bi-Wire
Sending reset...
fet: FET returned error code 4 (Could not find device (or device not supported))
warning: fet: reset failed
Set Vcc: 3000 mV
fet: FET returned error code 4 (Could not find device (or device not supported))
fet: command C_IDENT1 failed
fet: identify failed
make: *** [upload] Error 255
rafa@rafa-AOA110:~/launchpad/ds2e$

 

And this is the output if i use the other launchpad:

rafa@rafa-AOA110:~/launchpad/ds2e$ make && make upload
msp430-gcc -Os -Wall -g -mmcu=msp430g2231 -o main.elf main.o
mspdebug rf2500 "prog main.elf"
MSPDebug version 0.16 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2011 Daniel Beer <dlbeer@gmail.com>
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Trying to open interface 1 on 017
Initializing FET...
FET protocol version is 30066536
Configured for Spy-Bi-Wire
Set Vcc: 3000 mV
Device ID: 0xf201
Device: MSP430G2231
Code memory starts at 0xf800
Number of breakpoints: 1
Erasing...
Programming...
Writing  306 bytes to f800...
Writing   32 bytes to ffe0...
rafa@rafa-AOA110:~/launchpad/ds2e$

**Attention** This is a public forum