Bernard Mentink schrieb:
> I have tried both the parallel port adapter (original kickstart one ) and a
> the recent MSP-FET430UIF USB adapter, both don't pick up the device in JTAG

i have not have much time to test. a first look at a F5xx seemed to show
that the JTAG id of the device might be different.

the F1xx, F2xx and F4xx should work, but with spy-bi-wire it's a bit
tricky..

try msp430-jtag --help-backend. basically it means my mspgcc backend can
use 4 wire JTAG on spy-i-wire capable CPUs, TI's can't. But the TI
backend can use the USB JTAG that supports spy-bi-wire. it could also
use the 4 wire mode on these devices, but (currently) an option in
msp430-jtag is missing to do that.

> mode. I will try in SBW mode and see if that works. Can you please elaborate
> on what the statement "mspgcc frontend was used instead of default TI"
> means? and what is the "quick-and-dirty adapter" you are refering to?

it means he used --backend=mspgcc which uses a different JTAG
implementation on the PC. however, that one only support parallel port
adapters.

chris

Reply via email to