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.

MSP430F5659: XT2 Crystal Issue

Part Number: MSP430F5659
Other Parts Discussed in Thread: MSP430F5635

Hi team,

Building off the related post, we're working on bringing up a MSP430F5659. We had it working with a 16MHz crystal, but when we switched to a 20MHz crystal we begin having issues. The device starts, but then the code jumps around.

We tried replicating the same crystal change on a board with a MSP430F5635, but didn't have this issue.

Is there anything in the MSP430F5659 that would cause an issue when changing the crystal?

Thanks,

Jacob

  • Hi Jacob,

    First, lets look at any differences between the F5659 and F5635 that might explain this behavior.
    We know the F5659 and F5635 share the same XT2 crystal oscillator design so...
    1. Are the load caps used for the F5659 XT2 circuit the same value used for the F5635 XT2 circuit?
    2. Are there any differences in the PCB layout between the F5659 and F5635 around the XT2 crystal?
    3. Are the clocks and PMM configured in software exactly the same for the F5659 and F5635?

    Next, let's look at the F5659 configuration
    4. What is the VDD?
    5. Is the PMMCOREV voltage setting at level 3?
    6. If instead of using XT2, if the F5659 is operated using the DCO configured for 20MHz, is the same behavior observed?
    7. Is this behavior present when operating in both debug mode (with debugger) and normal (without debugger)?

  • Thanks Dennis!

    They said that the 5635 and 5659 are running on identical boards - one with each device.

    Both run at 16 MHz, same code.

    Change crystal to 20 MHz and 5635 works fine as expected but 5659 struggles getting crystal started and cannot set vCore.

     UCSCTL6 is set to  (XCAP_3 + XT2DRIVE_2 + XT1DRIVE_3)

    I've asked regarding the F5659 configuration. Hopefully will have their responses soon.

  • This is closed and the thread continues on TI internal forum.

**Attention** This is a public forum