We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
9.0.0 Beta. NA?
# NA
https://circuitpython.org/board/espressif_esp32c6_devkitc_1_n8/ HEADING says it's for ESP32-S3-DevKitC-1-N8.
It shows up in search results(https://circuitpython.org/downloads?q=esp32-s3-devkitc-1-n8) too: It goes to https://circuitpython.org/board/espressif_esp32c6_devkitc_1_n8/.
I'm still not sure if it's for ESP32-S3-DevKitC-1-N8 or ESP32-C6-DevKitC-1-N8.
Won't flashing wrong firmware break stuff?
No response
Wasn't sure where to report so reporting here.
The text was updated successfully, but these errors were encountered:
This is probably a typo or misnaming in the files that build the website. Transferring to the circuitpython.org repo.
Sorry, something went wrong.
This one is the ESP32-C6-DevKitC-1-N8. I'm submitting a PR to fix the name.
Successfully merging a pull request may close this issue.
CircuitPython version
Code/REPL
# NA
Behavior
https://circuitpython.org/board/espressif_esp32c6_devkitc_1_n8/ HEADING says it's for ESP32-S3-DevKitC-1-N8.

It shows up in search results(https://circuitpython.org/downloads?q=esp32-s3-devkitc-1-n8) too:

It goes to https://circuitpython.org/board/espressif_esp32c6_devkitc_1_n8/.
I'm still not sure if it's for ESP32-S3-DevKitC-1-N8 or ESP32-C6-DevKitC-1-N8.
Won't flashing wrong firmware break stuff?
Description
No response
Additional information
Wasn't sure where to report so reporting here.
The text was updated successfully, but these errors were encountered: