Hello,

 

i will move my project from RPI2 to tinkerboard. I have 2 Serial Converter, USB to RS422 and USB to RS485, both working on the PI.

On the Tinkerboard with "ARMBIAN 5.33 stable Ubuntu 16.04.3 LTS 4.13.3-rockchip" runs only the RS422,

the RS485 (Vendor 1a86) is not available as /dev/ttyUSB.

 

What can i do?

 

Regards

Marco

 

Tinkerboard Log:

Spoiler

Oct 14 17:52:45 localhost kernel: [    1.942542] usb 1-1.1: new full-speed USB device number 3 using dwc2
Oct 14 17:52:45 localhost kernel: [    2.020053] usb 1-1.1: New USB device found, idVendor=1a86, idProduct=7523
Oct 14 17:52:45 localhost kernel: [    2.020066] usb 1-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
Oct 14 17:52:45 localhost kernel: [    2.020076] usb 1-1.1: Product: USB2.0-Serial
Oct 14 17:52:45 localhost kernel: [    2.175542] usb 1-1.2: new full-speed USB device number 4 using dwc2
Oct 14 17:52:45 localhost kernel: [    2.258393] usb 1-1.2: New USB device found, idVendor=0403, idProduct=6001
Oct 14 17:52:45 localhost kernel: [    2.258407] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 14 17:52:45 localhost kernel: [    2.258416] usb 1-1.2: Product: FT232R USB UART
Oct 14 17:52:45 localhost kernel: [    2.258425] usb 1-1.2: Manufacturer: FTDI
Oct 14 17:52:45 localhost kernel: [    2.258433] usb 1-1.2: SerialNumber: 00000000
Oct 14 17:52:45 localhost kernel: [    2.261754] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
Oct 14 17:52:45 localhost kernel: [    2.261918] usb 1-1.2: Detected FT232RL
Oct 14 17:52:45 localhost kernel: [    2.262583] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0

 

Raspberry Log:

Spoiler

 

Oct  8 18:40:45 raspberrypi2 kernel: [    2.180505] usb 1-1.2: new full-speed USB device number 4 using dwc_otg
Oct  8 18:40:45 raspberrypi2 kernel: [    2.338225] usb 1-1.2: New USB device found, idVendor=0403, idProduct=6001
Oct  8 18:40:45 raspberrypi2 kernel: [    2.342105] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct  8 18:40:45 raspberrypi2 kernel: [    2.346076] usb 1-1.2: Product: FT232R USB UART
Oct  8 18:40:45 raspberrypi2 kernel: [    2.348063] usb 1-1.2: Manufacturer: FTDI
Oct  8 18:40:45 raspberrypi2 kernel: [    2.349980] usb 1-1.2: SerialNumber: 00000000
Oct  8 18:40:45 raspberrypi2 kernel: [    2.460527] usb 1-1.3: new full-speed USB device number 5 using dwc_otg
Oct  8 18:40:45 raspberrypi2 kernel: [    2.594261] usb 1-1.3: New USB device found, idVendor=1a86, idProduct=7523
Oct  8 18:40:45 raspberrypi2 kernel: [    2.597560] usb 1-1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0
Oct  8 18:40:45 raspberrypi2 kernel: [    2.601164] usb 1-1.3: Product: USB2.0-Serial
Oct  8 18:40:45 raspberrypi2 kernel: [    3.444436] usbcore: registered new interface driver usbserial
Oct  8 18:40:45 raspberrypi2 kernel: [    3.444562] usbcore: registered new interface driver usbserial_generic
Oct  8 18:40:45 raspberrypi2 kernel: [    3.444690] usbserial: USB Serial support registered for generic
Oct  8 18:40:45 raspberrypi2 kernel: [    3.462009] usbcore: registered new interface driver ch341
Oct  8 18:40:45 raspberrypi2 kernel: [    3.462155] usbserial: USB Serial support registered for ch341-uart
Oct  8 18:40:45 raspberrypi2 kernel: [    3.462280] ch341 1-1.3:1.0: ch341-uart converter detected
Oct  8 18:40:45 raspberrypi2 kernel: [    3.467197] usb 1-1.3: ch341-uart converter now attached to ttyUSB0
Oct  8 18:40:45 raspberrypi2 kernel: [    3.566268] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
Oct  8 18:40:45 raspberrypi2 kernel: [    3.710760] usbcore: registered new interface driver ftdi_sio
Oct  8 18:40:45 raspberrypi2 kernel: [    3.710934] usbserial: USB Serial support registered for FTDI USB Serial Device
Oct  8 18:40:45 raspberrypi2 kernel: [    3.711359] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
Oct  8 18:40:45 raspberrypi2 kernel: [    3.711676] usb 1-1.2: Detected FT232RL
Oct  8 18:40:45 raspberrypi2 kernel: [    3.732489] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB1

 

