mspdebug icon indicating copy to clipboard operation
mspdebug copied to clipboard
verified publisher icon dlbeer

Unable to use v0.23 with eZ430-RF2500 Dev tool board

Open tdelizy opened this issue 9 years ago • 4 comments

Hi,

Working with a ez430-RF2500 with mspdebug 0.23 I was unable to connect to the target. here is the log:

$ mspdebug rf2500

MSPDebug version 0.23 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2015 Daniel Beer <[email protected]>
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Chip info database from MSP430.dll v3.3.1.4 Copyright (C) 2013 TI, Inc.

Trying to open interface 1 on 014
Initializing FET...
FET protocol version is 30000002
Set Vcc: 3000 mV
Configured for Spy-Bi-Wire
Device ID: 0xf227
fet: unknown device
msg28_data: [0x12 bytes]
    f2 27 50 40 00 00 00 00 00 00 02 02 01 04 a1 61 
    80 00 
Using Olimex identification procedure
fet: missing info
fet: identify failed
Trying again...
Initializing FET...
FET protocol version is 30000002
Set Vcc: 3000 mV
Configured for Spy-Bi-Wire
Sending reset...
Device ID: 0xf227
fet: unknown device
msg28_data: [0x12 bytes]
    f2 27 50 40 00 00 00 00 00 00 02 02 01 04 a1 61 
    80 00 
Using Olimex identification procedure
fet: missing info
fet: identify failed

Tried on v0.22 and mspdebug can connect without facing the issue.

tdelizy avatar Jan 27 '16 15:01 tdelizy

On Wed, Jan 27, 2016 at 07:30:24AM -0800, Tristan Delizy wrote:

Working with a ez430-RF2500 with mspdebug 023 I was unable to connect to the target here is the log:

$ mspdebug rf2500

MSPDebug version 023 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2015 Daniel Beer <dlbeer@gmailcom>
This is free software; see the source for copying conditions  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE
Chip info database from MSP430dll v3314 Copyright (C) 2013 TI, Inc

Trying to open interface 1 on 014
Initializing FET
FET protocol version is 30000002
Set Vcc: 3000 mV
Configured for Spy-Bi-Wire
Device ID: 0xf227
fet: unknown device
msg28_data: [0x12 bytes]
    f2 27 50 40 00 00 00 00 00 00 02 02 01 04 a1 61 
    80 00 
Using Olimex identification procedure
fet: missing info
fet: identify failed
Trying again
Initializing FET
FET protocol version is 30000002
Set Vcc: 3000 mV
Configured for Spy-Bi-Wire
Sending reset
Device ID: 0xf227
fet: unknown device
msg28_data: [0x12 bytes]
    f2 27 50 40 00 00 00 00 00 00 02 02 01 04 a1 61 
    80 00 
Using Olimex identification procedure
fet: missing info
fet: identify failed

Tried on v022 and mspdebug can connect without facing the issue

Hi Tristan,

What's the target chip on this board? Have you tried this with the latest git version?

Cheers, Daniel

Daniel Beer [email protected] http://dlbeer.co.nz/ PGP: BA6E 0B26 1F89 246C E3F3 C910 1E58 C43A 160A 553B

dlbeer avatar Jan 27 '16 21:01 dlbeer

Hi, I was using the 0.23 tag, but I tried out of master today and got the same result. The processor on the board is the MSP430F2274 (the ti board).

here is the log generated from the master built today :

MSPDebug version 0.23 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2015 Daniel Beer <[email protected]>
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Chip info database from MSP430.dll v3.3.1.4 Copyright (C) 2013 TI, Inc.

Trying to open interface 1 on 038
Initializing FET...
FET protocol version is 30000002
Set Vcc: 3000 mV
Configured for Spy-Bi-Wire
Device ID: 0xf227
fet: unknown device
msg28_data: [0x12 bytes]
    f2 27 50 40 00 00 00 00 00 00 02 02 01 04 a1 61 
    80 00 
Using Olimex identification procedure
fet: missing info
fet: identify failed
Trying again...
Initializing FET...
FET protocol version is 30000002
Set Vcc: 3000 mV
Configured for Spy-Bi-Wire
Sending reset...
Device ID: 0xf227
fet: unknown device
msg28_data: [0x12 bytes]
    f2 27 50 40 00 00 00 00 00 00 02 02 01 04 a1 61 
    80 00 
Using Olimex identification procedure
fet: missing info
fet: identify failed

regards, Tristan

tdelizy avatar Jan 28 '16 15:01 tdelizy

Hi tidelizy! Were you able to fix it? I need help! Thanks!

tomexplorador avatar May 28 '16 22:05 tomexplorador

On Sat, May 28, 2016 at 03:26:09PM -0700, tomexplorador wrote:

Hi tidelizy! Were you able to fix it? I need help! Thanks!

Have either of you tried:

mspdebug rf2500 --fet-force-id MSP430F2274

...assuming, of course, that the chip is a 2274.

Cheers, Daniel

Daniel Beer [email protected] http://dlbeer.co.nz/ PGP: BA6E 0B26 1F89 246C E3F3 C910 1E58 C43A 160A 553B

dlbeer avatar May 28 '16 23:05 dlbeer