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?
mpremote: Fix listing when VID/PID are none, and add "devs" shortcut
Fixes #7636 , and implements "devs" as per discussion in #7480.