-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
ESP32S2 Dev Module detected ad Deneyap Mini #6384
Comments
Since 2.0.0 rc3 a lot has been changed / fixed. Have you tried with the actual 2.0.2? |
I don't think there is a 2.0.2 version of the Arduino IDE. |
the very top version of the link you posted does include 2.0.2 :) many boards will end up with the same pid/vid BTW... we will see how we will deal with this in near future. |
Hello, sorry for late reply. Are you able to retest this with Arduino core ESP32 version 2.0.3-rc1? Thanks! |
I'm closing the issue as expired due to no answer. If needed, please reopen it. Thanks for understanding. |
This is still true for version 2.0.7 |
I find that the problem is with this api that arduino-cli uses, it gives the wrong result.
|
Hi there, I´m encountering the same issue: --> Dev Board is detected as Deneyap Mini. A workaround could be, that i exchange the pins_arduino.h file in the variants-deneyap folder, so i can use it as a "normal dev board". |
2.2.1, still the same problem. If the dev's aren't interested in fixing this is there some way we can delete the Deneyap boards ourselves? |
Hi @IanEatsBabies, I would not call it as we are not interested in solving. Feel free to propose the fix, this is an open public project. Actually this is a bigger problem that some boards match PID/VID, there is no not straight-forward solution how to deal with this. Anyway, I am reopening the issue. Any ideas @P-R-O-C-H-Y and @me-no-dev? |
Sorry man, came across as such. I'll give it a go tonight at work when I've got some time. |
@IanEatsBabies this is both unslovable and partially solvable by the IDE folks.
|
I've been looking into fingerprinting until I came upon a far more powerfull solution: Why not build in a simple filter people can use? |
"The IDE could somewhat help by not picking random board that matches VID/PID every time and show you our main dev module instead (first in the list)" "All integrated CDC/JTAG boards (S3, C3, C6, H2) also use the same VID/PID for that interface. It is hardcoded into the chip and can not be changed" |
The fix is to remove all the non-unique VID/PID associations from The incorrect port identifications caused by the inappropriate associations make things confusing for Arduino IDE users, and make it impossible to use any of these boards in the "new" Arduino Cloud editor: https://forum.arduino.cc/t/web-editor-misidentifies-connected-board/1193052/9 It is currently possible to workaround that incompatibility by using the "old" Cloud Editor, but Arduino is about to remove access to the "old" editor. |
It's not using just boards.txt which is esp32 side. but also this web api (https://builder.arduino.cc/v3/boards/byVidPid/0x303A/0x0002 ) which i believe is provided by arduino and it's discovery machanism. |
This was resolved by #9717. The innovative solution that was implemented will cause the port to be identified as "ESP32 Family Device" instead of as a random board. Something to note is that this solution will result in the dummy "ESP32 Family Device" board to be selected when the user selects the board from the board selector menu in the Arduino IDE 2.x toolbar (which automatically sets the board when the port has a positive identification). This causes compilation to fail:
So the user must make sure to select the appropriate board from the Tools > Board menu. However, the new system has been in production use for a few weeks now and I don't find any reports of users of this happening so it seems that the benefits of the port having a helpful label will outweigh the potential harm of this causing misconfiguration of the IDE. |
@per1234 I'm glad that you find this helpful, as it was the only "solution" I could come up with. |
Board
ESP32S2 Dev Module
Device Description
Some hardware presents itself as an ESP32S2 Dev Module at times when they are being set into flashing mode and uses the built-in USB driver, i've seen this with Wemos S2 Pico, and i believe i've also encountered it with Unexpected Maker's FeatherS2.
Hardware Configuration
Not relevant
Version
latest master
IDE Name
Arduino IDE 2.0.0-rc3
Operating System
MacOS
Flash frequency
Not relevant
PSRAM enabled
yes
Upload speed
Not relevant
Description
When ever hardware that presents itself as ESP32S2 Dev Module, Arduino will detect it as a Deneyap Mini, as Deneyap Mini re-uses the same PID and VID.
I propose that the Deneyap Mini PID and VID get's less priority, so that board are primarily detected as ESP32S2 dev modules by default instead.
Sketch
Debug Message
Other Steps to Reproduce
Attach a ESP32S2 Dev Module to the Arduino 2.0.0-rc3 IDE and it will detect it as a Deneyap Mini
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: