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

TMS570LC4357: RAM13: How to test parity logic of RAM

TMS570LC4357: RAM13 Triggers EMS 3.15 as well as 2.17 and data abort

Max Wittekind
Expert 1875 points
Part Number: TMS570LC4357

Hi experts,

When running the RAM13 diagnostic, we expected ESM 3.15 to be triggered.
But we also see a ESM 2.7 and a data abort.

(Q1) is this the expected behaviour of this test?

Thank you and best regards,
Max

  • +1
    TI__Guru**** 196856 points

    Hi Max,

    Max Wittekind said:
    (Q1) is this the expected behaviour of this test?

    Yes, it is the expected behavior.

    When the ADDR_PARITY_OVERRIDE = 0xA, the parity scheme is inverted and the address checker will work on the inverted parity scheme.

    The default parity scheme is ODD which is defined in DEV Parity Control Register 1 (DEVCR1).

    Inverting the parity will generate command parity error (ESM 2.7)  and address/control parity error (ESM 3.15).