esp32 - Cannot Read Pin Value After Wake on Pin #3835

diginfo · 2018-06-02T02:45:31Z

This is also reported here: https://forum.micropython.org/viewtopic.php?f=18&t=4856
And Here: #3531 (comment)

This is what I thought would be a simple toggling of the wake pin trigger edge, but it turns out not !

This code should get the current value of door pin, and set the wake from deepsleep edge based on the pin value high or low and then put the device into deepsleep awaiting the trigger edge.

There is a 10K pull-down on pin 34 and the switch pulls it high.

The purpose is to wake up and sleep again each time the interrupt is triggered on a different edge.

The time.sleeps() are just to give time to view the output and should not have any other effect other than de-bouncing, but given that the esp32 startup time is 2 seconds, debouncing should not be needed.

It appears to work the first time deepsleep is fired, but thereafter door.value() always reads 0 even though the switch is closed and pulled high !

boot.py

import machine as mc, time
time.sleep(1)
door = mc.Pin(34,mc.Pin.IN)
edge =  5- door.value()
edgeMc = {
  5:'WAKE_HIGH',
  4:'WAKE_LOW'
}[edge] or 'BAD'

print('door:{}, edge:{}, edgeMc: {}'.format(door.value(), edge, edgeMc))
door.irq(trigger = edge, wake = mc.DEEPSLEEP)

time.sleep(5)
mc.deepsleep(60000)

Initially the switch was low:
door:0, edge:5, edgeMc: WAKE_HIGH

Then switch was then enabled (high):
door:1, edge:4, edgeMc: WAKE_LOW

Then, without changing the switch position, it just continuously loops, apparently unable to read the value of door any more:

door:0, edge:5, edgeMc: WAKE_HIGH
door:0, edge:5, edgeMc: WAKE_HIGH
door:0, edge:5, edgeMc: WAKE_HIGH
door:0, edge:5, edgeMc: WAKE_HIGH
door:0, edge:5, edgeMc: WAKE_HIGH
door:0, edge:5, edgeMc: WAKE_HIGH

The text was updated successfully, but these errors were encountered:

MrSurly · 2018-06-02T03:12:15Z

So, this part:

door:0, edge:5, edgeMc: WAKE_HIGH
door:0, edge:5, edgeMc: WAKE_HIGH
door:0, edge:5, edgeMc: WAKE_HIGH
door:0, edge:5, edgeMc: WAKE_HIGH
door:0, edge:5, edgeMc: WAKE_HIGH

I assume you've removed the intervening logging -- can I get a full log printout of 2 or 3 cycles?

diginfo · 2018-06-02T03:54:03Z

if 1==1:
  import machine as mc, time  
  wake = mc.Pin(35,mc.Pin.IN)
  
  time.sleep(1)
  val = wake.value()
  if val == 1:
    edge = mc.Pin.WAKE_LOW
  else:
    edge = mc.Pin.WAKE_HIGH

  wake.irq(trigger = edge , wake = mc.DEEPSLEEP)
  print('value:{}, edge:{}'.format(val, edge))

  time.sleep(1)
  mc.deepsleep()

Set Switch / Pin High
Hard Reset
Code stops correctly at: value:1, edge:4
Set Switch / Pin Low
Code loops forever
Set Switch High
Code continues looping and shows pin value = 0 and not 1

ets Jun  8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT)
flash read err, 1000
ets_main.c 371 
ets Jun  8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:4484
load:0x40078000,len:0
load:0x40078000,len:11816
entry 0x4007a9fc
I (408) cpu_start: Pro cpu up.
I (408) cpu_start: Single core mode
I (409) heap_init: Initializing. RAM available for dynamic allocation:
I (412) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (418) heap_init: At 3FFC5098 len 0001AF68 (107 KiB): DRAM
I (424) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM
I (431) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (437) heap_init: At 4008DD1C len 000122E4 (72 KiB): IRAM
I (443) cpu_start: Pro cpu start user code
I (14) cpu_start: Starting scheduler on PRO CPU.
value:1, edge:4
ets Jun  8 2016 00:22:57

