• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 391 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.

checkClockMonitor() and erratum SYS#46

Thomas Weber
Intellectual 680 points
Other Parts Discussed in Thread: HALCOGEN, TMS570LS3137

Hello,

in sys_selftest.c checkClockMonitor() the clock domain is switched to HF LPO. As described  in erratum SYS#46 the CSDIS and CSVSTAT registers should be checked that the clock is turned on. Is it in checkClockMonitor() not necessary?

Best regards,

Thomas Weber

Code is generated by Halcogen 04.05.01

Processor is TMS570LS3137

  • 0
    TI__Guru**** 191736 points
    Hi Thomas,
    If you are using the checkClockMonitor() diagnostic in your application then it makes sure that after the test it will wait for OSC to be valid before switching back to the OSC as a clock source. However, for users who do not use this diagnostic test or they intend to switch betwen clock sources per their application, the SYS#46 is still valid.