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.

TMS570LS1115: Clock failure and configurations in MCAL

Part Number: TMS570LS1115

Hi expert,

My customer met a clock failure issue.

For TMS570LS1115 device, Non-AUTOSAR version system.c from TI has some configurations on the MCU. In development process, we find system_init in _c_init00 and some other APIs have overlap with “MCU_init”. When we screen out System_init and some other code, MCU_Init cannot initialize main CPU clock anymore.

Our questions here:

1. Are there any API in cint00 have strong relation to main clock initialization? (in configure sequence or register level).

2. Do we have any user guide regarding how to configure main clock in MCAL?

Thanks

Sheldon

  • Hello Sheldon,

    The MCU initialization should follow the init sequence listed in this application note:

    https://www.ti.com/lit/an/spna106d/spna106d.pdf

    Once the valid bit (CSVSTAT register) is set, software may change values to the PLL. If the change of values results in a small percentage change to the VCO frequency (<10%), then these changes can be done on-the-fly. In this mode, the values are updated into the PLL synchronously, and the PLL re-locks to the new value without gating the clocks or the slip bits. If the operating point change is too large, then the slip bits will be set.

    If the changes to the VCO frequency are large, then the PLL should be disabled prior to changing the values. Typically, any change to the REFCLKDIV field or large changes to the PLLMUL field in the PLLCTL1 requires a complete disable-and-relock strategy.

    One more important thing to pay attention is about changing the trim value. The initial trim value is stored in one-time programmable section of the flash memory, and software reads the initial trim values from flash and write them to the control register. If you run system_init() and MCU_init() on your device, and bother init includes PLL settings and trim setting, please make both init uses the same trim value.