TI 3410 USB chipset?

[jefferee]

I have a 4-port USB/serial adapter (Startech ICUSB2324X) with TI 3410 chipset that isn't being recognized by dwc_otg (Pi 3B+, PiCore 13.0.3)

Kernel log from plugging it in:

Code: [Select]

[ 3437.714542] usb 1-1.1.3: new full-speed USB device number 10 using dwc_otg
[ 3437.847792] usb 1-1.1.3: not running at top speed; connect to a high speed hub
[ 3437.854422] usb 1-1.1.3: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice=32.98
[ 3437.854441] usb 1-1.1.3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 3437.854454] usb 1-1.1.3: Product: USB2.0 Hub
[ 3437.856726] hub 1-1.1.3:1.0: USB hub found
[ 3437.858405] hub 1-1.1.3:1.0: 4 ports detected
[ 3438.194540] usb 1-1.1.3.1: new full-speed USB device number 11 using dwc_otg
[ 3438.366927] usb 1-1.1.3.1: New USB device found, idVendor=0451, idProduct=3410, bcdDevice= 1.01
[ 3438.366950] usb 1-1.1.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3438.366963] usb 1-1.1.3.1: Product: TUSB3410 EECode Ser
[ 3438.366976] usb 1-1.1.3.1: Manufacturer: Texas Instruments
[ 3438.366989] usb 1-1.1.3.1: SerialNumber: 40002542
[ 3438.370552] ti_usb_3410_5052 1-1.1.3.1:1.0: TI USB 3410 1 port adapter converter detected
[ 3438.370668] usb 1-1.1.3.1: Direct firmware load for ti_usb-v0451-p3410.fw failed with error -2
[ 3438.370747] usb 1-1.1.3.1: Direct firmware load for ti_3410.fw failed with error -2
[ 3438.370763] usb 1-1.1.3.1: ti_download_firmware - firmware not found
[ 3438.370817] ti_usb_3410_5052: probe of 1-1.1.3.1:1.0 failed with error -2
[ 3438.474567] usb 1-1.1.3.2: new full-speed USB device number 12 using dwc_otg
[ 3438.646929] usb 1-1.1.3.2: New USB device found, idVendor=0451, idProduct=3410, bcdDevice= 1.01
[ 3438.646951] usb 1-1.1.3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3438.646965] usb 1-1.1.3.2: Product: TUSB3410 EECode Ser
[ 3438.646978] usb 1-1.1.3.2: Manufacturer: Texas Instruments
[ 3438.646990] usb 1-1.1.3.2: SerialNumber: 40002543
[ 3438.650532] ti_usb_3410_5052 1-1.1.3.2:1.0: TI USB 3410 1 port adapter converter detected
[ 3438.650654] usb 1-1.1.3.2: Direct firmware load for ti_usb-v0451-p3410.fw failed with error -2
[ 3438.650743] usb 1-1.1.3.2: Direct firmware load for ti_3410.fw failed with error -2
[ 3438.650764] usb 1-1.1.3.2: ti_download_firmware - firmware not found
[ 3438.650824] ti_usb_3410_5052: probe of 1-1.1.3.2:1.0 failed with error -2
[ 3438.754542] usb 1-1.1.3.3: new full-speed USB device number 13 using dwc_otg
[ 3438.926932] usb 1-1.1.3.3: New USB device found, idVendor=0451, idProduct=3410, bcdDevice= 1.01
[ 3438.926954] usb 1-1.1.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3438.926967] usb 1-1.1.3.3: Product: TUSB3410 EECode Ser
[ 3438.926980] usb 1-1.1.3.3: Manufacturer: Texas Instruments
[ 3438.926992] usb 1-1.1.3.3: SerialNumber: 40002544
[ 3438.930526] ti_usb_3410_5052 1-1.1.3.3:1.0: TI USB 3410 1 port adapter converter detected
[ 3438.930650] usb 1-1.1.3.3: Direct firmware load for ti_usb-v0451-p3410.fw failed with error -2
[ 3438.930740] usb 1-1.1.3.3: Direct firmware load for ti_3410.fw failed with error -2
[ 3438.930761] usb 1-1.1.3.3: ti_download_firmware - firmware not found
[ 3438.930816] ti_usb_3410_5052: probe of 1-1.1.3.3:1.0 failed with error -2
[ 3439.034597] usb 1-1.1.3.4: new full-speed USB device number 14 using dwc_otg
[ 3439.206928] usb 1-1.1.3.4: New USB device found, idVendor=0451, idProduct=3410, bcdDevice= 1.01
[ 3439.206949] usb 1-1.1.3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3439.206963] usb 1-1.1.3.4: Product: TUSB3410 EECode Ser
[ 3439.206976] usb 1-1.1.3.4: Manufacturer: Texas Instruments
[ 3439.206989] usb 1-1.1.3.4: SerialNumber: 40002545
[ 3439.210532] ti_usb_3410_5052 1-1.1.3.4:1.0: TI USB 3410 1 port adapter converter detected
[ 3439.210655] usb 1-1.1.3.4: Direct firmware load for ti_usb-v0451-p3410.fw failed with error -2
[ 3439.210744] usb 1-1.1.3.4: Direct firmware load for ti_3410.fw failed with error -2
[ 3439.210764] usb 1-1.1.3.4: ti_download_firmware - firmware not found
Any ideas? Everything I've used up to this point has been FTDI and worked out of the box.

