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.

AM62P-Q1: WIR Cert compare with Normal Debug Cert

Part Number: AM62P-Q1

Hi TI expert,

We received the CPR document (Sitara MPU Customer Returns) from TI, and have some open items need to claify.

It mentioned, we have to generate a WIR Cert to unlock the JTAG for ATE test.

We checked the WIR Cert data structure, it is similar with normal debug cert:

– [ debug ]

– debugUID = FORMAT:HEX,OCT:

– debugType = INTEGER:4

– coreDbgEn = INTEGER:0

– coreDbgSecEn = INTEGER:0 

But only the debugType set to 4 (Full), and also use the same Customer keys to sign it.

Q:

  1. What about the difference with normal debug Cert? except halt the cores in reset.
  2. How to send this WIR Cert? also use dbgauth.exe command?
  3. If the TIFS cannot bootup, then whether it can accept the WIR cert to unlock?
  • The security override mode enable access to the device via JTAG in order to run production functional test and bench tests for failure analysis.

    An unlock certificate is processed by ROM once entering the WIR security override mode. Once authenticated, the following actions are enforced by ROM.

    1/. Lock secure assets to equivalent of GP device:
    - Clear secure RAM
    - Lock secure ROM access
    - Lock access to OTP fuses
    2/. Enable access to device via JTAG

    Best,
    -Hong

  • Thanks

    So the WIR Cert will be handled by ROM during bootup stage? then how to send the WIR Cert into target?

    As I known, the normal debug Cert will be handled by TIFS at running time. 

    B.R

  • ROM enters WIR security override mode when EMU0=0/EMU1=1 at POR.
    The unlock certificate is sent over SAP via JTAG debugger, and the unlock certificate is processed by ROM

    Best,
    -Hong