• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 32 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.

AM263P4-Q1: Implementing STC to perform LBIST

Carwyn Griffiths
Prodigy 80 points

Part Number: AM263P4-Q1

Tool/software:

Hi,

I am currently looking at using the STC module to perform LBIST as part of our start-up routine. My understanding from the example in the SDL library is that the CPU under test will be reset after the STC has finished it's checks. So, if using two cores in lockstep then it will be necessary to reset the core running software as part of the start-up and then check the cause of the reset was STC and then the status of the STC registers after this. 

Is there a way to run the STC without resetting the CPU after or is this the only way the tests can be performed?

Thanks,

Carwyn

  • 0
    TI__Guru* 76006 points

    Hi Carwyn,

    Apologies for the delayed response!

    1. The CPU reset after STC/LBIST completion is a designed behavior. This is because the STC stands for CPU self-test controller and uses the deterministic Logic Built-in Self-Test (LBIST) Controller as the test engine to provide very high diagnostic coverage on the lockstep CPUs.

    2. For lockstep operation, this reset behavior is actually important because:

      • It ensures both cores start in a known clean state after the test

    3. The recommended approach for handling this in your startup routine is:

      • Execute the STC test
      • Wait for the reset to occur
      • After reset, check the reset cause to verify it was from STC
      • Check the STC status registers to verify test results
      • Continue with normal operation if tests passed

    --
    Thanks & regards,
    Jagadish.