Thanks!

[jefferee]

Update:

Googling "ti_3410.fw" and "ti_3410.fw location" turned up a blob:
https://github.com/joxer/raspberry-pi-joxer-kernel/blob/master/firmware/ti_3410.fw
which works when copied to /lib/firmware, as suggested here:
https://e2e.ti.com/support/interface-group/interface/f/interface-forum/659721/linux-tusb3410-tusb3410-linux-firmware

So... yay?

[Rich]

Hi jefferee
You can copy  firmware-ti-connectivity.tcz  from the x86 repository:
http://tinycorelinux.net/12.x/x86/tcz/

[jefferee]

Can confirm that the x86 version of firmware-ti-connectivity.tcz works.

Thanks, Rich!

[Rich]

Hi jefferee
You are welcome. Which version of piCore are you using, 12, 13?

[jefferee]

I'm using PiCore  13.0.3.

[Rich]

Hi jefferee
Added  firmware-ti-connectivity.tcz  to the piCore13 repository.

[jefferee]

Thanks.

With further testing I was a little premature in saying firmware-ti-connectivity.tcz works.
The USB/RS-232 converter correctly initializes after a reboot, but not after a power down.
On power up the kernel log is still reporting that firmware direct load fails:

Code: [Select]

[ 3438.370552] ti_usb_3410_5052 1-1.1.3.1:1.0: TI USB 3410 1 port adapter converter detected
[ 3438.370668] usb 1-1.1.3.1: Direct firmware load for ti_usb-v0451-p3410.fw failed with error -2
[ 3438.370747] usb 1-1.1.3.1: Direct firmware load for ti_3410.fw failed with error -2
[ 3438.370763] usb 1-1.1.3.1: ti_download_firmware - firmware not found
What *does* appear to work is creating a tcz that extracts ti_3410.fw to /lib/firmware (I call it ti_3410.fw.tcz),
dropping it into tce/optional, and adding it to onboot.lst.
This is in fact all that is needed to get my chipset up and running; having firmware-ti-connectivity.tcz extract at boot is not necessary.

I'm going to shrug and say, "eh, TI", but wanted to report the solution here for future googlers.

[Rich]

Hi jefferee
firmware-ti-connectivity.tcz  should probably be listed in  onboot.lst  before  net-usb-KERNEL.tcz  so the firmware
is available for the driver.

Also, it is not uncommon for firmware loads to fail initially. They usually succeed later after the firmware
extension has loaded.