-
Notifications
You must be signed in to change notification settings - Fork 7.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(uart): [IDF 5.3] fixes HardwareSerial::updateBaudRate() using a baud rate higher 230400 - checks UART Clock Source #10643
feat(uart): [IDF 5.3] fixes HardwareSerial::updateBaudRate() using a baud rate higher 230400 - checks UART Clock Source #10643
Conversation
👋 Hello SuGlider, we appreciate your contribution to this project! Click to see more instructions ...
Review and merge process you can expect ...
|
Test Results 61 files 61 suites 5m 46s ⏱️ Results for commit e4fd823. ♻️ This comment has been updated with latest results. |
Memory usage test (comparing PR against master branch)The table below shows the summary of memory usage change (decrease - increase) in bytes and percentage for each target.
Click to expand the detailed deltas report [usage change in BYTES]
|
EXCLUSIVE FOR IDF 5.3 - Arduino Core 3.1.x
Description of Change
ESP32 and ESP32S2 use REF_TICK as UART clock source whenever the baud rate is lower then 250,000.
This is done within
HardwareSerial::begin(uint32_t baud)
This prevents issues with chaning the APB clock to lower than 40MHz, specially when achieving lower power consumpition.
This PR also fixes it for the
HardwareSerial::updateBaudRate(uint32_t baud)
by checking the target baud rate and adjusting the UART Clock Source that will make it work correctly.Tests scenarios
Using this sketch (from the issue report) using ESP32 and ESP32S2
Related links
Closes #10641