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

AM625: R5F.RAM3 Software readback of written data

Andreas Münich
Prodigy 40 points

AM62x Functional Safety Manual mentions to apply R5F.RAM3 "Software readback of written data" in addition to R5F.RAM1 "Memory ECC" as part of R5F.DiagsRamA. We have some limitations to do this and believe that R5F.RAM1 "Memory ECC" will already provide diagnostic coverage >> 90%.

Limitations include: This is not really feasible for any write access, since it is not suitable for caches, and for TCM it depends on constraints, like compiler settings and implementation of third-party code.

Can you recommend an alternative approach?

  • 0
    TI__Expert 6880 points

    Hello Andreas,

    Agreed that R5F.RAM3 is not easily feasible considering caches. This diagnostic is considered optional as long as you have R5F.CPU1F which is R5F diagnostic library implemented (which can test for both R5 core and memories). Basically this diagnostic is used to detect latent faults in the memories as per ASIL-B requirements. Hardware PBIST is not supported on DM R5 memories which is why R5F.RAM3 or R5F.CPU1F is needed.

    Regards,
    Neelima