XR21V1410IL16TR-F [EXAR]
USB Bus Controller, CMOS, 3 X 3 MM, GREEN, MO-220VEED-4, QFN-16;
| 型号： | XR21V1410IL16TR-F |
| 厂家： | 
EXAR CORPORATION |
| 描述： | USB Bus Controller, CMOS, 3 X 3 MM, GREEN, MO-220VEED-4, QFN-16 外围集成电路 |
| 文件： | 总30页 (文件大小：371K) |
| 中文： | 中文翻译 | 下载： | 下载PDF数据表文档文件 |
XR21V1410
1-CH FULL-SPEED USB UART
REV. 1.4.0
JANUARY 2014
FEATURES
GENERAL DESCRIPTION
•
USB 2.0 Compliant, Full-Speed (12 Mbps)
The XR21V1410 (V1410) is an enhanced Universal
Asynchronous Receiver and Transmitter (UART) with
a USB interface. The USB interface is fully compliant
to Full Speed USB 2.0 specification that supports 12
Mbps USB data transfer rate. The USB interface also
supports USB suspend, resume and remote wakeup
operations.
■
Supports USB suspend, resume and remote
wakeup operations
•
•
•
± 5 kV HBM ESD protection on USB data pins
± 2 kV HBM ESD protection on all other pins
Enhanced UART Features
The V1410 operates from an internal 48MHz clock
therefore no external crystal/oscillator is required as
in previous generation UARTs. With the fractional
baud rate generator, any baud rate can accurately be
generated using the internal 48MHz clock.
■
■
■
■
■
■
■
■
UART data rates up to 12 Mbps
Fractional Baud Rate Generator
128 byte TX FIFO
384 byte RX FIFO
The large 128-byte TX FIFO and 384-byte RX FIFO
of the V1410 helps to optimize the overall data
throughput for various applications. The automatic
transceiver direction control feature simplifies both
the hardware and software for half-duplex RS-485
applications. If required, the multidrop (9-bit) mode
with automatic half-duplex transceiver control feature
7, 8 or 9 data bits
1 or 2 stop bits
Odd, even, mark, space, or no parity
Automatic Hardware (RTS/CTS or DTR/DSR)
Flow Control
■
■
■
■
■
Automatic Software (Xon/Xoff) Flow Control
Multidrop mode
further
simplifies
typical
multidrop
RS-485
applications.
Auto RS-485 Half-Duplex Control
Half-Duplex mode
The V1410 operates from a single 2.97 to 3.63 volt
power supply and has 5V tolerant inputs. The V1410
is available in a 16-pin QFN package.
Selectable GPIO or Modem I/O
•
•
•
•
•
Internal 48 MHz clock
WHQL certified software drivers for Windows 2000,
XP, Vista, 7, 8 and CE, as well as Linux and Mac are
supported for the XR21V1410.
Single 3.3V power supply
5V tolerant GPIO inputs
APPLICATIONS
16-pin QFN package
•
•
•
•
•
•
Portable Appliances
Virtual COM Port WHQL certified drivers
External Converters (dongles)
Battery-Operated Devices
Cellular Data Devices
■
■
■
■
Windows 2000, XP, Vista, Win7 and Win8
Windows CE 4.2, 5.0, 6.0, 7.0
Linux
Mac
Factory Automation and Process Controls
Industrial applications
Exar Corporation 48720 Kato Road, Fremont CA, 94538 • (510) 668-7000 • FAX (510) 668-7017 • www.exar.com
XR21V1410
1-CH FULL-SPEED USB UART
REV. 1.4.0
FIGURE 1. XR21V1410 BLOCK DIAGRAM
Internal
48MHz
Oscillator
128- byte
TX FIFO
TX
RX
Fractional
BRG
384- byte
RX FIFO
USB Slave
Interface
USBD+
USBD-
GPIO5/RTS#/RS485
GPIO4/CTS#
GPIO3/DTR#
GPIO2/DSR#
GPIO1/CD#
Internal
Status and
Control
GPIOs/
Modem IO
SDA
SCL
I2 C
Interface
Registers
GPIO0/RI#/RWK#
3.3V VCC
GND
UART
FIGURE 2. PIN OUT ASSIGNMENT
16 15 14 13
1
12 SCL
11 SDA
10 RX
9 TX
GND
16-Pin
QFN
LOWPOWER 2
GPIO5/RTS#/RS485
3
GPIO4/CTS# 4
5 6 7 8
ORDERING INFORMATION
P
ART
NUMBER
P
ACKAGE
O
PERATING
TEMPERATURE
R
ANGE
DEVICE STATUS
XR21V1410IL16-F
XR21V1410IL16TR-F
XR21V1410IL16MTR-F
16-pin QFN
16-pin QFN
16-pin QFN
-40°C to +85°C
-40°C to +85°C
-40°C to +85°C
Active
Active
Active
NOTE: TR = Tape and Reel, MTR = Mini Tape and Reel, F = Green / RoHS
2
XR21V1410
REV. 1.4.0
1-CH FULL-SPEED USB UART
PIN DESCRIPTIONS
16-QFN
NAME
TYPE
DESCRIPTION
P
IN #
UART Signals
RX
10
9
I
UART Channel A Receive Data or IR Receive Data. This pin has an internal
pull-up resistor. Internal pull-up resistor is not disabled during suspend mode.
TX
O
UART Channel A Transmit Data or IR Transmit Data.
8
I/O
GPIO0/RI#/RWK#
General purpose I/O or UART Ring-Indicator input (active low) or Remote
Wakeup input. See “Section 1.5.13, Remote Wakeup” on page 11
.
This pin has an internal pull-up resistor which is disabled during suspend
mode. If using this GPIO as an input, an external pull-up resistor is required to
minimize the device power consumption in the suspend mode.
7
6
I/O
I/O
GPIO1/CD#
General purpose I/O or UART Carrier-Detect input (active low). This pin has an
internal pull-up resistor which is disabled during suspend mode. If using this
GPIO as an input, an external pull-up resistor is required to minimize the
device power consumption in the suspend mode.
GPIO2/DSR#
General purpose I/O or UART Data-Set-Ready input (active low). See ”Sec-
tion 1.5.6, Automatic DTR/DSR Hardware Flow Control” on
page 9.
This pin has an internal pull-up resistor which is disabled during suspend
mode. If using this GPIO as an input, an external pull-up resistor is required to
minimize the device power consumption in the suspend mode.
5
I/O
GPIO3/DTR#
General purpose I/O or UART Data-Terminal-Ready output (active low). See
”Section 1.5.6, Automatic DTR/DSR Hardware Flow Control” on
page 9.
This pin has an internal pull-up resistor which is disabled during suspend
mode. If using this GPIO as an input, an external pull-up resistor is required to
minimize the device power consumption in the suspend mode.
4
3
I/O
I/O
GPIO4/CTS#
General purpose I/O or UART Clear-to-Send input (active low). See ”Sec-
tion 1.5.5, Automatic RTS/CTS Hardware Flow Control” on page 9.
This pin has an internal pull-up resistor which is disabled during suspend
mode. If using this GPIO as an input, an external pull-up resistor is required to
minimize the device power consumption in the suspend mode.
GPIO5/RTS#/RS485
General purpose I/O or UART Request-to-Send output (active low) or auto RS-
485 half-duplex control. See “Section 1.5.5, Automatic RTS/CTS Hard-
ware Flow Control” on page 9 or “Section 1.5.8, Auto RS-485 Half-
Duplex Control” on page 10. This pin has an internal pull-up resistor
which is disabled during suspend mode. If using this GPIO as an input, an
external pull-up resistor is required to minimize the device power consumption
in the suspend mode.
USB Interface Signals
USBD+
15
14
I/O
I/O
USB port differential data plus. This pin has a 1.5 K Ohm internal pull-up.
USB port differential data minus.
USBD-
3
XR21V1410
1-CH FULL-SPEED USB UART
REV. 1.4.0
16-QFN
NAME
TYPE
DESCRIPTION
P
IN #
I2C Interface Signals
SDA
11
I/O
OD
I2C-controller data input/output (open-drain). An optional external I2C
EEPROM can be used to store default configurations upon power-up including
the USB Vendor ID and Device ID. See Table 3. A pull-up resistor (typically
4.7 to 10k Ohms) is required.
If an EEPROM is not used, this pin can be used with the SCL pin to select the
Remote Wake-up and Power modes. An external pull-up or pull-down resistor
is required. See Table 2
SCL
12
I/O
OD
I2C-controller serial input clock. An optional external I2C EEPROM can be
used to store default configurations upon power-up including the USB Vendor
ID and Device ID. See Table 3. A pull-up resistor (typically 4.7 to 10k Ohms)
is required.
If an EEPROM is not used, this pin can be used with the SDA pin to select the
Remote Wake-up and Power modes. An external pull-up or pull-down resistor
is required. See Table 2
Miscellaneous Signals
2
O
LOWPOWER
Low power status output. The LOWPOWER pin will be asserted whenever it is
not safe to draw the amount of current from VBUS power requested in the
Device Max Power field of the Configuration Descriptor. The LOWPOWER pin
will behave differently for a low power device and a high power device.
•
Low-power device (<= 1 unit load or 100 mA i.e. bMaxPower <= 0x32): LOW-
POWER pin is asserted when the USB UART is in suspend mode.
High-power deivce (bMaxPower > 0x32): LOWPOWER pin is
•
asserted when the USB UART is in suspend mode or when it is not yet
configured.
The LOWPOWER pin will be de-asserted whenever it is safe to draw the
amount of current requested in the Device Maximum Power field.
This pin is sampled momentarily at power-up or at any USB bus reset to config-
ure the polarity of the LOWPOWER output during suspend mode. An external
(10K) pull-up resistor will cause the LOWPOWER pin to be asserted HIGH dur-
ing suspend mode. An external (3.3K) pull-down resistor will cause the LOW-
POWER pin to be asserted LOW during suspend mode.
Power / Ground Signals
16
Pwr
Pwr
Pwr
VCC
GND
GND
+3.3V power supply.
1, 13
Power supply common, ground.
Center
Pad
The center pad on the back side of the QFN package is metallic and should be
connected to GND on the PCB. The thermal pad size on the PCB should be
the approximate size of this center pad and should be solder mask defined.
The solder mask opening should be at least 0.0025" inwards from the edge of
the PCB thermal pad.
NOTE: Pin type: I=Input, O=Output, I/O= Input/output, OD=Output Open Drain.
4
XR21V1410
REV. 1.4.0
1-CH FULL-SPEED USB UART
1.0 FUNCTIONAL DESCRIPTIONS
1.1
USB interface
The USB interface of the V1410 is compliant with the USB 2.0 Full-Speed Specifications. The USB
configuration model presented by the V1410 to the device driver is compatible to the Abstract Control Model of
the USB Communication Device Class (CDC-ACM). The V1410 uses the following set of parameters:
•
1 Control Endpoint
Endpoint 0 as outlined in the USB specifications
■
•
•
1 Configuration is supported
2 interfaces for the UART channel
■
Single interrupt endpoint
■
Bulk-in and bulk-out endpoints
1.1.1
USB Vendor ID
Exar’s USB Vendor ID is 0x04E2. This is the default Vendor ID that is used for the V1410 unless a valid
EEPROM is present on the I2C interface signals. If a valid EEPROM is present, the Vendor ID from the
EEPROM will be used.
1.1.2
USB Product ID
The default USB Product ID for the V1410 is 0x1410. If a valid EEPROM is present, the Product ID from the
EEPROM will be used. Note that Exar’s custom drivers for all Windows OS require that the Product ID be an
even number for the V1410 device for proper identification of the device.
1.2
USB Device Driver
The V1410 device can be used with either a standard CDC-ACM driver or a custom driver. When the CDC-
ACM driver is used, the driver has no capability to read or write the V1410 device registers. Because of this,
the V1410 device is initialized to the settings in Table 1. With a custom driver, all GPIOs default in hardware to
inputs but these settings may be modified by the custom driver.
TABLE 1: V1410 REGISTER DEFAULTS WITH CDC-ACM DRIVER
REGISTER
VALUE
NOTES
FLOW_CONTROL
GPIO_MODE
0x01
0x01
0x08
0x30
Hardware flow control
RTS / CTS flow control
GPIO_DIRECTION
GPIO_INT_MASK
GPIO3/DTR# configured as an output
GPIO0/RI#, GPIO1/CD# and GPIO2/DSR# are interrupt sensi-
tive, i.e. can cause a USB interrupt to be generated
Note also that when using a CDC-ACM driver, the V1410 will automatically change the bMaxPacketSize to 63
bytes to compensate for a known issue with the Microsoft CDC-ACM device driver. A register is available to
change this setting with a custom driver as well. See “Section 3.4.1, CUSTOM Register Description (Read/
Write)” on page 23. Although there is no ability to read / write registers when using the CDC-ACM driver,
basic UART functions, including setting baud rate, character format and sending line break are supported by
the CDC driver. Refer to the 4 CDC_ACM_IF USB Control Commands listed in Table 4, “Supported USB
Control Commands,” on page 12.
1.3
I2C Interface
The I2C interface provides connectivity to an external I2C memory device (i.e. EEPROM) that can be read by
the V1410 for configuration. If no external EEPROM is present, the SDA and SCL are used to specify remote
wakeup support and power mode as described in Table 2. These pins are sampled at power-up.
5
XR21V1410
1-CH FULL-SPEED USB UART
REV. 1.4.0
TABLE 2: REMOTE
WAKEUP AND
POWER
MODES
R
EMOTE AKE-
W
UP
SDA
SCL
POWER MODE
S
UPPORT
1
1
0
0
1
0
1
0
No
Self-Powered
Bus-Powered
Self-Powered
Bus-Powered
No
Yes
Yes
1.3.1
EEPROM Contents
If SDA and SCL are both logic ’1’, the V1410 device will first confirm if there is an external EEPROM attached
by attempting to read the first 8 locations of the ROM. If address 0x07 of the ROM contains the value 0x58 (as
specified in Table 3), the contents of the ROM are assumed to be valid. Otherwise the EEPROM will be
ignored and the SDA / SCL bits are used to indicate remote wakeup support and device power mode.
The I2C address must be 0xA0. An EEPROM can be used to override default Vendor IDs and Device IDs, as
well as other attributes and maximum power consumption. Exar provides an in-circuit EEPROM programming
utility through the USB interface using UART Control block 0x65. Refer to Table 5, “Control Blocks,” on
page 13. The EEPROM programming utility can be downloaded from the Exar website. These values are
uploaded from the EEPROM to the corresponding USB Standard Device Descriptor or Standard Configuration
Descriptor. For details of the USB Descriptors, refer to the USB 2.0 specifications.
TABLE 3: EEPROM CONTENTS
EEPROM
CONTENTS
ADDRESS
0
1
2
3
4
5
6
7
Vendor ID (LSB)
Vendor ID (MSB)
Product ID (LSB)
Product ID (MSB)
Device Attributes
Device Maximum Power
Reserved
Signature of 0x58 (’X’). If the signature is not correct, the contents of the EEPROM are ignored.
1.3.1.1
The Vendor ID value replaces the idVendor field in the USB Standard Device Descriptor.
1.3.1.2 Product ID
The Product ID value replaces the idProduct field in the USB Standard Device Descriptor.
Vendor ID
6
XR21V1410
REV. 1.4.0
1-CH FULL-SPEED USB UART
1.3.1.3
Device Attributes
The Device Attributes value replaces the bmAttributes field in the USB Standard Configuration Descriptor. The
default setting in the V1410 device is 0xA0. The bit field definitions are:
•
•
•
•
Bit 7 is reserved - set to ’1’
Bit 6 is Self-powered mode - set to ’0’ for bus-powered, set to ’1’ for self-powered
Bit 5 is Remote Wakeup support - set to ’0’ for no support, set to ’1’ for remote wakeup support
Bit 4:0 are reserved - set to ’0’
1.3.1.4
Device Maximum Power
The Device Maximum Power value replaces the bMaxPower field in the USB Standard Configuration
Descriptor. The value specified is in units of 2 mA. For example, the value 0x2F is decimal 47 or 94 mA. Note
that the default bMaxPower of the V1410 device is 94 mA.
1.4
UART Manager
The UART Manager enables/disables the UART including the TX and RX FIFOs. The UART Manager is
located in a separate register block from the UART registers.
1.5
UART
The UART can be configured via USB control transfers from the USB host. The UART transmitter and receiver
sections are described seperately in the following sections. At power-up, the V1410 will default to 9600 bps, 8
data bits, no parity bit, 1 stop bit, and no flow control. If a standard CDC driver accesses the V1410, defaults
will change. See ”Section 1.2, USB Device Driver” on page 5.
1.5.1
Transmitter
The transmitter consists of a 128-byte TX FIFO and a Transmit Shift Register (TSR). Once a bulk-out packet
has been received and the CRC has been validated, the data bytes in that packet are written into the TX FIFO
of the specified UART channel. Data from the TX FIFO is transferred to the TSR when the TSR is idle or has
completed sending the previous data byte. The TSR shifts the data out onto the TX output pin at the data rate
defined by the CLOCK_DIVISOR and TX_CLOCK_MASK registers. The transmitter sends the start bit
followed by the data bits (starting with the LSB), inserts the proper parity-bit if enabled, and adds the stop-
bit(s). The transmitter can be configured for 7 or 8 data bits with or without parity or 9 data bits without parity.
If 9 bit data is selected without wide mode, the 9th bit will always be ’0’.
1.5.1.1
Wide Mode Transmit
When both 9 bit data and wide mode are enabled, two bytes of data must be written. The first byte that is
loaded into the TX FIFO are the first 8 bits (data bits 7-0) of the 9-bit data. Bit-0 of the second byte that is
loaded into the TX FIFO is bit-8 of the 9-bit data. The data that is transmitted on the TX pin is as follows: start
bit, 9-bit data, stop bit. Use the WIDE_MODE register to enable wide mode.
1.5.2
Receiver
The receiver consists of a 384-byte RX FIFO and a Receive Shift Register (RSR). Data that is received in the
RSR via the RX pin is transferred into the RX FIFO. Data from the RX FIFO is sent to the USB host in
response to a bulk-in request. Depending on the mode, error / status information for that data character may
or may not be stored in the RX FIFO with the data.
1.5.2.1
Normal receive operation with 7 or 8-bit data
Data that is received is stored in the RX FIFO. Any parity, framing or overrun error or break status information
related to the data is discarded. Receive data format is shown in Figure 3.
1.5.2.2
Normal receive operation with 9-bit data
The first 8 bits of data received is stored in the RX FIFO. The 9th bit as well as any parity, framing or overrun
error or break status information related to the data is discarded.
7
XR21V1410
1-CH FULL-SPEED USB UART
REV. 1.4.0
F
IGURE 3. NORMAL OPERATION RECEIVE DATA FORMAT
7,8,or9bitdata
1ST byte 7 6 5 4 3 2 1 0
7=‘0’in7bitmode
1.5.2.3
Wide mode receive operation with 7 or 8-bit data
Two bytes of data are loaded into the RX FIFO for each byte of data received. The first byte is the received
data. The second byte consists of the error bits and break status. Wide mode receive data format is shown in
Figure 4.
1.5.2.4
Wide mode receive operation with 9-bit data
Two bytes of data are loaded into the RX FIFO for each byte of data received. The first byte is the first 8 bits of
the received data. The 9th bit received is stored in the bit 0 of the second byte. The parity bit is not received /
checked. The remainder of the 2nd byte consists of the framing and overrun error bits and break status.
F
IGURE 4. WIDE MODE RECEIVE DATA FORMAT
7or 8bit mode
1st byte
7 6 5 4 3 2 1 0
x x x x O F B P
7=‘0’ in7bit mode
2ndbyte
P=ParityError (=‘0’ if not enabled)
B=Break
F=FramingError
O=OverrunError
x=‘0’
9bit mode
1st byte
2ndbyte
7 6 5 4 3 2 1 0
x x x x O F B 8
B=Break
F=FramingError
O=OverrunError
x=‘0’
Error flags are also available from the ERROR_STATUS register and the interrupt packet, however these flags
are historical flags indicating that an error has occurred since the previous request. Therefore, no conclusion
can be drawn as to which specific byte(s) may have contained an actual error in this manner.
1.5.3
Rx FIFO Low Latency
In normal operation all bulk-in transfers will be of maxPacketSize (64) bytes to improve throughput and to
minimize host processing. When there are 64 bytes of data in the RX FIFO, the V1410 will acknowledge a
bulk-in request from the host and transfer the data packet. If there is less than 64 bytes in the RX FIFO, the
V1410 may NAK the bulk-in request indicating that data is not ready to transfer at that time. However, if there
is less than 64 bytes in the RX FIFO and no data has been received for more than 3 character times, the
V1410 will acknowledge the bulk-in request and transfer any data in the RX FIFO to the USB host.
In some cases, especially when the baud rate is low, this increases latency unacceptably. The V1410 has a
low latency register bit that will cause the V1410 to immediately transfer any received data in the RX FIFO to
8
XR21V1410
REV. 1.4.0
1-CH FULL-SPEED USB UART
the USB host, i.e. it will not wait for 3 character times. The custom driver can automatically set the
RX_FIFO_LOW_LATENCY register bit to force the V1410 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
The 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):
FIGURE 5. AUTO RTS AND CTS FLOW
C
ONTROL
O
PERATION
Local UART
UARTA
Rem ote UART
UARTB
RXA
TXB
Receiver FIFO
Trigger Reached
Transm itter
RTSA#
CTSB#
Auto RTS
Trigger Level
Auto CTS
M onitor
TXA
RXB
Receiver FIFO
Trigger Reached
Transm itter
CTSA#
RTSB#
Auto CTS
M onitor
Auto RTS
Trigger Level
9
6
1
RTSA#
CTSB#
O N
O N
O N
O FF
2
3
7
10
ON
O FF
TXB
RXA
8
11
5
4
1) CO M port opened, RX FIFO em pty, RTSA# output is asserted
2) Signal propagated to CTSB# input
3) Data bytes enter TX FIFO , begin transm itting on TXB
4) Data propagates to Receiving device RXA
5) RX FIFO reaches threshold
6) RTSA# de-asserts
7) Signal propagates to CTSB# input
8) Transm ission stops on TXB
9) USB Bulk-In em pties RX FIFO below threshold, R TSA# is asserted
10) Signal propagated to CTSB# input
11) Data bytes resum e transm itting on TXB
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’.
9
XR21V1410
1-CH FULL-SPEED USB UART
REV. 1.4.0
1.5.7
Automatic XON/XOFF Software Flow Control
When software flow control is enabled, the V1410 compares the receive data characters with the programmed
Xon or Xoff characters. If the received character matches the programmed Xoff character, the V1410 will halt
transmission as soon as the current character has completed transmission. Data transmission is resumed
when a received character matches the Xon character.
FLOW_CONTROL[2:0] = ’010’.
Software flow control is enabled when
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 22. 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 19. 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 V1410 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 V1410 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 V1410) that draws power from the host VBUS.
10
XR21V1410
REV. 1.4.0
1-CH FULL-SPEED USB UART
1.5.13 Remote Wakeup
When the V1410 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#/RWK# pin
must be configured as an input. Additionally, the V1410 device must have the remote wakeup feature support
indicated in the USB attributes - See “Section 1.3, I2C Interface” on page 5. Lastly, a custom software driver
must inform the USB host that the peripheral device supports the remote wake-up feature.
11
XR21V1410
1-CH FULL-SPEED USB UART
2.0 USB CONTROL COMMANDS
REV. 1.4.0
The following table shows all of the USB Control Commands that are supported by the V1410. Commands
included are standard USB commands, CDC-ACM commands and custom Exar commands.
TABLE 4: SUPPORTED USB CONTROL COMMANDS
R
EQUEST
NAME
REQUEST
VALUE
I
NDEX
L
ENGTH
DESCRIPTION
TYPE
DEV GET_STATUS
IF GET_STATUS
0x80
0
0
0
0
0
2
0
0
Device: remote wake-up +
self-powered
0x81
0
0
0
1-4,
0
2
129-
132
Interface: zero
EP GET_STATUS
0x82
0
0
0
0-4,
0
2
0
129-
136
Endpoint: halted
Device remote wake-up
Endpoint halt
DEV CLEAR_FEATURE
EP CLEAR_FEATURE
0x00
0x02
1
1
1
0
0
0
0
0
0
0
0
0
0
0-4,
129-
136
DEV SET_FEATURE
DEV SET_FEATURE
EP SET_FEATURE
0x00
0x00
0x02
3
3
3
1
2
0
00
0
0
0
0
test
0
0
0
0
0
0
0
Device remote wake-up
Test mode
0
0-4,
129-
136
Endpoint halt
SET_ADDRESS
0x00
0x80
5
6
addr
0
0
1
0
0
0
0
0
0
GET_DESCRIPTOR
len
len
Device descriptor
LSB MSB
len len
LSB MSB
GET_DESCRIPTOR
0x80
6
0
2
0
0
Configuration descriptor
GET_CONFIGURATION
SET_CONFIGURATION
GET_INTERFACE
0x80
0x00
0x81
0x21
8
9
0
n
0
0
0
0
0
0
0
0
0
0
0
0
1
0
1
7
0
0
0
0
10
32
0-7
CDC_ACM_IF
SET_LINE_CODING
0, 2,
4, 6
Set the UART baud rate,
parity, stop bits, etc.
CDC_ACM_IF
GET_LINE_CODING
0xA1
0x21
33
34
0
0
0
0, 2,
4, 6
0
0
7
0
0
0
Get the UART baud rate,
parity, stop bits, etc.
CDC_ACM_IF
SET_CONTROL_LINE_
val
0, 2,
4, 6
Set UART control lines
STATE
12
XR21V1410
REV. 1.4.0
1-CH FULL-SPEED USB UART
TABLE 4: SUPPORTED USB CONTROL COMMANDS
R
EQUEST
NAME
REQUEST
VALUE
I
NDEX
L
ENGTH
DESCRIPTION
TYPE
CDC_ACM_IF
SEND_BREAK
0x21
35
val
val
0, 2,
4, 6
0
0
0
Send a break for the speci-
fied duration
LSB MSB
XR_SET_REG
0x40
0
1
val
0
0
regis- block
ter
0
0
Exar custom command: set
one 8-bit register
val: 8-bit register value
register address: see
Table 7
block number: see Table 5
XR_GETN_REG
0xC0
0
regis- block count count Exar custom register: get
ter
LSB MSB
count 8-bit registers
register address: see
Table 7
block number: see Table 5
2.1
UART Block Numbers
The table below lists the block numbers for accessing each of the UART channels and the UART Manager..
TABLE 5: CONTROL BLOCKS
BLOCK
NAME
BLOCK
NUMBER
DESCRIPTION
UART
0
The configuration and control registers for the UART.
UART Manager
4
The control registers for the UART Manager. The UART Manager
enables/disables the TX and RX FIFOs for each UART.
I2C EEPROM
UART Custom
0x65
0x66
Accesses external EEPROM via I2C interface.
Custom UART control registers. Enables / disables for wide mode, low
latency mode and custom interrupt packet.
13
XR21V1410
1-CH FULL-SPEED USB UART
3.0 REGISTER SET DESCRIPTION
REV. 1.4.0
The internal register set of the V1410 consists of 3 different blocks of registers: the UART Manager, UART
registers and UART miscellaneous registers. The UART Manager controls the TX and RX enables and FIFOs
of all UART channels. The UART registers configure and control the remaining UART channel functionality
with the exception of low latency mode, wide mode and custom interrupt packet enables in the UART custom
register block.
Registers are accessed only via the USB interface by the XR_SET_REG and XR_GET_REG commands listed
in Table 4. The register address offsets are given in Table 6, Table 7 and Table 15, and the register blocks
are given in Table 5.
3.1
UART Manager Registers
TABLE 6: UART MANAGER REGISTERS
ADDRESS
REGISTER
NAME
BIT-7
B
IT-6
B
IT-5
B
IT-4
B
IT-3
B
IT-2
B
IT-1
BIT-0
0X10 FIFO_ENABLE
0
0
0
0
0
0
RX
TX
0X18 RX_FIFO_RESET
0x1C TX_FIFO_RESET
Bit-7
Bit-7
Bit-6
Bit-6
Bit-5
Bit-5
Bit-4
Bit-4
Bit-3
Bit-3
Bit-2
Bit-2
Bit-1
Bit-1
Bit-0
Bit-0
3.1.1
FIFO_ENABLE Registers
Enables the RX FIFO and TX FIFOs. For proper functionality, the UART TX and RX must be enabled in the
following order:
FIFO_ENABLE = 0x1
UART_ENABLE = 0x3
FIFO_ENABLE = 0x3
// Enable TX FIFO
// Enable TX and RX
// Enable RX FIFO
3.1.2
RX_FIFO_RESET and TX_FIFO_RESET Registers
Writing a non-zero value to these registers resets the FIFOs.
14
XR21V1410
REV. 1.4.0
1-CH FULL-SPEED USB UART
3.2
UART Register Map
TABLE 7: UART REGISTERS
A
DDRESS
R
EGISTER
N
AME
B
IT-7
B
IT-6
0
B
IT-5
0
B
IT-4
0
B
IT-3
0
B
IT-2
0
B
IT-1
0
B
IT-0
0
0X00 Reserved
0X01 Reserved
0X02 Reserved
0X03 UART_ENABLE
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
RX
Bit-1
Bit-9
Bit-17
Bit-1
Bit-9
Bit-1
Bit-9
TX
Bit-0
Bit-8
Bit-16
Bit-0
Bit-8
Bit-0
Bit-8
0X04 CLOCK_DIVISOR0
Bit-7
Bit-15
0
Bit-6
Bit-14
0
Bit-5
Bit-13
0
Bit-4
Bit-12
0
Bit-3
Bit-11
0
Bit-2
Bit-10
Bit-18
Bit-2
0x05
0x06
0x07
0x08
0x09
0x0A
0x0B
CLOCK_DIVISOR1
CLOCK_DIVISOR2
TX_CLOCK_MASK0
TX_CLOCK_MASK1
RX_CLOCK_MASK0
RX_CLOCK_MASK1
CHARACTER_FORMAT
Bit-7
Bit-15
Bit-7
Bit-15
Stop
Bit-6
Bit-14
Bit-6
Bit-14
Bit-5
Bit-13
Bit-5
Bit-13
Parity
Bit-4
Bit-12
Bit-4
Bit-12
Bit-3
Bit-11
Bit-3
Bit-11
Bit-10
Bit-2
Bit-10
Data Bits
Flow Control Mode Select
0x0C FLOW_CONTROL
Half-
Duplex
0
0
0
0
0x0D Reserved
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0x0E
0x0F
0x10
0x11
0x12
0x13
Reserved
Reserved
0
0
0
0
0
0
0
0
XON_CHAR
XOFF_CHAR
LOOPBACK_CTL
ERROR_STATUS
Bit-7
Bit-7
0
Bit-6
Bit-6
0
Bit-5
Bit-5
0
Bit-4
Bit-4
0
Bit-3
Bit-3
0
Bit-2
Bit-2
En
Bit-1
Bit-1
0
Bit-0
Bit-0
0
Break
Status
Overrun
Error
Parity
Error
Framing
Error
Break
Error
0
0
0
0x14
0x15
0x16
0x17
0x18
0x19
0x1A
TX_BREAK
RS485_DELAY
Reserved
Bit-7
Bit-6
Bit-5
Bit-4
Bit-3
Bit-2
Bit-1
Bit-0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Delay
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Reserved
Reserved
Reserved
GPIO_MODE
RS485
Polarity
0
0
0
0
Mode Select
0x1B
GPIO_DIRECTION
0
0
0
0
0
0
0
0
0
0
GPIO5
GPIO5
GPIO5
GPIO5
GPIO5
GPIO4
GPIO4
GPIO4
GPIO4
GPIO4
GPIO3
GPIO3
GPIO3
GPIO3
GPIO3
GPIO2
GPIO2
GPIO2
GPIO2
GPIO2
GPIO1
GPIO1
GPIO1
GPIO1
GPIO1
GPIO0
GPIO0
GPIO0
GPIO0
GPIO0
0x1C GPIO_INT_MASK
0x1D GPIO_SET
0x1E
0x1F
GPIO_CLEAR
GPIO_STATUS
15
XR21V1410
1-CH FULL-SPEED USB UART
REV. 1.4.0
3.3
All register bits default to a value of ’0’ unless otherwise noted.
3.3.1 UART_ENABLE Register Description (Read/Write)
UART Register Descriptions
This register enables the UART TX and RX. For proper functionality, the UART TX and RX must be enabled in
the following order:
FIFO_ENABLE = 0x1
UART_ENABLE = 0x3
// Enable TX FIFO
// Enable TX and RX of that channel
// Enable RX FIFO
FIFO_ENABLE = 0x3
UART_ENABLE[0]: Enable UART TX
•
Logic 0 = UART TX disabled.
Logic 1 = UART TX enabled.
•
UART_ENABLE[1]: Enable UART RX
•
Logic 0 = UART RX disabled.
Logic 1 = UART RX enabled.
•
UART_ENABLE[7:2]: Reserved
These bits are reserved and should remain ’0’.
3.3.2 CLOCK_DIVISOR0, CLOCK_DIVISOR1, CLOCK_DIVISOR2 Register Description (Read/Write)
These registers are used for programming the baud rate. The V1410 uses a 19-bit divisor and 16-bit mask
register. Using the internal 48MHz oscillator, the 19-bit divisor is calculated as follows:
CLOCK_DIVISOR = Trunc ( 48000000 / Baud Rate )
For example, if the the baud rate is 115200bps, then
CLOCK_DIVISOR = Trunc ( 48000000 / 115200 ) = Trunc (416.66667) = 416
CLOCK_DIVISOR0[7:0]: Baud rate clock divisor bits [7:0]
CLOCK_DIVISOR1[7:0]: Baud rate clock divisor bits [15:8]
CLOCK_DIVISOR2[2:0]: Baud rate clock divisor bits [18:16]
CLOCK_DIVISOR2[7:3]: Reserved
These bits are reserved and should remain ’0’.
3.3.3
TX_CLOCK_MASK0, TX_CLOCK_MASK1 Register Description (Read/Write)
A look-up table is used for the value of the 16-bit TX Clock mask registers. The index of the look-up table is
calculated as follows:
index = Trunc ( ( ( 48000000 / Baud Rate ) - CLOCK_DIVISOR ) * 32)
For example, if the baud rate is 115200bps, then the index will be:
index = Trunc ( ( ( 48000000 / 115200 ) - 416 ) * 32) = Trunc (21.3333) = 21
The values for some baud rates to program the TX_CLOCK_MASK registers are listed in Table 8. For baud
rates that are not listed, use the index to select TX_CLOCK_MASK register values from Table 9.
3.3.4
RX_CLOCK_MASK0, RX_CLOCK_MASK1 Register Description (Read/Write)
The values for some example baud rates to program the RX_CLOCK_MASK registers are listed in Table 8.
For baud rates that are not listed, use the same index calculated for the TX_CLOCK_MASK register to select
RX_CLOCK_MASK register values from Table 9.
16
XR21V1410
REV. 1.4.0
1-CH FULL-SPEED USB UART
TABLE 8: CLOCK
D
IVISOR AND
C
LOCK
M
ASK
VALUES FOR
C
OMMON
B
AUD
R
ATES
B
AUD
RATE
(
BPS
)
CLOCK
D
IVISOR (DECIMAL
)
TX CLOCK
MASK (HEX
)
RX CLOCK MASK (HEX)
1200
2400
40000
20000
10000
5000
2500
1250
833
416
208
104
96
0x0000
0x0000
0x0000
0x0000
0x0000
0x0000
0x0912
0x0B6D
0x0912
0x0208
0x0000
0x0912
0x0040
0x0000
0x0B6D
0x0000
0x0000
0x0104
0x0000
0x0492
0x076D
0x0000
0x0122
0x0B6D
0x0000
0x0000
0x0000
0x0000
0x0000
0x0000
0x0000
0x0000
0x0924
0x0B6A
0x0924
0x0040
0x0000
0x0924
0x0000
0x0000
0x0DB6
0x0000
0x0000
0x0108
0x0000
0x0492
0x0BB6
0x0000
0x0224
0x0DB6
0x0000
0x0000
4800
9600
19200
38400
57600
115200
230400
460800
500000
576000
921600
83
52
1000000
1152000
1500000
2000000
2500000
3000000
3125000
3500000
4000000
4250000
6250000
8000000
12000000
48
41
32
24
19
16
15
13
12
11
7
6
4
For baud rates that are not listed in the table above, use the index value calcuated using the formula in
“Section 3.3.3, TX_CLOCK_MASK0, TX_CLOCK_MASK1 Register Description (Read/Write)” on page 16
to determine which TX Clock and RX Clock Mask register values to use from Table 9. For the the RX Clock
Mask register, there are 2 values listed and would depend on whether the Clock Divisor is even or odd. For
even Clock Divisors, use the value from the first column. For odd Clock Divisors, use the value from the last
column.
17
XR21V1410
1-CH FULL-SPEED USB UART
REV. 1.4.0
TABLE 9:
T
TX AND RX CLOCK
MASK
VALUES
I
NDEX
RX CLOCK
M
ASK (HEX) -
RX CLOCK
M
ASK (HEX) -
TX CLOCK
MASK (HEX)
(DECIMAL
0
)
E
VEN LOCK
C
DIVISOR
ODD CLOCK DIVISOR
0x0000
0x0000
0x0100
0x0020
0x0010
0x0208
0x0104
0x0844
0x0444
0x0122
0x0912
0x0492
0x0252
0x094A
0x052A
0x0AAA
0x0AAA
0x0555
0x0B55
0x06B5
0x05B5
0x0B6D
0x076D
0x0EDD
0x0DDD
0x07BB
0x0F7B
0x0DF7
0x07F7
0x0FDF
0x0F7F
0x0FFF
0x0000
0x0000
0x0000
0x0400
0x0100
0x0040
0x0820
0x0210
0x0110
0x0888
0x0448
0x0248
0x0928
0x04A4
0x0AA4
0x0954
0x0554
0x0AD4
0x0AB4
0x05AC
0x0D6C
0x0B6A
0x06DA
0x0DDA
0x0BBA
0x0F7A
0x0EF6
0x0BF6
0x0FEE
0x0FBE
0x0EFE
0x0FFE
0x0000
0x0000
0x0100
0x0020
0x0010
0x0208
0x0108
0x0884
0x0444
0x0224
0x0924
0x0492
0x0292
0x0A52
0x054A
0x04AA
0x0AAA
0x05AA
0x055A
0x0B56
0x06D6
0x0DB6
0x0BB6
0x076E
0x0EEE
0x0DDE
0x07DE
0x0F7E
0x0EFE
0x07FE
0x0FFE
0x0FFD
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
18
XR21V1410
REV. 1.4.0
1-CH FULL-SPEED USB UART
3.3.5
CHARACTER_FORMAT Register Description (Read/Write)
This register controls the character format such as the word length (7, 8 or 9), parity (odd, even, forced ’0’, or
forced ’1’) and number of stop bits (1 or 2).
CHARACTER_FORMAT[3:0]: Data Bits.
TABLE 10: DATA BITS
DATA
BITS
CHARACTER_FORMAT[3:0]
7
0111
1000
1001
8
9
All other values for CHARACTER_FORMAT[3:0] are reserved.
CHARACTER_FORMAT[6:4]: Parity Mode Select
These bits select the parity mode. If 9-bit data mode has been selected, then writing to these bits will not have
any effect. In other words, there will not be an additional parity bit.
TABLE 11: PARITY
S
ELECTION
B
IT-6
B
IT-5
0
B
IT-4
0
P
ARITY SELECTION
0
No parity
Odd parity
Even parity
0
0
1
0
1
0
0
1
1
Force parity to mark, “1”
Force parity to space, “0”
1
0
0
CHARACTER_FORMAT[7]: Stop Bit select
This register selects the number of stop bits to add to the transmitted character and how many stop bits to
check for in the received character.
TABLE 12: STOP
B
IT
S
ELECTION
BIT-7
N
UMBER OF
S
TOP ITS
B
0
1 stop bit
2
2 stop bits
3.3.6
FLOW_CONTROL Register Description (Read/Write)
These registers select the flow control mode. These registers should only be written to when the UART is
disabled. Writing to the FLOW_CONTROL register when the UART is enabled will result in undefined
behavior. Note that the FLOW_CONTROL register settings are used in conjunction with the GPIO_MODE
register.
19
XR21V1410
1-CH FULL-SPEED USB UART
FLOW_CONTROL[2:0]: Flow control mode select
REV. 1.4.0
TABLE 13: FLOW
C
ONTROL
MODE
SELECTION
M
ODE
B
IT-2
B
IT-1
0
B
IT-0
0
M
ODE D
ESCRIPTION
0
0
No flow control, no address matching.
1
0
0
1
HW flow control enabled. Auto RTS/CTS or DTR/DSR must be selected by
GPIO_MODE.
2
3
0
0
1
1
0
1
SW flow control enabled
Multidrop mode - RX only after address match, TX independent. (Typically
used with GPIO_MODE 3)
4
1
0
0
Multidrop mode - RX / TX only after address match. (Typically used with
GPIO_MODE 4)
FLOW_CONTROL[3]: Half-Duplex Mode
•
Logic 0 = Normal (full-duplex) mode. The UART can transmit and receive data at the same time.
•
Logic 1 = Half-duplex Mode. In half-duplex mode, any data on the RX pin is ignored when the UART is
transmitting data.
FLOW_CONTROL[7:4]: Reserved
These bits are reserved and should remain ’0’.
3.3.7
XON_CHAR, XOFF_CHAR Register Descriptions (Read/Write)
The XON_CHAR and XOFF_CHAR registers store the XON and XOFF characters, respectively, that are used
in the Automatic Software Flow control. If the V1410 is configured in multidrop mode, the XON_CHAR and
XOFF_CHAR registers are instead used for address matching.
XON_CHAR[7:0]: XON Character
In Automatic Software Flow control mode, the UART will resume data transmission when the XON character
has been received.
For behavior in the Address Match mode, see “Section 1.5.9, Multidrop Mode with address matching” on
page 10.
XOFF_CHAR[7:0]: XOFF Character
In Automatic Software Flow control mode, the UART will suspend data transmission when the XOFF character
has been received.
For behavior in the Address Match mode, see “Section 1.5.9, Multidrop Mode with address matching” on
page 10.
3.3.8
LOOPBACK_CTL Register Descriptions (Read/Write)
LOOPBACK_CTL[1:0]: Reserved
These bits are reserved and should remain ’0’.
LOOPBACK_CTL[2]: Enable
•
Logic 0 = Internal UART (TX to RX) loopback is disabled.
Logic 1 = Internal UART (TX to RX) loopback is enabled.
•
LOOPBACK_CTL[7:3]: Reserved
These bits are reserved and should remain ’0’.
20
XR21V1410
REV. 1.4.0
1-CH FULL-SPEED USB UART
3.3.9
ERROR_STATUS Register Description - Read-only
This register reports any errors that may have occurred on the line such as framing, parity and overrun as well
as break status.
ERROR_STATUS[2:0]: Reserved
These bits are reserved. Any values read from these bits should be ignored.
ERROR_STATUS[3]: Break status
•
Logic 0 = No break condition
•
Logic 1 = A break condition has been detected (clears after read).
ERROR_STATUS[4]: Framing Error
•
Logic 0 = No framing error
•
Logic 1 = A framing error has been detected (clears after read). A framing error occurs when a stop bit is not
present when it is expected.
ERROR_STATUS[5]: Parity Error
•
Logic 0 = No parity error
•
Logic 1 = A parity error has been detected (clears after read).
ERROR_STATUS[6]: Overrun Error
•
Logic 0 = No overrun error
•
Logic 1 = An overrun error has been detected (clears after read). An overrun error occurs when the RX FIFO
is full and another byte of data is received.
ERROR_STATUS[7]: Break Status
•
Logic 0 = Break condition is no longer present.
•
Logic 1 = Break condition is currently being detected.
3.3.10 TX_BREAK Register Description (Read/Write)
Writing a non-zero value to this register causes a break condition to be generated continuously until the
register is cleared. If data is being shifted out of the TX pin, the data will be completely shifted out before the
break condition is generated.
3.3.11 RS485_DELAY Register Description (Read/Write)
RS485_DELAY[3:0]: Turn-around delay
This is the number of bit times the V1410 waits before de-asserting the GPIO5/RTS#/RS485 pin when it is
configured for automatic RS-485 half-duplex control.
RS485_DELAY[7:4]: Reserved
These bits are reserved and should be ’0’.
21
XR21V1410
1-CH FULL-SPEED USB UART
REV. 1.4.0
3.3.12 GPIO_MODE Register Description (Read/Write)
GPIO_MODE[2:0]: GPIO Mode Select
There are 4 modes of operation for the GPIOs. The descriptions can be found in “Section 1.5, UART” on
page 7.
TABLE 14: GPIO MODES
BITS
[2:0]
GPIO0 GPIO1
GPIO2
GPIO3
GPIO4
GPIO5
MODE DESCRIPTION
000
001
GPIO0 GPIO1
GPIO0 GPIO1
GPIO2
GPIO2
GPIO3
GPIO3
GPIO4
CTS#
GPIO5 GPIO Mode, All GPIO pins available as GPIO
RTS# GPIO4 and GPIO5 used for Auto RTS/CTS HW
Flow Control
010
GPIO0 GPIO1
DSR#
DTR#
GPIO4
GPIO5 GPIO2 and GPIO3 used for Auto DTR/DSR HW
Flow Control
011
100
GPIO0 GPIO1
GPIO0 GPIO1
GPIO2
GPIO2
GPIO3
GPIO3
GPIO4
GPIO4
RS485 GPIO5 used for auto RS-485 half-duplex control
RS485 GPIO5 used for auto RS-485 half-duplex control
after address match (See FLOW_CONTROL
mode 4).
GPIO_MODE[3]: RS485 Polarity
•
Logic 0 = GPIO5/RTS#/RS485 Low for TX
Logic 1 = GPIO5/RTS#/RS485 High for TX
•
GPIO_MODE[7:4]: Reserved
These register bits are reserved. When writing to these bits, the value should be ’0’. When reading from these
bits, they are undefined and should be ignored.
3.3.13 GPIO_DIRECTION Register Description (Read/Write)
This register controls the direction of pins configured as GPIO. (Pins configured for UART functions via the
GPIO_MODE register, e.g. RTS# are not controlled or reported in the GPIO_DIRECTION register.)
GPIO_DIRECTION[5:0]: GPIOx Direction
•
Logic 0 = GPIOx is an input.
Logic 1 = GPIOx is an output.
•
GPIO_DIRECTION[7:6]: Reserved
These register bits are reserved and should be ’0’.
3.3.14 GPIO_INT_MASK Register Description (Read/Write)
Enables / disables generation of a USB interrupt packet at the change of state of GPIO pins when they are
configured as inputs.
GPIO_INT_MASK[5:0]: GPIOx Interrupt Mask
•
Logic 0 = A change on this input causes the device to generate an interrupt packet.
Logic 1 = A change on this input does not cause the device to generate an interrupt packet.
•
GPIO_INT_MASK[7:6]: Reserved
These register bits are reserved and should be ’0’.
22
XR21V1410
REV. 1.4.0
1-CH FULL-SPEED USB UART
3.3.15 GPIO_SET Register Description (Read/Write)
Writing a ’1’ in this register drives the GPIO output high. Writing a ’0’ to a bit has no effect. Bits 7-6 are unused
and should be ’0’.
3.3.16 GPIO_CLEAR Register Description (Read/Write)
Writing a ’1’ in this register drives the GPIO output low. Writing a ’0’ to a bit has no effect. Bits 7-6 are unused
and should be ’0’.
3.3.17 GPIO_STATUS Register Description (Read-Only)
This register reports the current state of the GPIO pin.
3.4
UART Custom Registers
TABLE 15: UART CUSTOM REGISTERS
A
DDRESS
R
EGISTER
NAME
B
IT-7
B
IT-6
0
B
IT-5
0
B
IT-4
0
B
IT-3
0
B
IT-2
B
IT-1
BIT-0
0X03 CUSTOM
WIDE_
En
MaxPkt-
Size
0
0
0x04 LOW_LATENCY
0x06 CUSTOM_INT_PACKET
0
0
0
0
0
0
0
0
0
EN
GPIO5
GPIO4
GPIO3
GPIO0
GPIO2
GPIO1
3.4.1
CUSTOM Register Description (Read/Write)
This register controls the bMaxPacketSize and enables the Wide mode functionality for the UART.
CUSTOM[0]: Enable wide mode
•
Logic 0 = Normal (7, 8 or 9 bit data) mode
•
Logic 1 = Wide mode - See “Section 1.5.1.1, Wide Mode Transmit” on page 7, “Section 1.5.2.3, Wide
mode receive operation with 7 or 8-bit data” on page 8 and “Section 1.5.2.4, Wide mode receive
operation with 9-bit data” on page 8.
CUSTOM[1]: Max Packet Size
•
Logic 0 = bMaxPacketSize = 64 bytes
•
Logic 1 = bMaxPacketSize = 63 bytes (this bit is automatically set to ’1’ if the XR21V1410 receives a
CDC_ACM USB command)
CUSTOM[7:2]: Reserved
These bits are reserved and should remain ’0’
3.4.2
LOW_LATENCY Register Description (Read/Write)
This register is automatically set to logic ’1’ for baud rates below 46921 bps, and can be manually set for baud
rates of 46921 bps and higher. This register enables the Low latency feature of the UART. Write to this
register following any desired baud rate setting change.
LOW_LATENCY[0]: Enable Low Latency mode
•
Logic 0 = Receive data is not forwarded from the Rx FIFO until bMaxPacketSize (64 bytes) or timeout (3
characters) has occurred.
•
Logic 1 = All data in the RX FIFO is provided to the USB host at the next BULK IN request irrespective of the
number of bytes in the FIFO.
LOW_LATENCY[7:1]: Reserved
These bits are reserved and should remain ’0’.
23
XR21V1410
1-CH FULL-SPEED USB UART
REV. 1.4.0
3.4.3
CUSTOM_INT_PACKET (Read/Write)
This register is used to enable / disable GPIO status in the high data byte of the custom interrupt packet. See
Table 16, “Interrupt Packet Format,” on page 25 and Table 18, “Data Field of Customized Interrupt
Packet - Exar Vendor Specific,” on page 26.
CUSTOM_INT_PACKET[0]: GPIO1
•
Logic 0 = Disable GPIO1 status in custom interrupt packet.
Logic 1 = Enable GPIO1 status in custom interrupt packet.
•
CUSTOM_INT_PACKET[1]: GPIO2
•
Logic 0 = Disable GPIO2 status in custom interrupt packet.
Logic 1 = Enable GPIO2 status in custom interrupt packet.
•
CUSTOM_INT_PACKET[2]: Reserved
This bit is reserved and should remain ’0’.
CUSTOM_INT_PACKET[3]: GPIO0
•
•
Logic 0 = Disable GPIO0 status in custom interrupt packet.
Logic 1 = Enable GPIO0 status in custom interrupt packet.
•
CUSTOM_INT_PACKET[4]: GPIO3
•
Logic 0 = Disable GPIO3 status in custom interrupt packet.
Logic 1 = Enable GPIO3 status in custom interrupt packet.
•
CUSTOM_INT_PACKET[5]: GPIO4
•
Logic 0 = Disable GPIO4 status in custom interrupt packet.
Logic 1 = Enable GPIO4 status in custom interrupt packet.
•
CUSTOM_INT_PACKET[6]: GPIO5
•
Logic 0 = Disable GPIO5 status in custom interrupt packet.
Logic 1 = Enable GPIO5 status in custom interrupt packet.
•
CUSTOM_INT_PACKET[7]: Reserved
This bit is reserved and should remain ’0’.
24
XR21V1410
REV. 1.4.0
1-CH FULL-SPEED USB UART
TABLE 16: INTERRUPT PACKET FORMAT
S
IZE
OFFSET
F
IELD
VALUE
DESCRIPTION
(BYTES
)
0
bmRequestType
1
8’b10100001 D7 = Device-to-host direction
D6:5 = Class Type
D4-0: = Interface Recipient
1
2
4
bNotification
wValue
1
2
2
8’h20
Defined encoding for SERIAL_STATE
16’h0000
16’h0000
wIndex
D15-8 = Reserved (0)
D7-0 = Interface number, 8’h00 for the CDC Com-
mand Interface
6
8
wLength
Data
2
2
16’h0002
2 bytes of transferred data
Standard
int_status
D15-7 = Reserved (0)
D6 = bOverRun
(See Table 17
D5 = bParity
or Table 18
)
D4 = bFraming
D3 = bRingSignal (RI)
D2 = bBreak
D1 = bTxCarrier (DSR)
D0 = bRxCarrier (CD)
TABLE 17: DATA FIELD OF STANDARD INTERRUPT PACKET
BIT
(
S
)
F
IELD
DESCRIPTION
D15..D7
D6
Reserved (0)
bOverRun
bParity
Received data has been discarded due to overrun in the device.
A parity error has occured.
D5
D4
bFraming
bRingSignal
bBreak
A framing error has occured.
D3
State of ring signal detection of the device.
State of break detection mechanism of the device.
D2
D1
bTxCarrier
State of transmission carrier. This signal corresponds to V.24 signal 106 and
RS-232 signal DSR.
D0
bRxCarrier
State of receiver carrier detection mechanism of device. This signal corre-
sponds to V.24 signal 109 and RS-232 signal DCD.
If the Exar vendor specific packet mapping is enabled then the data field also includes status for all of the
UART / GPIO pins as follows:
25
XR21V1410
1-CH FULL-SPEED USB UART
REV. 1.4.0
TABLE 18: DATA
F
IELD OF
C
USTOMIZED
INTERRUPT
PACKET - EXAR VENDOR SPECIFIC
BIT
(
S
)
F
IELD
DESCRIPTION
15
D15
Reserved (0)
14
13
12
11
10
9
D14
D13
D12
D11
D10
D9
bGPIO5 (RTS)
bGPIO4 (CTS)
bGPIO3 (DTR)
bGPIO0 (RI)
Reserved (0)
bGPIO2 (DSR)
bGPIO1 (CD)
Reserved (0)
bOverRun
8
D8
7
D7
6
D6
5
D5
bParity
4
D4
bFraming
3
D3
bRingSignal (RI)
bBreak
2
D2
1
D1
bTxCarrier (DSR)
bRxCarrier (CD)
0
D0
26
XR21V1410
REV. 1.4.0
1-CH FULL-SPEED USB UART
4.0 ELECTRICAL CHARACTERISTICS
TABLE 19: ABSOLUTE
MAXIMUM
R
ATINGS
P
ARAMETER
RATING
UNIT
Vcc Supply Voltage
Input Voltage (all pins except USBD+ and USBD-)
Input Voltage (USBD+ and USBD-)
Junction Temperature
+ 4.0
V
V
- 0.3 to + 6.0
- 0.3 to + 5.75
125
V
deg. C
DC ELECTRICAL CHARACTERISTICS - POWER CONSUMPTION
U
NLESS OTHERWISE NOTED: TA = -40O TO +85OC, VCC IS 2.97 TO 3.63V
L
IMITS
S
YMBOL
P
ARAMETER
3.3V
TYP
UNITS
CONDITIONS
M
IN
MAX
ICC
Power Supply Current
Suspend mode Current
16
20
1.65
mA
mA
ISusp
1.5
DC ELECTRICAL CHARACTERISTICS - UART, LOWPOWER & GPIO PINS
U
NLESS OTHERWISE NOTED: TA = -40O TO +85OC, VCC IS 2.97 TO 3.63V
L
IMITS
S
YMBOL
P
ARAMETER
3.3V
UNITS
CONDITIONS
MIN
MAX
VIL
VIH
VOL
VOH
IIL
Input Low Voltage
-0.3
0.8
V
V
V
V
Input High Voltage
2.0
2.2
5.5
0.3
Output Low Voltage
IOL = 4 mA
IOH = -4 mA
Output High Voltage
Input Low Leakage Current
Input High Leakage Current
Input Pin Capacitance
±10
±10
5
uA
uA
pF
IIH
CIN
27
XR21V1410
1-CH FULL-SPEED USB UART
REV. 1.4.0
DC ELECTRICAL CHARACTERISTICS - USB I/O PINS
U
NLESS OTHERWISE NOTED: TA = -40O TO +85OC, VCC IS 2.97 TO 3.63V
L
IMITS
S
YMBOL
P
ARAMETER
3.3V
UNITS
CONDITIONS
MIN
MAX
VIL
VIH
VOL
Input Low Voltage
Input High Voltage
Output Low Voltage
-0.3
0.8
V
V
V
2.0
0
5.5
0.3
External 15 K Ohm to
GND on USBD- pin
VOH
Output High Voltage
2.8
28
3.6
V
External 15 K Ohm to
GND on USBD- pin
VDrvZ
IOSC
Driver Output Impedance
Open short current Current
44
Ohms
mA
38.5
1.5 V on USBD+ and
USBD-
28
XR21V1410
REV. 1.4.0
1-CH FULL-SPEED USB UART
PACKAGE DIMENSIONS (16 PIN QFN - 3 X 3 X 0.9 mm
)
NOTE: QFN16 theta ja = 36.4 deg. C/W, theta jc = 17.8 deg. C / W. All values are typical.
29
XR21V1410
1-CH FULL-SPEED USB UART
REV. 1.4.0
REVISION HISTORY
D
ATE
REVISION
DESCRIPTION
June 2009
1.0.0
Released Datasheet
September 2010
1.1.0
Clarified pin functionality, wide mode and low latency mode including registers /
blocks, clarified FLOW_CONTROL and GPIO_MODE register functionality.
April 2011
April 2012
1.2.0
1.3.0
Updated ordering information, SDA/SCL pin types, modified GPIO0 pin name and
added LOOPBACK_CTL register and description.
Updated LOWPOWER pin description, bMaxPacketSize and DC electrical charac-
terisitics. See PCN12-0305-01 for more details.
July 2013
1.3.1
1.4.0
Updated package drawing QFN16
January 2014
Added Windows driver versions, added absolute maximum tables, added ESD pro-
tection ratings, added QFN package center pad to pin descriptions, minor clarifica-
tions including requirement for even Product ID in Windows OS. Updated package
[ECN: 1402-04]
drawing.
NOTICE
EXAR Corporation reserves the right to make changes to the products contained in this publication in order to
improve design, performance or reliability. EXAR Corporation assumes no responsibility for the use of any
circuits described herein, conveys no license under any patent or other right, and makes no representation that
the circuits are free of patent infringement. Charts and schedules contained here in are only for illustration
purposes and may vary depending upon a user’s specific application. While the information in this publication
has been carefully checked; no responsibility, however, is assumed for inaccuracies.
EXAR Corporation does not recommend the use of any of its products in life support applications where the
failure or malfunction of the product can reasonably be expected to cause failure of the life support system or
to significantly affect its safety or effectiveness. Products are not authorized for use in such applications unless
EXAR Corporation receives, in writing, assurances to its satisfaction that: (a) the risk of injury or damage has
been minimized; (b) the user assumes all such risks; (c) potential liability of EXAR Corporation is adequately
protected under the circumstances.
Copyright 2014 EXAR Corporation
Datasheet January 2014.
Send your UART technical inquiry with technical details to hotline: uarttechsupport@exar.com.
Reproduction, in part or whole, without the prior written consent of EXAR Corporation is prohibited.
30
相关型号：
XR21V1412IL32-F
USB Bus Controller, CMOS, 5 X 5 MM, 0.90 MM HEIGHT, GREEN, MO-220VHHD-4, QFN-32
EXAR
XR21V1412IL32TR-F
USB Bus Controller, CMOS, 5 X 5 MM, 0.90 MM HEIGHT, GREEN, MO-220VHHD-4, QFN-32
EXAR
XR21V1414IM48TR-F
Serial I/O Controller, 4 Channel(s), 1.5MBps, CMOS, PQFP48, 7 X 7 MM, 1 MM HEIGHT, GREEN, TQFP-48
EXAR
©2020 ICPDF网 联系我们和版权申明