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.

TUSB3210: Unknow device on Window System

Part Number: TUSB3210

Hi Sirs,

Our TUSB3210 will be unknow device on system device manager.

We have install TUSB3410 Single driver but still unknow device

Our schematic as below

FLBDB01_R1_0816.output.pdf

Please tell us how to fix it? have others driver or?

Thanks!!

  • Hello Shu-Cheng,

    Can you please clarify if the device you are using is either TUSB3210 or TUSB3410?

    Have you programmed the required firmware to the external EEPROM? If so, which firmware did you programmed?

    Please provide a screenshot showing the device's "Hardware ID" on Device Manager

    Regards,

    Jorge

  • Hi Sirs,

    Can you please clarify if the device you are using is either TUSB3210 or TUSB3410?

    We use TUSB3210

    Have you programmed the required firmware to the external EEPROM? If so, which firmware did you programmed?

    We don't programmed any firmware to the external EEPROM

    Please provide a screenshot showing the device's "Hardware ID" on Device Manager

    Do you mean this?

  • Hi Sirs,

    Update pic as below

  • Shu-Cheng,

    The TUSB3210 is a General purpose USB controller. You will need to develop a firmware to define the behavior/interface of your device, and the firmware must be programmed to an external EEPROM that should be connected to the TUSB3210 through the I2C interface.

    The TUSB3410 USBUART driver is not intended for this device.

    Regards,
    Jorge
  • Hi Sirs,

    Thanks for your reply.

    For now we only connect and use on OS device manger then saw unknow device.

    On this step, do we still need to develop a firmware to define the behavior/interface of our device?

    As i know it could catch this device on OS device manger ( connected only) then develop a firmware to define the behavior/interface.

    Am i wrong?

  • Shu-Cheng,

    When the TUSB3210 is plugged-in over USB, the bootcode (which is stored on the device's internal ROM) will try to get your firmware from the external EEPROM. If there is no EEPROM, or if the data on the EEPROM is not valid, it will enumerate a USB interface (VID_0451&PID_2136) that would let you program the external EEPROM with your firmware over USB (This can be done using the TUSB3x10 EEPROM Burner - www.ti.com/.../sllc443).

    So what you are seeing when connecting the device is precisely that interface. You still need to develop your firmware (and program that on the external EEPROM) so you can manipulate the GPIOs and perform any other tasks you may need.

    Regards,
    Jorge