• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 5136 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 Linux Driver?

James Hillman
Expert 1355 points
Other Parts Discussed in Thread: TUSB3410

Hi everyone,

First time posting about TUSB3410. I am trying to connect the usb-serial link to a linux machine. However, dmseg does not link it to a device number. Does anyone know how I go about getting driver support for this? All the information on the internet seems to be for kernel versions 2.6, I am on 3.13.

Many thanks, 

  • 0
    TI__Genius 11255 points

    Hello James,

     

    The TUSB3410 is included as default since kernel 2.6.1, so it must be enabled by default on kernel 3.13.

     

    I’m attaching you a quick reference that will help you to enable the TUSB3410 driver in case that it’s not enabled.

     

    Regards,

    Roberto.5428.EnableVCPdriverLinux.doc

  • 0 in reply to Roberto Diaz
    Expert 1355 points

    Hi Roberto, Thank you for your fast and detailed reply. How can I tell if its included in the kernel? I setup and the rule as per .doc file but still the dmesg is incorrect. I found the id to be 0x5f00. James. 

  • 0 in reply to Roberto Diaz
    Expert 1355 points

    Hi everyone, anyone?


    I am still struggling with this.

    Aim: to connect MSP-EXP430F5438A board to Ubuntu 14.04LTS via usb-uart provided. (as you do on windows).

    Progress: I have found that the newer version has a different product id 0xF500. If I use command, sudo modprobe usbserial vendor=0x0451 product=0xF500 then connect the device I get the following in dmesg:

    [11436.797764] usbserial: USB Serial support registered for generic
    [11451.362491] usb 3-2: new full-speed USB device number 9 using xhci_hcd
    [11451.398852] usb 3-2: New USB device found, idVendor=0451, idProduct=f500
    [11451.398862] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [11451.398868] usb 3-2: Product: MSP-EXP430F5438
    [11451.398873] usb 3-2: Manufacturer: Texas Instruments
    [11451.398877] usb 3-2: SerialNumber: AFE7894604000F00
    [11451.400972] usbserial_generic 3-2:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes.
    [11451.400991] usbserial_generic 3-2:1.0: Tell linux-usb@vger.kernel.org to add your device to a proper driver.
    [11451.401006] usbserial_generic 3-2:1.0: generic converter detected
    [11451.401261] usb 3-2: generic converter now attached to ttyUSB0

    This is better as before I wasn't getting ttyUSB0. However is this correct - should it not be the ti_usb_3410_5052 driver? I ask, because if I use Python or Miniterm I see nothing (not even on the scope).

  • 0 in reply to James Hillman
    TI__Genius 11255 points

    Hello James, 

    The Linux driver is owned by the Linux community and they can help you with any problem on it. The contact info is

            Developer: “Brimson Laboratories” (www.brimson.com)

            Contact person: Al Borchers (alborchers@steinerpoint.com)

            Download site: www.brimson.com/downloads  - You can find the latest Linux drivers source code or binary files, as well as the release notes (ti_usb_2.6-1.1.tgz )

     

    Regards,

    Roberto.

  • 0 in reply to Roberto Diaz
    Expert 1355 points

    Hi Roberto,


    Not the most helpful reply.

    I have now figured this out - difficult when google is full of rather old fixes.

    Indeed what we expect to happen in the correct system is:

    [  937.271758] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880036a44a00
    [  937.436562] usb 3-2: new full-speed USB device number 6 using xhci_hcd
    [  937.497688] usb 3-2: New USB device found, idVendor=0451, idProduct=f500
    [  937.497700] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [  937.497705] usb 3-2: Product: MSP-EXP430F5438
    [  937.497710] usb 3-2: Manufacturer: Texas Instruments
    [  937.497714] usb 3-2: SerialNumber: AFE7894604000F00
    [  937.499465] ti_usb_3410_5052 3-2:1.0: TI USB 3410 1 port adapter converter detected
    [  937.499526] ti_usb_3410_5052: probe of 3-2:1.0 failed with error -5
    [  937.501455] ti_usb_3410_5052 3-2:2.0: TI USB 3410 1 port adapter converter detected
    [  937.501820] usb 3-2: TI USB 3410 1 port adapter converter now attached to ttyUSB0

    i.e. we want the ti_usb_3410 to pick up the msp-430f5438a which has the tusb3410. HOWEVER the newer tusb3410 on the msp5438a boards have a different ID which isn't hardcoded in the driver - 0xf500.

    To fix this, you would normally modprobe with the product ID and vendor ID. HOWEVER in 2013 this was changed to:


    "

    Remove the vendor and product module parameters which were added a long
time ago when we did not have the dynamic sysfs interface to add
new device ids (and which isn't limited to five new vid/pid pair).

A vid/pid pair can be added dynamically using sysfs, for example:

  echo 0451 1234 >/sys/bus/usb-serial/drivers/ti_usb_3410_5052_1/new_id

for 1-port adapters, or

  echo 0451 1234 >/sys/bus/usb-serial/drivers/ti_usb_3410_5052_2/new_id

for 2-port adapters.

Signed-off-by: Johan Hovold <jhovold@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    "

    So to add the new ID so the driver picks the device up is:
    sudo su (need to be root!)
    sudo echo 0451 F500 > /sys/bus/usb-serial/drivers/ti_usb_3410_5052_1/new_id 

    remember to add this at boot-up


  • 0 in reply to James Hillman
    TI__Genius 11255 points

    Hello James,

    It’s good to know that you have found how to figure it out. Thanks for share the information. 

    Regards,

    Roberto.