Skip to content

Update boards.txt with updated CodeCell board variant #11313

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 5 commits into from
Apr 28, 2025
Merged

Update boards.txt with updated CodeCell board variant #11313

merged 5 commits into from
Apr 28, 2025

Conversation

microbotsio
Copy link
Contributor

Description of Change

This Pull Request adds support for a custom ESP32-C3-based board named "CodeCell C3". The changes include:

  • A new entry in boards.txt under the identifier codecellc3
  • Configuration for upload tools, flash size, partition schemes, JTAG settings, and other board-specific options
  • Custom build.board=CODECELLC3 identifier

This allows users to select the "CodeCell C3" board from the Arduino IDE and build/upload sketches using the ESP32 Arduino core.

Tests scenarios

Tested on custom CodeCell C3 hardware using the following setup:

  • Arduino IDE 2.3.5
  • Verified detection and upload via USB CDC

Related links

N/A

@CLAassistant
Copy link

CLAassistant commented Apr 28, 2025 •
edited
Loading

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ microbotsio
❌ CarlBugeja
You have signed the CLA already but the status is still pending? Let us recheck it.

@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Apr 28, 2025 •
edited
Loading

Warnings
⚠️

Some issues found for the commit messages in this PR:

  • the commit message "Update boards.txt":
    • summary looks empty
    • type/action looks empty
  • the commit message "Update boards.txt":
    • summary looks empty
    • type/action looks empty
  • the commit message "Update boards.txt":
    • summary looks empty
    • type/action looks empty
  • the commit message "Update boards.txt":
    • summary looks empty
    • type/action looks empty

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

  • follow Conventional Commits style
  • correct format of commit message should be: <type/action>(<scope/component>): <summary>, for example fix(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 the Conventional Precommit Linter).

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

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


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

DangerJS is triggered with each push 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 is not 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 manually retry these Danger checks, please navigate to the Actions 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 against a091c33

P-R-O-C-H-Y
P-R-O-C-H-Y reviewed Apr 28, 2025
View reviewed changes
@P-R-O-C-H-Y P-R-O-C-H-Y added the Status: Pending Merge Pull Request is ready to be merged label Apr 28, 2025
@microbotsio
Copy link
Contributor Author

Is there anything further we need to address?

@me-no-dev
Copy link
Member

@microbotsio you need to sign the CLA

@me-no-dev me-no-dev added the Status: Pending CLA ⚠️ Contributor is required to sign the CLA label Apr 28, 2025
@microbotsio
Copy link
Contributor Author

@microbotsio you need to sign the CLA

CLA was signed but it still shown as pending

@me-no-dev
Copy link
Member

@microbotsio seems to be an issue with @CarlBugeja account

@CarlBugeja
Copy link
Contributor

@microbotsio seems to be an issue with @CarlBugeja account

signed

@me-no-dev
Copy link
Member

signed

@CarlBugeja still shows unsigned... strange

@me-no-dev me-no-dev removed the Status: Pending CLA ⚠️ Contributor is required to sign the CLA label Apr 28, 2025
@me-no-dev me-no-dev merged commit 9193c9d into espressif:master Apr 28, 2025
8 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

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

Assignees
No one assigned
Labels
Status: Pending Merge Pull Request is ready to be merged Type: 3rd party Boards
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@microbotsio @CLAassistant @me-no-dev @CarlBugeja @P-R-O-C-H-Y