• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 32 subscribers
  • Views 1529 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 on Samsung PCOIP zero client.

eric Mollenthiel
Prodigy 50 points
Other Parts Discussed in Thread: TUSB3410

I'm looking on advice for TUSB3410 COM port problem.

We're a canadian bank and in a Virtual Desktop migration project. The PC are replaced by Samsung Zero Client "terminals". These terminal include a builtin com port which is in fact a TUSB3410.   Unfortunatly for us samsung has just started shipping the particular model of zero client (NB-NH)  with the TUSB3410. Until last week the USB/COM port was a prolific... and right when we go production they switched the hardware on us.  All of our testing was done with Prolific.    The only place I could find  a Windows 7 32 driver for the TUSB3410 is here. I downloaded it from the 3410 page. It installs fine, the driver and device seems healthy (COM number is ok) but the particular device we need the COM port for just does not work with the TUSB3410.  If I switch to a terminal with a prolific chip it works. If I use a FTDI USB/COM converter it works right off the bat.

I'm not sure  if the Windows 6.7.2.0 driver I download from TI is a generic driver that whould work with any implementation or if I absolutly need a Samsung specific driver.

Our application is an  inhouse application that prints bank statements on a serial IBM Passbook printer (the windows printer driver is a inhouse serial driver) so we will put our programmers on the issue. But that same print driver works just fine with Prolific and FTDI so I'm assuming it's ok.

We are trying to dig though our Samsung contacts the help us resolve the issue but at the same I'm coming here to see anybody has insight or advice.

Thanks in advance.

