I am trying desperately to communicate from Linux (Raspbian kernel 4.4.12-v7+) with a device that uses the TIUSB3410 USB part.
Here is the output from dmesg:
[ 2730.016013] usb 1-1.4: new full-speed USB device number 5 using dwc_otg
[ 2730.161030] usb 1-1.4: New USB device found, idVendor=0451, idProduct=3410
[ 2730.161049] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2730.161062] usb 1-1.4: Product: TUSB3410 Boot Device
[ 2730.161074] usb 1-1.4: Manufacturer: Texas Instruments
[ 2730.161087] usb 1-1.4: SerialNumber: TUSB3410
[ 2730.164670] ti_usb_3410_5052 1-1.4:1.0: TI USB 3410 1 port adapter converter detected
[ 2730.164793] usb 1-1.4: Direct firmware load for ti_usb-v0451-p3410.fw failed with error -2
[ 2730.164934] usb 1-1.4: ti_download_firmware - firmware too large 37874
[ 2730.164986] ti_usb_3410_5052: probe of 1-1.4:1.0 failed with error -5
I have searched high and low for information and nothing works. Any assistance would be greatly appreciated.
I am using the latest Raspbian kernel 4.4.12-v7+
Answered my own question:
I am running a raspberry pi model 3 with the latest debian kernel 4.4.13.
I downloaded the latest source, ran make menuconfig, and most importantly enabled USB TI 3410/5052 Serial Driver located here:
Device Driver --->
[*] USB support --->
[*] USB Serial Converter support --->
<*> USB TI 3410/5052 Serial Driver
It is important to enable each level above by pressing Y to include in the kernel. In my example having the feature modularized M did NOT work.
I followed the instructions here to configure and build the kernel:
https://www.raspberrypi.org/documentation/linux/kernel/building.md
Related
I have a device(STM32 Virtual COM Port).In Linux it is detected normally /dev/ttyACM0. After starting the operating system, I do not receive data from the device. If turn it off and back on it works fine. The problem appears only when I reboot the operating system. Can you tell me how to make it work after restarting the OS.
Its my dmesg
[ 1.077892] usb 1-5: new full-speed USB device number 2 using xhci_hcd
[ 1.228321] usb 1-5: New USB device found, idVendor=0483, idProduct=5740, bcdDevice= 2.00
[ 1.228335] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1.228341] usb 1-5: Product: STM32 Virtual COM Port
[ 1.228345] usb 1-5: Manufacturer: STMicroelectronics
[ 1.228349] usb 1-5: SerialNumber: 5CF862553730
I have a board with an embedded system that is buildroot based. In "make linux-menuconfig" I would like to add the appropriate drivers for the USB-RS232 adapter "Moxa UPORT 1110". I marked in "make linux-menuconfig":
Device Drivers-> USB support -> USB Serial Converter support-> USB MoxaUPORT Serial Driver
after connecting the adapter with the device, linux will not recognize the device.
When I check "lsusb" I get:
lsusb
Bus 001 Device 006: ID 110a:1110
Bus 001 Device 001: ID 1d6b:0002
The board does not see the producer's name etc. On my Ubuntu computer I get after plugging in usb and typing "lsusb ::
Bus 001 Device 036: ID 110a:1110 Moxa Technologies Co., Ltd.
When I check dmesg after plugging in the USB and see:
[ 9752.822985] usb 1-1: USB disconnect, device number 5
[ 9754.605939] usb 1-1: new full-speed USB device number 6 using musb-hdrc
[ 9754.768212] usb 1-1: New USB device found, idVendor=110a, idProduct=1110
[ 9754.775263] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 9754.782783] usb 1-1: Product: UPort 1110
[ 9754.786903] usb 1-1: Manufacturer: Moxa Technologies Co., Ltd.
should I check any additional settings / drivers in "make linux-menuconfig" to see the USB-R232 adapter?
From looking at the Linux source code, I understand that you enabled the mxuport driver which does not cover the UPORT 1110. However, it looks like the ti_usb_3410_5052 driver does. You can enable it by setting CONFIG_USB_SERIAL_TI.
In the Buildroot sources I see that you must make sure that BR2_PACKAGE_LINUX_FIRMWARE_USB_SERIAL_TI is set in order to include the firmware file (moxa-1110.fw).
So, in make menuconfig enable USB TI 3410/5052 Serial Firmware under Target packages > Hardware handling > Firmware > linux-firmware > USB to Serial Firmware
I am running Linux 3.0.35_4.1.0 on a custom freescale i.mx6 board similar to the Boundary devices nitrogen6x board.
The issue i'm having is that when I connect the wireless transceiver dongle for the "Microsoft Wireless Desktop 2000", the mouse works intermittently, and the keyboard does not work at all.
The HID ID of the transceiver is 045e:0745
The error in the terminal is:
root#devonit-tc3:~#
root#devonit-tc3:~# [ 59.225756] usb 1-1: USB disconnect, device number 2
[ 61.050541] usb 1-1: new full speed USB device number 3 using fsl-ehci
[ 61.211567] usb 1-1: device v045e p0745 is not supported
[ 61.224000] input: Microsoft Microsoft® 2.4GHz Transceiver v7.0 as /devices/platform/fsl-ehci.0/usb1/1-1/1-1:1.0/input/input3
[ 61.237194] generic-usb 0003:045E:0745.0003: input,hidraw0: USB HID v1.11 Keyboard [Microsoft Microsoft® 2.4GHz Transceiver v7.0] on usb-fsl-ehci.0-1/input0
[ 61.261561] input: Microsoft Microsoft® 2.4GHz Transceiver v7.0 as /devices/platform/fsl-ehci.0/usb1/1-1/1-1:1.1/input/input4
[ 61.277992] generic-usb 0003:045E:0745.0004: input,hidraw1: USB HID v1.11 Mouse [Microsoft Microsoft® 2.4GHz Transceiver v7.0] on usb-fsl-ehci.0-1/input1
[ 61.327164] input: Microsoft Microsoft® 2.4GHz Transceiver v7.0 as /devices/platform/fsl-ehci.0/usb1/1-1/1-1:1.2/input/input5
[ 61.344711] generic-usb 0003:045E:0745.0005: input,hiddev0,hidraw2: USB HID v1.11 Device [Microsoft Microsoft® 2.4GHz Transceiver v7.0] on usb-fsl-ehci.0-1/input2
[ 62.560605] usb 1-1: reset full speed USB device number 3 using fsl-ehci
[ 63.940594] usb 1-1: reset full speed USB device number 3 using fsl-ehci
[ 64.230571] usb 1-1: reset full speed USB device number 3 using fsl-ehci
[ 65.590572] usb 1-1: reset full speed USB device number 3 using fsl-ehci
[ 65.880556] usb 1-1: reset full speed USB device number 3 using fsl-ehci
A kernel configuration option "Improved Transaction Translator scheduling" (CONFIG_USB_EHCI_TT_NEWSCHED) was necessary.
This allowed the Microsoft Wireless Desktop 2000 to work flawlessly with our device.
I have a smart card reader called SK-284. It support two communication methods, RS232 and USB.
In my case only USB is enable. When I connect this device to my Linux laptop, via USB, It wont get detected. I run '$dmesg' command to check on which ttyUSB port it get detected, I got following output,
[ 2321.208330] usb 2-1.2: new full-speed USB device number 7 using ehci_hcd
[ 2321.384628] generic-usb 0003:8203:8288.0003: hiddev0,hidraw1: USB HID v1.10 Device [\xffffffe6\xffffffb7\xffffffb1\xffffffb7\xffffffb1\xffffffe5\xffffff9c\xffffffb3\xffffff9c\xffffffb3\xffffffe5\xffffff88\xffffff9b\xffffff88\xffffff9b\xffffffe8\xffffff87\xffffffaa\xffffff87\xffffffaa\xffffffe6\xffffff8a\xffffff80\xffffff8a\xffffff80\xffffffe6\xffffff9c\xffffffaf\xffffff9c\xffffffaf\xffffffe6\xffffff9c\xffffff89\xffffff9c\xffffff89\xffffffe9\xffffff99\xffffff90\xffffff99\xffffff90\xffffffe5\xffffff85\xffffffac\xffffff85\xffffffac\xffffffe5\xffffff8f\xffffffb8\xffffff8f\xffffffb8 CRT450 USB 1.1] on usb-0000:00:1d.0-1.2/input0
[ 2326.634925] usb 2-1.2: USB disconnect, device number 7
[ 2326.855479] usb 2-1.2: new full-speed USB device number 8 using ehci_hcd
[ 2326.954303] usb 2-1.2: config index 0 descriptor too short (expected 9, got 0)
[ 2326.954310] usb 2-1.2: can't read configurations, error -22
[ 2327.027211] usb 2-1.2: new full-speed USB device number 9 using ehci_hcd
[ 2327.171371] generic-usb 0003:CEA0:2840.0004: hiddev0,hidraw1: USB HID v1.10 Device [\xffffffe6\xffffffb7\xffffffb1\xffffffb7\xffffffb1\xffffffe5\xffffff9c\xffffffb3\xffffff9c\xffffffb3\xffffffe5\xffffff88\xffffff9b\xffffff88\xffffff9b\xffffffe8\xffffff87\xffffffaa\xffffff87\xffffffaa\xffffffe6\xffffff8a\xffffff80\xffffff8a\xffffff80\xffffffe6\xffffff9c\xffffffaf\xffffff9c\xffffffaf\xffffffe6\xffffff9c\xffffff89\xffffff9c\xffffff89\xffffffe9\xffffff99\xffffff90\xffffff99\xffffff90\xffffffe5\xffffff85\xffffffac\xffffff85\xffffffac\xffffffe5\xffffff8f\xffffffb8\xffffff8f\xffffffb8 CRT284 USB 1.1] on usb-0000:00:1d.0-1.2/input0
My laptop specification:
OS: Ubuntu 12.04
Kernel: 3.2.0-54-generic-pae
When I connect same device to Windows 7 and run device manager, It got detected under Human Interface Device (HID). and some test applications are running fine.
My task is to write a small code on Linux to detect the smart card by device.
So where do I get to know on which ttyUSB port is used by this device, or any other method to get connected to this device.
Thanks in advance.
You may try to change some parameter in usbcore module:
echo y > /sys/module/usbcore/parameters/old_scheme_first
and then replug you usb-device.
As it is full-speed device (not hi-speed) you may also do such thing:
rmmod ehci-hcd
insmod uhci-hcd
insmod ohci-hcd
It seems like there is problem in usb communication. Probably on the usb-device side, because usb-host expects 9 bytes but usb-device sends 0 bytes.
I am working on SBC 6845(Atmel processor) in linux embedded development. My kernel version is 2.6.30.
This board comes with 2 USB ports(Both with Type A), one can be configured as host and other as USB device.
I have configured these USB modules in kernel. I have burned kernel and file system with necessary modules including USB modules. I have loaded these USB modules through /init.d/rcS file.
When board turns on and I type lsmod on console it shows me these modules loaded.
When I connect board to computer, USB is not detected (device functionality).
When I connect pendrive to board, it is not detected (host functionality).
/init.d/rcS Script
#install USB Gadgate mass_storage
modprobe g_file_storage file=/home/mass_storage/backed_storage_file stall=n
losetup -o 4096 /dev/loop0 /home/mass_storage/backed_storage_file
#install USB ehci-hcd
modprobe ehci-hcd
rcS running log
g_file_storage gadget: File-backed Storage Gadget, version: 20 November 2008
g_file_storage gadget: Number of LUNs=1
g_file_storage gadget-lun0: ro=0, file: /home/mass_storage/backed_storage_file
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
atmel-ehci atmel-ehci: Atmel EHCI UHP HS
atmel-ehci atmel-ehci: new USB bus registered, assigned bus number 1
atmel-ehci atmel-ehci: irq 22, io mem 0x00800000
atmel-ehci atmel-ehci: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: Atmel EHCI UHP HS
usb usb1: Manufacturer: Linux 2.6.30 ehci_hcd
usb usb1: SerialNumber: atmel-ehci
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
lsmod output
Module Size Used by Not tainted
ehci_hcd 30132 0
g_file_storage 24260 0
Any help is welcome!
Your drivers seem well installed. I don't have a straight answer but I work with software-hardware integration very often. Here is what I would do to get more clues. That kind of processor often have pins that are multipurposes. Sometimes, on an evaluation board, they are not configured the way we want by default. You can look at the documentation but also, you can use an Oscilloscope and probe the D+ and D- of the USB. Are they OK when in IDLE? What happen when you connect a device on your host port? The first few things will be done by the USB controller and involves little even no interaction with the software after the controller is configured. If you see the beginning of a negociation (a bunch of 0s and 1s) then, you know your hardware is configured properly and your basic driver is installed and work properly. The result of this will narrow the scope of the problem.
You are missing upper layer drivers. EHCI is only an interface driver, you need device drivers on top of it. Board<-->PC communication is usually done via serial over USB, so for this you need USB Serial driver. In Kernel config go to Device Drivers -> USB Support -> USB Serial Converter support and select driver according to the chip on your board/cable.
Here's an example dmesg dump seen when board is connected to the Ubuntu laptop:
[ 3469.923779] usb 2-1.2: new full-speed USB device number 5 using
ehci_hcd
[ 3470.019145] cp210x 2-1.2:1.0: cp210x converter detected
[ 3470.091614] usb 2-1.2: reset full-speed USB device number 5 using
ehci_hcd
[ 3470.184995] usb 2-1.2: cp210x converter now attached to ttyUSB0
I believe similar situation is with pendrive too - upper layer driver is missing.