Rx Timeout example was not working correctly using ESP32 and ESP32-S2 due to default selection of REF_TICK as UART Clock Source. REF_TICK limits RX Timeout to 1.

This PR adds the necessary call toHardwareSerial::setClockSource() in order to make it work properly.

Tests scenarios

Expect output (see the time it takes to read 10 bytes):

ets Jul 29 2019 12:21:46rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)configsip: 0, SPIWP:0xeeclk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00mode:DIO, clock div:1load:0x3fff0030,len:4888load:0x40078000,len:16516load:0x40080400,len:4load:0x40080404,len:3476entry 0x400805b4[     8][I][esp32-hal-psram.c:102] psramAddToHeap(): PSRAM added to the heap.================================Test Case #1================================Testing the time for receiving 10 bytes at 9600 baud, using RX Timeout = 50:It has sent 10 bytes from Serial1 TX to Serial1 RXIt took 62 milliseconds to read 10 bytesReceived data: [0123456789]========================Finished!================================Test Case #2================================Testing the time for receiving 10 bytes at 9600 baud, using RX Timeout = 20:It has sent 10 bytes from Serial1 TX to Serial1 RXIt took 31 milliseconds to read 10 bytesReceived data: [0123456789]========================Finished!================================Test Case #3================================Testing the time for receiving 10 bytes at 9600 baud, using RX Timeout = 10:It has sent 10 bytes from Serial1 TX to Serial1 RXIt took 21 milliseconds to read 10 bytesReceived data: [0123456789]========================Finished!================================Test Case #4================================Testing the time for receiving 10 bytes at 9600 baud, using RX Timeout = 5:It has sent 10 bytes from Serial1 TX to Serial1 RXIt took 16 milliseconds to read 10 bytesReceived data: [0123456789]========================Finished!================================Test Case #5================================Testing the time for receiving 10 bytes at 9600 baud, using RX Timeout = 1:It has sent 10 bytes from Serial1 TX to Serial1 RXIt took 11 milliseconds to read 10 bytesReceived data: [0123456789]========================Finished!

Related links

None

feat(uart): sets correct ESP32/S2 clock source for the example

9dacdf9

SuGlider added the Peripheral: UARTRelated to the UART peripheral or its functionality. label

Apr 23, 2025

SuGlider added this to the3.2.1 milestone

Apr 23, 2025

SuGlider self-assigned this

Apr 23, 2025

SuGlider added this toArduino ESP32 Core Project Roadmap

Apr 23, 2025

github-project-automationbot moved this toTodo inArduino ESP32 Core Project Roadmap

Apr 23, 2025

SuGlider moved this fromTodo toIn Progress inArduino ESP32 Core Project Roadmap

Apr 23, 2025

Copy link

Contributor

github-actionsbot commentedApr 23, 2025•
edited
Loading

	Messages
📖	🎉 Good Job! All checks are passing!

👋Hello SuGlider, we appreciate your contribution to this project!

📘 Please review the project'sContributions Guide for key guidelines on code, documentation, testing, and more.

🖊️ Please also make sure you haveread and signed theContributor License Agreement for this project.

Click to see more instructions ...

This automated output is generated by thePR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with eachpush event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger isnot a substitute for human code reviews; it's still important to request a code review from your colleagues.
- To manuallyretry these Danger checks, please navigate to theActions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫dangerJS against4b975f9

Copy link

Contributor

github-actionsbot commentedApr 23, 2025

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.

Memory	FLASH [bytes]		FLASH [%]		RAM [bytes]		RAM [%]
Target	DEC	INC	DEC	INC	DEC	INC	DEC	INC
ESP32P4	0	0	0.00	0.00	0	0	0.00	0.00
ESP32S3	0	0	0.00	0.00	0	0	0.00	0.00
ESP32S2	0	⚠️ +64	0.00	⚠️ +0.02	0	0	0.00	0.00
ESP32C3	0	0	0.00	0.00	0	0	0.00	0.00
ESP32C6	0	0	0.00	0.00	0	0	0.00	0.00
ESP32H2	0	0	0.00	0.00	0	0	0.00	0.00
ESP32	0	⚠️ +76	0.00	⚠️ +0.02	0	0	0.00	0.00