USB hosts hubs transceivers Forum Discussions

We have a board with a CY7C65620 USB HUB connected to a M95080 SPI EEPROM.
The EEPROM is empty and we need the CY7C65620 USB HUB to program it.

The CY7C65620 datasheet states the following:
"If a blank EEPROM is connected, the hub enumerates as vendor defined
class instead of a hub class. This is for the purpose of programming
the EEPROM with the Cypress driver"

This triggers the following questions.

We want to program the SPI EEPROM with the CY7C65620. We have
linux up and running on our board, is there anyway this can be done from
linux ?

What is (and how to get) the Cypress driver ?

Will the USB HUB operate normally if it enumerates as a vendor defines
class (if EEPROM is blank) ?

Thanks in advance for any advice/answers.

---
NvBolhuis

Btw. the reason we need the CY7C65620 to program the SPI EEPROM
is that even though RSTN (pin 45) is set, the CY7C65620 still
pulls down SPI_CS and SPI_CLK. This makes it impossible for
another SPI master to access the SPI EEPROM.
 

We have been using the Cypress USB 2.0 microcontroller (e.g. CY7C68013A) in our device for quite along time. Our customers are asking for USB 3.0 (and have been for some time). Ideally we would like to continue using a Cypress chip in the next version of our device.

Could you please let me know the best estimate of when a Cypress USB 3.0 device chip will be available and also if/when a development environment will be available?

Thanks.

Ian

Hi,

My PC couldn't detect the cy7c67300 after I loaded the msc firmware into EEPROM.The usb device in the bottom right corner of PC windows is missing!The following steps are my loading process.

1.[cy]$ cd Source/stand-alone/msc

2.[cy]$ make clean all

3.[cy] $ make

4.[cy]$ make clean wrap

5.[cy]$ load_i2c

The result is that the PC couldn't detect cy7c67300 after I did as the bash prompt told me to reset the button on the board. I have no idea about it,can you help me?

Thanks,

sunlei

Hi, I'm using Xilinx ML403 development kit which contains CY7C67300-100AXI. I'm trying to establish an USB communication via cy chip using HPI interface. I'm using fpga(virtex4) as uBlaze processor.

Xilinx tools contains sample project which configures cy as host, and reads the inputs from a USB keyboard. At my first try, the given code worked properly. However, after several days, when I loaded the very same bit file into the fpga, it did not work.

As to remember, given code works as follows, hard resets the cy, loads binary file into the cy, soft resets the cy, wait for COMM_ACK( 0x0FED ) from the cy, sets the program counter. Then communication is established. However, in my second try rather than sending COMM_ACK message, cy sends 0xFA58 constantly. Eventhough I looked at AN6010 "Using HPI", I have found no meaning for this message 0xFA58.

Simultaneously, direct connection with cy is also gone. When I connected the peripheral2 port of ML403 to my computer(Windows XP Pro SP2), after the installation of the driver, I was able to use bash environment and read the values of the internal memory of cy using qtudump command. Now, when I plug the USB cable in, my computer does not recognize anything; not fail to enumerate, simply recognize no new device attached. And of course, bash environment returns "USB device not found" error.

Is there anyone who experinced the same or similar problem? I don't know where to start debugging. Can there be any physical damage on the cy chip? Or, do some booting/loading functionality work incorrectly?

Dears:

I have two USB camera need to connect to PC by one chip. I also need some GPIO to realize simple control logic.

Firstly, I selected the USB Hub----CY7C65113C, but then I found it is not recommend to use in new design.

So I want to change to another way which use USB Host----CY7C67300, two usb host interfaces connected with camera, usb otg connected to PC. See picture as attached.

But it is only a idea, I really don'y know whether it is feasible. Please suggested. Thanks!

Hi Experts,

I'm using the USB transceiver CY7C68003. In the datasheet, we can see that there's some difference for the pin order between the two type of package for this device.

24-Pin QFN: counter-clockwise, DATA[0], DATA[1] ... DATA[7]; DP, DM.

20-Ball WLCSP: counter-clockwise, DATA[7], DATA[6] ... DATA[0]; DM, DP.

Who can tell me why there's such a difference pin order between the two type of package?

Does Cypress suggest that when using the 24-Pin QFN package, put it on the same side on the PCB with the MCU, and when using the 20-Ball WLCSP package, put it on the opposite side on the PCB with the MCU?

Any help will be appreciated!

Phaedo Ding