-
Notifications
You must be signed in to change notification settings - Fork 43
feat: add chip support status for esp32c5 #473
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
feat: add chip support status for esp32c5 #473
Conversation
f-hollow
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ginkgm Please review the ESP32-C5 chip support status page. The link to it will be added on the main page.
Unfortunately main page references to articles do not render correctly in previews.
| According to the chip mass production plan, the planned support for ESP32-C5 in ESP-IDF v5.4 has been rescheduled to ESP-IDF v5.5. Thank you for your understanding. | ||
|
|
||
| - ESP-IDF v5.5, whose planned release date is June 30th 2025, will include the initial support for ESP32-C5 v1.0. Now the master branch contains the latest preview support for ESP32-C5 v1.0. Until ESP-IDF v5.5 is released, please update to the HEAD of master branch to develop with v1.0 chips. | ||
| - If you would like to try features with the early samples of the ESP32-C5 v1.0, please refer to the ESP32-C5 v0.1 support status page. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- If you would like to try features with the early samples of the ESP32-C5 v0.1, please refer to ESP32-C5 v0.1 support status page.
6911889 to
a70286b
Compare
a70286b to
77f8cc2
Compare
|
@ginkgm @Alvin1Zhang Updated according to your comments. PTAL again. |
Description
This PR adds the chip support status page for ESP32-C5 v1.0.
Testing
Checklist
Before submitting a Pull Request, please ensure the following: