Why doesn't Windows re-recognize CY7C65215 devices after COM port connections made on USB 2.0 Hub?

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
miba_4627926
Level 1
Level 1
Welcome!

Windows7

Cypress Windows Driver Package v3.13.0.84

Renesas Electronics USB 3.0 Host Controller Driver v3.0.23.0

Tera Term v4.99

Equipment to simulate system interconnect:

     - StarTech PEXUSB3S4V PCIe  USB 3.0 4 port Card

     - C2G 29525 2-Port USB Hub (required to simulate USB 2.0 environment)

     - Cypress CYUSBS236 DVK Board (2x)

Problem:

Re-connect of Cypress USB device on USB 2.0 hub after opening a session to all COM ports of each device results in Windows "USB Device Not Recognized" message.  Requires (minimum) restart of USB 3.0 Root Hub device to remedy.

Initial connection:  USB Serial Composite Devices on USB 2.0 Hub

Connection after opening & closing session to all COM ports:  Unknown Devices on USB 2.0 Hub

Steps (repeat as necessary):

  1. Connect Cypress A (CYUSBS236 SW1)
  2. Connect to Cypress A COM port 0 (Tera Term "New Connection")
  3. Connect to Cypress A COM port 1 (Tera Term "New Connection")
  4. Connect Cypress B (CYUSBS236 SW1)
  5. Connect to Cypress B COM port 0 (Tera Term "New Connection")
  6. Connect to Cypress B COM port 1 (Tera Term "New Connection")
  7. Disconnect Cypress B COM port 1 (Tera Term "Disconnect")
  8. Disconnect Cypress B COM port 0 (Tera Term "Disconnect")
  9. Disconnect Cypress B (CYUSBS236 SW1)
  10. Disconnect Cypress A COM port 1 (Tera Term "Disconnect")
  11. Disconnect Cypress A COM port 0 (Tera Term "Disconnect")
  12. Disconnect Cypress A (CYUSBS236 SW1)
0 Likes
1 Solution

Hello,

Please bind the manufacturing (MFG) interface of the device to the cyusb3 driver version 1.2.3.20.

Can you uninstall all the currently bound drivers to the device (COM port) and please try the below methods:

1. On initial connect,  bind the device (COM port) to the driver attached to this response (version 3.13.0.84) and check for the issue. Does the issue exist?

2. On initial connect bind the device (COM port) to the Windows CDC Driver (refer to this KBA for steps) and check for the issue, Does the issue exist?

If the issue exists, can you please capture the USB logs for the above cases and provide the same?

Thanks,

Yatheesh

View solution in original post

0 Likes
11 Replies
YatheeshD_36
Moderator
Moderator
Moderator
750 replies posted 500 replies posted 250 solutions authored

Hello,

Can you please let me know the below:

1. Are serial numbers assigned to the USB-Devices (CY7C65215 on the CYUSBS236 DVK)? If no, please assign serial numbers and check if the issue still persists?

2. When the CYUSBS236 DVK is connected for the first time do you perform any transfers with the teraterm before disconnecting it?

3.  Can you please share a snippet of the device manager with the issue and the properties of the device with error (general Tab)

4. Is it the same issue with other HUBs as well, or is it specific a single 2.0 HUB.

Thanks,

Yatheesh

0 Likes

1. Both DVK boards have serial numbers programmed

2. No transfers with Tera Term.  Create a new connection and disconnect (must connect to both COM ports).

3.USBcontrollerUnknownDevice.PNGDeviceManagerUnknownDevice.PNG

4. Issue seems specific to Renesas 2.0 hub.  Generic hub doesn't exhibit the issue.

0 Likes
miba_4627926
Level 1
Level 1
Welcome!

I have tried multiple USB 3.0/3.1 Host controllers

StartTech PEXUSB3S4V

  • PCIe Adapter
  • Renesas chipset
  • Renesas Electronics USB 3.0 Host Controller v3.0.23.0

StarTech PEXUSB314A2V

  • PCIe Adapter
  • ASMedia chipset
  • ASMedia USB3.1 eXtensible Host Controller v1.16.47.2

Dell Optiplex 7020

  • Internal device
  • Intel chipset
  • Intel(R) 8 Series/C220 Series USB EHCI #2 - 8C2D v9.4.0.1025

When following the steps defined in the original message, multiple connect/disconnect actions of the CYUSBS236 ports result in the OS not recognizing the Cypress devices for the Renesas and ASMedia hosts.  This issue is not duplicated on the Intel host.

The issue only exists when the USB tree includes a USB 2.0 Hub between the USB 3.0 Host and the Cypress device.

0 Likes

Hello,

Can you please confirm if the USB 2.0 Hub mentioned in your previous response is only the Renesas 2.0 Hub? or other 2.0 Hubs exhibit this as well?

Thanks,

Yatheesh

0 Likes

I am seeing the issue on Renesas and ASMedia USB 3.0 host controllers with a USB 2.0 hub.  I cannot duplicate with a USB 2.0 hub on the Intel 3.0 host.

0 Likes

Hello,

Is a specific 2.0 Hub between the Renesas and ASMedia USB 3.0 host controllers and USB-Serial Device causing an issue?

If yes, which Hub is it?

Thanks,

Yatheesh

0 Likes

I've seen issues with the following 2.0 Hubs:

  • C2G 2-Port USB Hub Model #29525
    • Bus powered
  • D-Link 4port Model DUB-H4
    • BUs and self powered

I'm trying to find other 2.0 HW to add to the exercise.

A USB 1.1 hub had no issue.

The original issue was found on a USB 2.0 PXIe Switched Hub instrument.

0 Likes

Hello,

Please bind the manufacturing (MFG) interface of the device to the cyusb3 driver version 1.2.3.20.

Can you uninstall all the currently bound drivers to the device (COM port) and please try the below methods:

1. On initial connect,  bind the device (COM port) to the driver attached to this response (version 3.13.0.84) and check for the issue. Does the issue exist?

2. On initial connect bind the device (COM port) to the Windows CDC Driver (refer to this KBA for steps) and check for the issue, Does the issue exist?

If the issue exists, can you please capture the USB logs for the above cases and provide the same?

Thanks,

Yatheesh

0 Likes

The provided Cypress driver v3.13.0.84 still exhibits the issue.  What USB logs need to be captured and how would you like that done?

The Windows CDC driver does not exhibit the issue.

0 Likes

Hello,

Good to see that the windows driver is not showing the issue.

Can you please connect a hardware analyzer between the USB host and the Hub, and capture the logs while the issue is reproduced?

If another hardware analyzer is available, please connect it between the Hub and the USB-Serial Device.

Thanks,

Yatheesh

0 Likes

I only have a USB 2.0 analyzer (TotalPhase Beagle USB12) available at the moment and have captured data between USB 2.0 hub and serial devices.

naming convention --> <driver name>_<dev kit sn>_<date>

Included data for the Windows and Cypress 3.13.0.84 drivers.

Data for Cypress driver was collected until failure occurred.

Attachments in .tdc and .csv format.

0 Likes