Universal Serial Bus single-chip host and device controller
Rev. 03 — 23 December 2004Product data
1.General description
The ISP1161A1 is a single-chip Universal Serial Bus (USB) Host Controller (HC) and
Device Controller (DC). The Host Controller portion of the ISP1161A1 complies with
Universal Serial Bus Specification Rev. 2.0,
(12 Mbit/s) and low-speed (1.5 Mbit/s). The Device Controller portion of the
ISP1161A1 also complies with
supporting data transfer at full-speed (12 Mbit/s). These two USB controllers, the HC
and the DC, share the same microprocessor bus interface. They have the same data
bus, butdifferent I/O locations. They also have separate interrupt request output pins,
separate DMA channels that include separate DMA request output pins and DMA
acknowledge input pins. This makes it possible for a microprocessor to control both
the USB HC and the USB DC at the same time.
The ISP1161A1 provides two downstream ports for the USB HC and one upstream
port for the USB DC. Each downstream port has an overcurrent (OC) detection input
pin and power supply switching control output pin. The upstream port has a V
detection input pin.The ISP1161A1 also provides separate wake-up input pins and
suspended status output pins for the USB HC and the USB DC, respectively. This
makes power management flexible. The downstream ports for the HC can be
connected with any USB compliant devices and hubs that have USB upstream ports.
The upstream port for the DC can be connected to any USB compliant USB host and
USB hubs that have USB downstream ports.
supporting data transfer at full-speed
Universal Serial Bus Specification Rev. 2.0,
BUS
The HC is adapted from the
Release 1.0a
The DC is compliant with most USB device class specifications such as Imaging
Class, Mass Storage Devices, Communication Devices, Printing Devices and Human
Interface Devices.
The ISP1161A1 is well suited for embedded systems and portable devices that
require a USB host only, a USB device only, or a combination of a configurable USB
host and USB device. The ISP1161A1 brings high flexibility to the systems that have
it built-in. For example, a system that uses an ISP1161A1 allows it not only to be
connected to a PC or USB hub with a USB downstream port, but also to be
connected to a device that has a USB upstream port such as a USB printer, USB
camera, USB keyboard or a USB mouse. Therefore, the ISP1161A1 enables
point-to-point connectivity between embedded systems. An interesting application
example is to connect an ISP1161A1 HC with an ISP1161A1 DC.
Consider an example of an ISP1161A1 being used in a Digital Still Camera (DSC)
design. Figure 1 shows an ISP1161A1 being used as a USB DC. Figure 2 shows an
ISP1161A1 being used as a USB HC.Figure 3 shows an ISP1161A1 being used as a
USB HC and a USB DC at the same time.
, referred to as OHCI in the rest of this document.
Open Host Controller Interface Specification for USB
Philips Semiconductors
ISP1161A1
USB single-chip host and device controller
EMBEDDED SYSTEM
PC
(host)
USB cable
USB I/F
Fig 1. ISP1161A1 operating as a USB device.
EMBEDDED SYSTEM
µP
ISP1161A1
DSC
µP SYSTEM
µP bus I/F
HOST/
DEVICE
USB host
MEMORY
USB I/F
USB I/F
µP
ISP1161A1
USB device
USB cable
µP SYSTEM
MEMORY
µP bus I/F
HOST/
DEVICE
DSC
004aaa173
PRINTER
(device)
USB I/F
004aaa174
Fig 2. ISP1161A1 operating as a stand-alone USB host.
EMBEDDED SYSTEM
HOST/
DEVICE
µP SYSTEM
MEMORY
µP bus I/F
USB host
PRINTER
(device)
USB I/FUSB I/F
USB I/F
004aaa175
PC
(host)
µP
DSC
USB cableUSB cable
USB I/F
ISP1161A1
USB device
Fig 3. ISP1161A1 operating as both USB host and device simultaneously.
DGND45-digital ground
H_PSW146Opower switching control output for downstream port 1;
open-drain output
H_PSW247Opower switching control output for downstream port 2;
open-drain output
D_DM48AI/OUSB D− data line for DC upstream port; when not in use,
this pin must be left open
D_DP49AI/OUSB D+ data line for DC upstream port; when not in use,
this pin must be left open
H_DM150AI/OUSB D− data line for HC downstream port 1
H_DP151AI/OUSB D+ data line for HC downstream port 1
H_DM252AI/OUSB D− data line for HC downstream port 2; when not in
use, this pin must be left open
H_DP253AI/OUSB D+ data line for HC downstream port 2; when not in
use, this pin must be left open
H_OC154Iovercurrent sensing input for HC downstream port 1
H_OC255Iovercurrent sensing input for HC downstream port 2
V
CC
56-power supply voltage input (3.0 V to 3.6 V or
4.75 V to 5.25 V). This pin supplies the internal 3.3 V
regulator input. When connected to 5 V, the internal
regulator will output 3.3 V to pins V
reg(3.3),Vhold1
and V
hold2
When connected to 3.3 V, it will bypass the internal
regulator.
AGND57-analog ground
V
reg(3.3)
58-internal 3.3 V regulator output; when pin VCC is connected
to 5 V, this pin outputs 3.3 V. When pin V
is connected to
CC
3.3 V, connect this pin to 3.3 V.
A059Iaddress input; selects command (A0 = 1) or data (A0 = 0)
A160Iaddressinput;selects AutoMux switching to DC (A1 = 1) or
AutoMux switching to HC (A1 = 0); see Table 3
n.c.61-no connection
DGND62-digital ground
D063I/Obit 0 of bidirectional data; slew-rate controlled; TTL input;
A 6 MHz to 48 MHz clock multiplier Phase-Locked Loop (PLL) is integrated on-chip.
This allows for the use of a low-cost 6 MHz crystal, which also minimizes EMI. No
external components are required for the operation of the PLL.
7.2 Bit clock recovery
The bit clock recovery circuit recovers the clock from the incoming USB data stream
using a 4 times over-sampling principle. It is able to track jitter and frequency drift as
specified in the
7.3 Analog transceivers
Three sets of transceivers are embedded in the chip: two are used for downstream
ports with USB connector type A; one is used for upstream port with USB connector
type B. The integrated transceivers are compliant with the
Specification Rev. 2.0
through external termination resistors.
ISP1161A1
USB single-chip host and device controller
Universal Serial Bus Specification Rev. 2.0
. They interface directly with the USB connectors and cables
.
Universal Serial Bus
7.4 Philips Serial Interface Engine (SIE)
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 (de)stuffing, CRC
checking/generation, Packet IDentifier (PID) verification/generation, address
recognition, handshake evaluation/generation. There are separate SIEs in the HC
and the DC.
7.5 SoftConnect
The connection to the USB is accomplished by bringing D+ (for full-speed USB
devices) HIGH through a 1.5 kΩ pull-up resistor. In the ISP1161A1 DC, the 1.5 kΩ
pull-up resistor is integrated on-chip and is not connected to VCC by default. The
connection 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 with the USB. Re-initialization of
the USB connection can also be performed without disconnecting the cable.
The ISP1161A1 DC will check for USB V
established. V
Remark: The tolerance of the internal resistors is 25 %. This is higher than the 5 %
tolerance specified by the USB specification. However, the overall voltage
specification for the connection can still be met with a good margin. The decision to
make use of this feature lies with the USB equipment designer.
Indication of a good USB connection is provided at pin GL through GoodLink
technology. During enumeration, the LED indicator will blink on momentarily. When
the DC has been successfully enumerated (the device address is set), the LED
indicator will remain permanently on. Upon each successful packet transfer (with
ACK) to and from the ISP1161A1 the LED will blink off for 100 ms. During ‘suspend’
state the LED will remain off.
This feature provides a user-friendly indication of the status of the USB device, the
connected hub and the USB traffic. It is a useful field diagnostics tool for isolating
faulty equipment. It can therefore help to reduce field support and hotline overhead.
8.Microprocessor bus interface
8.1 Programmed I/O (PIO) addressing mode
A generic PIO interface is defined for speed and ease-of-use. It also allows direct
interfacing to most microcontrollers. To a microcontroller, the ISP1161A1 appears as
a memory device with a 16-bit data bus and uses only two address lines: A1 and A0
to access the internal control registers and FIFO buffer RAM. Therefore, the
ISP1161A1 occupies only four I/O ports or four memory locations of a
microprocessor. External microprocessors can read from or write to the ISP1161A1
internal control registers and FIFO buffer RAM through the Programmed I/O (PIO)
operating mode. Figure 8 shows the Programmed I/O interface between a
microprocessor and an ISP1161A1.
ISP1161A1
USB single-chip host and device controller
MICRO-
PROCESSOR
D[15:0
WR
IRQ1
IRQ2
µP bus I/F
]
RD
CS
A2
A1
D[15:0
RD
WR
CS
A1
A0
INT1
INT2
]
ISP1161A1
004aaa178
Fig 8. Programmed I/O interface between a microprocessor and an ISP1161A1.
8.2 DMA mode
The ISP1161A1 also provides DMA mode for external microprocessors to access its
internal FIFO buffer RAM. Data can be transferred by DMA operation between a
microprocessor’s system memory and the ISP1161A1 internal FIFO buffer RAM.
Remark: The DMA operation must be controlled by the external microprocessor
system DMA controller (Master).
Figure 9 shows the DMA interface between a microprocessor system and the
ISP1161A1. The ISP1161A1 provides two DMA channels:
• DMA channel 1 (controlled by DREQ1, DACK1 signals) is for the DMA transfer
• DMA channel 2 (controlled by DREQ2, DACK2 signals) is for the DMA transfer
The EOT signal is an external end-of-transfer signal used to terminate the DMA
transfer. Some microprocessors may not have this signal. In this case, the
ISP1161A1 provides an internal EOT signal to terminate the DMA transfer as well.
Setting the HcDMAConfiguration register (21H to read, A1H to write) enables the
ISP1161A1 HC internal DMA counter for DMA transfer. When the DMA counter
reaches the value set in the HcTransferCounter register (22H to read, A2H to write),
an internal EOT signal will be generated to terminate the DMA transfer.
ISP1161A1
USB single-chip host and device controller
between a microprocessor’s system memory and the ISP1161A1 HC internal
FIFO buffer RAM.
between a microprocessor system memory and the ISP1161A1 DC internal FIFO
buffer RAM.
µP bus I/F
]
D[15:0
RD
WR
MICRO-
PROCESSOR
DACK1
DREQ1
DACK2
DREQ2
EOT
Fig 9. DMA interface between a microprocessor and an ISP1161A1.
8.3 Control register access by PIO mode
8.3.1 I/O port addressing
Table 3 shows the ISP1161A1 I/O port addressing. Complete decoding of the I/O port
address should include the chip select signal CS and the address lines A1 and A0.
However, the direction of the access of the I/O ports is controlled by the RD and WR
signals. When RD is LOW, the microprocessor reads data from the ISP1161A1 data
port. When WR is LOW, the microprocessor writes a command to the command port,
or writes data to the data port.
D[15:0
RD
WR
DACK1
DREQ1
DACK2
DREQ2
EOT
]
ISP1161A1
004aaa179
Table 3:I/O port addressing
PortCSA1,A0
(Bin)
AccessData bus width
(bits)
Description
0000R/W16HC data port
1001W16HC command port
2010R/W16DC data port
3011W16DC command port
Figure 10 and Figure 11 illustrate how an external microprocessor accesses the
ISP1161A1 internal control registers.
Fig 10. Microprocessor access to a HC or a DC via an automux switch.
USB single-chip host and device controller
AUTOMUX
DC/HC
0
µP bus I/F
1
A1
When A1 = 0, the microprocessor accesses the HC.
When A1 = 1, the microprocessor accesses the DC.
CMD/DATA
SWITCH
command port
Host or Device
bus I/F
A0
1
data port
0
Host bus I/F
Device bus I/F
MGT935
.
.
.
ISP1161A1
Commands
Command register
When A0 = 0, the microprocessor accesses the data port.
When A0 = 1, the microprocessor accesses the command port.
Fig 11. Microprocessor access to internal control registers.
8.3.2 Register access phases
The ISP1161A1 register structure is a command-data register pair structure. A
complete register access cycle comprises a command phase followed by a data
phase. The command (also known as the index of a register) points the ISP1161A1 to
the next register to be accessed. A command is 8 bits long. On a microprocessor’s
16-bit data bus, a command occupies the lower byte, with the upper byte filled with
zeros.
Figure 12 shows a complete 16-bit register access cycle for the ISP1161A1. The
microprocessor writes a command code to the command port, and then reads or
writes the data word from or to the data port. Take the example of a microprocessor
attempting to read the ISP1161A1’s ID, which is saved in the HC’s HcChipID register
(index 27H, read only). The 16-bit register access cycle is therefore:
1. Microprocessor writes the command code of 27H (0027H in 16-bit width) to
the HC command port
2. Microprocessor reads the data word of the chip’s ID (6110H for engineering
sample; version one) from the HC data port.
Most of the ISP1161A1 internal control registers are 16-bit wide. Some of the internal
control registers, however, have 32-bit width. Figure 13 shows how the 32-bit internal
control register is accessed. The complete cycle of accessing a 32-bit register
consists of a command phase followed by two data phases. In the two data phases,
the microprocessor first reads or writes the lower 16-bit data, followed by the upper
16-bit data.
32-bit register access cycle
write command
(16 bits)
read/write data
(lower 16 bits)
read/write data
(upper 16 bits)
t
MGT938
Fig 13. 32-bit register access cycle.
To further describe the complete access cycles of the internal control registers, the
status of some pins of the microprocessor bus interface are shown in Figure 14 and
Since the ISP1161A1 internal memory is structured as a FIFO buffer RAM, the FIFO
buffer RAM is mapped to dedicated register fields. Therefore, accessing the internal
FIFO buffer RAM is similar to accessing the internal control registers in multiple data
phases.
Figure 16 shows a complete access cycle of the HC internal FIFO buffer RAM. For a
write cycle, the microprocessor first writes the FIFO buffer RAM’s command code to
the command port, and then writes the data words one by one to the data port until
half of the transfer’s byte count is reached. The HcTransferCounter register (22H to
read, A2H to write) is used to specify the byte count of a FIFO buffer RAM’s read
cycle or write cycle. Every access cycle must be in the same access direction. The
read cycle procedure is similar to the write cycle.
For access to the DC FIFO buffer RAM, see Section 13.
The DMA interface between a microprocessor and the ISP1161A1 is shown in
Figure 9.
When doing a DMA transfer, at the beginning of every burst the ISP1161A1 outputs a
DMA request to the microprocessor via the DREQ pin (DREQ1 for HC, DREQ2
for DC). After receiving this signal, the microprocessor will reply with a DMA
acknowledge via the DACK pin (DACK1 for HC, DACK2 for DC), and at the same
time, execute the DMA transfer through the data bus. In the DMA mode, the
microprocessor must issue a read or write signal to the ISP1161A1 RD or WR pin.
The ISP1161A1 will repeat the DMA cycles until it receives an EOT signal to
terminate the DMA transfer.
The ISP1161A1 supports both external and internal EOT signals. The external EOT
signal is received as input on pin EOT, and generally comes from the external
microprocessor. The internal EOT signal is generated by the ISP1161A1 internally.
To select either EOT method, set the appropriate DMA configuration register (see
Section 10.4.2 and Section 13.1.6). For example, for the HC, setting
DMACounterSelect of the HcDMAConfiguration register (21H to read, A1H to write)
to logic 1 will enable the DMA counter for DMA transfer. When the DMA counter
reaches the value of the HcTransferCounter register, the internal EOT signal will be
generated to terminate the DMA transfer.
ISP1161A1
USB single-chip host and device controller
The ISP1161A1 supports either single-cycle DMA operation or burst mode DMA
operation; see Figure 17 and Figure 18.
To program the four configuration modes of the HC’s interrupt output signal (INT1),
set bits InterruptPinTrigger and InterruptOutputPolarity of the
HcHardwareConfiguration register (20H to read, A0H to write). Bit InterruptPinEnable
is used as the master enable setting for pin INT1.
INT active
INT active
INT active
166 ns
INT active
166 ns
clear or disable INT
clear or disable INT
MGT944
INT1 has many associated interrupt events, as shown as in Figure 20.
The interrupt events of the HcµPInterrupt register (24H to read, A4H to write)
changes the status of pin INT1 when the corresponding bits of the
HcµPInterruptEnable register (25H to read, A5H to write) and pin INT1’s global
enable bit (InterruptPinEnable of the HcHardwareConfiguration register) are all set to
enable status.
However, events that come from the HcInterruptStatus register (03H to read, 83H to
write) affect only bit OPR_Reg of the HcµPInterrupt register. They cannot directly
change the status of pin INT1.
There are two groups of interrupts represented by group 1 and group 2 in Figure 20.
A pair of registers control each group.
Group 2 contains six possible interrupt events (recorded in the HcInterruptStatus
register). On occurrence of any of these events,the corresponding bit would be set to
logic 1; and if the corresponding bit in the HcInterruptEnable register is also logic 1,
the 6-input OR gate would output a logic 1. This output is AND-ed with the value of
MIE (bit 31 of HcInterruptEnable). Logic 1 at the AND gate will cause bit OPR in the
HcµPInterrupt register to be set to logic 1.
Group 1 contains six possible interrupt events, one of which is the output of group 2
interrupt sources. The HcµPInterrupt and HcµPInterruptEnable registers work in the
same way as the HcInterruptStatus and HcInterruptEnable registers in the interrupt
group 2. The output from the 6-input OR gate is connected to a latch, which is
controlled by InterruptPinEnable (bit 0 of the HcHardwareConfiguration register).
In the event in which the software wishes to temporarily disable the interrupt output of
the ISP1161A1 Host Controller, the following procedure should be followed:
1. Make sure that bit InterruptPinEnable in the HcHardwareConfiguration register is
set to logic 1.
Remark: Bit InterruptPinEnable in the HcHardwareConfiguration register latches the
interrupt output. When this bit is set to logic 0, the interrupt output will remain
unchanged, regardless of any operations on the interrupt control registers.
If INT1 is asserted, and the HCD wishes to temporarily mask off the INT signal
without clearing the HcµPInterrupt register, the following procedure should be
followed:
1. Make sure that bit InterruptPinEnable is set to logic 1.
2. Clear all bits in the HcµPInterruptEnable register.
3. Set bit InterruptPinEnable to logic 0.
To re-enable the interrupt generation:
1. Set all bits in the HcµPInterruptEnable register according to the HCD
2. Set bit InterruptPinEnable to logic 1.
ISP1161A1
USB single-chip host and device controller
requirements.
8.6.3 DC interrupt output pin (INT2)
The four configuration modes of DC’s interrupt output pin INT2 can also be
programmed by setting bits INTPOL and INTLVL of the DcHardwareConfiguration
register (BBH to read, BAH to write). Bit INTENA of the DcMode register (B9H to
read, B8H to write) is used to enable pin INT2. Figure 21 shows the relationship
between the interrupt events and pin INT2.
Each of the indicated USB events is logged in a status bit of the DcInterrupt register.
Corresponding bits in the DcInterruptEnable register determine whether or not an
event will generate an interrupt.
Interrupts can be masked globally by means of bit INTENA of the DcMode register
(see Table 81).
The active level and signalling mode of the INT output is controlled by bits INTPOL
and INTLVL of the DcHardwareConfiguration register (see Table 83). Default settings
after reset are active LOW and level mode. When pulse mode is selected, a pulse of
166 ns is generated when the OR-ed combination of all interrupt bits changes from
logic 0 to logic 1.
Bits RESET, RESUME, SP_EOT, EOT and SOF are cleared upon reading the
DcInterrupt register. The endpoint bits (EP0OUT to EP14) are cleared by reading the
associated DcEndpointStatus register.
Bit BUSTATUS follows the USB bus status exactly, allowing the firmware to get the
current bus status when reading the DcInterrupt register.
SETUP and OUT token interrupts are generated after the DC has acknowledged the
associated data packet. In bulk transfer mode, the DC will issue interrupts for every
ACK received for an OUT token or transmitted for an IN token.
In isochronous mode, an interrupt is issued upon each packet transaction. The
firmware must take care of timing synchronization with the host. This can be done via
the Pseudo Start-Of-Frame (PSOF) interrupt, enabled via bit IEPSOF in the
DcInterruptEnable register. If a Start-Of-Frameis lost, PSOF interrupts are generated
every1 ms. This allows the firmware to keep data transfer synchronized with the host.
After 3 missed SOF events, the DC will enter ‘suspend’ state.
An alternative way of handling isochronous data transfer is to enable both the SOF
and the PSOF interrupts and disable the interrupt for each isochronous endpoint.
DcInterrupt register
RESET
SUSPND
RESUME
SOF
EP14
...
EP0IN
EP0OUT
EOT
IERST
IESUSP
IERESM
IESOF
IEP14
...
IEP0IN
IEP0OUT
IEEOT
DcInterruptEnable register
.
.
.
.
.
.
MGT946
ISP1161A1
USB single-chip host and device controller
.
.
.
.
.
.
DcMode register
INTENA
LATCH
LE
INT2
Fig 21. DC interrupt logic.
Interrupt control: Bit INTENA in the DcMode register is a global enable/disable bit.
The behavior of this bit is given in Figure 22.
A
INT2 pin
INTENA = 0
(during this time,
an interrupt event
occurs. For example,
SOF asserted.)
Pin INT2: HIGH = de-assert; LOW = assert (individual interrupts are enabled).
Event A (see Figure 22): When an interrupt event occurs (for example, SOF interrupt)
with bit INTENA set to logic 0, an interrupt will not be generated at pin INT2.
However, it will be registered in the corresponding DcInterrupt register bit.
Event B (see Figure 22): When bit INTENA is set to logic 1, pin INT2 is asserted
because bit SOF in the DcInterrupt register is already asserted.
Event C (see Figure 22): If the firmware sets bit INTENA to logic 0, pin INT2 will still
be asserted. The bold dashed line shows the desired behavior of pin INT2.
De-assertion of pin INT2 can be achieved in the following manner. Bits[23:8] of the
DcInterrupt register are endpoint interrupts. These interrupts are cleared on reading
their respective DcEndpointStatus register. Bits[7:0] of the DcInterrupt register are
bus status and EOT interrupts that are cleared on reading the DcInterrupt register.
Make sure that bit INTENA is set to logic 1 when you perform the clear interrupt
commands.
For more information on interrupt control, see Section 13.1.3, Section 13.1.5 and
The ISP1161A1 USB HC has four USB states − USBOperational, USBReset,
USBSuspend, and USBResume − that define the HC’s USB signaling and bus states
responsibilities.
ISP1161A1
USB single-chip host and device controller
USBOperational
USBOperational write
USBSuspend write
Fig 23. ISP1161A1 HC USB states.
The USB states are reflected in the HostControllerFunctionalState field of the
HcControl register (01H to read, 81H to write), which is located at bits 7 and 6 of the
register.
USBSuspend
USBOperational write
USBResume
USBResume write
or
remote wake-up
USBReset write
USBReset write
USBReset
hardware or software
reset
USBReset write
MGT947
The Host Controller Driver (HCD) can perform only the USB state transitions shown
in Figure 23.
Remark: The Software Reset in Figure 23 is not caused by the HcSoftwareReset
command. It is caused by the HostControllerReset field of the HcCommandStatus
register (02H to read, 82H to write).
9.2 Generating USB traffic
USB traffic can be generated only when the ISP1161A1 USB HC is in the
USBOperational state. Therefore, the HCD must set the
HostControllerFunctionalState field of the HcControl register before generating USB
traffic.
A simplistic flow diagram showing when and how to generate USB traffic is shown in
1. Reset
This includes hardware reset by pin RESET and software reset by the
HcSoftwareReset command (A9H). The reset function will clear all the HC’s
internal control registers to their reset status. After reset, the HCD must initialize
the ISP1161A1 USB HC by setting some registers.
2. Initialize HC
It includes:
a. Setting the physical size for the HC’s internal FIFO buffer RAM by setting the
HcITLBufferLength register (2AH to read, AAH to write) and the
HcATLBufferLength register (2BH to read, ABH to write)
b. Setting the HcHardwareConfiguration register according to requirements
c. Clearing interrupt events, if required
d. Enabling interrupt events, if required
e. Setting the HcFmInterval register (0DH to read, 8DH to write)
f. Setting the HC’s Root Hub registers
g. Setting the HcControl register to move the HC into USBOperational state
See also Section 9.5.
3. Entry
The normal entry point. The microprocessor returns to this point when there
are HC requests.
4. Need USB traffic
USB devices need the HC to generate USB traffic when they have USB traffic
requests such as:
a. Connecting to or disconnecting from the downstream ports
b. Issuing the Resume signal to the HC
To generate USB traffic, the HCD must enter the USB transaction loop.
5. Prepare PTD data in microprocessor’s system RAM
The communication between the HCD and the ISP1161A1 HC is in the form of
Philips Transfer Descriptor (PTD) data. The PTD data provides USB traffic
information about the commands, status, and USB data packets.
8. HC performs USB transactions via USB bus interface
9. HC informs HCD of the USB traffic results
ISP1161A1
USB single-chip host and device controller
The physical storage media of PTD data for the HCD is the microprocessor’s
system RAM. For the ISP1161A1 HC, the storage media is the internal FIFO
buffer RAM.
The HCD prepares PTD data in the microprocessor system RAM for transfer to
the ISP1161A1 HC internal FIFO buffer RAM.
When PTD data is ready in the microprocessor’s system RAM, the HCD must
transfer the PTD data from the microprocessor’s system RAM into the
ISP1161A1 internal FIFO buffer RAM.
The HC determines what USB transactions are required based on the PTD data
that has been transferred into the internal FIFO buffer RAM.
The HC performs the USB transactions with the specified USB device endpoint
through the USB bus interface.
The USB transaction status and the feedback from the specified USB device
endpoint will be put back into the ISP1161A1 HC internal FIFO buffer RAM in
PTD data format. The HCD can read back the PTD data from the internal FIFO
buffer RAM.
9.3 PTD data structure
The Philips Transfer Descriptor (PTD) data structure provides communication
between the HCD and the ISP1161A1 USB HC. The PTD data contains information
required by the USB traffic. PTD data consists of a PTD followed by its payload data,
as shown in Figure 25.
top
bottom
Fig 25. PTD data in FIFO buffer RAM.
FIFO buffer RAM
PTD
payload data
PTD
payload data
PTD
payload data
PTD data #1
PTD data #2
PTD data #N
MGT949
The PTD data structure is used by the HC to define a bufferof data that will be moved
to or from an endpoint in the USB device. This data buffer is set up for the current
frame (1 ms frame) by the HCD.The payload data for every transfer in the frame must
have a PTD as a header to describe the characteristics of the transfer. PTD data is
DWORD (double-word or 4-byte) aligned.
The PTD forms the header of the PTD data. It tells the HC the transfer type, where
the payload data should go, and the actual size of the payload data. A PTD is an
8 byte data structure that is very important for HCD programming.
Table 4:Philips Transfer Descriptor (PTD): bit allocation
Table 5:Philips Transfer Descriptor (PTD): bit description
SymbolAccess Description
ActualBytes[9:0]R/WContains the number of bytes that were transferred for this PTD
CompletionCode[3:0]R/W0000NoErrorGeneral TD or isochronous data packet processing
completed with no detected errors.
0001CRCLast data packet from endpoint contained a CRC error.
0010BitStuffingLast data packet from endpoint contained a bit stuffing
violation.
0011DataToggleMismatchLast packet from endpoint had data toggle PID that did
not match the expected value.
0100StallTD was moved to the Done queue because the
endpoint returned a STALL PID.
0101DeviceNotResponding Device did not respond to token (IN) or did not provide a
handshake (OUT).
0110PIDCheckFailureCheck bits on PID from endpoint failed on data PID (IN)
or handshake (OUT)
0111UnexpectedPIDReceived PID was not valid when encountered or PID
value is not defined.
1000DataOverrunThe amount of data returned by the endpoint exceeded
either the size of the maximum data packet allowed
from the endpoint (found in the MaxPacketSize field of
ED) or the remaining buffer size.
1001DataUnderrunThe endpoint returned is less than MaxPacketSize and
that amount was not sufficient to fill the specified buffer.
1010reserved1011reserved1100BufferOverrunDuring an IN, the HC received data from an endpoint
faster than it could be written to system memory.
1101BufferUnderrunDuring an OUT,the HC could not retrieve data from the
system memory fast enough to keep up with the USB
data rate.
ActiveR/WSet to logic 1 by firmware to enable the execution of transactions by theHC. When the
transaction associated with this descriptor is completed, the HC sets this bit to logic 0,
indicating that a transaction for this element will not be executed when it is next
encountered in the schedule.
ToggleR/WUsed to generate or compare the data PID value (DATA0 or DATA1). It is updated after
each successful transmission or reception of a data packet.
MaxPacketSize[9:0]RThe maximum number of bytes that can be sent to or received from the endpoint in a
single data packet.
EndpointNumber[3:0]RUSB address of the endpoint within the function.
LastRLast PTD of a list (ITL or ATL). Logic 1 indicates that the PTD is the last PTD.
SpeedRSpeed of the endpoint:
0 — full speed
1 — low speed
TotalBytes[9:0]RSpecifies the total number of bytes to be transferred with this data structure. For Bulk and
Control only, this can be greater than MaxPacketSize.
B5_5R/WThis bit is logic 0 at power-on reset. When this feature is not used, software used for the
ISP1161A1 is the same for the ISP1160 and the ISP1161. When this bit is set to logic 1
in this PTD for interrupt endpoint transfer, only one PTD USB transaction will be sent out
in 1 ms.
FormatRThe format of this data structure. If this is a Control, Bulk or Interrupt endpoint, then
Format = 0. If this is an Isochronous endpoint, then Format = 1.
FunctionAddress[6:0]RThis is the USB address of the function containing the endpoint that this PTD refers to.
…continued
9.4 HC internal FIFO buffer RAM structure
9.4.1 Partitions
According to the
USB data transfers: Control, Bulk, Interrupt and Isochronous.
The HC’s internal FIFO buffer RAM has a physicalsize of 4 kbytes.This internal FIFO
buffer RAM is used for transferring data between the microprocessor and USB
peripheral devices. This on-chip buffer RAM can be partitioned into two areas:
Acknowledged Transfer List (ATL) buffer and Isochronous (ISO) Transfer List (ITL)
buffer. The ITL buffer is a Ping-Pong structured FIFO buffer RAM that is used to keep
the payload data and their PTD header for Isochronous transfers. The ATL buffer is a
non Ping-Pong structured FIFO buffer RAM that is used for the other three types of
transfers.
Universal Serial Bus Specification Rev. 2.0
, there are four types of
The ITL buffer can be further partitioned into ITL0 and ITL1 for the Ping-Pong
structure. The ITL0 buffer and ITL1 buffer always have the same size. The
microprocessor can put ISO data into either the ITL0 buffer or the ITL1 buffer. When
the microprocessor accesses an ITL buffer,the HC can take over the other ITL buffer
at the same time. This architecture improves the ISO transfer performance.
The HCD can assign the logical size for the ATL buffer and ITL buffers at any time, but
normally at initialization after power-on reset. This is done by setting the
HcATLBufferLength register (2BH to read, ABH to write) and HcITLBufferLength
register (2AH to read, AAH to write). The total buffer length cannot exceed the
maximum RAM size of 4 kbytes (ATL buffer + ITL buffer). Figure 26 shows the
partitions of the internal FIFO buffer RAM. When assigning buffer RAM sizes, follow
this formula:
ATL buffer length + 2 × (ITL buffer size) ≤ 1000H (that is, 4 kbytes)
where: ITL buffer size = ITL0 buffer length = ITL1 buffer length
The following assignments are examples of legal uses of the internal FIFO buffer
This is insufficient use of the internal FIFO buffer RAM.
This will use the internal FIFO buffer RAM for only ATL transfers.
FIFO buffer RAM
top
ITL0
ITL buffer
ITL1
ISO_A
ISO_B
programmable
sizes
ATL buffer
Fig 26. HC internal FIFO buffer RAM partitions.
ATL
bottom
control/bulk/interrupt
data
not used
MGT950
4 kbytes
The actual requirement for the buffer RAM need not reach the maximum size. You
can make your selection based on your application.
The following are some calculations of the ISO_A or ISO_B space for a frame of data:
• Maximum number of useful data sent during one USB frame is 1280 bytes (20
ISO packets of 64 bytes). The total RAM size needed is:
20 × 8 + 1280 = 1440 bytes.
• Maximum number of packets for different endpoints sent during one USB frame is
150 (150 ISO packets of 1 byte). The total RAM size needed is:
150 × 8 + 150 × 1 = 1350 bytes.
• The Ping buffer RAM (ITL0) and the PongbufferRAM (ITL1) havea maximum size
of 2 kbytes each. All data needed for one frame can be stored in the Ping or the
Pong buffer RAM.
When the embedded system wants to initiate a transfer to the USB bus, the data
needed for one frame is transferred to the ATL buffer or ITL buffer. The
microprocessor detects the buffer status through the interrupt routines. When the
HcBufferStatus register (2CH to read only) indicates that the buffer is empty,then the
microprocessor writes data into the buffer. When the HcBufferStatus register
indicates that the buffer is full, the data is ready on the buffer,and the microprocessor
needs to read data from the buffer.
During every 1 ms, there might be many events to generate interrupt requests to the
microprocessor for data transfer or status retrieval. However, each of the interrupt
types defined in this specification can be enabled or disabled by setting the
HcµPInterruptEnable register bits accordingly.