Okay, I concur that the CH341 are crappy.
I connected an
USB2DB9 cable to
a DB9-to-TTL and got garbage, too. Then I reconnected the
CH340 module which now registered at ttyUSB1, because ttyUSB0 was still used by the cable and voilą: I got a login prompt.
Really crappy way to get it working. And probably not terribly reproducable. Earlier the connection kept sending Carriage returns or line feeds, effectively drowning the login in garbage info.
Still this does allow me to change the system to enable dropbear and such to work over USBnet. So now I have a board that has WiFi and an microUSB and a microSD card.
What could I build with?
@very_rude_Turnip Could you give me a link to a _good_ pl2303 or FTDI?
NEXT: Getting a connection to my cracked Kobo Aura: see whether the PCB was undamaged and the system is still working.
EDIT: No discernable life in the Kobo Aura PCB. The light stays on for a few seconds after pulling the power switch, but there is no reaction to the reset button nor any joy from the serial headers:
Code:
# sudo picocom -b 115200 /dev/ttyUSB0
picocom v2.2
port is : /dev/ttyUSB0
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
stopbits are : 1
escape is : C-a
local echo is : no
noinit is : no
noreset is : no
nolock is : no
send_cmd is : sz -vv
receive_cmd is : rz -vv -E
imap is :
omap is :
emap is : crcrlf,delbs,
Type [C-a] [C-h] to see available commands
Terminal ready
?��������a?�������)�Ϳr��w��}ǭY��b�ZM� d���kR
�i�e�D6�9a�_
E���Ŝl8���T�{m��H X��^��|d (H
��� ]P"(u�"D`
H H@d�F�$��H@@!��� @������~�������k�����۟������m�߾���q�����������į
+���������]��J"����q!r�f�@�
&!0t����(D�� �� �IH���_���L�XT4
Thanks for using picocom