-
-
Notifications
You must be signed in to change notification settings - Fork 81
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
Error Compiling For ESP32 C3 #45
Comments
I found a temporary workaround. If I comment out lines 310, and 312-317 of the latest Button2.cpp file (d7d62e8) then it compiles correctly. So, there is definitely something about the definition of those pins that is making it think those pins are capacitive. And none of the pins on a C3 can be capacitive. |
Hey @ryancasler, Could you try this sketch and tell me if all your C3s are detected?
(Reminder to myself: Using this comment as a starting point.) |
Hey @ryancasler, |
pushed new version |
Yup...new version worked perfectly. Thanks!!! |
When compiling a Button2 sketch using an ESP32 C3 board (I tried 2 different brands, DFRobot and Adafruit), I get the following error:
One thing that sets the C3 apart from other members of the ESP32 family is the fact that it doesn't support touch. I can't seem to figure out why it's reading this as capacitive. Here are the relevant sections of my sketch:
And of course I have all the relevant callbacks and whatnot.
Now, If I switch to an ESP32 S2 board, the exact same sketch compiles perfectly with zero changes. So, I assume there is something wrong in the board definition or the variants pin definition for the C3 boards but for the life of me I can't find it. I also tried to define a custom state function for all of the buttons and that didn't help. I still got the same error when compiling. Any advice on where to look and what might need to be changed? I'm using the latest version of the ESP32 Core for Arduino, v2.0.5.
https://github.com/espressif/arduino-esp32/releases/tag/2.0.5
Thanks so much!!
The text was updated successfully, but these errors were encountered: