TonBERRY/micropython
3
0
Fork 0
Code Pull Requests Activity

docs/esp32: Mention the use of Timer(0) by UART.IRQ_RXIDLE.

Browse Source 
In both the machine.UART and esp32.quickref sections.

Signed-off-by: robert-hh <robert@hammelrath.com>
This commit is contained in:
robert-hh
2025-03-31 08:10:18 +02:00
committed by Damien George
parent 92c219afd6
commit 5cfafb73da
2 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/esp32/quickref.rst
View File

@@ -284,7 +284,8 @@ with a timer ID of 0, 0 and 1, or from 0 to 3 (inclusive)::
tim1 = Timer(1) tim1 = Timer(1)
tim1.init(period=2000, mode=Timer.PERIODIC, callback=lambda t:print(1)) tim1.init(period=2000, mode=Timer.PERIODIC, callback=lambda t:print(1))
The period is in milliseconds. The period is in milliseconds. When using UART.IRQ_RXIDLE, timer 0 is needed for
the IRQ_RXIDLE mechanism and must not be used otherwise.
Virtual timers are not currently supported on this port. Virtual timers are not currently supported on this port.

3
docs/library/machine.UART.rst
View File

@@ -224,7 +224,8 @@ Methods
.. note:: .. note::
- The ESP32 port does not support the option hard=True. - The ESP32 port does not support the option hard=True. It uses Timer(0)
for UART.IRQ_RXIDLE, so this timer cannot be used for other means.
- The rp2 port's UART.IRQ_TXIDLE is only triggered when the message - The rp2 port's UART.IRQ_TXIDLE is only triggered when the message
is longer than 5 characters and the trigger happens when still 5 characters is longer than 5 characters and the trigger happens when still 5 characters