Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

feat(board): add support for Waveshare ESP32-C3-Zero#12132

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
me-no-dev merged 5 commits intoespressif:masterfromDrayxR3X:esp32-c3-zero
Dec 17, 2025

Conversation

@DrayxR3X
Copy link
Contributor

Description of Change

This pull request adds support for theWaveshare ESP32-C3-Zero board to the Arduino-ESP32 core.

Changes include:

1.Added board entry in boards.txt
2.Created variants/waveshare_esp32_c3_zero with pin mapping

Test Scenarios

I have tested the following scenarios to verify the board support:

1.Verified compilation and upload with Arduino IDE 2.3.4 and Espressif Arduino-ESP32 v3.3.3
2.Tested basic examples successfully on the Waveshare ESP32-C3-Zero board

The following examples were compiled, uploaded, and executed successfully:

1.Blink (WS2812 LED with digitalWrite)
2.Blink RGB (WS2812 / RGB LED with rgbLedWrite)
3.Serial CDC (USB communication)
4.WiFi (WiFiClient example)

@github-actions
Copy link
Contributor

github-actionsbot commentedDec 13, 2025•
edited
Loading

Warnings
⚠️

Some issues found for the commit messages in this PR:

  • the commit message"Change the board name back to Waveshare ESP32-C3-Zero to align with Waveshare’s unified product naming convention.":
    • summary should not end with a period (full stop)
    • summary looks empty
    • type/action looks empty
  • the commit message"Modify the boards.txt file according to the review":
    • summary looks empty
    • type/action looks empty

Please fix these commit messages - here are some basic tips:

  • followConventional Commits style
  • correct format of commit message should be:<type/action>(<scope/component>): <summary>, for examplefix(esp32): Fixed startup timeout issue
  • allowed types are:change,ci,docs,feat,fix,refactor,remove,revert,test
  • sufficiently descriptive message summary should be between 10 to 72 characters and start with upper case letter
  • avoid Jira references in commit messages (unavailable/irrelevant for our customers)

TIP: Install pre-commit hooks and run this check when committing (uses theConventional Precommit Linter).

👋Hello DrayxR3X, we appreciate your contribution to this project!

📘 Please review the project'sContributions Guide for key guidelines on code, documentation, testing, and more.
🖊️ Please also make sure you haveread and signed theContributor License Agreement for this project.
Click to see more instructions ...


This automated output is generated by thePR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with eachpush event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger isnot a substitute for human code reviews; it's still important to request a code review from your colleagues.
-Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- To manuallyretry these Danger checks, please navigate to theActions tab and re-run last Danger workflow.

Review and merge process you can expect ...


We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫dangerJS against9f2470b

Copy link
Member

@P-R-O-C-H-YP-R-O-C-H-Y left a comment•
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Hi@DrayxR3X, please move the Waveshare C3 ZERO next to the Waveshare C6 Zero in the boards.txt file. Will be much better. PR looks good otherwise

@P-R-O-C-H-YP-R-O-C-H-Y added the Type: 3rd party BoardsRelated to third-party/non-Espressif hardware boards. labelDec 15, 2025
@P-R-O-C-H-YP-R-O-C-H-Y added the Status: Pending MergePull Request is ready to be merged labelDec 17, 2025
@me-no-dev
Copy link
Member

@P-R-O-C-H-Y please fix the conflicts

@P-R-O-C-H-Y
Copy link
Member

@me-no-dev Done

@me-no-devme-no-dev merged commita048db0 intoespressif:masterDec 17, 2025
13 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@P-R-O-C-H-YP-R-O-C-H-YP-R-O-C-H-Y approved these changes

Assignees

No one assigned

Labels

Status: Pending MergePull Request is ready to be mergedType: 3rd party BoardsRelated to third-party/non-Espressif hardware boards.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@DrayxR3X@me-no-dev@P-R-O-C-H-Y
[8]ページ先頭
©2009-2025 Movatter.jp