Product specification
Supersedes data of 1999 Feb 25
1999 Jul 22
Page 2
Philips SemiconductorsProduct specification
PDIUSBH12USB 2-port hub
FEA TURES
•Complies with the Universal Serial Bus specification Rev. 1.0
•Complies with the ACPI, OnNOW, and USB power management
requirements
•Compliant with USB Human Interface Devices and Monitor
Control Class
•Compliant with System Management Bus Specification Rev. 1.0
•Two downstream ports with per packet connectivity and auto
speed detection
•Supports up to 3 embedded functions
•Integrated SIE (Serial Interface Engine), FIFO memory and
transceivers
•Automatic USB protocol handling
•High speed slave I
2
C Interface (up to 1 Mbit/s)
•Compatible with the PDIUSBH11 hardware and software
•Software controllable connection to USB bus (SoftConnect)
•Good USB downstream connection indicators that blink with traffic
(GoodLink)
•Low frequency 12 MHz crystal oscillator eases EMI design issues
•Programmable output clock frequency
•Bus powered capability with very low suspend current
•Controllable LazyClock output at 30 kHz (nominal) during suspend
•Single 3.3V supply with 5V tolerant I/O
•Available in 28-pin DIP and SO packages
•Full-scan design with high fault coverage (>99%) insures high
quality
•Higher than 8 KV in-circuit ESD protection lowers cost of extra
components
DESCRIPTION
The Universal Serial Bus Hub PDIUSBH12 is a cost and feature
optimized second generation USB Hub with 2 downstream ports and
3 embedded functions (compound hub). It is normally used in any
microcontroller-based system and communicates with the system
microcontroller over the high speed I
approach to implementing a hub and embedded functions allows the
designer to choose the optimum system microcontroller from the
available wide variety. This flexibility cuts down the development
time, risks and costs by allowing the use of the existing architecture
and the firmware investments. This results in the fastest way to
develop the most cost-effective USB peripheral solutions that need
hub functionality. The PDIUSBH12 is ideally suited for computer
monitors, docking stations, keyboards and many other applications
that use the I
The PDIUSBH12 conforms to the USB specification Rev 1.0, I2C
serial interface and the SMBus specifications. It is fully compliant
with the Human Interface Device Class and Monitor Control Class
specifications. Its low suspend power consumption along with the
programmable LazyClock output allows for easy implementation of
equipment that is compliant to the ACPI, OnNow and USB power
management requirements. The low operating power allows the
implementation of the bus powered or the compound powered hub
function.
The PDIUSBH12 is fully backward compatible to the first generation
PDIUSBH11 hardware and software. This allows an easy running
change in the manufacturing line to realize the cost savings. In
addition, it also incorporates the feature enhancements like
SoftConnect
lower frequency crystal oscillator, additional embedded functions
and integration of termination resistors. All of these feature
enhancements contribute to significant cost savings in the system
implementation and at the same time ease the implementation of
advanced USB functionality into the peripherals.
PACKAGESTEMPERATURE RANGEOUTSIDE NORTH AMERICANORTH AMERICAPKG. DWG. #
28-pin plastic SO–40°C to +85°CPDIUSBH12 DPDIUSBH12 DSOT136-1
28-pin plastic DIP–40°C to +85°CPDIUSBH12 NPDIUSBH12 NSOT117-1
1999 Jul 22853-2062 22025
2
Page 3
Philips SemiconductorsProduct specification
PDIUSBH12USB 2-port hub
BLOCK DIAGRAM
UPSTREAM
3.3V
1.5kΩ
D+
SoftConnect
PORT
D+
ANALOG
TX/R
HUB
D–
X
FULL SPEED
REPEATER
ANALOG
T
X/RX
D–D+
DOWNSTREAM
PORT 2
GOODLINK
CONTROL
LED
ANALOG
T
X/RX
D–D+
DOWNSTREAM
PORT 3
GOODLINK
CONTROL
LED
NOTE:
1. This is a conceptual block diagram and does not include each individual signal.
12 MHz
PLL
BIT CLOCK
RECOVERY
PHILIPS
SIE
END OF
FRAME
TIMERS
INTEGRATED
RAM
MEMORY
MANAGEMENT
UNIT
GENERAL
PORT
CONTROLLER
INTERRUPTSDA SCL
NO LIGHTLITBLINKING
NO
CONNECTION
CONNECTED
GOODLINK
I
SLAVE
INTERFACE
DATA
TRANSFER
SV00852
2
C
1999 Jul 22
3
Page 4
Philips SemiconductorsProduct specification
PDIUSBH12USB 2-port hub
Analog Transceivers
These transceivers interface directly to the USB cables through
some termination resistors. They are capable of transmitting and
receiving serial data at both “full speed” (12 Mbit/s) and “low speed”
(1.5 Mbit/s) data rates.
Hub Repeater
The hub repeater is responsible for managing connectivity on a per
packet basis. It implements packet signaling connectivity and
resume connectivity.
Low speed devices can be connected to downstream ports since the
repeater will not propagate upstream packets to downstream ports,
to which low speed devices are connected, unless they are
preceded by a PREAMBLE PID.
End of Frame Timers
This block contains the specified EOF1 and EOF2 timers which are
used to detect loss-of-activity and babble error conditions in the hub
repeater. The timers also maintain the low-speed keep-alive strobe
which is sent at the beginning of a frame.
General and Individual Port Controller
The general and individual port controllers together provide status
and control of individual downstream ports. Via the I
microcontroller can access the downstream ports and request or
change the status of each individual port.
Any change in the status or settings of the individual port will result
in an interrupt request. Via an interrupt register, the servicing
microcontroller can look up the downstream port which generated
the interrupt and request its new status. Any port status change can
then be reported to the host via the hub status change (interrupt)
endpoint.
2
C-interface a
PLL
A 12 MHz to 48 MHz clock multiplier PLL (Phase-Locked Loop) is
integrated on-chip. This allows for the use of low-cost 12 MHz
crystal. EMI is also minimized due to lower frequency crystal. No
external components are needed for the operation of the PLL.
Bit Clock Recovery
The bit clock recovery circuit recovers the clock from the incoming
USB data stream using 4X over-sampling principle. It is able to track
jitter and frequency drift specified by the USB specification.
Philips Serial Interface Engine (PSIE)
The Philips SIE implements the full USB protocol layer. It is
completely hardwired for speed and needs no firmware intervention.
The functions of this block include: synchronization pattern
recognition, parallel/serial conversion, bit stuffing/de-stuffing, CRC
checking/generation, PID verification/generation, address
recognition, handshake evaluation/generation.
Memory Management Unit (MMU) and Integrated
RAM
The MMU and the integrated RAM is used to handle the large
difference in data rate between USB, running in bursts of 12 Mbit/s
and the I
1 Mbit/s. This allows the microcontroller to read and write USB
packets at its own speed through I2C.
2
C interface to the microcontroller, running at up to
I2C Slave Interface
This block implements the necessary I2C interface protocol. A slave
2
I
C allows for simple micro-coding. An interrupt is used to alert the
microcontroller whenever the PDIUSBH12 needs attention. As a
2
slave I
C device, the PDIUSBH12 I2C clock: SCL is an input and is
controlled by the microcontroller. The I
Mbit/s.
2
C interface can run up to 1
SoftConnect
The connection to the USB is accomplished by bringing D+ (for
high-speed USB device) high through a 1.5 kΩ pull-up resistor. In
the PDIUSBH12, the 1.5 kΩ pull-up resistor is integrated on-chip
and is not connected to V
pull-down resistors are integrated on-chip and are not connected to
GND by default. The connection of the internal resistors to Vcc is
established through a command sent by the external/system
microcontroller. This allows the system microcontroller to complete
its initialization sequence before deciding to establish connection to
the USB. Re-initialization of the USB bus connection can also be
affected without requiring the pull out of the cable.
The PDIUSBH12 will check for USB VBUS availability before the
connection can be established. VBUS sensing is provided through
OCURRENT_N pin. See the pin description for details. Sharing of
VBUS sensing and overcurrent sensing can be easily accomplished
by using VBUS voltage as the pull-up voltage for the open drain
output of the overcurrent indication device.
It should be noted that the tolerance of the internal resistors is
higher (30%) than that specified by the USB specification (5%).
However, the overall V
can still be met with good margin. The decision to make use of this
feature lies with the users.
SoftConnect is a patent pending technology from Philips
Semiconductors.
by default. Similarly, the 15 kΩ
CC
voltage specification for the connection
SE
GoodLink
Good downstream USB connection indication is provided through
GoodLink
least one valid upstream traffic from the port, the LED indicator will
be ON. The LED indicator will blink on every valid upstream traffic. A
valid upstream traffic is defined as traffic with a good SOP and
terminated by a good EOP. During global suspend, all LEDs will be
OFF.
This feature provides a user-friendly indicator on the status of the
hub, the connected downstream devices and the USB traffic. It is a
useful field diagnostics tool to isolate the faulty equipment. This
feature helps lower the field support and the hotline costs.
technology . When the port is enabled and there is at
1999 Jul 22
4
Page 5
Philips SemiconductorsProduct specification
01Control
2–3: Downstream
03Control
14Generic
1
27Generic
39Generic
01Control
2–3: Downstream
03Control
1
14Generic
011Control
6
17Generic
013Control
7
19Generic
PDIUSBH12USB 2-port hub
ENDPOINT DESCRIPTIONS
There are two endpoint configuration modes supported by the PDIUSBH12, the Single Embedded Function mode and the Multiple (3)
Embedded Function mode. The Single Embedded Function mode is the default at power up reset. The Multiple (3) Embedded Function mode
can be configured by writing a zero to bit 7 of the first byte of the Set Mode command. Either mode is backward compatible to the PDIUSBH11.
T able 1. SINGLE EMBEDDED FUNCTION MODE (DEFAULT AT POWER UP)
FUNCTIONPORTSENDPOINT #
Hub
Embedded
Function 1
NOTE:
1. Hub interrupt endpoint is not indexed.
2. Generic endpoint can be used for Interrupt or Bulk endpoint.
0: Upstream
ENDPOINT
INDEX
0
1
–
2
5
6
8
TRANSFER
TYPE
Interrupt
DIRECTION
OUT8
IN8
IN1
OUT8
IN8
OUT8
IN8
OUT8
IN8
OUT8
IN8
MAX
PACKET SIZE
(BYTES)
T able 2. MULTIPLE (3) EMBEDDED FUNCTION MODE
FUNCTIONPORTSENDPOINT #
Hub
Embedded
Function 1
Embedded
Function 6
Embedded
Function 7
0: Upstream
1–InterruptIN1
ENDPOINT
INDEX
0
2
5
10
6
12
8
TRANSFER
TYPE
DIRECTION
OUT8
IN8
OUT8
IN8
OUT8
IN8
OUT8
IN8
OUT8
IN8
OUT8
IN8
OUT8
IN8
MAX
PACKET SIZE
(BYTES)
1999 Jul 22
5
Page 6
Philips SemiconductorsProduct specification
PDIUSBH12USB 2-port hub
PINNING
The PDIUSBH12 has two modes of operation. The first mode (Mode 0) configures the pins DNx_GL_N for GoodLink LED indication. The
second mode (Mode 1) configures the LED pins as per port overcurrent condition pins. An overcurrent condition on any port can be uniquely
identified in Mode 1. However, all downstream ports are disabled as a result of a single overcurrent condition. In addition to the two modes of
operation, the PDIUSBH12 can also be configured to take either a 48 MHz crystal oscillator (for backward compatibility to PDIUSBH11) or a 12
MHz crystal.
The internal 4X clock multiplier PLL will be activated when 12 MHz input XTAL mode is selected. Also, the output clock frequenc y is now
programmable rather than fixed to 12 MHz. The output clock frequency can be programmed through the Set Mode command. All these new
features are added while maintaining backward compatibility to the PDIUSBH11 through TEST2 and TEST1 pins.
TEST2 TEST1
00
01
10
11
MODE
MODE 0
(GoodLink)
MODE 0
(GoodLink)
MODE 1
(Individual Overcurrent)
MODE 1
(Individual Overcurrent)
NOTE:
1. Pin TEST3 should always be connected to Ground at all times.
Pin configuration
1
2
TEST2
3
TEST3
RESET_N
CLKOUT
OCURRENT_N /
OCURRENT2_N
SWITCH_N
DN3_GL_N /
OCURRENT3_N
4
5
GND
6
XTAL1
7
XTAL2
8
9
V
CC
10
11
1217
1316 RSVDDN2_GL_N
1415 RSVD
NOTE:
Pin 10 and Pin 14 show alternative pin functions, depending on
mode of operation (Mode 0 or Mode 1) as described in
3TEST3InputConnect to Ground
4RESET_NInputSTPower-on reset
5GNDPowerGround reference
6XTAL1InputCrystal connection 1 (48 or 12MHz depending on TEST1 pin)
7XTAL2OutputCrystal connection 2 (48 or 12MHz depending on TEST1 pin)
8CLKOUTOutput3mAProgrammable output clock for external devices
9V
10OCURRENT_NInputST
11SWITCH_NOutputOD6Enables power to downstream ports
12SUSPENDOutputOD6Device is in suspended state
13DN2_GL_NOutputOD6Downstream port 2 GoodLink LED indicator
14DN3_GL_NOutputOD6Downstream port 3 GoodLink LED indicator
15RSVDInputReserved. Connect to GND for normal operation.
16RSVDInputReserved. Connect to GND for normal operation.
17INT_NOutputOD6Connect to microcontroller interrupt
18SDAI/OOD6I2C bi-directional data
19SCLI/OOD6I2C bit-clock
20GNDPowerGround reference
21DN3_DPAI/ODownstream port 3 D+ connection
22DN3_DMAI/ODownstream port 3 D– connection
23DN2_DPAI/ODownstream port 2 D+ connection
24DN2_DMAI/ODownstream port 2 D- connection
25AGNDPowerAnalog Ground reference
26AV
27UP_DPAI/OUpstream D+ connection
28UP_DMAI/OUpstream D- connection
NOTE:
1. Signals ending in _N indicate active low signals.
ST: Schmitt Trigger
OD6: Open Drain with 6 mA drive
AI/O: Analog I/O
CC
CC
PowerVoltage supply 3.3V ± 0.3V
PowerAnalog voltage supply 3.3V ± 0.3V
Connect to Ground for 48MHz crystal input.
Connect to VCC for 12MHz crystal input.
Over-current notice to the device. This pin is also used to sense the USB VBUS.
A LOW on this pin of less than 2 seconds is interpreted as an overcurrent notice;
longer than 2 seconds is interpreted as loss of VBUS.
1999 Jul 22
7
Page 8
Philips SemiconductorsProduct specification
PDIUSBH12USB 2-port hub
Pin description (MODE 1 – Individual Overcurrent)
PIN NOPIN SYMBOLTYPEDRIVEDESCRIPTION
1TEST1Input
2TEST2InputConnect to V
3TEST3InputConnect to Ground
4RESET_NInputSTPower-on reset
5GNDPowerGround reference
6XTAL1InputCrystal connection 1 (48 or 12MHz depending on TEST1 pin)
7XTAL2OutputCrystal connection 2 (48 or 12MHz depending on TEST1 pin)
8CLKOUTOutput3mAProgrammable output clock for external devices
9V
10OCURRENT2_NInputST
11SWITCH_NOutputOD6Enables power to downstream ports
12SUSPENDOutputOD6Device is in suspended state
13DN2_GL_NOutputOD6Downstream port 2 GoodLink LED indicator
14OCURRENT3_NInputSTDownstream port 3 over-current notice
15RSVDInputReserved. Connect to GND for normal operation.
16RSVDInputReserved. Connect to GND for normal operation.
17INT_NOutputOD6Connect to microcontroller interrupt
18SDAI/OOD6I2C bi-directional data
19SCLI/OOD6I2C bit-clock
20GNDPowerGround reference
21DN3_DPAI/ODownstream port 3 D+ connection
22DN3_DMAI/ODownstream port 3 D– connection
23DN2_DPAI/ODownstream port 2 D+ connection
24DN2_DMAI/ODownstream port 2 D- connection
25AGNDPowerAnalog Ground reference
26AV
27UP_DPAI/OUpstream D+ connection
28UP_DMAI/OUpstream D- connection
NOTE:
1. Signals ending in _N indicate active low signals.
ST: Schmitt Trigger
OD6: Open Drain with 6 mA drive
AI/O: Analog I/O
CC
CC
PowerVoltage supply 3.3V ± 0.3V
PowerAnalog voltage supply 3.3V ± 0.3V
Connect to VCC for 48MHz crystal input.
Connect to Ground for 12MHz crystal input.
CC
Downstream port 2 over-current notice. This pin is also use to sense the USB
VBUS. A LOW on this pin of less than 2 seconds is interpreted as an overcurrent
notice; longer than 2 seconds is interpreted as loss of VBUS.
1999 Jul 22
8
Page 9
Philips SemiconductorsProduct specification
PDIUSBH12USB 2-port hub
APPLICATION DIAGRAM
USB
3.3V
UPSTREAM
12MHz
CLKOUT
H12
USB
5V
POWER SWITCH
AND
OVERCURRENT CIRCUIT
DOWNSTREAM
SWITCHED
5V
I2C Interface
The I2C bus is used to interface to an external microcontroller
needed to control the operation of the hub. For cost consideration,
the target system microcontroller can be shared and utilized for this
purpose. The PDIUSBH12 implements a slave I
the PDIUSBH12 needs to communicate with the microcontroller it
asserts an interrupt signal. The microcontroller services this interrupt
by reading the appropriate status register on the PDIUSBH12
through the I
refer to the
2
C bus. (For more information about the I2C serial bus,
I2C Handbook
, Philips order number 9397 750 00013).
The I2C interface on the PDIUSBH12 defines two types of
transactions:
1. command transaction
A command transaction is used to define which data (e.g., status
byte, buffer data, ...) will be read from / written to the USB
interface in the next data transaction. A data transaction usually
follows a command transaction.
2. data transaction
A data transaction reads data from / writes data to the USB
interface. The meaning of the data is dependent on the
command transaction which was sent before the data
transaction.
Two addresses are used to differentiate between command and
data transactions. Writing to the command address is interpreted as
a command, while reading from / writing to the data address is used
to transfer data between the PDIUSBH12 and the controller.
2
C interface. When
I2C
GOODLINK LED
µC
SV00853
ADDRESS TABLE
TYPE OF ADDRESS
Command0011 011 (binary)
Data0011 010 (binary)
PHYSICAL ADDRESS
(MSB to LSB)
Protocol
An I2C transaction starts with a ‘Start Condition’, followed by an
address. When the address matches either the command or data
address the transaction starts and runs until a ‘Stop Condition’ or
another ‘Start Condition’ (repeated start) occurs.
The command address is write-only and is unable to do a read. The
next bytes in the message are interpreted as commands. Several
command bytes can be sent after one command address. Each of
the command bytes is acknowledged and passed on to the Memory
Management Unit inside the PDIUSBH12.
When the start condition address matches the data address, the
next bytes are interpreted as data. When the RW bit in the address
indicates a ‘master writes data to slave’ (=‘0’) the bytes are received,
acknowledged and passed on to the Memory Management Unit. If
the RW bit in the address indicates a ‘master reads data from slave’
(=‘1’) the PDIUSBH12 will send data to the master. The I
must acknowledge all data bytes except the last one. In this way the
2
I
C interface knows when the last byte has been transmitted and it
then releases the SDA line so that the master controller can
generate the STOP condition.
Repeated start support allows another packet to be sent without
generating a Stop Condition.
Timing
2
The I
C interface in the PDIUSBH12 can support clock speeds up to
1MHz.
2
C-master
1999 Jul 22
9
Page 10
Philips SemiconductorsProduct specification
PDIUSBH12USB 2-port hub
COMMAND SUMMARY
Some commands have the same command code (e.g., Read Buffer and Write Buffer). In these cases, the direction of the Data Phase (read or
write) indicates which command is executed.
COMMAND NAME
Set Address / EnableHubD0hWrite 1 byte
Set Endpoint EnableHub + Embedded FunctionsD8hWrite 1 byte
Set ModeHub + Embedded FunctionsF3hWrite 2 bytes
Read Interrupt RegisterF4hRead 2 bytes
Select EndpointHub Control OUT00hRead 1 byte (optional)
Read Last Transaction StatusHub Control OUT40hRead 1 byte
Read Endpoint StatusHub Control OUT80hRead 1 byte
Read BufferSelected EndpointF0hRead n bytes
Write BufferSelected EndpointF0hWrite n bytes
Set Endpoint StatusHub Control OUT40hWrite 1 byte
Acknowledge SetupSelected EndpointF1hNone
Clear BufferSelected EndpointF2hNone
Validate Buf ferSelected EndpointFAhNone
Clear Port FeaturePort 2E0hWrite 1 byte
Set Port FeaturePort 2E8hWrite 1 byte
Get Port StatusPort 2E0hRead 1 or 2 bytes
Set Status Change BitsF7hWrite 1 byte
Send ResumeF6hNone
Read Current Frame NumberF5hRead 1 or 2 bytes
RECIPIENTCODINGDATA PHASE
Initialization Commands
Embedded Function 1D1hWrite 1 byte
Embedded Function 6D2hWrite 1 byte
Embedded Function 7D3hWrite 1 byte
Data Flow Commands
Hub Control IN01hRead 1 byte (optional)
Other Endpoints00h + Endpoint IndexRead 1 byte (optional)
Hub Control IN41hRead 1 byte
Other Endpoints40h + Endpoint IndexRead 1 byte
Hub Control IN81hRead 1 byte
Other Endpoints80h + Endpoint IndexRead 1 byte
Hub Control IN41hWrite 1 byte
Other Endpoints40h + Endpoint IndexWrite 1 byte
Hub Commands
Port 3E1hWrite 1 byte
Port 3E9hWrite 1 byte
Port 3E1hRead 1 or 2 bytes
General Commands
1999 Jul 22
10
Page 11
Philips SemiconductorsProduct specification
PDIUSBH12USB 2-port hub
COMMAND DESCRIPTIONS
Command Procedure
There are four basic types of commands: Initialization, Data, Hub
Specific, and General commands. Respectively, these are used to
initialize the hub and embedded function; for data flow between the
hub, embedded function, and the host; some hub specific
commands for controlling individual downstream ports; and some
general commands.
Initialization Commands
Initialization commands are used during the enumeration process of
the USB network. These commands are used to enable the hub and
embedded function endpoints. They are also used to set the USB
assigned address.
Set Address / Enable
Command: D0h (Hub), D1h, D2h, D3h,
Data: Write 1 byte
This command is used to set the USB assigned address and enable
the hub or embedded functions respectively. The hub powers up
enabled and needs not be enabled by the firmware at power up
initialization.
(Embedded Functions)
7654320100
000000
POWER ON VALUE
ADDRESS
ENABLE
SV00825
Set Endpoint Enable
Command: D8h
Data: Write 1 byte
The hub’s interrupt endpoint and the embedded functions generic
endpoints can only be enabled when the corresponding hub/function
is enabled via the Set Address/Enable command.
7654320100
00XXXX
Hub’s Interrupt EndpointA value of ‘1’ indicates
Embedded Function 1 Generic EndpointA value of ‘1’ indicates
Embedded Function 6 Generic EndpointA value of ‘1’ indicates
Embedded Function 7 Generic EndpointA value of ‘1’ indicates
POWER ON VALUE
HUB’S INTERRUPT ENDPOINT
EMBEDDED FUNCTION 1 GENERIC ENDPOINTS
EMBEDDED FUNCTION 6 GENERIC ENDPOINTS
EMBEDDED FUNCTION 7 GENERIC ENDPOINTS
RESERVED
SV00841
the hub’s interrupt
endpoint is enabled.
the embedded function
1 generic endpoints are
enabled.
the embedded function
6 generic endpoints are
enabled.
the embedded function
7 generic endpoints are
enabled.
AddressThe value written becomes the address.
EnableA ‘1’ enables this function.
1999 Jul 22
Set Mode
Command: F3h
Data: Write 2 bytes
The Set Mode command is followed by two data writes. The first
byte contains the configuration byte values. The second byte is the
clock division factor byte.
11
Page 12
Philips SemiconductorsProduct specification
PDIUSBH12USB 2-port hub
Configuration Byte
7654320110
Remote WakeupA ‘1’ indicates that a remote
No LazyClockA ‘1’ indicates that CLKOUT will
Clock RunningA ‘1’ indicates that the internal
Debug ModeA ‘1’ indicates that all errors and
SoftConnectA ‘1’ indicates that the upstream
110010
POWER ON VALUE
REMOTE WAKEUP
NO LAZYCLOCK
CLOCK RUNNING
DEBUG MODE
SoftConnect
CONNECT DOWNSTREAM RESISTORS
NON-BLINKING LEDs
EMBEDDED FUNCTION MODE
SV00842
wakeup feature is ON. Bus reset
will set this bit to ‘1’.
not switch to LazyClock. A ‘0’
indicates that the CLKOUT
switches to LazyClock 1ms after
the Suspend pin goes high.
LazyClock frequency is 30KHz (±
40%). The programmed value will
not be changed by a bus reset.
clocks and PLL are always
running even during Suspend
state. A ‘0’ indicates that the
internal clock, crystal oscillator
and PLL are stopped whenever
not needed. To meet the strict
Suspend current requirement, this
bit needs to be set to ‘0’. The
programmed value will not be
changed by a bus reset.
“NAKing” are reported and a ‘0’
indicates that only OK and
babbling are reported. The
programmed value will not be
changed by a bus reset.
pull-up resistor will be connected if
VBUS is available. A ‘0’ means
that the upstream resistor will not
be connected. The programmed
value will not be changed by a bus
reset.
Connect Downstream Resistors A ‘1’ indicates that downstream
resistors are connected. A ‘0’
means that downstream resistors
are not connected. The
programmed value will not be
changed by a bus reset.
Non-blinking LEDsA ‘1’ indicates that GoodLink
LEDs will NOT blink when there is
traffic. Leave this bit at ‘0’ to
achieve blinking LEDs. The
programmed value will not be
changed by a bus reset.
Embedded Function ModeA ‘1’ indicates single embedded
function mode. A ‘0’ indicates
multiple (3) embedded function
mode. See
endpoint descriptions
for details. The programmed value
will not be changed by a bus
reset.
Clock Division Factor Byte
7654321110
0000XX
111011XX
Clock Division FactorThe value indicates clock division
POWER ON VALUE FOR 48MHz INPUT
POWER ON VALUE FOR 12MHz INPUT
CLOCK DIVISION FACTOR
RESERVED
SV00843
factor for CLKOUT. The output
frequency is 48 MHz/(N+1) where
N is the Clock Division Factor. The
reset value is 3. This will give a
default output frequency at
CLKOUT pin of 12 MHz, thus
maintaining backward
compatibility to the PDIUSBH11.
When the 12 MHz input crystal
frequency is selected, the reset
value is 11. This will produce the
lowest output frequency of 4 MHz
which can then be programmed
up by the user. The PDIUSBH12
design ensures no glitching during
frequency change. The
programmed value will not be
changed by a bus reset.
1999 Jul 22
12
Page 13
Philips SemiconductorsProduct specification
PDIUSBH12USB 2-port hub
Data Flow Commands
Data flow commands are used to manage the data transmission
between the USB endpoints and the monitor. Much of the data flow
is initiated via an interrupt to the microcontroller. The microcontroller
utilizes these commands to access and determine whether the
endpoint FIFOs have valid data.
Read Interrupt Register
Command: F4h
Data: Read 2 bytes
Interrupt Register Byte 1
7654320100
Interrupt Register Byte 2
7654320100
This command indicates the origin of an interrupt. A ‘1’ indicates an
interrupt occurred at this endpoint. The bits are cleared by reading
the endpoint status register through Read Endpoint Status
command.
After a bus reset an interrupt will be generated and bit 6 of the
Interrupt Register Byte 2 will be ‘1’. [In the PDIUSBH11, the bus
reset event is indicated by the absence of a ‘1’ in any bit of the
Interrupt Register. Note that the backward compatibility is still
maintained because in the PDIUSBH11, the Interrupt Register Byte
2 does not exist.]
The bus reset interrupt is internally cleared by reading the interrupt
register. A bus reset is completely identical to the hardware reset
through the RESET_N pin with the sole difference of interrupt
notification.
The hub interrupt endpoint is handled internally by the PDIUSBH12
hardware without the need of microcontroller intervention.
000000
0000X0
POWER ON VALUE
ENDPOINT INDEX 0 (HUB CONTROL OUT)
ENDPOINT INDEX 1 (HUB CONTROL IN)
ENDPOINT INDEX 2
ENDPOINT INDEX 3
ENDPOINT INDEX 4
ENDPOINT INDEX 5
ENDPOINT INDEX 6
ENDPOINT INDEX 7
SV00844
POWER ON VALUE
ENDPOINT INDEX 8
ENDPOINT INDEX 9
ENDPOINT INDEX 10
ENDPOINT INDEX 11
ENDPOINT INDEX 12
ENDPOINT INDEX 13
BUS RESET
RESERVED
SV00845
Select Endpoint
Command: 00-0Dh
Data: Optional Read 1 byte
The Select Endpoint command initializes an internal pointer to the
start of the Selected buffer. Optionally, this command can be
followed by a data read, which returns ‘0’ if the buffer is empty and
‘1’ if the buffer is full.
765432X100
XXXXXX
POWER ON VALUE
FULL/EMPTY
RESERVED
SV00831
Full/EmptyA ‘1’ indicates the buffer is full, ‘0’
indicates an empty buffer.
Read Last Transaction Status
Command: 40–4Dh
Data: Read 1 byte
The Read Last Transaction Status command is followed by one data
read that returns the status of the last transaction of the endpoint.
This command also resets the corresponding interrupt flag in the
interrupt register, and clears the status, indicating that it was read.
This command is useful for debugging purposes. Since it keeps
track of every transaction, the status information is overwritten for
each new transaction.
7654320100
Data Receive/Transmit SuccessA ‘1’ indicates data has been
Error CodeSee Table 3, Error Codes.
Setup PacketA ‘1’ indicates the last
Data 0/1 PacketA ‘1’ indicates the last
Previous Status not ReadA ‘1’ indicates a second event
000000
POWER ON VALUE
DATA RECEIVE/TRANSMIT SUCCESS
ERROR CODE (SEE TABLE)
SETUP PACKET
DATA 0/1 PACKET
PREVIOUS STATUS NOT READ
SV00832
received or transmitted
successfully.
successful received packet
had a SETUP token (this will
always read ‘0’ for IN buffers.
successful received or sent
packet had a DATA1 PID.
occurred before the previous
status was read.
1999 Jul 22
13
Page 14
Philips SemiconductorsProduct specification
PDIUSBH12USB 2-port hub
Table 3.Error codes
ERROR
CODE
0000No Error
0001
0010
0011
0100Token CRC Error
0101Data CRC Error
0110Time Out Error
0111Babble Error
1000Unexpected End-of-packet
1001Sent or received NAK
1010
1011
1101Bitstuff Error
1111
PID encoding Error; bits 7–4 are not the inversion of
bits 3–0
PID unknown; encoding is valid, but PID does not
exist
Unexpected packet; packet is not of the type expected
(= token, data or acknowledge), or SETUP token to a
non-control endpoint
Sent Stall, a token was received, but the endpoint was
stalled
Overflow Error, the received packet was longer than
the available buffer space
Wrong DATA PID; the received DATA PID was not the
expected one
RESULT
Read Endpoint Status
Command: 80–8Dh
Data: Read 1 byte
765432X1X0
Setup PacketA ‘1’ indicates the last received
STALLA ‘1’ indicates the endpoint is
Data 0/1 PacketA ‘1’ indicates if the last received
Buffer FullA ‘1’ indicates that the buffer is
0000XX
POWER ON VALUE
RESERVED
SETUP PACKET
STALL
DATA 0/1 PACKET
BUFFER FULL
RESERVED
SV00833
packet had a SETUP token.
stalled.
or sent packet had a DATA1 PID.
full.
Read Buffer
Command: F0h
Data: Read multiple bytes (max 10)
The Read Buffer command is followed by a number of data reads,
which return the contents of the selected endpoint data buffer. After
each read, the internal buffer pointer is incremented by 1.
The buffer pointer is not reset to the buffer start by the Read Buffer
command. This means that reading or writing a buffer can be
interrupted by any other command (except for Select Endpoint), or
can be done by more than one I
to get the number of data bytes, then read the rest in other
transactions).
The data in the buffer are organized as follows:
2
C transaction (read the first 2 bytes
•byte 0:Reserved: can have any value
•byte 1:Number/length of data bytes
•byte 2:Data byte 1
•byte 3:Data byte 2
Write Buffer
Command: F0h
Data: Write multiple bytes (max 10)
The Write Buffer command is followed by a number of data writes,
which load the endpoints buffer. The data must be organized in the
same way as described in the Read Buffer command. The first byte
(reserved) should always be 0. As in the Read Buffer command, the
data can be split up into different I
WARNING:
There is no protection against writing or reading over a buffer’s
boundary or against writing into an OUT buffer or reading from an IN
buffer . Any of these actions could cause an incorrect operation. Data
in an OUT buffer are only meaningful after a successful transaction.
Clear Buffer
Command: F2h
Data: None
When a packet is received completely, an internal endpoint buffer
full flag is set. All subsequent packets will be refused by returning a
NAK. When the microcontroller has read the data, it should free the
buffer by the Clear Buffer command. When the buffer is cleared new
packets will be accepted.
Validate Buffer
Command: FAh
Data: None
When the microprocessor has written data into an IN buffer, it should
set the buffer full flag by the Validate Buffer command. This indicates
that the data in the buffer are valid and can be sent to the host when
the next IN token is received.
2
C data transactions.
1999 Jul 22
14
Page 15
Philips SemiconductorsProduct specification
PDIUSBH12USB 2-port hub
Set Endpoint Status
Command: 40–4Dh
Data: Write 1 byte
A stalled control endpoint is automatically unstalled when it receives
a SETUP token, regardless of the content of the packet. If the
endpoint should stay in its stalled state, the microcontroller can
re-stall it.
When a stalled endpoint is unstalled (either by the Set Endpoint
Status command or by receiving a SETUP token), it is also
re-initialized. This flushes the buffer and if it is an OUT buffer it waits
for a DATA 0 PID, if it is an IN buffer it writes a DATA 0 PID.
Even when unstalled, writing Set Endpoint Status to ‘0’ initializes the
endpoint.
765432X100
StalledA ‘1’ indicates the endpoint is stalled.
XXXXXX
POWER ON VALUE
STALLED
RESERVED
SV00834
Acknowledge Setup
Command: F1h
Data: None
The arrival of a SETUP packet flushes the IN buffer and disables the
Validate Buffer and Clear Buffer commands for both IN and OUT
endpoints.
The microcontroller needs to re-enable these commands by the
Acknowledge Setup command. This ensures that the last SETUP
packet stays in the buffer and no packet can be sent back to the
host until the microcontroller has acknowledged explicitly that it has
seen the SETUP packet.
The microcontroller must send the Acknowledge Setup command to
both the IN and OUT endpoints.
Hub Commands
Hub commands are used to report connectivity and power status
between the hub and the host. These commands allow the host to
enable each port individually and get any change of status such as
new connectivity information.
Clear/Set Port Feature
Command: E0–E1h (Clear) and E8h–E9h (Set)
Data: Write 1 byte
The data written in the data phase is the feature code described in
Table 4.
When the controller receives a Set Feature or a Clear Feature
request, there are two possibilities:
The request applies to port 1, the embedded port. In this case the
request should be handled internally by the controller.
If the request applies to ports 2 and 3, the controller should translate
the request into a Set Feature or Clear Feature command towards
the PDIUSBH12.
When the PDIUSBH12 is configured in mode 0, there is only one
power switch output and one overcurrent input. This means that the
F_PORT_POWER and C_PORT_OVERCURRENT features are not
port specific. For these features, any of the Set / Clear Feature
commands can be used. The specific port assignment is ignored.
When the PDIUSBH12 is configured in mode 1, there is still only one
power switch output but there are two individual overcurrent input
pins corresponding to each port. This means that the
F_PORT_POWER feature is port specific and the
C_PORT_OVERCURRENT feature is not port specific.
Setting the F_PORT_POWER feature turns the power on when it is
off and turns the overcurrent detection on only when the power is
already on. This allows it to have a short period of overcurrent
condition at the moment that power is switched on. For this reason,
the F_PORT_POWER feature needs to be set twice. Clearing this
feature turns both the power and the overcurrent detection off.
Table 4.
FEATUREFEATURE CODESETCLEAR
F_PORT_ENABLE0Enables a portDisables a port
F_PORT_SUSPEND1Suspends a portResumes a port
FC_PORT_RESET2Resets a portClears a port Reset Change bit
F_PORT_POWER3Powers all portsUnpowers all ports
C_PORT_CONNECTION4–Clears a port Connection Change bit
C_PORT_ENABLE5–Clears a port Enable Change bit
C_PORT_SUSPEND6–Clears a port Suspend Change bit
C_PORT_OVERCURRENT7–Clears a port (Mode 1) or hub (Mode 0) Overcurrent Change bit
1999 Jul 22
15
Page 16
Philips SemiconductorsProduct specification
PDIUSBH12USB 2-port hub
Get Port Status
Command: E0h–E1h
Data: Read 1 or 2 bytes
The Get Port Status Command can be followed by one or two data
reads. The first byte returned contains the port status. The second
byte returned is the port status change byte.
Port Status Byte
7654320100
ConnectA ‘1’ indicates that a device is connected on
EnabledA ‘1’ indicates that this port is enabled.
SuspendA ‘1’ indicates that this port is suspended.
OverCurrentA ‘1’ indicates that overcurrent condition
ResetA ‘1’ indicates that bus reset on this port is in
PowerA ‘1’ indicates that power is supplied to
Low SpeedA ‘1’ indicates that low speed device is
0000X0
POWER ON VALUE
CONNECT
ENABLED
SUSPEND
OVERCURRENT
RESET
POWER
LOW SPEED
RESERVED
SV00846
this port of the hub.
exists on this port. In mode 0 of operation,
this bit is the same for all ports. In mode 1,
individual port overcurrent indication is
possible.
progress. When reset is completed (nominal
duration of 10 ms), this bit indicates a ‘0’.
downstream ports. Since the PDIUSBH12
supports gang mode power switching, this
bit is the same for all ports.
connected to this port. This bit is only valid
when Connect bit is a ‘1’.
Port Status Change Byte
The description for the Port Status Change Byte is similar to the Port
Status Byte except that the value of the bits are ‘1’ only when a
change has occurred.
7654320100
00X0XX
POWER ON VALUE
CONNECT
ENABLED
SUSPEND
OVERCURRENT
RESET
RESERVED
SV00847
Set Status Change Bits
Command: F7h
Data: Write 1 byte
For assembling the hub’s status change register, the device needs
some additional information from the controller, i.e. the Local Power
Status Change bit and the embedded function Status Change bit.
These are provided by the Set Status Change Bits command. This
command is always followed by one data write which contains the
Local Power Status Change bit at the LSB and the embedded
function Status Change bit at position 1. All other bits should be 0.
7654320100
00XXXX
POWER ON VALUE
LOCAL POWER
EMBEDDED FUNCTION 1
EMBEDDED FUNCTION 6
EMBEDDED FUNCTION 7
RESERVED
SV00848
1999 Jul 22
16
Page 17
Philips SemiconductorsProduct specification
PDIUSBH12USB 2-port hub
General Commands
Send Resume
Command: F6h
Data: None
Sends an upstream resume signal for 10 ms. This command is
normally issued when the device is in suspend. The RESUME
command is not followed by a data read or write.
The PDIUSBH12 automatically sends a RESUME command when
an event occurs downstream.
Read Current Frame Number
Command: F5h
Data: Read One or Two Bytes
This command is followed by one or two data reads and returns the
frame number of the last successfully received SOF. The frame
number is returned Least Significant Byte first.
765432X1X0
765432X1X0
XXXXXX
XXXXXX
LEAST SIGNIFICANT BYTE
MOST SIGNIFICANT BYTE
SV00835
Embedded Function
The USB host sees no difference between the embedded function
and a function connected to one of the downstream ports. Some of
the port commands sent by the host must be handled appropriately
by the embedded function to appear as any other downstream port.
The microcontroller maintains a series of status and status change
bits for the embedded function as described in the Get Port Status
command section. From these bits, the Status Change bit for the
embedded function is derived (i.e. the port specific Status Change
bits). This Status Change bit is then provided to the PDIUSBH12 by
the Set Status Change Bits command.
Host Requests
SetFeature PORT_RESET
Reinitialize the embedded function and set the Reset Change bit to
indicate that the reset has completed. Reset the Enable Status bit,
enable the embedded function and set its address to ‘0’ by the Set
embedded function Address / Enable command. Disable the
embedded function interrupt endpoint by the Set Endpoint Enable
command.
SetFeature PORT_ENABLE
Enable the function by the Set embedded function Address/Enable
command. Set the Enable Status bit.
SetFeature PORT_SUSPEND
Disable the function by the Set embedded function Address/Enable
command. Reset the Enable Status bit and set the Suspend Status
bit.
ClearFeature PORT_ENABLE
Disable the function by the Set embedded function Address / Enable
command. Reset the Enable Status bit.
ClearFeature PORT_SUSPEND
Enable the function by the Set embedded function Address / Enable
command. Set the Enable Status bit, reset the Suspend Status bit;
set the Resume Status Change bit to indicate that the resume has
completed.
ClearFeature any Change Indicator
Clear the corresponding status change bit.
Babbling condition
When the embedded function causes a babbling condition, the
function is automatically disabled by the PDIUSBH12. As soon as
the microcontroller detects the babbling error, it must set the Enable
Status Change bit and reset the Enable Status bit.
Remote WakeUp
There are three scenarios when a remote wakeup can occur. The
following describes the course of actions for each of the cases:
1. The device is not suspended and the embedded port is
suspended:
Enable back the function by setting the enable bit in the Set
Address/Enable register and update the following status bits in
the microcontroller program: reset the Suspend Status bit, set
the Enable Status bit and set the Suspend Status Change bit.
2. The device is suspended and the embedded port is suspended:
Send an upstream Resume using the Send Resume command,
enable back the function by setting the enable bit in the Set
Address/Enable register and update the following status bits in
the microcontroller program: reset the Suspend Status bit, set
the Enable Status bit and set the Suspend Status Change bit.
3. The device is suspended and the embedded port is enabled:
Send an upstream resume using the Send Resume command.
1999 Jul 22
17
Page 18
Philips SemiconductorsProduct specification
PDIUSBH12USB 2-port hub
RECOMMENDED OPERATING CONDITIONS
SYMBOLPARAMETERTEST CONDITIONSMINMAXUNIT
V
T
V
V
V
CC
V
AI/O
amb
DC supply voltage3.03.6V
DC input voltage range05.5V
I
DC input voltage range for I/O05.5V
I/O
DC input voltage range for analog I/O0V
DC output voltage range0V
O
Operating ambient temperature range in free airSee DC and AC characteristics per device–4085°C
CC
CC
V
V
ABSOLUTE MAXIMUM RATINGS
SYMBOL
I
GND
V
CC
I
IK
V
I
V
I/O
I
OK
V
O
I
O
I
O
, I
V
ESD
T
STG
P
TOT
DC supply voltage–0.5+4.6V
DC input diode currentVI < 0–50mA
DC input voltageNote 2–0.5+5.5V
DC input voltage range for I/O’s–0.5VCC + 0.5V
DC output diode currentVO > VCC or VO < 0±50mA
DC output voltageNote 2–0.5VCC + 0.5V
DC output sink or source current for other pinsVO = 0 to V
DC output sink or source current for D+/D– pinsVO = 0 to V
DC VCC or GND current±100mA
CC
Electrostatic discharge voltageIIL < 1 µA
Storage temperature range–60+150°C
Power dissipation per package
1
PARAMETERTEST CONDITIONSMINMAXUNIT
CC
CC
3
—±4000
±15mA
±50mA
4
V
NOTES:
1. Stresses beyond those listed may cause damage to the device. These are stress ratings only and functional operation of the device at these
or any other conditions beyond those listed in the RECOMMENDED OPERATING CONDITIONS table is not implied. Exposure to absolute
maximum rated conditions for extended periods may affect device reliability .
2. The input and output voltage ratings may be exceeded if the input and output current ratings are observed.
3. Values are given for device only: in-circuit V
4. For open-drain pins V
ESD(MAX)
= ±2000 V .
ESD(MAX)
= ±8000 V .
1999 Jul 22
18
Page 19
Philips SemiconductorsProduct specification
VOLLOW level out ut voltage
VOHHIGH level out ut voltage
PDIUSBH12USB 2-port hub
DC CHARACTERISTICS (Digital pins)
SYMBOLPARAMETERTEST CONDITIONSMINTYPMAXUNIT
Input Levels
V
VIH
V
TLH
V
THL
V
HYS
Output Levels
Leakage Current
I
OZ
I
I
I
LOW level input voltage0.6V
IL
HIGH level input voltage2.7V
LOW to HIGH threshold voltageST (Schmitt Trigger) pins1.41.9V
HIGH to LOW threshold voltageST pins0.91.5V
Hysteresis voltageST pins0.40.7V
p
p
IOL = rated drive0.4
IOL = 20 µA0.1V
IOH = rated drive2.4
IOH = 20 µAVCC – 0.1V
OFF state currentOD (Open Drain) pins±1µA
Input leakage current±1µA
L
Suspend current
S
Operating current02 ports operating13mA
O
Oscillator stopped and
inputs to GND/V
CC
V
V
15µA
DC CHARACTERISTICS (AI/O pins)
SYMBOLPARAMETERTEST CONDITIONSMINMAXUNIT
Leakage Current
I
LO
Hi-Z state data line leakage0V < VIN < 3.3V±10µA
Input Levels
V
V
CM
V
Differential input sensitivity|(D+) – (D–)|
DI
Differential common mode rangeIncludes VDI range0.82.5V
Single-ended receiver threshold0.82.0V
Figure 1. Differential data to EOP transition skew and EOP width
EOPT
EOPR1
, t
EOPR2
SV00837
1999 Jul 22
21
Page 22
Philips SemiconductorsProduct specification
PDIUSBH12USB 2-port hub
V
DD
UPSTREAMDIFFERENTIAL
DATA
V
SS
DOWNSTREAMDIFFERENTIAL
DATA
V
SS
A. DOWNSTREAM HUB DELAYB. UPSTREAM HUB DELAY
SOP DISTORTION
= t
t
SOP
HDD
LOW SPEED TIMINGS ARE DETERMINED IN THE SAME WAY FOR:
t
AND t
LHDD
(SOP) – t
LSOP
CROSSOVER
POINT
Hub Delay
Downstream
t
(NEXT J)
HDD
HDD
CROSSOVER
POINT
DOWNSTREAM
DIFFERENTIAL
DATA
UPSTREAM
DIFFERENTIAL
DATA
Figure 2. Hub Differential Data Delay and SOP distortion
CROSSOVER
POINT
Hub Delay
Upstream
t
HDD
CROSSOVER
POINT
SV00514
V
DD
UPSTREAMDIFFERENTIAL
DATA
V
SS
DOWNSTREAMDIFFERENTIAL
DATA
V
SS
DOWNSTREAM
PORT
UPSTREAM
END OF CABLE
t
EOP–
t
EOP–
t
EOP+
CROSSOVER
POINT
EXTENDED
CROSSOVER
POINT
EXTENDED
A. DOWNSTREAM EOP DELAYB. UPSTREAM EOP DELAY
EOP DELAY
= t
t
EOPD
EOP–
EOP DELAY RELATIVE TO t
t
= t
= t
, t
EOPD
EOP+
LEOPDR
– t
–t
EOP–
, AND t
EOPDR
EOP SKEW
t
HESK
LOW SPEED TIMINGS ARE DETERMINED IN THE SAME WAY FOR:
t
LEOPD
HDD
HDD
LHESK
Figure 3. Hub EOP Delay and EOP Skew
t
EOP+
CROSSOVER
POINT
EXTENDED
CROSSOVER
POINT
EXTENDED
SV00515
1999 Jul 22
22
Page 23
Philips SemiconductorsProduct specification
PDIUSBH12USB 2-port hub
AC CHARACTERISTICS (I2C pins)
All timing values are valid within the operating supply voltage and ambient temperature range and reference to VIL and VIH with an input voltage
swing of V
SYMBOL
t
t
t
t
t
t
SU;STO
A detailed description of the I2C-bus specification, with applications, is given in the brochure “
be ordered using the Philips order number 9398 393 40011.
f
SCL
t
BUF
SU;STA
HD;STA
t
LOW
t
HIGH
t
r
t
f
SU;DAT
HD;DAT
VD;DAT
and VDD.
SS
PARAMETERTEST CONDITIONSMINMAXUNIT
SCL clock frequency1000kHz
Bus free time0.5µs
Start condition set-up time0.25µs
Start condition hold time0.25µs
SCL LOW time0.45µs
SCL HIGH time0.45µs
SCL and SDA rise time0.3µs
SCL and SDA fall time0.1µs
Data set-up time100ns
Data hold time0ns
SCLLOW to data out valid0.4µs
Stop condition set-up time0.25µs
The I2C-bus and how to use it
”. This brochure may
PROTOCOL
SCL
SDA
START
CONDITION
(S)
t
SU;STA
t
BUF
t
HD;STA
t
LOW
BIT 7
MSB
(A7)
t
HIGH
t
r
t
f
t
SU;DAT
1/f
BIT 6
(A6)
SCL
t
HD;DAT
BIT 0
LSB
(R/W)
ACKNOWLEDGE
(A)
t
VD:DAT
STOP
CONDITION
(P)
t
SU;STO
SV00756
Figure 4. I2C-bus timing diagram
1999 Jul 22
23
Page 24
Philips SemiconductorsProduct specification
PDIUSBH12USB 2-port hub
SO28: plastic small outline package; 28 leads; body width 7.5mmSOT136-1
This text gives a very brief insight to a complex technology. A more
in-depth account of soldering ICs can be found in our
Handbook IC26; Integrated Circuit Packages”
number 9398 652 90011).
There is no soldering method that is ideal for all IC packages. Wave
soldering is often preferred when through-hole and surface mount
components are mixed on one printed circuit board. However, wave
soldering is not always suitable for surface mount ICs, or for
printed-circuit boards with high population densities. In these
situations, reflow soldering is often used.
“Data
(document order
Through-hole mount packages
OLDERINGBYDIPPINGORBYSOLDERWAVE
S
The maximum permissible temperature of the solder is 260°C;
solder at this temperature must not be in contact with the joints for
more than 5 seconds. The total contact time of successive solder
waves must not exceed 5 seconds.
The device may be mounted up to the seating plane, but the
temperature of the plastic body must not exceed the specified
maximum storage temperature (T
has been pre-heated, forced cooling may be necessary immediately
after soldering to keep the temperature within the permissible limit.
). If the printed-circuit board
stg(max)
MANUALSOLDERING
Apply the soldering iron (24 V or less) to the lead(s) of the package,
either below the seating plane or not more than 2 mm above it. If the
temperature of the soldering iron bit is less than 300°C, it may
remain in contact for up to 10 seconds. If the bit temperature is
between 300 and 400°C, contact may be made for up to 5 seconds.
Surface mount packages
R
EFLOWSOLDERING
Reflow soldering requires solder paste (a suspension of fine solder
particles, flux and binding agent) to be applied to the printed-circuit
board by screen printing, stencilling or pressure-syringe dispensing
before package placement.
Several methods exist for reflowing; for example, infrared/convection
heating in a conveyor-type oven. Throughput times (preheating,
soldering and cooling) vary between 100 and 200 seconds,
depending on heating method.
Typical reflow peak temperatures range from 215 250°C. The
top-surface temperature of the packages should preferably be kept
below 230°C.
WAVESOLDERING
Conventional single-wave soldering is not recommended for surface
mount devices (SMDs) or printed-circuit boards with a high
component density , as solder bridging and non-wetting can present
major problems.
To overcome these problems, the double-wave soldering method
was specifically developed.
If wave soldering is used, the following conditions must be observed
for optimal results:
•Use a double-wave soldering method comprising a turbulent wave
with high upward pressure followed by a smooth laminar wave.
•For packages with leads on two sides and a pitch (e):
– larger than or equal to 1.27 mm, the footprint longitudinal axis
is preferred to be parallel to the transport direction of the
printed-circuit board;
– smaller than 1.27 mm, the footprint longitudinal axis must be
parallel to the transport direction of the printed-circuit board.
The footprint must incorporate solder thieves at the downstream
end.
•For packages with leads on four sides, the footprint must be
placed at a 45° angle to the transport direction of the
printed-circuit board. The footprint must incorporate solder thieves
downstream and at the side corners.
During placement, and before soldering, the package must be fixed
with a droplet of adhesive. The adhesive can be applied by screen
printing, pin transfer or syringe dispensing. The package can be
soldered after the adhesive has cured.
Typical dwell time is 4 seconds at 250°C. A mildly-activated flux will
eliminate the need for removal of corrosive residues in most
applications.
MANUALSOLDERING
Fix the component by first soldering two diagonally-opposite end
leads. Use a low-voltage (24 V or less) soldering iron applied to the
flat part of the lead. Contact time must be limited to 10 seconds at
up to 300°C.
When using a dedicated tool, all other leads can be soldered in one
operation within 2 to 5 seconds between 270 and 320°C.
1999 Jul 22
26
Page 27
Philips SemiconductorsProduct specification
Mounting
Package
PDIUSBH12USB 2-port hub
SUITABILITY OF IC PACKAGES FOR W AVE, REFLOW AND DIPPING SOLDERING METHODS
1. All surface mount (SMD) packages are moisture sensitive. Depending upon the moisture content, the maximum temperature (with respect to
time) and body size of the package, there is a risk that internal or external package cracks may occur due to vaporization of the moisture in
them (the so-called “popcorn” effect). For details, refer to the Drypack information in the
2
3
4, 5
6
“Data Handbook IC26; Integrated Circuit Packages;
Section: Packing Methods”.
2. For SDIP packages, the longitudinal axis must be parallel to the transport direction of the printed-circuit board.
3. These packages are not suitable for wave soldering as a solder joint between the printed-circuit board and heatsink (at bottom version)
cannot be achieved, and as solder may stick to the heatsink (on top version).
4. If wave soldering is considered, then the package must be placed at a 45° angle to the solder wave direction. The package footprint must
incorporate solder thieves downstream and at the side corners.
5. Wave soldering is only suitable for LQFP, QFP, and TQFP packages with a pitch (e) equal to or larger than 0.8 mm; it is definitely not
suitable for packages with a pitch (e) equal to or smaller than 0.65 mm.
6. Wave soldering is only suitable for SSOP and TSSOP packages with a pith (e) equal to or larger than 0.65 mm; it is definitely not suitable for
packages with a pitch (e) equal to or smaller than 0.5 mm.
1
–suitable
suitable–
suitable–
suitable–
Dipping
1999 Jul 22
27
Page 28
Philips SemiconductorsProduct specification
PDIUSBH12USB 2-port hub
Data sheet status
Data sheet
status
Objective
specification
Preliminary
specification
Product
specification
Product
status
Development
Qualification
Production
Definition
This data sheet contains the design target or goal specifications for product development.
Specification may change in any manner without notice.
This data sheet contains preliminary data, and supplementary data will be published at a later date.
Philips Semiconductors reserves the right to make changes at any time without notice in order to
improve design and supply the best possible product.
This data sheet contains final specifications. Philips Semiconductors reserves the right to make
changes at any time without notice in order to improve design and supply the best possible product.
[1]
[1] Please consult the most recently issued datasheet before initiating or completing a design.
Definitions
Short-form specification — The data in a short-form specification is extracted from a full data sheet with the same type number and title. For
detailed information see the relevant data sheet or data handbook.
Limiting values definition — Limiting values given are in accordance with the Absolute Maximum Rating System (IEC 134). Stress above one
or more of the limiting values may cause permanent damage to the device. These are stress ratings only and operation of the device at these or
at any other conditions above those given in the Characteristics sections of the specification is not implied. Exposure to limiting values for extended
periods may affect device reliability.
Application information — Applications that are described herein for any of these products are for illustrative purposes only. Philips
Semiconductors make no representation or warranty that such applications will be suitable for the specified use without further testing or
modification.
Disclaimers
Life support — These products are not designed for use in life support appliances, devices or systems where malfunction of these products can
reasonably be expected to result in personal injury . Philips Semiconductors customers using or selling these products for use in such applications
do so at their own risk and agree to fully indemnify Philips Semiconductors for any damages resulting from such application.
Right to make changes — Philips Semiconductors reserves the right to make changes, without notice, in the products, including circuits, standard
cells, and/or software, described or contained herein in order to improve design and/or performance. Philips Semiconductors assumes no
responsibility or liability for the use of any of these products, conveys no license or title under any patent, copyright, or mask work right to these
products, and makes no representations or warranties that these products are free from patent, copyright, or mask work right infringement, unless
otherwise specified.
Philips Semiconductors
811 East Arques Avenue
P.O. Box 3409
Sunnyvale, California 94088–3409
Telephone 800-234-7381
Copyright Philips Electronics North America Corporation 1999
All rights reserved. Printed in U.S.A.
Date of release: 07-99
Document order number:9397 750 06221
1999 Jul 22
28
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.