Eric

 

  • 0
    TI__Genius 11255 points

    Hello Eric,

     

    The TUSB3410 driver v6.7.2.0 is the latest release driver compatible for all the Windows version (XP, Vista, Win7 and Win8) and as you comment it’s a  generic driver compatible with any device that contains the default TUSB3410’s VID and PID.

     

    I’m wondering if you have tried only using the TUSB3410 driver on a Virtual environment? Unfortunately the TUSB3410 is not supported for virtual environments as it present several unexpected behaviors.

     

    Could you please try in a non-Virtual environment? And verify if you have the same problems?

     

    Regards,

    Roberto.

  • 0 in reply to Roberto Diaz
    Prodigy 50 points

    Roberto,

    Thanks for you answer. 

    We did a series of tests this morning with a pure vanilla Windows and only the v6.7.2.0 TI driver. So the behavior/problem I am having is unrelated to conflicts with other USB/com ports or drivers. 

    Also the Samsung NB-NH I am referring to is a device dedicated to virtual environments and it has a builtin TUSB3410 (on the motherboard).   So yes I have only tested in virtual and we do not have any TUSB3410 in any other form than the Samsung device.   

    I'm new to TUSB3410, is it possible to buy a simple external TUSB34010 USB to COM adaptor (like the many FTDI I have seen) ?. If so I will try to get my hands on one to test outside the virtual environment .

    http://www.samsunglfd.com/product/feature.do?modelCd=LF-NBNHNN

    Eric

  • 0 in reply to eric Mollenthiel
    TI__Genius 11255 points

    Eric,

                     Exists a TUSB3410 EVM (Evaluation module) that you can buy, it’ll work as a USB to com adaptor using the 6.7.2 driver.

                    http://www.ti.com/tool/tusb3410uartpdk#descriptionArea

                    Also I think you should contact to Samsung and explain your problem to them.

     

                    Regards,

                    Roberto.

  • 0 in reply to Roberto Diaz
    Prodigy 50 points

    Very good info thanks Roberto. 

    I've just ordered the EVM, it will really help us build our case and troubleshoot this issue.

    We're also already talking to Samsung on another front.

  • 0 in reply to eric Mollenthiel
    TI__Genius 11255 points

    Hello Eric,

     Contacting Samsung now it’s more clear that it’s a problem between the WDM driver (v1.2.11.08) and the Printer driver.

     

     I have uploaded a TUSB3410 WDM debug driver version to the following FTP site it’ll help us to make a better analysis of the problem,

     

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

     

                    Name: pickup

                 Password: piurh!

     

    Could you please try to reproduce the issue using this driver and capture some logs following the next steps:

     

                    1. Manually install the WDM debug driver.

                    2. Download an d install the DebugView software, you can find it at at http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx

                    3. Select all the options on the “Capture” menu (Capture Win32, capture Kernel, Pass-through, Capture Events)

                    4. Now reproduce the issue and save the log file.

     

                    Please try it using a clean system without previous TUSB3410 drivers installed?

     

                    NOTE: this is a debug driver and should be used only for testing purposes and It’s not a official release.

     

                    Regards,

                    Roberto.

  • 0 in reply to Roberto Diaz
    Prodigy 50 points

    I will work on this tomorrow. 

    Thanks.

  • 0 in reply to Roberto Diaz
    Prodigy 50 points

    Roberto,

    I did the test and set the log file back to Samsung. They did send me a similar request as yours.  I will continue with them to avoid double work. Otherwise the log file is not very explicit (unless this means something to you)

    00000001 0.00000000 [4356] TTYUI: IOemCB:No Interface. Return NULL.
    00000002 0.00006677 [4356] ERROR TTYUI: OEMGetInfo() ERROR_INVALID_PARAMETER.
    00000003 0.00066210 [4356] TTYUI: IOemCB:No Interface. Return NULL.
    00000004 0.00070959 [4356] ERROR TTYUI: OEMGetInfo() ERROR_INVALID_PARAMETER.
    00000005 0.00113255 [4356] TTYUI: IOemCB:No Interface. Return NULL.
    00000006 0.00117892 [4356] ERROR TTYUI: OEMGetInfo() ERROR_INVALID_PARAMETER.
    00000007 0.00317806 [4356] TTYUI: IOemCB:No Interface. Return NULL.
    00000008 0.00321298 [4356] ERROR TTYUI: OEMGetInfo() ERROR_INVALID_PARAMETER.
    00000009 0.00373623 [4356] TTYUI: IOemCB:No Interface. Return NULL.
    00000010 0.00377115 [4356] ERROR TTYUI: OEMGetInfo() ERROR_INVALID_PARAMETER.
    00000011 0.00427317 [4356] TTYUI: IOemCB:No Interface. Return NULL.
    00000012 0.00430865 [4356] ERROR TTYUI: OEMGetInfo() ERROR_INVALID_PARAMETER.
    00000013 0.00540432 [4356] TTYUI: IOemCB:No Interface. Return NULL.
    00000014 0.00543924 [4356] ERROR TTYUI: OEMGetInfo() ERROR_INVALID_PARAMETER.
    00000015 0.00596640 [4356] TTYUI: IOemCB:No Interface. Return NULL.
    00000016 0.00600048 [4356] ERROR TTYUI: OEMGetInfo() ERROR_INVALID_PARAMETER.
    00000017 0.00892991 [4356] TTYUI: IOemCB:No Interface. Return NULL.
    00000018 0.00898438 [4356] ERROR TTYUI: OEMGetInfo() ERROR_INVALID_PARAMETER.
    00000019 0.01243845 [4356] TTYUI: IOemCB:No Interface. Return NULL.
    00000020 0.01247114 [4356] ERROR TTYUI: OEMGetInfo() ERROR_INVALID_PARAMETER.
    00000021 3.90137815 [4356] TTYUI: IOemCB:No Interface. Return NULL.
    00000022 3.90143061 [4356] ERROR TTYUI: OEMGetInfo() ERROR_INVALID_PARAMETER.
    00000023 3.90214539 [4356] TTYUI: IOemCB:No Interface. Return NULL.
    00000024 3.90217757 [4356] ERROR TTYUI: OEMGetInfo() ERROR_INVALID_PARAMETER.
    00000025 3.92882442 [4356] TTYUI: IOemCB:Return NULL.