• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 97 subscribers
  • Views 577 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.

TDA4VM: POK: Self Diagnostic

Zhihua Ding
Intellectual 460 points

Part Number: TDA4VM

Hi, TI

I am working on the safety mechanism "POWER-T1 - Software Test of POK monitor".  The general test step is as follow:

1. Set wrong threshold value by trim bits

2. Check if the error status is set in register "PRG_STAT"

3. Clear the error status by set bit "POK_CLR" in register "PRG_STAT"

But after set "POK_CLR" bit, when repeat the testing, we can't detect the error anymore.  Is that any special steps should be performed after set "POK_CLR" bit?

Thank you!

Zhihua

  • 0
    TI__Guru*** 125941 points

    Hi Zhihua,

    The overall programming sequence can be seen in the TRM as below.   As an UV or OV is not expected, the generated ESM reported, would likely trigger some follow up safety action.

    If you follow through the full sequence again, does a 2nd run of the POK test work?

    Regards,

    kb

  • 0 in reply to KB
    Intellectual 460 points

    Hi KB,

    Yes, I fully follow up the sequence, and 2nd run of POK test doesn't work. 

    Do you mean I can't get the POK status from "PRG_STAT" and I shall use ESM to catch the error status?

    Thank you!

    zhihua

  • 0 in reply to Zhihua Ding
    TI__Guru*** 125941 points

    Hi Zhihua, 

    TI recommendation for POK, is to follow the pok example, documented in SDL_RLS_01.00.00/sdl/sdl_docs/userguide/j721e/examples/pok.html

    In this example code the ESM error event is used to indicate pass/fail, for UV/OV tests.    The CTRL_MMR_STAT is not used in determining POK status.   Please note that CTRL_MMR_STAT register is currently under investigation by TI.

    The sample output shown in pok.html, reflects what is being seen in TI local testing.

    Regards,

    kb