XR21V1414
13
REV. 1.3.0
4-CH FULL-SPEED USB UART
RX_FIFO_LOW_LATENCY register bit to force the V1414 to be in the low latency mode, or the user may
manually set this bit. With the CDC-ACM driver, the low latency mode is automatically set whenever the baud
rate is set to a value of less than 46921 bps using the CDC_ACM_IF_SET_LINE_CODING command.
1.5.4 GPIO
Each UART has 6 GPIOs. By hardware default the GPIOs are configured as inputs but may be modified by a
custom driver. Additionally, there are several modes that can be enabled to add additional feature such as
auto RTS/CTS flow control, auto DTR/DSR flow control or auto RS-485 half duplex control. See Table 14.
1.5.5 Automatic RTS/CTS Hardware Flow Control
GPIO5 and GPIO4 of the UART channel can be enabled as the RTS# and CTS# signals for Auto RTS/CTS
flow control when GPIO_MODE[2:0] = ’001’ and FLOW_CONTROL[2:0] = ’001’. Automatic RTS flow control is
used to prevent data overrun errors in local RX FIFO by de-asserting the RTS signal to the remote UART.
When there is room in the RX FIFO, the RTS pin will be re-asserted. Automatic CTS flow control is used to
prevent data overrun to the remote RX FIFO. The CTS# input is monitored to suspend/restart the local
transmitter (see Figure 5):
1.5.6 Automatic DTR/DSR Hardware Flow Control
Auto DTR/DSR hardware flow control behaves the same as the Auto RTS/CTS hardware flow control
described above except that it uses the DTR# and DSR# signals. For Auto hardware flow control,
FLOW_CONTROL[2:0] = ’001’. GPIO3 and GPIO2 become DTR# and DSR#, respectively, when
GPIO_MODE[2:0] = ’010’.
F
IGURE
5. A
UTO
RTS
AND
CTS F
LOW
C
ONTROL
O
PERATION
T r a n s m i t t e r
A u to C T S
M o n it o r
R e c e iv e r F IF O
T rig g e r R e a c h e d
A u to R T S
T r ig g e r L e v e l
R e m o te U A R T
U A R T B
R T S A #
C T S B #
T X B
R X A
O N O N
O F F
O N O N
O F F
1
2
3
4
1 ) C O M p o r t o p e n e d , R X F IF O e m p t y , R T S A # o u t p u t is a s s e r t e d
2 ) S ig n a l p ro p a g a te d t o C T S B # in p u t
3 ) D a ta b y t e s e n t e r T X F IF O , b e g in t r a n s m i t t i n g o n T X B
4 ) D a ta p ro p a g a t e s t o R e c e iv in g d e v i c e R X A
5 ) R X F I F O r e a c h e s t h r e s h o ld
6 ) R T S A # d e - a s s e r ts
7 ) S ig n a l p ro p a g a te s t o C T S B # in p u t
8 ) T ra n s m i s s io n s to p s o n T X B
9 ) U S B B u lk - In e m p tie s R X F IF O b e l o w th r e s h o ld , R T S A # is a s s e r t e d
1 0 ) S ig n a l p r o p a g a t e d to C T S B # in p u t
1 1 ) D a ta b y t e s r e s u m e t ra n s m i t t in g o n T X B
5
6
7
8
9
1 0
1 1
R T S A # C T S B #
T X BR X A
C T S A #
T X A
R T S B #
R X B
R e c e iv e r F I F O
T rig g e r R e a c h e d
A u to R T S
T rig g e r L e v e l
T ra n s m it t e r
A u to C T S
M o n i t o r
L o c a l U A R T
U A R T A
XR21V1414
14
4-CH FULL-SPEED USB UART
REV. 1.3.0
1.5.7 Automatic XON/XOFF Software Flow Control
When software flow control is enabled, the V1414 compares the receive data characters with the programmed
Xon or Xoff characters. If the received character matches the programmed Xoff character, the V1414 will halt
transmission as soon as the current character has completed transmission. Data transmission is resumed
when a received character matches the Xon character. Software flow control is enabled when
FLOW_CONTROL[2:0] = ’010’.
1.5.8 Auto RS-485 Half-Duplex Control
The Auto RS-485 Half-Duplex Control feature changes the behavior of the GPIO5/RTS#/RS485 pin when
enabled by the GPIO_MODE register bits 2-0. See ”Section 3.3.12, GPIO_MODE Register Description
(Read/Write)” on page 26. The FLOW_CONTROL register must also be set appropriately for use in multidrop
applications. See ”Section 3.3.6, FLOW_CONTROL Register Description (Read/Write)” on page 23. If
enabled, the transmitter automatically asserts the GPIO5/RTS#/RS485 output prior to sending the data. By
default, it de-asserts GPIO5/RTS#/RS485 following the last stop bit of the last character that has been
transmitted, but the RS485_DELAY register may be used to delay the deassertion. The polarity of the GPIO5/
RTS#/RS485 signal may also be modified using the GPIO_MODE register bit 3.
1.5.9 Multidrop Mode with address matching
The V1414 device has two address matching modes which are also set by the flow control register using
modes 3 and 4. These modes are intended for a multi-drop network application. In these modes, the
XON_CHAR register holds a unicast address and the XOFF_CHAR holds a multicast address. A unicast
address is used by a transmitting master to broadcast an address to all attached slave devices that is intended
for only one slave device. A multicast address is used to broadcast an address intended for more than one
recipient device. Each attached slave device should have a unique unicast address value stored in the
XON_CHAR register, while multiple slaves may have the same multicast adderss stored in the XOFF_CHAR
register. An address match occurs when an address byte (9th bit or parity bit is ’1’) is received that matches the
value stored in either the XON_CHAR or XOFF_CHAR register.
1.5.9.1 Receiver
If an address match occurs in either flow control mode 3 or 4, the address byte will not be loaded into the RX
FIFO, but all subsequent data bytes will be loaded into the RX FIFO. The UART Receiver will automatically be
disabled when an address byte is received that does not match the values in the XON_CHAR or XOFF_CHAR
register.
1.5.9.2 Transmitter
In flow control mode 3, the UART transmitter is always enabled, irrespective of the Rx address match. In flow
control mode 4, the UART transmitter will only be enabled if there is an Rx address match.
1.5.10 Programmable Turn-Around Delay
By default, the GPIO5/RTS#/RS485 pin will be de-asserted immediately after the stop bit of the last byte has
been shifted when auto RS-485 half-duplex control is enabled by the GPIO_MODE register. However, this
may not be ideal for systems where the signal needs to propagate over long cables. Therefore, the de-
assertion of GPIO5/RTS#/RS485 pin can be delayed from 1 to 15 bit times via the RS485_DELAY register to
allow for the data to reach distant UARTs.
1.5.11 Half-Duplex Mode
Half-duplex mode is enabled when FLOW_CONTROL[3] = 1. In this mode, the UART will ignore any data on
the RX input when the UART is transmitting data.
1.5.12 USB Suspend
All USB peripheral devices must support the USB suspend mode. Per USB standard, the V1414 device will
begin to enter the Suspend state if it does not detect any activity (including Start of Frame or SOF packets) on
its USB data lines for 3 ms. The device must then reduce power consumption from VBUS power within the
next 7 ms to the allowed limit of 2.5 mA for the suspended state. Note that in this context, the "device" is all
circuitry (including the V1414) that draws power from the host VBUS.
XR21V1414
15
REV. 1.3.0
4-CH FULL-SPEED USB UART
1.5.13 Remote Wakeup
When the V1414 is suspended, the GPIO0/RI#/RWK# pin can be used to request that the host exit the
Suspend state. A high to low transition on this pin will cause the device to signal a remote wakeup request to
the host via a custom driver. Note that the standard CDC-ACM driver does not support this feature. In order for
the remote wakeup to work, several things must be properly configured. First, the GPIO0/RI# pin must be
configured as an input. Additionally, the V1414 device must have the remote wakeup feature support indicated
in the USB attributes - See “Section 1.3, I2C Interface” on page 10. Lastly, the software driver must inform
the USB host that the peripheral device supports the remote wake-up feature.

XR21V1414IM48-F

Mfr. #:
Manufacturer:
MaxLinear
Description:
USB Interface IC 4-Ch 12Mbps 48MHz Internal clock; UART
Lifecycle:
New from this manufacturer.
Delivery:
DHL FedEx Ups TNT EMS
Payment:
T/T Paypal Visa MoneyGram Western Union

Products related to this Datasheet