I am trying to get a USB Serial adapter working on my Asus Tinkerboard running Armbian.

 

if i lsusb i get:

root@tinkerboard:~# lsusb
Bus 001 Device 006: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
 

however no /dev/ttyUSB0 shows up.

 

 

Is there an armbian kernel for the asus tinkerboard with usb serial support? 

 

USB driver for your USB-UART device should be enabled by default in both kernelbranches we provide for the tinker.

 

https://github.com/armbian/build/blob/8fa1d6d98fcf07e41c65d7247a2fca6803c884a5/config/kernel/linux-rockchip-default.config#L3645

https://github.com/armbian/build/blob/8fa1d6d98fcf07e41c65d7247a2fca6803c884a5/config/kernel/linux-rockchip-next.config#L3763

 

Which image did you test? 

 

have you see this thread ? maybe it can help you.

 

On 26.4.2018 at 2:31 PM, recklessop said:

root@tinkerboard:~# lsusb
Bus 001 Device 006: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
however no /dev/ttyUSB0 shows up.

Is there an armbian kernel for the asus tinkerboard with usb serial support? 

if you insert the USB-serial-device after the boot is completed - what did tell you the last lines of

dmesg

about the device? Maybe ther is a hint for a devicename or a missing driver?
I dont know if the USB-serial-device drivers are in the kernel or could be loaded...

 

https://github.com/armbian/build/blob/development/config/kernel/linux-rockchip-default.config

 

It's enabled as a module in default.

Sorry for hijacking this thread, but I'm also having (two) issues with having USB Serial Support not working.

 

Background: I plan to migrate my setup off a Cubiertuck over to an Espressobin, and as both devices are "remote" in the basement I thought I could ease my life by cross-connecting their "uart/serial/usb/jtag" ports.

So a micro-usb cable is connected from the CT's USB to the EB's micro-USB port

Cubietruck with ARMBIAN 5.70 stable Debian GNU/Linux 9 (stretch) 4.19.13-sunxi
root@share:~# lsusb
Bus 003 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
root@share:~# dmesg | grep -i usb
 usb 3-1: new full-speed USB device number 2 using ohci-platform
 usb 3-1: New USB device found, idVendor=067b, idProduct=2303, bcdDevice= 4.00
 usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
 usb 3-1: Product: USB-Serial Controller D
 usb 3-1: Manufacturer: Prolific Technology Inc.
 usbcore: registered new interface driver usbserial_generic
 usbserial: USB Serial support registered for generic
 usbcore: registered new interface driver pl2303
 usbserial: USB Serial support registered for pl2303
 usb 3-1: pl2303 converter now attached to ttyUSB0

 

and an USB-TTL cable is connected from the EB's USB2.0 port to the CT's JTAG pins

Espressobin with ARMBIAN 5.70 stable Debian GNU/Linux 9 (stretch) 4.19.14-mvebu64
root@espressobin:~# lsusb
Bus 001 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
root@espressobin:~# dmesg | grep -i USB
 usb 1-1: new high-speed USB device number 2 using orion-ehci
 usb 1-1: config 1 interface 0 altsetting 0 bulk endpoint 0x2 has invalid maxpacket 64
 usb 1-1: config 1 interface 0 altsetting 0 bulk endpoint 0x83 has invalid maxpacket 64
 usb 1-1: New USB device found, idVendor=067b, idProduct=2303, bcdDevice= 3.00
 usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
 usb 1-1: Product: USB-Serial Controller
 usb 1-1: Manufacturer: Prolific Technology Inc.
 usbcore: registered new interface driver uas

 

Issue #1: On the CT I can connect to the EB via root@share:~# minicom -b 115200 --device /dev/ttyUSB0, but though I e.g. see the message on "the console" while rebooting the EB I can't interact with it, e.g. hitting "CR" during uboot does not work, nor can I logon via the console as it seems that no keystroke gets there.

 

Issue #2: is even worse, as I don't have a ttyUSB0 port on the EB for CB's JTAG port at all. What's going wrong here? Why is it registered as an UAS? Using the same connection with puTTY on Windows I have noch issue to get to the CB's serial port. (Only issue is that the USB-TTL cable which I brought seems to be Prolific fake, which is disabled by recent Prolific's device drivers. Is that the same with Debian?)

 

32 minutes ago, odoll said:

Issue #2: is even worse, as I don't have a ttyUSB0 port on the EB

Did you check if PL2303 is part of your EB kernel using "grep PL23 /boot/config-*" ?

 

no, but now:

CT y

EB n

24 minutes ago, odoll said:

no, but now:

CT y

EB n

So, you got the answer ... Maybe you can build your own EB image and enabling this driver ...

thx! - but don't think so (using armbian as didn't want to bother with those details myself ;-)

I can confirm that latest armbian with next kernel (4.19) on rk3288 works flawlessy with prolific USB-to-serial adapters:

15567.072909] usb 2-1: new full-speed USB device number 2 using dwc2
[15567.281604] usb 2-1: New USB device found, idVendor=067b, idProduct=2303, bcdDevice= 3.00
[15567.281616] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[15567.281623] usb 2-1: Product: USB-Serial Controller
[15567.281630] usb 2-1: Manufacturer: Prolific Technology Inc.
[15567.318362] usbcore: registered new interface driver pl2303
[15567.323408] usbserial: USB Serial support registered for pl2303
[15567.323550] pl2303 2-1:1.0: pl2303 converter detected
[15567.327312] usb 2-1: pl2303 converter now attached to ttyUSB0

I use it daily with Arduino IDE to develop and push things to ESP8266 and works without issues.

Thx for the reply. That's odd, so the issue might be caused by the fact, that I'm not using an original Prolific, but cheap "China" clone cable!?

I though this wouldn't cause an issue with Linux, as it does with Windows (with the latter I had to downgrade to a former Prolific driver to get it working, as the actual would detect the "fake".)