Windows PC misidentifies the PID of the HX3 USB hub controller

[ando]

model：CYUSB3324-88LTXC

Event: After turning on the power to the HUB, there are cases where it is recognized as 650B or 650C instead of the Product ID 650A / 6508 originally recognized by the device manager of the Windows 10 PC connected via USB. At this time, the expected driver is not assigned correctly, and communication failure under the HUB occurs.The USB driver is a generic usbhub3.inf.

[Ajeethkumar_P]

Hi,

Thanks for posting in Infineon Developer Community!

Do you use External EEPROM for the custom configuration of HX3? 

If not confidential, can you attach your schematics here? If not Please let us know if you followed our HX3 Hardware guidelines.

Thanks,
Ajeeth

[ando]

I am using an external EEPROM.

The schematics around HX3 that falsely detects PID is attached.

[Ajeethkumar_P]

Hi Ando,

Please share your custom configuration loaded into the EEPROM.

Also, attach the screenshots of driver binding(with unknown driver) when the device is binding with a different driver.

Are the Downstream ports work, when the driver is bound correctly?

Thanks,
Ajeeth

[ando]

Attach the custom settings of the firmware.

   - Ghost charge enable was changed to disabled.
   - I2C speed was changed to 400 kHz.
   - Other settings have not been intentionally changed.

When it is recognized as PID_650B, it looks like Microsoft's usbhub3 driver is bound in Device Manager. The same driver is bound when it is normal.Downstream port does not work when recognized as PID_650B.Attach the USB View and event viewer when it is recognized as PID_650B.

[Ajeethkumar_P]

Hi Ando,

Can you change the I2C clock frequency to 100KHz and try if it resolves the issue?

Also please share the I2C analyzer logs when HX3 is initializing.

Thanks,
Ajeeth

[ando]

Hi Ajeeth,

  How should I get the I2C analyzer logs?

Thank you,

Ando

[Ajeethkumar_P]

Hi Ando,

You can use any Hardware analyzers like Saleae to get the I2C data logs on the HX3 I2C pins.

Please also share the device descriptors for enumerated HX3 device(both SS and HS device descriptors).

Thanks,
Ajeeth

[ando]

Hi Ajeeth,

I got I2C data logs. There was different data than it was normal. please confirm.

Thank you,

Ando

[Ajeethkumar_P]

Hi,

Thanks for sharing the I2C logs.

Do you see this issue in many HX3 silicons?

Thanks,
Ajeeth

[ando]

Hi,

The frequency of this problem is not clear, as it often recovers with a power cycle. At least 3pcs false positives have occurred and I2C confirmation is only 1pcs.

Thank you,

Ando

[Ajeethkumar_P]

Hi,

I have sent you a private message regarding this issue.

Thanks,
Ajeeth