• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 820 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TUSB3410 issue on Win7

Patrick Chen(TPE System & Application)
Expert 3430 points
Other Parts Discussed in Thread: TUSB3410

Hi Sir,

We have a USB to Serial board with TUSB3410, sometimes PC detected a “MicroSoft Serial BallPoint” device after connected TUSB3410 with PC, please see the attached picture, you can find the Location of “MicroSoft Serial BallPoint” is on TUSB3410 Device, do you have any idea? does that relate to driver? Please advise, thank you.

 

We are working on Windows 7 PC, and the driver for TU3410 is TI_WDF_USBUART_SINGLE_DRIVER_V6.7.2.0_WHQL, FYI.

Thanks,

Patrick

  • 0
    TI__Genius 11255 points

    Hello Peter, 

    We never have seen this behavior before,

     -Are you using our default driver or the customer modified the INF file?

    -It has been tested in a clean system? I would like to avoid any conflict with other drivers.

     Regards,

    Roberto

  • 0
    Guru 272490 points

    This has nothing to do with the TUSB3410 itself.

    The Microsoft Serial Ballpoint could, in theory, be connected to any serial port. Therefore, Windows probes every serial port to see if such a device is present.

    A single "M" or "B" character reveived after twiddling the DTR/RTS lines is enough to detect some mouse, so any other device that sends data without being explicitly prompted can be misdetected.

    This is known bug, but Microsoft will not fix this as long as there might be users of actual Ballpoint devices.

    See this or that thread for partial workarounds.