Skip to content

Feature request: Can board list report the vid/pid found in the json output? #1069

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

Closed
obra opened this issue Nov 12, 2020 · 0 comments · Fixed by #1076
Closed

Feature request: Can board list report the vid/pid found in the json output? #1069

obra opened this issue Nov 12, 2020 · 0 comments · Fixed by #1076
Labels
type: enhancement Proposed improvement

Comments

@obra
Copy link
Contributor

obra commented Nov 12, 2020

Related to #1068 : Like the Leonardo, my Arduino-powered keyboards use a separate USB PID when they're in bootloader mode vs when they're in device mode.

Because we want to avoid the possibility of unintentional or malicious flashing, our bootloader checks to see if a safety-interlock key is held down before accepting a sketch upload. Otherwise, it boots into the user's sketch.

We have tooling that uses the device pid to determine whether a keyboard is in bootloader mode. Otherwise, it prompts the user to hold down the safety interlock key before doing the standard serial port tickle.

In the bad old days (with arduino-builder), we built our own logic to probe for serial ports by vid/pid pair. With arduino-cli, we no longer need to do that. Almost.

Right now, the json output from arduino-cli board listdoesn't include the USB vendor-id and USB product-id reported back by serial-discovery.

If you folks would be willing to include the vid and pid in the json output from board list, I'd really appreciate it.

(It might be useful to also include the board serial number, too, but I myself don't have an immediate need for it.)

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement Proposed improvement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants