USB hosts hubs transceivers Forum Discussions
Hi.
We're using CYUSB3304 + i.MX8M-Plus + Ubuntu. Of course I know it is not necessary to use special drivers.
But, we have error messages during Linux startup.
It seems Linux detected CYUSB3304 but failed configuration.
Is there any check points?
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 5.4.70 (wig@wig-TN) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #1 SMP PREEMPT Thu Aug 26 17:37:19 CST 2021
:
[ 3.101915] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
:
[ 3.219038] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 3.227674] platform regulatory.0: Falling back to sysfs fallback for: regulatory.db
[ 3.241825] ALSA device list:
[ 3.244807] #0: audio-hdmi
:
[ 3.342818] usb usb2-port1: config error
[ 3.491748] imx6q-pcie 33800000.pcie: Phy link never came up
[ 3.497442] imx6q-pcie 33800000.pcie: failed to initialize host
Connection:
CYUSB.US_D* - i.MX8MP.USB2_D*
CYUSB.US_TX* - i.MX8MP.USB2.RX*
CYUSB.US_RX* - i.MX8MP.USB2.TX*
CYUSB.VBUS - 10kR PU and PD
MODE* - 10K PU
Show LessHello,
I'm working on a PCBA design that includes a CYUSB3314. The previous version of this PCBA had the same CYUSB3314 hub, and when used with internal ROM mode the hub and the downstream devices enumerated correctly. When I try connecting to the hub on the new PCBA, I only see a device for the USB 2.0 part of the hub (nothing for the 3.0 part) and no downstream devices. The device that shows up has the correct PID (6506), but it's not being recognized as a USB hub and I get an error when trying to bind it to the generic hub driver that comes with the HX3 Blaster Utility.
I've confirmed that the device is getting power and is out of reset (the device disappears from Device Manager when reset is asserted). I've also confirmed that the mode select pins are set for internal ROM mode. I'm beginning to suspect that there's something wrong with the internal ROM, though.
We have an external EEPROM device that can be used with the HX3's I2C master mode. I was able to bind the Vendor driver to the device from Device Manager, but nothing is recognized in the HX3 Blaster Plus tool, so I can't get anything to the EEPROM.
Is there anything else I can try?
Show LessWhere can I find the utility to program the HX2LP (CY7C65621) EEPROM?
Do I need a header on-board to use an external programmer, or does this EEPROM utility allow you to program directly through the HX2LP device?
Thanks.
Show LessWhat would be the closest replacement of CY7C65632-28LTXC. The distributors are saying that there is a manufacturing issue with this HUB. The size is important do not have much room. Need 4 ports.
Show LessHey,
I saw that in the CY4609 schematics files there is a cross in all DS RX lines between the HX3 and the DS connector, USB_DS_RXM is connected to pin 5 of the DS connector which is StdA_SSRX+, what is the reason for that?
thanks,
Show Less
Hey,
I have designed a board with the HX3 with 1 US and 2 DS ports.
Looks like it is working only as USB2, I mean when I connect a USB2 camera it works ok, but when connecting a USB3 camera it does now work.
What can be the problem?
P.s
I'm working with internal ROM boot.
Thanks,
Show LessI am using CYUSB3328-88LTXC hub on a custom board.
US port is towards the main processor (running Android, Linux kernel 4.9), three DS ports are converted to USB-C and the fourth DS port is permanently connected to a USB-ETH bridge. The hub is set in pin-strap mode.
In order to set pin-strap boot, what do I need to set the MODE_SEL pins to? (currently trying 0b11, originally tried 0b01)
PIN_STRAP = 'H'
MODE_SEL [1:0] = 'HH'
I2C_DEV_ID = 'L' is 0x60
ACA_DOCK = 'L'
PORT_DISABLE = 'LL' all DS active
NON_REMOVABLE = 'LL' all DS removable
VID_SEL = 'HHH' default CY VID
PWR_SW_POL = 'H' for DSx_PWR_EN and DSx_OVRCURR active 'H'
PWR_EN_SEL = 'L' Individual DS power switching
DSx_PWR_CDP_EN = 'HHHH' all CDP enabled
Thanks
Show LessI used to use HX2VL before. It is currently considering replacement with HX2LP.
The configuration that worked as HS on HX2VL no longer works on HX2LP. Does HX2LP require specific control? Where is the place to check?
The details are listed below:
- US connects from MCU (directly connects DP / DM of HOST)
- The XIN is supplied with 24MHz from the MCU.
- The RESET pin is controlled by the MCU
- When a FS device (USB memory) is connected to the DS port, the connected device can be controlled from the MCU.
- When an HS device (USB memory) is connected to the DS port, the MCU cannot control the USB memory.
- In HX2VL, it was operating normally as HS in this configuration.
Thanks,
Tetsuo