• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 89 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.

AM62A7: Clarification on Omission of GPIO1 Safety Mechanism in Section 6.3 of SITARA Safety Manual

Ashish Goyal
Prodigy 30 points
Part Number: AM62A7

Tool/software:

Dear All,

I hope you are doing well.

While reviewing the SITARA Safety Manual i.e. "AM62Ax Functional Safety Manual", I observed that the safety mechanism "GPIO1 - Software Test of Function Using I/O Loopback" or "GPIO2 - Information redundancy techniques" is mentioned under Section 5.17. However, its heading and description are not included in the Safety Mechanism section (Section 6.3).

Could you please clarify the reason for this omission? We would like to understand whether this was a deliberate decision or if the mechanism is covered elsewhere in the documentation.

Your clarification would help us align our safety analysis accordingly.

Thank you in advance for your support.

Best regards,

Ashish Goyal

Functional Safety, 

Valeo, India

  • 0
    TI__Prodigy 200 points

    Hello Ashish,

    It looks like this is an error in the current draft of the AM62A safety manual. We are planning on at least one more update for the safety manual and will add these descriptions in as part of that.

    I have copied our descriptions for GPIO1 and GPIO2 for your immediate use. For GPIO2 another method of information redundancy would be to use 2 different GPIOs to measure a signal.

    GPIO1 On-demand software test of function including I/O checking A software test can be utilized to test basic functionality as well as to inject diagnostic errors and check for proper error response. Such a test can be executed at boot or periodically. Software requirements necessary are defined by the software implemented by the system integrator.

    The GIO module does not support a distinct I/O loopback mode. However, it is possible to support I/O checking using normal functionality. To do this software generates output and reads back and checks for the same value in the input registers. This implements functionality similar to analog loopback in other modules. For best results, any tests of the GIO functionality should include the I/O loopback.
    GPIO2 Information redundancy techniques Information redundancy techniques can be applied via software as an additional runtime diagnostic for this module. There are many techniques that can be applied, such as read back of written values and multiple output of the same data with comparison of results. Error response, diagnostic testability, and any necessary software requirements are defined by the software implemented by the system integrator.

    When the timer is operating in PWM mode, the timer output signal can be connected to one or more GPIO inputs. The GPIO inputs can be configured as interrupts that can be timestamped to provide a check on the pulse widths of the PWM.