USB hosts hubs transceivers Forum Discussions

Hi I am using CYUSB4357-BZXC Hub IC with US as Type C port and DS1 and DS2 as Type C port and DS6 and DS7 as usb2 ports. how can i disable PD functionality completely from hub and use for hub purpose? I have followed recommendation mentioned in below link. After that, with Type C to Type A cable will detect as Superspeed hub, generic hub and DMC controller under device manager, but if we use Type C to Type C cable, its continuously resetting/ refreshing in device manager. Do we need to provide external pulldown on both CC pins? Or firmware flashing needs to be done to work as Super speed HUB( am not sure programming is mandatory or not). How can i enable DS6 and DS7 power switch? i am referring CY6611 schematic for my design. https://community.infineon.com/t5/Knowledge-Base-Articles/Use-EZ-USB-HX3PD-as-Type-C-hub-by-disabling-PD-from-US-and-DS-ports-KBA234778/ta-p/336058 Show Less

The data sheet calls out maximum current consumption of 526mA on the combined 1.2V rails. They don’t specify how that  the maximum consumption is spread  between the DVDD12 and the AVDD12 rails. Could you please provide that data ?

 

 

 

Show Less

Hi Cypress

We have Two FX3 connect to HX3PD hub design in our system board. The goal is to stream data on both FX3 at the same time.

The issue we seens is:
1.) Connect PC to the hub. The hub will connect to two FX3. Two FX3 will connect FPGA<->Sensor.
2.) See Two bootloader shown on device manager.
3.) Load Two Firmware into FX3.
4.) See device manager has Two Streamer Example (Means firmware successfully loaded)
5.) Try Data steam on both device using CyAPI Xferdata
6.) One FX3 able to grab data, One FX3 Xferdata() return false. 0 data grabbed <-Issue.

The workaround is.
1.) do FX3 reset on the FX3 that not able to grabbed data.
2.) Load only the one firmware back again to the FX3
3.) Try Data steam on both device using CyAPI Xferdata
4.) Now could grab data on both device.

*Note:
a) Both FX3 firmware are identical for two FX3.
b) when steps 6 happens, the control end point of two FX3 still able to function. host able to communicate to either both FX3 correctly and able to read/write register to fpga thru either FX3 correctly.
c) After the workaround where two fx3 could data stream, we closed the host software and reopen again. The fx3 also can do data steam on both.
c) before the workaround, we closed the host software and reopen again. The behavior is same where only one fx3 can grab data only. it somehow need to reset and load firmware again for the no data fx3.
d) We using 32bit mode GPIF on firmware. Host using CYAPI C++

Any clue where we can debug this issue?
Thanks

 

Show Less

Hi All,

In our setup, we have a USB3 extender with local and remote units.  The Cypress Hub is on the Remote extender with two devices.  This is the setup

Host ....Local Extender ....Remote Extender..CYUSB3314-88LTXC Hub ----Seagate Backup Plus Portable Drive 1TB

                                                                                                                                            -----Aver VB342 (Isochronous) camera

When we cycle the power for the Remote or Local extender unit, we observe that sometimes the Hub does not enumerate. In these cases, the Host attempts three Warm Resets and when the Hub does not enumerate on the third attempt, the host gives up.

The above issue only happens when we have the Ghost Charging disabled on the Hub, but the issue is not seen when the Ghost Charging is enabled on the Hub.

The Lecroy Analyzer Trace collected shows that the Hub sends an NRDY packet but never sends back the ERDY. I have attached the Trace for your reference.

Can someone please let me know what is going on, and why the Hub goes into this lockup state?

Thanks,

Show Less

Hi there,

I am currently using the CY7C65642 hub to connect to a Raspberry Pi CM4 host running the latest mainline kernel (Linux retropie 5.10.103-v7l+) in standalone boostrap mode (i.e with no MCU present). I've been able to get the chip working just fine and then Pi host is recognizing it via lsusb as a connected high speed device. The only problem here is when I disconnect my host directly from the USB-C port (i.e physically pull it out of the docking station). 

Does anyone know why this would be occuring? I've attached my relevant schematics here and setup, as well as the dmesg I get after the console is pulled out of the dock.

Interestingly enough, if I pull the USB-C adapter out the back of the dock and then back in, the device hub enumerates just fine (i.e I can do it mulitple times). A physical removal from the dock itself however results in this dmesg (note that if I pull it out quickly and then reinsert it within a very short time frame, the hub still seems to enumerate as a USB device). 

[ 162.044343] usb usb1-port1: disabled by hub (EMI?), re-enabling...
[ 162.044356] usb 1-1: USB disconnect, device number 5
[ 162.044364] usb 1-1.4: USB disconnect, device number 6
[ 163.554427] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?

VBUS power is delivered to the hub when the CC lines negotiate a USB-C PD contract, the buck steps down the 5V and powers the hub. I currently believe based on my schematics I have the hub being self-powered (i.e the 0 ohm jumper R24 is not populated). 

Basic front dock PCB that has USB-C connector. VCC_5V is connected to SBU_DOCK1 which switches the TS3USB221A mux.  The left FFC connects the front dock PCB (containing the male USB-C plug to the rear board over an FFC). 

USB hub (CY7C65642) inside the dock:

Power circuitry (5v buck reg powering the hub) inside the dock:

USB 2.0 mux switch in console that switches to the docking USB lines to disconnect internal controller when docked: 

Is there anything in my schematic I should fix here/help to debug this issue?

Kind regards,
Benjamin

Show Less

After powering up HX2VL, sometimes OSC stops oscillating even though reset has not been applied. Can a device actively stop OSC? If so, what are the factors?

I think the internal logic is not working at all because the OSC is stuck. Is this correct?

Thanks,
Tetsuo

Show Less

Need MCDS for CYUSB3314-88LTXC to check exemptions for REACH compliance.  If a specific REACH certificate is available for the part number that will work as well.

Show Less

Occasionally one of the connected downstream devices stops working and Error Code 807A3980 is reported to the host.  Is this a Cypress error code? If so, what does it mean?

Show Less

When using CYUSB4357, whether its SPI ROM BIN FILE can use the BIN FILE of CYUSB4347 (Firmware: CYUSB4347-BZXC_FW_2_0_0.bin), the function of Signed Firmware Update is not required at this time.

 

Show Less