1 hour ago, MB2 said:

What can i do?

 

https://docs.armbian.com/Developer-Guide_Build-Preparation/
Enable, build (with parameter KERNEL_CONFIGURE="yes") and(or) send a patch upstream or wait few days that its added ... under the condition that only enabling is needed. We rebuild all kernels daily and you can find them in beta.armbian.com repository.

Hi Igor,

 

thanks for the reply, but I do not quite understand. 

I am not a specialist in the ux world, but only compile the kernel is not enough?
As I see it is missing the driver for the CH340 / CH341 or even only the assignment of the Vendor / Device ID to this driver.
I do not know how I can check whether the driver is available or how I can include.

There is a driver for the converter, but only for kernels 2.x and 3.x

http://www.wch.cn/download/CH341SER_LINUX_ZIP.html

 

regards

Marco

This is a bit strange that CH34x driver is missing, it has been added months, maybe year ago.

Here is the results of "grep CH34" in Armbian defconfig :

config/kernel/linux-sun4i-default.config:CONFIG_USB_SERIAL_CH341=m
config/kernel/linux-sun7i-default.config:CONFIG_USB_SERIAL_CH341=m
config/kernel/linux-sun8i-default.config:CONFIG_USB_SERIAL_CH341=m
config/kernel/linux-sun8i-dev.config:CONFIG_USB_SERIAL_CH341=m
config/kernel/linux-sunxi64-dev.config:CONFIG_USB_SERIAL_CH341=m
config/kernel/linux-sunxi64-next.config:CONFIG_USB_SERIAL_CH341=m
config/kernel/linux-sunxi-dev.config:CONFIG_USB_SERIAL_CH341=m
config/kernel/linux-sunxi-next.config:CONFIG_USB_SERIAL_CH341=m

Verify that is really missing by doing : find /lib/modules/ -name "ch34*ko"

Check also "dmesg" while plugging the USB-RS485 device, you should see something like :

[2830916.592706] usb 1-1: new full-speed USB device number 3 using dwc2
[2830916.776738] usb 1-1: New USB device found, idVendor=1a86, idProduct=7523
[2830916.776768] usb 1-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[2830916.776788] usb 1-1: Product: USB2.0-Serial
[2830918.390022] usbcore: registered new interface driver usbserial
[2830918.390154] usbcore: registered new interface driver usbserial_generic
[2830918.390266] usbserial: USB Serial support registered for generic
[2830918.393881] usbcore: registered new interface driver ch341
[2830918.394055] usbserial: USB Serial support registered for ch341-uart
[2830918.394199] ch341 1-1:1.0: ch341-uart converter detected
[2830918.397152] usb 1-1: ch341-uart converter now attached to ttyUSB0

 

22 minutes ago, martinayotte said:

it has been added months, maybe year ago

but not to Rockchip configs, so somebody has to add it and push the changes to our repository.

1 hour ago, zador.blood.stained said:

but not to Rockchip configs

I'm still thinking AllWinner all the time ...

 

EDIT : Another reason for by "bad", I'm still using Ayufan build ... So, it is a good oppotunity to add those drivers and test new Armbian ... I will probably commit that this afternoon.

no ch3xx.ko with

"find /lib/modules/ -name "ch34*ko""

In the mean time that I'm doing the required commit, you can use temporarily an Ayufan image, it has this driver.

 

@martinayotte

Tinkerboard images are not compatible with Rock64 ones, so there are no Ayufan's images for it 

... But, I will do the task for Rock64 ...

 

Thanks @martinayotte, I'm operating from cell phone right now, a storm took out my power...

 

I'll check these when it comes back if it hasn't been done, it will need added to the Meson64 as well, I would expect.

Oh, to my surprise since I was still using Ayufan image on my Rock64, it seems that current Dev build, although building properly, isn't booting and get stuck at "starting kernel" ...

Anyone got the Dev working ? Then, I've built Default version, and this one is working ... It is maybe question of DT itself or U-Boot, I will need to investigate more.

 

 

any news from the driver?

So my project ist migrated to the tinkerboard with an ttl to rs485 adapter, 

but I would be happy if the usb adapter would work

 

The commit has been done 4 days ago : https://github.com/armbian/build/commit/d70ce66742a55579c49e712ce6a867c7ac68df83

So, if you build your own image, you will getting those USB-TTL dongles working.

oh, I did not see that.

I will try that, thanks