You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My basic wish is to have second USB-SERIAL device in
ESP32-S2 which will lead to hardware TX/RX lines.
I was thinking - if descriptor must be static, and list all supported
device for which same endpoints have to be shared, then
perhaps on the OS (at least linux) is possible to blacklist unneeded
drivers, so that actually endpoints will be used only by not blacklisted
drivers, and things may work. (at least in heory)
The text was updated successfully, but these errors were encountered:
I'm not quite sure what you're looking for. We have been thinking about a secondary CDC serial connection over USB. So for instance on Linux, you'd have /dev/tty/ACM0 for the REPL connection, and then also a /dev/ttyACM1 on the host side, which was a read/write stream on the Python side. But if you want hardware UART, then you want to use busio.UART.
Yes I'd like to have this secondary CDC /dev/ttyACM1
and a possibility to bridge its traffic to external pins TX/RX
it would be practical to run usb-serial bridge in
"background" of esp32 so that more user code
can work too if technologically possible.
On 12/19/20, Dan Halbert ***@***.***> wrote:
I'm not quite sure what you're looking for. We have been thinking about a
secondary CDC serial connection over USB (e.g. you'd have `/dev/tty/ACM0`
for the REPL connection, and then also a `/dev/ttyACM1`. But if you want
hardware UART, then you want to use `busio.UART`.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#3849 (comment)
My basic wish is to have second USB-SERIAL device in
ESP32-S2 which will lead to hardware TX/RX lines.
I was thinking - if descriptor must be static, and list all supported
device for which same endpoints have to be shared, then
perhaps on the OS (at least linux) is possible to blacklist unneeded
drivers, so that actually endpoints will be used only by not blacklisted
drivers, and things may work. (at least in heory)
The text was updated successfully, but these errors were encountered: