> Any ideas?
Just one: Is your programming tool erasing info memory when you flash
your program? If it is, you'll be erasing the calibration values each time
you program a microcontroller, including the first time you program a new
micro.
Michael K.
16 MHz Verification
Started by ●November 16, 2009
Reply by ●November 18, 20092009-11-18
Reply by ●November 18, 20092009-11-18
First try setting calib values direcly (not or'ing):
BCSCTL1 = CALBC1_1MHZ;
DCOCTL = CALDCO_1MHZ;
If needed, do changes in these registers afterwards.
Then you could try to calculate the checksum over all the calib values in INFO_A and check against the stored checksum (if your MSP430 has a TAG_STRUCTURE saved to INFO_A! Check your datasheet for information about this. Checksum calculation is described in the user guide: TLV Structure)
BCSCTL1 = CALBC1_1MHZ;
DCOCTL = CALDCO_1MHZ;
If needed, do changes in these registers afterwards.
Then you could try to calculate the checksum over all the calib values in INFO_A and check against the stored checksum (if your MSP430 has a TAG_STRUCTURE saved to INFO_A! Check your datasheet for information about this. Checksum calculation is described in the user guide: TLV Structure)
Reply by ●November 18, 20092009-11-18
--- In m..., "Michael" wrote:
>
> > Any ideas?
> Just one: Is your programming tool erasing info memory when you
>flash your program? If it is, you'll be erasing the calibration
>values each time you program a microcontroller, including the first
>time you program a new micro.
Yes, this was also my first thought.
But the all calib values should be 0xFF!
>
> > Any ideas?
> Just one: Is your programming tool erasing info memory when you
>flash your program? If it is, you'll be erasing the calibration
>values each time you program a microcontroller, including the first
>time you program a new micro.
Yes, this was also my first thought.
But the all calib values should be 0xFF!