Re: [Mspgcc-users] trouble with the launchpad

Yama Ploskonka Sat, 03 Nov 2012 08:43:56 -0700

I just remembered I had some non-recognition issues early on with thepreinstalled 2553 MSP430 chip, it had to do with what version ofmspdebug I was using at the time.

You say you have 0.20, IMHO that should deal with most anything, butjust for the maybe value, to try what "worked" for me, try switching thechips in your launchpad, put the older one (2452, in a plastic baggie)instead of the 2553 that comes pre-installed, and see. That was actuallymy first "breaktrough", early on.

I nowadays use the 2553s very seldom, as I am developing mostly with14-pin chips.

Still, sometimes the mspdebug will deny there is a Launchpad there,usually after me plugging and unplugging several times in the samesession, worst if I did not quit mspdebug cleanly (Ctrl-D) beforeunplugging. One of my computers even sometimes goes so bad as even messup keyboard access.

A reboot gets me back on track - I hate rebooting, Linux people do, butI am a noob, and I must live with it... :-)



On 11/02/2012 11:31 PM, Alex Burka wrote:

Hi Daniel,

Thanks! Unfortunately, that did not fix the problem. There is a little bit of extra output now when 
mspdebug starts (in between "Number of breakpoints: 2" and "Chip ID data: 25 
53"):
fet: FET returned NAK
warning: device does not support power profiling


But then the behavior is the same as before :(

Alex


On Wednesday, October 31, 2012 at 3:19 PM, Daniel Beer wrote:

On Tue, Oct 30, 2012 at 11:04:02PM -0400, Alex Burka wrote:

I apologize if this is a common issue, but I can't seem to find anything. I'm using 
mspgcc (LTS) and mspdebug 0.20 on Mountain Lion with the Launchpad (MSP-EXP430G2). The 
board is fresh out of the box, and it did start to blink the LEDs when I plugged it in. I 
wrote my own little blinking program and ... it doesn't work. It appears to program to 
the device, but then it won't run. mspdebug says "FET returned error code 17 (Could 
not run device (to breakpoint))".
Output and code are here (https://gist.github.com/3984520). As you can see, at first mspdebug fails to find the device, which is sort of worrying (this does not happen every time), but then it succeeds and claims to write the program. However, "run" fails, and nothing happens when I quit mspdebug either, or hit the reset button on the Launchpad.The only thing I've found is that perhaps I need to update my firmware (http://processors.wiki.ti.com/index.php/MSP430_LaunchPad_Firmware_Update)? But some comments on that page say that it bricks the Launchpad.

It's possible that there's a problem with mspdebug's chip database. If

you fetch the latest git version of mspdebug and apply the patch below,
does it work? Note that you might have to replug the Launchpad before
trying the patched version:

diff --git a/drivers/fet_db.c b/drivers/fet_db.c

index 3bcd2fe..c88cb6c 100644
--- a/drivers/fet_db.c
+++ b/drivers/fet_db.c
@@ -1467,7 +1467,7 @@ static const struct fet_db_record fet_db[] = {
/* extra: 89 00 00 00 00 00 00 00 */
},
.msg29_params = {0x00, 0x39, 0x31},
- .msg29_data = { /* Copied from MSP430G2452, with changes */
+ .msg29_data = {
0x00, 0xc0, 0xff, 0xff, 0x00, 0x00, 0x00, 0x10,
0xff, 0x10, 0x40, 0x00, 0x00, 0x02, 0xff, 0x03,
0x00, 0x00, 0x00, 0x00, 0x02, 0x00, 0x01, 0x00,
@@ -1475,14 +1475,14 @@ static const struct fet_db_record fet_db[] = {
0x08, 0x07, 0x10, 0x0e, 0xc4, 0x09, 0x70, 0x17,
0x58, 0x1b, 0x01, 0x00, 0x03, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00,
- 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
- 0x00, 0x00, 0x00, 0x00, 0x33, 0x0f, 0x1f, 0x0f,
+ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
+ 0x00, 0x00, 0x00, 0x00, 0x33, 0xff, 0x1f, 0xff,
0xff, 0xff
},
.msg2b_len = 0x4a,
.msg2b_data = { /* Copied from MSP430G2452 */
- 0x00, 0x0c, 0xff, 0x0f, 0x00, 0x02, 0x02, 0x00,
- 0x08, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
+ 0x00, 0x00, 0x00, 0x00, 0x00, 0x02, 0x00, 0x00,
+ 0x02, 0x00, 0x40, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,



------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d


_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d

_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

Re: [Mspgcc-users] trouble with the launchpad

Reply via email to