USB hosts hubs transceivers Forum Discussions
Are there any time restrictions from power-on to OSC oscillation start?
OSC oscillates after USBHUB (CY7C65642) power is turned on. Is this a problem?
Also, are there any restrictions on the waveform to be input to RESET? For example, is there a rise time specification? I'm wondering if the ramp up rate of the waveform affects the behavior of the HX2VL.
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
Customer uses CYUSB3314 on RISC Linux platform
They ask how to generate Test pattern for SI test.
Could you please provide software guide line ?Show Less
I would like to test and verify the CY7C65630-56LTXC part before placing it on the final production board. A development board with a socket for the part would work great. If there is a socket that is also surface mount could be mounted on our board for a test fixture for us. Can anyone suggest a solution.Show Less
What is the voltage value for recognizing High or Low in the following signal, which is the data signal of CY7C65630-56LTXC?
My understanding is that these lines are differential signals, so the Vih/Vil given in the datasheet cannot be specified.
This is my first post, I hope I've outlined the issue properly. Any ideas would be appreciated.
I designed and manufactured a first article order of a Voxl2(companion computer) 3.0 USB hub breakout board. The USB 3.0 hub/Voxl2 was initially sending data. However, at some point the 3.0 bus stopped functioning. Currently only the 2.0 USB works on the hub.
What I've tested:
- 1.2v/3.3v/5v power in the system looks good on a voltmeter and oscilloscope.
- SS TX-/+ & RX-/+ are going to the correct upstream pins from the Voxl2.
- Visual inspection appears to show no issues.
In troubleshooting I use a Linux terminal command called lsusb & dmesg to ascertain the status of the USB. The CYUSB3328 initially came up as USB 3.0 now the chip appears to only be a USB 2.0. This leads me to believe that something on the chip is "broken"
Would anyone have any ideas on how to further troubleshoot this issue or what could be happening?
Is it necessary to do anything on the device to perform "TD.1.8 Receiver Jitter Tolerance Test at 5 GT/s", which is one of the USB3.0 compliance tests? The certification authority has not been able to perform this test. Please let me know if there are any operations you need.
配置在IIC主模式，在调试CYUSB3314时出现通过Blaster Plus更改PID，复位/重启HUB后，数据未发生改变的情况，已反复确认是配置在IIC主模式下，并且在Blaster Plus中可读到EEPROM存储的是已经修改过的PID数据，同时用示波器监测，IIC总线上在复位/重启时，无数据流，请问，发生这样的情况，可能还有哪些原因？
I have been making composite images and uploading to the EVK board for some time now and just hit a weird situation where the EVK board does not get recognized by the utility when I press the "Get Status" button. The device manager says "usb device descriptor request failed" but the hub still manages to work with my mouse so I'm confused. This happened after a particular composite image upload. Now I'm stuck with the unwanted uploaded firmware and want to revert back to factory settings. Is there a hardware factory reset? Or a software reset that could be accomplished somehow? I did also notice during the upload attempt of the suspect firmware, it failed to upload but somehow the PDO's managed to get changed and the hub is still functional.