Closed umbynos closed 1 year ago
The deficiency of being unable to specify both port and FQBN via the command is tracked at https://github.com/arduino/arduino-cli/issues/1073
@per1234
this issue was only tracked internally.
Yesterday, during grooming/planning, we made it public in order to add it to the 1.0
milestone.
This is why this one popped up seemingly out of the blue.
Your mention of #1073 publicly links the two 🙏🏼
Am doing this.
:metal:
The
board attach
command has a broken implementation:Inconsistent port argument format
Currently, the command will only accept a port when passed in as a full path (e.g.:
serial:///dev/cu.usbmodem14301
). This is inconsistent with all the other commands that accept a port argument, which allow the more user friendly address (e.g.:/dev/cu.usbmodem14301
) to be used.The command must accept the same address format as the other commands.
In order to allow a protocol of the port to be specified in addition to the address in cases where this is necessary, the command should also support a
--protocol
flag just as in the other commands that accept a port argument. This information will be stored in thecpu.protocol
field ofsketch.json
.Support for the previous port format should be retained.
Outdated board identification feature
Currently, when a port is passed to the command, it attempts to automatically identify the board on that port and save its FQBN and name in the
cpu.fqbn
andcpu.name
fields ofsketch.json
.This feature uses the obsolete
github.com/arduino/board-discovery
module.Although the feature could be modernized, its value is questionable. The available resources would be better allocated to more important work than to updating and maintaining the feature. For this reason, the auto-detection of board data from port feature should simply be removed.