Chris, it's a x149 with MSP430P140FET, dedicated JTAG pins.
Some additional experiences: If I do a "jtag.py -Iepvr out.hex", and jtag.py managed to succeed (i.e. no error msg), the program isn't started. If I then give a "jtag.py -r" this described error message occures but the controller starts running... funny! My guess is: jtag.py leaves the reset line (or another one crucial for starting) applied, if it succeeds. If there is an error, the reset (or other) line is released, which starts the MSP. (or something alike) In any case, it seems that jtag.py does a bad job when initializing. For example, the first run of jtag.py after using C-SPY *allways* works! Any ideas? Ralf "Chris Liechti" <cliec...@gmx.net> schrieb im Newsbeitrag news:3f17e4b0.1070...@gmx.net... > Ralf Guetlein wrote: > > jtag.py works only once every second time i invoke it, no matter what > > parameters used. > > one of two tries (on a very regular base) end up with a message like: > > "Can't open interface" > > that means that the JTAG connection to the target failed. it could not > reset the target. > > > my configuration: > > Windows XP > > Python 2.2.3 > > jtag.py fresh from cvs > > thats fine > > > Anybody there go give an answer? > > works fine for me... > > check the JTAG connections. is it a F1xx with multiplexed data/JTAG > pins, if so can the JTAG interface drive the load on that pins? > do you have a separate power supply for the target? > > chris > > > > ------------------------------------------------------- > This SF.net email is sponsored by: VM Ware > With VMware you can run multiple operating systems on a single machine. > WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the > same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
