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
