8/30/2023 0 Comments Ch340 driver serialUsbcore: registered new interface driver ch341 Usbserial: USB Serial support registered for generic Usbcore: registered new interface driver usbserial_generic Usbcore: registered new interface driver usbserial Usb 1-1.2.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0 Usb 1-1.2.4: New USB device found, idVendor=1a86, idProduct=7523 HW is good - windows applications work properly.Īfter connecting converter syslog look like this: If I have free time I try to test this on Debian. Communication over this type converter is not possible even though kernel detects HW and everything looks like on other type of chipsets. But I tested 3 or 4 devices with CH340 or CH341 and result is the same - driver in raspbian is wrong. Your HW is probably other so you get success resuts. This eliminated my application (minicom) and I am sure now, that driver for CH340 is realy wrong. And if I send chars less than 20 I get other chars. I press ''a'' and I get ''a'' but if I press ''f" I get "F". I connect raspberry with converter with minicom application with windows PC. But your idea - to check it with minicom - was very good for me. I use serial port from C language and settings for communication are the same for each type of converter - pl2302, FT232RL and of course CH340. I tried to test your advices - stty command was new for me.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |