-
-
Notifications
You must be signed in to change notification settings - Fork 433
No ports discovered #605
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 looks very similar to #573, but there is a significant difference:
When I experience #573, after unplugging and then replugging the board its port is always recognized by the IDE (though any other ports on the computer remain unrecognized. |
Because this is beta.12 not 11?😀 The bug grows up along with the version number😀 |
Hello @Silver-Fang. The similar bug #573 was fixed for me by Please try the nightly build and let us know whether the bug is fixed for you or not. The download links for the nightly build are here: |
Hi @Silver-Fang. Please try again with the latest release of the Arduino IDE and let us know whether or not the bug is fixed for you. |
Yes, it's fixed. |
I have a similar bug. After connecting a Wemos Lolin32 board, the port to which the board is connected is not displayed in the Boards Manager or the Tools menu. Restarting the computer and restarting the IDE does not solve the problem. If I connect an original Arduino Uno board, the IDE sees it and shows the port it is connected to. |
Hi @Asderlop. Please post about your problem over on the Arduino Forum: https://forum.arduino.cc/c/software/arduino-ide-2-0/93 I'll provide support for your problem over there. If we eventually determine it is caused by a problem in Arduino IDE, I will follow up to make sure it is tracked by the developers. |
Describe the bug
IDE could not discover any board
To Reproduce
Steps to reproduce the behavior:
Expected behavior
IDE should have found my Arduino Mega 2560 board.
Screenshots

Desktop (please complete the following information):
Additional context
Both windows device manager and MATLAB can discover my board. MATLAB scripts can normally connect to and operate on the board.
I rolled back to beta.11 and everything went fine. There must be something wrong in beta.12.
The text was updated successfully, but these errors were encountered: