USB Serial Drivers package

All discussions/development regarding the Intel D510 Chip can be placed here.
Traxxi
I'm New!
I'm New!
Posts: 4
Joined: Thu Mar 23, 2017 8:49 pm

Re: USB Serial Drivers package

Postby Traxxi » Fri Mar 24, 2017 7:46 pm

thanx for these informations !

I don't have the usbserial.ko file in /lib/modules.... and i can't find a version compatible with my NAS and DSM 6.1 .... (i didn't find it neither in the Jadahl's package...)

Can you send me your version of "usbserial.ko" ?, so i can test it ?

Thank you again ! :)
Traxxi
I'm New!
I'm New!
Posts: 4
Joined: Thu Mar 23, 2017 8:49 pm

Re: USB Serial Drivers package

Postby Traxxi » Fri Mar 24, 2017 7:53 pm

Good news !!!

While i was writing my last post, i saw that an update of the USB drivers package was realased...

update it ...and...tadaaamm ! it's working !!!

Thank you so much for your help ! :)
bruce_miranda
Rookie
Rookie
Posts: 36
Joined: Tue Oct 13, 2015 10:43 pm

Re: USB Serial Drivers package

Postby bruce_miranda » Fri Mar 24, 2017 10:13 pm

I too have loaded the new version of the package. I'm hoping it solves my issues with the ti serial device. I took the ti*.fw files from the new Domoticz package too, just to be safe. I'll report later how I get on because I see failures in the dmesg log only after a while. For the moment everything seems fine. My FTDI is ttyUSB0 and my HGI80 is ttyUSB1

Code: Select all

[  105.902973] loop: module loaded
[  111.309956] usbcore: registered new interface driver usbserial
[  111.343306] usbcore: registered new interface driver ftdi_sio
[  111.349224] usbserial: USB Serial support registered for FTDI USB Serial Devi                                                                                                                                                             ce
[  111.356849] ftdi_sio 5-2:1.0: FTDI USB Serial Device converter detected
[  111.363672] usb 5-2: Detected FT232RL
[  111.367445] usb 5-2: Number of endpoints 2
[  111.371641] usb 5-2: Endpoint 1 MaxPacketSize 64
[  111.376346] usb 5-2: Endpoint 2 MaxPacketSize 64
[  111.381052] usb 5-2: Setting MaxPacketSize 64
[  111.388326] usb 5-2: FTDI USB Serial Device converter now attached to ttyUSB0
[  112.137347] usbcore: registered new interface driver cp210x
[  112.143098] usbserial: USB Serial support registered for cp210x
[  112.169237] usbcore: registered new interface driver pl2303
[  112.175008] usbserial: USB Serial support registered for pl2303
[  112.211612] usbcore: registered new interface driver ch341
[  112.217335] usbserial: USB Serial support registered for ch341-uart
[  112.464552] usbcore: registered new interface driver ti_usb_3410_5052
[  112.471198] usbserial: USB Serial support registered for TI USB 3410 1 port a                                                                                                                                                             dapter
[  112.479086] usbserial: USB Serial support registered for TI USB 5052 2 port a                                                                                                                                                             dapter
[  112.486901] ti_usb_3410_5052 7-2:1.0: TI USB 3410 1 port adapter converter de                                                                                                                                                             tected
[  113.327564] usb 7-2: reset full-speed USB device number 2 using xhci_hcd
[  113.357441] usb 7-2: device firmware changed
[  113.361789] ti_usb_3410_5052: probe of 7-2:1.0 failed with error -5
[  113.361791] usb 7-2: USB disconnect, device number 2
[  113.373378] xhci_hcd 0000:04:00.0: xHCI xhci_drop_endpoint called with disabl                                                                                                                                                             ed ep ffff880036f64180
[  113.553065] ata1.00: configured for UDMA/133
[  113.557434] ata1: EH complete
[  113.563364] ata2.00: configured for UDMA/133
[  113.567709] ata2: EH complete
[  113.590010] ata3.00: configured for UDMA/133
[  113.594440] ata3: EH complete
[  114.464616] ip_tables: (C) 2000-2006 Netfilter Core Team
[  114.505902] usb 7-2: new full-speed USB device number 3 using xhci_hcd
[  114.547371] nf_conntrack version 0.5.0 (7909 buckets, 31636 max)
[  114.614915] ti_usb_3410_5052 7-2:1.0: TI USB 3410 1 port adapter converter de                                                                                                                                                             tected
[  114.622706] ti_usb_3410_5052: probe of 7-2:1.0 failed with error -5
[  114.632930] ti_usb_3410_5052 7-2:2.0: TI USB 3410 1 port adapter converter de                                                                                                                                                             tected
[  114.641024] usb 7-2: TI USB 3410 1 port adapter converter now attached to tty                                                                                                                                                             USB1
bruce_miranda
Rookie
Rookie
Posts: 36
Joined: Tue Oct 13, 2015 10:43 pm

Re: USB Serial Drivers package

Postby bruce_miranda » Sun Mar 26, 2017 3:35 pm

Unfortunately for me the errors still continue. Theyou don't appear for about a day after a reboot but they eventually appear.

Code: Select all

                   
[Sun Mar 26 13:47:28 2017] usb 7-2: ti_bulk_in_ca
llback - nonzero urb status, -71                 
[Sun Mar 26 13:47:28 2017] usb 7-2: ti_bulk_in_ca
llback - stopping read!
bruce_miranda
Rookie
Rookie
Posts: 36
Joined: Tue Oct 13, 2015 10:43 pm

Re: USB Serial Drivers package

Postby bruce_miranda » Wed Mar 29, 2017 12:04 pm

So an update is that since 24th Mar I've had two instances of the following error. I guess I will just have to live with it. I've set Domoticz to restart the hardware device its inactive for a period of time. That seems to solve the problem. Still cannot understand why I get these issues after the upgrade to DSM 6.1 and I don't know if anyone else gets these or not.

Code: Select all

[Sun Mar 26 12:47:28 2017] usb 7-2: ti_bulk_in_callback - nonzero urb status, -71
[Sun Mar 26 12:47:28 2017] usb 7-2: ti_bulk_in_callback - stopping read!
[Tue Mar 28 00:51:47 2017] usb 7-2: ti_bulk_in_callback - nonzero urb status, -71
[Tue Mar 28 00:51:47 2017] usb 7-2: ti_bulk_in_callback - stopping read!
Gaston_a
I'm New!
I'm New!
Posts: 3
Joined: Tue Mar 29, 2016 11:02 am

Re: USB Serial Drivers package

Postby Gaston_a » Sun Apr 02, 2017 3:40 pm

Hello,

I've just connected my RFXCom rfxtrx433e to my DS1515+.
Drivers installation is ok, and the module seems to be connected :
"usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0"

I try to send this commande to the module, but it doesn't work and I don't know where to find any logs :
echo 0D4302003DD10201010101010000 > /dev/ttyUSB0

Apparently, I need to have the serial connection configured with 38400,8,1,N without handshake but I don't know where to do that.

My system is DSM 6.1-15047 Update 2

Thanks if you could help,
Gaston
jadahl
Sharp
Sharp
Posts: 159
Joined: Tue Dec 16, 2014 6:55 pm

Re: USB Serial Drivers package

Postby jadahl » Sun Apr 02, 2017 6:00 pm

Gaston_a wrote:Hello,

I've just connected my RFXCom rfxtrx433e to my DS1515+.
Drivers installation is ok, and the module seems to be connected :
"usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0"

I try to send this commande to the module, but it doesn't work and I don't know where to find any logs :
echo 0D4302003DD10201010101010000 > /dev/ttyUSB0

Apparently, I need to have the serial connection configured with 38400,8,1,N without handshake but I don't know where to do that.

My system is DSM 6.1-15047 Update 2

Thanks if you could help,
Gaston



Here is some info how to use minicom:
https://help.ubuntu.com/community/Minic ... he_program
https://www.cyberciti.biz/tips/connect- ... nicom.html
Last edited by jadahl on Wed Aug 02, 2017 7:07 pm, edited 1 time in total.
bbelx
I'm New!
I'm New!
Posts: 1
Joined: Tue Apr 25, 2017 11:30 pm

Re: USB Serial Drivers package

