Arnd-Hendrik Mathias wrote:
Hi and thanks for the info. The Version of msp430-gdbproxy is indeed the
one from ftp.opencall.org with creation date July 22nd 2004. The other
date is only the one I receive as response to "monitor version". I also
checked "monitor vcc" but according to the msp's user's guide the 3.0V
should be enough. I increased it a bit:
>monitor vcc 3.3
>monitor erase info
with the same result:
Could not preserve/restore device memory (12)
I don't understand why.
actualy , you can set it to any voltage != 0 and get the same result ;-)
the HIL.dll we use does not set individual voltages, just on/off. thats
becasue the parallel port adapters that are commonly used do not support
setting the voltage. (but the tools support it, in case a future adapter
supports it, just the HIL.dll has to be changed)
instead, you should check the supply on your board. you need around 5mA
at >2.7V. it works best if the JTAG adapters voltage matches the VCC on
your board.
also, some voltage supervisors/reset devices can cause trouble if they
reset the mcu when there are current spikes/voltage drops.
i have a shottky diode from the JTAG apdaters VCC to pin 2 on the JTAG
connector which is used to back up the VCC on the target. but i have
boads that start up with a current limit of a few hundret uA,
programming these does only work with external VCC backup...
chris
