Dear Ti,
We are getting DCO constant verification failed problem in few msp430f2618 microcontroller. Please check Image for details.
can you tell me how to solved problem.
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Dear Ti,
We are getting DCO constant verification failed problem in few msp430f2618 microcontroller. Please check Image for details.
can you tell me how to solved problem.
I haven't used (nor even noticed) that feature before, but based on the check-box text it appears your InfoA segment has been erased.
Are these brand-new chips? If so, there's really supposed to be something in InfoA.
Are you using the CALDCOxx constants in your program? If not, maybe you don't care.
In a suitable environment, it is possible to re-generate the CALDCOxx constants. There's even a program in the Examples suite for this.
Yes, this happened with new brand chip. 4 out of 50 Nos chip we found such problem.
Can you tell me step wise procedure?
The program is MSP430x261x_dco_flashcal.c, here:
http://dev.ti.com/tirex/explore/node?node=AOxqEmguy.Sf3RhcRFQAQQ__IOGqZri__LATEST
It supposes that ACLK is running from a reliable clock (nominally a 32kHz crystal), and uses timer capture to tune the DCO for each of the calibrated frequencies and then store the results in InfoA.
If your board has a 32kHz crystal, you can run it directly -- it only takes a few seconds. If it doesn't, you have to get creative.
**Attention** This is a public forum