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

TUSB3410 driver issue in Win7

Bahram Moinvaziri
Prodigy 70 points
Other Parts Discussed in Thread: TUSB3410

Hi,
We are using the Texas Instrument driver TUSB3410 with our XL50 product – our XL50 product uses the TI chip and has two ports, a serial port and a USB (2.0) port.  I have written a terminal emulator program which communicates to the DB9 serial port and also to the USB port, well except when the user pulls the USB cable out of the XL50. In this case, the TUSB3410 driver which we installed from the TI web site is removed from the Device Manager and the terminal emulator’s memory is “internally” corrupted due to buffer over-run. Other times, the driver and the terminal emulator work fine and memory leak detections program do not detect any leaks. We are running this under Win 7 but our clients could use WinXP or Win7 (32 or 64).  Is there a configuration on the driver side to have Windows 7 not remove the driver when the USB cable is unplugged?

Thanks,
Bahram

  • 0
    TI__Genius 11255 points

    Hello Bahram,

    Could you please help us to clarify the issue scenario? When you mention that you “disconnect the USB cable”, it means that you are unplugging the TUSB3410 from the system?

    Regards,
    Roberto.

  • 0 in reply to Roberto Diaz
    Prodigy 70 points

    Hi Roberto,
    We based on the link we have "http://www.ti.com/product/TUSB3410", TUSB3410  refers to the Texas Instrument chip. We are using this chip i.e. TUSB3410 in our product as part of the circuit board for XL50 http://www.enteq-xxt.com/pdfs/XXTPDS-XL50-29APR2013-RevA.pdf. In the PDF link in previous sentense, the picture on the bottom right, you see the USB port.  The PC connects to this USB port through a cable. So, to answer you question, when we say "disconnect the USB cable, we are saying remove the USB cable to the XL50 which then the host terminal emulator session is disconnected from the TUSB3410 chip. But this also removes the device driver in the host PC from the windows host PC causing the issue described in our original message.
    Best Regards, 
    Bahram 

  • 0 in reply to Bahram Moinvaziri
    TI__Genius 11255 points

    Baham,

    As you are disconnecting the USB cable then the TUSB3410 instance are going to disappear from the DeviceMager, it’s an expected behavior since the device is not more present on the system.

    Unfortunately there is no a “special configuration” on the driver side that be able to keep the driver instance on the device manager when the device is not present.

    Regards,
    Roberto.

  • 0 in reply to Roberto Diaz
    Prodigy 70 points

    Hi Roberto,
    Ok, i understand that the driver is leaving because the user unplugged the USB cable. But this should not cause a crash in the Kernel DLL. The reason i am sure this is caused by removing the USB cable is because this problem is very repeatable on my side to the point where when the debugger stops at the WriteFile breakpoint, i disconnect the cable and then execute the command and the crash happens. So, although your response to the original question is satisfied, the issue that caused me to write the post has evolved and i still have an issue with the TUSB3410 driver.
    Best Regards,
    Bahram