Other Parts Discussed in Thread: TUSB2036, TUSB3410, TPS2044
Hello all,
I am having problems with the TUSB2036 HUB device and I was hoping someone here could help me out. My design followed the reference designs where possible and is highlighted below:
- TUSB2036 configured as a two port hub (NP3 pin HIGH).
- Self-powered hub (BUSPWR pin HIGH)
- Each port has a TUSB3410 permanently attached device (Header file in external I2C EEPROM, Binary firmware on PC, Serialized)
- 48 MHz oscillator (MODE pin HIGH)
- No EEPROM to force default VID/PID (EXTMEM pin HIGH) to rely upon the default VID/PID settings for the OS (WinXP, SP3) to recognize a General Purpose USB Hub (as per datasheet).
- No over current detection circuity (OVRCUR1, OVRCUR2, OVRCUR3 pins HIGH though 10K pull-up)
- No Power-On/Off control (PWRON1, PWRON2, PWRON3 pins N/C)
- Permanatly attached 2 device (NPINT1, NPINT 0 pins HIGH)
I cannot get my OS (WinXP, SP3) to recognize the device as a General Purpose USB Hub. When I attach the device windows prompts with a bubble saying that “USB Device Not recognized”. Under the Device Manager / Universal Serial Bus controllers I see an “Unknown Device” pop up. When checking the properties / details of this device I read that it has a VID_0000&PID_0000. The full device instance id is listed below:
USB\VID_0000&PID_0000\5&132757A4&0&2
Is there a specific driver I must load to communicate with the TUSB2036? What should the default VID/PID combination be for the TUSB2036? Is it necessary to remove downstream USB devices (i.e. the TUSB3410) to allow the OS to install the proper drivers for the TUSB2036, then power down and install these downstream ports? Any ideas on where to troubleshoot the design? Again, a sample schematic is available.
Thanks in advance for your support
BMurphy