• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 163 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS570LC4357: Error forcing Test of Checker CPU Inactivity Monitor triggers ESM 2.26

Max Wittekind
Expert 1835 points
Part Number: TMS570LC4357

Hi experts,

When testing our implementation of the Checker CPU Inactivity Monitor "Error Forcing Test" we would expect a ESM 1.31 and 2.2 Error.
Instead we get a EMS 1.31 and 2.26. ESM 2.26 would be a "CPU1 AXIM Bus Monitor failure".

(Q1) Is this the expected behavior when running this test?

Thank you and best regards,
Max

  • 0
    TI__Guru 58380 points

    Hi Max,

    Max Wittekind said:
    (Q1) Is this the expected behavior when running this test?

    This is expected behavior only, because Checker CPU Inactivity Monitor test doesn't involve any comparison between both CPU's bus signals. In this test, several key bus signals such as the bus valid control signals from the checker CPU are validated against their clamped safe values.

    So, in this test we will get EMS 1.31 and 2.26(CPU1 AXIM Bus Monitor failure) only.

    And the ESM 2.2(CCM-R5F - CPU compare) will get trigger in CPU/VIM Output Compare Diagnostic test because in this test the bus signals of both CPU's are compared.

    --
    Thanks & Regards,
    Jagadish.