What happens if TPL5110 doesn't get DONE signal?

[rafikii]

What does the TPL5110 do if it doesn't get a DONE signal before the next cycle is supposed to begin?

For example, say I have an arduino sketch that sometimes takes 30 seconds, but the TPL5110 is set for a 10 second cycle time. What happens at that 10 second mark? Will the Arduino be very quickly power cycled?

[dastels]

Yes. the power will be disconnected for the last 50mS of the time cycle.

Dave

[rafikii]

For an M0, is there any general recommendations for working around this?

[dastels]

I don't see that the MCU has anything to do with it. The use case is really to have your project wake up occasionally and do something quick, then shut down again. The project that wakes up and takes a few sensor readings now & then, and either logs the result or sounds an alarm as appropriate is a classic example. The TPL5110 excells at those tasks. There are some aspects of it's behavior that can make it problematic for other, albeit similar, uses.

Dave

[rafikii]

Is there another product that would serve this need better?

[rafikii]

Interesting the data sheet on Pg 11 says
"An extended assertion of a logic HIGH at the DELAY/M_DRV pin will turn on the MOSFET for a time longer than the programmed time interval. DONE signals received while the DELAY/M_DRV is HIGH are ignored. If the DRV is already LOW (MOSFET ON) the manual power ON is ignore"

although I am not totally sure what that means. Does it mean putting a HIGH voltage signal on the delay pin will allow us to

[dastels]

It sounds like while DELAY is high (e.g. hold the button pressed) the output is "on" regardless of any timing or activity on DONE.

Dave