• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 606 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: Force a March13N failure?

ngohara1991
Intellectual 555 points
Part Number: TMS570LS3137

Hello, 
I am working on some Software Requirments Verification for our TMS570 product, and I would like to know if there is any way to force a March13N algorithm failure, either with code, register settings, or debug mode in Code Composer?
Thank you for any advice or reference material.

  • 0
    TI__Guru 59540 points
    Hello ngohara1991,

    Unfortunately, there is no way to force an error with the PBIST controller. The strategy that we rely on is the testing of the PBIST ROM pattern to insure validity of the PBIST Controller operation. A similar answer can be seen in this post: e2e.ti.com/.../480767
  • 0 in reply to Chuck Davenport
    Intellectual 555 points
    Hello Chuck,
    Could you please point me to a reference that I could study to understand your "test the PBIST Controller" method?
    That may work for our needs, but I need to understand this all better first.

    Thank you for any assistance.
  • 0 in reply to ngohara1991
    TI__Guru 59540 points
    Hello Ngohara,

    The documentation on this is really based on the understanding of PBIST, ROM and the March13N algorithm.

    Essentially, the algorithm is writing a value to a RAM location and reading it back. If there is a mismatch, then an error is generated.

    Since the prescribed solution is to run the March13N algorithm on a ROM location, the March13N algo is unable to write to these locations (it's ROM) and the readback results in a mismatch between what the algo thought it wrote and what is read back. The end result is a PBIST error generation just like would happen if there were a similar failure in one of the RAMs under test. From this point, your software handler should react tot he PBIST ESM error as if it were a true error.