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 based application not able to Open COM port and hangs in Windows 7 32 bit OS which is installed in INTEL Core I5 CPU BIOS A07

Other Parts Discussed in Thread: TUSB3410

Hi,

My laptop (DELL Latitude E5510) has Windows 7 32 bit OS installed in Intel Core I5 BIOS A07. I have installed TI USB 3410 USB to Serial driver 6.5.9017 driver which is compatible with Windows 7. When I try to open COM port, application hangs. When I tried to monitor the port through "Port Monitor" app, port stopped working at CLEANUP point.

Any ideas or any patch that has to be installed in my machine to resolve this issue? Any help will be mostly appreciated.

Thanks in advance

  • Hello Giri,

     

                Could you please provide us the “Port Monitor” application that you are using and the issue reproduction steps? Also if it’s possible, could you provide us what you getting in the device manager?.

     

    Regards,

    Roberto.

  • Hi Roberto,

    PortMon application is available in http://technet.microsoft.com/en-us/sysinternals/bb896644

    I have an application(Modbus tool) which acts an interface to connect to the instrument. Application should open the port, reads the data and closes the port. But application hangs and locks the process. System will not be accessible until restart.

    This issue is specific to my laptop which has Intel I5 with BIOS A07. Application runs in other machines.

    In Device manager, under Ports (COM & LPT), I can able to see TUSB3410 device with driver version 6.5.9017.

  • Could anyone please provide help on this issue?

    Thanks

  • Hello Giri

     

                I have try using a similar laptop (Dell Latitude E6410 i5, BIOS A05) but I can’t reproduce the issue, the “Modbus tool” application send and receive the data through TUSB3410 without problem. Unfortunately we can’t determinate what is the root cause of the issue without the required hardware.

     

    Regards,

    Roberto.

  • Oh! OK. Thanks for your effort on this Roberto.

  • I am still not able to find what causes application to hang on laptops which have Intel I5 or I7 processor with BIOS A05. If anyone have similar kind of issue, please help me to solve it.

    Thanks.

  • Hello Giri,

     

                    As we have not the required hardware to reproduce the issue, could you please help us to generate some logs to analyze the driver behavior. To generate the logs you’ll need to install TUSB3410 driver debug version.

    I suggest to first uninstall all the pre-installed TUSB3410 instances, If you installed the driver using the TI installer just run the installer again and remove the drivers. Restart your system afterwards. When windows comes up, connect your device to PC and the device should be appears on the device manager without drivers installed.

    Now, manually install the debug drivers: Please go to Device Manager --> TUSB3410 ( Right Click ) --> Update drivers Software…  --> Browse my computer for driver software --> Click “Browse” and select the debug driver path --> Click next, now the debug driver will be installed, provably you’ll see a “unsigned driver” warning message because this debug driver is only for debug purposes.

     

    Now you’ll need to install and open the debugView software, you can find it at http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx . Select the “Capture Win32” option in the “Capture” menu, and try to reproduce the issue, debugView will capture all the driver’s debug messages. Now please try to reproduce the issue and save the log file. If possible, you can try it out on a clean PC with no other previous old VCP driver installed.

     

                    Please follow the next steps to download the driver debug version.

     

    The ftp pickup directory 'quooroth' was created on 06/23/2011 10:15:00.

    The files from the dropoff area have been moved to the pickup directory and are available for 7 days.

     

    To retrieve the files from the pickup directory:

     

      1. Open an ftp session to ftppickup.ti.com.

             ftp ftppickup.ti.com

     

      2. Login with the userid 'pickup'.

             Name: pickup

     

      3. Enter the password.

             Password: piurh!

     

      4. Change directories to the pickup directory.

             ftp> cd /pub/share/quooroth

     

         Note: If you are using a graphical ftp client, you will not

               see the hidden pickup directory name quooroth appear

               in the file list.  You will need to use a manual

               'Change Directory' or 'CD' command to change into the

               dropoff directory.

     

      5. Set the file transfer mode to ascii or binary as necessary.

             ftp> bin

     

      6. Transfer the file.

             ftp> get <file>

     

      7. End the ftp session.

             ftp> quit

     

    The files can also be retrieved with the url:

     

      ftp://pickup@ftppickup.ti.com/pub/share/quooroth

     

    List of files in the pickup directory 'quooroth':

    DebugDriver_TUSB3410.zip

  • Sorry Robert. I missed to pickup the DebugDriver files. Could you please place those files in ftp, so that I can provide you the details?

    Thanks,
    Giri 

  • Hello Giri,

     

                    We have fixed some transmission problems related with the i3,i5 and i7 microprocessors, could you please try using this new driver?

     

                    You can find it at:

     

                    http://www.ti.com/tool/tusbwinvcp

     

    Best regards,

    Roberto.

  • Sorry. Even this new driver did not help me. Please let me know if you require any information regarding this to troubleshoot this issue.

    Thanks,
    Giri 

  • Unfortunately we have not be able to reproduce this issues using our EVM board. We have tried in a similar i5 laptops without luck. Apparently this issue occurs only using a specific hardware.  Would it be possible to provide your TUSB3410 hardware for us to test as well as whatever SW app you are running?