feat: Add Twin AIoT Module support for ESP32-S3-N4R2 #11755

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

Jump to bottom

Merged

me-no-dev merged 2 commits into espressif:master from bekirr12:feature/twin-aiot-board

Aug 26, 2025

Merged

feat: Add Twin AIoT Module support for ESP32-S3-N4R2 #11755

me-no-dev merged 2 commits into espressif:master from bekirr12:feature/twin-aiot-board

Aug 26, 2025

Conversation

bekirr12

Copy link

Contributor

@bekirr12 bekirr12 commented Aug 22, 2025

Description of Change
This pull request adds support for the "Twin AIoT Module" to the Arduino-ESP32 core. As a product developed by our company, "Twin Science", we aim to make it easily accessible and usable for all our users directly within the Arduino IDE.

The "Twin AIoT Module" is a development board based on the "ESP32-S3-MINI-1" chip. It features "led matrix", "touchpad", "rgb led", "analog and digital pins". The board's pin definitions and configuration have been carefully prepared and tested.

Tests scenarios
I have tested this pull request on my "Twin AIoT Module".

The tests were performed using the Arduino IDE 2.3.6.

The following scenarios were tested successfully:

Basic Functionality: The classic "Blink", "Serial Monitor", "RGB Led", "Led Matrix" examples worked as expected, confirming core functionality and proper board selection.

GPIOs: A series of digital and analog I/O tests were performed to verify the correctness of the pinout definitions.

Note:

Connectivity: Wi-Fi and Bluetooth examples were run successfully to confirm wireless connectivity.

Related Library

@bekirr12


 feat: Add Twin AIoT Module support for ESP32-S3-N4R2

137d20b

@bekirr12 bekirr12 requested a review from P-R-O-C-H-Y as a code owner

August 22, 2025 10:43

@github-actions GitHub Actions

Copy link

Contributor

github-actions bot commented Aug 22, 2025 •

edited

Loading

Messages
📖	🎉 Good Job! All checks are passing!

👋 Hello bekirr12, 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.
- 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 53bf894