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.

AM2432: How to configure the input clock frequency for a peripheral

Part Number: AM2432
Other Parts Discussed in Thread: SYSCONFIG

In order to configure an input clock for a peripheral, take OPSI for example, the input clock could be set to be either 200 MHz or 166 MHz, based on ti's SDK example. I have a few questions regarding how to configure the input clock:

1) Is there a document available that provides the supported input clock for each peripheral?  

2) In order to change the input clock, take OSPI as an example, if we would like to use 200 MHz as its input clock, do we need to change both SBL and our app project?  Is there a hard-coded value in SDK that would prevent this re-configuration?

Thanks a lot,

Hong 

  • Hello Hong,

    1) Yes, this information is contained in the module integration diagram/tables in the device TRM. There is a OSPI Clocks table that describes clock source options.

    2) This depends on your use case, if system uses OSPI as SBL source, then it will need to be changed in both places. If the OSPI is being used as secondary application memory, then it only needs to be defined the user application code. There isn't a hard-coded value in the SDK, instead it is dynamically generated from the provided SysConfig values.

    Best Regards,

    Zackary Fleenor

  • Hello Zackary,

    Thank you very much for the information. Have a follow-up question as below: 

    1) In our use, we use OSPI as SBL source and OSPI is also being used as secondary application memory, I understand the OSPI interface needs to be defined in both SBL and application code.  For SBL and application code these two projects, could the input clock be different? Like one is set to be 200 MHz, and the other is set to be 166 MHz.

    Thanks a lot,

    Hong

  • Hello Hong,

    As long as the OSPI IC configuration/control is properly implemented to support operating at both frequencies, then it should be okay to define these values differently for SBL and Application code.

    Best Regards,

    Zackary Fleenor

  • Hello Zackary,

    Thanks a lot for the information.

    Hong