Postby bbelx » Tue Apr 25, 2017 11:50 pm

Hello,
I had the same problem as ditbenik when I upgraded my DS216play yesterday to DSM6.1: my USB Rflink stopped working.
I tried to update to the last package from Jadahl: Domoticz for Synology DSM 6.1 with Python Plugin Beta, also tried to install the 6.1 USB Driver, without success: my RFLINK no longer shows up when starting Domoticz :-(:-(

note: I have another stick: "USB teleinfo" that works fine on USBO but I see no other USB..
I tried also to upgrade to the latest version of Rflink but without more success.

Synology DS216play: version DSM 6.1-15047
Domoticz: Version: 3.7376 from Jadahl 6.1 site
Rflink: v1.1 R46

Too bad because until yesterday my set-up worked like a charm :-( .. will be more careful for future DSM upgrades !!
Any idea ?
thanks!!
limpsilver
I'm New!
I'm New!
Posts: 1
Joined: Wed May 03, 2017 4:43 pm

Re: USB Serial Drivers package

Postby limpsilver » Wed May 03, 2017 4:49 pm

Hello jadahl,

I've facing the same issue. I can't see my AEON lab GEN 5.

My NAS : DS112 (DSM 6.1)

Code: Select all

root@DiskStafion:/usr/lib/modules# uname -a
Linux DiskStafion 2.6.32.12 #15101 Thu Apr 20 03:59:56 CST 2017 armv5tel GNU/Linux synology_88f6282_112


I'm using domoticz for DSM 6.1 beta : http://www.jadahl.com/domoticz_beta_6.1/?arch=88f6281

Code: Select all

root@DiskStafion:/usr/lib/modules# lsusb
|__usb1          1d6b:0002:0206 09  2.00  480MBit/s   0mA 1IF  (Linux 2.6.32.12 ehci_hcd Marvell Orion EHCI orion-ehci.0) hub
|__usb2          1d6b:0003:0206 09  3.00 5000MBit/s   0mA 1IF  (xhci_hcd 0000:01:01.0) hub


I tried several different version of domoticz.
I tried with/without usb driver (I know that driver are supposed to be in the spk) from http://www.jadahl.com/synology6.1/?arch=88f6281.
I tried restart the NAS.

Can you help me? Do you need more informations?

Thanks a lot
bruce_miranda
Rookie
Rookie
Posts: 36
Joined: Tue Oct 13, 2015 10:43 pm

Re: USB Serial Drivers package

Postby bruce_miranda » Mon May 08, 2017 10:55 am

bruce_miranda wrote:So an update is that since 24th Mar I've had two instances of the following error. I guess I will just have to live with it. I've set Domoticz to restart the hardware device its inactive for a period of time. That seems to solve the problem. Still cannot understand why I get these issues after the upgrade to DSM 6.1 and I don't know if anyone else gets these or not.

Code: Select all

[Sun Mar 26 12:47:28 2017] usb 7-2: ti_bulk_in_callback - nonzero urb status, -71
[Sun Mar 26 12:47:28 2017] usb 7-2: ti_bulk_in_callback - stopping read!
[Tue Mar 28 00:51:47 2017] usb 7-2: ti_bulk_in_callback - nonzero urb status, -71
[Tue Mar 28 00:51:47 2017] usb 7-2: ti_bulk_in_callback - stopping read!


This bug is very strange. Whenever I restart the NAS, everything will work for about 24-48 hours without an issue and then I get above error messages. This issue has only started since DSM 6.1 and is very frustrating.
hexigen
I'm New!
I'm New!
Posts: 1
Joined: Thu May 11, 2017 3:12 pm

Re: USB Serial Drivers package

Postby hexigen » Thu May 18, 2017 3:33 pm

Jadahl, thank you for your efforts.
I too have similar problem with my Aeon Z-stick 5gen. I can add it in domoticz and it would work for a short period of time and then freeze domoticz or stop communicating.
I noticed that it depends of whether or not I set the "data timeout" setting in the Hardware tab. I'm assuming the Z-stick works shortly after being reset. If I don't reset it sensors stop working after a while.
So I installed your USB serial driver package and then also reinstalled domoticz from your site, built with latest drivers.
My /var/log/messages still shows the following every ten minutes (used to be every minute).

Code: Select all

2017-05-18T09:46:43-04:00 viking synousbmodemd: usbmodem_lib/usbmodem_atif.cpp:114 Unknown vendor id 0658, assign default ATIF
2017-05-18T09:46:44-04:00 viking synousbmodemd: usbmodem_lib/usbmodem_devicenodehandler.cpp:278 No respond on modem cmd AT+CPIN?
2017-05-18T09:46:44-04:00 viking synousbmodemd: usbmodem_lib/usbmodem_simhandler.cpp:50 Warning: sim mute before handler init
2017-05-18T09:46:44-04:00 viking synousbmodemd: usbmodem_lib/usbmodem.cpp:481 failed on setup sim handler
2017-05-18T09:46:44-04:00 viking synousbmodemd: usbmodem_lib/usbmodem_list.cpp:116 Failed to init info [2002]
2017-05-18T09:46:44-04:00 viking synousbmodemd: usbmodem_lib/usbmodem.cpp:709 USBModem [2002] is not inited
2017-05-18T09:46:53-04:00 viking synousbmodemd: usbmodem_lib/usbmodem_atif.cpp:114 Unknown vendor id 0658, assign default ATIF
2017-05-18T09:46:54-04:00 viking synousbmodemd: usbmodem_lib/usbmodem_devicenodehandler.cpp:278 No respond on modem cmd AT+CPIN?
2017-05-18T09:46:54-04:00 viking synousbmodemd: usbmodem_lib/usbmodem_simhandler.cpp:50 Warning: sim mute before handler init
2017-05-18T09:46:54-04:00 viking synousbmodemd: usbmodem_lib/usbmodem.cpp:481 failed on setup sim handler
2017-05-18T09:46:54-04:00 viking synousbmodemd: usbmodem_lib/usbmodem_list.cpp:116 Failed to init info [2002]
2017-05-18T09:46:54-04:00 viking synousbmodemd: usbmodem_lib/usbmodem.cpp:709 USBModem [2002] is not inited


Code: Select all

$ dmesg | grep tty
[   41.293712] cdc_acm 2-1:1.0: ttyACM0: USB ACM device


Code: Select all

$ dmesg | grep cdc_acm
[   41.282570] cdc_acm 2-1:1.0: This device cannot do calls on its own. It is not a modem.
[   41.293712] cdc_acm 2-1:1.0: ttyACM0: USB ACM device
[   41.301226] usbcore: registered new interface driver cdc_acm
[   41.306904] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters


Code: Select all

$ lsusb
Bus 002 Device 002: ID 0658:0200 Sigma Designs, Inc.
Bus 004 Device 002: ID 0480:a007 Toshiba America Info. Systems, Inc. External Disk USB 3.0


Hard to say if the right drivers are loading.
I will continue looking for a solution, but any help is appreciated.

Thanks,
- Serg
jadahl
Sharp
Sharp
Posts: 159
Joined: Tue Dec 16, 2014 6:55 pm

Re: USB Serial Drivers package

Postby jadahl » Fri May 19, 2017 2:25 pm

@hexigen
I have also this message (cdc_acm 2-1:1.0: This device cannot do calls on its own. It is not a modem.) you can ignore this message, it's only telling you that your z-stick is not an modem.

I don't know why you have the freeze problem, but I don't think this is a driver problem.
BTW the drivers in USBSerial package is the same drivers included in domoticz package!

You can test to disable synousbmodemd and see if that helps.
type: sudo killall synousbmodemd
domi1893
I'm New!
I'm New!
Posts: 3
Joined: Mon Oct 31, 2016 3:34 pm

Re: USB Serial Drivers package

Postby domi1893 » Fri Jun 02, 2017 4:33 pm

Hi Jadahl,

great idea to invent the usb drivers for synology.
i have tried to install the usb driver on my 916+ with Software 6.1.1 to use my ZWave USB stick. Don´t have a permission to the Port.

Can you help me please?

Thanks in advance

Domi
Cyberwizzard
I'm New!
I'm New!
Posts: 1
Joined: Sun Mar 05, 2017 2:48 pm

Re: USB Serial Drivers package

Postby Cyberwizzard » Sun Jun 04, 2017 9:05 pm

I have an DS415+ and an RFLink which uses the cdc-acm driver.

The Arduino board is found just fine using the DSM 6.0 and DSM 6.1 version of your driver package, but after a very short while, the serial port seems to lock up.

The DSM 6.0 version works for a few seconds (where I can see readings from my weather station or button presses on my NewKaku compatible switches) and then seems to stall: no new output is generated.
The DSM 6.1 version of the serial drivers works up to the point where I see the RFLink version string and perhaps one button press if I'm fast enough - but it stalls after a second or so.

Dmesg shows no errors or warnings, lsusb shows the device just fine. I tried all 3 USB ports on my Synology, all with the same result.

I also tested the RFLink using a normal computer - the serial port connection was working fine for hours until I unplugged it.

Am I the only one with this issue?
dh99999
I'm New!
I'm New!
Posts: 3
Joined: Mon Apr 04, 2016 2:01 am

Re: USB Serial Drivers package

Postby dh99999 » Sat Jun 10, 2017 3:36 pm

Hi Jadahl,

Thanks very much for putting together the usbserial packages for the synology...

I've been using them for a year or so without issue on my DS216Play, but made the error of upgrading to DSM 6.1.1-15101 Update 4 today.

I have 2 USB devices - a FTDI which is working fine, and a Prolific (detected previously as pl2303) which is no longer working.

The prolific is being detected via lsusb, but the /dev/ttyUSB01 device is no being created - do you happen to have any idea as to why this may be?

Code: Select all

|__usb1          1d6b:0002:0310 09  2.00  480MBit/s 0mA 1IF  (ehci_hcd ehci-platform.0) hub
|__usb2          1d6b:0001:0310 09  1.10   12MBit/s 0mA 1IF  (Linux 3.10.102 ohci_hcd Generic Platform OHCI Controller ohci-platform.0) hub
  |__2-1         067b:2303:0300 00  1.10   12MBit/s 100mA 1IF  (Prolific Technology Inc. USB-Serial Controller c6a3cfa3ccbecaa4cb88a8c4a5ccbedb)
|__usb3          1d6b:0002:0310 09  2.00  480MBit/s 0mA 1IF  (Linux 3.10.102 xhci-hcd xHCI Host Controller xhci-hcd.0.auto) hub
  |__3-1         0403:6001:0600 00  2.00   12MBit/s 90mA 1IF  (FTDI FT232R USB UART A60084Jw)
|__usb4          1d6b:0003:0310 09  3.00 5000MBit/s 0mA 1IF  (Linux 3.10.102 xhci-hcd xHCI Host Controller xhci-hcd.0.auto) hub


I have tried both the usbserial and domoticz packages (http://www.jadahl.com/synology6.1/ and http://www.jadahl.com/domoticz_beta_6.1/) without any luck.

I can see these warnings in dmesg, but the FTDI devices seems to cope ok with the warning:

Code: Select all

[   62.121994] usbserial: version magic '3.10.102 mod_unload ARMv7 p2v8 ' should be '3.10.102 SMP mod_unload ARMv7 p2v8 '
[   62.164486] ftdi_sio: version magic '3.10.102 mod_unload ARMv7 p2v8 ' should be '3.10.102 SMP mod_unload ARMv7 p2v8 '
[   62.317564] cp210x: version magic '3.10.102 mod_unload ARMv7 p2v8 ' should be '3.10.102 SMP mod_unload ARMv7 p2v8 '
[   62.386316] pl2303: version magic '3.10.102 mod_unload ARMv7 p2v8 ' should be '3.10.102 SMP mod_unload ARMv7 p2v8 '
[   62.548799] ch341: version magic '3.10.102 mod_unload ARMv7 p2v8 ' should be '3.10.102 SMP mod_unload ARMv7 p2v8 '
[   62.632095] ti_usb_3410_5052: version magic '3.10.102 mod_unload ARMv7 p2v8 ' should be '3.10.102 SMP mod_unload ARMv7 p2v8 '


Thanks again for any assistance!

Regards,
Dave.

Return to “Intel D510 Development Room”

Who is online

Users browsing this forum: No registered users and 1 guest