-
-
Notifications
You must be signed in to change notification settings - Fork 398
Allow specifying FQBN *and* port in board attach
#1073
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
A slightly related issue is that when specifying a port and doing autodetection, the "name" is set in arduino-cli/commands/board/attach.go Lines 56 to 59 in 1855b53
and arduino-cli/commands/board/attach.go Lines 95 to 99 in 1855b53
|
@matthijskooijman I have started reviewing this kind of workflows because in my opinion every time you need to pass a board model you should prefix it with the |
@matthijskooijman |
This problem has been resolved by the complete reworking of the board attach command in #1930. The user preferences are now saved in the |
Bug Report
Current behavior
The
board attach
command allows specifying a port or FQBN. If you specify a port, the FQBN is autodetected from the board (if possible) and the resulting sketch.json has both the port and fqbn set. If you specify just the FQBN, only that is set in sketch.json.For boards that can be autodetected, it is sufficient to specify the port. But for boards that cannot be autodetected (i.e. that use a common USB-to-serial chip without their own VIDPID), specifying the serial port is now not possible (since that triggers autodetection, which fails).
As a workaround, you can just edit
sketch.json
manually, of course.Maybe it would be useful to add a
--fqbn
option toboard attach
, to allow specifying the FQBN in addition to the serial port and override autodetection? The interface might get a little messy, though. Maybe it would be better to then also add--port
and stop support the<port>|<FQBN>
non-option argument? i.e. change:to:
This would break compatibility, though...
arduino-cli version
): Current git master 1855b53The text was updated successfully, but these errors were encountered: