|
|
PDF AT43311 Data sheet ( Hoja de datos )
| Número de pieza | AT43311 | |
| Descripción | USB Hub | |
| Fabricantes | ATMEL Corporation | |
| Logotipo |  |
|
Hay una vista previa y un enlace de descarga de AT43311 (archivo pdf) en la parte inferior de esta página. Total 24 Páginas | ||
|
No Preview Available !
AT43311
Features
• Self-Powered Hub with Bus Power Controller
• Full Compliance with USB Spec Rev 1.0
• Full Speed USB Host Interface
• Four Downstream Ports
• Downstream Support for Full Speed and Low Speed Transfer Rates
• Continual Monitoring of Port by System Host
• Individual Port Power Control
• USB Connection Status Indicators
• 6 MHz Oscillator with On-Chip PLL
Description
The AT43311 is a fully compliant USB hub chip with 5 ports, one upstream port and
four full/low-speed downstream ports. The AT43311 can be used as a stand alone or
can provide a simple and quick method of adding USB ports to an existing device.
As a repeater, the AT43311 provides upstream connectivity between the selected
function and the host. Connectivity involves setting up and tearing down connections,
handling bus faults, recovering from bus faults and detecting downstream device con-
nections and disconnections.
The AT43311 may also act as a hub controller managing the hub operations and
recording the status of the hub, bus transactions, and downstream ports. In this mode,
the AT43311 tracks and generates the bus enumeration, provides configuration infor-
mation to the host, provides individual port status to the host, and controls the port
operation based on host commands.
USB Hub
AT43311
Preliminary
Pin Configurations
SOIC/DIP/Cerdip
PWR2
PWR3
PWR4
VCC5
VSS
OSC1
OSC2
LFT
VCCA
OVL4
OVL3
OVL2
OVL1
VREF
GND
STAT4
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
32 PWR1
31 DP4
30 DM4
29 DP3
28 DM3
27 GND
26 DP2
25 DM2
24 VCC3
23 DP1
22 XDM1
21 DP0
20 DM0
19 STAT1
18 STAT2
17 STAT3
0738A-A
1
1 page  
AT43311
Endpoint0
Endpoint0 is the AT43311’s default endpoint used for enu-
meration of the Hub and exchange of configuration infor-
mation and requests between the Host and the AT43311.
Endpoint0 supports control transfers.
Standard USB Device Requests and class-specific Hub
Requests are supported through Endpoint0.
The Hub Controller supports the following descriptors
through Endpoint0 (Descriptors are described in detail in
the Descriptors Section of this document):
• Device Descriptor
• Configuration Descriptor
• Interface Descriptor
• Endpoint Descriptor
• Hub Descriptor
Endpoint1
Endpoint1 is used by the Hub Controller to send status
change information to the Host. Endpoint1 supports inter-
rupt transfers.
The Hub Controller samples the changes at the end of
every frame at time marker EOF2 in preparation for a
potential data transfer in the subsequent frame. The sam-
pled information is stored as a byte in Status Change Reg-
ister using a bitmap scheme.
Each bit in the Status Change Register corresponds to one
port as shown below.
An IN Token packet from the Host to Endpoint1 indicates a
request for port change status. If the Hub has not detected
any change on the ports or any changes in the hub itself,
then all bits in this register will be 0 and the Hub Controller
will return a NAK to requests on Endpoint1. If a change in
the port status exists, the Hub Controller will transfer the
whole byte. The Hub Controller will continue to report a sta-
tus change when polled until that particular change has
been removed by a ClearPortFeature request from the
Host. No status change will be reported by Endpoint1 until
the AT43311 has been enumerated and configured by the
Host through Endpoint0.
Power Management
The AT43311 is designed to be powered from the USB
bus. As such, the power consumption for the AT43311
itself is less than 100 mA. However, downstream devices
require separate power supplies. The AT43311 monitors
and controls each power supply to the individual down-
stream devices.
Careful design and selection of the power switch is
required to meet the USB specification. The USB specifica-
tions requires that the voltage drop at the power switch be
no more than 100 mV. USB requirements specify that a
downstream device may use a maximum of 500 mA. These
conditions are best met by using a MOSFET switch with an
on resistance of 200 mΩ or less.
As a sample power circuit, consider a P-channel enhance-
ment mode MOSFET. The condition of the port’s power is
monitored at the output side of the PMOS switch which is
connected to the port’s OVL[1:4] pin. During an overcurrent
condition, the MOSFET switch’s internal resistance causes
the MOSFET’s output voltage to drop at the OVL[1:4] pin. If
the MOSFET’s output voltage drops to less than the volt-
age at the VREF voltage reference pin, the AT43311 inter-
prets this drop as an overcurrent condition. The AT43311
does internal filtering to make sure that spurious or switch-
ing transients are ignored. If an overcurrent condition
exists, the AT43311 removes the power from that port by
de-activating the port’s PWR[1:4] pin and reports the condi-
tion to the Host.
Status Change Register
Bit Function
0 Hub status change
1 Port1 status change
2 Port2 status change
3 Port3 status change
4 Port4 status change
5-7 Reserved
Value
0
1
0
1
0
1
0
1
0
1
0
Meaning
No change in status
Change in status detected
No change in status
Change in status detected
No change in status
Change in status detected
No change in status
Change in status detected
No change in status
Change in status detected
Default values
5
5 Page 
AT43311
Standard Requests
All required Standard Requests are supported by the
AT43311. Standard Requests, or commands, are sent to
the AT43311 from the Host on the AT43311’s default pipe,
endpoint0. These requests are made using control trans-
fers to endpoint0. The request and request parameters are
sent in a Setup packet which consists of eight bytes. The
following sections describe which requests are supported
by the AT43311 and the corresponding responses as well
as those requests not supported and responded with a
STALL packet.
Clear Device Feature
A Clear Device Feature will disable its remote wakeup fea-
ture when the setup packet is:
Field
Value
bmRequestType
Byte 0
x0000000B
bRequest
Byte 1
01H
wValue
Byte 2
Byte 3
01H
00H
wIndex
Byte 4
Byte 5
00H
00H
wLength
Byte 6
Byte 7
00H
00H
Clear Interface Feature
AT43311 does not support this feature and will respond
with a STALL if a setup packet from the Host is decoded
as:
Field
Value
bmRequestType
Byte 0
x0000001B
bRequest
Byte 1
01H
wValue
Byte 2
Byte 3
xxH
xxH
wIndex
Byte 4
Byte 5
xxH
xxH
wLength
Byte 6
Byte 7
xxH
xxH
Clear Endpoint Feature
The Clear Endpoint Feature request causes the AT43311
to clear an endpoint’s stall status bit if the condition causing
the stall has been removed. A Clear Endpoint Feature
occurs if a setup packet from the Host is decoded as:
Field
Value
bmRequestType
Byte 0
x0000002B
bRequest
Byte 1
01H
wValue
Byte 2
Byte 3
00H
00H
wIndex
Byte 4
Byte 5
00H for EP0
81H for EP1
00H
wLength
Byte 6
Byte 7
00H
00H
Get_Configuration
Get_Configuration returns one byte of data. Bit 0 will be a
copy of bit 0 of the Controller_Status Register. All other bits
will be set to 0. This action will be taken, if the Setup packet
from host is decoded as:
Field
Value
bmRequestType
Byte 0
10000000B
bRequest
Byte 1
08H
wValue
Byte 2
Byte 3
00H
00H
wIndex
Byte 4
Byte 5
00H
00H
wLength
Byte 6
Byte 7
01H
00H
11
11 Page | ||
| Páginas | Total 24 Páginas | |
| PDF Descargar | [ Datasheet AT43311.PDF ] | |
Hoja de datos destacado
| Número de pieza | Descripción | Fabricantes |
| AT43310 | USB Hub | ATMEL Corporation |
| AT43311 | USB Hub | ATMEL Corporation |
| AT43312 | Self- and Bus- Powered USB Hub Controller | ATMEL Corporation |
| AT43312A | Self- and Bus-Bus-powered USB Hub Controller | ATMEL Corporation |
| Número de pieza | Descripción | Fabricantes |
| SLA6805M | High Voltage 3 phase Motor Driver IC. |
 Sanken |
| SDC1742 | 12- and 14-Bit Hybrid Synchro / Resolver-to-Digital Converters. |
 Analog Devices |
|
DataSheet.es es una pagina web que funciona como un repositorio de manuales o hoja de datos de muchos de los productos más populares, |
| DataSheet.es | 2020 | Privacy Policy | Contacto | Buscar |