• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 34 subscribers
  • Views 333 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TUSB8042: Hub only showing up as "Texas Instruments Vendor-Specific Device" or "Unknown Device"

Stefan S
Prodigy 55 points
Part Number: TUSB8042
Other Parts Discussed in Thread: HD3SS3220

Hi,

I'm trying to implement a hub using the TUSB8042, I have produced a board, and the device shows up if I plug it in, but only as "Texas Instruments Vendor-Specific Device" (in osx) or "Unknown Device" (windows). I'm using a usb-c upstream and a HD3SS3220 between the hub and usb-c connector. Do you have any tips on where to start troubleshoot? 

This is how it shows up in OSX:

Thanks!

  • 0
    TI__Guru 60870 points

    Hi Stefan,

    The hub is in programming mode, SMBUSz should be high if you are not planning to use EEPROM or a SMBUS controller..

    Regards,

    JMMN

  • 0 in reply to JMMN
    Prodigy 55 points

    Ok, good, interesting!

    I am planning to use EEPROM (I need to change USB2.0 polarity on the hub-ports), and the EEPROM currently mounted and connected, but not programmed. I was under the impression (from the datasheet) that it would just load default config, if the contents of address 00h on the EEPROM is not 55h? Why is it still in programming mode?

    Thanks for input JMMN, very appreciated!

  • 0 in reply to Stefan S
    TI__Guru 60870 points
    Ah, ok that's the other case where the hub will default to programming mode even if SMBUSz is high: a blank EEPROM is attached to the hub with SDA / SCL pullups installed. You will need to either remove the EEPROM, the SDA/SCL pullups or program the EEPROM.

    Regards,
    JMMN
  • 0 in reply to JMMN
    Prodigy 55 points
    Ok JMMN, I will program the EEPROM and see if it exits programming mode!

    Thanks!