• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 81 subscribers
  • Views 287 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.

CCS/TMS320F28031: C2000-GANG DSP CLOCK

Susan Yang
Genius 9955 points
Part Number: TMS320F28031

Tool/software: Code Composer Studio

Dear team,

It says that "The C2000-GANG is using internal 10MHz CLK for programming - regardless your external XTAL frequency."

So how could the customer change the DSP CLOCK in GUI?

I can't select any value of frequency in the GUI. It is fixed at 10MHz.

The customer is using an external crystal oscillator with 20MHz.

Customers can use the internal crystal oscillator to program normally, but the program is configured with an external crystal oscillator and cannot be programmed.

  • 0
    TI__Guru 71785 points

    Susan,

    This is odd.  As you said the GANG should always use the internal clock for these operations since it is 10MHz from the factory.  This eliminates the potential error if customer doesn't remember to change this based on their external clock.

    To my knowledge this frequency check should never fail on these devices; i.e. the internal clock will always be in the 10MHz region and the external clock will not be selected.  This is intended as a safeguard on a device without internal clock if customer does select incorrect frequency.

    Is this an isolated unit, or does customer see this on all devices?  Would it be possible for customer to connect through JTAG with CCS to examine some internal registers?  I'd like to confirm that the device is behaving as expected without the GANG.

    Best,

    Matthew

  • 0 in reply to MatthewPate
    TI__Guru 71785 points

    Susan,

    Looking back at this issue, I have another thread where using Wait Boot mode resolves this issue.  It is caused by a CSM(security module) blocking reads of the clock calibration routines if normal application boot occurs.  Wait Boot should prevent this, and allow the calibration to complete.

    Best,
    Matthew