Chris and all,
what I stated below is true: there is an issue with the reset
line. I checked it by monitoring the reset pin.
The code of jtag.py seems to be "quirky" in more than that regard.
If I use -D as parameter, I get following message (amongst others):
_parjtag.configure(DEBUG_OPTION, DEBUG)
AttributeError: 'module' object has no attribute 'configure'
The current jtag.py and _parjtag don't fit together, I suppose.
Ralf
"Ralf Guetlein" <ralf.guetl...@web.de> schrieb im Newsbeitrag
news:bf8rti$u8...@main.gmane.org...
> 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
>
