Okay I'm understanding a little more of the situation. I have the interrupt set on rising edge and wakeup set on high, so I should not get this repeated triggering of interrupts correct? This situation only occurs when the interrupt gets triggered while asleep not while the device is awake. As I mentioned in my original post (sorry if it wasn't written well) the interrupt only fires once when awake as it should and resets a timer to put the device into light sleep. When attempting to wake the device from sleep, it wakes correctly and calls the interrupt but it gets called continually thus triggering the watch dog. If I'm understanding what you've said correctly this should not be the case.ESP_Sprite wrote: ↑Wed Sep 11, 2019 3:41 amI think you're conflating two things here: one is wake-up, the other one is the interrupt. At the moment, it seems you have both set to level, that is, while the line is high, the CPU will keep waking up (which I think is what you want) and while the line is high, it will also keep triggering the interrupt. The second bit is what bites you: as the CPU keeps executing the interrupt handler over and over and over again, it does never have time to do other things and the watchdog will kill it.
Normally, the way you use a level interrupt is that in the interrupt routine, you clear the interrupt, in other words, you 'take away' the reason for the interrupt line to be high. In your case, it would mean e.g. resetting a chip that is connected to your GPIO line. In case you cannot do this, you're better served by an edge interrupt, which only triggers once when the signal goes high.
Note that this is different from using a GPIO as a wake-up source: the settings of that are, to my knowledge, not connected to the interrupt handling of a pin at all.
Let me know if I've stated anything that doesn't make sense.