Grant Edwards schrieb:
On 2008-01-17, Chris Liechti <[email protected]> wrote:
It never has any problem entering JTAG mode. The problem is
that after the program operation completes, there are almost
always a few bits that didn't get programmed -- they're 1's
when they should be 0's.
oh, so this sounds more like a misconfiguration of the flash controller
frequency.
msp430-jtag tries to adjust the DCO clk. and the code that is run from
RAM uses the MSP430 itself to programm flash using the so adjusted clock.
when the clock adjustment fails is the backend logging a warning and
tries to continue. you should see this warning with "-D"
you should see it adjusting the clock too.
- advertisement - the same clock adjusting code can be used to generate
calibration values, see the "msp430-dco" tool :-)
i've not checked the 2330 data sheet yet. is there something different
in the DCO, cycle count of some basic instructions (that the code
snippet run to determine the speed counts differently) or the flash
controller specs?
wrong flash timing leads to poorly programmed devices, so this would
explain the effects you see.
The problem is that the verify fails: a couple bits (random
locations as far as I can tell) just don't get programmed from
1->0.
so erase seems to work, but not the writes.
chris
