OpenCores
URL https://opencores.org/ocsvn/neorv32/neorv32/trunk

Subversion Repositories neorv32

[/] [neorv32/] [trunk/] [docs/] [datasheet/] [soc_uart.adoc] - Diff between revs 65 and 66

Go to most recent revision | Show entire file | Details | Blame | View Log

Rev 65 Rev 66
Line 56... Line 56...
transfer is completed when the _UART_CTRL_TX_BUSY_ control register flag returns to zero. A new received byte
transfer is completed when the _UART_CTRL_TX_BUSY_ control register flag returns to zero. A new received byte
is available when the _UART_DATA_AVAIL_ flag of the `DATA` register is set. A "frame error" in a received byte
is available when the _UART_DATA_AVAIL_ flag of the `DATA` register is set. A "frame error" in a received byte
(invalid stop bit) is indicated via the _UART_DATA_FERR_ flag in the `DATA` register. The flag is cleared by
(invalid stop bit) is indicated via the _UART_DATA_FERR_ flag in the `DATA` register. The flag is cleared by
reading the `DATA` register.
reading the `DATA` register.
 
 
 
[TIP]
 
A transmission (RX or TX) can be terminated at any time by disabling the UART module
 
by clearing the _UART_CTRL_EN_ control register bit.
 
 
 
 
**RX and TX FIFOs**
**RX and TX FIFOs**
 
 
UART0 provides optional FIFO buffers for the transmitter and the receiver. The _UART0_RX_FIFO_ generic defines
UART0 provides optional FIFO buffers for the transmitter and the receiver. The _UART0_RX_FIFO_ generic defines
the depth of the RX FIFO (for receiving data) while the _UART0_TX_FIFO_ defines the depth of the TX FIFO
the depth of the RX FIFO (for receiving data) while the _UART0_TX_FIFO_ defines the depth of the TX FIFO
Line 71... Line 75...
 _UART_CTRL_?X_HALF_ and _UART_CTRL_*X_FULL_ flags in the `CTRL` register.
 _UART_CTRL_?X_HALF_ and _UART_CTRL_*X_FULL_ flags in the `CTRL` register.
 
 
If the RX FIFO is already full and new data is received by the receiver unit, the _UART_DATA_OVERR_ flag
If the RX FIFO is already full and new data is received by the receiver unit, the _UART_DATA_OVERR_ flag
in the `DATA` register is set indicating an "overrun". This flag is cleared by reading the `DATA` register.
in the `DATA` register is set indicating an "overrun". This flag is cleared by reading the `DATA` register.
 
 
 
[NOTE]
 
In contrast to other FIFO-equipped peripherals, software **cannot** determine the UART's FIFO size configuration
 
by reading specific control register bits (simply because there are no bits left in the control register).
 
 
 
 
**Hardware Flow Control - RTS/CTS**
**Hardware Flow Control - RTS/CTS**
 
 
UART0 supports optional hardware flow control using the standard CTS (clear to send) and/or RTS (ready to send
UART0 supports optional hardware flow control using the standard CTS (clear to send) and/or RTS (ready to send

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.