Recent changes in IDF [0] allow significantly lower light sleep current. Testing this today, I found some interesting behaviour I don't quite understand. The TL;DR is that this is a great improvement (825uA -> 375uA) but it seems it can be achieved much more easily by resetting a small number of off...

Isn't it likely that you still have power supply problems? That could cause odd behaviour with touch sensors, but you won't know about it now with brownout detection disabled. If you have a reliable reproduction for the brownout reset issue you should reply to @igrr: https://github.com/adafruit/circ...

Don't dwell on it, there's no leak if there's not a consistent pattern of reduction. See this post: https://esp32.com/viewtopic.php?t=14056#p55646 And also consider that there are other tasks doing work behind the scenes - especially WiFi/lwip in this case, which will be dynamically allocating/deall...

skip_cert_common_name_check will not allow you to bypass TLS, it will only avoid checking the certificate's CN (so a possible mismatch would not fail validation). To completely disable the certificate check, you will need to go to ESP-TLS in menuconfig, enable "Allow potentially insecure options" an...

Same as this? https://github.com/espressif/esp-idf/issues/6179

istokm wrote: ↑

Sun Jan 17, 2021 1:16 am

Oh I thought that ESP32_RTC_CLK_SRC also applies to the ULP..

You're right, it does. I assumed you were using 150khz internal. Ignore that part.

Cycles for all instructions are included here: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/ulp_instruction_set.html read the RTC_TIME registers at the very beginning, then reading them at the very end of the program, and using the difference to alter the ULPs sleep timer? ...

It's not clear where ULP variable offsets are coming from (eg. debounce_max_count). Maybe I missed something. The xxx->ulp_xxx pattern is only used when compiling ULP assembly. You can't do it that way with legacy macros. See here for an alternative with macros (and ulp_var_t in HULP examples for an...

It's not clear where ULP variable offsets are coming from (eg. debounce_max_count). Maybe I missed something. For RTCIOs 0-15, you would want RTC_GPIO_IN_NEXT_S to RTC_GPIO_IN_NEXT_S+15. For the upper two you want RTC_GPIO_IN_NEXT_S+16 to RTC_GPIO_IN_NEXT_S+16+1. RTC_CNTL_RDY_FOR_WAKEUP -> RTC_CNTL_...

Keypads like this work by toggling column pins output low sequentially, reading the state of each row pin for each column. In case 2, GPIO 35 is used as a column pin yet it is not output capable, so the row pins are always pulled high. 34-39 should only be used as row pins here (with external pullup...