You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
I have searched the issue tracker for a similar issue and not found a similar issue.
General issue report
In ESP-IDF 5.3.1 and before, the APB frequency lock was only used if the glitch filter was enabled for a PCNT unit. This allowed the device to enter light sleep even when a PCNT unit was enabled (but without a glitch filter).
In ESP-IDF 5.3.2 the commit 33f8207 introduced new behavior, and the lock is always installed and used, even if the glitch filter is not enabled.
This means that since 5.3.2 the device cannot enter light sleep when a PCNT unit is enabled, even if it uses no glitch filter.
The commit comment says "fix" but I found no record of what problem this is fixing.
The documentation in 5.3.2 still says the lock is installed lazily only when a glitch filter is present:
github-actionsbot
changed the title
Device unable to go to light sleep with PCNT unit enabled without glitch filter
Device unable to go to light sleep with PCNT unit enabled without glitch filter (IDFGH-14231)
Dec 13, 2024
Answers checklist.
General issue report
In ESP-IDF 5.3.1 and before, the APB frequency lock was only used if the glitch filter was enabled for a PCNT unit. This allowed the device to enter light sleep even when a PCNT unit was enabled (but without a glitch filter).
In ESP-IDF 5.3.2 the commit 33f8207 introduced new behavior, and the lock is always installed and used, even if the glitch filter is not enabled.
This means that since 5.3.2 the device cannot enter light sleep when a PCNT unit is enabled, even if it uses no glitch filter.
The commit comment says "fix" but I found no record of what problem this is fixing.
The documentation in 5.3.2 still says the lock is installed lazily only when a glitch filter is present:
https://github.com/espressif/esp-idf/blob/v5.3.2/components/esp_driver_pcnt/include/driver/pulse_cnt.h#L128
The text was updated successfully, but these errors were encountered: