-
-
Notifications
You must be signed in to change notification settings - Fork 444
Compilation error: Error: 2 UNKNOWN: no FQBN provided while board is in and plugged #421
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
Hi @jerabaul29. Do you see the boards listed under the Arduino IDE's Tools > Board > Sparkfun Apollo3 Boards menu? |
Please post the output you get in the Linux terminal after starting the Arduino IDE. |
Here it is :)
|
(just launching as |
I updated from beta.5 to beta.8 today and I am now experiencing the same problem (on Windows). The Generic ESP boards are now grayed out and the same message occurs UPDATE: It seems to be an problem with updating the Arduino IDE, onces the Arduino IDE is updated just uninstall and re-install the ESP boards library in the Boards Manager. |
I was not able to reproduce this issue of the SparkFun Apollo3 Boards platform not appearing under the IDE's board menus until I finally spotted the essential clue:
Notice that version 1.2.2 was installed, but the latest version offered by the package index at that time was 2.1.0 There was a bug where the IDE did not recognize outdated boards platforms. This was actually a bug in the Arduino CLI tool the Arduino IDE uses to handle all the non-GUI tasks: arduino/arduino-cli#1401 That bug has already been fixed: arduino/arduino-cli#1410 The fixed version of Arduino CLI is used starting with Arduino IDE 2.0.0-beta.12, so you should no longer experience this issue when using the latest version of the IDE. |
This may be a duplicate of #151 in which case feel free to close. But it may be another issue (see the "greyed board problem lower down).
host OS: Ubuntu 20.04
ide version etc: installed today from your pages:
steps
Any idea what causes that?
The text was updated successfully, but these errors were encountered: