• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 32 subscribers
  • Views 755 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.

TUSB 3410 Manufacturer string descriptor issue

harshit
Expert 1090 points
Other Parts Discussed in Thread: TUSB3410

HI Roberto,

 

  We have used the TUSB3410 to UART EVM reference design to build a USB to serial device. We wanted to display our own string when the device is plugged into windows. For this I used the I2C header generator utility to modify the PID and VID and the EEPROM programmer application to program the eeprom.

But after modifying the config file to custom PID and VID and string descriptors the device gets detected as TUSB3410 device and shows default descriptors in the driver details.

 

Please help to resolve this issue.

 

 

regards,

Harshit

  • 0
    TI__Genius 11255 points

    8130.TUSB3410 Implementation Tips.doc

    Hello Harshit,

     

                    Apparently your are missing something in the process I’m attaching you a quick guide to perform the changes, please verify if you are missing something.

     

                    Please let me know your comments.

     

    Regards

    Roberto.

    2746.TUSB3410 Implementation Tips.doc

  • 0 in reply to Roberto Diaz
    Expert 1090 points

    Hi Roberto,

     

    Thanks for the reply...... and the well guided document

    I had earlier referred your post for the same topic and has followed all the steps till point j). Could you elaborate more on your last point as follows.

     

    1. "You can now proceed to install your TUSB3410 implementation using any Windows, Linux or Mac OS-X Virtual COM port driver example."

    Is there any more modifications to be done before handing over it to customer. We wanted to avoid any modification in the inf file at the customer end. Is it required to modify the strings in INF file. If yes which file has to be modified????.

    Because as I have followed your instructions correctly till 'J'. And when I plugged the programmed board once again it showed the same descriptors. I used the TUSB3410 VCP driver supplied by Texas Instruments.

     

    Regards,

    Harshit.

  • 0 in reply to harshit
    TI__Genius 11255 points

     

    ·         Hello Oliver,

     

    Before install the driver the customer will need to modify the .inf file. And add their VID/PID, also they can remove the TI’s VID/PID from the .inf file.

     

    After running the Installer wrapper file and before run the Installer provided by TI at http://focus.ti.com/docs/toolsw/folders/print/tusbwinvcp.html the .inf file is usually located located at:

     

    C:\Program Files\Texas Instruments Inc\TUSB3410 Single Driver Installer\DISK1\Windows\tiinst\TUSB3410\Common-64\usbuart3410.inf for 32-bit and

    C:\Program Files\Texas Instruments Inc\TUSB3410 Single Driver Installer\DISK1\Windows\tiinst\TUSB3410\Common-32\usbuart3410.inf for 64-bit

    Include your VID/PID in the following lines (in this example I have added the VID=0451 and PID=5678)

     


    Now connect your device and install the driver. I recommend you don't use the installer distributed for TI for use this modified INF file, I recommend to the customer to create a newinstaller for their specific device.

     

    NOTE:Please remove all the old driversbefore to install the modified inf.

    Note2: The digital signatures will be lost when the customer modify the INF file; that’s because the digital signatures are linked to a specific INF file.

    Regards,

    Roberto,

  • 0 in reply to Roberto Diaz
    Expert 1090 points

    Hi Roberto,

     

    Thanks for your reply. I have followed your instructions and could observe the change in the string descriptors when device is getting detected.

     

    Roberto Diaz said:

    I recommend to the customer to create a newinstaller for their specific device.

     

    I need your help in creating a customized installer for the same. Could you please suggest the right installer creator software and what all files must be included in the installer before distributing it to the customer.

     

    Regards,

    Harshit

  • 0 in reply to harshit
    TI__Genius 11255 points

    Harshit,

     

                    We use InstallShield to build our installers, but you are free to use the software that is better for you. Some customers only perform the necessary changes to the INF files including their VID/PID and creates a new installer that simply execute the TI installer.

     

                    Regards,

    Roberto.