• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 242 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:

SRAM_RADECODE_DIAGNOSTICS will trigger ESM interrupt？

Questions about SRAM RADECODE DIAGNOSE for TMS570LS3137?

zhang xiaohong
Intellectual 730 points

When calling the SRAM diagnostic interface and diagnosing SRAM_RADECODE_DIAGNONISTCS, there are two questions as follows:

(1) When the redundant address decoding diagnosis is called, the interrupts of 2.6 and 2.8 should be generated, but when I tested it, no interrupt was generated. What could be the reason?

(2) For the following code, when the equality and inequality tests are performed, the check conditions of the diagnostic results are different, one is or |, and the other is & &, is it a problem with the diagnostic library code? thanks

  • +1
    TI__Guru**** 200256 points
    zhang xiaohong said:
    (1) When the redundant address decoding diagnosis is called, the interrupts of 2.6 and 2.8 should be generated, but when I tested it, no interrupt was generated. What could be the reason?

    After the selftest, are ESM2.6 and ESM2.8 set? If those two bits are set, the ESM high interrupt should be generated. By the way, is the IRQ enabled?

    zhang xiaohong said:
    (2) For the following code, when the equality and inequality tests are performed, the check conditions of the diagnostic results are different, one is or |, and the other is & &, is it a problem with the diagnostic library code?

    For equality test:

    • If the comparator matches (no true silicon fail), there is no status bit set for ADDR_COMP_LOGIC_FAIL or ADDR_DEC_FAIL.
    • If there is true silicon malfunction, ADDR_COMP_LOGIC_FAIL and ADDR_DEC_FAIL will be set.

    For inequality test, the compare vector will not match since non-inverted and inverted values of the same test vector are fed to the comparator:

    • If there is a silicon malfunction on any of the comparator bits, then, ADDR_COMP_LOGIC_FAIL and ADDR_DEC_FAIL will be set. 
    • If there is no silicon malfunction on any of the comparator bits, then only ADDR_DEC_FAIL will be set. This is why the AND is used.