ISD-300A1 Cypress Semiconductor Corp, ISD-300A1 Datasheet - Page 13

• Manufacturer Part Number: ISD-300A1
• Description: IC USB 2.0 BRIDGE BULK 100LQFP
• Manufacturer: Cypress Semiconductor Corp

Specifications of ISD-300A1

• Applications: USB 2.0 to ATA/ATAPI Bridge
• Interface: ATA, ATAPI
• Voltage - Supply: 3 V ~ 3.6 V
• Package / Case: 100-LQFP
• Mounting Type: Surface Mount
• Lead Free Status / RoHS Status: Contains lead / RoHS non-compliant
• Other names: 428-1459

October 19, 2001
Table 3 describes how the ISD-300A1 determines USB descriptor / configuration sources.
I_MODE
Pin Active
Table 3 – ISD-300A1 Configuration and Descriptor Sources
Internal ROM Contents
Internal on-board ROM addresses and the contents of those locations are shown in the ISD-300A1
Configuration/USB Descriptor Data Formatting section on page 9 of this document.
Internal ROM is necessary for manufacturing activities. Internal ROM contents allow the host to
enumerate the ISD-300A1 when an un-programmed I
I
The ISD-300A1 supports a subset of the “slow mode” specification (100 KHz) required for 24LC01-16
EEPROM family device support. Features such as “Multi-Master”, “Clock Synchronization” (the SCL pin
is output only), “10-bit addressing”, and “CBUS device support”, are NOT supported. Vendor specific
USB commands allow the ISD-300A1 to address up to 2 K bytes of data (although configuration /
descriptor information is limited to 512 bytes of register space).
Following release of NRESET, the ISD-300A1 waits 50ms, then checks for I
device is present but does not pass signature check (first two data bytes must equal 0x4D54), the ISD-
300A1 re-tests the signature with each vendor specific USB load or read access of configuration bytes 0
and 1. Once the signature check passes, I
is detected initially, it is always assumed present until the next reset cycle (NRESET). If an I
present, a lack of an ACK response when required causes the ISD-300A1 to stall that USB request. The
ISD-300A1 will attempt the access again with the next USB request.
Programming of the I
300A1 supported vendor specific USB commands, or using a “bed of nails”. An example of I
device data formatting is shown in Appendix A – Example EEPROM or FBh Identify Data Contents.
2
C Memory Device Interface
Yes
Yes
No
No
No
I
Memory
Device
present
2
C
Yes
Yes
No
X
X
2
C memory device can be accomplished using an external device programmer, ISD-
Signature
Check
Passes
Yes
Yes
No
No
X
2
C data is returned for USB descriptor requests. If an I
ISD-300A1 Configuration and USB Descriptor Retrieval
In this mode, the ISD-300A1 uses internal ROM contents for USB
descriptor information and configuration register values. This mode
is for debug / manufacturing operation only. Not for shipping
products.
In this mode, the ISD-300A1 uses internal ROM contents for USB
descriptor information. Configuration register values are loaded
from internal ROM. This is not a valid mode of operation.
The ISD-300A1 retrieves all Descriptor and Configuration values
from the vendor-specific Identify (FBh) data. The ISD-300A1 is
configured using internal ROM values until FBh data becomes
available.
The ISD-300A1 uses internal ROM contents for USB descriptor
information. Configuration register values are loaded from internal
ROM. In this mode of operation, any ISD-300A1 vendor specific
configuration access causes the ISD-300A1 to recheck the signature
field. Once the signature check passes, SROM data is returned for
USB descriptors requests. This is not a valid mode of operation.
The ISD-300A1 retrieves all Descriptor and Configuration values
from the I
values present in the I
2
8
C memory device is connected.
2
C memory device. The ISD-300A1 is configured using
2
C memory device data.
2
C device presence. If an I
2
ISD-300A1
C device is
2
C memory
2
C device
2
C