Full-speed Universal Serial Bus peripheral controller
Rev. 05 — 08 December 2004Product data
1.General description
The ISP1181A is a Universal Serial Bus (USB) peripheral controller that complies
with
UniversalSerial Bus Specification Rev. 2.0
(12 Mbit/s). It provides full-speed USB communication capacity to microcontroller or
microprocessor-based systems. The ISP1181A communicates with the system’s
microcontroller or microprocessor through a high-speed general-purpose parallel
interface.
The ISP1181A supports fully autonomous, multi-configurable Direct Memory Access
(DMA) operation.
The modular approach to implementing a USB peripheral controller allows the
designer to select the optimum system microcontrollerfrom the wide variety available.
The ability to reuse existing architecture and firmware investments shortens
development time, eliminates risks and reduces costs. The result is fast and efficient
development of the most cost-effective USB peripheral solution.
, supporting data transferat full-speed
2.Features
The ISP1181A is ideally suited forapplication in many personal computer peripherals
such as printers, communication devices, scanners, external mass storage (Zip
drive) devices and digital still cameras. It offers an immediate cost reduction for
applications that currently use SCSI implementations.
■ Complies with
specifications
■ Supports data transfer at full-speed (12 Mbit/s)
■ High performance USB peripheral controller with integrated Serial Interface
Engine (SIE), FIFO memory, transceiver and 3.3 V voltage regulator
■ High speed (11.1 Mbyte/s or 90 ns read/write cycle) parallel interface
■ Fully autonomous and multi-configuration DMA operation
■ Up to 14 programmable USB endpoints with 2 fixed control IN/OUT endpoints
■ Integrated physical 2462 bytes of multi-configuration FIFO memory
■ Endpoints with double buffering to increase throughput and ease real-time data
transfer
■ Seamless interface with most microcontrollers/microprocessors
■ Bus-powered capability with low power consumption and low ‘suspend’ current
■ 6 MHz crystal oscillator input with integrated PLL for low EMI
polarity, see Table 21); used by the DMA
controller to force the end of a DMA transfer
to the ISP1181A
DREQ116ODMA request output (4 mA; programmable
polarity, see Table 21); signals to the DMA
controller that the ISP1181A wants to start
a DMA transfer
DACK127IDMA acknowledge input (programmable
polarity, see Table 21); used by the DMA
controller to signal the start of a DMA
transfer requested by the ISP1181A
TEST1138Itest input; this pin must be connected to
via an external 10 kΩ resistor
V
CC
TEST2149Itest input; this pin must be connected to
via an external 10 kΩ resistor
V
CC
INT1510Ointerrupt output; programmable polarity
(active HIGH or LOW) and signalling (level
or pulse); see Table 21
TEST31611Otest output; this pin is used for test
purposes only
BUS_CONF01712Ibus configuration selector; see Table 3
BUS_CONF11813Ibus configuration selector; see Table 3
DATA151914I/Obit 15 of D[15:0]; bidirectional data line
(slew-rate controlled output, 4 mA)
DATA142015I/Obit 14 of D[15:0]; bidirectional data line
(slew-rate controlled output, 4 mA)
DATA132116I/Obit 13 of D[15:0]; bidirectional data line
(slew-rate controlled output, 4 mA)
DATA122217I/Obit 12 of D[15:0]; bidirectional data line
(slew-rate controlled output, 4 mA)
DATA112318I/Obit 11 of D[15:0]; bidirectional data line
(slew-rate controlled output, 4 mA)
DATA102419I/Obit 10 of D[15:0]; bidirectional data line
(slew-rate controlled output, 4 mA)
GND2520-ground supply
V
ref
2621-I/O pin reference voltage (3.3 V); no
connection if V
CC
= 5.0 V
DATA92722I/Obit9 of D[15:0]; bidirectional data line
(slew-rate controlled output, 4 mA)
DATA82823I/Obit8 of D[15:0]; bidirectional data line
(slew-rate controlled output, 4 mA)
DATA72924I/Obit7 of D[15:0]; bidirectional data line
(slew-rate controlled output, 4 mA)
DATA63025I/Obit6 of D[15:0]; bidirectional data line
The ISP1181A is a full-speed USB peripheral controller with up to 14 configurable
endpoints. It has a fast general-purpose parallel interface for communication with
many types of microcontrollers or microprocessors. It supports different bus
configurations (see Table 3) and local DMA transfers of up to 16 bytes per cycle. The
block diagram is given in Figure 1.
The ISP1181A has 2462 bytes of internal FIFO memory, which is shared among the
enabled USB endpoints. The type and FIFO size of each endpoint can be individually
configured, depending on the required packet size. Isochronous and bulk endpoints
are double-buffered for increased data throughput.
The ISP1181A requires a single supply voltage of 3.3 Vor 5.0 V and has an internal
3.3 V voltage regulator for powering the analog USB transceiver. It supports
bus-powered operation.
The ISP1181A operates on a 6 MHz oscillator frequency. A programmable clock
output is available up to 48 MHz. During ‘suspend’ state the 100 kHz ± 50 %
LazyClock frequency can be output.
ISP1181A
Full-speed USB peripheral controller
7.1 Analog transceiver
The transceiver is compliant with the
speed)
resistors.
. It interfaces directly with the USB cable through external termination
Universal Serial Bus Specification Rev. 2.0 (full
7.2 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.
7.3 Memory Management Unit (MMU) and integrated RAM
The MMU and the integrated RAM provide the conversion between the USB speed
(12 Mbit/s bursts) and the parallel interface to the microcontroller (max. 12 Mbyte/s).
This allows the microcontroller to read and write USB packets at its own speed.
7.4 SoftConnect
The connection to the USB is accomplished by bringing D+ (for full-speed USB
peripherals) HIGH through a 1.5 kΩ pull-up resistor. In the ISP1181A, the 1.5 kΩ
pull-up resistor is integrated on-chip and is not connected to VCC by default. The
connection is established by a command sent from the external/system
microcontroller. This allows the system microcontroller to complete its initialization
sequence before deciding to establishconnection with the USB. Reinitialization of the
USB connection can also be performed without disconnecting the cable.
Without V
With V
there is noise on the (D+, D-) lines, it is not taken into account. This ensures that the
peripheral remains in the suspend state.
Remark: Note that 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.
7.5 GoodLink
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 ISP1181A has been successfully enumerated (the peripheral address is set), the
LED indicator will remain permanently on. Upon each successful packettransfer(with
ACK) to and from the ISP1181A, the LED will blink off for 100 ms. During ‘suspend’
state, the LED will remain off.
Full-speed USB peripheral controller
sensing prevents the peripheral from wake-up when V
sensing, any activity or noise on (D+, D-) might wake up the peripheral.
BUS
sensing, (D+, D-) is decoupled when no V
BUS
is present. Therefore, even if
BUS
ISP1181A
is not present.
BUS
This feature provides a user-friendly indication of the status of the USB peripheral,
the connected hub,and the USB traffic. It is a useful field diagnostics tool forisolating
faulty equipment. It can therefore help to reduce field support and hotline overhead.
7.6 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 by the
USB Specification Rev. 2.0
.
7.7 Voltage regulator
A 5 V-to-3.3 V voltage regulator is integrated on-chip to supply the analog transceiver
and internal logic. This voltage is availableat pin V
to supply an external 1.5 kΩ
reg(3.3)
pull-up resistor on the D+ line. Alternatively, the ISP1181A provides SoftConnect
technology via an integrated 1.5 kΩ pull-up resistor (see Section 7.4).
7.8 PLL clock multiplier
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.9 Parallel I/O (PIO) and Direct Memory Access (DMA) interface
A generic PIO interface is defined for speed and ease-of-use. It also allows direct
interfacing to most microcontrollers. To a microcontroller, the ISP1181A appears as a
memory device with an 8/16-bit data bus and a 1-bit address line. The ISP1181A
supports both multiplexed and non-multiplexed address and data buses.
The ISP1181A can also be configured as a DMA slave device to allow more efficient
data transfer. One of the 14 endpoint FIFOs may directly transfer data to/from the
local shared memory. The DMA interface can be configured independently from the
PIO interface.
The ISP1181A has fourbusconfiguration modes, selected via pins BUS_CONF1 and
BUS_CONF0:
Mode 016-bit I/O port shared with 16-bit DMA port
Mode 1reserved
Mode 28-bit I/O port shared with 8-bit DMA port
Mode 3reserved.
The bus configurations foreach of these modes are given in Table 3. Typical interface
circuits for each mode are given in Section 21.1.
Table 3:Bus configuration modes
ModeBUS_CONF[1:0]PIO widthDMA widthDescription
DMAWD = 0DMAWD = 1
000D[15:1], AD0-D[15:1], AD0multiplexed address/data on pin AD0;
bus is shared by 16-bit I/O port and
16-bit DMA port
101reservedreservedreservedreserved
210D[7:1], AD0D[7:1], AD0-multiplexed address/data on pin AD0;
bus is shared by 8-bit I/O port and 8-bit
DMA port
311reservedreservedreservedreserved
9.Endpoint descriptions
Each USB peripheral is logically composed of several independent endpoints. An
endpoint acts as a terminus of a communication flow between the host and the
peripheral. At design time each endpoint is assigned a unique number (endpoint
identifier, see Table 4). The combination of the peripheral address (given by the host
during enumeration), the endpoint number, and the transfer direction allows each
endpoint to be uniquely referenced.
The ISP1181A has 16 endpoints: endpoint 0 (control IN and OUT) plus 14
configurable endpoints, which can be individually defined as
interrupt/bulk/isochronous, IN or OUT. Each enabled endpoint has an associated
FIFO, which can be accessed either via the parallel I/O interface or via DMA.
9.1 Endpoint access
Table 4 lists the endpoint access modes and programmability. All endpoints support
I/O mode access. Endpoints 1 to 14 also support DMA access. FIFO DMA access is
selected and enabled via bits EPIDX[3:0] and DMAEN of the DMA Configuration
Register. A detailed description of the DMA operation is given in Section 10.
064 (fixed)noyesnocontrol OUT
064 (fixed)noyesnocontrol IN
1programmablesupportedsupportedsupportedprogrammable
2programmablesupportedsupportedsupportedprogrammable
3programmablesupportedsupportedsupportedprogrammable
4programmablesupportedsupportedsupportedprogrammable
5programmablesupportedsupportedsupportedprogrammable
6programmablesupportedsupportedsupportedprogrammable
7programmablesupportedsupportedsupportedprogrammable
8programmablesupportedsupportedsupportedprogrammable
9programmablesupportedsupportedsupportedprogrammable
10programmablesupportedsupportedsupportedprogrammable
11programmablesupportedsupportedsupportedprogrammable
12programmablesupportedsupportedsupportedprogrammable
13programmablesupportedsupportedsupportedprogrammable
14programmablesupportedsupportedsupportedprogrammable
FIFO size (bytes)
[1]
Double
buffering
I/O mode
access
DMA mode
access
Endpoint type
[2]
[2]
[1] The total amount of FIFO storage allocated to enabled endpoints must not exceed 2462 bytes.
[2] IN: input for the USB host (ISP1181A transmits); OUT: output from the USB host (ISP1181A receives). The data flow direction is
determined by bit EPDIR in the Endpoint Configuration Register.
9.2 Endpoint FIFO size
The size of the FIFO determines the maximum packet size that the hardware can
support for a given endpoint. Only enabled endpoints are allocated space in the
shared FIFO storage, disabled endpoints have zero bytes. Table 5 lists the
programmable FIFO sizes.
The following bits in the Endpoint Configuration Register (ECR) affect FIFO
allocation:
• Endpoint enable bit (FIFOEN)
• Size bits of an enabled endpoint (FFOSZ[3:0])
• Isochronous bit of an enabled endpoint (FFOISO).
Remark: Register changes that affect the allocation of the shared FIFO storage
among endpoints must not be made while valid data is present in any FIFO of the
enabled endpoints. Such changes will render all FIFO contents undefined.
Each programmable FIFO can be configured independently via its ECR, but the total
physical size of all enabled endpoints (IN plus OUT) must not exceed 2462 bytes.
Table 6 showsan exampleof a configuration fitting in the maximumavailable space of
2462 bytes. The total number of logical bytes in the example is 1311. The physical
storage capacity used for double buffering is managed by the peripheral hardware
and is transparent to the user.
Table 6:Memory configuration example
Physical size
(bytes)
6464control IN (64 byte fixed)
6464control OUT (64 byte fixed)
20461023double-buffered 1023-byte isochronous endpoint
161616-byte interrupt OUT
161616-byte interrupt IN
12864double-buffered 64-byte bulk OUT
12864double-buffered 64-byte bulk IN
In response to the standard USB request, Set Interface, the firmware must program
all 16 ECRs of the ISP1181A in sequence (see Table 4), whether the endpoints are
enabled or not. The hardware will then automatically allocate FIFO storage space.
If all endpoints havebeen configured successfully, the firmware must return an empty
packet to the control IN endpoint to acknowledge success to the host. If there are
errors in the endpoint configuration, the firmware must stall the control IN endpoint.
When reset by hardware or via the USB bus, the ISP1181A disables all endpoints
and clears all ECRs, except for the control endpoint which is fixed and always
enabled.
Endpoint initialization can be done at any time; however, it is valid only after
enumeration.
9.4 Endpoint I/O mode access
When an endpoint event occurs (a packet is transmitted or received), the associated
endpoint interrupt bits (EPn) of the Interrupt Register (IR) will be set by the SIE. The
firmware then responds to the interrupt and selects the endpoint for processing.
ISP1181A
Full-speed USB peripheral controller
The endpoint interrupt bit will be cleared by reading the Endpoint Status Register
(ESR). The ESR also contains information on the status of the endpoint buffer.
For an OUT (= receive) endpoint, the packet length and packet data can be read from
ISP1181A using the Read Buffer command. When the whole packet has been read,
the firmware sends a Clear Buffer command to enable the reception of new packets.
For an IN (= transmit) endpoint, the packet length and data to be sent can be written
to ISP1181A using the Write Buffer command. When the whole packet has been
written to the buffer, the firmware sends a Validate Buffer command to enable data
transmission to the host.
9.5 Special actions on control endpoints
Control endpoints require special firmware actions. The arrival of a SETUP packet
flushes the IN bufferand disables the Validate Buffer and Clear Buffer commands for
the control IN and OUT endpoints. The microcontroller needs to re-enable these
commands by sending an Acknowledge Setup command to both control endpoints.
This ensures that the last SETUP packet stays in the buffer and that no packets can
be sent back to the host until the microcontroller has explicitly acknowledged that it
has seen the SETUP packet.
Direct Memory Access (DMA) is a method to transfer data from one location to
another in a computer system, without intervention of the central processor (CPU).
Many different implementations of DMA exist. The ISP1181A supports two methods:
• 8237 compatible mode: based on the DMA subsystem of the IBM personal
• DACK-only mode: based on the DMA implementation in some embedded RISC
The ISP1181A supports DMA transfer for all 14 configurable endpoints (see Table 4).
Only one endpoint at a time can be selected for DMA transfer.The DMA operation of
the ISP1181A can be interleaved with normal I/O mode access to other endpoints.
The following features are supported:
• Single-cycle or burst transfers (up to 16 bytes per cycle)
• Programmable signal levels on pins DREQ, DACK and EOT.
ISP1181A
Full-speed USB peripheral controller
computers (PC, AT and all its successors and clones); this architecture uses the
Intel 8237 DMA controller and has separate address spaces for memory and I/O
processors, which has a single address space for both memory and I/O.
short/empty packet
10.1 Selecting an endpoint for DMA transfer
The target endpoint for DMA access is selected via bits EPDIX[3:0] in the DMA
Configuration Register, as shown in Table 7. The transfer direction (read or write) is
automatically set by bit EPDIR in the associated ECR, to match the selected endpoint
type (OUT endpoint: read; IN endpoint: write).
Asserting input DACK automatically selects the endpoint specified in the DMA
Configuration Register, regardless of the current endpoint used for I/O mode access.
The 8237 compatible DMA mode is selected by clearing bit DAKOLY in the Hardware
Configuration Register (see Table 20). The pin functions for this mode are shown in
Table 8.
Table 8:8237 compatible mode: pin functions
SymbolDescriptionI/OFunction
DREQDMA requestOISP1181A requests a DMA transfer
DACKDMA acknowledgeIDMA controller confirms the transfer
EOTend of transferIDMA controller terminates the transfer
RDread strobeIinstructs ISP1181A to put data on the bus
WRwrite strobeIinstructs ISP1181A to get data from the
…continued
EPDIR = 0EPDIR = 1
bus
The DMA subsystem of an IBM compatible PC is based on the Intel 8237 DMA
controller. It operates as a ‘fly-by’ DMA controller: the data is not stored in the DMA
controller, but it is transferred between an I/O port and a memory address. A typical
example of ISP1181A in 8237 compatible DMA mode is given in Figure 4.
The 8237 has two control signals for each DMA channel: DREQ (DMA Request) and
DACK (DMA Acknowledge). General control signals are HRQ (Hold Request) and
HLDA (Hold Acknowledge). The bus operation is controlled via MEMR (Memory
Read), MEMW (Memory Write), IOR (I/O read) and IOW (I/O write).
The following example shows the steps which occur in a typical DMA transfer:
1. ISP1181A receives a data packet in one of its endpoint FIFOs; the packet must
2. ISP1181A asserts the DREQ signal requesting the 8237 for a DMA transfer.
3. The 8237 asks the CPU to release the bus by asserting the HRQ signal.
4. After completing the current instruction cycle, the CPU places the bus control
5. The 8237 now sets its address lines to 1234H and activates the MEMW and IOR
6. The 8237 asserts DACK to inform the ISP1181A that it will start a DMA transfer.
7. The ISP1181A now places the byte or word to be transferred on the data bus
8. The8237waits one DMA clock period and then de-asserts MEMW and IOR. This
9. The ISP1181A de-asserts the DREQ signal to indicate to the 8237 that DMA is
10. The 8237 de-asserts the DACK output indicating that the ISP1181A must stop
11. The 8237 places the bus control signals (MEMR, MEMW, IOR and IOW) and the
12. The CPU acknowledges control of the bus by de-asserting HLDA. After activating
ISP1181A
Full-speed USB peripheral controller
be transferred to memory address 1234H.
signals (MEMR, MEMW, IOR and IOW) and the address lines in three-state and
asserts HLDA to inform the 8237 that it has control of the bus.
control signals.
lines, because its RD signal was asserted by the 8237.
latches and stores the byte or word at the desired memory location. It also
informs the ISP1181A that the data on the bus lines has been transferred.
no longer needed. In Single cycle mode this is done after each byte or word, in
Burst mode following the last transferred byte or word of the DMA cycle.
placing data on the bus.
address lines in three-state and de-asserts the HRQ signal, informing the CPU
that it has released the bus.
the bus control lines (MEMR, MEMW, IOR and IOW) and the address lines, the
CPU resumes the execution of instructions.
Fora typical bulk transfer the above process is repeated 64 times, once for each byte.
After each byte the address register in the DMA controller is incremented and the
byte counter is decremented. When using 16-bit DMA, the number of transfers is 32,
and address incrementing and byte counter decrementing is done by 2 for each word.
10.3 DACK-only mode
The DACK-only DMA mode is selected by setting bit DAKOLY in the Hardware
Configuration Register (see Table 20). The pin functions for this mode are shown in
Table 9.Atypical exampleof ISP1181A in DACK-onlyDMA mode is given in Figure 5.
Table 9:DACK-only mode: pin functions
SymbolDescriptionI/OFunction
DREQDMA requestOISP1181A requests a DMA transfer
DACKDMA acknowledgeIDMA controller confirms the transfer;
also functions as data strobe
EOTEnd-Of-TransferIDMA controller terminates the transfer
RDread strobeInot used
WRwrite strobeInot used
In DACK-only mode the ISP1181A uses the DACK signal as data strobe. Input
signals RD and WR are ignored. This mode is used in CPU systems that have a
single address space for memory and I/O access. Such systems have no separate
MEMW and MEMR signals: the RD and WR signals are also used as memory data
strobes.
ISP1181A
Full-speed USB peripheral controller
ISP1181ADMA
DREQ
DACK
AD0,
DATA1 to DATA15
Fig 5. ISP1181A in DACK-only DMA mode.
10.4 End-Of-Transfer conditions
10.4.1 Bulk endpoints
A DMA transfer to/from a bulk endpoint can be terminated by any of the following
conditions (bit names refer to the DMA Configuration Register, see Table 24):
• An external End-Of-Transfer signal occurs on input EOT
• The DMA transfer completes as programmed in the DMA Counter register
(CNTREN = 1)
• A short packet is received on an enabled OUT endpoint (SHORTP = 1)
• DMA operation is disabled by clearing bit DMAEN.
RAM
CONTROLLER
DREQ
DACK
RD
WR
HRQ
HLDA
CPU
HRQ
HLDA
004aaa023
External EOT: When reading from an OUT endpoint, an external EOT will stop the
DMA operation and clear any remaining data in the current FIFO. For a doublebuffered endpoint the other (inactive) buffer is not affected.
When writing to an IN endpoint, an EOT will stop the DMA operation and the data
packet in the FIFO (evenif it is smaller than the maximum packet size) will be sent to
the USB host at the next IN token.
DMA Counter Register: An EOT from the DMA Counter Register is enabled by
setting bit CNTREN in the DMA Configuration Register. The ISP1181A has a 16-bit
DMA Counter Register, which specifies the number of bytes to be transferred. When
DMA is enabled (DMAEN = 1), the internal DMA counter is loaded with the value from
the DMA Counter Register. When the internal counter completes the transfer as
programmed in the DMA counter, an EOT condition is generated and the DMA
operation stops.
Short packet: Normally, the transfer byte count must be set via a control endpoint
before any DMA transfer takes place. When a short packet has been enabled as EOT
indicator (SHORTP = 1), the transfer size is determined by the presence of a short
packet in the data. This mechanism permits the use of a fully autonomous data
transfer protocol.
When reading from an OUT endpoint, reception of a short packet at an OUT token
will stop the DMA operation after transferring the data bytes of this packet.
Table 10: Summary of EOT conditions for a bulk endpoint
EOT conditionOUT endpointIN endpoint
EOT inputEOT is activeEOT is active
DMA Counter Registertransfer completes as
Short packetshort packet is received and
DMAEN bit in DMA
Configuration Register
Full-speed USB peripheral controller
programmed in the DMA
Counter register
transferred
DMAEN = 0
[1]
ISP1181A
transfer completes as
programmed in the DMA
Counter register
counter reaches zero in the
middle of the buffer
DMAEN = 0
[1]
[1] The DMA transfer stops. However, no interrupt is generated.
10.4.2 Isochronous endpoints
A DMA transfer to/from an isochronous endpoint can be terminated by any of the
following conditions (bit names refer to the DMA Configuration Register, see
Table 24):
• An external End-Of-Transfer signal occurs on input EOT
• The DMA transfer completes as programmed in the DMA Counter register
(CNTREN = 1)
• An End-Of-Packet (EOP) signal is detected
• DMA operation is disabled by clearing bit DMAEN.
Table 11: Recommended EOT usage for isochronous endpoints
EOT conditionOUT endpointIN endpoint
EOT input activedo not usepreferred
DMA Counter Register zerodo not usepreferred
End-Of-Packetpreferreddo not use
The ISP1181A detects a USB suspend status when a constant idle state is present
on the USB bus for more than 3 ms.
The bus-powered devices that are suspended must not consume more than 500 µA
of current. This is achieved by shutting down power to system components or
supplying them with a reduced voltage.
The steps leading up to suspend status are as follows:
1. On detecting a wakeup-to-suspend transition, the ISP1181A sets bit SUSPND in
the Interrupt register. This will generate an interrupt if bit IESUSP in the Interrupt
Enable register is set.
2. When the firmware detects a suspend condition, it must prepare all system
components for the suspend state:
a. Allsignals connected to the ISP1181A must enter appropriate states to meet
the power consumption requirements of the suspend state.
b. All input pins of the ISP1181A must have a CMOS LOW or HIGH level.
3. In the interrupt service routine, the firmware must check the current status of the
USB bus. When bit BUSTATUS in the Interrupt register is logic 0, the USB bus
has left the suspend mode and the process must be aborted. Otherwise, the next
step can be executed.
4. To meet the suspend current requirements for a bus-powered device, the internal
clocks must be switched off by clearing bit CLKRUN in the Hardware
Configuration register.
5. When the firmware has set and cleared bit GOSUSP in the Mode register, the
ISP1181A enters the suspend state. In powered-off application, the ISP1181A
asserts output SUSPEND and switches off the internal clocks after 2 ms.
• A: indicates the point at which the USB bus enters the idle state.
• B: indicates resume condition, which can be a 20 ms K-state on the USB bus, a
HIGH level on pin WAKEUP, or a LOW level on pin CS.
• C: indicates remote wake-up. The ISP1181A will drive a K-state on the USB bus
for 10 ms after pin WAKEUP goes HIGH or pin CS goes LOW.
• D: after detecting the suspend interrupt, set and clear bit GOSUSP in the Mode
register.
11.1.1 Powered-off application
Figure 7 shows a typical bus-powered modem application using the ISP1181A. The
SUSPEND output switches off powerto the microcontroller and other external circuits
during the suspend state. The ISP1181A is woken up through the USB bus (global
resume) or by the ring detection circuit on the telephone line.
Fig 7. SUSPEND and WAKEUP signals in a powered-off modem application.
11.2 Resume conditions
A wake-up from the suspend state is initiated either by the USB host or by the
application:
• USB host: drives a K-state on the USB bus (global resume)
• Application: remote wake-up through a HIGH level on input WAKEUP or a LOW
ISP1181A
Full-speed USB peripheral controller
V
BUS
V
BUS
USB
DP
DM
ISP1181A
SUSPEND
WAKEUP
level on input CS (if enabled using bit WKUPCS in the Hardware Configuration
register). Wake-up on CS will work only if V
V
CC
8031
RST
RING DETECTION
is present.
BUS
LINE
004aaa673
The steps of a wake-up sequence are as follows:
1. Theinternal oscillator and the PLL multiplier are re-enabled. When stabilized, the
clock signals are routed to all internal circuits of the ISP1181A.
2. TheSUSPEND output is deasserted, and bit RESUME in the Interrupt register is
set. This will generate an interrupt if bit IERESUME in the Interrupt Enable
register is set.
3. Maximum15 ms after starting the wake-up sequence, the ISP1181A resumes its
normal functionality.
4. In case of a remote wake-up, the ISP1181A drives a K-state on the USB bus for
10 ms.
5. Following the deassertion of output SUSPEND, the application restores itself and
other system components to the normal operating mode.
6. After wake-up, the internal registers of the ISP1181A are write-protected to
prevent corruption by inadvertent writing during power-up of external
components. The firmware must send an Unlock Device command to the
ISP1181A to restore its full functionality.
11.3 Control bits in suspend and resume
Table 12: Summary of control bits
RegisterBitFunction
InterruptSUSPNDa transition from awake to the suspend state was detected
BUSTATUSmonitors USB bus status (logic 1 = suspend); used when
interrupt is serviced
RESUMEa transition from suspend to the resume state was detected
Interrupt Enable IESUSPenables output INT to signal the suspend state
ModeSOFTCTenables SoftConnect pull-up resistor to USB bus
Hardware
Configuration
Unlockallsending data AA37H unlocks the internal registers for
12. Commands and registers
The functions and registers of ISP1181A are accessed via commands, which consist
of a command code followed by optional data bytes (read or write action). An
overview of the available commands and registers is given in Table 13.
A complete access consists of two phases:
1. Commandphase: when address bit A0 = 1, the ISP1181A interprets the data on
the lower byte of the bus bits D[7:0] as a command code. Commands without a
data phase are executed immediately.
2. Data phase (optional): when address bit A0 = 0, the ISP1181A transfers the
data on the bus to or from a register or endpoint FIFO. Multi-byte registers are
accessed least significant byte/word first.
…continued
IERESUMEenables output INT to signal the resume state
GOSUSPa HIGH-to-LOW transition enables the suspend state
EXTPULselects internal (SoftConnect) or external pull-up resistor
WKUPCSenables wake-up on LOW level of input
PWROFFselects powered-off mode during the suspend state
writing after a resume
CS
The following applies for register or FIFO access in 16-bit bus mode:
• The upper byte (bits D15 to D8) in command phase or the undefined byte in data
phase are ignored.
• The access of registers is word-aligned: byte access is not allowed.
• If the packet length is odd, the upper byte of the last word in an IN endpoint buffer
is not transmitted to the host. When reading from an OUT endpoint buffer, the
upper byte of the last word must be ignored by the firmware. The packet length is
stored in the first 2 bytes of the endpoint buffer.
Table 13: Command and register summary
NameDestinationCode (Hex)Transaction
Initialization commands
Write Control OUT ConfigurationEndpoint Configuration Register
endpoint 0 OUT
Write Control IN ConfigurationEndpoint Configuration Register
endpoint 0 IN
Write Endpoint n Configuration
(n = 1 to 14)
Read Control OUT ConfigurationEndpoint Configuration Register
Write Control OUT Bufferillegal: endpoint is read-only(00)Write Control IN BufferFIFO endpoint 0 IN01N ≤ 64 bytes
Write Endpoint n Buffer
(n = 1 to 14)
FIFO endpoint 1 to 14
(IN endpoints only)
02 to 0Fisochronous: N ≤ 1023 bytes
interrupt/bulk: N ≤ 64 bytes
Read Control OUT BufferFIFO endpoint 0 OUT10N ≤ 64 bytes
Read Control IN Bufferillegal: endpoint is write-only(11)Read Endpoint n Buffer
(n = 1 to 14)
FIFO endpoint 1 to 14
(OUT endpoints only)
12 to 1Fisochronous:
N ≤ 1023 bytes
interrupt/bulk: N ≤ 64 bytes
Stall Control OUT EndpointEndpoint 0 OUT40Stall Control IN EndpointEndpoint 0 IN41Stall Endpoint n
Endpoint 1 to 1442 to 4F-
(n = 1 to 14)
Read Control OUT StatusEndpoint Status Register
50read 1 byte
[2]
endpoint 0 OUT
Read Control IN StatusEndpoint Status Register
51read 1 byte
[2]
endpoint 0 IN
Read Endpoint n Status
(n = 1 to 14)
Validate Control OUT Bufferillegal: IN endpoints only
Validate Control IN BufferFIFO endpoint 0 IN
Validate Endpoint n Buffer
(n = 1 to 14)
Endpoint Status Register n
endpoint 1 to 14
[5]
[5]
FIFO endpoint 1 to 14
(IN endpoints only)
[5]
52 to 5Fread 1 byte
(60)6162 to 6F-
Clear Control OUT BufferFIFO endpoint 0 OUT70Clear Control IN Bufferillegal
Clear Endpoint n Buffer
(n = 1 to 14)
[6]
FIFO endpoint 1 to 14
(OUT endpoints only)
(71)72 to 7F
[6]
[3]
[3]
[3]
[3]
[2]
Unstall Control OUT EndpointEndpoint 0 OUT80Unstall Control IN EndpointEndpoint 0 IN81-
[1] With N representing the number of bytes, the number of words for 16-bit bus width is: (N + 1) DIV 2.
[2] When accessing an 8-bit register in 16-bit mode, the upper byte is invalid.
[3] In 8-bit bus mode this command requires more time to complete than other commands. See Table 58.
[4] During isochronous transfer in 16-bit mode, because N≤ 1023, the firmware must take care of the upper byte.
[5] Validating an OUT endpoint buffer causes unpredictable behavior of ISP1181A.
[6] Clearing an IN endpoint buffer causes unpredictable behavior of ISP1181A.
[7] Reads a copy of the Status Register: executing this command does not clear any status bits or interrupt bits.
12.1 Initialization commands
Initialization commands are used during the enumeration process of the USB
network. These commands are used to configure and enable the embedded
endpoints. They also serve to set the USB assigned address of ISP1181A and to
perform a device reset.
12.1.1 Write/Read Endpoint Configuration
This command is used to access the Endpoint Configuration Register (ECR) of the
target endpoint. It defines the endpoint type (isochronous or bulk/interrupt), direction
(OUT/IN), FIFO size and buffering scheme. It also enables the endpoint FIFO. The
register bit allocation is shown in Table 14. A bus reset will disable all endpoints.
The allocation of FIFO memory only takes place after all 16 endpoints have been
configured in sequence (from endpoint 0 OUT to endpoint 14). Although the control
endpoints have fixed configurations, they must be included in the initialization
sequence and be configured with their default values (see Table 4). Automatic FIFO
allocation starts when endpoint 14 has been configured.
Remark: If any change is made to an endpoint configuration which affects the
allocated memory (size, enable/disable), the FIFO memory contents of all endpoints
becomes invalid. Therefore, all valid data must be removed from enabled endpoints
before changing the configuration.
Code (Hex): 20 to 2F — write (control OUT, control IN, endpoint 1 to 14)
Code (Hex): 30 to 3F — read (control OUT, control IN, endpoint 1 to 14)
Transaction — write/read 1 byte
Table 14: Endpoint Configuration Register: bit allocation
Table 15: Endpoint Configuration Register: bit description
BitSymbolDescription
7FIFOENA logic 1 indicates an enabled FIFO with allocated memory.
A logic 0 indicates a disabled FIFO (no bytes allocated).
6EPDIRThis bit defines the endpoint direction (0 = OUT, 1 = IN). It also
determines the DMA transfer direction (0 = read, 1 = write).
5DBLBUFA logic 1 indicates that this endpoint has double buffering.
4FFOISOA logic 1 indicates an isochronous endpoint. A logic 0 indicates
a bulk or interrupt endpoint.
3 to 0FFOSZ[3:0]Selects the FIFO size according to Table 5
12.1.2 Write/Read Device Address
This command is used to set the USB assigned address in the Address Register and
enable the USB device. The Address Register bit allocation is shown in Table 16.
A USB bus reset sets the device address to 00H (internally) and enables the device.
The value of the Address Register (accessible by the micro) is not altered by the bus
reset. In response to the standard USB request Set Address the firmware must issue
a Write Device Address command, followed by sending an empty packet to the host.
The new device address is activated when the host acknowledges the empty packet.
7DEVENA logic 1 enables the device.
6 to 0DEVADR[6:0] This field specifies the USB device address.
12.1.3 Write/Read Mode Register
This command is used to access the ISP1181A Mode Register, which consists of
1 byte (bit allocation: see Table 18). In 16-bit bus mode the upper byte is ignored.
The Mode Register controls the DMA bus width, resume and suspend modes,
interrupt activity and SoftConnect operation. It can be used to enable debug mode,
where all errors and Not Acknowledge (NAK) conditions will generate an interrupt.
0 and 2). A logic 0 selects 8-bit DMA bus width. Bus reset value:
unchanged.
6-reserved
5GOSUSPWriting a logic 1 followed by a logic0 will activate ‘suspend’
mode.
4-reserved
3INTENAA logic 1 enables all interrupts. Bus reset value: unchanged.
2DBGMODA logic 1 enables debug mode. where all NAKs and errors will
generate an interrupt. A logic 0 selects normal operation, where
interrupts are generated on every ACK (bulk endpoints) or after
every data transfer (isochronous endpoints). Bus reset value:
unchanged.
1-reserved
0SOFTCTA logic 1 enables SoftConnect (see Section 7.4). This bit is
ignored if EXTPUL = 1 in the Hardware Configuration Register
This command is used to access the Hardware Configuration Register, which
consists of 2 bytes. The first (lower) byte contains the device configuration and
control values, the second (upper) byte holds the clock control bits and the clock
division factor. The bit allocation is given in Table 20. A bus reset will not change any
of the programmed bit values.
The Hardware Configuration Register controls the connection to the USB bus, clock
activity and power supply during ‘suspend’ state, output clock frequency, DMA
operating mode and pin configurations (polarity, signalling mode).
Table 21: Hardware Configuration Register: bit description
BitSymbolDescription
6DRQPOLSelects DREQ signal polarity (0 = active LOW, 1 = active
HIGH). Bus reset value: unchanged.
5DAKPOLSelects DACK signal polarity (0 = activeLOW, 1 = active HIGH).
Bus reset value: unchanged.
4EOTPOLSelects EOT signal polarity (0 = active LOW, 1 = active HIGH).
Bus reset value: unchanged.
3WKUPCSA logic 1 enables remote wake-up via a LOW level on input
(For wake-up on
Bus reset value: unchanged.
2PWROFFA logic 1 enables powering-off during ‘suspend’ state. Output
SUSPEND is configured as a power switch control signal for
external devices (HIGH during ‘suspend’). This value should
always be initialized to logic 1. Bus reset value: unchanged.
1INTLVLSelects the interrupt signalling mode on output INT (0 = level,
1 = pulsed). In pulsed mode an interrupt produces an 166 ns
pulse. See Section 13 for details. Bus reset value: unchanged.
0INTPOLSelects INT signal polarity (0 = active LOW, 1 = active HIGH).
Bus reset value: unchanged.
12.1.5 Write/Read Interrupt Enable Register
This command is used to individually enable/disable interrupts from all endpoints, as
well as interrupts caused by events on the USB bus (SOF, SOF lost, EOT, suspend,
resume, reset). A bus reset will not change any of the programmed bit values.
CS to work, V
…continued
must be present.).
BUS
CS
The command accesses the Interrupt Enable Register, which consists of 4 bytes. The
bit allocation is given in Table 22.
Table 23: Interrupt Enable Register: bit description
BitSymbolDescription
31 to 24-reserved; must write logic 0
23 to 10IEP14 to IEP1 A logic 1 enables interrupts from the indicated endpoint.
9IEP0INA logic 1 enables interrupts from the control IN endpoint.
8IEP0OUTA logic 1 enables interrupts from the control OUT endpoint.
7, 6-reserved
5IEPSOFA logic 1 enables 1 ms interrupts upon detection of Pseudo
SOF.
4IESOFA logic 1 enables interrupt upon SOF detection.
3IEEOTA logic 1 enables interrupt upon EOT detection.
2IESUSPA logic 1 enables interrupt upon detection of ‘suspend’ state.
1IERESMA logic 1 enables interrupt upon detection of a ‘resume’ state.
0IERSTA logic 1 enables interrupt upon detection of a bus reset.
12.1.6 Write/Read DMA Configuration
This command defines the DMA configuration of ISP1181A and enables/disables
DMA transfers. The command accesses the DMA Configuration Register, which
consists of 2 bytes. The bit allocation is given in Table 24. A bus reset will clear bit
DMAEN (DMA disabled), all other bits remain unchanged.
Table 25: DMA Configuration Register: bit description
BitSymbolDescription
15CNTRENA logic 1 enables the generation of an EOT condition, when the
14SHORTPA logic 1 enables short/empty packet mode. When receiving
13 to 8-reserved
7 to 4EPDIX[3:0]Indicates the destination endpoint for DMA, see Table 7.
3DMAENWriting a logic 1 enables DMA transfer, a logic 0 forces the end
2-reserved
1 to 0BURSTL[1:0]Selects the DMA burst length:
ISP1181A
Full-speed USB peripheral controller
DMA Counter Register reaches zero. Bus reset value:
unchanged.
(OUT endpoint) a short/empty packet an EOT condition is
generated. When transmitting (IN endpoint) this bit should be
cleared. Bus reset value: unchanged.
of an ongoing DMA transfer. Reading this bit indicates whether
DMA is enabled (0 = DMA stopped, 1 = DMA enabled). This bit
is cleared by a bus reset.
00 — single-cycle mode (1 byte)
01 — burst mode (4 bytes)
10 — burst mode (8 bytes)
11 — burst mode (16 bytes).
Bus reset value: unchanged.
12.1.7 Write/Read DMA Counter
This command accesses the DMA Counter Register, which consists of 2 bytes. The
bit allocation is givenin Table 26. Writing to the register sets the number of bytes for a
DMA transfer. Reading the register returns the number of remaining bytes in the
current transfer. A bus reset will not change the programmed bit values.
The internal DMA counter is automatically reloaded from the DMA Counter Register
when DMA is re-enabled (DMAEN = 1). See Section 12.1.6 for more details.
15 to 8DMACRH[7:0] DMA Counter Register (high byte)
7 to 0DMACRL[7:0] DMA Counter Register (low byte)
12.1.8 Reset Device
This command resets the ISP1181A in the same way as an external hardware reset
via input RESET. All registers are initialized to their ‘reset’ values.
Code (Hex): F6 — reset the device
Transaction — none
12.2 Data flow commands
Data flow commands are used to manage the data transmission between the USB
endpoints and the system microcontroller. Much of the data flow is initiated via an
interrupt to the microcontroller. The data flow commands are used to access the
endpoints and determine whether the endpoint FIFOs contain valid data.
ISP1181A
Full-speed USB peripheral controller
Remark: The IN buffer of an endpoint contains input data for the host, the OUT bufferreceives output data from the host.
12.2.1 Write/Read Endpoint Buffer
This command is used to access endpoint FIFO buffers for reading or writing. First,
the buffer pointer is reset to the beginning of the buffer. Following the command, a
maximum of (N + 2) bytes can be written or read, N representing the size of the
endpoint buffer. For 16-bit access the maximum number of words is (M + 1), with M
given by (N + 1) DIV 2. After each read/write action the buffer pointer is automatically
incremented by 1 (8-bit bus width) or by 2 (16-bit bus width).
In DMA access the first 2 bytes or the first word (the packet length) are skipped:
transfers start at the third byte or the second word of the endpoint buffer. When
reading, the ISP1181A can detect the last byte/word via the EOP condition. When
writing to a bulk/interrupt endpoint, the endpoint buffer must be completely filled
beforesending the data to the host. Exception: when a DMA transfer is stopped by an
external EOT condition, the current buffer content (full or not) is sent to the host.
Remark: Reading data after a Write Endpoint Buffer command or writing data after a
Read Endpoint Buffer command data will cause unpredictable behavior of ISP1181A.
Code (Hex): 01 to 0F — write (control IN, endpoint 1 to 14)
Code (Hex): 10, 12 to 1F — read (control OUT, endpoint 1 to 14)
Transaction — write/read maximum N + 2 bytes (isochronous endpoint: N ≤ 1023,
bulk/interrupt endpoint: N ≤ 32)
The data in the endpoint FIFO must be organized as shown in Table 28. Examples of
endpoint FIFO access are given in Table 29 (8-bit bus) and Table 30 (16-bit bus).
Table 30: Example of endpoint FIFO access (16-bit bus width)
A0PhaseBus linesWord #Description
1commandD[7:0]-command code (00H to 1FH)
0dataD[15:0]0packet length
0dataD[15:0]1data word 1 (data byte 2, data byte 1)
0dataD[15:0]2data word 2 (data byte 4, data byte 3)
……………
Remark: There is no protection against writing or reading past a buffer’s boundary,
against writing into an OUT buffer or reading from an IN buffer. Any of these actions
could cause an incorrect operation. Data residing in an OUT buffer are only
meaningful after a successful transaction. Exception: during DMA access of a
double-buffered endpoint, the buffer pointer automatically points to the secondary
buffer after reaching the end of the primary buffer.
12.2.2 Read Endpoint Status
This command is used to read the status of an endpoint FIFO. The command
accesses the Endpoint Status Register, the bit allocation of which is shown in
Table 31. Reading the Endpoint Status Register will clear the interrupt bit set for the
corresponding endpoint in the Interrupt Register (see Table 48).
All bits of the Endpoint Status Register are read-only. Bit EPSTAL is controlled by the
Stall/Unstall commands and by the reception of a SETUP token (see Section 12.2.3).
D[15:8]-ignored
Code (Hex): 50 to 5F — read (control OUT, control IN, endpoint 1 to 14)
Table 32: Endpoint Status Register: bit description
BitSymbolDescription
7EPSTALThis bit indicates whether the endpoint is stalled or not
(1 = stalled, 0 = not stalled).
Set to logic 1 by a Stall Endpoint command,clearedtologic 0 by
an Unstall Endpoint command. The endpoint is automatically
unstalled upon reception of a SETUP token.
6EPFULL1A logic 1 indicates that the secondary endpoint buffer is full.
5EPFULL0A logic 1 indicates that the primary endpoint buffer is full.
4DATA_PIDThis bit indicates the data PID of the next packet (0 = DATA PID,
1 = DATA1 PID).
3OVERWRITEThis bit is set by hardware, a logic 1 indicating that a new Setup
packet has overwritten the previous setup information, before it
was acknowledgedorbefore the endpoint was stalled. This bit is
cleared by reading, if writing the setup data has finished.
Firmware must check this bit before sending an Acknowledge
Setup command or stalling the endpoint. Upon reading a logic 1
the firmware must stop ongoing setup actions andwaitfor a new
Setup packet.
2SETUPTA logic 1 indicates that the buffer contains a Setup packet.
1CPUBUFThis bit indicates which buffer is currently selected for CPU
These commands are used to stall or unstall an endpoint. The commands modify the
content of the Endpoint Status Register (see Table 31).
A stalled control endpoint is automatically unstalled when it receives a SETUP token,
regardless of the packet content. If the endpoint should stay in its stalled state, the
microcontroller can restall it with the Stall Endpoint command.
When a stalled endpoint is unstalled (either by the Unstall Endpoint command or by
receiving a SETUP token),it is also reinitialized. This flushes the buffer: 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.
Code (Hex): 40 to 4F — stall (control OUT, control IN, endpoint 1 to 14)
Code (Hex): 80 to 8F — unstall (control OUT, control IN, endpoint 1 to 14)
Transaction — none
This command signals the presence of valid data for transmission to the USB host, by
setting the Buffer Full flag of the selected IN endpoint. This indicates that the data in
the buffer is valid and can be sent to the host, when the next IN token is received. For
a double-buffered endpoint this command switches the current FIFO for CPU access.
Remark: For special aspects of the control IN endpoint see Section 9.5.
Code (Hex): 61 to 6F — validate endpoint buffer (control IN, endpoint 1 to 14)
Transaction — none
12.2.5 Clear Endpoint Buffer
This command unlocks and clears the buffer of the selected OUT endpoint, allowing
the reception of new packets. Reception of a complete packet causes the Buffer Full
flag of an OUT endpoint to be set. Any subsequent packets are refused by returning a
NAK condition, until the buffer is unlocked using this command. For a double-buffered
endpoint this command switches the current FIFO for CPU access.
Remark: For special aspects of the control OUT endpoint see Section 9.5.
ISP1181A
Full-speed USB peripheral controller
Code (Hex): 70, 72 to 7F — clear endpoint buffer (control OUT, endpoint 1 to 14)
Transaction — none
12.2.6 Check Endpoint Status
This command is used to check the status of the selected endpoint FIFO without
clearing any status or interrupt bits. The command accesses the Endpoint Status
Image Register, which contains a copy of the Endpoint Status Register. The bit
allocation of the Endpoint Status Image Register is shown in Table 33.
Code (Hex): D0 to DF — check status (control OUT, control IN, endpoint 1 to 14)
Transaction — write/read 1 byte
Table 33: Endpoint Status Image Register: bit allocation
Table 34: Endpoint Status Image Register: bit description
BitSymbolDescription
7EPSTALThis bit indicates whether the endpoint is stalled or not
(1 = stalled, 0 = not stalled).
6EPFULL1A logic 1 indicates that the secondary endpoint buffer is full.
5EPFULL0A logic 1 indicates that the primary endpoint buffer is full.
4DATA_PIDThis bit indicates the data PID of the next packet
Table 34: Endpoint Status Image Register: bit description
BitSymbolDescription
3OVERWRITEThis bit is set by hardware, a logic 1 indicating that a new Setup
2SETUPTA logic 1 indicates that the buffer contains a Setup packet.
1CPUBUFThis bit indicates which buffer is currently selected for CPU
0-reserved
12.2.7 Acknowledge Setup
This command acknowledges to the host that a SETUP packet was received. The
arrival of a SETUP packet disables the Validate Buffer and Clear Buffer commands
for the control IN and OUT endpoints. The microcontroller needs to re-enable these
commands by sending an Acknowledge Setup command, see Section 9.5.
This command returns the status of the last transaction of the selected endpoint, as
stored in the Error Code Register. Each new transaction overwrites the previous
status information. The bit allocation of the Error Code Register is shown in Table 35.
Code (Hex): A0 to AF — read error code (control OUT, control IN, endpoint 1 to 14)
Transaction — read 1 byte
5-reserved
4 to 1ERROR[3:0]Error code. For error description, see Table 37.
0RTOKA logic 1 indicates that data was received or transmitted
successfully.
Table 37: Transaction error codes
Error code
(Binary)
0000no error
0001PID encoding error; bits 7 to 4 are not the inverse of bits 3 to 0
0010PID unknown; encoding is valid, but PID does not exist
0011unexpected packet; packet is not of the expected type (token, data, or
0100token CRC error
0101data CRC error
0110time-out error
0111babble error
1000unexpected end-of-packet
1001sent or received NAK (Not AcKnowledge)
1010sent Stall; a token was received, but the endpoint was stalled
1011overflow; the received packet was larger than the available buffer space
1100sent empty packet (ISO only)
1101bit stuffing error
1110sync error
1111wrong (unexpected) toggle bit in DATA PID; data was ignored
Description
acknowledge), or is a SETUP token to a non-control endpoint
…continued
12.3.2 Unlock Device
This command unlocks the ISP1181A from write-protection mode after a ‘resume’. In
‘suspend’ state all registers and FIFOs are write-protected to prevent data corruption
by external devices during a ‘resume’. Also,theregister access for reading is possible
only after the ‘Unlock Device’ command is executed.
After waking up from ‘suspend’ state, the firmware must unlock the registers and
FIFOs via this command, by writing the unlock code (AA37H) into the Lock Register
(8-bit bus: lower byte first). The bit allocation of the LockRegister is given in Table 38.
15 to 0UNLOCK[15:0] Sending data AA37H unlocks the internal registers and FIFOs
for writing, following a ‘resume’.
12.3.3 Write/Read Scratch Register
This command accesses the 16-bit Scratch Register, which can be used by the
firmware to save and restore information, for example, the device status before
powering down in ‘suspend’ state. The register bit allocation is given in Table 40.
Table 41: Scratch Information Register: bit description
BitSymbolDescription
15-reserved; must be logic 0
14 to 8SFIRH[6:0]Scratch Information Register (high byte)
7 to 0SFIRL[7:0]Scratch Information Register (low byte)
12.3.4 Read Frame Number
This command returns the frame number of the last successfully received SOF. It is
followedbyreading one or two bytes from the FrameNumber Register,containing the
frame number (lower byte first). The Frame Number Register is shown in Table 42.
Remark: After a bus reset, the value of the Frame Number Register is undefined.
Code (Hex): B4 — read frame number
Transaction — read 1 or 2 bytes
Table 42: Frame Number Register: bit allocation
Bit15141312111098
SymbolreservedSOFRH[2:0]
[1]
Reset
AccessRRRRRRRR
Bit76543210
SymbolSOFRL[7:0]
[1]
Reset
AccessRRRRRRRR
[1] Reset value undefined after a bus reset.
00000000
00000000
Table 43: Frame Number Register: bit description
BitSymbolDescription
15 to 11-reserved
10 to 8SOFRH[2:0]SOF frame number (upper byte)
7 to 0SOFRL[7:0]SOF frame number (lower byte)
Table 44: Example of Frame Number Register access (8-bit bus width)
A0PhaseBus linesByte #Description
1commandD[7:0]-command code (B4H)
0dataD[7:0]0frame number (lower byte)
0dataD[7:0]1frame number (upper byte)
Table 45: Example of Frame Number Register access (16-bit bus width)
A0PhaseBus linesWord #Description
1commandD[7:0]-command code (B4H)
D[15:8]-ignored
0dataD[15:0]0frame number
12.3.5 Read Chip ID
This command reads the chip identification code and hardware version number. The
firmware must check this information to determine the supported functions and
features. This command accesses the Chip ID Register, which is shown in Table 46.
15 to 8CHIPIDH[7:0] chip ID code (81H)
7 to 0CHIPIDL[7:0]silicon version (41H, with 41H representing the BCD encoded
version number)
12.3.6 Read Interrupt Register
This command indicates the sources of interrupts as stored in the 4-byte Interrupt
Register. Each individual endpoint has its own interrupt bit. The bit allocation of the
Interrupt Register is shown in Table 48. Bit BUSTATUS is used to verify the current
bus status in the interrupt service routine. Interrupts are enabled via the Interrupt
Enable Register, see Section 12.1.5.
While reading the interrupt register, read all the 4 bytes completely.
31 to 24-reserved
23 to 10EP14 to EP1A logic 1 indicates the interrupt source(s): endpoint 14 to 1.
9EP0INA logic 1 indicates the interrupt source: control IN endpoint.
8EP0OUTA logic 1 indicates the interrupt source: control OUT endpoint.
7BUSTATUSIt monitors the current USB bus status (0 = awake,
1 = suspend).
6-reserved
5PSOFA logic 1 indicates that an interrupt is issued every 1 ms
because of the Pseudo SOF; after 3 missed SOFs ‘suspend’
state is entered.
4SOFA logic 1 indicates that a SOF condition was detected.
3EOTA logic 1 indicates that an internal EOT condition was generated
by the DMA Counter reaching zero.
2SUSPNDA logic 1 indicates that an ‘awake’ to ‘suspend’ change of state
was detected on the USB bus.
1RESUMEA logic 1 indicates that a ‘resume’ state was detected.
0RESETA logic 1 indicates that a bus reset condition was detected.
…continued
Figure 8 shows the interrupt logic of the ISP1181A. Each of the indicated USB events
is logged in a status bit of the Interrupt Register. Corresponding bits in the Interrupt
Enable Register determine whether or not an event will generate an interrupt.
Interrupts can be masked globally by means of the INTENA bit of the Mode Register
(see Table 19).
The active level and signalling mode of the INT output is controlled by the INTPOL
and INTLVL bits of the Hardware Configuration Register (see Table 21). 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, EOT and SOF are cleared upon reading the Interrupt
Register.The endpoint bits (EP0OUT to EP14) are cleared by reading the associated
Endpoint Status Register.
Bit BUSTATUS follows the USB bus status exactly, allowing the firmware to get the
current bus status when reading the Interrupt Register.
SETUP and OUT token interrupts are generated after ISP1181A has acknowledged
the associated data packet. In bulk transfer mode, the ISP1181A 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 Interrupt
Enable Register. If a Start-Of-Frame is lost, PSOF interrupts are generated every
1 ms. This allows the firmware to keep data transfersynchronized with the host. After
3 missed SOF events the ISP1181A 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.
The ISP1181A is powered from a single supply voltage, ranging from 4.0 V to 5.5 V.
An integrated voltage regulator provides a 3.3 V supply voltage for the internal logic
and the USB transceiver. This voltage is available at pin V
external pull-up resistor on USB connection D+. See Figure 9.
The ISP1181A can also be operated from a 3.0 V to 3.6 V supply, as shown in
Figure 10. In this case, the internal voltage regulator is disabled and pin V
be connected to VCC.
ISP1181A
Full-speed USB peripheral controller
for connecting an
reg(3.3)
must
reg(3.3)
ISP1181A
V
V
CC(3.3)
V
V
reg(3.3)
CC
4.0 V to 5.5 V
ref
004aaa026
ISP1181A
V
V
CC(3.3)
V
V
reg(3.3)
CC
ref
3.0 V to 3.6 V
004aaa027
Fig 9. ISP1181A with a 4.0 V to 5.5 V supply.Fig 10. ISP1181A with a 3.0 V to 3.6 V supply.
15. Crystal oscillator and LazyClock
The ISP1181A has a crystal oscillator designed for a 6 MHz parallel-resonant crystal
(fundamental). A typical circuit is shown in Figure 11. Alternatively, an external clock
signal of 6 MHz can be applied to input XTAL1, while leaving output XTAL2 open.
CLKOUT
ISP1181A
XTAL2
XTAL1
18 pF
6 MHz
18 pF
004aaa028
Fig 11. Typical oscillator circuit.
The 6 MHz oscillator frequency is multiplied to 48 MHz by an internal PLL. This
frequency is used to generate a programmable clock output signal at pin CLKOUT,
ranging from 3 MHz to 48 MHz.
In ‘suspend’ state the normal CLKOUT signal is not available, because the crystal
oscillator and the PLL are switched off to save power. Instead, the CLKOUT signal
can be switched to the LazyClock frequency of 100 kHz ± 50 %.
The oscillator operation and the CLKOUT frequency are controlled via the Hardware
Configuration Register, as shown in Figure 12. The following bits are involved:
• CLKRUN switches the oscillator on and off
• CLKDIV[3:0] is the division factor determining the normal CLKOUT frequency
• NOLAZY controls the LazyClock signal output during ‘suspend’ state.
When ISP1181A enters ‘suspend’ state (by setting and clearing bit GOSUSP in the
Mode Register), outputs SUSPEND and CLKOUT change state after approximately
2 ms delay. When NOLAZY = 0, the clock signal on output CLKOUT does not stop,
but changes to the 100 kHz ± 50 % LazyClock frequency.
When resuming from ‘suspend’ state by a positive pulse on input WAKEUP, output
SUSPEND is cleared and the clock signal on CLKOUT is restarted after a 0.5 ms
delay. The timing of the CLKOUT signal at ‘suspend’ and ‘resume’ is given in
Figure 13.
GOSUSP
WAKEUP
LAZYCLOCK
enable
100 (±50 %) kHz
MGS775
1.8 to 2.2 ms
SUSPEND
CLKOUT
If enabled, the 100 kHz ± 50 % LazyClock frequency will be output on pin CLKOUT during ‘suspend’ state.
0.5 ms
PLL circuit stable
3 to 4 ms
MGS776
Fig 13. CLKOUT signal timing at ‘suspend’ and ‘resume’.
The ISP1181A has an internal power-on reset (POR) circuit. Input pin RESET can be
directly connected to VCC. The clock signal on output CLKOUT starts 0.5 ms after
power-on and normally requires 3 to 4 ms to stabilize.
The triggering voltage of the POR circuit is 2.0 V nominal. A POR is automatically
generated when VCC goes below the trigger voltage for a duration longer than 50 µs.
ISP1181A
Full-speed USB peripheral controller
POR
(1)
V
CC
> 50 µs
≤ 350 µs
t
1
2.0 V
0 V
t1: clock is running
t2: BUS_CONF pins are sampled
t3: registers are accessible
(1) Supply voltage (5 Vor 3.3 V), connected externally to pin RESET.
1 ms
t
2
1 ms
t
3
MGT026
Fig 14. Power-on reset timing.
A hardware reset disables all USB endpoints and clears all ECRs, except for the
control endpoint which is fixed and always enabled. Section 9.3 explains how to
(re-)initialize the endpoints.
Table 54: Static characteristics: analog I/O pins (D+, D−)
VCC= 3.3 V±10 % or 5.0 V±10 %; V
GND
=0V; T
=−40°Cto+85°C; unless otherwise specified.
amb
[1]
SymbolParameterConditionsMinTypMaxUnit
Input levels
V
DI
V
CM
differential input sensitivity|V
differential common mode
− V
I(D+)
|0.2--V
I(D−)
includes VDI range0.8-2.5V
voltage
V
IL
V
IH
LOW-level input voltage--0.8V
HIGH-level input voltage2.0--V
Output levels
V
OL
V
OH
LOW-level output voltageRL= 1.5 kΩ to +3.6 V--0.3V
HIGH-level output voltageRL=15kΩ to GND2.8-3.6V
Leakage current
I
LZ
OFF-state leakage current--±10µA
Capacitance
C
IN
transceiver capacitancepin to GND--20pF
Resistance
R
PU
[2]
Z
DRV
Z
INP
pull-up resistance on D+SoftConnect = ON1-2kΩ
driver output impedancesteady-state drive29-44Ω
input impedance10--MΩ
Termination
V
TERM
[3]
termination voltage for
upstream port pull-up (R
PU
)
3.0
[4]
-3.6V
[1] D+ is the USB positive data pin; D− is the USB negative data pin.
[2] Includes external resistors of 22 Ω±1 % on both D+ and D−.
[3] This voltage is available at pin V
[4] In ‘suspend’ mode the minimum voltage is 2.7 V.
21.2 Interfacing ISP1181A with an H8S/2357 microcontroller
This section gives a summary of the ISP1181A interface with a H8S/2357 (or
compatible) microcontroller. Aspects discussed are: interrupt handling, address
mapping, DMA and I/O port usage for suspend and remote wake-up control. A typical
interface circuit is shown in Figure 31.
21.2.1 Interrupt handling
• ISP1181A: program the Hardware Configuration register to select an active LOW
• H8S/2357: program the IRQ Sense Control Register (ISCRH and ISCRL) to
21.2.2 Address mapping in H8S/2357
The H8S/2357 bus controller partitions its 16 Mbyte address space into eight areas
(0 to 7) of 2 Mbyte each. The bus controller will activate one of the outputs CS0 to
CS7 when external address space for the associated area is accessed.
The ISP1181A can be mapped to any address area, allowing easy interfacing when
the ISP1181A is the only peripheral in that area. If in the example circuit for bus
configuration mode 0 (see Figure 31) the ISP1181A is mapped to address FFFF08H
(in area 7), output CS7 of the H8S/2357 can be directly connected to input CS of the
ISP1181A.
ISP1181A
Full-speed USB peripheral controller
level for output INT (INTPOL = 0, see Table 20)
specify low-level sensing for the IRQ input.
The external bus specifications, bus width, number of access states and number of
program wait states can be programmed for each address area. The recommended
settings of H8S/2357 for interfacing the ISP1181A are:
• 8-bit bus in Bus Width Control Register (ABWCR)
• enable wait states in Access State Control Register (ASTCR)
• 1 program wait state in the Wait Control Register (WCRH and WCRL).
21.2.3 Using DMA
The ISP1181A can be configured for several methods of DMA with the H8S/2357 and
other devices. The interface circuit in Figure 31 shows an example of the ISP1181A
working with the H8S/2357 in single-address DACK-only DMA mode. External
devices are not shown.
For single-address DACK-only mode, firmware must program the following settings:
• ISP1181A:
– program the DMA Counter register with the total transfer byte count
– program the Hardware Configuration Register to select active level LOW for
DREQ and DACK
– select the target endpoint and transfer direction
– select DACK-only mode and enable DMA transfer.
In the interface circuit of Figure 31 pin P1.1 of the H8S/2357 is configured as a
general purpose output port. This pin drives the ISP1181A’s WAKEUP input to
generate a remote wake-up.
The H8S/2357 has 3 registers to configure port 1: Port 1 Data Direction Register
(P1DDR), Port 1 Data Register (P1DR) and Port 1 Register (PORT1). Only registers
P1DDR and P1DR must be configured, register PORT1 is only used to read the
actual levels on the port pins.
• H8S/2357:
22. Test information
The dynamic characteristics of the analog I/O ports (D+ and D−) as listed in Table 56,
were determined using the circuit shown in Figure 33.
ISP1181A
Full-speed USB peripheral controller
– select pin P1.1 to be an output in register P1DDR
– program the desired bit value for P1.1 in register P1DR.
test point
D.U.T
Load capacitance:
CL= 50 pF (full-speed mode)
Speed:
full-speed mode only: internal 1.5 kΩ pull-up resistor on D+
24.1 Introduction to soldering surface mount packages
This text gives a very brief insight to a complex technology. A more in-depth account
of soldering ICs can be found in our
Packages
There is no soldering method that is ideal for all surface mount IC packages. Wave
soldering can still be used for certain surface mount ICs, but it is not suitable for fine
pitch SMDs. In these situations reflow soldering is recommended. In these situations
reflow soldering is recommended.
24.2 Reflow soldering
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. Driven by legislation and
environmental forces the worldwide use of lead-free solder pastes is increasing.
ISP1181A
Full-speed USB peripheral controller
Data Handbook IC26; Integrated Circuit
(document order number 9398 652 90011).
Several methods exist for reflowing; for example, convection or convection/infrared
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 to 270 °C depending on solder
paste material. The top-surface temperature of the packages should preferably be
kept:
• below 225 °C (SnPb process) or below 245 °C (Pb-free process)
– for all BGA, HTSSON..T and SSOP..T packages
– for packages with a thickness ≥ 2.5 mm
– for packages with a thickness < 2.5 mm and a volume ≥ 350 mm3 so called
thick/large packages.
• below240 °C (SnPb process) or below 260 °C (Pb-free process) forpackageswith
a thickness < 2.5 mm and a volume < 350 mm3 so called small/thin packages.
Moisture sensitivity precautions, as indicated on packing, must be respected at all
times.
24.3 Wave soldering
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):
• For packages with leads on four sides, the footprint must be placed at a 45° angle
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 is cured.
Typical dwell time of the leads in the wave ranges from 3 to 4 seconds at 250 °C or
265 °C, depending on solder material applied, SnPb or Pb-free respectively.
A mildly-activated flux will eliminate the need for removal of corrosive residues in
most applications.
ISP1181A
Full-speed USB peripheral controller
– larger than or equal to 1.27 mm, the footprintlongitudinal 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.
to the transport direction of the printed-circuit board. The footprint must
incorporate solder thieves downstream and at the side corners.
24.4 Manual soldering
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.
24.5 Package related soldering information
Table 61: Suitability of surface mount IC packages for wave and reflow soldering
[1] For more detailed information on the BGA packages refer to the
(AN01026); order a copy from your Philips Semiconductors sales office.
[2] All surface mount (SMD) packages are moisture sensitive. Dependinguponthemoisture content, the
maximum temperature (withrespect to time) and body size ofthepackage, 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
[3] These transparent plastic packages are extremely sensitive to reflow soldering conditions and must
[4] These packages are not suitable for wave soldering. On versions with the heatsink on the bottom
[5] If wave soldering is considered, then the package must be placed at a 45° angle to the solder wave
[6] Wave soldering is suitable for LQFP, QFP and TQFP packages with a pitch (e) larger than 0.8 mm; it
[7] Wave soldering is suitable for SSOP, TSSOP, VSO and VSOP packages with a pitch (e) equal to or
[8] Image sensor packages in principle shouldnot be soldered. They aremountedin sockets or delivered
[9] Hot bar soldering or manual soldering is suitable for PMFP packages.
ISP1181A
Full-speed USB peripheral controller
on no account be processed through more than one soldering cycle or subjected to infrared reflow
soldering with peak temperatureexceeding 217 °C ± 10 °C measured in theatmosphereof the reflow
oven. The package body peak temperature must be kept as low as possible.
side, thesolder cannot penetrate betweentheprinted-circuit board and the heatsink.Onversions with
the heatsink on the top side, the solder might be deposited on the heatsink surface.
direction. The package footprint must incorporate solder thieves downstream and at the side corners.
is definitely not suitable for packages with a pitch (e) equal to or smaller than 0.65mm.
larger than 0.65 mm; it is definitely not suitable for packages with a pitch (e) equal to or smaller than
0.5 mm.
pre-mounted on flex foil. However, the image sensor package can be mounted by the client on a flex
foil by using a hot bar soldering process. The appropriate soldering profile can be provided on
request.
• Section 11 “Suspend and resume”: updated the complete section
• Section 12.1.4 “Write/Read Hardware Configuration”: changed bit name from CKDIV to
CLKDIV
• Table 32 “Endpoint Status Register: bit description”: changed the description for bit 7
from “The endpoint automatically resumes upon reception of a SETUP token.” to “The
endpoint is automatically unstalled upon reception of a SETUP token.”
• Section 12.2.3 “Stall Endpoint/Unstall Endpoint”: updated second and third paragraphs:
– second paragraph: changed “A stalled control endpoint automatically resumes when
it receives a SETUP token, regardless of the packet content.” to “A stalled control
endpoint is automatically unstalled when it receives a SETUP token, regardless of
the packet content.”
– third paragraph: changed “When a stalled endpoint resumes (either by the Unstall
Endpoint command or by receiving a SETUP token), it is also re-initialized.”to“When
a stalled endpoint is unstalled (either by the Unstall Endpoint command or by
receiving a SETUP token), it is also re-initialized.”
• Created a separate section for “Recommended operating conditions”
IObjective dataDevelopmentThis data sheet contains data from the objective specification for product development. Philips
IIPreliminary dataQualificationThis data sheet contains datafrom the preliminaryspecification. Supplementary datawill be published
IIIProduct dataProductionThis data sheet contains data from the product specification. Philips Semiconductors reserves the
[1] Please consult the most recently issued data sheet before initiating or completing a design.
[2] The product status of the device(s) described in this data sheet may have changed since this data sheet was published. The latest information is available on the Internet at
URL http://www.semiconductors.philips.com.
[3] For data sheets describing multiple type numbers, the highest-level product status determines the data sheet status.
[1]
Product status
27. 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 60134). 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.
[2][3]
Definition
Semiconductors reserves the right to change the specification in any manner without notice.
at alater date. Philips Semiconductors reserves the right to change the specificationwithout notice, in
order to improve the design and supply the best possible product.
right to makechanges at any time in order to improve the design, manufacturing and supply. Relevant
changes will be communicated via a Customer Product/Process Change Notification (CPCN).
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 in the products - including circuits, standard cells, and/or
software - described or contained herein in order to improve design and/or
performance. When the product is in full production (status ‘Production’),
relevant changes will be communicated via a Customer Product/Process
Change Notification (CPCN). Philips Semiconductors assumes no
responsibility or liability for the use of any of these products, conveys no
licence or title under any patent, copyright, or mask work right to these
products, and makesno representations or warranties that these productsare
free frompatent, copyright,or mask workright infringement, unlessotherwise
specified.
29. Trademarks
28. 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
ACPI — is an open industry specification for PC power management,
co-developed by Intel Corp., Microsoft Corp. and Toshiba
GoodLink — is a trademark of Koninklijke Philips Electronics N.V.
OnNow — is a trademark of Microsoft Corp.
SoftConnect — is a trademark of Koninklijke Philips Electronics N.V.
Zip — is a registered trademark of Iomega Corp.
Contact information
For additional information, please visit http://www.semiconductors.philips.com.
For sales office addresses, send e-mail to: sales.addresses@www.semiconductors.philips.com.Fax: +31 40 27 24825
All rights are reserved. Reproduction in whole or in part is prohibited without the prior
written consent of the copyright owner.
The information presented in this document does not form part of any quotation or
contract, is believed to be accurate and reliable and may be changed without notice. No
liability will be accepted by the publisher for any consequence of its use. Publication
thereof does not convey nor imply any license under patent- or other industrial or
intellectual property rights.
Date of release: 08 December 2004Document order number: 9397 750 13959
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.