-
-
Notifications
You must be signed in to change notification settings - Fork 398
Custom board is detected as "Unknown" #456
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
It may be that the vid/pid pairs start with the progressive number
May you try to change the above lines with:
and see if this fixes the problem? |
cmaglie
added a commit
that referenced
this issue
Oct 30, 2019
Even if vid.0/pid.0 is missing. Fix #456
cmaglie
added a commit
that referenced
this issue
Oct 30, 2019
Even if vid.0/pid.0 is missing. Fix #456
intrigus
added a commit
to intrigus/ftduino
that referenced
this issue
Oct 31, 2019
cmaglie
added a commit
that referenced
this issue
Nov 4, 2019
Even if vid.0/pid.0 is missing. Fix #456
cmaglie
added a commit
that referenced
this issue
Nov 4, 2019
* Board identification: always check vid.1/pid.1 Even if vid.0/pid.0 is missing. Fix #456 * Renamed 'again'->'present' and 'found'->'matched' for clarity
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Current behavior
The connected board is not recognized.
Expected behavior
I'd expect the device to get recognized.
The arduino IDE correctly recognizes it.
The pid and vid are defined in the extension here:
https://github.com/harbaum/ftduino/blob/master/ftduino/boards.txt#L3-L7
Is there something else that needs to be done to recognize a custom board?
Environment
arduino-cli version
): arduino-cli Version: 0.6.0 Commit: 3a08b07Additional context
The text was updated successfully, but these errors were encountered: