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
When Support for power management is enabled in menuconfig and Enable dynamic frequency scaling (DFS) at startup is NOT enabled, soon after application start the UART output becomes garbled (corrupt).
If Enable dynamic frequency scaling (DFS) at startup is enabled, this does not happen.
This only happens if→ Component config → ESP32-specific → CPU frequencyis set to 240 MHz.
Possible workaround is to set the the CPU frequency to 160 MHz at the application start, then set it back to 250 MHz:
Even with this workaround, after changing the max CPU frequency to 160 or 80 MHz, the console output (readable befor the frequency change) becomes unreadable, as if the boudrate changed.
Printing with printf works before freq change, not after.
Is REF_TICK used as clock source for the console uart ?
FayeY
changed the title
Trash on console when Power Management enabled
[TW#19295] Trash on console when Power Management enabled
Mar 19, 2018
When
Support for power management
is enabled in menuconfig andEnable dynamic frequency scaling (DFS) at startup
is NOT enabled, soon after application start the UART output becomes garbled (corrupt).If
Enable dynamic frequency scaling (DFS) at startup
is enabled, this does not happen.This only happens if
→ Component config → ESP32-specific → CPU frequency
is set to 240 MHz.Possible workaround is to set the the CPU frequency to 160 MHz at the application start, then set it back to 250 MHz:
The text was updated successfully, but these errors were encountered: