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
$ espflash -V
espflash 1.5.1
$ uname -a
Linux ada-DT0 5.13.0-41-generic #46~20.04.1-Ubuntu SMP Wed Apr 20 13:16:21 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
In modern versions of Linux, the devfs system includes symlinks that allow you to unambiguously reference items by ID -- this includes serial devices.
e.g.
$ ls /dev/serial/by-id/ -lah
total 0
drwxr-xr-x 2 root root 80 May 16 19:55 .
drwxr-xr-x 4 root root 80 May 16 16:58 ..
lrwxrwxrwx 1 root root 13 May 16 19:19 usb-Raspberry_Pi_Picoprobe_[REDACTED]_if00 -> ../../ttyACM0
lrwxrwxrwx 1 root root 13 May 16 19:55 usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0 -> ../../ttyUSB0
Instead of following symlinks passed for serial device file paths, it returns an error, like so:
$ espflash /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0 target/xtensa-esp32-espidf/debug/rust-esp32-std-demo
Error: espflash::serial_not_found
× The serial port '/dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0' could not be found
help: Make sure the correct device is connected to the host system
This leads me to use workarounds with basename and readlink, which definitely seems subpar and unnecessary. :P
The text was updated successfully, but these errors were encountered:
In modern versions of Linux, the devfs system includes symlinks that allow you to unambiguously reference items by ID -- this includes serial devices.
e.g.
Instead of following symlinks passed for serial device file paths, it returns an error, like so:
This leads me to use workarounds with
basename
andreadlink
, which definitely seems subpar and unnecessary. :PThe text was updated successfully, but these errors were encountered: