• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 81 subscribers
  • Views 444 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

MSP430G2231: MSP430G2231

MSP430G2231: MSP430G2231

Tanujakshi Byakod
Prodigy 30 points
Part Number: MSP430G2231


Dear Team,

          I need one clarification on MSP430G2231 clock configurations, We are using CALDCO_12MHZ micro with  MSP430G2231 by including msp430x20x2.h header file, which is not supposed to be used as this micro is not defined for MSP430G2231, but the confusing part is, our firmware is working fine most of the time with this clock configuration, only sometime we are facing the issues.

          I want to know that if  CALDCO_12MHZ is not valid for MSP430G2231 , how come its working ?? and which value is it taking for CALDCO_12MHZ ?? and May I know the values of CALDCO_12MHZ  and CALDCO_1MHZ (memory contents).

Thank You In Advance,

Tanuja.

 

  • 0
    TI__Mastermind 23275 points
    Hi Tanuja
    Compared with page 16 of SLAS491I (device MSP430F20x3 DS), CALDCO_12MHZ is available on 12 MHz DCO Calibration Data
    Checked in page 12 of SLAS694J (MSP430G2x31, MSP430G2x21 DS), there is no CALDCO_12MHZ. only CALDCO_1MHz is available.
  • 0
    Guru 100705 points
    1) Try using the debugger to read the word at 0x10fa [Ref User Guide (SLAU144J) Table 24-1]. If it's not 0xFFFF, there may have been calibration constants put there "accidentally" in manufacturing but who knows if they're truly calibrated. I'm pretty sure 0xFF for DCO/BC1 run your MCU out of spec (too fast).

    2) If you have a 32kHz crystal, you can use msp430g2xx1_dco_flashcal.c from the Examples suite (SLAC463G, from the Tools and Software tab on the Product page) to generate the missing calibration constants. No one can tell you what the "correct" values are for your physical chip.
  • 0
    Genius 4350 points
    Are you also writing the CALBC1_12MHZ value to BCSCTL1? If not, then you are still in the 1MHz range. If you are using both CALDCO_12MHZ and CALBC1_12MHZ, and both are 0xFF, then I would be surprised if it works at all since you would be well above 16 MHz. Typical values for CALDCO_12MHZ and CALBC1_12MHZ would be 0x7C and 0x8E. The latter determines the range. It's usually 0x86 for 1 MHz, 0x8D for 8 MHz, 0x8E for 12 MHz, and 0x8F for 16 MHz.

**Attention** This is a public forum