CY4611B Cypress Semiconductor Corp, CY4611B Datasheet - Page 8

• Manufacturer Part Number: CY4611B
• Description: KIT USB TO ATA REFERENCE DESIGN
• Manufacturer: Cypress Semiconductor Corp
• Series: EZ-USB FX2LP™r

Specifications of CY4611B

• Main Purpose: Interface, USB 2.0 to ATA/CF
• Utilized Ic / Part: CY7C68013A, CY7C68014A, CY7C68015A, CY7C68016A
• Silicon Manufacturer: Cypress
• Silicon Core Number: UDMA-100
• Kit Application Type: Interface
• Application Sub Type: USB To ATA
• Rohs Compliant: No
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Secondary Attributes: -
• Embedded: -
• Primary Attributes: -
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

1) Unplug the EEPROM jumper (J22)
2) Turn on power to your board. The board will
3) Plug the EEPROM jumper back in so your code
4) Open cyconsole and select options/EZ-USB
5) Hit the “Load Mon” button
6) Start the Keil debugger and download your
Once the firmware is bound to the generic driver,
commands can be sent to the device using the
control panel. An easy way to do this is to construct
a file containing the command and use the FileTrans
button to send it.
1) Start the Keil debugger; download your firmware
2) Run the firmware, it will enumerate and bind to
3) Start the control panel.
4) Do a “get pipes” on the control panel. This will
5) Select the OUT pipe and hit the FileTrans
6) Select your command file.
7) Manually transfer the IN or OUT data required
8) Do a final IN to collect the CSW.
Difference between ATAPI and IDE
devices
Although both ATAPI and IDE devices attach to the
same 40 pin cable, they operate using different
protocols, much like TCP/IP and NetBEUI share the
same Ethernet wire, but cannot talk to each other.
ATAPI commands are basically SCSI commands
sent over an ATA interface.
enumerate and bind to the generic driver
(CYUSB.sys).
can access the config data in the EEPROM.
interface
firmware via the Keil debugger
the general purpose driver
fill in the pipe fields.
button.
by the command
EZ-USB FX2LP USB to ATA Reference Design Notes
8
This firmware will support both ATAPI and IDE task
file commands. It will detect the type of device after
reset. If the device is an IDE device, the ATAPI
commands received over USB will be translated into
IDE task file commands. One way to gain additional
code space is to eliminate one of the supported
protocols.
ATACB – ATA Command Block
The ATA Command Block (ATACB) feature enables
the host to directly access the ATA register file on
the device. This allows the host to send IDE
commands that don’t have direct SCSI translations.
It also provides a powerful debug capability.
ATACB commands are transferred in the Command
Block Wrapper Command Block (CBWCB) portion of
the Command Block Wrapper (CBW) as shown
below:
The ATACB is distinguished from other command
blocks by having the first two bytes of the command
block match the bVSCBSignature and
bVSCBSubCommand values that are defined in the
configuration area of the EEPROM. Only command
blocks that have a valid bVSCBSignature 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.
20-27
28-30
Byte
8-11
0-3
4-7
12
13
14
15
16
17
18
19
bit
7
Reserved
Reserved (0)
bATACBTransferBlockCount
bATACBTaskFileWriteData
(0)
dCBWDataTransferLength
6
bmATACBRegisterSelect
bmATACBActionSelect
bVSCBSubCommand
bVSCBSignature
dCBWSignature
5
bmCBWFlags
dCBWTag
Reserved
4
bCBWCBLength
3
bCBWLUN
2
1
0