mpremote should not limit name shortcuts to 1st 4 devices
The mpremote help says you can use the following shortcuts:
a0 connect to serial port "/dev/ttyACM0"
a1 connect to serial port "/dev/ttyACM1"
a2 connect to serial port "/dev/ttyACM2"
a3 connect to serial port "/dev/ttyACM3"
c0 connect to serial port "COM0"
c1 connect to serial port "COM1"
c2 connect to serial port "COM2"
c3 connect to serial port "COM3"
u0 connect to serial port "/dev/ttyUSB0"
u1 connect to serial port "/dev/ttyUSB1"
u2 connect to serial port "/dev/ttyUSB2"
u3 connect to serial port "/dev/ttyUSB3"
That's good, but why limit them to 4? I had 5 devices connected so for the first 4 I could address easily, e.g. mpremote u3 but the 5th device I had to specify the full device path (because mpremote u4 is not accepted), i.e. I had to type mpremote connect /dev/ttyUSB4. Just seems like an unnecessary constraint and surely would be easy to fix.
This is using mpremote from master branch as of today (v1.20.0-50-g786013d46) .
mpremote on Mac OS X: allow env var or option in config file to select default serial port to use
I'm using Mac OS X, and I'm struggling to get mpremote to do anything more than giving me a REPL.
This is the list of devices I get when trying to connect to an ESP32 DevKitC1 board:
mpremote connect list
/dev/cu.BLTH None 0000:0000 None None
/dev/cu.Bluetooth-Incoming-Port None 0000:0000 None None
/dev/cu.usbserial-0001 0001 10c4:ea60 Silicon Labs CP2102 USB to UART Bridge Controller
Issuing mpremote connect /dev/cu.usbserial-0001 connects to the board and gives me a REPL back. But any other command (fs, run, exec...) won't work as mpremote always assume that the device is has to connect to is the first in the previous list (/dev/cu.BLTH in my case).
As mpremote CLI syntax does not seem to allow specifying both the serial port to use and the action to perform (imagine something like mpremote -D /dev/cu.usbserial-001 fs ls), would it be possible to consider a shell env var à la ampy (or minicom) to tell it what serial port to use?