TUSB3410 v6.5.9017 is not working with Windows 7 consistently

I downloaded the latest driver v6.5.9018.1 from the site and tried now, I am still getting the same results. Application stops communicating after few times. This is urgent, please help.

Hello Ganapathy,

                Could you please provide us the reproduction steps of the issue? Also if that’s possible could you send us the applications that you are using in order to reproduce the issue at our side? And what is the VCOM configuration that you are using?

                Are using a TI TUSB3410 EVM board or it’s your own design? If it’s your own design could you please provide us your schematic in order to perform a sanity check?

Regards,

Roberto.

What is VCOM? We only deal with the low level firmware for the TUSB3410. As for the schematic, we don’t typically send those out unless there is an NDA in place. I’m attaching the USB to TUSB3410 schematic.

Hello Ganapathy,

                 From our hardware experts:

 1)      The schematic does not show the RESET signal connection, the reset requires a special timing, it is described on section 13.4 of
datasheet.

2)      Terminal /WAKEUP requires an external pull-up to 3.3V (10K should be fine)

Could you please verify that this implementations are correct?

 Everything else looks correct.

The VCOM is the Virtual COM port instance that is created at the TUSB3410 installation.

Regards,

Roberto

Ganapathy,

The driver v6.5.9017 present some transmission issues, could please try using the latest driver v 6.5.9018.1? Its located at: http://www.ti.com/tool/tusbwinvcp

Regards,

Roberto.

Roberto,

I have sent your suggestion to our embedded team. Let's wait for their response.

As I said earlier, I downloaded the latest driver v6.5.9018.1 from the site and tried now, I am getting the same results.7043.Working vs NonWorking.xlsx

I have attached the comparison of USB port settings which I got through USBView. If it is helpful to troubleshoot, please let me know.

Thanks,
Ganapathy

1. The Reset signal is connected to a microprocessor supervisory chip (ADM809TART) 
2. The Terminal/Wakeup signal is connected through a 10kohm resistor to 3.3V.

Hi Roberto,

Thanks for your help so far.

After investigating this issue with several laptops, it seems that this issue is reproducible only in i5 processors. I have tried in three laptops, DELL Latitude E5510, HP EliteBook 8540p and Lenova 431328U, where all are with i5 processors and Windows 7. It is good to connect 1 to max of 4 times, then it blocks the all USB ports. I have tried using v6.5.9017 and latest v6.5.9018.1, with the same results.

Application is perfectly working as expected in i7 processors in different machines. v6.5.9017 and v6.5.9018.1 are working fine.

Could you please help me to resolve this issue in particular with i5 processors since I am facing this issue in large phase?

Please let me know what other information you require to investigate.

Thanks,
Ganapathy

Hello Ganapathy,

                We’ll try to reproduce the issue using a similar laptop i5 Dell latitude E6410 using other applications and I’ll send you our feedback. In the meanwhile as we have not the same application that you are using could you please help us to generate some logs from the issue? I have created a FTP site where you can download the TUSB3410 debug driver version.

I suggest to first uninstall all the pre-installed TUSB3410 instances, If you have installed the driver using the TI installer just run the installer again and remove the drivers. Restart the system afterwards. When windows comes up, connect the 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 it’s possible, you can try it out on a clean PC with no other previous old VCP driver installed.

Note: If you are using a Win7 64-bit system please note that this driver is an engineering version and you’ll require to  boot your Win7 64bits systems on “Disable driver signature enforcement” mode pressing F8 during the system’s startup in order to use an unsigned driver.

                Follow the next instructions in order to download the driver from the FTP site

The ftp pickup directory 'oojutei' was created on 03/07/2012 14:00: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/oojutei

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

           see the hidden pickup directory name oojutei 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/oojutei

List of files in the pickup directory 'oojutei':

TI_WDF_USBUART_SINGLE_DRIVER_TI_V3.3_(Debug_version)_wrapper.zip

Regards,

Roberto.

Ganapathy,

                The issue is present only connecting and disconnecting the TUSB3410 device or it occurs during a transmission? Could you please provide us the reproduction steps in order to reproduce the issue?

                Also I’m wondering if you can reproduce it using the TUSB3410 EVM board?

Thanks and regards,

Roberto.

