-
Notifications
You must be signed in to change notification settings - Fork 7.6k
fix(uart): uart rx timeout validation with proper log message #11141
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
👋 Hello SuGlider, we appreciate your contribution to this project! 📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more. 🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project. Click to see more instructions ...
Review and merge process you can expect ...
|
Test Results 76 files 76 suites 14m 35s ⏱️ Results for commit 760896c. ♻️ 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]
|
Description of Change
UART RX Timeout value may change depending on the UART Clock Source, Baudrate and the SoC running it.
This PR brings more clarity to the
HardwareSerial::setRxTimeout(uint8_t symbols_timeout)
function in order to validate the requested timeout and also log proper error message if necessary.Tests scenarios
Tested with ESP32, ESP32-S2 and ESP32-S3.
Related links
Related to #11132