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.

TPL5010: Issue: Erratic timing between WAKE pulses

Part Number: TPL5010

Prior to integrating the TPL5010 into a larger design I prepared a small schematic to test it.

In this situation I am using a push-button to produce the pulse on the DONE input in order to trigger the next WAKE pulse.

I set the DELAY/M_RST resistor to 16Kohm to get a theoretical WAKE pulse timing of about 30 seconds (not critical for the test).

I don't need the RSTn capability in my case so I left the pin unconnected. I also tried to connect a pull-up to VCC but didn't notice any change in overall result.

The schematic is as follows:

The problem is that the WAKE pulse is not triggered at a steady frequency, as it should. The delay between pulses varies from 8 s to 28 s when I was expecting a pulse every 30 seconds or so.

My understanding is that the DONE pulse triggers the counter for the first cycle. So shouldn't I expect the WAKE pulse 30 s after the DONE pulse (talking of the first cycle only). Then, for subsequent cycles the DONE pulse should be triggered within the tD_DONE delay (para 7.6 of the datasheet) and my understanding is that I should have periodic WAKE pulses every 30s.

Is there anything wrong with the schematic or/and with my interpretation of the datasheet?

  • Yes, the DONE pulse triggers the counter for the first cycle. However, the first WAKE pulse is not necessarily 30 seconds after the DONE pulse.
    If a DONE pulse is received within the programmed time interval after the resistance reading and RSTn goes high, the first WAKE pulse will output after the programmed time interval expires. See figure 9 of the datasheet for a startup timing diagram.

    This is also addressed in my response on the other post. I'll link the threads here for reference:
    e2e.ti.com/.../2649650
    https://e2e.ti.com/support/clock_and_timing/f/48/t/718085

    Kind regards,
    Lane

  • Thank you Lane,
    If I understood correctly, the delay "seems erratic" only for the first cycle, after the first DONE pulse. Subsequent WAKE pulses should occur according to the delay set by R_EXT (cf figure 1. in the datasheet).
    Then, how can we control the first delay, i.e. first WAKE pulse timing? Is it the time, determined by R_EXT, elapsed since POR?

    Jean-Christophe
  • Hi Jean-Cristophe,

    After a POR event, the device first reads the external resistance for 100ms. Next, it holds RSTn low for 320ms until RSTn is set high and the timer begins.
    In other words, the first WAKE pulse will occur 30 seconds after RSTn is set high if a valid DONE pulse is received. Otherwise, you will see a pulse on RSTn.

    Kind regards,
    Lane

  • Thank you very much Lane
    It was not so explicit in the datasheet. That clarifies the point.
    best regards
    Jean-Christophe