Skip to content

Added FoBE Quill ESP32S3 Mesh board support #11698

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 1 commit into from
Aug 22, 2025
Merged

Added FoBE Quill ESP32S3 Mesh board support #11698

merged 1 commit into from
Aug 22, 2025

Conversation

chihosin
Copy link
Contributor

@chihosin chihosin commented Aug 7, 2025

This pull request introduces support for the FoBE Quill ESP32-S3 Mesh board by adding its configuration to the boards.txt file and defining its pin mappings in pins_arduino.h. These changes primarily implement compatibility for the FoBE Quill ESP32-S3 Mesh hardware and provide the necessary settings for its operation.

image
  • Introduced new variant files including pins_arduino.h, variant.cpp, and bootloader configurations.
  • Added definitions for USB, GPIO, and various peripherals.
  • Included binary files for tinyuf2 bootloader and firmware.

Product doc link: https://docs.fobestudio.com/product/f1102

@chihosin chihosin requested a review from P-R-O-C-H-Y as a code owner August 7, 2025 05:45
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Aug 7, 2025 •
edited
Loading

Warnings
⚠️

Some issues found for the commit messages in this PR:

  • the commit message "add(board): Added FoBE Quill ESP32S3 Mesh board support":
    • type/action should be one of [change, ci, docs, feat, fix, refactor, remove, revert, test]
    • body must have leading blank line

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 chihosin, 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 2b14210

P-R-O-C-H-Y
P-R-O-C-H-Y requested changes Aug 21, 2025
View reviewed changes
Copy link
Member

@P-R-O-C-H-Y P-R-O-C-H-Y left a comment

Choose a reason for hiding this comment

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

@chihosin PTAL on my comments.

@P-R-O-C-H-Y P-R-O-C-H-Y added Type: 3rd party Boards Related to third-party/non-Espressif hardware boards. Status: Awaiting Response Awaiting a response from the author labels Aug 21, 2025
@chihosin chihosin force-pushed the feat/variants_fobe_quill_esp32_s3_mesh branch from 2e5a376 to 2598aa3 Compare August 21, 2025 11:23
@chihosin chihosin closed this Aug 21, 2025
@chihosin chihosin force-pushed the feat/variants_fobe_quill_esp32_s3_mesh branch from 2598aa3 to 15be2a5 Compare August 21, 2025 11:28
@chihosin
add(board): Added FoBE Quill ESP32S3 Mesh board support
2b14210 
- Introduced new variant files including pins_arduino.h, variant.cpp, and bootloader configurations.
- Added definitions for USB, GPIO, and various peripherals.
- Included binary files for tinyuf2 bootloader and firmware.

Signed-off-by: Chiho Sin <chihosin@icloud.com>
@chihosin chihosin reopened this Aug 21, 2025
@chihosin chihosin requested a review from P-R-O-C-H-Y August 21, 2025 11:31
@P-R-O-C-H-Y P-R-O-C-H-Y added Status: Pending Merge Pull Request is ready to be merged and removed Status: Awaiting Response Awaiting a response from the author labels Aug 21, 2025
@me-no-dev me-no-dev merged commit 956b687 into espressif:master Aug 22, 2025
27 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 Related 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
@chihosin @P-R-O-C-H-Y @me-no-dev