-
Notifications
You must be signed in to change notification settings - Fork 13.3k
uart_rx_fifo_available considerations #4565
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
Comments
* Fix for #4565 (rx fifo length), protect access to rx_buffer * Fix typo * reworked to separate safe from unsafe functions, factorized some code, constness * additional rework for uart_rx_fifo_available() * swapped unsafe function definition order * Remove static for overrun string * Some shorthand for perf and readability
Good work guys, the new commit works perfectly with all my serial tests, including a simulated DOS attack while WiFi is on. I did see my S/W buffer as high as 900 characters during that, but it's still running and no errors were detected in the Serial stream. |
Thanks for your feedback ! |
…sp8266#4568) * Fix for esp8266#4565 (rx fifo length), protect access to rx_buffer * Fix typo * reworked to separate safe from unsafe functions, factorized some code, constness * additional rework for uart_rx_fifo_available() * swapped unsafe function definition order * Remove static for overrun string * Some shorthand for perf and readability (cherry picked from commit 29580e8)
Just wanted to add a comment here to say that this change fixes a crash in my project that was very easy to reproduce when there is sufficient messages being sent to the ESP8266 serial port. With the new version of 🙇 🤗 🎁 |
According to @jasoroony's comments and after checking the doc, it appears that:
should be:
reference section 11.3.7:
where
(both
USRXC
andUART_RXFIFO_CNT_S
are 0)The text was updated successfully, but these errors were encountered: