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.

TPS659037: About DEV_ON control

Part Number: TPS659037

Hi,

Let the additional questions for the following thread.

e2e.ti.com/.../2935472
〉2. Starting at Table 5-9 in the datasheet explains the ON and OFF requests and what can gate them.
〉For example: "The DEV_ON event has a lower priority over other ON events; it forces the TPS659037 device to go to the OFF state only if no other ON conditions are keeping the device active" 

Please tell me the condition of "other ON conditions" in detail.
The conditions for writing 0 to the DEV_ON bit are as follows.

・PWRON : High
・PWRDOWN : Open
・RESET_IN : High
・POWERHOLD : High

Customer can not imagine a pattern (example) that requires writing a 0 to the DEV_ON bit.
Could you give me your advice?

Best Regards,
Yusuke
  • Yusuke-san,

    The ON Requests are located in table 5-9 of the datasheet and include PWRON event, POWERHOLD event, as well as RPWRON and some interrupts. If any of these ON Requests are present, writing a '0' to DEV_ON (which would turn the device off) will not do anything because this event has lower priority than the ON Requests.

    In your example, POWERHOLD is high so writing a '0' to DEV_ON will not do anything. This bit is intended for when you have a push button on PWRON and you are toggling PWRON to turn the device on. In that case, you would need to set the DEV_ON bit to '1' to keep the device on. Once you are ready to turn the device off, you can set DEV_ON to '0' or use the long press on the PWRON to disable the device. This is only useful when you are not using POWERHOLD.

    Please let me know if this answers your question.

    Thanks,
    Nastasha