Hi Roberto,

I have downloaded the debug version of TIUSB driver and attached the debug logs here.

3288.Full DebugView.LOG

[\\CEI3018]
00000001	0.00000000	[3576] In WM_DEVICECHANGE
00000002	0.80940443	[3576] In WM_DEVICECHANGE
00000003	0.80964893	[3492] WM_DEVICECHANGE KillTimer(1013a, 0).
00000004	1.47574997	[3576] In WM_DEVICECHANGE
00000005	1.47717154	[3492] WM_DEVICECHANGE KillTimer(1013a, 0).
00000006	1.48355949	[3576] In WM_DEVICECHANGE
00000007	1.48587739	[3492] WM_DEVICECHANGE KillTimer(1013a, 0).
00000008	1.55735934	[3492] WM_DEVICECHANGE KillTimer(1013a, 0).
00000009	1.55747473	[3576] In WM_DEVICECHANGE
00000010	1.56352472	[3576] In WM_DEVICECHANGE
00000011	1.56395745	[3492] WM_DEVICECHANGE KillTimer(1013a, 0).
00000012	3.57439327	[3492] hkcmd ---In WM_DEVICECHANGE
00000013	3.57441616	[3492] hkcmd ---TVwizard not Enabled
00000014	82.23552704	[3576] In WM_DEVICECHANGE
00000015	82.30072021	[3576] In WM_DEVICECHANGE
00000016	82.30097198	[3492] WM_DEVICECHANGE KillTimer(1013a, 0).
00000017	84.30638885	[3492] hkcmd ---In WM_DEVICECHANGE
00000018	84.30643463	[3492] hkcmd ---TVwizard not Enabled

Issue occurs during transmission.

Steps to reproduce:
1.Open connection
2. Try to read any register
3. Close connection

Try the above for atleast 5 to 10 times. After few times, app will hang.

Regards,
Ganapathy

Ganapathy,

                We have tried to reproduce it using a i5 Dell E6410 laptop without luck using HyperTerminal software, as we have not the software that you are using, could you please confirm if it’s reproducible using our TUSB3410 EVM board?

Regards,

Roberto.

Hi Roberto,

Let me check with embedded team to reproduce the issue with EVM board.

I have attached excerpt of my application, which is enough to reproduce the issue. This application reads the value present in register #1 of connected device with Slave address of 5. Please try to run the application in i5 processor and let me know if you see any issue.

Start TIUSBTestApp.exe and click "Start" button after connecting device through USB

Regards,
Ganapathy

Hi Ganapathy,

                I have testing using your app on a i5 laptop but unfortunately I can reproduce the issue, I only have the following log messages.

                Trying to read register #1. Count 1 of 15

                Unable to read.

                .

                .

                Trying to read register #1. Count 15 of 15

                Unable to read.

                Done.

                 I have tried with different devices and I’m getting the same results. Do you know if I need to use a specific device? And what do you mean with “Slave address of 5”

                Regards,

                Roberto.

Please try this application which will read any register from the connected device.

6064.TIUSBTestApp2.zip

Please try to run it for atleast 5 to 10 times which might reproduce the issue.

Let me know if you have any questions.

Thanks,
Ganapathy

Please let me know if there any updates on this.

Thanks.

Hello Ganapathy,

                 We have tried to reproduce it using the new app that you send us setting all the Baud Rates available on a i5 laptop using Win7-32 and Win7-64 but unfortunately we can’t reproduce the issue, I have run the app a lot of times (more than 50 times) and the devices and USB ports still  working without problems.

                 I’m getting the following messages from your app.

Reading Register #1…1 of 15 times

0         Hex:0x0

Reading Register #1…1 of 15 times

0    Hex:0x0

 .

 .

 .

 Reading Register #1…11 of 15 times

0         Hex:0x0

Done!

                Do you know If your embedded team has been able to reproduce the issue using the TUAB3410 EVM board?

Regards,

Roberto.

Hi Roberto,

I got the following response from my embedded team for your question about EVM board:

-------
We don’t use the EVM board, we use our datalink boards.
-------

As per your above response, let me request embedded team to double check this issue with datalink board. I will let you know once they get back.

Please let me know if you have any other suggestions.

Regards,
Ganapathy