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

CCS/TMDXRM46HDK: For ADC1 and ADC2, how do we detect specific faults that would not impact both

NeilBerry_at_Parker
Expert 1995 points

Part Number: TMDXRM46HDK

Tool/software: Code Composer Studio

I was able to find fault detection for open point and shorted point.  Faults like those would appear on both ADC1 and ADC2 (when points are shared).

How do we detect faults that would let us select one source of values over the other (ADC1 versus ADC2)?

  • 0
    TI__Guru 72500 points
    When the converted values from the two ADC disagree you can first verify if both values are within the expected range. If you don't have an expected range limit, or if both values are within the expected range, run the ADC diagnostics on both converters.
  • 0 in reply to Bob Crosby
    Expert 1995 points

    From the RM44 manual there might be some tests to discover specific faults.  Reading in the configuration and discovering that either ADC1 or ADC2 no longer had a matching configuration would be a possible case.  If anyone can think of other valuable test results from the option below, let me know. 

     

    The following tests can be applied as diagnostics for this module (to provide diagnostic coverage on a

    specific function):

    • Hardware Disable of JTAG Port

    • Boot Time Input Self-Test

    • Boot Time MibADC Calibration

    • Periodic MibADC Calibration

    • MibADC Information Redundancy Techniques

    • MibADC SRAM Data Parity

    • Boot Time PBIST Check of MibADC SRAM

    • Periodic PBIST Check of MibADC SRAM

    • Bit Multiplexing in MibADC SRAM Array

    • Periodic Hardware CRC Check of MibADC SRAM Contents

    • Periodic Software Readback of Static Configuration Registers

    • Software Readback of Written Configuration

    • Boot Time Software Test of Function Using I/O Checking In GIO Mode

    • Periodic Software Test of Function Using I/O Checking In GIO Mode

    • Information Redundancy Techniques (while in GIO Mode)

    The following tests can be applied as a test-for-diagnostic on this module, and could be used to meet

    Latent Fault Metric Requirements of ISO26262 (in combination with other diagnostics on the primary

    function):

    • Software test of Parity Logic

    • PBIST Test of Parity Bit Memory

    • Software Test of Hardware CRC

    • CRC Auto-Coverage

    • Software Test of PBIST

    • PBIST Auto-Coverage

    • Internal Watchdog

    • External Watchdog

    • CPU Lockstep Compare

    • Flash Data ECC

    • RAM Data ECC