Datasheet

t
d17
t
d18
TXRDY
(A−B)
IOW
Active
Trigger
Lead
Byte 32D0−D7
Start
Bit
5 Data Bits
6 Data Bits
7 Data Bits
Parity
Bit
Stop
Bit
Data Bits (5−8)
TX (A−B)
D0 D1 D2 D3 D4 D5 D6 D7
TL16C752B-EP
www.ti.com SGLS153B –FEBRUARY 2003–REVISED DECEMBER 2007
TYPICAL CHARACTERISTICS (continued)
Figure 20. Transmit Ready Timing in FIFO Mode
Timing Error Condition
Texas Instruments has discovered a timing anomaly in the TL16C752B.
The problem only occurs under a special set of circumstances (non-FIFO mode) and can be worked around by
using certain timing. Depending on actual system application, some customers may not see this problem. There
are currently no plans to fix this problem, because it is felt that it is a minor issue. It is unlikely the device is used
in non-FIFO mode, and if it is, the software workaround does not have a significant impact on throughput (< 1%).
Problem Description
When using the non-FIFO (single byte) mode of operation, it is possible that valid data could be reported as
available by either the line status register (LSR) or the interrupt identification register (IIR), before the receiver
holding register (RHR) can be read. In other words, the loading of valid data in RHR may be delayed when the
part operates in non-FIFO mode. The data in the RHr is valid after a delay of one baud-clock period after the
update of the LSR or IIR. The baud-clock runs at 16× the baud rate. The following table is a sample of baud
rates and associated required delays. Depending on the operating environment, this time may well be
transparent to the system, e.g., less than the context switch time of the interrupt service routine.
This problem does not exist when using FIFO mode (64 byte) mode of operation.
BAUDRATE (BIT PER SECOND) REQUIRED DELAY (μs)
1200 52.1 ms
2400 26 ms
4800 13 ms
9600 6.5 ms
19200 3.3 ms
38400 1.6 ms
57600 1.1 ms
115200 0.5 ms
1000000 62.5 ns
Copyright © 2003–2007, Texas Instruments Incorporated Submit Documentation Feedback 23
Product Folder Links: TL16C752B-EP