• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 79 subscribers
  • Views 426 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:

MSP430FR2433: DCO Software Trim in extremely cold environments

MSP430FR2433: DCO = 4.9152MHz is unstable after reset in cold environments.

Cruijff
Expert 2760 points

Part Number: MSP430FR2433
Other Parts Discussed in Thread: MSP-EXP430FR2433

Hi community member,

My customer was further verification.
As a result, the same problem occurred in LaunchPad (MSP-EXP430FR2433).

If reset in a low temperature environment (About -35C),
DCO will not oscillate 4.9152MHz even with LaunchPad.
In this case, DCORSEL is 010b.

I would like to know your views on this issue.
Please reply as soon as possible.


Best regards.
Cruijff

  • 0
    TI__Genius 13215 points

    Hi Cruijff,

    Glad to see you again for the discussed issue.

    As we discussed in the original thread, the DCO is out of range under the given temperature. Please find my comments in the original discussion.

    I don't think there are any dependence on the PCB board, unless you use the external crystal for DCO reference, for this issue. So I have no additional comments for the same issue.

  • 0 in reply to Wei.Jetim Zhao
    Expert 2760 points

    Hi wei

    Thank you agein answer my question!

    Please let me know a little more.

    Your comment : [Wei] You shouldn't need to change DCORSEL for temperature changes. DCORSEL=2 should work for you.

    Even if DCOFTLIM and DCO tap were changed, DCO did not oscillate 4.9152MHz with DCORSEL = 2.
    There are a few chip that DCO can oscillate 4.9152MHz with DCORSEL=3 at low temperature.

    As a workaround, the customer designed the software to switch to DCORSEL = 3 if DCO cannot oscillate with DCORSEL = 2.
    Do you think that such measures are effective as a workaround?

    Best regards.
    Cruijff

  • 0 in reply to Cruijff
    TI__Genius 13215 points

    Hi Cruijff,

    That would work for your case with the software re-configuration when the DCO can't lock under DCORSEL = 2. 

    But I would highly recommended to use 1MHz instead of you current frequency, as we discussed before.

**Attention** This is a public forum