I gave the IDF source code a look and this definitely smells like a bug to me.
A quick search through gitlab issues didn't show anything similar, so I suggest you to open one.
Search found 4 matches
- Sun Mar 03, 2024 5:56 am
- Forum: ESP-IDF
- Topic: Understanding ADC Continuous Mode Configuration in ESP32S2 Using IDF-5.1.1
- Replies: 1
- Views: 4308
- Tue Feb 06, 2024 1:55 pm
- Forum: ESP-IDF
- Topic: UART read timeout looks not working
- Replies: 8
- Views: 8131
Re: UART read timeout looks not working
I should especially note that I did not use any interrupt tuning whatsoever , i.e. never called any of those uart_intr_config, uart_set_rx_timeout, uart_enable_rx_intr etc.
Okay, I bit the bullet and made a dive into the confusing world of the aforementioned interrupt functions.
After reading the ...
Okay, I bit the bullet and made a dive into the confusing world of the aforementioned interrupt functions.
After reading the ...
- Mon Feb 05, 2024 9:43 pm
- Forum: ESP-IDF
- Topic: How to use custom interrupt for handling UART
- Replies: 11
- Views: 6672
Re: How to use custom interrupt for handling UART
There is a pending feature request about this.Is it possible to receive a notification when the TX FIFO becomes empty?
- Mon Feb 05, 2024 9:26 pm
- Forum: ESP-IDF
- Topic: UART read timeout looks not working
- Replies: 8
- Views: 8131
Re: UART read timeout looks not working
If you need low-latency reaction to Rx, you must always call uart_read_bytes with length of 1.
See an ugly, but working, crutch in this post.
I tested it by connecting UART Rx to the same UART's Tx, and calling esp_timer_get_time both after uart_write_bytes and after the aforementioned crutch (when ...
See an ugly, but working, crutch in this post.
I tested it by connecting UART Rx to the same UART's Tx, and calling esp_timer_get_time both after uart_write_bytes and after the aforementioned crutch (when ...