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.

TPS65381-Q1 Behavior of DIAG_EXIT bit(No.139)

Other Parts Discussed in Thread: TPS65381EVM

0842.N0.139.pptxHello,

Please answer following question.

 

Q1:

I want to know the behavior of TPS65381 with following operation.

1)    Set DIAG_EXIT=0 and DIAG_EXIT_MASK=1 in DIAGNOSTIC state.

2)    Set DIAG_EXIT_MASK=0

3)    Dose TPS65381 go to SAFE state or stay DIAGNOSTIC state?

 

Q2:

I tried to test above operation using TPS65381EVM but I could not set DIAG_EXIT=0 in DIAGNOSTIC state. ( I cricked DIAG_EXIT field but it returned to checked as below.)

Please advise why I could not set DIAG_EXIT=0.

 

Cleared ERR_FAIL and WD_FAIL flags are set after set DIAG_EXIT=0 (SPI_WRITE 0x49 ; 0x16).

Please advise why these flags are set.

Best Regards.

  • 1)       Set DIAG_EXIT=0 and DIAG_EXIT_MASK=1 in DIAGNOSTIC state.

    1. Under these conditions device remains in DIAG state
    2. After 600 ms in DIAG state, DIAG state time out event occurs -> ERR_FAIL and WD_FAIL status flag bits to be set to ‘1’

     

    2)       Set DIAG_EXIT_MASK=0

    1. Case 1: clearing DIAG_EXIT_MASK (setting to ‘0’) while ERR_FAIL = ‘1’ and/or WD_FAIL = ‘1’ -> device transitions to SAFE state
    2. Case 2: clearing DIAG_EXIT_MASK (setting to ‘0’) while ERR_FAIL = ‘0’ and WD_FAIL = ‘0’ -> device transitions to ACTIVE state

                                                        i.     NOTE: this implies that ERR_FAIL and WD_FAIL status flag bits are cleared before DIAG_EXIT_MASK is cleared (while device was in DIAG state)

    3)    Dose TPS65381 go to SAFE state or stay DIAGNOSTIC state?

          1. see above explanation

  • Hello Mahmoud-san,

    Thank you very much for your answer.

    Please answer following question regarding your answer.

     

    Please answer following question Regarding your explanation of Case 2.

    1)     I think DIAG_EXIT should be ‘1’ to exit DIAG state but it is ‘0’ in this case.

    Please explain why state transition to ACTIVE state will occur in spite of DIAG_EXIT=0.

    2) I think if DIAG_EXIT_MASK is cleared before 600ms time out TPS65381 stays DIAG state until 600ms and transition to SAFE state after 600ms timeout.

     

    Also, please answer for following original my question Q2: because I want to confirm the behavior on EVM.

    Q2:

    I tried to test above operation using TPS65381EVM but I could not set DIAG_EXIT=0 in DIAGNOSTIC state. ( I cricked DIAG_EXIT field but it returned to checked as below.)

    Please advise why I could not set DIAG_EXIT=0.

     

    Thanks and Beast Regards.

  • Hello Mahmoud-san,

    Please answer above my question.

    Best Regards.

  • Hello Mahmoud-san,

    Please answer above my question.

    Best Regards.

  • Hello Mahmoud-san,

    Please advice when you will bw able to answer my question .

    Best Regards.

  • Hello Mahmoud-san,

    Please answer my question I posted Jul 31 2014 21:39 PM.

    Best Regards.

  • 1) 

    From last post:

    2)       Set DIAG_EXIT_MASK=0

      1. Case 1: clearing DIAG_EXIT_MASK (setting to ‘0’) while ERR_FAIL = ‘1’ and/or WD_FAIL = ‘1’ -> device transitions to SAFE state
      2. Case 2: clearing DIAG_EXIT_MASK (setting to ‘0’) while ERR_FAIL = ‘0’ and WD_FAIL = ‘0’ -> device transitions to ACTIVE state

                                                        i.     NOTE: this implies that ERR_FAIL and WD_FAIL status flag bits are cleared before DIAG_EXIT_MASK is cleared (while device was in DIAG state)

    -->  Please see the highlighted sentances.  This is the answer to the question. 

    2)  Yes.

    Q2:  clarification:  are you observing the DIAG_EXIT bit was set to 1 while the device was in diagnostic state? And then you are trying to clear the diag_exit bit (set to 0)? 

    Note:  using the GUI we have to use the DIAG_EXIT masks to get to active state since we cannot service the devic in the required 600ms of a real time system so what we do in the lab on the GUI and for debug is not always what a running system would do.  Usually the system will do this in less than 600ms.