• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 377 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.

TMS570LS3137: SPNU511D safety manual para. 7.2: Bit Error Detection

Chuck Wong
Genius 3950 points

Part Number: TMS570LS3137

Hello,

In the safety manual 7.2, it is written that:

When this module transmits information onto it's bus, it can also monitor the bus to ensure that the transmitted information is appearing as expected on the bus. If the expected values are not read back
from the bus, the hardware can flag the error and signal an interrupt to the CPU. This feature must be enabled and configured in software.

Some questions to help me understanding:

1) Which module?

2) The HW can flag which error and signal which interrupt to the CPU?

3) Where to enable this feature?

4) What should the application do following such error?

Thank you!

  • 0
    TI__Mastermind 49120 points
    Hi Chuck,

    See answers/comments below:

    1) Which module?
    >> This is a general description of what the "Bit Error Detection" diagnostic mechanism includes. Further sections include specific description of the mechanism in the communication modules that support this.

    2) The HW can flag which error and signal which interrupt to the CPU?
    >> e.g. MibSPI has a mechanism to continuously compare its output to the expected value. A mismatch is flagged as a bit error (BITERR) and generates an interrupt to the CPU, if enabled.

    3) Where to enable this feature?
    >> It needs to be enabled in each individual module that supports this. The comparison is always enabled, the interrupt signaling needs to be enabled.

    4) What should the application do following such error?
    >> This is application dependent. For example, a bit error from the MibSPI means that the data on the pin does not match what was sent from the data buffer. This could be a result of incorrect output multiplexing, or an actual fault in the hardware.

    Regards,
    Sunil
  • 0 in reply to Sunil Oak
    Genius 3950 points
    Hi Sunil,

    So it is what I was thinking, a general safety mechanism built into the MCU, but its description raises questions, as many other within this SPNU511D safety manual, which lead us to countless hours of searching through many documents in search of answers.

    As subjects described in chapter 7 are not categorized at all, it is extremely difficult to find our way through it, especially when trying to associate a given error to its applicable ESM channel ... suggest TI to improve this manual.

    Best regards.