• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 83 subscribers
  • Views 390 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

TMS320F280049: PLL May Not Lock on the First Lock Attempt

TMS320F280049: PLL May Not Lock on the First Lock Attempt

Luke Andraka89
Prodigy 85 points

Part Number: TMS320F280049
Other Parts Discussed in Thread: TMS320F28069, , C2000WARE

I have a customer interested in migrating from the TMS320F280049 from the TMS320F28069. The 28069 has been great for them and the 280049 would offer significant improvements. His only concern was the errata titled "PLL: PLL May Not Lock on the First Lock Attempt”. The issue described by this errata (and by answers to questions in the forum) suggests the powerup & initialization time for applications that use the PLL would be non-deterministic. 

  1. Does TI have a silicon revision planned to fix this? I know the part is at revision B but am currious if there is a revision C planned to address this.
  2. Can the likelihood of a failure of the PLL to lock be quantified? What about the likelihood of successive, back-to-back lock failures?

Thank you!

Luke Andraka

  • 0
    TI__Mastermind 44030 points
    Hi Luke,

    There is no silicon rev planned for this errata. Having mentioned that, the errata fix has been very effective in addressing this errata. Please ensure that the customer will use the latest C2000Ware version as there are several checks that ensure the PLL will correctly lock. The fail rate is very low (unfortunately I do not have volume history ready on the TMS320F280049 to establish this and so far we do not have any reports of failures from this fail signature). The behavior of this failure is such that once the PLL locks, it will stay locked for the rest of the application provided that there is no POR since the errata issue is observed only during PLL startup.

    Best regards,
    Joseph