• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 79 subscribers
  • Views 241 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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:

MSP430G2302 Microcontroller fails to load program

MSP430G2302: DCO Calibration

Kyle_B
Intellectual 375 points
Part Number: MSP430G2302
Other Parts Discussed in Thread: MSP-GANG

We’ve programmed a few devices (MSP430G2302IPW14R) and the device is not performing as expected. We confirm the flashed data is correct, but suspected the DCO settings to be culprit.However, I have confirmed with our programming vendor that they’re algorithm doesn’t influence these settings. 


I use our Phyton-G41 manual programmer to program this device and BPM Microsystems once in production. Per Phyton lead engineer, Phytons algorithm doesn’t influence DCO settings because they’re factory set. Can TI confirm this? Also, upon studying the BPM algorithm, there’s no influence on the DCO sector either.

When applying DCO calibration within TI’s gang programmer, the devices function as intended. Should programming have any influence over the DCO calibration? If DCO calibration is not factory set by TI accordingly, how can we tell? Should there be data within address 0x10F8 to 0x10FF?

Thank you,

-Kyle

  • 0
    Guru 88700 points

    There should be data (from the factory) in 0x10F8-FF. Per data sheet (SLAS723H) Table 10, all four CALDCO pairs should be present on the G2302.

    The most common failure mode is for them to be erased (0xFF). My experience is that it's easier to do this (accidentally) than one might think. I don't recall a case where they were present but incorrect.

    Re-generating the constants can be done, but it requires an external clock source (typically a 32kHz crystal). Glancing through the MSP-GANG user guide (SLAU358Q) I don't see an option for doing this, though there are references to preserving them and/or re-writing them from an (externally) saved copy..

  • 0 in reply to Bruce McKenney47378
    Intellectual 375 points

    Thanks!

    That was it, our programming algorithm was erasing/wiping the presets at location 0x10F8. Removing these functions has allowed us to maintain the settings.

    Thanks,

    -Kyle

**Attention** This is a public forum