This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 1 Vote(s) - 3 Average
  • 1
  • 2
  • 3
  • 4
  • 5
no ttyUSB with arduino nano clone ch340
#1
Hey!
hope this one is easy ...

i am trying to connect to the arduino and it shows as an usb device but does not attach to a /ttyUSB.

The Arduino IDE shows only ttyS as well.
If I connect to my Pi it just attaches the arduino and serial communication is possible.

this is what dmesg | grep USB says ->


[ 2534.175393] usb 1-1.4.1: new full-speed USB device number 10 using dwc2
[ 2534.348103] usb 1-1.4.1: New USB device found, idVendor=1a86, idProduct=7523
[ 2534.348158] usb 1-1.4.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 2534.348194] usb 1-1.4.1: Product: USB2.0-Serial

lsusb says ->

Bus 001 Device 010: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter

I have already tried several tinker os versions and I feel stuck right now.

As I am new to this board I would really appreciate your support !
Reply
#2
Dear vladt,

If you can't find ttyUSB*, could you try to find ttyACM*?
Maybe that device initialized as ttyACM not ttyUSB...

Best Regards,
ASUS Tinker Board Team
Reply
#3
There are no additional ttys.
I just see S0 to 3.
Reply
#4
Dear vladt,

The ttyS* are for GPIO/UART.
You can use "ls /dev/tty*" to check as below:
[Image: mDZ1Bk9.png]

Best Regards,
ASUS Tinker Board Team
Reply
#5
I know, the problem is that the Arduino does not attach.
So no ttyUSB or ttyACM are present in the dev/ folder
Reply
#6
Do I have to activate the serial communication via USB somewhere ? Is this a "driver problem" with the ch340 chip or is serial communication via usb per default not available in tinker os?
Reply
#7
Have you tried to enable this kernel config ? CONFIG_USB_SERIAL_CH341
This config is not enabled by the official Tinker Board kernel image.
Reply
#8
I would try, but i dont know how exactly  Big Grin ...
This would need a rebuild, right? Or could it be done on an operating system?

Thx for the answer anyway!
 I hoped it wont be a problem with the Kernel because I have no expertise what so ever on this stuff...
Reply
#9
(08-31-2017, 05:25 PM)mojojojojojo Wrote: I would try, but i dont know how exactly  Big Grin ...
This would need a rebuild, right? Or could it be done on an operating system?

Thx for the answer anyway!
 I hoped it wont be a problem with the Kernel because I have no expertise what so ever on this stuff...

Yes, you need rebuild the kernel.

step 1. download kernel 
git clone https://github.com/TinkerBoard/debian_kernel.git

step 2. add the following line to arch/arm/configs/miniarm-rk3288_defconfig
CONFIG_USB_SERIAL_CH341=y

step 3. rebuild the kernel
make ARCH=arm miniarm-rk3288_defconfig
make zImage ARCH=arm CROSS_COMPILE=arm-linux-gnueabi-

then you will get a new zImage file under arch/arm/boot

step 4. replace the zImage file which is in your boot sdcard
Reply
#10
(09-01-2017, 10:05 AM)Vinci Wrote:
(08-31-2017, 05:25 PM)mojojojojojo Wrote: I would try, but i dont know how exactly  Big Grin ...
This would need a rebuild, right? Or could it be done on an operating system?

Thx for the answer anyway!
 I hoped it wont be a problem with the Kernel because I have no expertise what so ever on this stuff...

Yes, you need rebuild the kernel.

step 1. download kernel 
git clone https://github.com/TinkerBoard/debian_kernel.git

step 2. add the following line to arch/arm/configs/miniarm-rk3288_defconfig
CONFIG_USB_SERIAL_CH341=y

step 3. rebuild the kernel
make ARCH=arm miniarm-rk3288_defconfig
make zImage ARCH=arm CROSS_COMPILE=arm-linux-gnueabi-

then you will get a new zImage file under arch/arm/boot

step 4. replace the zImage file which is in your boot sdcard
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)