Hi,
Here it is:
mspdebug uif -d /dev/ttyUSB1 --fet-force-id foo
MSPDebug version 0.10 - debugging tool for MSP430 MCUs
Copyright (C) 2009, 2010 Daniel Beer <dan...@tortek.co.nz>
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 UIF on /dev/ttyUSB1...
Initializing FET...
FET protocol version is 20405003
Configured for Spy-Bi-Wire
Set Vcc: 3000 mV
Device ID: 0xf227
fet: unknown device
msg28_data: [0x1a bytes]
f2 27 50 40 00 00 00 00 00 00 02 02 01 04 a1 61
82 00 89 00 00 00 00 00 00 00
fet: identify failed
On 10.08.2010, at 2:22, Daniel Beer wrote:
> On Mon, Aug 09, 2010 at 05:59:11PM +0300, Andres Vahter wrote:
>> I got msp430f2234 working with mspdebug 0.1
>> It has less RAM and flash than f2234 so it has different start and stop
>> adresses.
>> I made a new .name called MSP430F2234 to fet_db.c, so i can use
>> --fet-force-id MSP430F2234:
>
> Hi Andres,
>
> This looks good -- but we can go slightly better and get the ID data
> so that you don't need to use --fet-force-id. If you try this:
>
> mspdebug [usual options ...] --fet-force-id foo
>
> Or anything in place of "foo" that doesn't actually name a chip. This
> will cause MSPDebug to think it doesn't recognise the chip and it'll
> dump the ID data on stdout. If you post this on the mailing list we
> can put together a patch which will identify and support the 2234
> without any special options.
>
> If you get this data as well, I'll add the patch to the main
> repository.
>
> Thanks and regards,
> Daniel
