CY7C68320C-56LTXC [CYPRESS]
EZ-USB AT2LP™ USB 2.0 to ATA/ATAPI Bridge; EZ- USB AT2LP ™ USB 2.0到ATA / ATAPI桥型号: | CY7C68320C-56LTXC |
厂家: | CYPRESS |
描述: | EZ-USB AT2LP™ USB 2.0 to ATA/ATAPI Bridge |
文件: | 总41页 (文件大小:797K) |
中文: | 中文翻译 | 下载: | 下载PDF数据表文档文件 |
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
EZ-USB AT2LP™ USB 2.0 to
ATA/ATAPI Bridge
■ Supports Compact Flash and one ATA/ATAPI Device
Features
■ Supports Board-level Manufacturing Test using the USB I/F
■ Fixed Function Mass Storage Device—Requires no Firmware
■ CanPlacetheATAInterfaceinHighImpedance(Hi-Z)toenable
Sharing of the ATA Bus with another Controller such as an
IEEE-1394 to ATA Bridge Chip or MP3 Decoder)
■ Two Power Modes: Self Powered and USB Bus Powered to
enableBusPoweredCFReadersandTrulyPortableUSBHard
Drives
■ Low Power 3.3V Operation
■ Certified Compliant for USB 2.0 (TID# 40490119), the USB
Mass Storage Class, and the USB Mass Storage Class
Bulk-Only Transport (BOT) Specification
■ Fully Compatible with Native USB Mass Storage Class Drivers
■ Cypress Mass Storage Class Drivers available for Windows
(98SE, ME, 2000, XP) and Mac OS X operating systems
■ Operates at High Speed (480 Mbps) or Full Speed (12 Mbps)
USB
Features (CY7C68320C/CY7C68321C only)
■ Complies with ATA/ATAPI-6 Specification
■ Supports 48-bit Addressing for Large Hard Drives
■ Supports ATA Security Features
■ Supports HID Interface or Custom GPIOs to enable features
such as Single Button Backup, Power Off, LED-based Notifi-
cation, and so on
■ 56-Pin QFN and 100-Pin TQFP Pb-free Packages
■ CY7C68321C is Ideal for Battery Powered Designs
■ CY7C68320C is Ideal for Self and Bus Powered Designs
■ Supports any ATA Command with the ATACB Function
■ Supports Mode Page 5 for BIOS Boot Support
■ Supports ATAPI Serial Number VPD Page Retrieval for Digital
Rights Management (DRM) Compatibility
Features (CY7C68300C/CY7C68301C only)
■ Supports PIO Modes 0, 3, and 4, Multiword DMA Mode 2, and
UDMA Modes 2, 3, and 4
■ Pin Compatible with CY7C68300A (using Backward
Compatibility Mode)
■ Uses one small External Serial EEPROM for Storage of USB
Descriptors and Device Configuration Data
■ 56-Pin SSOP and 56-Pin QFN Pb-free Packages
■ CY7C68301C is Ideal for Battery Powered Designs
■ CY7C68300C is Ideal for Self and Bus Powered Designs
■ ATA Interface IRQ Signal Support
■ Supports one or two ATA/ATAPI Devices
Cypress Semiconductor Corporation
Document 001-05809 Rev. *C
•
198 Champion Court
•
San Jose, CA 95134-1709
•
408-943-2600
Revised July 08, 2009
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Logic Block Diagram
SCL
SDA
I2C Bus Master
24
MHz
XTAL
Misc control signals and GPIO
ATA 3-state Control
PLL
Internal Control Logic
ATA Interface
Control
Control Signals
ATA
Interface
Logic
VBUS
D+
D-
USB 2.0
Tranceiver
CY Smart USB
FS/HS Engine
4 kByte FIFO
Data
USB
16 Bit ATA Data
■ ATA/ATAPI master only
■ ATA/ATAPI slave only
Applications
The CY7C68300C/301C and CY7C68320C/321A implement
a USB 2.0 bridge for all ATA/ATAPI-6 compliant mass storage
devices, such as the following:
■ ATA/ATAPI master and ATA/ATAPI slave
■ CompactFlash only
■ Hard drives
■ ATA/ATAPI slave and CompactFlash or other removable IDE
■ CD-ROM, CD-R/W
■ DVD-ROM, DVD-RAM, DVD±R/W
■ MP3 players
master
Additional Resources
■ CY4615C EZ-USB AT2LP Reference Design Kit
■ USB Specification version 2.0
■ Personal media players
■ CompactFlash
■ ATA Specification T13/1410D Rev 3B
■ Microdrives
■ USB Mass Storage Class Bulk Only Transport Specification
http://www.usb.org/devel-
opers/devclass_docs/usbmassbulk_10.pdf
■ Tape drives
■ Personal video recorders
The CY7C68300C/301C and CY7C68320C/321A support one
or two devices in the following configurations:
Document 001-05809 Rev. *C
Page 2 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
signature is 0x534B, the AT2LP configures itself with the AT2LP
pinout and begins normal mass storage operation.
Introduction
The EZ-USB AT2LP™ (CY7C68300C/CY7C68301C and
Refer to the logic flow in Figure 1 for more information on the
pinout selection process.
CY7C68320C/CY7C68321C) implements
a
fixed-function
bridge between one USB port and one or two ATA- or
ATAPI-based mass storage device ports. This bridge adheres to
the Mass Storage Class Bulk-Only Transport Specification (BOT)
and is intended for bus and self powered devices.
Most designs that use the AT2 can migrate to the AT2LP with no
changes to either the board layout or EEPROM data. Cypress
has published an application note focused on migrating from the
AT2 to the AT2LP to help expedite the process. It can be
downloaded from the Cypress website (http://www.cypress.com)
or obtained through a Cypress representative.
The AT2LP is the latest addition to the Cypress USB mass
storage portfolio, and is an ideal cost- and power-reduction path
for designs that previously used Cypress’s ISD-300A1,
ISD-300LP, or EZ-USB AT2.
Figure 1. Simplified Pinout Selection Flowchart
Specifically, the CY7C68300C/CY7C68301C includes a mode
that makes it pin-for-pin compatible with the EZ-USB AT2
(CY7C68300A).
Read EEPROM
The
USB
port
of
the
CY7C68300C/301C
and
CY7C68320C/321A (AT2LP) are connected to a host computer
directly or with the downstream port of a USB hub. Software on
the USB host system issues commands and sends data to the
AT2LP and receives status and data from the AT2LP using
standard USB protocol.
EEPROM
Signature
No
The ATA/ATAPI port of the AT2LP is connected to one or two
mass storage devices. A 4 KB buffer maximizes ATA/ATAPI data
transfer rates by minimizing losses due to device seek times. The
ATA interface supports ATA PIO modes 0, 3, and 4, multiword
DMA mode 2, and Ultra DMA modes 2, 3, and 4.
0x4D4D?
Yes
The device initialization process is configurable, enabling the
AT2LP to initialize ATA/ATAPI devices without software inter-
vention.
Set
Set
EZ-USB AT2
(CY7C68300A)
Pinout
EZ-USB AT2LP
(CY7C68300B)
Pinout
CY7C68300A Compatibility
As mentioned in the previous section, the CY7C68300C/301C
contains a backward compatibility mode that enables it to be
used in existing EZ-USB AT2 (CY7C68300A) designs. The
backward compatibility mode is enabled by programming the
EEPROM with the CY7C68300A signature.
Normal Operation
During startup, the AT2LP checks the I2C™ bus for an EEPROM
with a valid signature in the first two bytes. If the signature is
0x4D4D, the AT2LP configures itself for pin-to-pin compatibility
with the AT2 and begins normal mass storage operation. If the
Document 001-05809 Rev. *C
Page 3 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Pin Diagrams
The AT2LP is available in different package types to meet a variety of design needs. The CY7C68320C/321C is available in 56-pin
QFN and 100-pin TQFP packages to provide the greatest flexibility for new designs. The CY7C68300C/301C is available in 56-pin
SSOP and QFN package types to ensure backward compatibility with CY7C68300A designs.
Figure 2. 56-Pin SSOP Pinout (CY7C68300C/CY7C68301C only)
1
56
55
54
53
52
51
50
49
48
47
46
45
44
43
42
41
40
39
38
37
36
35
34
33
32
31
30
29
DD13
DD12
2
DD14
DD11
3
DD15
DD10
4
GND
DD9
5
ATAPUEN (GND)
VCC
DD8
6
(ATA_EN ) VBUS_ATA_ENABLE
7
GND
VCC
8
IORDY
DMARQ
AVCC
RESET#
9
GND
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
ARESET#
XTALOUT
XTALIN
AGND
( VBUS_PWR_ VALID) DA2
CS1#
CS0#
VCC
(DA2 ) DRVPWRVLD
DPLUS
DMINUS
GND
DA1
DA0
INTRQ
VCC
VCC
GND
DMACK #
DIOR#
DIOW #
GND
PWR500 # ( PU10K)
GND(Reserved )
SCL
SDA
VCC
VCC
GND
DD0
DD7
DD1
DD6
DD2
DD5
DD3
DD4
NOTE: Labels in italics denote pin functionality
during CY7C68300A compatibility mode.
Document 001-05809 Rev. *C
Page 4 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Figure 3. 56-Pin QFN Pinout (CY7C68300C/CY7C68301C)
IORDY
DMARQ
AVCC
1
2
3
4
5
6
7
8
9
42 RESET#
41 GND
40 ARESET#
39 DA2 (VBUS_PWR_VALID)
38 CS1#
XTALOUT
XTALIN
AGND
37 CS0#
VCC
36 DRVPWRVLD (DA2)
35 DA1
DPLUS
DMINUS
34 DA0
GND 10
VCC 11
33 INTRQ
32 VCC
GND 12
31 DMACK#
30 DIOR#
(PU10K) PWR500# 13
GND 14
29 DIOW#
Document 001-05809 Rev. *C
Page 5 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Figure 4. 56-Pin SSOP Pinout (CY7C68320C/CY7C68321C)
1
56
55
54
53
52
51
50
49
48
47
46
45
44
43
42
41
40
39
38
37
36
35
34
33
32
31
30
29
DD13
DD14
DD15
GND
DD12
DD11
2
3
DD10
4
DD9
5
GPIO2
VCC
DD8
6
VBUS_ATA_ENABLE
VCC
7
GND
8
IORDY
DMARQ
AVCC
XTALOUT
XTALIN
AGND
VCC
RESET#
GND
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
ARESET#
DA2
CS1#
CS0#
GPIO0
DA1
DPLUS
DMINUS
GND
DA0
INTRQ
VCC
VCC
GND
DMACK#
DIOR#
DIOW#
GND
GPIO1
GND
SCL
SDA
VCC
VCC
GND
DD0
DD7
DD1
DD6
DD2
DD5
DD3
DD4
Document 001-05809 Rev. *C
Page 6 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Figure 5. 56-Pin QFN Pinout (CY7C68320C/CY7C68321C)
IORDY
DMARQ
AVCC
1
2
3
4
5
6
7
8
9
42 RESET#
41 GND
40 ARESET#
39 DA2
XTALOUT
XTALIN
AGND
38 CS1#
37 CS0#
36 GPIO0
35 DA1
VCC
DPLUS
DMINUS
34 DA0
GND 10
VCC 11
GND 12
GPIO1 13
GND 14
33 INTRQ
32 VCC
31 DMACK#
30 DIOR#
29 DIOW#
Document 001-05809 Rev. *C
Page 7 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Figure 6. 100-Pin TQFP Pinout (CY7C68320C/CY7C68321C only)
1
80
79
78
77
76
75
74
73
72
71
70
69
68
67
66
65
64
63
62
61
60
59
58
57
56
55
54
53
52
51
VCC
GND
IORDY
DMARQ
GND
GND
GND
GND
AVCC
XTALOUT
XTALIN
AGND
NC
NC
NC
VCC
DPLUS
DMINUS
GND
VCC
GND
SYSIRQ
GND
GND
GND
PWR500#
GND
DD8
2
VBUS_ATA_ENABLE
3
VCC
RESET#
NC
GND
ARESET#
DA2
4
5
6
7
8
9
CS1#
CS0#
DRVPWRVLD
DA1
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
DA0
INTRQ
VCC
GND
NC
NC
VBUSPWRD
NC
NC
NC
LOWPWR#
NC
DMACK#
DIOR#
DIOW#
VCC
NC
SCL
SDA
NC
NC
Document 001-05809 Rev. *C
Page 8 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Pin Descriptions
The following table lists the pinouts for the 56-pin SSOP, 56-pin QFN, and 100-pin TQFP package options for the AT2LP. Refer to the
“Pin Diagrams” on page 4 for differences between the 68300C/01C and 68320C/321C pinouts for the 56-pin packages. For information
on the CY7C68300A pinout, refer to the CY7C68300A data sheet that is found in the ’EZ-USB AT2’ folder of the CY4615C reference
design kit CD.
Table 1. AT2LP Pin Descriptions
Note: (Italic pin names denote pin functionality during CY7C68300A compatibility mode)
100
56
56
Pin DefaultState
Pin Name
Pin Description
TQFP QFN SSOP
Type
PWR
GND
I[1]
at Startup
1
2
3
4
55
56
1
6
7
VCC
GND
VCC. Connect to 3.3V power source.
Ground.
8
IORDY
DMARQ
GND
Input
Input
ATA control. Apply a 1k pull up to 3.3V.
ATA control.
2
9
I[1]
5
6
7
8
N/A
N/A
Ground.
9
3
4
10
11
AVCC
XTALOUT
XTALIN
AGND
NC
PWR
Xtal
Analog VCC. Connect to VCC through the shortest path
possible.
10
11
12
Xtal
Xtal
24 MHz crystal output. (See “XTALIN, XTALOUT” on
page 12).
5
12
Xtal
24 MHz crystal input. (See “XTALIN, XTALOUT” on
page 12).
6
13
GND
Analog ground. Connect to ground with as short a
path as possible.
13
14
15
N/A
N/A
No connect.
16
17
18
19
20
21
22
7
8
14
15
VCC
DPLUS
DMINUS
GND
PWR
I/O
VCC. Connect to 3.3V power source.
USB D+ signal (See “DPLUS, DMINUS” on page 12).
USB D–signal (See “DPLUS, DMINUS” on page 12).
Ground.
Hi-Z
Hi-Z
9
16
I/O
10
11
12
N/A
17
GND
PWR
GND
I
18
VCC
VCC. Connect to 3.3V power source.
Ground.
19
GND
N/A
SYSIRQ
Input
USB interrupt request. (See “SYSIRQ” on page 13).
Active HIGH. Connect to GND if functionality is not
used.
23
24
25
26[3]
N/A
N/A
20
GND
GND
O
Ground.
13[3]
PWR500#[2]
bMaxPower request granted indicator. (See
(PU 10K)
“PWR500#” on page 14). Active LOW.
N/A for CY7C68320C/CY7C68321C 56-pin packages.
27
14
21
GND (RESERVED)
Reserved. Tie to GND.
Notes
1. If byte 8, bit 4 of the EEPROM is set to ‘0’, the ATA interface pins are only active when VBUS_ATA_EN is asserted. See “VBUS_ATA_ENABLE” on page 14.
2. A ‘#’ sign after the pin name indicates that it is active LOW.
3. The General Purpose inputs can be enabled on ATAPUEN, PWR500#, and DRVPWRVLD via EEPROM byte 8, bit 7 on CY7C68320C/CY7C68321C.
Document 001-05809 Rev. *C
Page 9 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Table 1. AT2LP Pin Descriptions
Note: (Italic pin names denote pin functionality during CY7C68300A compatibility mode) (continued)
100
56
56
Pin DefaultState
Pin Name
Pin Description
TQFP QFN SSOP
Type
at Startup
28
29
N/A
15
N/A
22
NC
No connect.
SCL
O
Active for Clock signal for I2C interface. (See “SCL, SDA” on
several ms at page 12). Apply a 2.2k pull up resistor.
startup.
30
16
23
SDA
NC
I/O
Data signal for I2C interface. (See “SCL, SDA” on
page 12).
Apply a 2.2k pull up resistor.
31
32
N/A
N/A
No connect.
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
17
18
24
25
VCC
DD0
DD1
DD2
DD3
VCC
GND
NC
PWR
I/O[1]
I/O[1]
I/O[1]
I/O[1]
PWR
GND
NC
VCC. Connect to 3.3V power source.
Hi-Z
Hi-Z
Hi-Z
Hi-Z
ATA data bit 0.
19
26
ATA data bit 1.
20
27
ATA data bit 2.
21
28
ATA data bit 3.
N/A
N/A
N/A
N/A
N/A
N/A
22
N/A
N/A
N/A
N/A
N/A
N/A
29
VCC. Connect to 3.3V power source.
Ground.
No connect.
GND
NC
Ground.
NC
No connect.
GND
DD4
DD5
DD6
DD7
GND
VCC
GND
NC
Ground.
I/O[1]
I/O[1]
I/O[1]
I/O[1]
GND
PWR
GND
NC
Hi-Z
Hi-Z
Hi-Z
Hi-Z
ATA data bit 4.
23
30
ATA data bit 5.
24
31
ATA data bit 6.
25
32
ATA data bit 7. Apply a 1k pull down to GND.
Ground.
26
33
27
34
VCC. Connect to 3.3V power source.
Ground.
28
35
51
52
N/A
N/A
No connect.
53
54
N/A
29
N/A
36
VCC
DIOW#[2]
PWR
VCC. Connect to 3.3V power source.
O/Z[1] Driven HIGH ATA control.
(CMOS)
55
56
30
31
37
38
DIOR#
O/Z[1] Driven HIGH ATA control.
(CMOS)
DMACK#
O/Z[1] Driven HIGH ATA control.
(CMOS)
57
58
N/A
N/A
N/A
N/A
NC
NC
O
No connect.
LOWPWR#
USB suspend indicator. (See “LOWPWR#” on
page 14).
59
60
61
N/A
N/A
N/A
N/A
NC
NC
I
No connect.
62
VBUSPWRD
Input
Bus powered mode selector. (See “VBUSPWRD” on
page 14).
Document 001-05809 Rev. *C
Page 10 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Table 1. AT2LP Pin Descriptions
Note: (Italic pin names denote pin functionality during CY7C68300A compatibility mode) (continued)
100
56
56
Pin DefaultState
Pin Name
Pin Description
TQFP QFN SSOP
Type
at Startup
63
64
N/A
N/A
NC
NC
No connect.
Ground.
65
66
67
68
N/A
32
N/A
39
GND
VCC
GND
PWR
I[1]
VCC. Connect to 3.3V power source.
ATA interrupt request.
33
40
INTRQ
DA0
Input
34
41
O/Z[1] Driven HIGH ATA address.
after 2 ms
delay
69
35
42
43
DA1
O/Z[1] Driven HIGH ATA address.
after 2 ms
delay
70[3]
36[3]
DRVPWRVLD
I
Input
Device presence detect. (See “DRVPWRVLD” on
page 14). Configurable logical polarity is controlled by
EEPROM address 0x08. This pin must be pulled HIGH
if functionality is not utilized.
(DA2)
Alternate function. Input when the EEPROM configu-
ration byte 8 has bit 7 set to one. The input value is
reported through EP1IN (byte 0, bit 0).
71
72
73
37
38
39
44
45
46
CS0#
CS1#
O/Z[1] Driven HIGH ATA chip select.
after 2 ms
delay
O/Z[1] Driven HIGH ATA chip select.
after 2 ms
delay
O/Z[1] Driven HIGH ATA address.
DA2
(VBUS_PWR_VALID)
after 2 ms
delay
74
75
76
77
78
79
40
41
47
48
ARESET#
GND
O/Z[1]
GND
NC
I
ATA reset.
Ground.
N/A
42
N/A
49
NC
No connect.
RESET#
VCC
Input
Input
Chip reset (See “RESET#” on page 15).
VCC. Connect to 3.3V power source.
43
50
PWR
I
44
51
VBUS_ATA_ENABLE
VBUS detection (See “VBUS_ATA_ENABLE” on
page 14).
(ATA_EN)
80
81
82
83
84
85
45
46
52
53
DD8
DD9
DD10
DD11
GND
VCC
I/O[1]
I/O[1]
I/O[1]
I/O[1]
Hi-Z
Hi-Z
Hi-Z
Hi-Z
ATA data bit 8.
ATA data bit 9.
47
54
ATA data bit 10.
ATA data bit 11.
Ground.
48
55
N/A
N/A
N/A
N/A
N/A
N/A
PWR
NC
VCC. Connect to 3.3V power source.
No connect.
86
87
NC
88
89
90
91
92
93
36[3]
13[3]
54[3]
N/A
GPIO0
GPIO1
GPIO2
GPIO3
GPIO4
GPIO5
I/O[3]
General purpose I/O pins (See “GPIO Pins” on
page 14). The GPIO pins must be tied to GND if
functionality is not used.
Document 001-05809 Rev. *C
Page 11 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Table 1. AT2LP Pin Descriptions
Note: (Italic pin names denote pin functionality during CY7C68300A compatibility mode) (continued)
100
56
56
Pin DefaultState
Pin Name
Pin Description
TQFP QFN SSOP
Type
GND
I/O[1]
I/O[1]
I/O[1]
I/O[1]
GND
I/O
at Startup
94
95
96
97
98
99
N/A
49
50
51
52
53
N/A
56
1
GND
DD12
DD13
DD14
DD15
GND
Ground.
Hi-Z
Hi-Z
Hi-Z
Hi-Z
ATA data bit 12.
ATA data bit 13.
ATA data bit 14.
ATA data bit 15.
Ground.
2
3
4
100[3] 54[3]
5
ATAPUEN
Bus-powered ATA pull up voltage source (see
(NC)
“ATAPUEN” on page 14).
Alternate function: General purpose input when the
EEPROM configuration byte 8 has bit 7 set to ‘1’. The
input value is reported through EP1IN (byte 0, bit 2).
Additional Pin Descriptions
The following sections provide additional pin information.
XTALIN, XTALOUT
The AT2LP requires a 24 MHz (±100 ppm) signal to derive
internal timing. Typically, a 24 MHz (12 pF, 500 μW,
parallel-resonant, fundamental mode) crystal is used, but a
24 MHz square wave (3.3V, 50/50 duty cycle) from another
source can also be used. If a crystal is used, connect its pins
to XTALIN and XTALOUT, and also through 12 pF capacitors
to GND as shown in Figure 7. If an alternate clock source is
used, apply it to XTALIN and leave XTALOUT unconnected.
DPLUS, DMINUS
DPLUS and DMINUS are the USB signaling pins; they must
be tied to the D+ and D– pins of the USB connector. Because
they operate at high frequencies, the USB signals require
special consideration when designing the layout of the PCB.
See “General PCB Layout Recommendations for USB Mass
Storage Designs” on page 39 for PCB layout recommenda-
tions.
Figure 7. XTALIN/XTALOUT Diagram
When RESET# is released, the assertion of the internal pull
up on D+ is gated by a combination of the state of the
VBUS_ATA_ENABLE pin, the value of configuration address
0x08 bit 0 (DRVPWRVLD Enable), and the detection of a
non-removable ATA/ATAPI drive on the IDE bus. See Table 2
for a description of this relationship.
24MHz Xtal
12pF
12pF
Table 2. D+ Pull Up Assertion Dependencies
VBUS_ATA_EN
DRVPWRVLD Enable Bit
ATA/ATAPI Drive Detected
State of D+ pull up
1
1
1
1
0
0
1
1
0
0
1
1
Yes
No
Yes
No
Yes
No
1
1
1
0
0
0
XTALIN
XTALOUT
SCL, SDA
The clock and data pins for the I2C port must be connected to
the configuration EEPROM and to 2.2K pull up resistors tied
to VCC. If no EEPROM is used in the design, the SCL and SDA
pins must still be connected to pull up resistors. The SCL and
SDA pins are active for several milliseconds at startup.
Document 001-05809 Rev. *C
Page 12 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
SYSIRQ
0x09 of the configuration data. The state of any GPIO pin that is
not set as an input is reported as ‘0’ in the EP1 data.
The SYSIRQ pin provides a way for systems to request service
from host software by using the USB Interrupt pipe on endpoint
1 (EP1). If the AT2LP has no pending interrupt data to return,
USB interrupt pipe data requests are NAKed. If pending data is
available, the AT2LP returns 16 bits of data. This data indicates
whether AT2LP is operating in high speed or full speed, whether
the AT2LP is reporting self-powered or bus-powered operation,
and the states of any GPIO pins that are configured as inputs.
GPIO pins can be individually set as inputs or outputs, with byte
Table 3 gives the bitmap for the data returned on the interrupt
pipe and Figure 8 depicts the latching algorithm incorporated by
the AT2LP.
The SYSIRQ pin must be pulled LOW if HID functionality is used.
Refer to “HID Functions for Button Controls” on page 15 for more
details on HID functionality.
Table 3. Interrupt Data Bitmap
EP1 Data Byte 1
EP1 Data Byte 0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
Figure 8. SYSIRQ Latching Algorithm
No
No
USB Interrupt
Pipe Polled?
SYSIRQ=1?
Yes
Yes
Latch State of IO Pins
Set Int_Data = 1
Yes
Int_Data = 1?
No
No
NAK Request
Yes
Int_Data = 0
and
SYSIRQ=0?
Return Interrupt Data
Set Int_Data = 0
Document 001-05809 Rev. *C
Page 13 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
DRVPWRVLD
AT2LP releases the pull up on D+ as required by the USB speci-
fication.
When this pin is enabled with bit 0 of configuration address 0x08
(DRVPWRVLD Enable), the AT2LP informs the host that a
removable device, such as a CF card, is present. The AT2LP
uses DRVPWRVLD to detect that the removable device is
present. Pin polarity is controlled by bit 1 of configuration
address 0x08. When DRVPWRVLD is deasserted, the AT2LP
reports a “no media present” status (ASC = 0x3A, ASQ = 0x00)
when queried by the host. When the media has been detected
again, the AT2LP reports a “media changed” status to the host
(ASC = 0x28, ASQ = 0x00) when queried.
Also, if bit 4 of configuration address 0x08 is ‘1’, the ATA interface
pins are placed in a Hi-Z state when VBUS_ATA_ENABLE is ‘0’.
If bit 4 of configuration address 0x08 is ‘0’, the ATA interface pins
are still driven when VBUS_ATA_ENABLE is ‘0’.
ATAPUEN
This output can be used to control the required host pull up
resistors on the ATA interface in a bus-powered design to
minimize unnecessary power consumption when the AT2LP is in
suspend. ATAPUEN is driven to ‘0’ when the ATA bus is inactive.
ATAPUEN is driven to ‘1’ when the ATA bus is active. ATAPUEN
is set to a Hi-Z state along with all other ATA interface pins if
VBUS_ATA_ENABLE is deasserted and the ATA_EN function-
ality (bit 4 of configuration address 0x08) is enabled (0).
When a removable device is used, it is always considered by the
AT2LP to be the IDE master device. Only one removable device
may be attached to the AT2LP. If the system only contains a
removable device, bit 6 of configuration address 0x08 (Search
ATA Bus) must be set to ‘0’ to disable ATA device detection at
startup. If a non-removable device is connected in addition to a
removable media device, the non-removable device must be
configured as IDE slave (device address 1).
ATAPUEN can also be configured as a GPIO input. See “HID
Functions for Button Controls” on page 15 for more information
on HID functionality.
GPIO Pins
PWR500#
The GPIO pins enable a general purpose input and output
interface. There are several different interfaces to the GPIO pins:
The AT2LP asserts PWR500# to indicate that VBUS current may
be drawn up to the limit specified by the bMaxPower field of the
USB configuration descriptors. If the AT2LP enters a low-power
state, PWR500# is deasserted. When normal operation is
resumed, PWR500# is restored. The PWR500# pin must never
be used to control power sources for the AT2LP. In the 56-pin
package, PWR500# only functions during bus-powered
operation.
■ Configuration bytes 0x09 and 0x0A contain the default settings
for the GPIO pins upon initial AT2LP configuration.
■ The host can modify the settings of the GPIO pins during
operation. This is done with vendor-specific commands
described in “Programming the EEPROM” on page 34.
PWR500# can also be configured as a GPIO input. See “HID
Functions for Button Controls” on page 15 for more information
on HID functionality.
■ ThestatusoftheGPIOpinsisreturnedontheinterruptendpoint
(EP1) in response to a SYSIRQ. See “SYSIRQ” on page 13 for
SYSIRQ details.
VBUSPWRD
LOWPWR#
VBUSPWRD is used to indicate self- or bus-powered operation.
Some designs require the ability to operate in either self- or
bus-powered modes. The VBUSPWRD input pin enables these
devices to switch between self-powered and bus-powered
modes by changing the contents of the bMaxPower field and the
self-powered bit in the reported configuration descriptors (see
Table 4).
LOWPWR# is an output pin that is driven to ‘0’ when the AT2LP
is not in suspend. LOWPWR# is placed in Hi-Z when the AT2LP
is in a suspend state. This pin only indicates the state of the
AT2LP and must not be used to determine the status of the USB
host because of variations in the behavior of different hosts.
ATA Interface Pins
The ATA Interface pins must be connected to the corresponding
pins on an IDE connector or mass storage device. To enable
sharing of the IDE bus with other master devices, the AT2LP can
place all ATA Interface Pins in a Hi-Z state whenever
VBUS_ATA_ENABLE is not asserted. Enabling this feature is
done by setting bit 4 of configuration address 0x08 to ‘1’.
Otherwise, the ATA bus is driven by the AT2LP to a default
inactive state whenever VBUS_ATA_ENABLE is not asserted.
Note that current USB host drivers do not poll the device for this
information, so the effect of this pin is only seen on a USB or
power on reset.
Table 4. Behavior of Descriptor Data that is Dependent Upon
VBUSPWRD State
VBUSPWRD
N/A (56-pin)
Pin
VBUSPWRD = ‘1’ VBUSPWRD = ‘0’
Design practices for signal integrity as outlined in the
ATA/ATAPI-6 specification must be followed with systems that
utilize a ribbon cable interconnect between the AT2LP’s ATA
interface and the attached mass storage device, especially if
Ultra DMA Mode is used.
bMaxPower
Reported
Value
0xFA
0x01
The value
from configu-
ration
(500 mA)
(2 mA)
address0x34
is used.
bmAttributes
bit 6
Reported
Value
‘0’
‘1’
‘0’ if
bMaxPower>
0x01
‘1’ if
bMaxPower≤
0x01
(bus-powered)
(self-powered)
VBUS_ATA_ENABLE
VBUS_ATA_ENABLE is typically used to indicate to the AT2LP
that power is present on VBUS. This pin is polled by the AT2LP
at startup and then every 20 ms thereafter. If this pin is ‘0’, the
Document 001-05809 Rev. *C
Page 14 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
RESET#
HID Functions for Button Controls
Asserting RESET# for 10 ms resets the entire AT2LP. In
self-powered designs, this pin is normally tied to VCC through a
100k resistor, and to GND through a 0.1 μF capacitor, as shown
in Figure 9.
Cypress’s CY7C68320C/CY7C68321C has the capability of
supporting Human Interface Device (HID) signaling to the host.
If there is a HID descriptor in the configuration data, the GPIO
pins that are set as inputs are polled by the AT2LP logic approx-
imately every 17 ms (depending on other internal interrupt
routines). If a change is detected in the state of any HID-enabled
GPIO, an HID report is sent through EP1 to the host. The report
format for byte 0 and byte 1 are shown in Table 5.
Cypress does not recommend an RC reset circuit for
bus-powered devices because of the potential for VBUS voltage
drop, which may result in a startup time that exceeds the USB
limit. Refer to the application note titled EZ-USB
FX2™/AT2™/SX2™ Reset and Power Considerations, at
www.cypress.com, for more information.
The ability to add buttons to a mass storage solution opens new
applications for data backup and other device-side notification to
the host. The AT2LP Blaster software, found in the CY4615C
files, provides an easy way to enable and modify the HID
features of the AT2LP.
While the AT2LP is in reset, all pins are held at their default
startup state.
Figure 9. R/C Reset Circuit for Self-Powered Designs
GPIO pins can be individually set as inputs or outputs, with byte
0x09 of the configuration data, enabling a mix of HID and general
purpose outputs. GPIOs that are not configured as inputs are
reported with a value of ‘0’ in the HID data. The RESERVED bits’
values must be ignored, and Cypress recommends using a
bitmask in software to filter out unused HID data.
100KΩ
RESET#
0.1μF
Note that if using the 56-pin package, the reported GPIO[5:3]
values must be ignored because the pins are not actually
present.
Table 5. HID Data Bitmap
USB Interrupt Data Byte 1
USB Interrupt Data Byte 0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
Functional Overview
Chip functionally is described in the subsequent sections.
Additionally, the AT2LP translates ATAPI SFF-8070i commands
to ATA commands for seamless integration of ATA devices with
generic Mass Storage Class BOT drivers.
USB Signaling Speed
AT2LP operates at the following two rates defined in the USB
Specification Revision 2.0 dated April 27, 2000:
ATA Command Block (ATACB)
The ATA Command Block (ATACB) functionality provides a
means of passing ATA commands and ATA register accesses to
the attached device for execution. ATACB commands are trans-
ferred in the Command Block Wrapper Command Block
(CBWCB) portion of the Command Block Wrapper (CBW). The
ATACB is distinguished from other command blocks by having
the first two bytes of the command block match the bVSCBSig-
nature and bVSCBSubCommand values that are defined in
Table 6. Only command blocks that have a valid bVSCBSig-
nature and bVSCBSubCommand are interpreted as ATA
Command Blocks. All other fields of the CBW and restrictions on
the CBWCB remain as defined in the USB Mass Storage Class
Bulk-Only Transport Specification. The ATACB must be 16 bytes
in length. The following table and text defines the fields of the
ATACB.
■ Full speed, with a signaling bit rate of 12 Mbits/sec.
■ High speed, with a signaling bit rate of 480 Mbits/sec.
AT2LP does not operate at the low-speed signaling rate of 1.5
Mbits/sec.
ATA Interface
The ATA/ATAPI port on the AT2LP is compatible with the Infor-
mation Technology–AT Attachment with Packet Interface–6
(ATA/ATAPI-6) Specification, T13/1410D Rev 2a. The AT2LP
supports both ATAPI packet commands as well as ATA
commands (by use of ATA Command Blocks), as outlined in
“ATA Command Block (ATACB)” on page 15. Refer to the USB
Mass Storage Class (MSC) Bulk Only Transport (BOT) Specifi-
cation for information on Command Block formatting.
Document 001-05809 Rev. *C
Page 15 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Table 6. ATACB Field Descriptions
Byte
Field Name
bVSCBSignature
Field Description
0
This field indicates to the CY7C68300C/CY7C68301C that the ATACB
contains a vendor-specific command block. This value of this field must match
the value in EEPROM address 0x04 for the command to be recognized as a
vendor-specific ATACB command.
1
2
bVSCBSubCommand
bmATACBActionSelect
This field must be set to 0x24 for ATACB commands.
This field controls the execution of the ATACB according to the bitfield values:
Bit 7 IdentifyPacketDevice – This bit indicates that the data phase of the
command contains ATAPI (0xA1) or ATA (0xEC) IDENTIFY device data.
Setting IdentifyPacketDevice when the data phase does not contain IDENTIFY
device data results in unspecified device behavior.
0 = Data phase does not contain IDENTIFY device data
1 = Data phase contains ATAPI or ATA IDENTIFY device data
Bit 6 UDMACommand – This bit enables supported UDMA device transfers.
Setting this bit when a non-UDMA capable device is attached results in
undetermined behavior.
0 = Do not use UDMA device transfers (only use PIO mode)
1 = Use UDMA device transfers
Bit 5 DEVOverride – This bit determines whether the DEV bit value is taken
from the value assigned to the LUN during startup or from the ATACB.
0 = The DEV bit is taken from the value assigned to the LUN during startup
1 = The DEV bit is taken from the ATACB field 0x0B, bit 4
Bit 4 DErrorOverride – This bit controls the device error override feature. This
bit must not be set during a bmATACBActionSelect TaskFileRead.
0 = Data accesses are halted if a device error is detected
1 = Data accesses are not halted if a device error is detected
Bit 3 PErrorOverride – This bit controls the phase error override feature. This
bit must not be set during a bmATACBActionSelect TaskFileRead.
0 = Data accesses are halted if a phase error is detected
1 = Data accesses are not halted if a phase error is detected
Bit 2 PollAltStatOverride – This bit determines whether or not the Alternate
Status register is polled and the BSY bit is used to qualify the ATACB operation.
0 = The AltStat register is polled until BSY=0 before proceeding with the ATACB
operation
1 = The ATACB operation is executed without polling the AltStat register.
Bit 1 DeviceSelectionOverride – This bit determines when the device selection
is performed in relation to the command register write accesses.
0 = Device selection is performed before command register write accesses
1 = Device selection is performed following command register write accesses
Bit 0 TaskFileRead – This bit determines whether or not the taskfile register
data selected in bmATACBRegisterSelect is returned. If this bit is set, the
dCBWDataTransferLength field must be set to 8.
0 = Execute ATACB command and data transfer (if any)
1 = Only read taskfile registers selected in bmATACBRegisterSelect and return
0x00h for all others. The format of the 8 bytes of returned data is as follows:
❐ Address offset 0x00 (0x3F6) – Alternate Status
❐ Address offset 0x01 (0x1F1) – Features/Error
❐ Address offset 0x02 (0x1F2) – Sector Count
❐ Address offset 0x03 (0x1F3) – Sector Number
❐ Address offset 0x04 (0x1F4) – Cylinder Low
❐ Address offset 0x05 (0x1F5) – Cylinder High
❐ Address offset 0x06 (0x1F6) – Device/Head
❐ Address offset 0x07 (0x1F7) – Command/Status
Document 001-05809 Rev. *C
Page 16 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Table 6. ATACB Field Descriptions (continued)
Byte
Field Name
Field Description
3
bmATACBRegisterSelect
This field controls which of the taskfile register read or write accesses occur.
Taskfile read data is always 8 bytes in length, and unselected register data are
returned as 0x00. Register accesses occur in sequential order as outlined here
(0 to 7):
Bit 0 (0x3F6) Device Control/Alternate Status
Bit 1 (0x1F1) Features/Error
Bit 2 (0x1F2) Sector Count
Bit 3 (0x1F3) Sector Number
Bit 4 (0x1F4) Cylinder Low
Bit 5 (0x1F5) Cylinder High
Bit 6 (0x1F6) Device/Head
Bit 7 (0x1F7) Command/Status
4
bATACBTransferBlockCount
bATACBTaskFileWriteData
This value indicates the maximum requested block size be in 512-byte incre-
ments. This value must be set to the last value used for the ’Sectors per block’
in the SET_MULTIPLE_MODE command. Legal values are 0, 1, 2, 4, 8, 16,
32, 64, and 128 where 0 indicates 256 sectors per block. A command failed
status is returned if an illegal value is used in the ATACB.
5–12
These bytes contain ATA register data used with ATA command or PIO write
operations. Only registers selected in bmATACBRegisterSelect are required to
hold valid data when accessed. The registers are as follows.
ATACB Address Offset 0x05 (0x3F6) – Device Control
ATACB Address Offset 0x06 (0x1F1) – Features
ATACB Address Offset 0x07 (0x1F2) – Sector Count
ATACB Address Offset 0x08 (0x1F3) – Sector Number
ATACB Address Offset 0x09 (0x1F4) – Cylinder Low
ATACB Address Offset 0x0A (0x1F5) – Cylinder High
ATACB Address Offset 0x0B (0x1F6) – Device
ATACB Address Offset 0x0C (0x1F7) – Command
These bytes must be set to 0x00 for ATACB commands.
13–15
Reserved
Document 001-05809 Rev. *C
Page 17 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Operating Modes
The different modes of operation and EEPROM information are presented in the following sections.
Operational Mode Selection Flow
During the power up sequence, the AT2LP queries the I2C bus for an EEPROM. The AT2LP then selects a pinout configuration as
shown here, and checks to see if ARESET# is configured for Board Manufacturing Test Mode.
■ If no EEPROM is detected, the AT2LP uses the values in the factory-programmable (fused) memory space. See “Fused Memory
Data” on page 19 for more information. This is not a valid mode of operation if no factory programming has been done.
■ If an EEPROM signature of 0x4D4D is found, the CY7C68300C/CY7C68301C uses the same pinout and EEPROM format as the
CY7C68300A (EZ-USB AT2+).
■ If an EEPROM signature of 0x534B is found, the AT2LP uses the values stored in the EEPROM to configure the USB descriptors
for normal operation.
■ If an EEPROM is detected, but an invalid signature is read, the AT2LP defaults into Board Manufacturing Test Mode.
Figure 10. Operational Mode Selection Flow
Check I2C Bus
No
EEPROM
Found?
Yes
No
Signature
0x534B?
Signature
0x4D4D?
Yes
Yes
Set
Load Fused
Memory Data
(AT2LP Pinout)
Set
EZ-USB AT2+
(CY7C68300A)
Pinout
EZ-USB AT2LP
Pinout
No
VBUS_ATA_ENABLE
Pin HIGH?
Yes
No
ARESET#
Pin LOW?
Yes
DD7 Pin Set
HIGH
No
ARESET#
Pin HIGH?
Yes
Normal Mass
Storage Mode
Board Manufacturing
Test Mode
Document 001-05809 Rev. *C
Page 18 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
EEPROM accesses (CfgCB) and one for board level testing
(MfgCB), as described in the following sections.
Fused Memory Data
When no EEPROM is detected at startup, the AT2LP
enumerates with the VID/PID/DID values that are stored in the
fused memory space. These values can be programmed into the
AT2LP during chip manufacturing for high volume applications to
avoid the need for an external EEPROM in some designs.
Contact your local Cypress Semiconductor sales office for more
information on this feature.
There is a convenient method available for starting the AT2LP in
Board Manufacturing Test Mode to enable reprogramming of
EEPROMs without a mass storage device attached. If the ATA
Reset (ARESET#) line is LOW on power up, the AT2LP enters
Board Manufacturing Test Mode. It is recommended that a 10k
resistor be used to pull ARESET# to LOW. An easy way to pull
the ARESET# line LOW is to short pins 1 and 3 on the 40-pin
ATA connector with a 10k resistor, that ties the ARESET# line to
the required pull down on DD7.
If no factory programming has been done, the values returned
from the fused memory space would all be 0x00, which is not a
valid mode of operation. In this case the chip uses the manufac-
turing mode and return the default descriptors (VID/PID of
0x4B4/0x6830). An EEPROM must be used with designs that do
not use factory-programmed chips in order to identify the device
as your company’s product.
CfgCB
The cfg_load and cfg_read vendor-specific commands are
passed down through the bulk pipe in the CBWCB portion of the
CBW. The format of this CfgCB is shown as follows. Byte 0 is a
vendor-specific command designator whose value is config-
urable and set in the configuration data (address 0x04). Byte 1
must be set to 0x26 to identify it as a CfgCB command. Byte2 is
reserved and must be set to zero. Byte 3 is used to determine
the memory source to write/read. For the AT2LP, this byte must
be set to 0x02, indicating the EEPROM is present. Bytes 4 and
5 are used to determine the start address, which must always be
0x0000. Bytes 6 through 15 are reserved and must be set to
zero.
Normal Mass Storage Mode
In Normal Mass Storage Mode, the chip behaves as a USB 2.0
to ATA/ATAPI bridge. This includes all typical USB device states
(powered, configured, etc.). The USB descriptors are returned
according to the values stored in the external EEPROM or fused
memory space. A unique serial number is required for Mass
Storage Class Bulk-Only Transport compliance, which is one
reason why an EEPROM or factory-programmed part is needed.
The data transferred to the EEPROM must be in the format
specified in Table 11 of this data sheet. Maximum data transfer
size is 255 bytes.
Board Manufacturing Test Mode
In Board Manufacturing Test Mode the AT2LP behaves as a USB
2.0 device but the ATA/ATAPI interface is not fully active. This
mode must not be used for mass storage operation in a finished
design. In this mode, the AT2LP enable reading from and writing
to the EEPROM, and for board level testing, through vendor
specific ATAPI commands utilizing the CBW Command Block as
described in the USB Mass Storage Class Bulk-Only Transport
Specification. There is a vendor-specific ATAPI command for
The data transfer length is determined by the CBW Data Transfer
Length specified in bytes 8 through 11 (dCBWDataTransfer-
Length) of the CBW (refer to Table 7). The type/direction of the
command is determined by the direction bit specified in byte 12,
bit 7 (bmCBWFlags) of the CBW (refer to Table 7).
Table 7. Command Block Wrapper
Bits
Offset
7
6
5
4
3
2
1
0
0–3
4–7
DCBWSignature
dCBWTag
8–11 (08h–0Bh)
12 (0Ch)
dCBWDataTransferLength
bwCBWFLAGS
Dir
Obsolete
Reserved (0)
13 (0Dh)
Reserved (0)
Reserved (0)
bCBWLUN
bCBWCBLength
CBWCB (CfgCB or MfgCB)
14 (0Eh)
15–30 (0Fh1Eh)
Document 001-05809 Rev. *C
Page 19 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Table 8. Example CfgCB
Offset
CfgCB Byte Descriptions
Bits
7
0
0
0
0
0
0
0
6
0
0
0
0
0
0
0
5
1
1
0
0
0
0
0
4
0
0
0
0
0
0
0
3
0
0
0
0
0
0
0
2
1
1
0
0
0
0
0
1
0
1
0
1
0
0
0
0
0
0
0
0
0
0
0
0
1
2
3
4
5
bVSCBSignature (set in configuration bytes)
bVSCBSubCommand (must be 0x26)
Reserved (must be set to zero)
Data Source (must be set to 0x02)
Start Address (LSB) (must be set to zero)
Start Address (MSB) (must be set to zero)
6–15 Reserved (must be set to zero)
MfgCB
Mfg_read
The mfg_load and mfg_read vendor-specific commands are
passed down through the bulk pipe in the CBWCB portion of the
CBW. The format of this MfgCB is shown as follows. Byte0 is a
vendor-specific command designator whose value is config-
urable and set in the AT2LP configuration data. Byte 1 must be
0x27 to identify a MfgCB. Bytes 2 through 15 are reserved and
must be set to zero.
This USB request returns a ’snapshot’ of select AT2LP input
pins. AT2LP input pins not directly associated with USB
operation can be sampled at any time during Manufacturing Test
Mode operation. See Table 10 for an explanation of the
Mfg_read data format. Any data length can be specified, but only
bytes 0 through 3 contain usable information, so a length of 4
bytes is recommended.
The data transfer length is determined by the CBW Data Transfer
Length specified in bytes 8 through 11 (dCBWDataTransfer-
Length) of the CBW. The type and direction of the command is
determined by the direction bit specified in byte 12, bit 7
(bmCBWFlags) of the CBW.
Table 10. Mfg_read and Mfg_load Data Format
Byte
Bits
7
Read/Load
Function
ARESET#
0
R/L
R
6
DA2
Table 9. Example MfgCB
5:4
3
R/L
R/L
R/L
R
CS#[1:0]
DRVPWRVLD
DA[1:0]
Offset MfgCB Byte Description
Bits
7 6 5 4 3 2 1 0
0 0 1 0 0 1 0 0
2:1
0
0
1
0 bVSCBSignature
(set in configuration bytes)
INTRQ
1 bVSCBSubCommand
(hardcoded 0x27)
0 0 1 0 0 1 1 1
1
7
L
DD[15:0] High-Z Status
0 = Hi-Z all DD pins
1 = Drive DD pins
2–15 2–15 Reserved (must be zero) 0 0 0 0 0 0 0 0
6
R
MFG_SEL
0 = Mass Storage Mode
1 = Manufacturing Mode
Mfg_load
During a Mfg_load, the AT2LP enters into Manufacturing Test
Mode. Manufacturing Test Mode is provided as a means to
implement board or system level interconnect tests. During
Manufacturing Test Mode operation, all outputs not directly
associated with USB operation are controllable. Normal control
of the output pins are disabled. Control of the select AT2LP I/O
pins and their tri-state controls are mapped to the ATAPI data
packet associated with this request. (See Table 10 for an expla-
nation of the required Mfg_load data format.) Any data length can
be specified, but only bytes 0 through 3 are mapped to pins, so
a length of 4 bytes is recommended. To exit Manufacturing Test
Mode, a hard reset (toggle RESET#) is required.
5
4
R
VBUS_ATA_ENABLE
DMARQ
R
3
R
IORDY
2
R/L
R/L
R/L
R/L
R/L
DMACK#
DIOR#
1
0
DIOW#
2
3
7:0
7:0
DD[7:0]
DD[15:8]
Document 001-05809 Rev. *C
Page 20 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
to program AT2LP-based products in
a manufacturing
EEPROM Organization
environment and provides for serial number randomization. See
“Board Manufacturing Test Mode” on page 19 for details on how
to use vendor-specific ATAPI commands to read and program
the EEPROM.
The contents of the recommended 256-byte (2048-bit) I2C
EEPROM are arranged as follows. In Table 11, the column
labeled ‘Required Contents’ contains the values that must be
used for proper operation of the AT2LP. The column labeled
‘Variable Contents’ contains suggested entries and values that
may vary (such as string lengths) according to the EEPROM
data. Some values, such as the Vendor ID, Product ID and
device serial number, must be customized to meet USB
compliance. The ‘AT2LP Blaster’ tool in the CY4615C kit can be
used to edit and program these values into an AT2LP-based
product (refer to Figure 11). The ‘AT2LP Primer’ tool can be used
The address pins on the serial EEPROM must be set such that
the EEPROM is at physical address 2 (A0 = 0, A1 = 1, A2 = 0)
or address 4 (A0 = 0, A1 = 0, A2 = 1) for EEPROM devices that
are internally byte-addressed memories. It is recommended that
the address pins be set this way even on EEPROMs that may
indicate that the address pins are internal no-connects.
Figure 11. Snapshot of ‘AT2LP Blaster’ Utility
Document 001-05809 Rev. *C
Page 21 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Table 11. Configuration Data Organization
Byte
Address
Configuration
Item Name
Configuration
Item Description
Required Variable
Contents Contents
Note Devices running in Backward Compatibility (CY7C68300A) Mode must use the CY7C68300A EEPROM organization, and
not the format shown in this document. Refer to the CY7C68300A data sheet for the CY7C68300A EEPROM format.
AT2LP Configuration
0x00
0x01
0x02
EEPROM signature byte 0
EEPROM signature byte 1
APM Value
I2C EEPROM signature byte 0. This byte must be 0x53 for
proper AT2LP pin configuration.
I2C EEPROM signature byte 1. This byte must be 0x4B for
proper AT2LP pin configuration.
0x53
0x4B
ATA Device Automatic Power Management Value. If an
attached ATA device supports APM and this field contains
other than 0x00, the AT2LP issues a SET_FEATURES
command to Enable APM with this value during the drive
initialization process. Setting APM Value to 0x00 disables
this functionality. This value is ignored with ATAPI devices.
0x00
0x03
0x04
Reserved
Must be set to 0x00.
0x00
0x24
bVSCBSignature Value
Value in the first byte of the CBW CB field that designates
that the CB is to be decoded as vendor specific ATA
commands instead of the ATAPI command block. See
“Functional Overview” on page 15 for more detail on how
this byte is used.
0x05
Reserved
Bits 7:6
0x07
Enable mode page 8
Bit 5
Enable the write caching mode page (page 8). If this page
is enabled, Windows disables write caching by default,
which limits write performance.
0= Disable mode page 8.
1= Enable mode page 8.
Disable wait for INTRQ
BUSY Bit Delay
Bit 4
Poll status register rather than waiting for INTRQ. Setting
this bit to 1 improves USB BOT test results but may
introduce compatibility problems with some devices.
0 = Wait for INTRQ.
1 = Poll status register instead of using INTRQ.
Bit 3
Enable a delay of up to 120 ms at each read of the DRQ bit
where the device data length does not match the host data
length. This enables the CY7C68300C/CY7C68301C to
work with most devices that incorrectly clear the BUSY bit
before a valid status is present.
0 = No BUSY bit delay.
1 = Use BUSY bit delay.
Short Packet Before Stall
Bit 2
Determines if a short packet is sent before the STALL of an
IN endpoint. The USB Mass Storage Class Bulk-Only Speci-
fication enables a device to send a short or zero-length IN
packet before returning a STALL handshake for certain
cases. Certain host controller drivers may require a short
packet before STALL.
0 = Do not force a short packet before STALL.
1 = Force a short packet before STALL.
Document 001-05809 Rev. *C
Page 22 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Table 11. Configuration Data Organization (continued)
Byte
Address
Configuration
Item Name
Configuration
Item Description
Required Variable
Contents Contents
SRST Enable
Bit 1
Determines if the AT2LP is to do an SRST reset during drive
initialization. At least one reset must be enabled. Do not set
SRST to 0 and Skip Pin Reset to 1 at the same time.
0 = Do not perform SRST during initialization.
1 = Perform SRST during initialization.
Skip Pin Reset
Bit 0
Skip ARESET# assertion. When this bit is set, the AT2LP
bypasses ARESET# during any initialization other than
power up. Do not set SRST Enable to 0 and Skip Pin Reset
to 1 at the same time.
0 = Allow ARESET# assertion for all device resets.
1 = Disable ARESET# assertion except for chip reset cycles.
0x06
ATA UDMA Enable
ATAPI UDMA Enable
UDMA Modes
Bit 7
0xD4
Enable Ultra DMA data transfer support for ATA devices. If
enabled, and if the ATA device reports UDMA support for the
indicated modes, the AT2LP uses UDMA data transfers at
the highest negotiated rate possible.
0 = Disable ATA device UDMA support.
1 = Enable ATA device UDMA support.
Bit 6
Enable Ultra DMA data transfer support for ATAPI devices.
If enabled, and if the ATAPI device reports UDMA support
for the indicated modes, the AT2LP uses UDMA data
transfers at the highest negotiated rate possible.
0 = Disable ATAPI device UDMA support.
1 = Enable ATAPI device UDMA support.
Bits 5:0
These bits select which UDMA modes are enabled. The
AT2LP operates in the highest enabled UDMA mode
supported bythe device. The AT2LP supports UDMA modes
2, 3, and 4 only.
Bit 5 = Reserved. Must be set to 0.
Bit 4 = Enable UDMA mode 4.
Bit 3 = Enable UDMA mode 3.
Bit 2 = Enable UDMA mode 2.
Bit 1 = Reserved. Must be set to 0.
Bit 0 = Reserved. Must be set to 0.
0x07
Reserved
Bits 7:3
Must be set to 0.
0x07
Multi-word DMA mode
Bit 2
This bit enables multi-word DMA support. If this bit is set and
the drive supports it, multi-word DMA is used.
PIO Modes
Bits 1:0
These bits select which PIO modes are enabled. Setting to
‘1’ enables use of that mode with the attached drive, if the
drive supports it. Multiple bits may be set. The AT2LP
operates in the highest enabled PIO mode supported by the
device. The AT2LP supports PIO modes 0, 3, and 4 only.
PIO mode 0 is always enabled and has no corresponding
configuration bit.
Bit 1 = Enable PIO mode 4.
Bit 0 = Enable PIO mode 3.
Document 001-05809 Rev. *C
Page 23 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Table 11. Configuration Data Organization (continued)
Byte
Address
Configuration
Item Name
Configuration
Item Description
Required Variable
Contents Contents
0x08
BUTTON_MODE
Bit 7
0x78
Button mode (100-pin package only). Sets ATAPUEN,
PWR500# and DRVPWRVLD to become button inputs
returned on bits 2, 1, and 0 of EP1IN. This bit must be set to
‘0’ if the 56-pin packages are used.
0 = Disable button mode.
1 = Enable button mode.
SEARCH_ATA_BUS
Bit 6
Search ATA bus after RESET to detect non-removable ATA
and ATAPI devices. Systems with only a removable device
(such as CF readers) must set this bit to ‘0’. Systems with at
least one non-removable device must set this bit to ‘1’.
0 = Do not search for ATA devices.
1 = Search for ATA devices.
BIG_PACKAGE
ATA_EN
Bit 5
Selects the 100- or 56-pin package pinout configuration.
Using the wrong pinout may result in unpredictable behavior.
0 = Use 56-pin package pinout.
1 = Use 100-pin package pinout.
Bit 4
Drive ATA bus when AT2LP is in suspend. For designs in
which the ATA bus is shared between the AT2LP and
another ATA master (such as an MP3 player), the AT2LP
can place the ATA interface pins in a Hi-Z state when it
enters suspend. For designs that do not share the ATA bus,
the ATA signals must be driven while the AT2LP is in
suspend to avoid floating signals.
0 = Drive ATA signals when AT2LP is in suspend.
1 = Set ATA signals to Hi-Z when AT2LP is in suspend.
Reserved
Bit 3
Reserved. This bit must be set to ‘0’.
Reserved
Bit 2
Reserved. This bit must be set to ‘0’
Drive Power Valid Polarity
Bit 1
Configure the logical polarity of the DRVPWRVLD input pin.
0 = Active LOW (‘connector ground’ indication)
1 = Active HIGH (power indication from device)
Drive Power Valid Enable
Bit 0
Enable the DRVPWRVLD pin. When this pin is enabled, the
AT2LP enumerates a removable ATA device, such as
CompactFlash or MicroDrive, as the IDE master device.
Enabling this pin also affects other pins related to removable
device operation.
0 = Disable removable ATA device support.
1 = Enable removable ATA device support.
Document 001-05809 Rev. *C
Page 24 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Table 11. Configuration Data Organization (continued)
Byte
Address
Configuration
Item Name
Configuration
Item Description
Required Variable
Contents Contents
0x09
Reserved
Bits 7:6
0x00
Reserved. Must be set to zero.
General Purpose I/O Pin
Output Enable
Bits 5:0
GPIO[5:0] Input and output control. GPIOs can be individ-
ually set as inputs or outputs using these bits.
0 = Hi-Z (pin is an input). The state of the signal connected
to GPIO input pins is reported in the SYSIRQ or HID data.
1 = Output enabled (pin is an output). The state of GPIO
output pins is controlled by the value in address 0x0A.
0x0A
Reserved
Bits 7:6
0x00
Reserved. Must be set to zero.
GPIO Output Pin State
Bits 5:0
These bits select the value driven on the GPIO pins that are
configured as outputs in configuration address 0x09.
0 = Drive the GPIO pin LOW
1 = Drive the GPIO pin HIGH
0x0B
0x0C
LUN0 Identify String
LUN1 Identify String
This byte is a pointer to the start of a 24 byte ASCII
0x00
0x00
(non-Unicode) string in the EEPROM that is used as the
LUN0 device identifier. This string is used by many operating
systems as the user-visible name for the drive. If this byte is
0x00, the Identify Device data from the drive is used instead.
This byte is a pointer to the start of a 24 byte ASCII
(non-Unicode) string in the EEPROM that is used as the
LUN1 device identifier. This string is used by many operating
systems as the user-visible name for the drive. If this byte is
0x00, the Identify Device data from the drive is used instead.
0x0D
0x0E
Delay After Reset
Reserved
Number of 20-ms ticks to wait between AT2LP startup or
reset, and the first attempt to access any drives.
0x00
0x00
Bits 7:5
Must be set to zero.
Bus-Powered Flag
Bit 4
Enable bus-powered HDD support. This bit enables the use
ofDRVPWRVLDfeatureswithoutreportingtheLUN0device
as removable media.
0 = LUN0 is removable media or DRVPWRVLD is disabled
1 = LUN0 device is bus-powered and non-removable
CF UDMA Enable
Bit 3
Enable UDMA transfers for removable devices. Some CF
devices interfere with UDMA transfers when more than one
drive is connected to the ATA bus.
0 = Do not use UDMA transfers with removable devices
(UDMA signals are not connected to the CF pins).
1 = Allow UDMA transfers to be used with removable
devices (UDMA signals are connected to the CF pins).
Fixed Number of Logical
Bits 2:1
Assume the presence of devices and do not perform a
search of the ATA bus to discover the number of LUNs.
00 = Search ATA bus and determine number of LUNs
01 = Assume only LUN0 present; no ATA bus search
10 = Assume LUN0 and LUN1 present; no ATA bus search
11 = Assume LUN0 and LUN1 present; no ATA bus search
Document 001-05809 Rev. *C
Page 25 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Table 11. Configuration Data Organization (continued)
Byte
Address
Configuration
Item Name
Configuration
Item Description
Required Variable
Contents Contents
Search ATA on VBUS
Bit 0
Search for ATA devices when VBUS returns. If this bit is set,
the ATA bus is searched for ATA devices every time
VBUS_ATA_ENABLE is asserted. This feature enables the
AT2LP to be used in designs where the drive may be physi-
cally removed (such as docking stations or port replicators).
0 = Search ATA bus on VBUS_ATA_ENABLE assertion
1 = No ATA bus search on VBUS_ATA_ENABLE assertion
0x0F
Reserved
Must be set to 0x00
0x00
Device Descriptor
0x10
0x11
0x12
0x13
0x14
0x15
0x16
0x17
0x18
0x19
0x1A
0x1B
0x1C
bLength
Length of device descriptor in bytes
Descriptor type.
0x12
0x01
0x00
0x02
0x00
0x00
0x00
0x40
bDescriptor Type
bcdUSB (LSB)
bcdUSB (MSB)
bDeviceClass
USB Specification release number in BCD
Device class
bDeviceSubClass
bDeviceProtocol
bMaxPacketSize0
idVendor (LSB)
idVendor (MSB)
idProduct (LSB)
idProduct (MSB)
bcdDevice (LSB)
Device subclass
Device protocol
USB packet size supported for default pipe
Vendor ID. Cypress’ Vendor ID may only be used for evalu-
ation purposes, and not in released products.
Your
Vendor ID
Product ID
Your
Product ID
Device release number in BCD LSB (product release
number)
Your
release
number
0x1D
0x1E
bcdDevice (MSB)
iManufacturer
Device release number in BCD MSB (silicon release
number)
Index to manufacturer string. This entry must equal half of
the address value where the string starts or 0x00 if the string
does not exist.
0x53
0x69
0x75
0x1F
0x20
iProduct
Index to product string. This entry must equal half of the
address value where the string starts or 0x00 if the string
does not exist.
iSerialNumber
Index to serial number string. This entry must equal half of
the address value where the string starts or 0x00 if the string
does not exist. The USB Mass Storage Class Bulk-Only
Transport Specification requires a unique serial number (in
upper case, hexadecimal characters) for each device.
0x21
bNumConfigurations
Number of configurations supported
1 for mass storage: 2 for HID: 3 for CSM
0x03
Device Qualifier
0x22
0x23
0x24
0x25
0x26
0x27
0x28
bLength
Length of device descriptor in bytes
Type Descriptor type
0x0A
0x06
0x00
0x02
0x00
0x00
0x00
bDescriptor
bcdUSB (LSB)
bcdUSB (MSB)
bDeviceClass
bDeviceSubClass
bDeviceProtocol
USB Specification release number in BCD
USB Specification release number in BCD
Device class
Device subclass
Device protocol
Document 001-05809 Rev. *C
Page 26 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Table 11. Configuration Data Organization (continued)
Byte
Address
Configuration
Item Name
Configuration
Item Description
Required Variable
Contents Contents
0x29
0x2A
0x2B
bMaxPacketSize0
USB packet size supported for default pipe
Number of configurations supported
0x40
0x01
0x00
bNumConfigurations
bReserved
Reserved for future use. Must be set to zero
Configuration Descriptor
0x2C
0x2D
0x2E
0x2F
bLength
Length of configuration descriptor in bytes
Descriptor type
0x09
0x02
bDescriptorType
bTotalLength (LSB)
bTotalLength (MSB)
Number of bytes returned in this configuration. This includes
the configuration descriptor plus all the interface and
endpoint descriptors.
0x20
0x00
0x30
0x31
bNumInterfaces
Number of interfaces supported
0x01
bConfiguration Value
The value to use as an argument to Set Configuration to
select the configuration. This value must be set to 0x01.
0x01
0x32
0x33
iConfiguration
bmAttributes
Index to the configuration string. This entry must equal half
of the address value where the string starts, or 0x00 if the
string does not exist.
0x00
0xC0
Device attributes for this configuration
Bit 7 Reserved. Must be set to 1
Bit 6 Self-powered. See Table 4 for reported value
Bit 5 Remote wakeup. Must be set to 0
Bits 4–0 Reserved. Must be set to 0
0x34
bMaxPower
Maximum power consumption for this configuration. Units
used are mA*2 (i.e., 0x31 = 98 mA, 0xF9 = 498 mA). The
value entered here is only used by the 56-pin packages and
affect the reported value of bit 6 of address 0x33 in that case.
See Table 4 on page 14 for a description of what value is
reported to the host by the AT2LP.
0x01
Interface and Endpoint Descriptors
Interface Descriptor
0x35
0x36
0x37
0x38
0x39
0x3A
0x3B
0x3C
0x3D
bLength
Length of interface descriptor in bytes
Descriptor type
0x09
0x04
0x00
0x00
bDescriptorType
bInterfaceNumber
bAlternateSetting
bNumEndpoints
bInterfaceClass
bInterfaceSubClass
bInterfaceProtocol
iInterface
Interface number
Alternate setting
Number of endpoints
Interface class
0x02
0x06
0x00
0x08
0x50
Interface subclass
Interface protocol
Index to first interface string. This entry must equal half of
the address value where the string starts or 0x00 if the string
does not exist.
USB Bulk Out Endpoint
0x3E
0x3F
0x40
0x41
0x42
0x43
bLength
Length of this descriptor in bytes
Endpoint descriptor type
0x07
0x05
0x02
0x02
bDescriptorType
bEndpointAddress
bmAttributes
This is an Out endpoint, endpoint number 2.
This is a bulk endpoint.
wMaxPacketSize (LSB)
wMaxPacketSize (MSB)
Max data transfer size. To be set by speed (Full speed
0x0040; High speed 0x0200)
0x00
0x02
Document 001-05809 Rev. *C
Page 27 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Table 11. Configuration Data Organization (continued)
Byte
Address
Configuration
Item Name
Configuration
Item Description
Required Variable
Contents Contents
0x44
bInterval
High speed interval for polling (maximum NAK rate)
0x00
USB Bulk In Endpoint
0x45
0x46
0x47
0x48
0x49
0x4A
0x4B
bLength
Length of this descriptor in bytes
Endpoint descriptor type
0x07
0x05
0x86
0x02
bDescriptorType
bEndpointAddress
bmAttributes
This is an In endpoint, endpoint number 6
This is a bulk endpoint
wMaxPacketSize (LSB)
wMaxPacketSize (MSB)
bInterval
Max data transfer size. Automatically set by AT2 (Full speed
0x0040; High speed 0x0200)
0x00
0x02
High speed interval for polling (maximum NAK rate)
0x00
(Optional) HID Interface Descriptor
0x4C
0x4D
0x4E
0x4F
0x50
0x51
0x52
0x53
0x54
bLength
Length of HID interface descriptor
Interface descriptor type
Number of interfaces (2)
Alternate setting
0x09
0x04
0x02
0x00
0x01
0x03
0x00
0x00
0x00
bDescriptorTypes
bInterfaceNumber
bAlternateSetting
bNumEndpoints
bInterfaceClass
bInterfaceSubClass
bInterfaceSubSubClass
iInterface
Number of endpoints used by this interface
Class code
Sub class
Sub Sub class
Index of string descriptor
USB Interrupt In Endpoint
0x5E
0x5F
0x60
0x61
0x62
0x63
0x64
bLength
Length of this descriptor in bytes
Endpoint descriptor type
0x07
0x05
0x81
0x03
0x02
0x00
bDescriptorType
bEndpointAddress
bmAttributes
This is an In endpoint, endpoint number 1
This is an interrupt endpoint
Max data transfer size
wMaxPacketSize (LSB)
wMaxPacketSize (MSB)
bInterval
Interval for polling (max. NAK rate)
0x10
(Optional) HID Descriptor
0x55
0x56
0x57
0x58
0x59
0x5A
0x5B
0x5C
0x5D
bLength
Length of HID descriptor
0x09
0x21
0x10
0x01
0x00
0x01
0x22
0x22
0x00
bDescriptorType
bcdHID (LSB)
Descriptor Type HID
HID Class Specification release number (1.10)
bcdHID (MSB)
bCountryCode
Country Code
bNumDescriptors
bDescriptorType
wDescriptorLength (LSB)
wDescriptorLength (MSB)
Number of class descriptors (1 report descriptor)
Descriptor Type
Length of HID report descriptor
Terminator Descriptors
0x65 Terminator
0x00
(Optional) HID Report Descriptor
Document 001-05809 Rev. *C
Page 28 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Table 11. Configuration Data Organization (continued)
Byte
Address
Configuration
Item Name
Configuration
Item Description
Required Variable
Contents Contents
0x66
0x67
0x68
0x69
0x6A
0x6B
0x6C
0x6D
0x6E
Usage_Page
Vendor defined
0x06
0xA0
0xFF
0x09
0xA5
0xA1
0x01
0x09
0xA6
Usage
Vendor defined
Application
Collection
Usage
Vendor defined
Input Report
0x6F
0x70
0x71
0x72
0x73
0x74
0x75
0x76
0x77
0x78
0x79
0x7A
Usage
Vendor defined
–128
0x09
0xA7
0x15
0x80
0x25
0x7F
0x75
0x08
0x95
0x02
0x81
0x02
Logical_Minimum
Logical_Maximum
Report_Size
Report_Count
Input
127
8 bits
2 fields
Input (Data, Variable, Absolute)
Output Report
0x7B
0x7C
0x7D
0x7E
0x7F
0x80
0x81
0x82
0x83
0x84
0x85
0x86
0x87
Usage
Usage - vendor defined
Logical Minimum (–128)
Logical Maximum (127)
Report Size 8 bits
0x09
0xA9
0x15
0x80
0x25
0x7F
0x75
0x08
0x95
0x02
0x91
0x02
0xC0
Logical_Minimum
Logical_Maximum
Report_Size
Report_Count
Output
Report Count 2 fields
Output (Data, Variable, Absolute)
End Collection
(optional) Standard Content Security Interface Descriptor
0x88
0x89
0x8A
0x8B
bLength
Byte length of this descriptor
Interface Descriptor type
Number of interface
0x09
0x0D
0x02
bDescriptorType
bInterfaceNumber
bAlternateSetting
Value used to select an alternate setting for the interface
identified in prior field
0x00
Document 001-05809 Rev. *C
Page 29 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Table 11. Configuration Data Organization (continued)
Byte
Address
Configuration
Item Name
Configuration
Item Description
Required Variable
Contents Contents
0x8C
0x8D
0x8E
0x8F
0x90
bNumEndpoints
Number of endpoints used by this interface (excluding
endpoint 0) that are CSM dependent
0x02
0x0D
0x00
0x00
0x00
bInterfaceClass
bInterfaceSubClass
bInterfaceProtocol
iInterface
Must be set to zero
Must be set to zero
Index of a string descriptor that describes this Interface
Channel Descriptor
0x91
0x92
0x93
bLength
Length of this descriptor in bytes
Channel descriptor type
0x09
0x22
0x00
bDescriptorType
bChannelID
Number of the channel, must be a zero based value that is
unique across the device
0x94
bmAttributes
Bits7:5
0x01
Reserved. Must be set to zero
Bits 4:0
0x95
bRecipient
Identifier of the target recipient
0x00
If Recipient type field of bmAttributes = 1 then
bRecipient field is the bInterfaceNumber
If Recipient type field of bmAttributes = 2 then
bRecipient field is an endpoint address, where:
D7: Direction (0 = Out, 1 = IN)
D6...D4: Reserved and set to zero
D3...D0: Endpoint number
0x96
bRecipientAlt
alternate setting for the interface to which this channel
applies
0x00
0x97
0x98
bRecipientLogicalUnit
bMethod
Recipient Logical Unit
0x00
0x01
Index of a class-specific CSM descriptor That describes one
of the Content Security Methods (CSM) offered by the
device
0x99
bMethodVariant
CSM Variant descriptor
0x00
CSM Descriptor
0x9A
0x9B
0x9C
bLength
Byte length of this descriptor
CSM Descriptor type
0x06
0x23
0x01
bDescriptorType
bMethodID
Index of a class-specific CSM descriptor that describes on
of the Content Security Methods offered by the device
0x9D
iCSMDescriptor
Indexofstringdescriptorthatdescribesthe Content Security
Method
0x00
0x9E
0x9F
0xA0
bcdVersion (LSB)
bcsVersion (MSB)
Terminator
CSM Descriptor Version number
0x10
0x02
0x00
USB String Descriptor–Index 0 (LANGID)
0xA1
0xA2
0xA3
0xA4
bLength
LANGID string descriptor length in bytes
Descriptor type
0x04
0x03
bDescriptorType
LANGID (LSB)
LANGID (MSB)
Language supported. The CY7C68300B supports one
LANGID value.
0x09
0x04
USB String Descriptor–Manufacturer
0xA5
0xA6
bLength
String descriptor length in bytes (including bLength)
Descriptor type
0x2C
bDescriptorType
0x03
Document 001-05809 Rev. *C
Page 30 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Table 11. Configuration Data Organization (continued)
Byte
Address
Configuration
Item Name
Configuration
Item Description
Required Variable
Contents Contents
0xA7
0xA8
0xA9
0xAA
0xAB
0xAC
0xAD
0xAE
0xAF
0xB0
0xB1
0xB2
0xB3
0xB4
0xB5
0xB6
0xB7
0xB8
0xB9
0xBA
0xBB
0xBC
0xBD
0xBE
0xBF
0xC0
0xC1
0xC2
0xC3
0xC4
0xC5
0xC6
0xC7
0xC8
0xC9
0xCA
0xCB
0xCC
0xCD
0xCE
0xCF
0xD0
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
Unicode character LSB
’C’ 0x43
0x00
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
’y’ 0x79
0x00
’p’ 0x70
0x00
’r’ 0x72
0x00
’e’ 0x65
0x00
’s’ 0x73
0x00
’s’ 0x73
0x00
’ ’ 0x20
0x00
’S’ 0x53
0x00
’e’ 0x65
0x00
’m’ 0x6D
0x00
’i’ 0x69
0x00
’c’ 0x63
0x00
’o’ 0x6F
0x00
’n’ 0x6E
0x00
’d’ 0x64
0x00
’u’ 0x75
0x00
’c’ 0x63
0x00
’t’ 0x74
0x00
’o’ 0x6F
0x00
’r’ 0x72
0x00
Document 001-05809 Rev. *C
Page 31 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Table 11. Configuration Data Organization (continued)
Byte
Address
Configuration
Item Name
Configuration
Item Description
Required Variable
Contents Contents
USB String Descriptor–Product
0xD1
0xD2
0xD3
0xD4
0xD5
0xD6
0xD7
0xD8
0xD9
0xDA
0xDB
0xDC
0xDD
0xDE
0xDF
0xE0
0xE1
0xE2
0xE3
0xE4
0xE5
0xE6
0xE7
0xE8
bLength
bDescriptorType
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
String descriptor length in bytes (including bLength)
Descriptor type.
0x2C
0x03
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
’U’ 0x55
0x00
’S’ 0x53
0x00
’B’ 0x42
0x00
’2’ 0x32
0x00
’.’ 0x2E
0x00
’0’ 0x30
0x00
’ ’ 0x20
0x00
’D’ 0x53
0x00
’i’ 0x74
0x00
’s’ 0x6F
0x00
’k’ 0x72
0x00
USB String Descriptor–Serial Number (Note: The USB Mass Storage Class specification requires a unique serial number in
each device. If you do not provide a unique serial number, the operating system may crash. The serial number must be at least
12 characters, but some USB hosts only use the least significant 12 characters of the serial number as a unique identifier.
0xE9
0xEA
0XEB
0XEC
0XED
0XEE
0XEF
0XF0
0xF1
0xF2
0xF3
0xF4
0xF5
0xF6
0xF7
bLength
bDescriptor Type
bString
String descriptor length in bytes (including bLength).
Descriptor type.
0x22
0x03
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
’1’ 0x31
0x00
bString
bString
’2’ 0x32
0x00
bString
bString
’3’ 0x33
0x00
bString
bString
’4’ 0x34
0x00
bString
bString
’5’ 0x35
0x00
bString
bString
’6’ 0x36
0x00
bString
bString
’7’ 0x37
Document 001-05809 Rev. *C
Page 32 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Table 11. Configuration Data Organization (continued)
Byte
Address
Configuration
Item Name
Configuration
Item Description
Required Variable
Contents Contents
0xF8
0xF9
0xFA
0xFB
0xFC
0xFD
0xFE
0xFF
0Xxx
0Xxx
0Xxx
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
bString
Unicode character MSB
0x00
’8’ 0x38
0x00
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
Unicode character LSB
Unicode character MSB
’9’ 0x39
0x00
’0’ 0x30
0x00
’A’ 0x41
0x00
’B’ 0x42
0x00
Identify Device String (Note: This is not a Unicode string. It is the ASCII string returned by the device in the Identify Device
information. It is a fixed length (24 bytes). Changing this string may cause CD authoring software to incorrectly identify the device.)
0Xxx
0Xxx
0Xxx
0Xxx
0Xxx
0Xxx
0Xxx
0Xxx
0Xxx
0Xxx
0Xxx
0Xxx
0Xxx
0Xxx
0Xxx
0Xxx
0Xxx
0Xxx
0Xxx
0Xxx
0Xxx
0Xxx
0Xxx
0Xxx
0Xxx
Device name byte 1
Device name byte 2
Device name byte 3
Device name byte 4
Device name byte 5
Device name byte 6
Device name byte 7
Device name byte 8
Device name byte 9
Device name byte 10
Device name byte 11
Device name byte 12
Device name byte 13
Device name byte 14
Device name byte 15
Device name byte 16
Device name byte 17
Device name byte 18
Device name byte 19
Device name byte 20
Device name byte 21
Device name byte 22
Device name byte 23
Device name byte 24
Unused ROM Space
ASCII Character
’C’ 0x43
’y’ 0x79
’p’ 0x70
’r’ 0x72
’e’ 0x65
’s’ 0x73
’s’ 0x73
’ ’ 0x20
’C’ 0x43
’u’ 0x75
’s’ 0x73
’t’ 0x74
’o’ 0x6f
’m’ 0x6d
’ ’ 0x20
’N’ 0x4e
’a’ 0x61
’m’ 0x6d
’e’ 0x65
’ ’ 0x20
’L’ 0x4c
’U’ 0x55
’N’ 0x4e
’0’ 0x30
0xFF
ASCII Character
ASCII Character
ASCII Character
ASCII Character
ASCII Character
ASCII Character
ASCII Character
ASCII Character
ASCII Character
ASCII Character
ASCII Character
ASCII Character
ASCII Character
ASCII Character
ASCII Character
ASCII Character
ASCII Character
ASCII Character
ASCII Character
ASCII Character
ASCII Character
ASCII Character
ASCII Character
Amount of unused ROM space varies depending on strings.
Note: More than 0X100 bytes of configuration are shown for example only. The AT2LP only supports addresses up to 0xFF.
Document 001-05809 Rev. *C
Page 33 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
LOAD_CONFIG_DATA
Programming the EEPROM
This request enables writes to the AT2LP’s configuration data
space. The wIndex field specifies the starting address and the
wLength field denotes the data length in bytes.
There are three methods of programming the EEPROM:
■ Stand-alone EEPROM programmer
■ Vendor-specific USB commands, listed in Table 12
■ In-system programming (for example, bed-of-nails tester)
Legal values for wValue are as follows:
■ 0x0000 Internal Config bytes, address range 0x2 – 0xF
■ 0x0002 External I2C memory device
Any vendor-specific USB write request to the Serial ROM device
configuration space simultaneously update internal configuration
register values as well. If the I2C device is programmed without
vendor specific USB commands, the AT2LP must be synchro-
nously reset (toggle RESET#) before configuration data is
reloaded.
Internal Config byte writes must be constrained to addresses 0x2
through 0xF, as shown in Table 12. Attempts to write outside this
address space result in undefined operation. Internal Config byte
writes only overwrite AT2LP Configuration Byte registers, the
original data source (I2C memory device) remains unchanged.
The AT2LP supports a subset of the ’slow mode’ specification
(100 KHz) required for 24LCXXB EEPROM family device
support. Features such as ’Multi-Master,’ ’Clock Synchroni-
zation’ (the SCL pin is output only), ’10-bit addressing,’ and
’CBUS device support’ are not supported. Vendor-specific USB
commands enable the AT2LP to address up to 256 bytes of
EEPROM data.
Table 12. EEPROM-related Vendor-specific Commands
Label
bmRequestType bRequest
wValue
wIndex
wLength
Data
LOAD_CONFIG_DATA
0x40
0x01
0x0000
30x02 – 0x0F
Data Length
Configuration
Data
READ_CONFIG_DATA
0xC0
0x02
Data Source
Starting Address Data Length
Configuration
Data
READ_CONFIG_DATA
This USB request enables data retrieval from the data source specified by the wValue field. Data is retrieved beginning at the address
specified by the wIndex field (see Table 12). The wLength field denotes the length in bytes of data requested from the data source.
Legal values for wValue are as follows:
■ 0x0000
Configuration bytes, addresses 0x0 – 0xF only
External I2C memory device
■ 0x0002
Illegal values for wValue result in an undefined operation. Attempted reads from an I2C memory device when none is connected result
in an undefined operation. Attempts to read configuration bytes with starting addresses greater than 0xF also, result in an undefined
operation.
Document 001-05809 Rev. *C
Page 34 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Absolute Maximum Ratings
Operating Conditions
Exceeding maximum ratings may impair the useful life of the
device. These user guidelines are not tested.
TA (Ambient Temperature Under Bias)............. 0°C to +70°C
Supply Voltage............................................+3.00V to +3.60V
Ground Voltage.................................................................. 0V
Storage Temperature.................................. –65°C to +150°C
Ambient Temperature with Power Supplied...... 0°C to +70°C
Supply Voltage to Ground Potential................–0.5V to +4.0V
DC Input Voltage to Any Input Pin................................ 5.25V
DC Voltage Applied to Outputs in Hi-Z State–0.5V to VCC + 0.5V
Power Dissipation..................................................... 300 mW
Static Discharge Voltage...........................................> 2000V
Fosc (Oscillator or Crystal Frequency) .... 24 MHz ± 100 ppm,
Parallel Resonant
Max Output Current Per I/O Port
(D0-D7, D8-15, ATA control)........................................ 10 mA
DC Characteristics
Parameter
VCC
CC Ramp
Description
Supply Voltage
Conditions
Min
3.00
200
2
Typ
Max
Unit
V
3.3
3.60
V
Supply Ramp Up 0V to 3.3V
Input High Voltage
μs
V
VIH
VIL
5.25
0.8
Input Low Voltage
–0.5
V
II
Input Leakage Current
Crystal Input HIGH Voltage
Crystal Input LOW Voltage
Output Voltage High
Output Voltage Low
0 < VIH < VCC
±10
5.25
0.8
μA
V
VIH_X
VIL_X
VOH
VOL
IOH
IOL
2
–0.5
2.4
V
IOUT = 4 mA
V
IOUT = –4 mA
0.4
4
V
Output Current High
Output Current Low
mA
mA
pF
pF
mA
mA
μA
μA
mA
mA
mA
4
CIN
Input Pin Capacitance
All but DPLUS/DMINUS
DPLUS/DMINUS
Connected
10
15
1.2
1.0
380
150
85
65
ISUSP
Suspend Current
0.5
0.3
300
100
50
CY7C68300C/CY7C68320C
Suspend Current
Disconnected
Connected
CY7C68301C/CY7C68321C
Supply Current
Disconnected
ICC
IUNCONFIG
TRESET
USB High Speed
USB Full Speed
35
Unconfigured Current
Current before device is granted full
amount requested in bMaxPower
43
Reset Time After Valid Power
Pin Reset After Power Up
VCC > 3.0V
5.0
ms
200
μs
Document 001-05809 Rev. *C
Page 35 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
AC Electrical Characteristics
AT2LP configuration space and the data reported by the drives
in response to an IDENTIFY DEVICE command.
ATA Timing Characteristics
The ATA interface supports ATA PIO modes 0, 3, and 4, Ultra
DMA modes 2, 3, and 4, and multi-word DMA mode 2, per the
ATA/ATAPI 6 Specification. The highest enabled transfer rate
common to both the AT2LP and the attached mass storage
device is used. The AT2LP automatically determines the transfer
rates during drive initialization based upon the values in the
USB Transceiver Characteristics
Complies with the USB 2.0 specification for full- and high speed
modes of operation.
Ordering Information
Part Number
Package Type
56 SSOP Pb-free for self and bus powered designs
GPIO Pins
CY7C68300C-56PVXC
CY7C68301C-56PVXC
CY7C68300C-56LFXC
CY7C68300C-56LTXC
CY7C68301C-56LFXC
CY7C68301C-56LTXC
CY7C68320C-56LFXC
CY7C68320C-56PVXC
CY7C68320C-56LTXC
CY7C68321C-56LFXC
CY7C68321C-56LTXC
CY7C68320C-100AXC
CY7C68321C-100AXC
CY4615B
–
–
56 SSOP Pb-free for battery-powered designs
56 QFN Pb-free for self and bus powered designs
56 QFN Sawn Pb-free for self and bus powered designs
56 QFN Pb-free for battery-powered designs
56 QFN Sawn Pb-free for battery-powered designs
56 QFN Pb-free for self and bus powered designs
56 SSOP Pb-free for self and bus powered designs
56 QFN Sawn Pb-free for self and bus powered designs
56 QFN Pb-free for battery-powered designs
56 QFN Sawn Pb-free for battery-powered designs
100 TQFP Pb-free for self and bus powered designs
100 TQFP Pb-free for battery-powered designs
EZ-USB AT2LP Reference Design Kit
–
–
–
–
3[4]
3[4]
3[4]
3[4]
3[4]
6
6
n/a
Note
4. The General Purpose inputs can be enabled on ATAPUEN, PWR500#, and DRVPWRVLD with EEPROM byte 8, bit 7 on CY7C68320C/CY7C68321C.
Document 001-05809 Rev. *C
Page 36 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Package Diagrams (continued)
Figure 12. 100-Pin Thin Plastic Quad Flatpack (14 x 20 x 1.4 mm) A101
16.00 0.20
14.00 0.10
1.40 0.05
100
81
80
1
0.30 0.08
0.65
TYP.
12° 1°
(8X)
SEE DETAIL
A
30
51
31
50
0.20 MAX.
1.60 MAX.
R 0.08 MIN.
0.20 MAX.
0° MIN.
SEATING PLANE
STAND-OFF
0.05 MIN.
0.15 MAX.
NOTE:
1. JEDEC STD REF MS-026
0.25
GAUGE PLANE
2. BODY LENGTH DIMENSION DOES NOT INCLUDE MOLD PROTRUSION/END FLASH
MOLD PROTRUSION/END FLASH SHALL NOT EXCEED 0.0098 in (0.25 mm) PER SIDE
R 0.08 MIN.
0.20 MAX.
BODY LENGTH DIMENSIONS ARE MAX PLASTIC BODY SIZE INCLUDING MOLD MISMATCH
3. DIMENSIONS IN MILLIMETERS
0°-7°
0.60 0.15
1.00 REF.
0.20 MIN.
51-85050-*B
DETAIL
A
Document 001-05809 Rev. *C
Page 37 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Figure 13. 56-Pin Shrunk Small Outline Package 056
51-85062 *C
Figure 14. 56-Pin QFN 8 x 8 mm LF56A
51-85144 *G
Document 001-05809 Rev. *C
Page 38 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Figure 15. 56-Pin QFN (8 X 8 X 0.9 MM) - Sawn
001-53450 **
General PCB Layout Recommendations for
USB Mass Storage Designs
Quad Flat Package No Leads (QFN) Package
Design Notes
The following recommendations must be followed to ensure
reliable high-performance operation:
Electrical contact of the part to the Printed Circuit Board (PCB)
is made by soldering the leads on the bottom surface of the
package to the PCB. Hence, special attention is required to the
heat transfer area below the package to provide a good thermal
bond to the circuit board. A Copper (Cu) fill must be designed
into the PCB as a thermal pad under the package. Heat is trans-
ferred from the AT2LP through the device’s metal paddle on the
bottom side of the package. Heat from here is conducted to the
PCB at the thermal pad. It is then conducted from the thermal
pad to the PCB inner ground plane by a 5 x 5 array of vias. A via
is a plated through-hole in the PCB with a finished diameter of
13 mil. The QFN’s metal die paddle must be soldered to the
PCB’s thermal pad. Solder mask is placed on the board top side
over each via to resist solder flow into the via. The mask on the
top side also minimizes outgassing during the solder reflow
process.
■ Use at least a four-layer, impedance controlled board to
maintain signal quality.
■ Specify specific impedance targets (ask your board vendor
what they can achieve).
■ Maintain uniform trace widths and trace spacing to control
impedance.
■ Minimize reflected signals by avoiding using stubs and vias.
■ Connect the USB connector shell and signal ground as near to
the USB connector as possible.
■ Use bypass/flyback capacitors on VBUS near the connector.
■ Keep DPLUS and DMINUS trace lengths to within 2 mm of
each other in length, with a preferred length of 20–30 mm.
■ Maintain a solid ground plane under the DPLUS and DMINUS
traces. Do not allow the plane to be split under these traces.
■ Do not place vias on the DPLUS or DMINUS trace routing for
a more stable design.
For further information on this package design, refer to the appli-
cation note Surface Mount Assembly of AMKOR’s MicroLead-
Frame (MLF) Technology. The application note provides detailed
information on board mounting guidelines, soldering flow, rework
process, etc.
■ Isolate the DPLUS and DMINUS traces from all other signal
traces by no less than 10 mm.
Figure 16 displays a cross-sectional area underneath the
package. The cross section is of only one via. The solder paste
template needs to be designed to enable at least 50% solder
coverage. The thickness of the solder paste template must be
5 mil. It is recommended that ’No Clean,’ type 3 solder paste is
used for mounting the part. Nitrogen purge is recommended
during reflow.
■ Source for recommendations:
❐ EZ-USB FX2LP PCB Design Recommendations
www.cypress.com/?docID=4696
❐ High speed USB Platform Design Guidelines
http://www.usb.org/developers/
docs/hs_usb_pdg_r1_0.pdf
Document 001-05809 Rev. *C
Page 39 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Figure 16. Cross-Section of the Area Under the QFN Package
0.017” dia
Solder Mask
Cu Fill
Cu Fill
0.013” dia
PCB Material
PCB Material
Via hole for thermally connecting the
This figure only shows the top three layers of the
circuit board: Top Solder, PCB Dielectric, and
the Ground Plane
QFN to the circuit board ground plane.
Figure 17 is a plot of solder mask pattern and Figure 18 displays an X-Ray image of assembly (darker areas indicate solder).
Figure 17. Plot of the Solder Mask (White Area)
Figure 18. X-Ray Image of the Assembly
IDE Removable Media Devices
Other Design Considerations
The AT2LP does not fully support IDE removable media devices.
Changes in media state are not reported to the operating system
so users are unable to eject/reinsert media properly. This may
result in lost or corrupted data. Note that standard ATAPI optical
drives and ATA CompactFlash-type devices are not part of this
group.
Certain design considerations must be followed to ensure proper
operation of the CY7C68300C/CY7C68301C. The following
items must be taken into account when designing a USB device
with the CY7C68300C/CY7C68301C.
Proper Power Up Sequence
Devices With Small Buffers
Power must be applied to the CY7C68300C/CY7C68301C
before, or at the same time as the ATA/ATAPI device. If power is
supplied to the drive first, the CY7C68300C/CY7C68301C
startup in an undefined state. Designs that utilize separate power
supplies for the CY7C68300C/CY7C68301C and the ATA/ATAPI
device are not recommended.
The size of the drive’s buffer can greatly affect the overall data
transfer performance. Care must be taken to ensure that drives
have large enough buffers to handle the flow of data to and from
it. The exact buffer size needed depends on a number of
variables, but a good rule of thumb is:
(aprox min buffer) = (data rate) * (seek time + rotation time + other)
where ’other’ may include things such as the time required to
switch heads, power up a laser, etc. Drives with buffers that are
too small to handle the extra data may perform considerably
slower than expected.
Document 001-05809 Rev. *C
Page 40 of 41
[+] Feedback
CY7C68300C, CY7C68301C
CY7C68320C, CY7C68321C
Document History Page
Description Title: CY7C68300C/CY7C68301C/CY7C68320C/CY7C68321C EZ-USB AT2LP™ USB 2.0 to ATA/ATAPI Bridge
Document Number: 001-05809
Submission
Date
Orig. of
Change
REV.
ECN NO.
Description of Change
**
409321
611658
See ECN
See ECN
GIR
New data sheet.
*A
ARI/KKU Implemented new template. Added part number CY7C68320C-56PVXC to the
Ordering Information. Corrected part numbers on figure 5 and 6. Moved figure
titles to the top of each figure per new template requirements. Made
grammatical corrections. Changed the Fused Memory Data section. Added
new figure: 56-pin SSOP (CY7C68320C/CY7C68321C).
Changed figure 10 to reflect actual Flow for Operational Mode. Changes made
between “VBUS_ATA_ENABLE PIN HIGH?” and “Board Manufacturing Test
Mode”. Formatted“0=”, “1=”linesinConfigurationDataOrganizationtoalways
show up in the same order. Re-worded 3rd bullet point in the Operation
Selection Flow section.
GPIO2_nHS function removed and corrected the sense of ATA_EN to allow
drive on ‘0’ and Hi-Z on ‘1’.
*B
*C
2717536
2733311
06/11/2009
07/08/09
DPT
Added 56 QFN (8 X 8 mm) package diagram and added
CY7C68300C-56LTXC, CY7C68301C-56LTXC, CY7C68320C-56LTXC, and
CY7C68321C-56LTXC parts in the Ordering Information table
NMMA Updated package drawing spec 51-85062
Updated link in the Additional Resources section
Updated Ordering information table
Sales, Solutions, and Legal Information
Worldwide Sales and Design Support
Cypress maintains a worldwide network of offices, solution centers, manufacturer’s representatives, and distributors. To find the office
closest to you, visit us at cypress.com/sales.
Products
PSoC
psoc.cypress.com
clocks.cypress.com
wireless.cypress.com
memory.cypress.com
image.cypress.com
Clocks & Buffers
Wireless
Memories
Image Sensors
© Cypress Semiconductor Corporation, 2006-2009. The information contained herein is subject to change without notice. Cypress Semiconductor Corporation assumes no responsibility for the use of
any circuitry other than circuitry embodied in a Cypress product. Nor does it convey or imply any license under patent or other rights. Cypress products are not warranted nor intended to be used for
medical, life support, life saving, critical control or safety applications, unless pursuant to an express written agreement with Cypress. Furthermore, Cypress does not authorize its products for use as
critical components in life-support systems where a malfunction or failure may reasonably be expected to result in significant injury to the user. The inclusion of Cypress products in life-support systems
application implies that the manufacturer assumes all risk of such use and in doing so indemnifies Cypress against all charges.
Any Source Code (software and/or firmware) is owned by Cypress Semiconductor Corporation (Cypress) and is protected by and subject to worldwide patent protection (United States and foreign),
United States copyright laws and international treaty provisions. Cypress hereby grants to licensee a personal, non-exclusive, non-transferable license to copy, use, modify, create derivative works of,
and compile the Cypress Source Code and derivative works for the sole purpose of creating custom software and or firmware in support of licensee product to be used only in conjunction with a Cypress
integrated circuit as specified in the applicable agreement. Any reproduction, modification, translation, compilation, or representation of this Source Code except as specified above is prohibited without
the express written permission of Cypress.
Disclaimer: CYPRESS MAKES NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Cypress reserves the right to make changes without further notice to the materials described herein. Cypress does not
assume any liability arising out of the application or use of any product or circuit described herein. Cypress does not authorize its products for use as critical components in life-support systems where
a malfunction or failure may reasonably be expected to result in significant injury to the user. The inclusion of Cypress’ product in a life-support systems application implies that the manufacturer
assumes all risk of such use and in doing so indemnifies Cypress against all charges.
Use may be limited by and subject to the applicable Cypress software license agreement.
Document 001-05809 Rev. *C
Revised July 08, 2009
Page 41 of 41
Purchase of I2C components from Cypress or one of its sublicensed Associated Companies conveys a license under the Philips I2C Patent Rights to use these components in an I2C system, provided
that the system conforms to the I2C Standard Specification as defined by Philips.
All products and company names mentioned in this document may be the trademarks of their respective holders.
[+] Feedback
相关型号:
©2020 ICPDF网 联系我们和版权申明