The ML60852 is a general purpose Universal Serial Bus (USB) device controller.
The ML60852 provde a USB serial interface engine, USB transceiver, FIFOs, control/status registers, application
interface circuit, and oscillation circuit thereby easily realizing a USB system. The ML60852 supports four types
of data transfer such as control transfer, bulk transfer, interrupt transfer and isochronous transfer, and also supports
five or six endpoints.
FEATURES
•
USB1.1 compliant
•
Supports full-speed (12 Mbps).
•
Supports four types of transfer; control transfer, bulk transfer, interrupt transfer, and isochronous transfer.
•
Endpoints: 5 to 6 endpoints
Control EP1
Bulk/interrupt EP3
Isochronous/bulk/interrupt EP1 or 2
•
Built-in FIFO for data storage
•
A two-layer configuration of FIFO for each of EP1, EP2, EP4, and EP5
•
DMA transfer is possible (EP1, EP2, EP4, and EP5).
•
Supports bus-powered device.
The suspend condition is automatically detected and the low-power mode is activated. Normal operation is
automatically restarted when the resume condition is detected.
•
Built-in USB transceiver circuit
•
V
=3.0 to 3.6 V
CC
•
Interface with 5 V circuit is possible. (Input: 5 V tolerant, output: TTL)
•
Built-in 12 MHz oscillation circuit
•
Package options:
44-pin plastic QFP or TQFP
56-pin plastic LGA
1/81
Page 2
PEDL60852-01
Semiconductor
1
ML60852
Endpoints and FIFOs
In the ML60852, it is possible to select by making appropriate register setting either the 5EP mode in which there
are five end points or the 6EP mode in which there are six end points. Although the transfer mode that can be used
by EP0 is fixed, it is possible to select either the bulk transfer mode or the interrupt transfer mode for the end points
EP1, EP2, and EP3, and one of the modes of isochronous, bulk, or interrupt transfer can be selected for EP4 and
EP5. In addition, it is possible to selectively set the direction of data transfer for EP1 to EP5.
5EP Mode6EP ModeEnd
point
EP0Reception 32
EP164x2Bulk/interrupt transfer
EP264x2Bulk/interrupt transfer
EP332
EP4512x2
EP5——256x2 (64x2)Isochronous/bulk/
FIFO
Capacity
Transmission 32
(64x2)
Transfer
mode
Control transferReception 32
(IN/OUT)
(IN/OUT)
Bulk/interrupt transfer
(IN/OUT)
Isochronous/bulk/
interrupt transfer
(IN/OUT)
RemarksFIFO
Capacity
Transmission 32
DMA
Possible
DMA
Possible
DMA
Possible
64x2Bulk/interrupt transfer
64x2Bulk/interrupt transfer
256x2 (64x2)Isochronous/bulk/
32
Transfer
mode
Control transfer
(IN/OUT)
(IN/OUT)
Bulk/interrupt transfer
(IN/OUT)
interrupt transfer
(IN/OUT)
interrupt transfer
(IN/OUT)
Remarks
DMA
Possible
DMA
Possible
DMA
Possible
DMA
Possible
FIFO Capacity: The unit is bytes.
Note 1: The selection between the 5EP mode and the 6EP mode is made by bit D2 of the register
SYSCON.
Note 2: EP3 permits rate feedback data sequence toggling.
Note 3: EP1, EP2, and EP3 are all mutually independent, and can be assigned for bulk transfer or
interrupt transfer individually. It is possible to set the maximum packet size up to 64 bytes (32
bytes for EP3) during both bulk transfer and interrupt transfer.
Note 4: It is possible to set EP4 and EP5 to one of the modes of isochronous transfer, bulk transfer, and
interrupt transfer. The maximum packet size can be up to 64 bytes when these end points are set
to bulk transfer.
Note 5: When using EP4 and EP5 in the isochronous transfer mode:
In the 5EP mode, the maximum packet size of EP4 is 512 bytes. EP5 cannot be used.
In the 6EP mode, the maximum packet size of both EP4 and EP5 is 256 bytes.
Notes: 1. 1.5 kΩ pull-up to 3.3 V on the D + data line.
tR
tF
and
2.
are measured from 10% to 90% of the data signal.
D+, D-
9/81
Page 10
Semiconductor
1
SIGNAL DESCRIPTIONS
USB Interface
SignalTypeAssertionDescription
USB data (Plus). This signal and the D- signal are the transmitted or
received data from/to USB Bus. The table below shows values and results
for these signals.
D+D-Result
D+I/O—
D-I/O—
USB Data (Minus). This signal and the D+ signal are the transmitted or
received data from/to USB Bus. The table above shows values and results
for these signals.
00Single end 0
01Differential "0"
10Differential "1"
11Undefined
PEDL60852-01
ML60852
Crystal Oscillator Interface
SignalTypeAssertionDescription
XINI—
XOUTO—
For internal oscillation, connect a crystal to XIN and XOUT.
For external oscillation, supply an external 12 MHz clock signal to XIN.
Set XOUT to be open.
10/81
Page 11
Semiconductor
1
Application Interface
SignalTypeAssertionDescription
D15: D8I/O—Upper byte (MSB) of data bus.
AD7: AD0I/O—
A6: A0I—Address when ADSEL is LOW.
CS
RD
WR
INTR
DREQ0
DREQ1
DACK0I(Note 2)
DACK1I(Note 2)
ALE/PUCTLI or OHIGH
ADSELI—
RESET
ILOW
ILOW
ILOW
O(Note 1)
O(Note 1)DMA Request. This signal requests the DMA0 to make a DMA transfer.
O(Note 1)DMA Request. This signal requests the DMA1 to make a DMA transfer.
ILOW
Lower byte (LSB) of data bus when ADSEL is LOW.
Address and lower byte of data bus are multiplexed when ADSEL is HIGH.
Chip Select. When this signal is asserted LOW, the ML60852 is selected
and ready to read or write data. This signal is invalid in single address
mode during DMA transfer.
Read Strobe. When this signal is asserted LOW, the Read instruction is
executed.
Write Strobe. When this signal is asserted LOW, the Write instruction is
executed.
Interrupt Request. When this signal is asserted, the ML60852 makes an
interrupt request to the application.
DMA Acknowledge Signal for
accessing FIFOs, without address bus setting.
DMA Acknowledge Signal for
accessing FIFO, without address bus setting.
When ADSEL is HIGH, the address and CS on AD7: AD0 are latched at the
trailing edge of this signal. D+ pull-up resistor connection output when
ADSEL is LOW.
V
potential when bit D3 of SYSCON register is “1”, and high-impedance
CC
when it is “0”.
When ADSEL is LOW, the address is input on A6: A0 and data is input on
AD7: AD0. When ADSEL is HIGH, address and data are multiplexed on
AD7: AD0.
System Reset. When this signal is asserted LOW, the ML60852 is reset.
When the ML60852 is powered on, this signal must be asserted for 1 µs or
more.
DREQ0
DREQ1
PEDL60852-01
ML60852
. This signal, when asserted, enables
. This signal, when asserted, enables
Notes: 1. The assertion can be set by using the assertion select register.
The default is LOW.
2. The assertion can be set by using the assertion select register.
The default is HIGH.
11/81
Page 12
PEDL60852-01
Semiconductor
1
ML60852
FUNCTIONAL DESCRIPTIONS
(1) USB Interface
The ML60852 is a USB device controller. The ML60852 provides the following functions which are bases for a
USB protocol. Therefore, the application can process a lot of its own functions.
•
Bit synchronization
•
Encoding and decoding NRZI signals.
•
Generating and detecting Sync bytes.
•
Bit stuffing
•
Generating and checking CRCs (CRC5, CRC16).
•
Encoding and decoding PID (packet identifier).
1. Decoding token.
2. Encoding and decoding handshake.
•
Generating and detecting SOP.
•
Enpacket (packing) and depacket (unpacking)
•
Comparing device addresses.
•
Storing 8-byte setup data from a host into the setup register.
•
Transmitting data in transmit FIFO.
•
Storing receive data into receive FIFO of the corresponding endpoint.
(2) USB Transfer Modes
The ML60852 supports four kinds of transfer modes such as control transfer mode , interrupt transfer mode, bulk
transfer mode, and isochronous transfer mode, which are specified by USB Standards.
(a) The control transfer mode is used to receive and respond to configurations and commands from a host, and to
exchange status information between the host and peripherals.
(b) The bulk transfer mode is used to transfer a lot of data in the limited service period when the band width of
USB bus becomes sufficient.
(c) The interrupt transfer mode is used to transfer a small amount of data unfreguently in the limited service period.
(d) The isochronous transfer mode is used to continuously transfer audio data, moving pictures data and other data.
12/81
Page 13
PEDL60852-01
Semiconductor
1
ML60852
(3) Endpoints and FIFOs
In the ML60852, it is possible to select, by making appropriate setting in the SYSCON register, the 5EP mode in
which there are five end points or the 6EP mode in which there are six end points. Although the transfer mode that
can be used by EP0 is fixed, it is possible to select either the bulk transfer mode or the interrupt transfer mode for the
end points EP1, EP2, and EP3, and one of the modes of isochronous, bulk, or interrupt transfer can be selected for
EP4 and EP5. In addition, it is possible to selectively set the direction of data transfer for EP1 to EP5.
5EP Mode6EP ModeEnd
point
EP0Reception 32
EP164x2B/Int
EP264x2B/Int
EP332B/Int
EP4512x2
EP5——256x2 (64x2)Iso/B/Int
FIFO
Capacity
Transmission 32
(64x2)
Transfer
mode
CReception 32
(IN/OUT)
(IN/OUT)
(IN/OUT)
Iso/B/Int
(IN/OUT)
RemarksFIFO
Capacity
Transmission 32
DMA
Possible
DMA
Possible
Rate32B/Int
DMA
Possible
256x2 (64x2)Iso/B/Int
Transfer
mode
Control transfer
64x2B/Int
(IN/OUT)
64x2B/Int
(IN/OUT)
(IN/OUT)
(IN/OUT)
(IN/OUT)
Remarks
DMA
Possible
DMA
Possible
Rate
DMA
Possible
DMA
Possible
FIFO Capacity: The unit is bytes.
Note: Transfer modes:
C = Control transfer
B = Bulk transfer
Int = Interrupt transfer
Iso = Isochronous transfer
Rate = Compatible with data sequence toggling of rate feedback.
13/81
Page 14
PEDL60852-01
Semiconductor
1
ML60852
(4) Operation of control transfer
(a) Setup stage
The setup token and 8 bytes of setup data are transmitted from the host. The ML60852 decodes the setup token,
and automatically stores the 8 bytes of setup data in the setup register. When this is completed normally, the
ML60852 returns ACK to the host.
The 8-byte setup data is the standard request code defined in Section 9.3 of the USB Standards, or a code of the
requests unique to each device class, etc. The request is decoded on the local MCU side.
(b) Data stage
If the request specified by the 8-byte setup data is also accompanied by transfer of parameter data from the host
to the device, the transfer is a control write transfer, and the OUT token and the data packet are transmitted
from the host. When these are received normally, the ML60852 stores the parameter data in the EP0 receive
FIFO and returns ACK to the host.
If the request is accompanied by transfer of parameter data from the device to the host, the transfer is a control
read transfer, and when the host sends the IN token, the ML60852 sends the parameter data that was already
stored beforehand in the EP0 transmit FIFO by the local MCU. When the host receives this normally, it returns
an ACK to the ML60852.
On the other hand, in the case of requests that do not contain any parameter data that need to be transmitted or
received, this data stage will not be present and the processing proceeds directly to the status stage from the
setup stage.
(c) Status stage
The status stage is a stage intended for reporting the status of the result of executing a request from the device
to the host. During a control write transfer or a control transfer without data, the IN token is sent by the host,
and the ML60852 returns a response to it. During a control read transfer, the OUT token and data of zero
length are sent by the host, and the ML60852 returns a response to it.
During the above control transfers, the local MCU need only read from or write to the 8-byte setup registers
mapped at 00h to 07h, the EP0 transmit FIFO mapped at 70h, and the EP0 receive FIFO mapped at 78h
according to the interrupt cause, and all other operations will be carried out automatically by the ML60852.
14/81
Page 15
PEDL60852-01
Semiconductor
1
ML60852
(5) Data packet transmission and reception procedure during bulk transfer and interrupt transfer modes
The ML60852 is normally used on the peripheral device side. In this method of use, the ML60852 is connected on
one side to the host via the USB bus and is connected on the other side via a parallel interface to the local
microcontroller (local MCU) inside the peripheral device.
The transfer of data is the major function in all types of transfer modes other than the control transfer mode. When
carrying out transfer of data packets between the ML60852 and the host, the following packet communication is
carried out via the USB bus for the data transfer of each packet.
(a) Token packet transfer (IN token or OUT token) from the host to the ML60852.
(b) Data packet transfer in the desired direction (from the host to the device or from the device to the host).
(c) Transfer of handshake packet in a direction opposite to that of the data packet.
When packet transfer is completed normally, an ACK packet is returned in step (c) and the operation proceeds
to the next packet transfer.
The ML60852 requests the local MCU to transmit or receive a packet of data by asserting the
INTR
pin. The
interrupt cause will be “packet ready”. The transmit packet ready interrupt is one that requests that the packet
of data to be transmitted be written in the transmit FIFO, and the receive packet ready interrupt is one that
requests the local MCU to read out the data that has been received and stored in the receive FIFO.
The above procedures of transferring one packet of data are explained below for transmission and reception
separately.
1) During transmission
The local MCU writes one packet of data that has to be transmitted in the transmit FIFO of the corresponding
EP in the ML60852, and sets the transmit packet ready bit of the corresponding EP status register of the
ML60852. When the host transmits the IN token packet to the ML60852 specifying the communication
method, etc., the ML60852 transmits to the host the data packet stored in the above transmit FIFO. When the
host receives one data packet normally, it returns the ACK packet to the ML60852. Consequently, the
ML60852 resets the transmit packet ready status, thereby completing the transfer of one data packet over the
USB bus. When the transmit packet ready status is reset, the ML60852 gives a request to the local MCU in
terms of a transmit packet ready interrupt thereby prompting the local MCU to write the next packet of data to
be transmitted.
2) During reception
The host sends to the ML60852 an OUT token followed by a data packet. The ML60852 stores the received
data packet in the receive FIFO of the corresponding EP. When it is confirmed that all the data packets have
been accumulated and that there is no error, the ML60852 returns an ACK packet to the host. At the same time,
the receive packet ready bit of the corresponding EP status register will also be set and a request is sent to the
local MCU in terms of an interrupt. Upon receiving this interrupt, the local MCU reads out the received data
from the ML60852 and resets the receive packet ready bit.
15/81
Page 16
PEDL60852-01
Semiconductor
1
ML60852
(6) Data packet transmission and reception procedure during isochronous transfer mode
Transfer of data is the major function in the isochronous transfermode. When carrying out isochronous transfer
between the ML60852 and the host, the following packet communications are carried out via the USB bus for the
data transfer of each packet.
(a) Token packet transfer (IN token or OUT token) from the host to the ML60852.
(b) Data packet transfer in the desired direction (from the host to the device or from the device to the host).
In the isochronous transfer mode, there is no handshaking that reports whether or not the packet transfer was
done normally.
The ML60852 requests the local MCU to send or receive packet data by asserting the
INTR
pin. The interrupt
cause is SOF. Upon receiving this interrupt, the local MCU writes the packet data into the transmit FIFO of the
EP set for transmission (ISO IN) in the isochronous transfer mode, or reads out data from the receive FIFO of
the EP set for reception (ISO OUT) in the isochronous transfer mode.
The above procedures of transferring one packet of data are explained below for transmission and reception
separately.
1) During transmission
The EP for ISO IN has a two-layer FIFO configuration. One FIFO is used for storing the packet data that is
written in by the MCU via the local bus. The other FIFO is used for transmitting the stored data to the USB bus
when an IN token is received. The roles of the two FIFOs are interchanged when an SOF packet is received.
Upon receiving an SOF interrupt, the local MCU writes the data to be transmitted during the next frame into the
corresponding transmit FIFO of the EP of the ML60852. When the host transmits an IN token packet, the
ML60852 transmits to the host the packet data written in the transmit FIFO during one frame before the current
frame.
2) During reception
The EP for ISO OUT has a two-layer FIFO configuration. One FIFO is used for storing the packet data that is
output to the local bus when the MCU reads the received packet data. The other FIFO is used for storing the
packet data received from the USB bus. The roles of the two FIFOs are interchanged when an SOF packet is
received.
Upon receiving an SOF interrupt, the local MCU reads out the data that has been received during the previous
frame from the corresponding receive FIFO of the EP of the ML60852. When the host transmits an OUT token
and a data packet to the ML60852, the ML60852 stores that received data packet in the receive FIFO, and that
data packet is read out by the local MCU during the next frame.
16/81
Page 17
PEDL60852-01
)
Semiconductor
1
ML60852
(7) Packets and packet sizes
The ML60852 packs the transmit data into packets and unpacks (restores to the original form) the received data.
The packed data that is recognized by the software client is a set of data consisting of one or more packets, and this
is called an I/O request (IRP).
Among the several packets in an IRP, all the packets other than the last packet are transferred with the maximum
packet size. Only the last packet can be transferred as a "short packet", that is, a packet whose size is less than the
maximum packet size.
I/O Request Packet (IRP
Packet
1
Packet
2
Packet
n-1
Packet
n
1 Packet
M Bytes
Maximum packet size
The ML60852 has payload registers corresponding to each end point, and it is possible to set the maximum packet
size for each end point in these registers. The maximum packet size should be within the capacity of the
corresponding FIFO, and can be set as follows:
(1) EP0 Receive packet size can be 32 bytes or less;
(2) EP0 Transmit packet size can be 32 bytes or less;
(3) EP1 Transmit/receive packet size can be 64 bytes or less;
(4) EP2 Transmit/receive packet size can be 64 bytes or less;
(5) EP3 Transmit/receive packet size can be 32 bytes or less;
(6) EP4 Bulk/interrupt transmit/receive packet size can be 64 bytes;
In the 5EP mode, the EP4 isochronous packet size can be 512 bytes or less;
In the 6EP mode, the EP4 isochronous packet size can be 256 bytes or less;
(7) In the 6EP mode, the EP5 bulk/interrupt packet size can be 64 bytes or less;
In the 6EP mode, the EP5 isochronous packet size can be 256 bytes or less.
On the USB bus, the separation between successive packets is distinguished by appending a special signal condition
called EOP (End of Packet) at the end of each packet. The appending of EOP during transmission and the detection
and removal of EOP during reception are carried out by the ML60852 automatically.
(1) At the time of transmission, the packet is deemed to have ended when the local MCU has completed writing the
required number of bytes of data in the transmit FIFO and has then asserted the transmit ready status bit. (The
actual addition of EOP is executed at the time of transmitting the data over the USB bus after waiting for the IN
token from the host.) The packet will be a short packet if the transmit packet ready status bit is asserted after
writing data with less number of bytes than the maximum packet size. In particular, by asserting the transmit
packet ready status bit without writing any data, it is possible to form a null packet whose data length is zero.
17/81
Page 18
PEDL60852-01
Semiconductor
1
ML60852
(2) At the time of reception, when an EOP is detected in the received data string, the ML608522 recognizes it as
the end of the received packet and asserts the receive packet ready status bit. The number of bytes in the
received packet is counted automatically by the receive byte count register (Note 1) corresponding to that end
point.
Note 1: Receive byte count register address: 58h to 5Dh and 74h to 75h.
(8) Interrupts
The ML60852 requests interrupts to the local MCU, etc., by asserting the -INTR pin. The interrupt causes are the
following:
(a) Setup ready for the 8-byte setup data
(b) EP0 receive packet ready
(c) EP0 transmit packet ready
(d) EP1 transmit/receive packet ready
(e) EP2 transmit/receive packet ready
(f) EP3 transmit/receive packet ready
(g) EP4 transmit/receive packet ready
(h) EP5 transmit/receive packet ready
(i) SOF
(j) USB Bus reset assert
(k) USB Bus reset de-assert
(l) Suspend
(m) Awake
Although there is only one
INTR
pin, the local MCU can identify the contents of the interrupt by reading out the
interrupt status register 1 (INTSTAT1) and the interrupt status register 2 (INTSTAT2). These interrupts can also be
masked dynamically by making individual settings in the interrupt enable register 1 (INTENBL1) and the interrupt
enable register 2 (INTENBL2).
The causes of the interrupts, their setting and resetting conditions, and the responses to them are described below.
The functions of the setup ready bit and the packet ready bit can, in some situations, be different from those
described here because of some special automatic operations done by the ML60852. Please see the descriptions of
the registers EP0STAT to EP5STAT for more details of such functions.
(1) Setup ready interrupt
OperationSource of operationDescription (conditions, responses, etc.)
Setup ready
interrupt generation
End of setup ready interrupt Local MCU (firmware)
ML60852
The setup ready bit (D2 of EP0STAT) is asserted when the
8-byte setup control data is received normally and has
been stored in the set of setup registers.
An interrupt is generated at this time if D1 of INTENBL1 has
been asserted.
→ The firmware can now read the set of setup registers.
After making the firmware read the 8-byte setup data, write
a “1” in bit D2 of EP0 status register (EP0STAT). This
causes the interrupt to be de-asserted.
The interrupt will not be de-asserted If a new 8-byte setup
data is received during this period. In this case, discard the
setup data that was being read at that time and read the
new 8-byte setup data.
18/81
Page 19
Semiconductor
1
(2) EP0 Receive packet ready interrupt
This is used mainly during the reception of a data packet in a control write transfer.
OperationSource of operationDescription (conditions, responses, etc.)
EP0 Receive packet ready
interrupt generation
End of EP0 receive
packet ready interrupt
ML60852The EP0 receive packet ready bit (D0 of EP0STAT) is
asserted during a control write transfer when the
processing has changed from the setup stage to the data
stage, and the ML60852 has detected EOP of the data
packet and has stored the data without error in the EP0
receive FIFO. The end of a packet is recognized when an
EOP has arrived in the cases of both full packets and short
packets.
An interrupt is generated at this time, if the EP0 receive
packet ready interrupt enable bit (D6 of INTENBL1) has
been asserted.
(EOP: End of packet)
Local MCU (firmware) In the case of EP0 reception, after the number of bytes of
the EP0 receive FIFO data indicated by the EP0 receive
byte count register (EP0RXCNT) has been read, write a “1”
to the EP0 receive packet ready bit (bit D0 of EP0STAT).
(This status is reset when a “1” is written in this bit.)
PEDL60852-01
ML60852
Note: A short packet is a packet with a number of bytes less than the maximum packet size.
19/81
Page 20
Semiconductor
1
(3) EP0 Transmit packet ready interrupt
This is used mainly during the transmission of a data packet in a control read transfer.
OperationSource of operationDescription (conditions, responses, etc.)
EP0 Transmit packet ready
interrupt generation
End of EP0 transmit
packet ready interrupt
ML60852The EP0 transmit packet ready bit (D1 of EP0STAT) is de-
asserted during a control read transfer when the
processing has changed from the setup stage to the data
stage, and it is possible to write the transmit data to the
FIFO.
At this time, an interrupt is generated if the EP0 transmit
packet ready interrupt enable bit (bit D7 of INTENBL1) has
been asserted.
For the second and subsequent packets, in addition to this
condition, before the interrupt is generated, it is necessary
for an ACK response to come from the host for the packet
that has just been sent.
Local MCU (firmware) In the case of EP0 transmission, after the one packet of the
EP0 transmit data has been written in EP0TXFIFO, write a
“1” into the EP0 transmit packet ready bit (bit D1 of
EP0STAT). This puts the ML60852 in a state in which it
can transmit the data (that is, it can transmit the data packet
when an IN token arrives), and the
at the same time.
Even when the number of bytes in the write data is less
than the maximum packet size, it is possible to transmit the
data by writing a “1” into the transmit packet ready status
bit. This makes it possible to transmit a short packet.
These interrupts are generated when the respective EP has received an appropriate data packet from the USB
bus and the local MCU can read that data.
OperationSource of operationDescription (conditions, responses, etc.)
Receive packet ready
interrupt generation
End of receive packet ready
interrupt
ML60852The receive packet ready bit (D0) of the corresponding EP
status register (EPnSTAT) is asserted during data
reception when the EOP of the data packet has been
received and the data has been stored without error in the
corresponding FIFO. The end of a packet is recognized
when an EOP has arrived in the cases of both full packets
and short packets.
An interrupt is generated at this time, if the corresponding
receive packet ready interrupt enable bit has been
asserted.
(EOP: End of packet)
Local MCU (firmware) After the number of bytes in the receive FIFO data
(EPnFIFO) indicated by the corresponding receive byte
count register (EPnRXCNT) has been read, write a “1” into
the receive packet ready bit D0 of the corresponding EP
status register (EPnSTAT). (This status is reset when a “1”
is written in this bit.)
These interrupts are generated when it is possible for the local MCU to write the data packet to be sent to the
USB bus from the corresponding EP.
OperationSource of operationDescription (conditions, responses, etc.)
Transmit packet ready
interrupt generation
End of transmit packet ready
interrupt
ML60852(1) In the case of bulk transfer and interrupt transfer
When the respective EP has been set for transmission,
the transmit packet ready bit of the corresponding EP
(bit D1 of EPnSTAT) is de-asserted when it is possible
to write the transmit data into the FIFO.
At this time, an interrupt is generated if the
corresponding EP transmit packet ready interrupt
enable bit (INTENBL1) has been asserted.
For the second and subsequent packets, in addition to
this condition, before the interrupt is generated, it is
necessary for an ACK response to come from the host
for the packet that has just been sent.
Local MCU (firmware) (1) In the case of bulk transfer and interrupt transfer
After the one packet of the corresponding EP transmit
data has been written in EPnTXFIFO, write a “1” into the
corresponding transmit packet ready bit (bit D1 of
EPnSTAT). This puts the ML60852 in a state in which it
can transmit the data and the
the same time.
Even when the number of bytes in the write data is less
than the maximum packet size, it is possible to end the
pocket transmission by writing a “1” into the transmit
packet ready status bit.
INTR
pin is de-asserted at
22/81
Page 23
PEDL60852-01
Semiconductor
1
ML60852
(6) SOF Interrupt
OperationSource of operationDescription (conditions, responses, etc.)
SOF Interrupt generationML60852When an SOF packet is detected on the USB bus.
End of SOF interruptLocal MCU (firmware) When a “1” is written in the corresponding bit of the
interrupt status register 2 (INTSTAT2).
(7) USB Bus reset assert interrupt
OperationSource of operationDescription (conditions, responses, etc.)
USB Bus reset assert
interrupt generation
End of USB bus reset assert
interrupt
ML60852The ML60852 automatically detects the condition when the
SE0 state continues for 2.5µs or longer at the D+ and Dpins.
→ Carry this out by firmware processing for bus reset.
Local MCU (firmware)
When a “1” is written in the corresponding bit of the
interrupt status register 2 (INTSTAT2).
(8) USB Bus reset de-assert interrupt
OperationSource of operationDescription (conditions, responses, etc.)
USB Bus reset de-assert
interrupt generation
End of USB bus reset
de-assert
ML60852When there is a recovery to the J state from the SE0 state
of 2.5µs or longer at the D+ and D- pins.
→ Carry this out by firmware processing for bus reset
release.
Local MCU (firmware) When a “1” is written in the corresponding bit of the
interrupt status register 2 (INTSTAT2).
23/81
Page 24
PEDL60852-01
Semiconductor
1
ML60852
(9) Suspend state interrupt
OperationSource of operationDescription (conditions, responses, etc.)
Suspend state
interrupt generation
End of suspend state
interrupt
ML60852When the idle condition persists for 3ms or more at the D+
and D- pins.
→ The internal oscillations in the ML60852 are stopped
automatically when the idle condition continues for an
additional 2ms after this interrupt has been generated. The
firmware can take steps to put the device in the power save
mode.
Local MCU (firmware) When a “1” is written in the corresponding bit of the
interrupt status register 2 (INTSTAT2).
(10) Awake interrupt
OperationSource of operationDescription (conditions, responses, etc.)
Awake interrupt generationML60852
End of awake interruptLocal MCU (firmware) When a “1” is written in the corresponding bit of the
When the Resume signal (the SE0 state of about 1344ns
immediately after the K state) is detected at the D+ and Dpins.
interrupt status register 2 (INTSTAT2).
24/81
Page 25
PEDL60852-01
Semiconductor
1
ML60852
(9) DMA (Direct Memory Access)
It is possible to carry out 8-bit wide or 16-bit wide DMA transfer for the bulk transfer of EP1, EP2, EP4, and EP5,
and for the isochronous transfer of EP4 and EP5. The data bus used is the following:
During 8-bit transfer: AD7 to AD0
During 16-bit transfer: D15 toD8, AD7 to AD0
It is possible to carry out DMA transfers over two channels, Channel 0 and Channel 1. Both demand transfer and
single transfer are supported. The settings of the DMA transfer mode and parameters are done using the DMA
control register and the DMA interval register described later in this manual.
In the demand transfer mode, the
possible. The
DREQ
pin is de-asserted when the transfer of all the data of the receive packets is completed by the
DREQ
pin is asserted when the reading or writing of a data packet becomes
external DMA controller. Therefore, other devices cannot access the local bus during DMA transfer.
On the other hand, in the single transfer mode, the
DREQ
pin is de-asserted at the end of transfer of the number of
bytes (or words) of one transfer, and the other devices can access the local bus during this period.
(10) Power-down
When the ML60852 detects the suspend state on the USB bus, it automatically stops the internal oscillations and
enters the power-down state. When the resume signal is detected on the USB bus, the oscillations are restarted
automatically and the power-down state is released.
25/81
Page 26
PEDL60852-01
Semiconductor
1
ML60852
(11) Operation of 2-layer structure FIFO during bulk transfer
The FIFOs of EP1 and EP2 have a 64 bytes x 2-layer structure. Also, when EP4 is assigned for bulk transfer, its
FIFO also has a 64-bytes x 2-layer structure. As a consequence, these FIFOs can temporarily store a maximum of
128 bytes of bulk transfer data.
(1) 2-Layer reception operation (“O” indicates the assert condition and “x” indicates de-assert condition)
In the case of 1→2→3→4→5a→6
In the case of 1→2→3→4→5b→6
1Start storing data in layer A of receptionxxxx
2Data of one packet has been stored.x
Start reception and storing of data in
3
layer B.
4Local MCU starts reading layer A.x
When the storing of packet in layer B is
5a
completed following the completion of
reading layer A.
When the reading of packet in layer A is
5b
completed following the completion of
storing data in layer B.
From 5a: Layer A has become empty.
6
From 5b: Layer B has become full.
7Starting reading layer B also.x
•
When one packet of receive data is stored in layer A of the FIFO and EOP is received, the ML60852 asserts the
packet ready bit of EPn and also asserts the
Layer A
64 bytes
INTR
pin. This makes it possible for the local MCU to read the
Layer B
64 bytes
Layer A
PKT
RDY
Layer B
PKT
RDY
xxxx
x
EPn
receive
PKT
RDY
x
INTR
receive data.
•
Subsequently, data can be received from the host, and the ML60852 switches the FIFO for storing to layer B.
•
When one packet of data described above has been read from layer A of the FIFO, make the local MCU reset the
receive packet ready status of EPn (by writing a “1” into bit D0 of EPnSTAT).
•
At the time the EPn receive packet ready status is reset, if the reception of layer B has not been completed, the
ML60852 resets the EPn receive packet ready status and de-asserts the
•
However, if the reception of layer B has been completed a the time the EPn receive packet ready status is reset,
INTR
pin.
the ML60852 rejects the request from the local MCU to reset the EPn receive packet ready status, and continues
to maintain the EPn receive packet ready status and the asserted condition of the
INTR
pin.
26/81
Page 27
PEDL60852-01
Semiconductor
1
ML60852
(2) 2-Layer transmission operation (“O” indicates the assert condition and “x” indicates de-assert condition)
In the case of 1→2→3→4→5a→6
In the case of 1→2→3→4→5b→6
1Layer A and layer B are both empty.xxx
2The local MCU starts writing into layer A.xxx
3Writing of one packet is completed.xx
The data of layer A is transmitted and
4
the next packet is written in layer B.
When layer A has become empty after
5a
the writing in layer B is completed.
When the writing in layer B has been
completed after layer A has become
5b
empty.
From 5a: Layer A has become empty.
6
From 5b: Layer B has become full.
7Transmission of layer B is also started.xx
•
If the EPn transmit packet ready interrupt enable bit of INTENBL1 has been asserted, the transmit FIFO is empty,
Layer A
64 bytes
Layer B
64 bytes
Layer A
PKT
RDY
Layer B
PKT
RDY
xx x
xx
EPn
transmit
PKT
RDY
xx
INTR
and EPn transmit packet ready bit is de-asserted, the EPn transmit packet ready interrupt is asserted. This makes
it possible to write the transmit data into the EPn transmit FIFO.
•
When the data of one packet is written in layer A FIFO, make the local MCU set the transmit packet ready status
(bit D1 of EPnSTAT). By setting the transmit packet ready status, it becomes possible to transmit data to the
host. At this time, since layer B is still empty, the
INTR
pin maintains the asserted condition, thereby indicating
that the next packet data can be written. In this case, although bit D1 of EPnSTAT remains in the '0' condition,
the ML60852 recognizes that transmission is possible from layer A and starts transmission when an IN token is
received from the host.
•
It is possible for the local MCU to write the next packet of transmit data in the layer B FIFO while the data in
layer A is being transmitted over the USB bus.
•
When the writing of the data to be transmitted in layer B has been completed, the local MCU sets the transmit
packet ready bit, and the
INTR
pin becomes de-asserted at this time if the transmission of layer A data has not
been completed (that is, the ACK message is received from the host and the transmit packet ready bit is reset).
The local MCU cannot yet write the subsequent packet.)
•
If the layer A becomes empty before layer B goes into the transmit enable condition and transmission is carried
out normally, the ACK response is received from the host. The
INTR
pin remains asserted, and the local MCU
can write data into layer A FIFO after writing into layer B FIFO.
•
The transmission of data in layer A is continued from the state 4a, and when layer A becomes empty and the
transmission is completed normally, the ACK response is received from the host, whereupon the ML60852
asserts the
INTR
pin thereby prompting the local MCU to write data into layer A.
x
27/81
Page 28
PEDL60852-01
Semiconductor
1
ML60852
(12) Error processing and retry operation
1) Error processing during transmission
When an error such as a CRC error is detected in the data transmitted by the ML60852, the host will not send
the ACK packet, and hence the ML60852 does not reset the transmit packet ready status, but waits while
retaining the current packet of data. The current packet of data is transmitted again when the next IN token is
received from the host.
2) Error processing during reception
When an error is detected in the data received over the USB bus, the ML60852 does not assert the interrupt
signal to the local MCU and will also not send any message to the host (leading to a timeout condition).
When the timeout condition is generated, the host recognizes that an error has occurred, and can take measures
such as re-transmitting the data, etc. In addition, since no interrupt request is generated, the local MCU will not
read the erroneous data.
28/81
Page 29
PEDL60852-01
Semiconductor
1
ML60852
(13) D+ Pull-up control
Immediately after the power is switched on, the device may not be able to receive the token sent from the host
because the preparations at the firmware level have not been completed. In this case, until the initialization at the
firmware level is completed, the D+ line of the USB connector (the D- line in the case of a low speed device) is
turned off, and the 1.5k pull-up resistor is turned on after the initialization has been completed. To do this, a switch
circuit that can be turned on or off by the local MCU is provided in series with the 1.5K resistor.
In the ML60852, although it is possible to provide such switch circuits externally, it is also possible to use the
internal switch circuit in the ADSEL=0 state as shown in the following figure. The internal switch can be switched
on or off uniquely by the value of the bit D3 of the SYSCON register.
V
CC
D3 of the
SYSCON
ALE/PUCTL
D+
D-
1.5K
ML60852
USB
Transceiver
ADSEL
GND
29/81
Page 30
PEDL60852-01
Semiconductor
1
ML60852
INTERNAL REGISTERS
The register file of the ML60852 includes registers to set operating conditions and registers to report the status of
operating and the results of processing.
These registers are read-only registers, write-only register and read/write registers in view of the MCU of the
application.
The setup registers in which setup data to be transfered from a host via the control pipe is stored are mapped in the
addresses of the register file. Moreover, The data phase data in the control transfer mode and transmit/receive data
in other transfer modes are mapped in the addresses of the register file.
The mapping of these registers are described in the following pages.
The EP0 transmit data can be written in by writing to the address 70h.
The transmit data to the host in the data stage during a control read transfer is stored in EP0TXFIFO. When the
ML60852 issues an EP0 transmit packet ready interrupt request, the local MCU writes the transmit data to the
address 70h.
It is possible to write the packet data successively by writing continuously.
The EP0TXFIFO is cleared under the following conditions.
1. When an ACK signal is received from the host for the data transmission from EP0
2. When a setup packet is received
EP0 Receive FIFO (EP0RXFIFO)
Address0 x 78
TypeByte data
Access typeRead only
D7D6D5D4D3D2D1D0
After a hardware resetxxxxxxxx
After a bus reset xxxxxxxx
DefinitionEP0 Receive data
The receive data from the host computer in the data sate during a control Write transfer is stored in EPORXFIFO.
The EPO receive data can be read out by the local MPU through reading the address 78h when the ML60852 issues
an EPO receive packet ready interrupt request. It is possible to read successively the data in the packet by reading
continuously.
The EP2RXFIFO is cleared under the following conditions:
1. When the local MPU resets the EPO receive packet ready bit.
2. When a setup packet is received.
3. When the local MCU writes a “0” in the stall bit.
34/81
Page 35
PEDL60852-01
Semiconductor
1
ML60852
EP1 FIFO (EP1FIFO)
Address0 x 79
TypeByte data
Access typeWrite only
or
Read only
D7D6D5D4D3D2D1D0
After a hardware resetxxxxxxxx
After a bus reset xxxxxxxx
DefinitionEP1 Transmit data or EP1 receive data
It is possible to specify the direction of transfer of EP1 by setting the EP1 configuration register EP1CONF. The
FIFO address of EP1 is the same in both the transmit direction and the receive direction.
When EP1CONF (D7) = 0, EP1 is in the receive direction and EP1FIFO is in the read-only state.
When EP1CONF (D7) = 1, EP1 is in the transmit direction and EP1FIFO is in the write-only state.
When set for transmission, all bytes of EP1FIFO can be cleared by clearing EP1FIFO (writing a “1” into EP1CONT
(D2)).
EP2 FIFO (EP2FIFO)
Address0 x 7A
TypeByte data
Access typeWrite only
or
Read only
D7D6D5D4D3D2D1D0
After a hardware resetxxxxxxxx
After a bus reset xxxxxxxx
DefinitionEP2 Transmit data or EP2 receive data
It is possible to specify the direction of transfer of EP2 by setting the EP2 configuration register EP2CONF. The
FIFO address of EP2 is the same in both the transmit direction and the receive direction.
When EP2CONF (D7) = 0, EP2 is in the receive direction and EP2FIFO is in the read-only state.
When EP2CONF (D7) = 1, EP2 is in the transmit direction and EP2FIFO is in the write-only state.
When set for transmission, all bytes of EP2FIFO can be cleared by clearing EP2FIFO (writing a “1” into EP2CONT
(D2)).
35/81
Page 36
PEDL60852-01
Semiconductor
1
ML60852
EP3 FIFO (EP3FIFO)
Address0 x 7B
TypeByte data
Access typeWrite only
or
Read only
D7D6D5D4D3D2D1D0
After a hardware resetxxxxxxxx
After a bus reset xxxxxxxx
DefinitionEP3 Transmit data or EP3 receive data
It is possible to specify the direction of transfer of EP3 by setting the EP3 configuration register EP3CONF. The
FIFO address of EP3 is the same in both the transmit direction and the receive direction.
When EP3CONF (D7) = 0, EP3 is in the receive direction and EP3FIFO is in the read-only state.
When EP3CONF (D7) = 1, EP3 is in the transmit direction and EP3FIFO is in the write-only state.
When set for transmission, all bytes of EP3FIFO can be cleared by clearing EP3FIFO (writing a “1” into EP3CONT
(D2)).
EP4 FIFO (EP4FIFO)
Address0 x 7C
TypeByte data
Access typeWrite only
or
Read only
D7D6D5D4D3D2D1D0
After a hardware resetxxxxxxxx
After a bus reset xxxxxxxx
DefinitionEP4 Transmit data or EP4 receive data
It is possible to specify the direction of transfer of EP4 by setting the EP4 configuration register EP4CONF. The
FIFO address of EP4 is the same in both the transmit direction and the receive direction.
When EP4CONF (D7) = 0, EP4 is in the receive direction and EP4FIFO is in the read-only state.
When EP4CONF (D7) = 1, EP4 is in the transmit direction and EP4FIFO is in the write-only state.
When set for transmission, all bytes of EP4FIFO can be cleared by clearing EP4FIFO (writing a “1” into EP4CONT
(D2)).
36/81
Page 37
PEDL60852-01
Semiconductor
1
ML60852
EP5 FIFO (EP5FIFO)
Address0 x 7D
TypeByte data
Access typeWrite only
or
Read only
D7D6D5D4D3D2D1D0
After a hardware resetxxxxxxxx
After a bus reset xxxxxxxx
DefinitionEP5 Transmit data or EP5 receive data
In the ML60852, by making a setting of the system control register, it is possible to select either the 5EP mode with
the number of EPs being 5 or the 6EP mode with the number of EPs being 6. In the 5EP mode, only EP0 to EP4 are
present and EP5 will not be present. In the EP6 mode, all end points EP0 to EP5 will be valid.
It is possible to specify the direction of transfer of EP5 by setting the EP5 configuration register EP5CONF. The
FIFO address of EP5 is the same in both the transmit direction and the receive direction.
When EP5CONF (D7) = 0, EP5 is in the receive direction and EP5FIFO is in the read-only state.
When EP5CONF (D7) = 1, EP5 is in the transmit direction and EP5FIFO is in the write-only state.
When set for transmission, all bytes of EP5FIFO can be cleared by clearing EP5FIFO (writing a “1” into EP5CONT
(D2)).
37/81
Page 38
Semiconductor
1
bmRequestType Setup Register (bmRequestType)
Address0 x 00
TypeBit map
Access typeRead only
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset 00000000
DefinitionTypeReceiving side definitions
PEDL60852-01
ML60852
0 = Device
1 = Interface
2 = End point
3 = Others
4 to 31 = Reserved
0 = Standard
1 = Class
2 = Vendor
3 = Reserved
Data transfer direction0 = From the host to the device
1 = From the device to the host
During the setup stage of control transfer based on a request from the host, the 8-byte setup data transmitted by the
host is automatically received by the ML60852 and is stored in the 8 registers including this register. The formats
of these data items are defined in Section 9.3 of the USB Standards.
bRequest Setup Register (bRequest)
Address0 x 01
TypeByte data
Access typeRead only
D7D6D5D4D3D2D1D0
After a hardware resetxxxxxxxx
After a bus reset xxxxxxxx
DefinitionRequest code
During the setup stage of control transfer based on a request from the host, the 8-byte setup data transmitted by the
host is automatically received by the ML60852 and the second byte is stored in this register. The content of the
request code is defined in Section 9.3 of the USB Standards and in the related standards.
38/81
Page 39
PEDL60852-01
Semiconductor
1
ML60852
wValueLSB Setup Register (wValueLSB)
Address0 x 02
Type2-Byte data
Access typeRead only
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset 00000000
DefinitionwValueLSB
During the setup stage of control transfer based on a request from the host, the 8-byte setup data transmitted by the
host is automatically received by the ML60852 and the third byte is stored in this register. This is the lower-order
byte of the two-byte data.
wValueMSB Setup Register (wValueMSB)
Address0 x 03
Type2-Byte data
Access typeRead only
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset 00000000
DefinitionwValueMSB
During the setup stage of control transfer based on a request from the host, the 8-byte setup data transmitted by the
host is automatically received by the ML60852 and the fourth byte is stored in this register. This is the higher-order
byte of the two-byte data.
39/81
Page 40
PEDL60852-01
Semiconductor
1
ML60852
wIndexLSB Setup Register (wIndexLSB)
Address0 x 04
Type2-Byte data
Access typeRead only
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset 00000000
DefinitionwIndexLSB
During the setup stage of control transfer based on a request from the host, the 8-byte setup data transmitted by the
host is automatically received by the ML60852 and the fifth byte is stored in this register. This is the lower-order
byte of the two-byte data.
wIndexMSB Setup Register (wIndexMSB)
Address0 x 05
Type2-Byte data
Access typeRead only
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset 00000000
DefinitionwIndexMSB
During the setup stage of control transfer based on a request from the host, the 8-byte setup data transmitted by the
host is automatically received by the ML60852 and the sixth byte is stored in this register. This is the higher-order
byte of the two-byte data.
40/81
Page 41
PEDL60852-01
Semiconductor
1
ML60852
wLengthLSB Setup Register (wLengthLSB)
Address0 x 06
Type2-Byte data
Access typeRead only
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset 00000000
DefinitionwLengthLS
During the setup stage of control transfer based on a request from the host, the 8-byte setup data transmitted by the
host is automatically received by the ML60852 and the seventh byte is stored in this register. This is the lowerorder byte of the two-byte data.
wLengthMSB Setup Register (wLengthMSB)
Address0 x 07
Type2-Byte data
Access typeRead only
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset 00000000
DefinitionwLengthMSB
During the setup stage of control transfer based on a request from the host, the 8-byte setup data transmitted by the
host is automatically received by the ML60852 and the eighth byte is stored in this register. This is the higher-order
byte of the two-byte data.
41/81
Page 42
Semiconductor
1
DMA0,1 Control Registers (DMA0, 1CON)
Address0 x 10, 0 x 12
TypeBit map
Access typeRead/Write
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus resetThe previous value is retained
Definition
DMA Address mode
0 = Single address mode
1 = Dual address mode
DMA Byte count
0 = The number of bytes is not
inserted
1 = The data of the number of
bytes is inserted in the
leading byte or leading word
of the transfer data. (Note 1)
Specifies the target EP for the DMA transfer
0=EP1, 1=Ep2, 2=EP4, 3=EP5 (Note 3)
DMA Interrupting (Note 4)
0=Normal operation
DREQ
1=The
pin is de-asserted
Note 1: During the 16-bit mode, the higher order byte of the leading word will be 00h.
Note 2: The higher order byte and the lower order byte are allocated in the little-endian sequence. That is,
the LSB corresponds to AD0 to AD7 and the MSB corresponds to D8 to D15.
During the 16-bit mode and when the packet size is an odd number of bytes, the higher order byte
of the last word will be 00h.
Note 3: When the EP specifications for the DMA channels 0 and 1 both have the same values, DREQ0,
DREQ 1 and DACK0, DACK 1 will respectively be equivalent.
Note 4: The settings of all bits other than bit D7, that is, of bits D0 to D6 should be completed at the time
of initialization (at the latest, before a token packet for EP1 to Ep5 arrives), and should not be
altered thereafter. Write a “1” to D7 in order to temporarily stop DMA transfer in the middle.
When the transfer is restarted by writing a “0” to D7, it is possible to restart the transfer from the
byte (or word) next to the one at which the transfer was interrupted.
42/81
Page 43
PEDL60852-01
Semiconductor
1
ML60852
DMA0, 1 Interval Registers (DMA0, 1INTVL)
Address0 x 11, 0 x 13
TypeByte data
Access typeRead/Write
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus resetThe previous value is retained
DefinitionInterval time
This specifies the interval in the single DMA transfer mode, that is, the time duration after the end of DMA transfer
of the previous byte (or the previous word) until DREQ is asserted again. The time for 1 bit is 84ns (12 MHz,
period of one-cycle).
Interval time = (DREQ enable time) + 84xn (ns)
See the description of the DMA Transfer Timings (1), (2), (5), and (6) for the DREQ enable time.
43/81
Page 44
PEDL60852-01
Semiconductor
1
ML60852
Device Address Register (DVCADR)
Address0 x 20
Type7-bit data
Access typeRead/Write
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset
DefinitionDevice address (R/W)
The device address given by a SET_ADDRESS request from the host is written in this register by the local MCU.
Thereafter, the ML60852 judges the specified address in the token from the host, and this device will process only
the token packets sent to this device address.
Bit D7 is fixed at “0”, and even if a “1” is written, it will be ignored.
44/81
Page 45
Semiconductor
1
Interrupt Status Register 1 (INTSTAT1)
Address0 x 21
TypeBit map
Access typeRead only
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset Xxxxxxx0
Definition
PEDL60852-01
ML60852
Setup ready
interrupt status
(stup_ry)
EP1 packet ready
interrupt status
(ep1_pry)
EP2 packet ready interrupt status
(ep2_pry)
EP3 packet ready interrupt status
(ep3_pry)
EP4 packet ready interrupt status
(ep4_pry) (Note)
EP5 packet ready interrupt status (ep5_pry) (Note)
EP0 receive packet ready interrupt status
EP0 transmit packet ready interrupt status
Note: When isochronous transfer has been set in the EP4 or EP5 configuration register, the EP4 or EP5
packet ready interrupt status will always be fixed at “0”.
45/81
Page 46
Semiconductor
1
Interrupt Status Register 2 (INTSTAT2)
Address0 x 22
TypeBit map
Access typeRead/Reset
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset 00000000
Definition000
USB Bus reset assert
interrupt status (busrst_ass)
USB Bus reset de-assert
interrupt status (busrst_des)
PEDL60852-01
ML60852
SOF Interrupt status
(sof)
Device suspend state interrupt status
(suspend)
Device awake state interrupt status
(awake)
The status bit becomes “1” when the corresponding interrupt is generated.
The status is cleared when a “1” is written in that status bit itself.
(See Section (8) “Interrupt” of Functional Descriptions.)
This is valid when containing an end point in the isochronous transfer mode. When a start of frame (SOF) packet is
transmitted by the host, the ML60852 automatically writes into the FRAMELSB and FRAMEMSB registers.
Frame Number MSB (FRAMEMSB)
Address0 x 2E
Type11-Bit data
Access typeRead only
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset 00000000
DefinitionFrame number MSB
This is valid when containing an end point in the isochronous transfer mode. When a start of frame (SOF) packet is
transmitted by the host, the ML60852 automatically writes into the FRAMELSB and FRAMEMSB registers.
49/81
Page 50
Semiconductor
1
System Control Register (SYSCON)
Address0 x 2F
TypeBit map
Access typeRead/Write
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus resetThe previous value is retained
Definition0
Power-down mode
(R/W) (power)
0 = Power saving is not
done in the suspend
mode.
1 = Power saving is done
in the suspend mode.
EP Mode (R/W) (ep_mod)
0 = EP0 to EP5
1 = EP0 to EP4
PEDL60852-01
ML60852
Software reset
(R/W) (sereset)
Pull-up control (R/W) (plup)
Remote wakeup (R/W)
PLL Enable (pll_enable)
PLL Multiplication factor selection (fsel)
Software reset:Write-only bit. Even when this bit is read out, it will be fixed at “0”. A system reset is
executed when a “1” is written in this bit. This is functionally equivalent to a hardware reset.
However, this bit itself will always remain “0”.
Power-down mode: Read/Write bit. When this bit is “0”, the oscillations will not be stopped even during the
suspend mode. When this bit is made “1”', the oscillations will be stopped in the suspend
mode and the device goes into the power save mode.
EP mode:Read/Write bit. The 6EP mode is selected when this bit is 0 and the 5EP mode is selected
when this bit is “1”.
Pull-up control:The content of this bit becomes valid when the ADSEL pin is “L”. When the ADSEL pin is
“L”, the internal switch becomes ON and the ALE pin is pulled up to the Vcc level if this bit is
“1”. On the other hand, if the ADSEL pin is “L” and also this bit is “0”, the internal switch is
made OFF and the ALE pin goes into the high impedance state.
Remote wakeup:A remote wakeup is executed when a “1” is written in this bit. However, this bit itself will
always remain “0”.
PLL enable:This bit is for enabling the internal PLL. The internal PLL cannot be used when this bit is “0”.
The signal input to the XIN pin becomes the source oscillations for the internal circuits.
The internal PLL can be used when this bit is “1”.
PLL multiplication
factor selection:The frequency multiplication factor is 4 when this bit is “0”, and will be 8 when this bit is
“1”.
(The source oscillator frequency will be 12MHz in the 4x mode and will be 6MHz in the 8x
mode.)
50/81
Page 51
Semiconductor
g
1
Polarity Selection Register (POLSEL)
Address0 x 30
TypeBit map
Access typeRead/Write
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus resetThe previous value is retained
Definition000
DACK0 polarity
0 = Active High
1 = Active Low
PEDL60852-01
DREQ0
polarity
0 = Active Low
1 = Active Hi
ML60852
h
DREQ1
polarity
0 = Active Low
1 = Active High
DACK1 polarity
0 = Active High
1 = Active Low
INTR
polarity
0 = Active Low
1 = Active High
51/81
Page 52
PEDL60852-01
Semiconductor
1
ML60852
EP0 Configuration Register (EP0CONF)
Address0 x 40
TypeBit map
Access typeRead only
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset 00010000
Definition0000000
Transfer type (read only)
00 = Control transfer
Configuration bit (read only)
Transfer type:Although these bits indicate the type of transfer, since EP0 has been fixed for control transfer
in the ML60852, this value is always fixed at 00h. The local MCU cannot write into these
bits.
Configuration bit:The configuration bit of EP0 becomes “1” after a USB bus reset.
When this bit is “1”, the data transmitted by the host to the end point can be received and also
data can be transmitted from the end point to the host. When this bit is “0”, this LSI will not
respond to any transaction targeting this end point. This bit cannot be written in by the local
MCU.
10 = Bulk transfer
11 = Interrupt transfer
01 = Isochronous
transfer
Transfer direction
0=Reception,
1=transmission
Transfer type:These bits indicate the type of transfer. Only EP4 and EP5 can be set to isochronous transfer.
Configuration bit:When a Set Configuration request to make that EP active is received from the host, make sure
that the local MCU writes a “1” into this bit during the status stage in the control
transfermode.
Data transmission and reception can be made between the host and the EP when this bit is “1”.
When this bit is “0”, this LSI will not respond to the transactions targeted at that EP.
Transfer direction:Set the direction of data transfer using this bit.
53/81
Page 54
Semiconductor
1
EP0 Control Register (EP0CONT)
Address0 x 48
TypeBit map
Access typeRead/Write
D7D6D5D4D3D2D1D0
After a hardware reset000x00x0
After a bus reset000x00x0
Definition00000
PEDL60852-01
ML60852
Stall bit
(R/W)
Data sequence toggle bit
(reception)
Data sequence toggle bit
(transmission)
Stall bit:During EP0 reception (data stage of a control write transfer), if a packet with a number
of bytes exceeding the maximum packet size specified in EP0PLD is received (or if the
EOP packet is missing), the ML60852 automatically sets this bit to “1”. In order to
conform to the Protocol Stall of USB Rev. 1.1, this bit is reset automatically to “0” when
a setup packet is received.
Data sequence toggle bits: The ML60852 automatically carries out synchronization using the data sequence toggle
mechanism. Further, any write operation to these bits (D4 and D1) will be invalid.
54/81
Page 55
Semiconductor
1
EP1, 2, 3, 4, 5 Control Registers (EP1,2,3,4,5CONT)
Address0 x 49 to 4D
TypeBit map
Access typeSee below
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset 00000000
Definition0000
Data sequence toggle bit
(R/Reset)
FIFO Clear (R/Reset)
PEDL60852-01
ML60852
Stall bit
(R/W)
Rate feedback (R/W)
Stall bit:During EP0 reception (data stage of a control write transfer), if a packet with a number
of bytes exceeding the maximum packet size specified in EP0PLD is received (or if the
EOP packet is missing), the ML60852 automatically sets this bit to “1”.
Data sequence toggle bit: A reset will be made when a “1” is written in this bit. At the time of initializing the EP,
reset the toggle bit of the data packet by writing a “1” to this bit, and specify PID of
DATA0 (this bit too will become “0”). Thereafter, the synchronization operation using
the data sequence toggle mechanism will be made automatically.
FIFO Clear:The EP will be valid only when it has been set for transmission by the EP control register.
When a “1” is written in this bit, the transmit FIFO of that EP will be cleared. (However,
this bit itself will remain “0”.)
Rate feedback:This bit is valid only in the case of EP3. This bit will be fixed at “0” in all other EPs.
55/81
Page 56
PEDL60852-01
Semiconductor
1
ML60852
EP0 Payload Register (EP0PLD)
Address0 x 50
Type6-Bit data
Access typeRead only
D7D6D5D4D3D2D1D0
After a hardware reset00100000
After a bus reset 00100000
Definition0010
Maximum packet size
Maximum packet size: Since the FIFO of EP0 in the ML60852 has a size of 32 bytes, write 20h into the byte
bMaxPacketSize0 of the device descriptor. The maximum packet size is fixed at 32 bytes
in this EP0PLD register. When a packet with more than 32 bytes is received, the stall bit in
the EP0 status register is asserted and the stall handshake is returned to the host.
EP1, 2 Payload Registers (EP1,2PLD)
Address0 x 51, 52
Type7-Bit data
Access typeRead/Write
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset 00000000
Definition0Maximum packet size (R/W)
Maximum packet size: Make the local MCU write in this register the value of the descriptor wMaxPacketSize of
the end point selected by the Set_Configuration request from the host. The size of all
packets other than a short packet is specified here in units of a byte.
When the EP has been assigned for reception, if a data packet with a number of bytes
exceeding the maximum packet size specified in this register is received, the receive
packet ready status bit is not asserted, but the stall bit is set in EOP and the stall handshake
is returned to the host.
On the other hand, when the EP has been assigned for transmission, the transmit packet
ready bit is set automatically when writing by the DMA controller of data with the
maximum packet size specified in this register is completed. The content of this register is
ignored during non-DMA transmission of data.
56/81
Page 57
PEDL60852-01
Semiconductor
1
ML60852
EP3 Payload Register (EP3PLD)
Address0 x 53
Type6-Bit data
Access typeRead/Write
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset 00000000
Definition00
Maximum packet size
(R/W)
Maximum packet size: Make the local MCU write in this register the value of the descriptor wMaxPacketSize of
the end point selected by the Set_Configuration request from the host. The size of all
packets other than a short packet is specified here in units of a byte. Set 20h (32 bytes) or
less because the FIFO size is 32 bytes.
When EP3 has been assigned for reception, if a data packet with a number of bytes
exceeding the maximum packet size specified in this register is received, the receive
packet ready status bit is not asserted, but the stall bit is set in EOP and the stall handshake
is returned to the host.
There is no need to use this register when EP3 has been assigned for transmission.
EP4, 5 Payload LSB Registers (EP4, 5PLDLSB)
Address0 x 54, 55
Type10-Bit or 9-bit data
Access typeRead/Write
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset 00000000
DefinitionMaximum packet size LSB (R/W)
Maximum packet size LSB: Make the local MCU write in this register the value of the descriptor wMaxPacketSize
of the end point selected by the Set_Configuration request from the host. The lower 8
bits should be stored in this register and the higher-order bytes should be written in the
EP4,5 payload registers MSB. The maximum packet size is specified in units of a
byte.
When the EP has been assigned for reception, if a data packet with a number of bytes
exceeding the maximum packet size specified in these registers is received, the receive
packet ready status bit is not asserted, but the stall bit is set in EOP and the stall
handshake is returned to the host.
On the other hand, when the EP has been assigned for transmission, the transmit
packet ready bit is set automatically when writing by the DMA controller of data with
the maximum packet size specified in this register is completed.
57/81
Page 58
PEDL60852-01
Semiconductor
1
ML60852
EP0 Receive Byte Counter Register (EP0RXCNT)
Address0 x 58
Type6-Bit data
Access typeRead only
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset 00000000
Definition00Receive byte count (R)
The ML60852 automatically counts the number of bytes in the packet being received. Although the counting is
done only up to the number of bytes equal to the maximum packet size specified in the payload register in the case
of a full packet, the count will be less than that size in the case of a short packet. The local MCU refers to this value
and reads out the data of one packet from the EP0 Receive FIFO.
The EP0RXCNT register is cleared under the following conditions.
1. When the local MCU resets the EP receive packet ready bit.
2. When a setup packet is received.
3. When the local MCU writes a “0” into the stall bit.
The ML60852 automatically counts the number of bytes in the packet being received. Although the counting is
done only up to the number of bytes equal to the maximum packet size specified in the payload register in the case
of a full packet, the count will be less than that size in the case of a short packet. The local MCU refers to this value
and reads out the data of one packet from the EP1/2 Receive FIFO.
This register will be invalid when the transfer direction of the EP is set for transmission.
The EP1,2RXCNT register is cleared under the following conditions.
1. When an OUT token is received for the EP.
2. When the local MCU resets the EP receive packet ready bit.
3. When the local MCU writes a “0” into the stall bit.
58/81
Page 59
PEDL60852-01
Semiconductor
1
ML60852
EP3 Receive Byte Counter Register (EP3RXCNT)
Address0 x 5B
Type6-Bit data
Access typeRead only
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset 00000000
Definition00Receive byte count (R)
The ML60852 automatically counts the number of bytes in the packet being received. Although the counting is
done only up to the number of bytes equal to the maximum packet size specified in the payload register in the case
of a full packet, the count will be less than that size in the case of a short packet. The local MCU refers to this value
and reads out the data of one packet from the EP3 Receive FIFO.
This register will be invalid when the transfer direction of the EP is set for transmission.
The EP3RXCNT register is cleared under the following conditions.
1. When an OUT token is received for EP3.
2. When the local MCU resets the EP receive packet ready bit.
3. When the local MCU writes a “0” into the stall bit.
The ML60852 automatically counts the number of bytes in the packet being received. Although the counting is
done only up to the number of bytes equal to the maximum packet size specified in the payload register in the case
of a full packet, the count will be less than that size in the case of a short packet. The local MCU refers to this value
and reads out the data of one packet from the EP4/5 Receive FIFO. The lower 8 bits of the receive byte count are
stored in this register and the higher order bits are stored in the EP receive byte counter MSB.
This register will be invalid when the transfer direction of the EP is set for transmission.
The EP4,5RXCNT register is cleared under the following conditions.
1. When an OUT token is received for the EP.
2. When the local MCU resets the EP receive packet ready bit.
3. When the local MCU writes a “0” into the stall bit.
59/81
Page 60
Semiconductor
1
EP0 Status Register (EP0STAT)
Address0 x 60
TypeBit map
Access typeSee below
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset 00000000
Definition000
EP0 transmit packet ready
(R/Set)
Setup ready
(R/Reset)
PEDL60852-01
ML60852
EP0 receive packet
ready (R/Reset)
EP0 stage (R)
00 = Default state
01 = Data stage
10 = Data stage completed state
Setup ready:This bit is set automatically when a setup packet normally arrives in the 8-byte setup register,
and the EP0 Receive FIFO is locked.
If INTENBL1(0) is asserted, the
INTR
pin is also asserted automatically when this bit is set.
The local MCU should write a “1” into this bit after reading out the 8-byte setup data.
When this is performed, the setup ready bit is reset and the
INTR
pin also is de-asserted.
During a control write transfer, the packet ready bit of EP0 is reset simultaneously and the
lock condition is released, and it becomes possible to receive packets by EP0 during the data
stage. The register will not change even if a “0” is written in this bit.
EP0 transmit packet
ready bit (D1):The local MCU can read this bit. Writing when D1=1 sets this bit to “1”. The asserting and
de-asserting conditions are described below.
Bit nameAsserting conditionOperation when asserted
EP0 transmit packet ready (D1) When the local MCU has reset this bit Data can be transmitted from EP0.
Bit nameDe-asserting conditionOperation when de-asserted
EP0 transmit packet ready (D1)
1. When an ACK is received from the
host for data transmission
2. When a setup packet is received
EP0 is locked. That is, an NAK is
automatically returned when an IN
token is sent from the host.
60/81
Page 61
PEDL60852-01
Semiconductor
1
ML60852
EP0 receive packet ready bit (D0):The local MCU can read this bit. Writing when D1=1 sets this bit to “0”.
The asserting and de-asserting conditions are described below.
Bit nameAsserting conditionOperation when asserted
EP0 receive packet ready (D0)1. When data is received by EP0 and
stored in FIFO
2. When a setup packet is received
during control Read transfer or
control Write transfer
Bit nameDe-asserting conditionOperation when de-asserted
EP0 receive packet ready (D0)1. When the local MCU has reset this
bit ( a “1” is written in this bit)
2. When the local MCU resets the
setup ready bit during control Write
transfer
EP0 is locked (an NAK is
automatically returned when a data
packet is received from the host).
EP0 can receive data.
61/81
Page 62
Semiconductor
1
EP0 Stage (D5, D4): These bits indicate the stage transition during control transfer.
The flowchart of the stage transition is shown below.
Hardware Reset
Default State
Condition 1
Data State
PEDL60852-01
ML60852
Condition 2
Completed State
Condition 1:Reception of a setup packet of control READ transfer or control WRITE transfer.
Condition 2:Reception of a setup packet of control transfer without data.
Condition 3:Reception of a token (IN/OUT) of a direction opposite to the data flow in the data
stage.
Condition 3
Condition 1
Data Stage
62/81
Page 63
PEDL60852-01
Semiconductor
1
ML60852
EP1, 2, 4, 5 Status Registers (EP1, 2, 4, 5STAT)
Address0 x 61, 62, 64, 65
TypeBit map
Access typeSee below
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset 00000000
Definition000000
EP Receive packet
ready (Read/Reset)
EP Transmit packet ready
(Read/Set)
This register is valid only when the corresponding EP has been set for bulk or interrupt transfer.
EP1,2,4,5 Receive packet ready bit (D0): This bit can be read by the local MCU. Also, this bit can be made “0” by
writing a “1” into bit D0. The asserting and de-asserting conditions of
this bit are as given below. The FIFOs of EP1, EP2, EP4, and EP5 have
a 2-layer structure and also there are independent packet ready bits for
layer A and layer B. The switching between these two layers is done
automatically by the ML60852.
Bit nameAsserting conditionOperation when asserted
EP1 Receive packet ready (D0) When an error-free packet is received
in either layer A or layer B.
Bit nameDe-asserting conditionOperation when de-asserted
EP0 receive packet ready (D0)
When the local MCU has reset
(written a “1” in) the bits of both layer
A and layer B.
The local MCU can read the EP1
Receive FIFO. EP1 is locked in the
condition in which data packets have
been received by both layer A and
layer B.
Reception can be made by EP1 when
the bit of either layer A or layer B has
been reset.
EP1,2,4,5 Transmit packet ready bit (D1): This bit can be read by the local MCU. Also, this bit can be made “1” by
writing a “1” into bit D1. The asserting and de-asserting conditions of
this bit are as given below. The FIFO of EP1 has a 2-layer structure and
also there are independent packet ready bits for layer A and layer B. The
switching between these two layers is done automatically by the
ML60852.
Bit nameAsserting conditionOperation when asserted
EP1 Transmit packet ready (D1) When the local MCU has set the bits
of both layer A and layer B.
Transmission can be made from EP1
when either layer A or layer B has
been asserted.
Bit nameDe-asserting conditionOperation when de-asserted
EP1 Transmit packet ready (D1) When an ACK message is received
from the host for the data transmission
to either layer A or layer B.
EP1 is locked when transmit data has
not been prepared for both layer A
and layer B.
63/81
Page 64
PEDL60852-01
Semiconductor
1
ML60852
EP3 Status Register (EP3STAT)
Address0 x 63
TypeBit map
Access typeSee below
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset 00000000
Definition000000
EP3 Receive packet
ready (Read/Reset)
EP3 Transmit packet ready
(Read/Set)
This register is valid only when EP3 has been set for bulk or interrupt transfer.
EP3 Receive packet ready bit (D0): This bit can be read by the local MCU. Also, this bit can be made “0” by
writing a “1” into bit D0. The asserting and de-asserting conditions of this bit
are as given below.
Bit nameAsserting conditionOperation when asserted
EP3 Receive packet ready (D0) When an error-free packet is received. EP3 is locked.
Bit nameDe-asserting conditionOperation when de-asserted
EP3 Receive packet ready (D0) When the local MCU has reset (written
a “1” in) this bit.
Reception can be made by EP3.
EP3 Transmit packet ready bit (D1): This bit can be read by the local MCU. Also, this bit can be made “1” by
writing a“'1” into this bit. The asserting and de-asserting conditions of this bit
are as given below.
Bit nameAsserting conditionOperation when asserted
EP1 Transmit packet ready (D1) When the local MCU has set this bit.When an ACK message is received
from the host for the data transmission
from EP3.
Bit nameDe-asserting conditionOperation when de-asserted
EP1 Transmit packet ready (D1) Transmission can be made from EP3. Reception can be made by EP3.
64/81
Page 65
PEDL60852-01
Semiconductor
1
ML60852
EP4, 5 Payload MSB Registers (EP4, 5PLDMSB)
Address0 x 6C, 6D
Type10-Bit or 9-bit data
Access typeRead/Write
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset 00000000
Definition000000
EP Payload MSB
The higher-order 6 bits of EP4PLDMSB are fixed at “0” and the higher-order 7 bits of EP5PLDMSB are fixed at
“0”.
The higher-order 6 bits of EP4RXCNTMSB are fixed at “0” and the higher-order 7 bits of EP5RXCNTMSB are
fixed at “0”.
66/81
Page 67
Semiconductor
1
Packet Error Register (PKTERR)
Address0 x 39
TypeBit map
Access typeRead only
D7D6D5D4D3D2D1D0
After a hardware reset00000000
After a bus reset 00000000
Definition000000
PEDL60852-01
ML60852
Bit stuff error
Data CRC error
Address CRC error
PID error
Each of the above bits is asserted when the corresponding error occurs, and is de-asserted when SOP is received.
The error information is reported by this register. There is no particular need to access this register other than for
testing during development or for developing a product for making reports of measurement of error occurrence
frequency.
67/81
Page 68
Semiconductor
1
TIMING DIAGRAM
READ Timing (1)
(Address Separate, ADSEL =0)
ParameterSymbolConditionMin.Max.UnitNote
Address Setup Time (RD)t
Address Setup Time (CS)t
Address (CS) Hold Timet
Read Data Delay Timet
Read Data Hold Timet
Recovery Timet
FIFO Access Timet
Notes: (1) t3 is defined depending upon CS or RD which becomes active last.
(2) t
is defined depending upon CS or RD which becomes active first.
2
(3) 3-clock time of oscillation clock (clock period:21 ns). It is required for increment of FIFO.
(4) 2-clock time of oscillation clock (clock period:21 ns). It is required for increment of FIFO.
is required for reading FIFO. t1 is defined when either t1 (CS)or t t1 (RD)is satisfied.
Notes: (1) 3-clock time of oscillation clock (clock period:21 ns). It is required for increment of FIFO.
(2) 2-clock time of oscillation clock (clock period:21 ns). It is required for increment of FIFO.
AD7: AD0
CS
ALE
RD
DATA OUTADDRESS
t
t
1
2
t
3
t
6
t
4
t
5
69/81
Page 70
PEDL60852-01
Semiconductor
1
ML60852
WRITE Timing (1)
(Address Separate, ADSEL =0)
ParameterSymbolConditionMin.Max.UnitNote
Address Setup Timet1 (a-w)0—ns(1)
Address Setup Timet1 (a-c)0—ns(1)
Address (CS) Hold Timet
CS
Setup Timet
Write Data Setup Timet
Write Data Hold Timet
Recovery Timet
FIFO Access Timet
2
3
4
5
6
7
FIFO WRITE63—ns(2)
FIFO WRITE63ns(3)
0—ns
10—ns
30—ns
0—ns
Notes: (1) Either t1 (a –w) or t1 (a –c) should be satisfied.
is defined depending upon CS or WR which becomes active last.
(2) t
1
(3) 3-clock time of oscillation clock (clock period: 21ns). It is required for increment of FIFO.
(4) 2-clock time of oscillation clock (clock period: 21ns). It is required for increment of FIFO.
(5) Applied to all registers including CLRFIFO (address: 4Eh).
Notes: (1) 3-clock time of oscillation clock (clock period: 21 ns). It is required for increment of FIFO.
(2) 2-clock time of oscillation clock (clock period: 21 ns). It is required for increment of FIFO.
(3) Applied to all registers including CLRFIFO (address: 4Eh).
AD7: AD0
CS
ALE
WR
ADDRESS
DATA IN
t2t1
t4
t3
t5
t6
71/81
Page 72
Semiconductor
1
DMA Transfer Timing (1)
ML60852 to Memory (Single Transfer, Single Address Mode)
ParameterSymbolConditionMin.Max.UnitNote
DREQ
Disable Timet
DREQ
Enable Timet
DACK Hold Timet
Read Data Delay Timet
Data Hold Timet
Recovery Timet
1
2
3
4
5
6
Load 20 pF—20ns
—63ns(4)
0—ns
Load 20 pF—46ns(1)
0—ns
8-bit DMA63—ns(2)
16-bit DMA105—ns(3)
Notes: (1) When in Single Address mode, CS and A7: A0 are ignored.
and t4 are defined depending on DACK or RD which becomes active last.
t
1
(2) 3-clock time of oscillation clock (clock period: 21 ns).
(3) 5-clock time of oscillation clock (clock period: 21 ns).
(4) It is possible to increase t
by setting the DMA interval register (DMAINTVL).
2
PEDL60852-01
ML60852
DREQ
DACK
RD
DOUT
t
t
1
4
t
3
t
5
t
2
t
6
DATA OUT
72/81
Page 73
Semiconductor
1
DMA Transfer Timing (2)
ML60852 to Memory (Single Transfer, Dual Address Mode)
ParameterSymbolConditionMin.Max.UnitNote
DREQ
Disable Timet
DREQ
Enable Timet
Read Data Delay Timet
Data Hold Timet
Recovery Timet
1
2
3
4
5
Load 20 pF—20ns
Load 20 pF—46ns(1)
8-bit DMA63—ns(2)
16-bit DMA105—ns(3)
Notes: (1) When in Dual Address mode, the DACK is ignored.
t
1
and t
are defined depending on CS or RD which becomes active last.
3
A7: A0 specifies the FIFO address.
Refer to READ Timing (1) for Address Setup Time and Address Hold Time.
(2) 3-clock time of oscillation clock (clock period: 21 ns).
(3) 5-clock time of oscillation clock (clock period: 21 ns).
t
(4) It is possible to increase
t
by setting the DMA interval register (DMAINTVL).
2
PEDL60852-01
ML60852
—63ns(4)
0—ns
A7: A0
DREQ
CS
RD
DOUT
t
2
t
1
t
t
3
t
5
4
DATA OUT
73/81
Page 74
PEDL60852-01
Semiconductor
1
ML60852
DMA Transfer Timing (3)
ML60852 to Memory (Demand Transfer, Single Address Mode)
ParameterSymbolConditionMin.Max.UnitNote
DREQ
Disable Timet
DACK Hold Timet
Read Data Delay Timet
Data Hold Timet
Recovery Timet
1
2
3
4
5
Load 20 pF—20ns
0—ns
Load 20 pF—46ns(1)
0—ns
8-bit DMA63—ns(2)
16-bit DMA105—ns(3)
Notes: (1) When in Single Address mode, t3 is defined depending on DACK or RD which becomes
active last.
A7: A0 and CS are ignored.
(2) 3-clock time of oscillation clock (clock period: 21 ns).
(3) 5-clock time of oscillation clock (clock period: 21 ns).
DREQ
DACK
RD
DOUT
t
1
t
t
5
t
t
3
4
Last Packet Read
2
74/81
Page 75
Semiconductor
1
DMA Transfer Timing (4)
ML60852 to Memory (Demand Transfer, Dual Address Mode)
ParameterSymbolConditionMin.Max.UnitNote
DREQ
Disable Timet
CS
Hold Timet
Read Data Delay Timet
Data Hold Timet
Recovery Timet
1
2
3
4
5
Load 20 pF—20ns
Load 20 pF—46ns(1)
8-bit DMA63—ns(2)
16-bit DMA105—ns(3)
Notes: (1) When in Dual Address mode, the DACK is ignored.
t
is defined depending on CS or RD which becomes active last.
3
A7: A0 specifies the FIFO address.
Refer to READ Timing (1) for Address Setup Time and Address Hold Time.
(2) 3-clock time of oscillation clock (clock period: 21 ns).
(3) 5-clock time of oscillation clock (clock period: 21 ns).
PEDL60852-01
ML60852
0—ns
0—ns
AD7: A0
DREQ
CS
RD
DOUT
t1
t5
4
t
t3
Last Packet Read
t2
75/81
Page 76
Semiconductor
1
DMA Transfer Timing (5)
Memory to ML60852 (Single Transfer, Single Address Mode)
ParameterSymbolConditionMin.Max.UnitNote
DREQ
Disable Timet
DREQ
Enable Timet
FIFO Access Timet
DACK Hold Timet
Write Data Setup Timet
Write Data Hold Timet
Recovery Timet
1
2
3
4
5
6
7
Load 20 pF—20ns
—63ns(4)
FIFO WRITE42—ns(1)
0—ns
30—ns
5—ns
8-bit DMA63—ns(2)
16-bit DMA105—ns(3)
Notes: (1) When in Single Address mode, CS and A7: A0 are ignored.
(2) 3-clock time of oscillation clock (clock period: 21 ns).
(3) 5-clock time of oscillation clock (clock period: 21 ns).
(4) It is possible to increase
t2
by setting the DMA interval register (DMAINTVL).
PEDL60852-01
ML60852
DREQ
DACK
WR
DIN
4
t
1
t
3
t
t
t
t
5
6
t
2
7
76/81
Page 77
Semiconductor
1
DMA Transfer Timing (6)
Memory to ML60852 (Single Transfer, Dual Address Mode)
ParameterSymbolConditionMin.Max.UnitNote
DREQ
Disable Timet
DREQ
Enable Timet
FIFO Access Timet
Write Data Setup Timet
Write Data Hold Timet
Recovery Timet
1
2
3
4
5
6
Load 20 pF—20ns
FIFO WRITE42—ns(1)
8-bit DMA63—ns(2)
16-bit DMA105—ns(3)
Notes: (1) When in Dual Address mode, the DACK is ignored.
and t
t
1
are defined depending on CS or WR which becomes active last.
3
Refer to WRITE Timing (1) for Address Setup Time and Address Hold Time.
(2) 3-clock time of oscillation clock (clock period: 21 ns).
(3) 5-clock time of oscillation clock (clock period: 21 ns).
(4) It is possible to increase t
by setting the DMA interval register (DMAINTVL).
2
PEDL60852-01
ML60852
—63ns(4)
30—ns
5—ns
A7: A0
DREQ
CS
WR
RD
DIN
t
t
1
t
3
t
4
2
t
6
t
5
77/81
Page 78
Semiconductor
1
DMA Transfer Timing (7)
Memory to ML60852 (Demand Transfer, Single Address Mode)
ParameterSymbolConditionMin.Max.UnitNote
DREQ
Disable Timet
FIFO Access Timet
DACK Hold Timet
Write Data Setup Timet
Write Data Hold Timet
Recovery Timet
1
2
3
4
5
6
Load 20 pF—20ns
FIFO WRITE42—ns(1)
0—ns
30—ns
5—ns
8-bit DMA63—ns(2)
16-bit DMA105—ns(3)
Notes: (1) When in Single Address mode,A7: A0 and CS are ignored.
is defined depending on DACK or WR which becomes active last.
t
2
(2) 3-clock time of oscillation clock (clock period: 21 ns).
(3) 5-clock time of oscillation clock (clock period: 21 ns).
PEDL60852-01
ML60852
DREQ
t
1
DACK
t
2
t
t
6
3
WR
(Note)
t
4
t
5
Last Packet Write
DIN
(Note) The last Write to reach the byte size (maximum packet size) specified by the EP1 Payload
Register.
To terminate DMA transfer before reaching the maximum packet size, set EP1 Packet Ready by
writing "1"to the EP1 Endpoint Packet Ready bit.
78/81
Page 79
Semiconductor
1
DMA Transfer Timing (8)
Memory to ML60852 (Demand Transfer, Dual Address Mode)
ParameterSymbolConditionMin.Max.UnitNote
DREQ
Disable Timet
FIFO Access Timet
CS
Hold Timet
Write Data Setup Timet
Write Data Hold Timet
Recovery Timet
1
2
3
4
5
6
Load 20 pF—20ns
FIFO WRITE42—ns(1)
8-bit DMA63—ns(2)
16-bit DMA105—ns(3)
Notes: (1) When in Dual Address mode, the DACK is ignored.
A7: A0 specifies the FIFO address.
Refer to WRITE Timing (1) for Address Setup Time and Address Hold Time.
t
is defined depending on CS or WR which becomes active last.
2
(2) 3-clock time of oscillation clock (clock period: 21 ns).
(3) 5-clock time of oscillation clock (clock period: 21 ns).
PEDL60852-01
ML60852
0—ns
30—ns
5—ns
A7: A0
DREQ
CS
t
2
WR
t
4
DIN
(Note) Refer to the previous page.
t
1
t
6
t
5
t
3
79/81
Page 80
PEDL60852-01
Semiconductor
1
ML60852
NOTICE
1.The information contained herein can change without notice owing to product and/or technical improvements.
Before using the product, please make sure that the information being referred to is up-to-date.
2.The outline of action and examples for application circuits described herein have been chosen as an
explanation for the standard action and performance of the product. When planning to use the product, please
ensure that the external conditions are reflected in the actual circuit, assembly, and program designs.
3.When designing your product, please use our product below the specified maximum ratings and within the
specified operating ranges including, but not limited to, operating voltage, power dissipation, and operating
temperature.
4.Oki assumes no responsibility or liability whatsoever for any failure or unusual or unexpected operation
resulting from misuse, neglect, improper installation, repair, alteration or accident, improper handling, or
unusual physical or electrical stress including, but not limited to, exposure to parameters beyond the specified
maximum ratings or operation outside the specified operating range.
5.Neither indemnity against nor license of a third party’s industrial and intellectual property right, etc. is granted
by us in connection with the use of the product and/or the information and drawings contained herein. No
responsibility is assumed by us for any infringement of a third party’s right which may result from the use
thereof.
6.The products listed in this document are intended for use in general electronics equipment for commercial
applications (e.g., office automation, communication equipment, measurement equipment, consumer
electronics, etc.). These products are not authorized for use in any system or application that requires special
or enhanced quality and reliability characteristics nor in any system or application where the failure of such
system or application may result in the loss or damage of property, or death or injury to humans.
Such applications include, but are not limited to, traffic and automotive equipment, safety devices, aerospace
equipment, nuclear power control, medical equipment, and life-support systems.
7.Certain products in this document may need government approval before they can be exported to particular
countries. The purchaser assumes the responsibility of determining the legality of export of these products and
will take appropriate and necessary steps at their own expense for these.
8.No part of the contents contained herein may be reprinted or reproduced without our prior permission.
Copyright 2000 Oki Electric Industry Co., Ltd.
80/81
Page 81
PEDL60852-01
Semiconductor
1
ML60852
DATA SHEET REVISION HISTORY
From Ver. 0.32 to Ver. 0.40 - March 25, 1999
•
Changed the FIFO access time in the timing chart from 42ns to 63ns.
•
Changed the read data delay time in the timing chart from 25ns to 46ns.
•
Added functions to the higher order three bits of the DMA control register.
•
Added restrictions on the use of the DMA control register.
•
Discontinued supporting the 1K byte packet size in EP4.
•
Corrected the data packet transmission and reception procedure during isochronous transfer in paragraph (6) of
the FUNCTION DESCRIPTION.
•
Changed the maximum packet size (FIFO size) of EP0 and EP3 to 32 bytes.
•
Added remote wakeup bit in the system control register.
•
Changed the bit position of the receive/transmit packet ready bits in the EP status registers.
•
Changed the bit positions of the EP0 receive/transmit packet ready interrupt status/enable bits of the interrupt
status/enable register 1.
•
Added the function of conforming to protocol stall in the stall bit of the EP0 control register.
•
Added anew the MSB part in the EP4,5 payload/byte count register.
•
Changed the specifications of the interrupt statuses related to USB bus reset, suspend, and awake.
From Ver. 0.40 to Ver. 0.50 - June 25, 1999
•
Changed 48-pin TQFP to 56-pin LGA.
•
Changed PIN CONGURATION.
•
Changed the set value of the EP mode bit of the system control register.
•
Added the PLL enable bit in D5 of the system control register.
•
Added the PLL multiplication factor selection bit in D6 of the system control register.
•
Corrected other wrong Description.
From Ver. 0.50 to Ver. 0.51 - July 13, 1999
•
Added 56-pin LGA pin configration.
•
Corrected the figure.
•
Description of ALE/PUCTL: Corrected the bit map position of the SYSCON register.
•
Changed the description - End point and De-packeting
•
Reporting handshake is ACK ... <- Deleted ACK.
•
Added missing entry of the byte count register.
•
Corrected spelling mistake.
•
Corrected the bit map position of EPnSTAT.
•
Corrected the bit map position of EPnSTAT.
•
Corrected the bit map position of the SYSCON register.
•
Deleted the device state register.
•
Added description.
•
Corrected the shift in the figure.
•
Changed the expression.
•
Added description.
•
Changed the expression.
•
Added "Writing of the data sequence bit is invalid".
•
Changed from (R/Set) to (R/Reset) and from (R/Reset) to (R/Set), changes the name of EP0 stage.
•
nak to NAK
•
Corrected the drawing.
•
Changed from (R/Set) to (R/Reset) and from (R/Reset) to (R/Set)
•
Changed from (R/Set) to (R/Reset) and from (R/Reset) to (R/Set)
•
Deleted the device state register.
81/81
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.