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.

HITEX SAFETI-HSK-570LS31-ND state of the ENDRV pin is always LOW

Other Parts Discussed in Thread: RM48L952

The question is about SafeTI-HSK-570LS31-ND safety kit. I have already checked the suggested forum posts but could not get the related answer.

ENDRV pin is always LOW and it measures as 0.01 V. The necessary test code is achieved by using SafeTI Diagnostic Library 2.2.0 and I also checked the configuration from the following link.

http://processors.wiki.ti.com/index.php/Configuring_HALCoGen_for_using_TPS_Driver

I also checked the NRES pin then I measured it as 3.3 V. For this reason, it can be said that TPS65381 is not in Standby State or Reset State. Actually, according to our observations, TPS65381 enters Diagnostic State at first, then it enters Active State.

Both in Diagnostic or Active states, state of the ENDRV pin is determined by the Watchdog Fail Count value. Additionally, ENABLE_DRV and WD_RST_EN are set as true and false, respectively as default.

Probably, we miss some crucial point. We will be thankful if you give detailed information about state and working concept of the ENDRV pin.

Best Regards.

  • Hi,

    We are working on your question and will be back to you shortly.
  • Hi,


    I did some test using the Hitex board.

    I've installed the SafeTI Diagnostic Library 2.2.0 version.
    Part of this installation is a demo directory. I've compile and run successfully the "RM48L952_HitexKit"
    This code is testing the DUT to TPS65381.

    A serial connection via the micro USB port is necessary to display the log messages from the DUT.
    The configuration is:

    The COM port will be different for you.

    Once the code is flashed in the DUT, if you press the SW300 (Reset) you will see:

    At that point, the ENDRV is 0v.

    It is necessary to reset the Monitor micro on the Hitex board. To do so, you have to use the Hitex GUI, connect to the board and use the "Reset Safety-MCU" on the Hitex GUI.

    At that point, the DUT will start logging on the serial terminal as following:

    Also, here is the waveform of the ENDRV signal after doing the "Reset Safety-MCU"

    Based on this description, can you try to run your code and reset the Safety MCU via the HITEX GUI and let me know the result.

  • Hi Jean-Marc,

    Firstly, I really appreciate for your approach that includes detailed clarification.

    I have realized that the reason for power-on-reset necessity caused by the code checks the device state is in Diagnostic State or not in TPS_DriverInit section.

    I have fixed the problem by adding delay function to code and performing hard power-on-reset. At the time the delay function is being executed, I have chance to initialize serial terminal. However, of course HITEX GUI is a better solution, thanks for your suggestion. I did this trick because HITEX GUI looks incompatible with Windows 8 but I check it with Windows 7 and your suggestions works correctly.

    Eventually, I have achieved the same output with you.

    At that point, I would like to ask one more question to you. After the second part of the test code (watchdog errors in Active Mode) is executed, is there any chance to decrease watchdog fail counter value again by sending correct token responses?

    In order to decrease watchdog fail counter value, I arrange watchdog and RTI configurations as in the other parts of the code. Additionally, these configurations totally match with notification file content. However, watchdog fail counter value still remains as 7.

    Best Regards.

  • Hi Jean-Marc,

    Is there any outcome about the previous question? I would like to describe the problem by adding some detailed information for making it clear.

    Question was that after the second part of the test code (watchdog errors in Active Mode) is executed, is there any chance to decrease watchdog fail counter value again by sending correct token responses?

    The test code looks suitable for this scenario because at the end of the code, it tries to decrease watchdog fail counter value and then it checks ENDRV state. However, it looks there is something wrong because both “if” and “else” conditions are written with the same text in SafeTI Diagnostic Library 2.2.0 and I observed that at that point "else" state is executed in other words ENDRV is still low. This part can be seen from the added screenshot.

    The most curious circumstance is that I tried to decrease watchdog fail counter value in TEST_WDACT_ERRORS part by using similar method with screenshot. However, the result is same and WFC value still reaches 7. After the ineffective attempt, I arrange the whole conditions same with the last states before the attempt is realized. Then code is executed on its own direction but at that time at the end of the test code (the part that is seen from the above screenshot) “if” state is executed or in other words it can be said that WFC is equal to 0 and ENDRV is high as it should be.

    I would be grateful if you explain why both “if” and “else” states are written with the same text and what is the reason for WFC remaining as 7 in that part or what is the correct way for decreasing WFC value?

    Best Regards.