Re: [Mspgcc-users] msp430-jtag error when programming an F2012

[Chris L. <cli...@gm...>]

John Luciani schrieb:
> I am trying to program an MSP430F2012 with msp430-jtag (version 2.0)
> and the Olimex parallel port programmer. I get the following error
> message ---
> 
> An error occoured:
> Can't open interface
> make: *** [jtag] Error 1
> 
> This JTAG setup does program my MSP430F169 board.
> 
> I noticed in the 2012 datasheet that the JTAG TDO and TDI (pin 9) are
> multiplexed. The footnote states that the TDO or TDI function is
> selected by a JTAG instruction. How can I determine if the msp430-jtag
> is sending the appropriate instruction?

thats nothing special to the F20xx the mltiplexed pins are used when the 
security fuse is burnt.

 > Is there anything else that
> needs to be done to program the 2012?

the 2013 works for me. but note that:
- the TI backend (default) does not support spy-bi-wire capable devices 
on the parallel port
- only recent msp430-jtag have support for spy-bi-wire respectiveley 4 
wire JTAG on these devices (in the mspgcc backend)

so you need to upgrade your installation but then you should be able to 
programm with msp430-jtag --backend=mspgcc

spy-wi-wire itself is only supported with the TI USB adapters (or 
compatible) and the TI backend. (there are 3rd party suppliers with give 
you their own MSP430.dll which is compatible or they are compatible on 
the USB side)

newer msp430-jtag have a backend help that prints a table with a 
backend/connection compatibllity matrix (check the "--help")

> The TEST pin looks like it is being set properly. AFAIK this and the
> multiplexed TDO/TDI pin are the only differences between the
> JTAG on the 169 and the 2012.

there are timing restrictions. the pin must be pulsed for less than 
100us so that the 4 wire JTAG is activated, without this it is in the 
spy-bi-wire mode.  the mspgcc backend tries to generate this pulse, but 
the non-realtime of the operation system can not guarantee that it works 
(which means it can fail to get a connection, just retry. for me it 
works most of the time without retries)

chris