something wrong with my UART on ttyUSB0

[  105.283554] usb 1-2: ch341-uart converter now attached to ttyUSB0
[  106.112156] ch341-uart ttyUSB0: usb_serial_generic_write_bulk_callback - nonzero urb status: -71
[  106.134141] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
[  106.559701] usb 1-2: ch341-uart converter now attached to ttyUSB0
[  106.637436] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0

https://devtalk.nvidia.com/default/topic/1032862/jetson-tx2/a-guide-to-solve-usb-serial-driver-problems-on-tx2/

I followed the method above to install the ch341 drive and then connected my device(a robot base with an arduino in it) and dmesg | grep tty gave the err info. Sometimes I successfully communicate with my device and it disconnected soon and some times it reconnected to ttyUSB1. However it seems that my PC doesn’t have this kind of problem while communicating with it.

Besides, I searched “usb_serial_generic_write_bulk_callback - nonzero urb status: -71” on Google and some results aboout Ubuntu told me to update my kernel.

And the kernel version of my TX2 is 4.4.15-jetsonbot-v0.1, using Ubuntu 16.04LTS

What’s the problem? Should I update my kernel?

Which kernel version are you using? See “uname -r”. Which L4T release is this? See “head -n 1 /etc/nv_tegra_release” (technically knowing L4T implies knowing kernel, but only if nothing was modified).

This is what I’ve got

nvidia@tegra-ubuntu:~$ head -n 1 /etc/nv_tegra_release
# R27 (release), REVISION: 1.0, GCID: 8566447, BOARD: t186ref, EABI: aarch64, DATE: Thu Mar  2 05:14:54 UTC 2017
nvidia@tegra-ubuntu:~$ uname -r
4.4.15-jetsonbot-v0.1

This is the original version, and much has been updated. Would it be possible for you to flash R28.2.1? This is the most recent L4T version for a TX2. I suspect there are several fixes or changes to USB. You would still have to add a driver module for the ch341, but you shouldn’t change the whole kernel…you only need to add a module. When “uname -r” changes it implies you changed the whole kernel (which in turn means you need to fully reinstall all modules and not simply add one driver).

Okay, I think I’m going to try that. Thanks a lot!