![]() > I have tried this on a few different machines/kernels. > work fine in Windows but one has problems transmitting in Linux. > reports a different iProduct and bcdDevice from the others. > and use the ch341 driver with ID 1a86:7523 but I've found one that > I have a few CH340/341 USB RS485 adapters - they all look identical On Sun, at 05:40:36PM -0800, John Paul Morrison wrote: 1:40 problems with ch341 driver USB RS485 in Linux but not Windows John Paul 9:32 ` Johan HovoldĠ siblings, 1 reply 3+ messages in thread * Re: problems with ch341 driver USB RS485 in Linux but not Windows IdProduct 0x7523 HL-340 USB-Serial adapter The only difference is in bcdDevice, iProduct and MaxPower usb 1-1.4: ch341-uart converter now attached to ttyUSB0īus 001 Device 007: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapterīus 003 Device 002: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter ch341-uart ttyUSB0: break control not supported, using usb 1-1.4: New USB device strings: Mfr=0, Product=2, usb 1-1.4: New USB device found, idVendor=1a86, usb 1-1.4: new full-speed USB device number 7 using ehci-pci CTS: active DSR: active RI: active CD: active usb 3-4: ch341-uart converter now attached to ttyUSB1 usb 3-4: New USB device strings: Mfr=0, Product=2, usb 3-4: New USB device found, idVendor=1a86, usb 3-4: new full-speed USB device number 2 using xhci_hcd Using a pty the Linux serial application works perfectly but fails If I run socat in Windows sharing the serial port, and socat Linux In Windows the Termite com program shows CTS/DSR/RI/CD active CTS: inactive DSR: inactive RI: inactive CD: inactive RTS: active DTR: active BREAK: inactive I have not been able to work around this with stty or in miniterm Miniterm and dmesg offer some clues - the problem device shows Work fine in Windows but one has problems transmitting in Linux. Reports a different iProduct and bcdDevice from the others. I have a few CH340/341 USB RS485 adapters - they all look identicalĪnd use the ch341 driver with ID 1a86:7523 but I've found one that ![]() 9:32 ` Johan Hovold 0 siblings, 1 reply 3+ messages in threadįrom: John Paul Morrison 1:40 UTC ( / raw) I would like to know how to recompile the kernel to use the USB serial adapter with Ubuntu Touch on Pixel 3a.Problems with ch341 driver USB RS485 in Linux but not Windows All of help / color / mirror / Atom feed * problems with ch341 driver USB RS485 in Linux but not Windows 1:40 John Paul Morrison I have tried using the following two OS versions with the same results.Īccording to information at the following webpage, the kernel in ubuntu touch does not support the use USB serial adapters and the kernel must be recompiled to use it. Ls: cannot access '/dev/ttyUSB*': No such file or directory Ls: cannot access '/dev/serial*': No such file or directory However, /dev/serial* and /dev/ttyUSB* do not appear. ![]() $ susbīus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 001 Device 002: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapterīus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I tried to connect the USB serial adapter to the Pixel3A via a OTG adapter and executed the lsusb command, and it is recognized as follows. The USB serial adapter used is the following CH340. ![]() I would like to use a USB serial adapter with Ubuntu Touch installed on a Pixel3A. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |