• State Resolved
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 3 replies
  • Subscribers 32 subscribers
  • Views 244 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.

AM2432: Diagnostic measures for the software readback of written configuration

Jimmy
Prodigy 180 points
Part Number: AM2432

Tool/software:

Hi

We are implementing security diagnostics for the CBASS and R5F modules, which involve the 'Software Readback of Written Configuration' diagnostic procedure. However, when utilizing these features, we did not perform additional configurations on the registers of these two modules, hence making it impossible to execute this diagnostic procedure.


During the initialization phase, we carried out a 'Periodic Software Readback of Configuration Registers' diagnostic measure. Could this replace the 'Software Readback of Written Configuration' diagnostic measure?


Thank you

Jimmy

  • 0
    TI__Guru 68920 points

    No these are two different diagnostics.  Please see chapter 6 of the safety manual for the description of each.

    6.3.139 Periodic Software Readback of Static Configuration Registers

    versus

    6.3.179 Software readback of written configuration

    The first is done periodically,  the 2nd is done every time the MMRs are updated.

  • 0 in reply to Anthony F. Seely
    Prodigy 180 points

    Hi 

    In our application, we have not reconfigured the control registers for the CBASS and R5F modules. Can we skip the Software readback of written configuration diagnostic procedure?

    Thank you

    Jimmy

  • +1 in reply to Jimmy
    TI__Guru 68920 points

    If the IPs are being used, even if the registers are in a default state a soft error could occur in the MMRs.

    You would need to model that loss of transient fault coverage in the FMEDA to determine if you are OK with it,  by using a customer defined diagnostic on those items that has 0% transient coverage and seeing how it impacts the results you get.