Hugely different deepsleep current consumption with wake_on_ext0 and ext1
Posted: Sun Apr 25, 2021 1:34 pm
If I use this code with ext1:
I get 5uA consumption on my ESP32 break-out board
If I use this code with ext0:
I get consumption of 1400uA 
Have I met (made) some kind of anomaly or have other people seen this? I looked at the code behind wake_on_ext0 and wake_on_ext1 but I couldn't see anything obvious, but I am not a C programmer.
As usual, it's not a showstopper, but I don't like unexplained results.
While I am here, I can say that having any touch pin enabled seems to commit one to consumption of 218uA in deep sleep (very disappointing) rising to 226uA with 8 touch pins enabled. Hence looking at wake_on_extX...
Code: Select all
wu = Pin(34, mode=Pin.IN, pull=Pin.PULL_DOWN)
esp32.wake_on_ext1(pins = [wu], level = esp32.WAKEUP_ANY_HIGH)
deepsleep()
If I use this code with ext0:
Code: Select all
wu = Pin(34, mode=Pin.IN, pull=Pin.PULL_DOWN)
esp32.wake_on_ext0(pin = wu, level = esp32.WAKEUP_ANY_HIGH)
deepsleep()
Have I met (made) some kind of anomaly or have other people seen this? I looked at the code behind wake_on_ext0 and wake_on_ext1 but I couldn't see anything obvious, but I am not a C programmer.
As usual, it's not a showstopper, but I don't like unexplained results.
While I am here, I can say that having any touch pin enabled seems to commit one to consumption of 218uA in deep sleep (very disappointing) rising to 226uA with 8 touch pins enabled. Hence looking at wake_on_extX...