CYUSB3302 Просмотр технического описания (PDF) - Cypress Semiconductor

Номер в каталоге

Компоненты Описание

производитель

CYUSB3302

HX3 USB 3.0 Hub

Cypress Semiconductor 

CYUSB330x

CYUSB331x

CYUSB332x

I2C Configuration

When enabled for I2C configuration through the MODE_SEL

pins (See Table 4), HX3 can be configured as an I2C master or

as an I2C slave. HX3’s configuration data is a maximum of 197

bytes and HX3’s firmware is 10 KB. Note that HX3’s firmware

also includes configuration settings.

HX3 as I2C Master

HX3 reads configurations from an external I2C EEPROM with

sizes ranging from 16 to 64 KB. An example of a supported

EEPROM is 24LC128. Based on the contents of the bSignature

and bImageType fields in Table 6, HX3 performs one of the

following actions:

■ Loads custom configuration settings from the EEPROM when

bSignature is “CY” and bImageType is 0xD4.

■ Loads the Cypress-provided firmware from the EEPROM when

bSignature is “CY” and bImageType is 0xB0. This firmware also

includes configuration settings.

■ If bSignature  “CY”, HX3 enumerates in the vendor-specific

mode.

The contents of the EEPROM can be updated with the

easy-to-use Cypress Blaster Plus tool. Blaster Plus is a

GUI-based tool to configure HX3. This tool allows to do the

following:

■ Download the Cypress-provided firmware from a PC via HX3's

US port and store it on an EEPROM connected to HX3’s I2C

port.

■ Read the configuration settings from the EEPROM. These

settings are displayed in the Blaster Plus GUI. Modify settings

as required.

■ Write back the updated settings on to the EEPROM. In addition,

an image file can be created for external use.

The Blaster Plus tool, user guide, and the Cypress-provided

firmware are available at www.cypress.com/hx3.

HX3 as I2C Slave

An external I2C master can program the configuration settings

into HX3 according to the EEPROM map in Table 6. Alternatively,

the HX3 firmware (<10 KB), which includes configuration

settings, can also be programmed. It is recommended to use the

Blaster Plus tool to create the HX3 firmware or configuration

image file. HX3’s I2C slave address needs to be provided while

creating the image file. Refer to Table 5 for HX3’s I2C slave

address.

Table 6. EEPROM Map

I2C Offset Bits

Name

0

7:0 bSignature LSB (“C”)

1

7:0 bSignature MSB (“Y”)

2

7:6 bImageCTL

5:4 I2C Speed

3:1 bImageCTL

0 bImageCTL

3

7:0 bImageType

4

7:0 bD4Length

5

7:0 VID [7:0]

6

7:0 VID [15:8]

7

7:0 PID [7:0]

8

7:0 PID [15:8]

Default

Description

0x43

Two-byte signature initialized with “CY” ASCII text

When the signature is not valid, the hub enumerates as a

vendor-specific device.

0x59

Two-byte signature initialized with “CY” ASCII text

When the signature is not valid, the hub enumerates as a

vendor-specific device.

b’00 Reserved

b’11 b’01: 400 kHz

b’11: 100 kHz

b’000 Reserved

0 0: Execution binary file

1: Data file

0xD4 0xD4: Load only configuration

0xB0: Load firmware boot image

All other bImageType will return an error code.

40 bD4Length is defined in bytes as the length from offset 5.

I2C offset bytes 0–4 are the header bytes.

bD4Length = 6: Only update VID, PID, and DID

bD4Length = 18: Configuration options (no PHY trim)

bD4Length = 40: Configuration options with PHY trim options

bD4Length > 40: User must provide valid string descriptors

bD4Length > 192: Error

0xB4 Custom Vendor ID - LSB

0x04 Custom Vendor ID - MSB

0x04

0x65

Custom Product ID (PID)

Default: 0x6504

If separate PID is used for USB 2.0, the USB 2.0 PID will be read

from offset 35 and 36.

Else, USB 2.0 PID = 0x6506

Document Number: 001-73643 Rev. *G

Page 19 of 33

Share Link: