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.

TPS65986: Max Wake-up time from SLEEP after first I2C attempt, until next I2C attempt can be recognized

Part Number: TPS65986

From prior post, it is understood that when device is in SLEEP, we need to wait for 48M Osc to become stable before getting switched and able to recognize I2C commands.  It was empirically determined that 1ms delay between I2C attempts was sufficient to allow that to happen.  My customer implemented this along with a number of retries, but is now seeing successive NACK's, up to 3 NACKs before waking.  Is there potentially a period of time required to enter SLEEP mode, before it would be woken-up by an I2C write?   In other words, if the first I2C write attempt occurred right as the device starts to enter SLEEP, is there a period of time during SLEEP entry where it would not recognize or react to any I2C writes?   If so, can we quantify that time, so they can determine the max worst-case time period for the device to Enter and Exit SLEEP mode?    Thank you.

  • Hi Eric S.,

    I have informed the FW expert of the team about your question. Please allow for some time for him to look at your question.

    Thank you,
    Eric
  • Eric,
    Just wanted to check if there was any feedback from FW team yet. thank you for your assistance.
  • Eric,

    Yes - There could be that period where an I2C command is sent to the device while its just entering SLEEP state. The device in such cases will continue to NACK the commands till it transitions to a state where it's ready to receive (and process) these commands. We've not quantified this time, and as indicated in the other post, the recommendation is for the applications to implement a retry mechanism so that the I2C master will keep retrying to send its messages until the device acknowledges them.

    -/Praneet