Future models will have an onboard TTL to USB convertor, just like the OpenWrt One.
1 Like
Hopefully that will b a ftdi converter.
Connecting the usb side of ch340 or alike to another BPI board (R64 in my case) it is prone to giving errors. In my experience, only the ftdi (232RL) converter is really stable when connecting the usb side to a development board or using it with some (probably cheaper) usb hub.
When the is no options to choose which converter to use, I hope the built-in converter will be a very stable one.
The only issue I have with CP2104 is when I’m connecting in the same USB 3.0 HUB CP2104 and a USB3.1 SD card Reader.
Because I have also my mouse connected in the same Hub, some times there is a high current demand for SD Card reader and the CP2104 is starting to give errors.
When I reduced the number of devices in hub, this issue disappeared.
So is not CP2104 related issue, but more about USB Hub issue.
In rest I’m using on BPi-R4 without any issues.
I’m using my BPI-R64 to connect to the debugging console of my other development boards. These are the R3, R4, M7 and an AM3359-board.
So through ssh I can connect to the serial debugging console of any board. This is very usefull for testing (hardware) offloading network.
I’ve tried all sorts of different converters, but, when using (multiple) converters connected to the R64’s usb port, there is only one 1 stable, which is the FTDI 232 (RL)
Did you try CP2102N should work better than CP2104 …
we use HT42B534-2 (CDC-ACM, no driver required)
I would suggest testing (multiple) with the usb side connected to another mediatek devboard.
Some converters (like ch340) are not stable under this condition.
I’m using a FT232 USB To UART (TTL) Communication Module, USB-C Connector | FT232 USB UART Board (Type C), which is nice because it’s very easy to mount.
This one is even smaller: