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.

RM57L843: Errata SSWF021#45 affect the PLL reconfiguring after PLL is locked properly once?

Part Number: RM57L843

I checked the documentation SPNZ233A(Errata for Silion B) and SPNA233A(Herculas PLL Advisory SSWF021#45 ).

They say once the PLL is locked properly, it can be disabled or enabled without any issue.

My question is:

  1. In case that configuring and locking PLL are properly done, if  I disable PLL again and change the values of PLLCTL1/2/3, and then enable the PLL, do I need the workround for SSWF021#45 at this time?
  2. In this topic: https://e2e.ti.com/support/microcontrollers/hercules/f/312/p/554006/2025900, it says the workaround for SSWF021#45 is not 100% guaranteed effective. Is this still true for RM57L843?

  • Hello Canfoderiskii,

    canfoderiskii said:
    In case that configuring and locking PLL are properly done, if  I disable PLL again and change the values of PLLCTL1/2/3, and then enable the PLL, do I need the workround for SSWF021#45 at this time?

    The issue is tied specifically to the first lock after power up. i.e., once the first lock condition happens after power on, you will not see the issue again regardless of which setting in the PLL you change. So, in this case, you would not need to implement the workaround if the PLL had locked previously.

    canfoderiskii said:
    In this topic: https://e2e.ti.com/support/microcontrollers/hercules/f/312/p/554006/2025900, it says the workaround for SSWF021#45 is not 100% guaranteed effective. Is this still true for RM57L843?

    This is still true for the RM57L843 device. Keep in mind that this condition is very detectable and actionable by your application so it does not represent a safety risk since upon detection on power up, the system can be placed in a safe state.

  • thank you for the reply.