USB3500-ABZJ Standard Microsystems (SMSC), USB3500-ABZJ Datasheet - Page 23

• Manufacturer Part Number: USB3500-ABZJ
• Manufacturer: Standard Microsystems (SMSC)

Specifications of USB3500-ABZJ

• Operating Temperature (min): 0C
• Operating Temperature Classification: Commercial
• Operating Temperature (max): 70C
• Package Type: QFN
• Rad Hardened: No
• Lead Free Status / Rohs Status: Compliant

Hi-Speed USB Host, Device or OTG PHY With UTMI+ Interface
Datasheet
SMSC USB3500
The assertion of RESET will cause the USB3500 to deasserts RXACTIVE and RXVALID. When the
RESET signal is deasserted the Receive State Machine starts looking for a SYNC pattern on the USB.
When a SYNC pattern is detected, the receiver will assert RXACTIVE. The length of the received Hi-
Speed SYNC pattern varies and can be up to 32 bits long or as short as 12 bits long when at the end
of five hubs.
After valid serial data is received, the data is loaded into the RX Holding Register on the rising edge
of CLKOUT, and RXVALID is asserted. The Link must read the DATA bus on the next rising edge of
CLKOUT. In normal mode (OPMODE = 00), then stuffed bits are stripped from the data stream. Each
time 8 stuffed bits are accumulated the USB3500 will negate RXVALID for one clock cycle, thus
skipping a byte time.
When the EOP is detected the USB3500 will negate RXACTIVE and RXVALID. After the EOP has
been stripped, the USB3500 will begin looking for the next packet.
The behavior of the USB3500 receiver is described below:
Notes:
RXACTIVE and RXREADY are sampled on the rising edge of CLKOUT.
After a EOP is complete the receiver will begin looking for SYNC.
The USB3500 asserts RXACTIVE when SYNC is detected.
The USB3500 negates RXACTIVE when an EOP is detected and the elasticity buffer is empty.
When RXACTIVE is asserted, RXVALID will be asserted if the RX Holding Register is full.
RXVALID will be negated if the RX Holding Register was not loaded during the previous byte time.
This will occur if 8 stuffed bits have been accumulated.
The Link must be ready to consume a data byte if RXACTIVE and RXVALID are asserted (RX Data
state).
Figure 6.5
RXACTIVE, RXERROR and DATA signals.
Figure
When a HS/FS PHY is in FS Mode there are approximately 40 CLKOUT cycles every byte time.
The Receive State Machine assumes that the Link captures the data on the DATA bus if RXACTIVE
and RXVALID are asserted. In FS mode, RXVALID will only be asserted for one CLKOUT per byte
time.
In
The SYNC pattern received by a device can vary in length. These figures assume that all but the
last 12 bits have been consumed by the hubs between the device and the host controller.
Figure
6.5,
6.5,
Figure 6.4 Receive Timing for Data with Unstuffed Bits
shows the timing relationship between the received data (DP/DM), RXVALID,
Figure 6.6
Figure 6.6
and
and
Figure 6.7
Figure 6.7
DATASHEET
are timing examples of a HS/FS PHY when it is in HS mode.
23
the SYNC pattern on DP/DM is shown as one byte long.
Revision 1.0 (06-05-08)