• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 552 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.

TUSB3210: When my customized TUSB3210 device is connected to Windows 7, it is recognized as an HID-compliant device, When connecting to Windows 10, it will be displayed as unknown device.

Cheol-Hyeon Cho
Intellectual 310 points
Part Number: TUSB3210


The device was built with TUSB3210 + EEPROM,
Firmware to HID compliant device was created and put in EEPROM.

In Windows 7, it is normally recognized and communicates well. (VID_0451 & PID_3210)
But, in Windows 10, booting with EEPROM firmware is not possible. (VID_0451 & PID_2136)
After that when it is connect to Windows 7 again, it is recognized as an HID-compliant device and is doing well. (VID_0451 & PID_3210)

What's the problem?
What parts should I look for further?
Is there a compatibility issue on Windows 10?

  • 0
    Intellectual 310 points
    Hmm,

    It has been confirmed that the boot code works because the EEPROM information is erased.
    In Windows 7, the new firmware works through the firmware loader driver,
    In Windows 10, this is what happens because there is no loader.

    To solve this problem,

    EEPROM WP pin pulled up to HIGH,
    Installing the firmware loader driver on Windows 10.

    I have been suffering for three days.