hi,
i think that i may have found a bug during erase and program
verification in the jtag library's read-back routine, and before i try
to fix it, i thought that i'd ask if this is a known problem.
specifically, the comparison in jtag.py after the memread after either
an erase or a write is throwing an exception, indicating that the
erase/write was bad, or, more likely, the read is corrupted.
my environment:
mandriva 2006.0 updated
kernel 2.6.16.9
gcc 4.0.1
python 2.4.1
msp430f1611, on two different platforms.
i built the tools from source; the code came from a cvs checkout last week.
one thing that i note in the code is that MSP430_Memory uses signed
chars storing the results of calls to ReadMem; aren't unsigned chars
warranted here? it seems that 0x3fff is coming back instead of 0xffff...
i've taken a cursory look at the mail archives, but have not found a
reference to this.
thanks,
steve ayer
