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.

Debug -> Flash Settings -> Clock Configuration

Other Parts Discussed in Thread: TMS320F28335

Hello.

Using CCS 5.2.1 and a TMS320F28335.

Under Project Properties -> Debug -> Flash Settings -> Clock Configuration, what is OSCCLK doing?  Is it:

(a) Setting the F28335 internal oscillator (as is reported elsewhere for Piccolo)?

(b) Telling CCS what the external oscillator frequency is?

(c) And if (b), will a wrong value cause any problems?

We have been just accepting the defaults (30 MHz) when programming a F28335, which has never had a matching external source.  And now concerned that we should have matched them.

Regards.

  • Giles Robnson said:
    Under Project Properties -> Debug -> Flash Settings -> Clock Configuration, what is OSCCLK doing?

    Giles,

    It sets the input clock to the device.

    Giles Robnson said:
    (a) Setting the F28335 internal oscillator (as is reported elsewhere for Piccolo)?

    2833x does not have an internal oscillator

    Giles Robnson said:
    (b) Telling CCS what the external oscillator frequency is?

    Yes

    Giles Robnson said:

    (c) And if (b), will a wrong value cause any problems?

    We have been just accepting the defaults (30 MHz) when programming a F28335, which has never had a matching external source.  And now concerned that we should have matched them.

    It could.  The flash API has delay loops that are time critical.  If the clock configuration is incorrect the programming may not be to the proper voltage level.

    Regards

    Lori

  • Thanks - I thought so, but wanted to be quite sure.  We've been having flash problems (other posts), so trying to find all possible causes

    Regards.