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.

TMS320F280049: oscillator issue

Part Number: TMS320F280049


Hi team,

My customer is encountering an oscillator circuit issue. For about 10 boards out of ~1000, the XCLK clock cannot be generated properly.

1- They have changed the XTAL and paring caps, does not resolve the issue.

2- Use an active XO, and change the XCLK config, it can work

It is suspected the oscillator circuit inside is damaged, do you have any idea to debug this issue?

Thanks,

Zach

  • Hi Zach,

    Please provide some more details on this issue:

         1.) Is this a new design or is this an existing one and customers just started seeing this issue recently?

         2.) If this is an existing design, is the customer using a crystal that meets the parameters in section 7.9.3.4.7 Crystal Oscillator Specifications of the datasheet?

         3.) What is the active XO referred to above and what is the XCLK config change?

    Thanks and regards,

    Joseph

  • Hi Joseph,

    1}  I am not sure, but I know you may want us to check if any changes made to the board, I'll check with ctm

    2}  Hope you read below parameters of the crystal well, I find something not satisfying the DS, could you check?

    3) That change is from XTAL mode to single-ended input.

    Thanks,

    Zach

  • Hio Zach,

    1) Yes, it is really helpful to know if there is a change in existing design that may affect the operation of th external crystal.

    2) As far as I can tell, the parameters for the customer's crystal choice is in line with the datasheet spec crystal spec requirements for 20MHz.

    3) Good input that clocking works with single-ended mode clock supplied to X1 pin.  At least is validates that the input clock path to the device is working.

    Additionally, did the customer try to do an A/B device swap on a good board/bad board?  This may help tell if there is a board issue or a device issue.  If it is a device issue after A/B device swap then we could start checking the oscillator block to see why it failed on some devices.

    Best regards,

    Joseph

  • ABA is done, issue follows the F280049 chip. Should we initial a FA case?

  • Hi Zach,

    Yes, please initiate FA case with your region's FQE.

    Thanks and regards,

    Joseph