rst:0x5 (DEEPSLEEP_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:4484
load:0x40078000,len:0
load:0x40078000,len:11816
entry 0x4007a9fc
I (407) cpu_start: Pro cpu up.
I (408) cpu_start: Single core mode
I (408) heap_init: Initializing. RAM available for dynamic allocation:
I (411) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (417) heap_init: At 3FFC5098 len 0001AF68 (107 KiB): DRAM
I (424) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM
I (430) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (436) heap_init: At 4008DD1C len 000122E4 (72 KiB): IRAM
I (443) cpu_start: Pro cpu start user code
I (13) cpu_start: Starting scheduler on PRO CPU.
value:0, edge:5
ets Jun  8 2016 00:22:57

rst:0x5 (DEEPSLEEP_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:4484
load:0x40078000,len:0
load:0x40078000,len:11816
entry 0x4007a9fc
I (408) cpu_start: Pro cpu up.
I (408) cpu_start: Single core mode
I (408) heap_init: Initializing. RAM available for dynamic allocation:
I (411) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (417) heap_init: At 3FFC5098 len 0001AF68 (107 KiB): DRAM
I (424) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM
I (430) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (436) heap_init: At 4008DD1C len 000122E4 (72 KiB): IRAM
I (443) cpu_start: Pro cpu start user code
I (13) cpu_start: Starting scheduler on PRO CPU.
value:0, edge:5

MrSurly · 2018-06-02T05:31:55Z

Does this happen on other pins?

diginfo · 2018-06-02T05:51:33Z

Just tried on pin 26 exactly the same behaviour.

MrSurly · 2018-06-08T16:25:43Z

Still looking at this. Hang tight.

MrSurly · 2018-06-08T22:53:31Z

Filed upstream bug: espressif/esp-idf#2043

There are actually two bugs here (I think).

Not being able to read the GPIO pin properly. I've fixed this already by calling gpio_config(), per GPIO input from pin used for wakeup not readable after wakeup espressif/esp-idf#245 (comment). This sort of "masks" the problem below, because the pin always reads 0, so that's why it's immediately triggering, right? Not really ...
Seems that EXT0 wakes when level is 0 (wake low) don't work -- it always wakes immediately.

MrSurly · 2018-06-13T04:25:44Z

Workaround from Espressif, but I cannot implement or test until after the 25th, as I will be out-of-town.

diginfo · 2018-06-13T04:29:34Z

can this be implemented using the python pin settings ?

dpgeorge · 2018-06-15T06:26:07Z

It looks like Espressif have now fixed this bug in the latest ESP IDF. In d61d119 I updated the esp32 to use the new IDF version, so this bug should be fixed now.

MrSurly · 2018-06-24T22:21:35Z

@diginfo Can you confirm?

Greedily grab as much RMT memory as we can. It blocks other RMT transmit channels but we only use it temporarily anyway. The more we can grab, the fewer interrupts are needed to keep the transmit going. On ESP32, move CircuitPython to the second core. This helps NeoPixel by moving the RMT interrupt to the second core as well. When testing ESP32 I noticed that settings.toml writes won't apply until after hard reset. This removes that constraint but still requires the password to enable the web workflow. Fixes micropython#3835

Greedily grab as much RMT memory as we can. It blocks other RMT transmit channels but we only use it temporarily anyway. The more we can grab, the fewer interrupts are needed to keep the transmit going. Flickers may still happen due to file system writes but most of the time the animation just pauses. On ESP32, move CircuitPython to the second core. This helps NeoPixel by moving the RMT interrupt to the second core as well. When testing ESP32 I noticed that settings.toml writes won't apply until after hard reset. This removes that constraint but still requires the password to enable the web workflow. Fixes micropython#3835

diginfo mentioned this issue Jun 2, 2018

ports/esp32:* Implementation of deep sleep, esp32 module, machine.RTC #3531

Closed

dpgeorge added the port-esp32 label Jun 5, 2018

MrSurly mentioned this issue Jun 8, 2018

[TW#23307] esp_sleep_enable_ext0_wakeup() always wakes when level set to 0, ignoring pin state espressif/esp-idf#2043

Closed

dpgeorge closed this as completed Jun 15, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

esp32 - Cannot Read Pin Value After Wake on Pin #3835

esp32 - Cannot Read Pin Value After Wake on Pin #3835

diginfo commented Jun 2, 2018 •

edited

Loading

MrSurly commented Jun 2, 2018

diginfo commented Jun 2, 2018

MrSurly commented Jun 2, 2018

diginfo commented Jun 2, 2018

MrSurly commented Jun 8, 2018

MrSurly commented Jun 8, 2018

MrSurly commented Jun 13, 2018

diginfo commented Jun 13, 2018

dpgeorge commented Jun 15, 2018

MrSurly commented Jun 24, 2018

esp32 - Cannot Read Pin Value After Wake on Pin #3835

esp32 - Cannot Read Pin Value After Wake on Pin #3835

Comments

diginfo commented Jun 2, 2018 • edited Loading

MrSurly commented Jun 2, 2018

diginfo commented Jun 2, 2018

MrSurly commented Jun 2, 2018

diginfo commented Jun 2, 2018

MrSurly commented Jun 8, 2018

MrSurly commented Jun 8, 2018

MrSurly commented Jun 13, 2018

diginfo commented Jun 13, 2018

dpgeorge commented Jun 15, 2018

MrSurly commented Jun 24, 2018

diginfo commented Jun 2, 2018 •

edited

Loading