The ISP1181 is a Universal Serial Bus (USB) interface device which complies with
Universal Serial Bus Specification Rev. 1.1
communication capacity to microcontroller or microprocessor-based systems. The
ISP1181 communicates with the system’s microcontroller or microprocessor through
a high-speed general-purpose parallel interface.
The fully autonomous Direct Memory Access (DMA) operation - auto download, auto
repeat, auto execution - removes the need for the device to re-enable or re-initialize
the DMA operation every time.
The modular approachto implementing a USB interface deviceallows the designer to
select the optimum system microcontroller from the wide variety available.The ability
to re-use 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.
. It provides full-speed USB
2.Features
The ISP1181 is ideally suited for application in many personal computer peripherals,
such as printers, scanners, external mass storage (zip drive) devices and digital still
cameras. It offers an immediate cost reduction for applications that currently use
c
c
SCSI implementations.
■ Complies with
specifications
■ High performance USB interface device with integrated Serial Interface Engine
(SIE), FIFO memory, transceiver and 3.3 V voltage regulator
■ Interrupt endpoint can be configured in ‘rate feedback’ mode
■ 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 with integrated PLL for low EMI
Universal Serial Bus Specification Rev. 1.1
and most Device Class
Page 2
Philips Semiconductors
■ Controllable LazyClock (24 kHz) output during ‘suspend’
■ Software controlled connection to the USB bus (SoftConnect™)
■ Good USB connection indicator that blinks with traffic (GoodLink™)
■ Clock output with programmable frequency (up to 48 MHz)
■ Complies with the ACPI™, OnNow™ and USB power management requirements
■ Internal power-on and low-voltage reset circuit, with possibility of a software reset
■ Operation over the extended USB bus voltage range (4.0 to 5.5 V) with 5 V
■ Operating temperature range −40 to +85 °C
■ 8 kV in-circuit ESD protection for lower cost of external components
■ Full-scan design with high fault coverage
■ Available in a TSSOP48 package.
3.Applications
■ Personal digital assistant (PDA)
■ Digital camera
■ Communication device, e.g.
■ Printer
■ Scanner.
ISP1181
Full-speed USB interface
tolerant I/O pads
◆ router
◆ modem
4.Ordering information
Table 1:Ordering information
Type numberPackage
NameDescriptionVersion
ISP1181DGGTSSOP48Plastic thin shrink small outline package; 48 leads; body width 6.1 mmSOT362-1
9397 750 06896
Objective specificationRev. 01 — 13 March 20002 of 69
D−4AI/OUSB D− connection (analog)
D+5AI/OUSB D+ connection (analog)
V
BUS
GL7OGoodLink LED indicator output (open-drain, 8 mA); the LED
WAKEUP8Iwake-up input (edge triggered, LOW to HIGH); generates a
SUSPEND9O‘suspend’ state indicator output (4 mA); used as power switch
EOT10IEnd-Of-Transfer input (programmable polarity, see Table 23);
DREQ11ODMA request output (4 mA; programmable polarity, see
DACK12IDMA acknowledge input (programmable polarity, see
SDWR13IDMA write strobe input; used only in bus configuration
SDRD14IDMA read strobe input; used only in bus configuration
INT15Ointerrupt output; programmable polarity (active HIGH or LOW)
READY16OI/O ready output; a LOW level indicates that ISP1181 is
BUS_CONF117Ibus configuration selector; see Table 3
BUS_CONF018Ibus configuration selector; see Table 3
DATA1519I/Obit 15 of D[15:0]; bi-directional data line (slew-rate controlled
DATA1420I/Obit 14 of D[15:0]; bi-directional data line (slew-rate controlled
[1]
ISP1181
Full-speed USB interface
PinType Description
1-supply voltage (3.0 to 5.5 V)
3-regulated supply voltage (3.3 V ± 10%) from internal
regulator; used to connect decoupling capacitor and pull-up
resistor on D+ line;
Remark: Cannot be used to supply external devices.
6I V
sensing input
BUS
is default ON, blinks OFF upon USB traffic; to connect an
LED use a 330 Ω series resistor;
remote wake-up from ‘suspend’ state
control output (active LOW) for powered-off application or as
resume signal to the CPU (active HIGH) for powered-on
application
used by the DMA controller to force the end of a DMA transfer
by the ISP1181
Table 23); signals to the DMA controller that the ISP1181
wants to start a DMA transfer
Table 23); used by the DMA controller to signal the start of a
DMA transfer requested by the ISP1181
mode 1 (separate PIO and DMA ports)
mode 1 (separate PIO and DMA ports)
and signalling (level or pulse); see Table 23
processing a previous command or data and is not ready for
the next PIO command or data transfer; a HIGH level signals
that ISP1181 will complete a PIO data transfer; applies only
to a PIO port or a PIO port shared with a DMA port
output, 4 mA)
output, 4 mA)
9397 750 06896
Objective specificationRev. 01 — 13 March 20005 of 69
ALE42Iaddress latch enable input; a HIGH-to-LOW transition latches
CS43Ichip select input
RESET44Ireset input (Schmitt trigger); a LOW level produces an
CLKOUT45Oprogrammable clock output (2 mA)
GND46-ground supply
XTAL247Ocrystal oscillator output (6 MHz); connect a fundamental
XTAL148Icrystal oscillator input (6 MHz); connect a fundamental
[1]
PinType Description
the level on pin AD0 as address information in a multiplexed
address/data bus configuration; must be tied LOW (connect
to DGND) for a separate address/data bus configuration
asynchronous reset; connect to V
(internal POR circuit)
parallel-resonant crystal; leave this pin open when using an
external clock source on pin XTAL1
parallel-resonant crystal or an external clock source (leaving
pin XTAL2 is unconnected)
ISP1181
Full-speed USB interface
for power-on reset
CC
[1] Symbol names with an overscore (e.g. NAME) represent active LOW signals.
7.Functional description
The ISP1181 is a full-speed USB interface device 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 ISP1181 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. Interrupt IN endpoints can be
configured in rate-feedback mode.
The ISP1181 requires a single supply voltage of 3.0 to 5.5 V and has an internal
3.3 V voltage regulator for powering the analog USB transceiver. It supports
bus-powered operation.
The ISP1181 operates on a 6 MHz oscillator frequency.A programmable clock output
is available up to 48 MHz. During ‘suspend’ state the 24 kHz LazyClock frequency
can be output.
7.1 Analog transceiver
The transceiver is compliant with
interfaces directly with the USB cable through external termination resistors.
9397 750 06896
Objective specificationRev. 01 — 13 March 20007 of 69
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 high-speed USB
devices) HIGH through a 1.5 kΩ pull-up resistor. In the ISP1181 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.
ISP1181
Full-speed USB interface
The ISP1181 will check for USB V
established. V
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 VSEvoltage
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.
sensing is provided through pin V
BUS
availability before the connection can be
BUS
.
BUS
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 ISP1181 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 ISP1181 the LED will blink off for 100 ms. During ‘suspend’
state the LED will remain off.
This feature provides a user-friendly indicator 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 therefor help to reduce field support and hotline overhead.
A register bit can be set to stop the GoodLink LED blinking in traffic (see Table 20).
The LED indicator will then be permanently on.
7.6 Bit clock recovery
The bit clock recovery circuit recovers the clock from the incoming USB data stream
using a 4× over-sampling principle. It is able to track jitter and frequency drift as
specified by the
9397 750 06896
Objective specificationRev. 01 — 13 March 20008 of 69
A 5 V to 3.3 V voltage regulator is integrated on-chip to supply the analog transceiver
and internal logic. This voltage is available at pin V
pull-up resistor on the D+ line. Alternatively, the ISP1181 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 ISP1181 appears as a
memory device with an 8/16-bit data bus and an 1-bit address bus. The ISP1181
supports both multiplexed and non-multiplexed address and data buses.
The ISP1181 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.
ISP1181
Full-speed USB interface
to supply an external 1.5 kΩ
reg(3.3)
8.Modes of operation
The ISP1181 has four bus configuration modes, selected via pins BUS_CONF1 and
BUSCONF0:
Mode 016-bit I/O port shared with 8-bit or 16-bit DMA port
Mode 1separate 8-bit I/O port and 8-bit DMA port
Mode 28-bit I/O port shared with 8-bit or 16-bit DMA port
Mode 3reserved.
The bus configurations for each of these modes are given in Table 3. Typical interface
circuits for each mode are given in Section 20.1.
Table 3:Bus configuration modes
ModeBUS_CONF[1:0]PIO widthDMA widthDescription
DMAWD = 0DMAWD = 1
000D[15:0]D[7:0];D[15:0]multiplexed address/data on pin AD0;
busis shared by 16-bit I/O port and 8-bit
or 16-bit DMA port
101D[7:0]D[15:8]illegalmultiplexed address/data on pin AD0;
bus has separate I/O port (8-bit) and
DMA port (8-bit)
210D[7:0]D[7:0]D[15:0]multiplexed address/data on pin AD0;
bus is shared by 8-bit I/O port and 8-bit
or 16-bit DMA port
311reservedreservedreservedreserved
9397 750 06896
Objective specificationRev. 01 — 13 March 20009 of 69
Each USB device is logically composed of several independent endpoints. An
endpoint acts as a terminus of a communication flow between the host and the
device. At design time each endpoint is assigned a unique number (endpoint
identifier, see Table 4). The combination of the device address (given by the host
during enumeration), the endpoint number and the transfer direction allows each
endpoint to be uniquely referenced.
The ISP1181 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.
ISP1181
Full-speed USB interface
Table 4:Endpoint access and programmability
Endpoint
identifier
064 (fixed)noyesnocontrol OUT
064 (fixed)noyesnocontrol IN
1programmablesupportedsupportedsupportedprogrammable
2programmablesupportedsupportedsupportedprogrammable
3programmablesupportedsupportedsupportedprogrammable
4programmablesupportedsupportedsupportedprogrammable
5programmablesupportedsupportedsupportedprogrammable
6programmablesupportedsupportedsupportedprogrammable
7programmablesupportedsupportedsupportedprogrammable
8programmablesupportedsupportedsupportedprogrammable
9programmablesupportedsupportedsupportedprogrammable
10programmablesupportedsupportedsupportedprogrammable
11programmablesupportedsupportedsupportedprogrammable
12programmablesupportedsupportedsupportedprogrammable
13programmablesupportedsupportedsupportedprogrammable
14programmablesupportedsupportedsupportedprogrammable
[1] IN: input for the USB host (ISP1181 transmits); OUT: output from the USB host (ISP1181 receives).
[2] The data flow direction is determined by bit EPDIR in the Endpoint Configuration Register.
[3] The total amount of FIFO storage allocated to enabled endpoints must not exceed 2462 bytes.
FIFO size (bytes)Double
buffering
I/O mode
access
DMA mode
access
Endpoint type
[1]
[1]
9397 750 06896
Objective specificationRev. 01 — 13 March 200010 of 69
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:
•
•
•
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.
endpoint enable bit (FIFOEN)
size bits of an enabled endpoint (FFOSZ[3:0])
isochronous bit of an enabled endpoint (FFOISO).
256 bytes
rate feedback mode
320 bytes
rate feedback mode
384 bytes
rate feedback mode
512 bytes
rate feedback mode
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
(512 bytes for non-isochronous FIFOs).
Table 6 shows an example of a configuration fitting in the maximum available 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 device hardware and is
transparent to the user.
9397 750 06896
Objective specificationRev. 01 — 13 March 200011 of 69
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
9.3 Endpoint initialization
In response to the standard USB request Set Interface,the firmware must program all
16 ECRs of the ISP1181 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.
Logical size
(bytes)
ISP1181
Full-speed USB interface
Endpoint description
When reset by hardware or via the USB bus, the ISP1181 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.
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 packetlength and packet data can be read from
ISP1181 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 ISP1181 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 buffer and 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.
9397 750 06896
Objective specificationRev. 01 — 13 March 200012 of 69
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.
10. DMA transfer
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 ISP1181 supports two methods:
•
•
The ISP1181 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 ISP1181 can be interleaved with normal I/O mode access to other endpoints.
ISP1181
Full-speed USB interface
8237 compatible mode: based on the DMA subsystem of the IBM personal
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
DACK-only mode: based on the DMA implementation in some embedded RISC
processors, which has a single address space for both memory and I/O.
The following features are supported:
Single-cycle or burst transfers (up tot 16 bytes per cycle)
short/empty packet
Programmable signal levels on pins DREQ, DACK and EOT
•
Automatic DMA counter reload and transfer restart following EOT.
•
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 22). The pin functions for this mode are shown in
Table 8.
Table 8:8237 compatible mode: pin functions
SymbolDescriptionI/OFunction
DREQDMA requestOISP1181 requests a DMA transfer
DACKDMA acknowledgeIDMA controller confirms the transfer
EOTend of transferIDMA controller terminates the transfer
RDread strobeIinstructs ISP1181 to put data on the bus
WRwrite strobeIinstructs ISP1181 to get data from the 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 ISP1181 in 8237 compatible DMA mode is given in Figure 3.
The 8237 has two control signals for each DMA channel: DRQ (DMA Request) and
DACK (DMA Acknowledge). General control signals are HRQ (Hold Request), HLDA
(Hold Acknowledge) and EOP (End-Of-Process). The bus operation is controlled via
MEMR (Memory Read), MEMW (Memory Write), IOR (I/O read) and IOW (I/O write).
dth
DATA1 to DATA15
AD,
ISP1181
DREQ
DACK
RD
WR
RAM
Fig 3. ISP1181 in 8237 compatible DMA mode.
MEMR
MEMW
DMA
CONTROLLER
8237
DREQHRQ
DACK
IOR
IOW
HLDA
CPU
HRQ
HLDA
MGS778
9397 750 06896
Objective specificationRev. 01 — 13 March 200014 of 69
The following example shows the steps which occur in a typical DMA transfer:
1. ISP1181 receives a data packet in one of its endpoint FIFOs; the packet must be
2. ISP1181 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 ISP1181 that it will start a DMA transfer.
7. TheISP1181 now places the byte or word to be transferredon the data bus lines,
8. The8237 waits one DMA clock period and then de-asserts MEMW and IOR. This
9. The ISP1181 de-asserts the DREQ signal to indicate to the 8237 that DMA is no
10. The 8237 de-asserts the DACK output indicating that the ISP1181 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
ISP1181
Full-speed USB interface
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.
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 ISP1181 that the data on the bus lines has been transferred.
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 aboveprocess 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 22). The pin functions for this mode are shown in
Table 9. A typical example of ISP1181 in DACK-only DMA mode is given in Figure 4.
Table 9:DACK-only mode: pin functions
SymbolDescriptionI/OFunction
DREQDMA requestOISP1181 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
9397 750 06896
Objective specificationRev. 01 — 13 March 200015 of 69
In DACK-only mode the ISP1181 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.
ISP1181
Full-speed USB interface
dth
Fig 4. ISP1181 in DACK-only DMA mode.
ISP1181DMA
DREQ
DACK
AD,
DATA1 to DATA15
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 26):
An external End-Of-Transfer signal occurs on input EOT
•
The internal DMA Counter Register reaches zero (CNTREN = 1)
•
A short/empty 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
MGS779
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 (even if it is smaller than the maximum packet size) will be sent to
the USB host at the next IN token.
DMA Counter Register zero: An EOT from the DMA Counter Register is enabled by
setting bit CNTREN in the DMA Configuration Register. The ISP1181 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 reaches zero an EOTcondition
is generated and the DMA operation stops.
Short/empty packet: Normally, the transfer byte count must be set via a control
endpoint before any DMA transfer takes place. When a short/empty packet has been
enabled as EOT indicator (SHORTP = 1), the transfer size is determined by the
presence of a short/empty packet in the data. This mechanism permits the use of a
fully autonomous data transfer protocol.
9397 750 06896
Objective specificationRev. 01 — 13 March 200016 of 69
When reading from an OUT endpoint, reception of a short/empty packet at an OUT
token will stop the DMA operation after transferring the data bytes of this packet.
When writing to an IN endpoint, a short packet transferred at an IN token will stop the
DMA operation after all bytes have been transferred. If the number of bytes in the
buffer is zero, ISP1181 will automatically send an empty packet.
Table 10: Summary of EOT conditions for a bulk endpoint
EOT conditionOUT endpointIN endpoint
EOT inputEOT is activeEOT is active
DMA Counter Registercounter reaches zerocounter reaches zero
Short packetshort packet is received and
Empty packetempty packet is received and
DMAEN bit in DMA
Configuration Register
[1] If short/empty packet EOT is enabled (SHORTP = 1 in DMA Configuration Register) and DMA
Counter Register is zero.
Full-speed USB interface
counter reaches zero in the
transferred
transferred
DMAEN = 0DMAEN = 0
middle of the buffer
empty packet is automatically
appended when needed
ISP1181
[1]
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 26):
An external End-Of-Transfer signal occurs on input EOT
•
The internal DMA Counter Register reaches zero (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
10.4.3 DMA auto-restart
If the AUTOLD bit in the DMA Configuration Register is set, the DMA operation will
automatically restart when the last transfer has been completed. First the internal
DMA counter is reloaded from of the DMA Counter Register. Output DREQ is then
asserted to request a new DMA transfer for an IN endpoint, or when the buffer of an
OUT endpoint buffer has been filled.
9397 750 06896
Objective specificationRev. 01 — 13 March 200017 of 69
The ISP1181 detects a USB ‘suspend’ status in the following cases:
A J-state is present on the USB bus for 3 ms
•
V
•
•
ISP1181 will remain in ‘suspend’ state for at least 5 ms, before responding to external
wake-up events such as global resume, bus traffic, wake-up on CS or WAKEUP. The
typical timing is shown in Figure 5.
is lost (weak pull-up/down on D+ and D−)
BUS
SoftConnect is disabled by clearing bit SOFTCT in the Mode Register, with
external pull-ups disabled by EXTPUL = 0 in the Hardware Configuration Register.
In this situation ISP1181 is effectively disconnected from the USB bus.
ISP1181
Full-speed USB interface
handbook, full pagewidth
Fig 5. Typical suspend timing.
GOSUSP
WAKEUP
Bus-powered devices that are suspended must not consume more than 500 µA of
current. This is achieved by shutting down the power to system components or
supplying them with a reduced voltage.
ISP1181 can either be in powered-on or powered-off mode during ‘suspend’ state.
This is controlled by bit PWROFF in the Hardware Configuration Register. A full
explanation of these modes is given in Section 11.1.1 and Section 11.1.2.
The steps leading up to ‘suspend’ status are as follows:
1. Upon detection of a ‘wake-up’ to ‘suspend’ transition ISP1181 sets bit SUSPND
2. When the firmware detects a ‘suspend’ condition it must prepare all system
3. In the interrupt service routine the firmware must check the current status of the
suspend
>5 ms
start detection of
wake-up conditions
MGS949
in the Interrupt Register. This will generate an interrupt if bit IESUSP in the
Interrupt Enable Register is set.
components for ‘suspend’ state:
a. All signals connected to ISP1181 must enter appropriate states to meet the
power consumption requirements of ‘suspend’ state.
b. All input pins of ISP1181 must have a CMOS logic 0 or logic 1 level. Pin
settings differ for powered-on and powered-off application.
USB bus. When bit BUSTATUS in the Interrupt Register is logic 0, the USB bus
has left ‘suspend’ mode and the process must be aborted. Otherwise, the next
step can be executed.
9397 750 06896
Objective specificationRev. 01 — 13 March 200018 of 69
4. To meet the ‘suspend’ current requirements for a bus-powered device, the
5. When the firmware has set and cleared the GOSUSP bit in the Mode Register,
11.1.1 Powered-on application
In powered-on application (PWROFF = 0 in the Hardware Configuration Register) the
power supply of the CPU and other parts of the circuit is not switched off. The CPU is
normally placed in low-power mode. The SUSPEND output of ISP1181 is normally
HIGH and pulses LOW for 10 ms upon a ‘resume’ condition. This signal can be used
to wake up the CPU. The signal timing is shown in Figure 6.
ISP1181
Full-speed USB interface
internal clocks must be switched off by clearing bit CLKRUN in the Hardware
Configuration Register.
the ISP1181 enters ‘suspend’ state. In powered-off application, the ISP1181
asserts output SUSPEND and switches off the internal clocks after 2 ms.
handbook, full pagewidth
Fig 6. Suspend and resume timing for powered-on application.
GOSUSP
WAKEUP
0.5 ms10 ms
SUSPEND
In powered-on application ISP1181 drives its output pins, while the inputs are driven
by the application. Bi-directional pins are placed in three-state and driven HIGH or
LOW by the application. A summary of appropriate pin states is given in Table 12.
Table 12: Pin states in powered-on application
PinTypeAppropriate state
A0I/O (three-state)externally driven
DATA[15:0]I/O (three-state)depends on state of inputs
SUSPENDOISP1181 drives logic 1
WAKEUPIexternally driven to logic 1
INTO (three-state)ISP1181 drives logic 0 or logic 1
RESETIexternally driven to logic 1
CSIexternally driven to logic 0 or logic 1 (default: logic 1)
RDIexternally driven to logic 0 or logic 1 (default: logic 1)
WRIexternally driven to logic 1
XTAL1Iexternally driven to logic 1, if external oscillator is used
CLKOUTO (three-state)ISP1181 drives logic 0
[1]
to logic 0 or logic 1
RD and CS
MGS780
[1] ‘Externally driven’ refers to logic outside the ISP1181.
9397 750 06896
Objective specificationRev. 01 — 13 March 200019 of 69
The USB connections D+ and D− remain powered and logically connected to the
USB bus. If a crystal oscillator is used, powering down during ‘suspend’ is managed
by the internal logic of ISP1181. When using an external oscillator on pin XTAL1, a
stable logic 1 level must be applied during ‘suspend’ state.
Figure 7 shows a typical bus-powered modem application using ISP1181 in
powered-onmode. The SUSPEND output is connected to the reset input (RST) of the
8031 microcontroller via an external inverter.This allowsa ‘resume’ condition to wake
up the 8031 from power-down mode. The ISP1181 is woken up via the USB bus
(global resume) or by the ring detection circuit on the telephone line.
ISP1181
Full-speed USB interface
dth
USB
V
BUS
D+
D−
Fig 7. SUSPEND and WAKEUP signals in a powered-on modem application.
11.1.2 Powered-off application
In powered-off application (PWROFF = 1 in the Hardware Configuration Register) the
supply of the CPU and other parts of the circuit is removed during ‘suspend’ state.
The SUSPEND output is active HIGH during ‘suspend’ state, making it suitable as a
power switch control signal, e.g. for an external oscillator.
Input pins of ISP1181 are pulled to ground via the pin buffers. Outputs are made
three-state to prevent current flowing in the application. Bi-directional pins are made
three-state and must be pulled to ground externally by the application. The power
supply of external pull-ups must also be removed to reduce power consumption.
V
CC(5.0)
ISP1181
SUSPEND
WAKEUP
V
CC
8031
RST
RING DETECTION
LINE
MGS781
handbook, full pagewidth
GOSUSP
WAKEUP
2 ms0.5 ms
SUSPEND
MGS782
Fig 8. Suspend and resume timing for powered-off application.
9397 750 06896
Objective specificationRev. 01 — 13 March 200020 of 69
A0I/O (three-state)powered off; internally connected to ground (logic 0)
DATA[15:0]I/O (three-state)powered off; internally connected to ground (logic 0)
SUSPENDOISP1181 drives logic 1
WAKEUPIpowered off; internally connected to ground (logic 0)
INTO (three-state)powered off; internally connected to ground (logic 0)
RESETIexternally driven
CSIpowered off; internally connected to ground (logic 0)
RDIpowered off; internally connected to ground (logic 0)
WRIpowered off; internally connected to ground (logic 0)
XTAL1Ipowered off; internally connected to ground (logic 0)
CLKOUTO (three-state)ISP1181 drives logic 0
[1] ‘Externally driven’ refers to logic outside the ISP1181.
When external components are powered-off, it is possible that interface signals RD,
WR and CS have unknown values immediately after leaving ‘suspend’ state. To
prevent corruption of its internal registers, ISP1181 enables a locking mechanism
once suspend is enabled.
[1]
to logic 1
ISP1181
Full-speed USB interface
After wake-up from suspend’ state, all internal registers except the Unlock Register
are write-protected. A special unlock operation is needed to re-enable write access.
This prevents data corruption during power-up of external components.
Figure 9 shows a typical bus-powered modem application using ISP1181 in
powered-off mode. The SUSPEND output is used to switch off power to the
microcontroller and other external circuits during ‘suspend’ state. The ISP1181 is
woken up via the USB bus (global resume) or by the ring detection circuit on the
telephone line.
dth
Fig 9. SUSPEND and WAKEUP signals in a powered-off modem application.
USB
V
BUS
D+
D−
V
CC(5.0)
ISP1181
SUSPEND
WAKEUP
V
power
switch
CC
CONTROLLER
RING DETECTION
MICRO-
LINE
MGS783
9397 750 06896
Objective specificationRev. 01 — 13 March 200021 of 69
For both application modes (powered-on and powered-off) wake-up from ‘suspend’
state is initiated either by the USB host or by the application:
•
•
The steps of a wake-up sequence are as follows:
1. Theinternal oscillator and the PLL multiplier are re-enabled. When stabilized, the
2. The SUSPEND output is de-asserted and the RESUME bit in the Interrupt
3. Maximum 15 ms after starting the wake-up sequence the ISP1181 resumes its
4. Incase of a remote wake-up ISP1181 drives a K-state on the USB bus for10 ms.
5. Following the de-assertion of output SUSPEND, the application restores itself
6. After wake-up the internal registers of ISP1181 are write-protected to prevent
ISP1181
Full-speed USB interface
USB host: drives a K-state on the USB bus (global resume)
Application: remote wake-up via a HIGH level on input WAKEUP or a LOW level
on input CS (if enabled via bit WKUPCS in the Hardware Configuration Register).
clock signals are routed to all internal circuits of the ISP1181.
Register is set. This will generate an interrupt if bit IERESUME in the Interrupt
Enable Register is set.
normal functionality.
and other system components to normal operating mode.
corruption by inadvertent writing during power-up of external components. The
firmware must send an Unlock Device command to the ISP1181 to restore its full
functionality. See Section 12.3.2 for more details.
11.3 Control bits in suspend and resume
Table 14: Summary of control bits
RegisterBitFunction
InterruptSUSPNDa transition from ‘awake’ to ‘suspend’ state was
detected
BUSTATUSmonitors USB bus status (logic 1 = suspend);
used when interrupt is serviced
Interrupt EnableIESUSPenables output INT to signal ‘suspend’ state
ModeSOFTCTenables SoftConnect pull-up resistor to USB bus
GOSUSPa HIGH-to-LOW transition enables ‘suspend’
state
SNDRSUa HIGH-to-LOW transition enables sending a
10 ms resume signal (K-state)
Hardware
Configuration
Unlockallsending data AA37H unlocks the internal
EXTPULselects internal (SoftConnect) or external pull-up
resistor
WKUPCSenables wake-up on LOW level of input
PWROFFselects powered-off mode during ‘suspend’ state
registers for writing after a ‘resume’
CS
9397 750 06896
Objective specificationRev. 01 — 13 March 200022 of 69
The functions and registers of ISP1181 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 15.
A complete access consists of two phases:
1. Command phase: when address bit A0 = 1, the ISP1181 interprets the data on
the lower byte of the bus (bits D7 to D0) as a command code. Commands without
a data phase are executed immediately.
2. Data phase (optional): when address bit A0 = 0, the ISP1181 transfers the data
on the bus to or from a register or endpoint FIFO. Multi-byte registers are
accessed least significant byte/word first.
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.
ISP1181
Full-speed USB interface
Table 15: 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
Read Control IN ConfigurationEndpoint Configuration Register
[1] With N representing the number of bytes, the number of words for 16-bit bus width is: (N + 1) DIV 2.
[2] Validating an OUT endpoint buffer causes unpredictable behaviour of ISP1181.
[3] In 8-bit bus mode this command requires more time to complete than other commands. See Table 60.
[4] Clearing an IN endpoint buffer causes unpredictable behaviour of ISP1181.
[5] Reads a copy of the Status Register: executing this command does not clear any status bits or interrupt bits.
[6] In 8-bit mode, the upper byte is invalid.
[7] During isochronous transfer in 16-bit mode, because N ≤ 1023, the firmware must take care of the upper byte.
Error Code Register
endpoint 1 to 14
A0read 1 byte/word
A1read 1 byte/word
A2 to AFread 1 byte/word
[1]
[6]
[6]
[6]
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 ISP1181 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 16. 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
9397 750 06896
Objective specificationRev. 01 — 13 March 200025 of 69
Table 17: 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 18.
A USB bus reset sets the device address to 00H and enables the device.In response
to the standard USB request Set Address the firmware must issue a Write Device
Address command, followed by sending an empty packetto 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 ISP1181 Mode Register, which consists of
1 byte (bit allocation: see Table 19). In 16-bit bus mode the upper byte is ignored.
The Mode Register controls the DMA bus width, resume and suspend modes,
interrupt activity, GoodLink signalling and SoftConnect operation. It can be used to
enable debug mode, where all errors and Not Acknowledge (NAK) conditions will
generate an interrupt.
9397 750 06896
Objective specificationRev. 01 — 13 March 200026 of 69
0 and 2). A logic 0 selects 8-bit DMA bus width. Bus reset value:
unchanged.
6SNDRSUWriting a logic 1 followed by a logic 0 will generate an upstream
‘resume’ signal of 10 ms duration, after a 5 ms delay.
5GOSUSPWriting a logic 1 followed by a logic 0 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.
1DISGLBLA logic 1 disables GoodLInk LED blinking on USB traffic. The
LED will be continuously on (
enumeration. Bus reset value: unchanged.
0SOFTCTA logic 1 enables SoftConnect (see Section 7.4). This bit is
ignored if EXTPUL = 1 in the Hardware Configuration Register
(see Table 22). Bus reset value: unchanged.
[1]
[1]
0
GL = LOW) after successful
[1]
0
[1]
0
12.1.4 Write/Read Hardware Configuration
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 22. 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 23: Hardware Configuration Register: bit description
BitSymbolDescription
2PWROFFA logic 1 enables powering-off during ‘suspend’ state. Output
1INTLVLSelects the interrupt signalling mode on output INT (0 = level,
0INTPOLSelects INT signal polarity (0 = active LOW, 1= active HIGH).
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.
The command accesses the Interrupt Enable Register, which consists of 4 bytes.The
bit allocation is given in Table 24.
ISP1181
Full-speed USB interface
SUSPEND is configured as a power switch control signal for
external devices (HIGH during ‘suspend’). Bus reset value:
unchanged.
1 = pulsed). In pulsed mode an interrupt produces an 83 ms
pulse. See Section 13 for details. Bus reset value: unchanged.
Table 25: 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
5IENOSOFA logic 1 enables 1 ms interrupts upon loss of 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 ISP1181 and enables/disables DMA
transfers.The command accesses the DMA Configuration Register, which consists of
2 bytes. The bit allocation is given in Table 26. A bus reset will clear bits DMAEN and
AUTOLD (DMA and auto-restart disabled), all other bits remain unchanged.
Table 27: DMA Configuration Register: bit description
BitSymbolDescription
3DMAENWriting a logic 1 enables DMA transfer, a logic 0 forces the end
2AUTOLDA logic 1 enables automatic restarting of DMA transfers. This bit
1 to 0BURSTL[1:0]Selects the DMA burst length:
12.1.7 Write/Read DMA Counter
This command accesses the DMA Counter Register, which consists of 2 bytes. The
bit allocation is given in Table 28.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.
ISP1181
Full-speed USB interface
of an ongoing DMA transfer and generates an EOT interrupt.
Reading this bit indicates whether DMA is enabled (0 = DMA
stopped, 1 = DMA enabled). This bit is cleared by a bus reset.
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.
The internal DMA counter is automatically reloaded from the DMA Counter Register,
when DMA is re-enabled (DMAEN = 1) or upon completion of a DMA transfer, when
auto-restart is enabled (AUTOLD = 1). See Section 12.1.6 for more details.
This command resets the ISP1181 in the same wayas 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.
Remark: The IN bufferof an endpoint contains input data for the host, the OUT buffer
receives 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).
ISP1181
Full-speed USB interface
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 ISP1181 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 transferis 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 behaviour of ISP1181.
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 30. Examples of
endpoint FIFO access are given in Table 31 (8-bit bus) and Table 32 (16-bit bus).
9397 750 06896
Objective specificationRev. 01 — 13 March 200032 of 69
Table 32: Example of endpoint FIFO access (16-bit bus width)
A0PhaseBus linesWord #Description
1commandD[7:0]-command code (00H to 1FH)
D[15:8]-ignored
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 Write/Read Endpoint Status
This command is used to read the status of the endpoint FIFO or stall the endpoint by
writing. The command accesses the Endpoint Status Register, the bit allocation of
which is shown in Table 33.
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 re-stall it with the Write Endpoint Status command.
9397 750 06896
Objective specificationRev. 01 — 13 March 200033 of 69
When a stalled endpoint is unstalled (either by the Set Endpoint Status command or
by receiving a SETUP token), it is also re-initialized. This flushes the buffer: in and if it
is an OUT buffer it waits for a DATA 0 PID, if it is an IN buffer it writes a DATA 0 PID.
Code (Hex): 40 to 4F — write (control OUT, control IN, endpoint 1 to 14)
Code (Hex): 50 to 5F — read (control OUT, control IN, endpoint 1 to 14)
Transaction — write/read 1 byte
Table 33: Endpoint Status Register: bit allocation
Table 34: Endpoint Status Register: bit description
BitSymbolDescription
7EPSTALWriting a logic 1 will stall the endpoint. The endpoint is
automatically unstalled upon reception of a SETUP token.
Reading this 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.
4-reserved
3OVERWRITEThis bit is set by hardware, a logic 1 indicating that a new Setup
packet has overwritten the previous setup information, before it
was acknowledged or before 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 and wait fora new
Setup packet.
2SETUPTA logic 1 indicates that the buffer contains a Setup packet.
1CPUBUFThis bit indicates which buffer is currently selected for CPU
This command signals the presence of validdata fortransmission to the USB host, by
setting the Buffer Full flag of the selected IN endpoint. This indicates that the data in
the bufferis 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
9397 750 06896
Objective specificationRev. 01 — 13 March 200034 of 69
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 bufferis 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.
Code (Hex): 70, 72 to 7F — clear endpoint buffer (control OUT, endpoint 1 to 14)
Transaction — none
12.2.5 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 35.
Code (Hex): D0 to DF — check status (control OUT, control IN, endpoint 1 to 14)
ISP1181
Full-speed USB interface
Transaction — write/read 1 byte
Table 35: Endpoint Status Image Register: bit allocation
Table 36: 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.
4-reserved
3OVERWRITEThis bit is set by hardware, a logic 1 indicating that a new Setup
packet has overwritten the previous setup information, before it
was acknowledged or before 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 and wait fora new
Setup packet.
2SETUPTA logic 1 indicates that the buffer contains a Setup packet.
1CPUBUFThis bit indicates which buffer is currently selected for CPU
This command is acknowledges to the host that a Setup packet was received. It
re-enables the Validate Buffer and Clear Buffer commands for the control IN and
control OUT endpoints. These commands are disabled automatically when a Setup
packet is received, see Section 9.5.
Remark: The Acknowledge Setup command must be sent to both control endpoints
(IN and OUT).
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 37.
ISP1181
Full-speed USB interface
Code (Hex): A0 to AF — read error code (control OUT, control IN, endpoint 1 to 14)
Transaction — read 1 byte
7UNREADA logic 1 indicates that a new event occurred before the
previous status was read.
6DATA01Indicates the PID type of the last successfully received packet
(0 = DATA0 PID, 1 = DATA1 PID).
5-reserved
4 to 1ERROR[3:0]Error code. For error description, see Table 39.
0RTOKA logic 1 indicates that data was received or transmitted
successfully.
Table 39: 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
Description
acknowledge), or is a SETUP token to a non-control endpoint
9397 750 06896
Objective specificationRev. 01 — 13 March 200036 of 69
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
12.3.2 Unlock Device
This command unlocks the ISP1181 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’. Register access for reading is not blocked.
ISP1181
Full-speed USB interface
Description
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 Lock Register is given in Table 40.
This command accesses the 16-bit Scratch Register, which can be used by the
firmware to save and restore information, e.g. the device status before powering
down in ‘suspend’ state. The register bit allocation is given in Table 42.
Table 43: Scratch Information Register: bit description
BitSymbolDescription
15 to 8SFIRH[7: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
followedby reading one or two bytes from the Frame Number Register, containing the
frame number (lower byte first). The Frame Number Register is shown in Table 44.
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 45: 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 46: Example of Frame Number Register access (16-bit bus width)
A0PhaseBus linesWord #Description
1commandD[7:0]-command code (B4H)
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 47.
Table 48: Scratch Information Register: bit description
BitSymbolDescription
15 to 8CHIPIDH[7:0]Chip ID Register (high byte)
7 to 0CHIPIDL[7:0]Chip ID Register (low byte)
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 49. 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.
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
7BUSTATUSMonitors the current USB bus status (0 = awake, 1 = suspend).
6-reserved
5NOSOFA logic 1 indicates that an SOF was lost; interrupt is issued
every 1 ms; 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 EOTcondition 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,
9397 750 06896
Objective specificationRev. 01 — 13 March 200040 of 69
Figure 10 shows the interrupt logic of the ISP1181. 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 21).
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 23). Default
settings after reset are active LOW and level mode. When pulse mode is selected, a
pulse of 83 ns is generated when the OR-ed combination of all interrupt bits changes
from logic 0 to logic 1.
ISP1181
Full-speed USB interface
handbook, full pagewidth
interrupt register
interrupt enable
Fig 10. Interrupt logic.
RESET
SUSPND
RESUME
SOF
EP14
...
EP0IN
EP0OUT
EOT
register
IERST
IESUSP
IERESM
IESOF
IEP14
...
IEP0IN
IEP0OUT
IEEOT
.
.
.
.
.
.
.
.
.
.
.
.
device mode
register
INTENA
hardware configuration
register
INTLVL
INTPOL
PULSE
GENERATOR
1
0
INT
MGS772
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 ISP1181 has acknowledged
the associated data packet. In bulk transfer mode, the ISP1181 will issue interrupts
for every ACK received for an OUT token or transmitted for an IN token.
9397 750 06896
Objective specificationRev. 01 — 13 March 200041 of 69
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 loss of Start-Of-Frame (NOSOF) interrupt, enabled via bit IENOSOF in the
Interrupt Enable Register. If a Start-Of-Frame is lost, NOSOF interrupts are
generated every 1 ms. This allows the firmware to keep data transfer synchronized
with the host. After 3 missed SOF events the ISP1181 will enter ‘suspend’ state.
An alternative way of handling isochronous data transfer is to enable both the SOF
and the NOSOF interrupts and disable the interrupt for each isochronous endpoint.
14. Power supply
The ISP1181 is powered from a single supply voltage, ranging from 4.0 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 11.
The ISP1181 can also be operated from a 3.0 to 3.6 V supply, as shown in Figure 12.
In that case the internal voltage regulator is disabled and pin V
connected to VCC.
ISP1181
Full-speed USB interface
for connecting an
reg(3.3)
must be
reg(3.3)
handbook, halfpage
ISP1181
V
CC(5.0)
V
CC(3.3)
V
reg(3.3)
4.0 to 5.5 V
n.c.
MGS773
handbook, halfpage
ISP1181
V
CC(5.0)
V
CC(3.3)
V
reg(3.3)
3.0 to 3.6 V
MGS774
Fig 11. ISP1181 with a 4.0 to 5.5 V supply.Fig 12. ISP1181 with a 3.0 to 3.6 V supply.
15. Crystal oscillator and LazyClock
The ISP1181 has a crystal oscillator designed for a 6 MHz parallel-resonant crystal
(fundamental). A typical circuit is shown in Figure 13. Alternatively, an external clock
signal of 6 MHz can be applied to input XTAL1, while leaving output XTAL2 open.
handbook, halfpage
CLKOUT
ISP1181
XTAL2
XTAL1
18 pF
6 MHz
18 pF
MGS777
Fig 13. 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 to 48 MHz.
9397 750 06896
Objective specificationRev. 01 — 13 March 200042 of 69
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 24 kHz.
The oscillator operation and the CLKOUT frequency are controlled via the Hardware
Configuration Register, as shown in Figure 14. The following bits are involved:
•
•
•
ISP1181
Full-speed USB interface
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.
handbook, full pagewidth
hardware
configuration
register
CLKRUN
.
.
.
CKDIV[3:0
.
.
.
NOLAZY
SUSPEND
]
Fig 14. Oscillator and LazyClock logic.
When ISP1181 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 clocksignal on output CLKOUTdoes not stop,but
changes to the 24 kHz LazyClock frequency.
When resuming from ‘suspend’ state by a positive pulse on input WAKEUP, output
SUSPEND is cleared and the clock signal on CLKOUT restarted after a 0.5 ms delay.
The timing of the CLKOUT signal at ‘suspend’ and ‘resume’ is given in Figure 15.
enable
6 MHz
4
enable
PLL 8×XTAL OSC
LAZYCLOCK
enable
48 MHz
24 kHz
÷ (N + 1)
N
1
CLKOUT
0
NOLAZY
MGS775
9397 750 06896
Objective specificationRev. 01 — 13 March 200043 of 69
If enabled, the 24 kHz LazyClock frequency will be output on pin CLKOUT during ‘suspend’ state.
Fig 15. CLKOUT signal timing at ‘suspend’ and ‘resume’.
16. Power-on reset
The ISP1181 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.
0.5 ms
PLL circuit stable
3 to 4 ms
MGS776
handbook, full pagewidth
V
CC
2.0 V
0 V
(1)
POR
> 50 µs
≤ 350 µs
t
1
t1: clock is running
t2: BUS_CONF pins are sampled
t3: registers are accessible
(1) Supply voltage (5 V or 3.3 V), connected externally to pin RESET.
Fig 16. 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 55: Static characteristics: analog I/O pins (D+, D−)
VCC= 4.0 to 5.5 V; V
GND
=0V; T
=−40 to+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.6V--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.1-1.9kΩ
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.
9397 750 06896
Objective specificationRev. 01 — 13 March 200046 of 69
address hold after RD HIGH3-3-ns
address setup before RD LOW0-0-ns
data outputs high-impedance
CS HIGH
after
-3-3ns
RD pulse width25-25-ns
data valid after RD LOW-22-22ns
read interval after CS HIGH
read interval after CS HIGH
output READY HIGH before
[1]
READY pulsing22-22-ns
[1]
READY = HIGH90-180-ns
0- 0- ns
RD HIGH
read cycle duration-90-180ns
address hold after WR HIGH3-3-ns
address setup before WR LOW0-0-ns
write interval after CS HIGH
write interval after CS HIGH
[2]
READY pulsing22-22-ns
[2]
READY = HIGH90/180
[3]
-180-ns
WR pulse width22-22-ns
chip deselect after WR HIGH0-0-ns
data setup before WR HIGH5-5-ns
data hold after WR HIGH3-3-ns
write cycle duration-90/180
[3]
-180ns
ALE pulse width20-20-ns
address setup before ALE
10-10-ns
LOW
address hold after ALE LOWreading010010ns
writing0-0-ns
[1] Measured from CS going HIGH to CS and RD both going LOW.
[2] Measured from CS going HIGH to CS and WR both going LOW.
[3] Commands Acknowledge Setup, Clear Buffer, Validate Buffer and Write Endpoint Configuration require 180 ns to complete.
9397 750 06896
Objective specificationRev. 01 — 13 March 200050 of 69
Write command + write data (see Figure 25 and Figure 26)
T
cy(WC-WD)
cycle time for write command,
then write data
T
cy(WD-WD)
T
cy(WD-WC)
cycle time for write data90-180-ns
cycle time for write data, then
write command
Write command + read data (see Figure 27 and Figure 28)
T
cy(WC-RD)
cycle time for write command,
then read data
T
cy(RD-RD)
T
cy(RD-WC)
cycle time for read data90-180-ns
cycle time for read data, then
write command
[1]
Min
100
MaxMin
[2]
-200-ns
90-180-ns
[2]
100
-200-ns
90-180-ns
[1]
Max
[1] If the access cycle time is less than specified, the READY signal will be LOW until the internal processing has finished.
[2] Commands Acknowledge Setup, Clear Buffer, Validate Buffer and Write Endpoint Configuration require 180 ns to complete.
handbook, full pagewidth
DATA
WR
CS
command
T
cy(WC-WD)
T
cy(WD-WD)
datadata
MGT022
Fig 25. Write command + write data cycle timing.
9397 750 06896
Objective specificationRev. 01 — 13 March 200053 of 69
starts from DACK or RD/WR going LOW, whichever occurs later.
ASRP
(2) The RD/WR signals are not used in 8237 compatible DMA mode.
(3) The EOT condition is considered valid if DACK, RD/WR and EOT are all active (= LOW).
20.2 Interfacing ISP1181 with an H8S/2357 microcontroller
This section gives a summary of the ISP1181 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 35.
20.2.1 Interrupt Handling
•
•
20.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 ISP1181 can be mapped to any address area, allowing easy interfacingwhen the
ISP1181 is the only device in that area. If in the example circuit for bus configuration
mode 0 (see Figure 35) the ISP1181 is mapped to address FFFF08H (in area 7),
output CS7 of the H8S/2357 can be directly connected to input CS of the ISP1181.
ISP1181
Full-speed USB interface
ISP1181: program the Hardware Configuration register to select an active LOW
level for output INT (INTPOL = 0, see Table 22)H8S/2357: program the IRQ Sense Control Register (ISCRH and ISCRL) to
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 ISP1181 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).
•
20.2.3 Using DMA
The ISP1181 can be configured for several methods of DMA with the H8S/2357 and
other devices. The interface circuit in Figure 35 shows an example of the ISP1181
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:
ISP1181:
•
– 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.
9397 750 06896
Objective specificationRev. 01 — 13 March 200061 of 69
In the interface circuit of Figure 35 pin P1.1 of the H8S/2357 is configured as a
general purpose output port. This pin drives the ISP1181’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.
For single
•
21. Test information
The dynamic characteristics of the analog I/O ports (D+ and D−) as listed in Table 57,
were determined using the circuit shown in Figure 38.
ISP1181
Full-speed USB interface
H8S/2357:
– select pin P1.1 to be an output in register P1DDR
– program the desired bit value for P1.1 in register P1DR.
handbook, halfpage
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+
Fig 38. Load impedance for D+ and D− pins.
test point
22 Ω
15 kΩ
CL =
50 pF
MGS784
9397 750 06896
Objective specificationRev. 01 — 13 March 200062 of 69
Objective specificationRev. 01 — 13 March 200063 of 69
Page 64
Philips Semiconductors
23. Soldering
23.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 is not always suitable for surface mount ICs, or for printed-circuit boards
with high population densities. In these situations reflow soldering is often used.
23.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.
Several methods exist for reflowing; for example, infrared/convection heating in a
conveyor type oven. Throughput times (preheating, soldering and cooling) vary
between 100 and 200 seconds depending on heating method.
ISP1181
Full-speed USB interface
Data Handbook IC26; Integrated Circuit
(document order number 9398 652 90011).
Typical reflow peak temperatures range from 215 to 250 °C. The top-surface
temperature of the packages should preferable be kept below 230 °C.
23.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):
•
– larger than or equal to 1.27 mm, the footprint longitudinal axis is preferred to be
parallel to the transport direction of the printed-circuit board;
– smaller than 1.27 mm, the footprint longitudinal axis must be parallel to the
transport direction of the printed-circuit board.
The footprint must incorporate solder thieves at the downstream end.
For packages with leads on four sides, the footprint must be placed at a 45° angle
•
to the transport direction of the printed-circuit board. The footprint must
incorporate solder thieves downstream and at the side corners.
During placement and before soldering, the package must be fixed with a droplet of
adhesive. The adhesive can be applied by screen printing, pin transfer or syringe
dispensing. The package can be soldered after the adhesive is cured.
9397 750 06896
Objective specificationRev. 01 — 13 March 200064 of 69
Typical dwell time is 4 seconds at 250 °C. A mildly-activated flux will eliminate the
need for removal of corrosive residues in most applications.
23.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.
23.5 Package related soldering information
Table 63: Suitability of surface mount IC packages for wave and reflow soldering
[1] All surface mount (SMD) packages are moisture sensitive. Depending upon the moisture content, the
maximum temperature (with respect to time) and body size of the package,there is a risk that internal
or external package cracks may occur due to vaporization of the moisture in them (the so called
popcorn effect). For details, refer to the Drypack information in the
Circuit Packages; Section: Packing Methods
[2] These packages are not suitable for wavesoldering as a solder joint between the printed-circuit board
and heatsink (at bottom version) can not be achieved, and as solder may stick to the heatsink (on top
version).
[3] If wave soldering is considered, then the package must be placed at a 45° angle to the solder wave
direction. The package footprint must incorporate solder thieves downstream and at the side corners.
[4] Wave soldering is only suitable for LQFP, QFP and TQFP packages with a pitch (e) equal to or larger
than 0.8 mm; it is definitely not suitable for packages with a pitch (e) equal to or smaller than 0.65 mm.
[5] Wave soldering is only suitable for SSOP and TSSOP packages with a pitch (e) equal to or larger than
0.65 mm; it is definitely not suitable for packages with a pitch (e) equal to or smaller than 0.5mm.
.
Data Handbook IC26; Integrated
9397 750 06896
Objective specificationRev. 01 — 13 March 200065 of 69
Objective specificationDevelopmentThis data sheet contains the design target or goal specifications for product development. Specification may
change in any manner without notice.
Preliminary specification QualificationThis data sheet contains preliminary data, and supplementary data will be published at a later date. Philips
Semiconductors reserves the right to make changes at any time without notice in order to improve design and
supply the best possible product.
Product specificationProductionThis data sheet contains final specifications. Philips Semiconductors reserves the right to make changes at any
time without notice in order to improve design and supply the best possible product.
[1] Please consult the most recently issued data sheet before initiating or completing a design.
26. 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.
[1]
27. Disclaimers
Life support — These products are not designed for use in life support
appliances, devices, or systems where malfunction of these products can
reasonably be expected to result in personal injury. Philips Semiconductors
customers using or selling these products for use in such applications do so
at their own risk and agree to fully indemnify Philips Semiconductors for any
damages resulting from such application.
Right to make changes — Philips Semiconductors reserves the right to
make changes, without notice, in the products, including circuits, standard
cells, and/or software, described or contained herein in order to improve
design and/or performance. Philips Semiconductors assumes no
responsibility or liability for the use of any of these products, conveys no
licence or title under any patent, copyright, or mask work right to these
products, and makes no representations or warranties that these products
are free from patent, copyright, or mask work right infringement, unless
otherwise specified.
28. Trademarks
ACPI — is an open industry specification for PC power management,
co-developed by Intel Corp., Microsoft Corp. and Toshiba
GoodLink — is a trademark of Royal Philips Electronics
OnNow — is a trademark of Microsoft Corp.
SMBus — is a bus specification for PC power management, developed by
Intel Corp. based on the I
SoftConnect — is a trademark of Royal Philips Electronics
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: 13 March 2000Document order number: 9397 750 06896
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.