John Porubek writes:
> On Sat, Jul 10, 2010 at 6:29 PM, Andy Warner <[email protected]> wrote:
> > The 169 doesn't support spy-bi-wire, can you force JTAG mode with a
> > command line switch ?
> >
> > --
> > Andy
>
> Hi Andy,
>
> Thanks for the figurative "whack upside the head"! As often happens, I
> was looking elsewhere and overlooking what was right in front of me.
> There is a command line switch (-j) that forces JTAG mode and using it
> solved my problem. Seems so obvious in retrospect.
>
> I'm still confused about the supported devices issue, however. If the
> '169 I'm working with wasn't on the list of supported devices, would I
> still be having problems?
Hi John,
For each chip, the FET requires a record containing information such
as:
- the extent of info, code and RAM addresses
- the number of available breakpoints
- the type of flash memory controller
- the existence of peripherals which might interfere with debugging
To say that a chip is "supported" means that MSPDebug has in its
database a record of the type described above, plus ID information
(this is fet_db.c). This only applies to versions of the firmware >=
20300000.
In older versions, this database is contained within the FET firmware
itself. This is why old firmware can't be used to debug all
MSP430s.
If you have a newer version of the firmware and MSPDebug doesn't
support your chip, sometimes you can get away with forcing the use of
a record for a chip which is close enough. You just need to ensure
that the memory extent of the chip you select is a superset of the one
you're actually using, because the FET will perform range checks on
flash writes.
Cheers,
Daniel
