feat(3rd party board): Add Fri3d Badge 2024 (ESP32-S3-WROOM-1)

[francisduvivier]

Description of Change

Add Fri3d Badge 2024 (ESP32-S3-WROOM-1) as a new 3rd party board

Tests scenarios

I have tested my PR on the Fri3d Badge 2024 (ESP32-S3-WROOM-1)

Related links

Board Image: https://github.com/Fri3dCamp/badge_2024/blob/main/docs/badge2024.jpg
More info on https://github.com/Fri3dCamp/badge_2024

[CLAassistant]

All committers have signed the CLA.

[github-actions]

	Messages
📖	You might consider squashing your 4 commits (simplifying branch history).

👋 Hello francisduvivier, we appreciate your contribution to 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.
- Addressing info messages (📖) is strongly recommended; they're less critical but valuable.
- 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 2a081ee

[francisduvivier]

If I want to get this board in the v2.0.x release, should I then also make a PR towards the release/v2.0.x branch?

[P-R-O-C-H-Y]

@francisduvivier PTAL on my comments.

[P-R-O-C-H-Y]

If I want to get this board in the v2.0.x release, should I then also make a PR towards the release/v2.0.x branch?

If you want to get the board to the 2.x branch, you can open the PR targeting that branch. But it's not recommended anymore as IDF 4.4 is EOL and we don't have any plans to release a new 2.X version.

[P-R-O-C-H-Y]

One last change needed :)

[francisduvivier]

If I want to get this board in the v2.0.x release, should I then also make a PR towards the release/v2.0.x branch?

If you want to get the board to the 2.x branch, you can open the PR targeting that branch. But it's not recommended anymore as IDF 4.4 is EOL and we don't have any plans to release a new 2.X version.

Ah very good to know, thanks for the info!

[P-R-O-C-H-Y]

@francisduvivier Last few requests and suggestions, mostly related to the module you use on your board, which is ESP32-S3-WROOM-1-N16R8 with 16MB flash and 8MB OPI PSRAM. It's good to remove the options which are not possible to avoid crashing due to wrong selection. PTAL :)

[francisduvivier]

@francisduvivier Last few requests and suggestions, mostly related to the module you use on your board, which is ESP32-S3-WROOM-1-N16R8 with 16MB flash and 8MB OPI PSRAM. It's good to remove the options which are not possible to avoid crashing due to wrong selection. PTAL :)

Thanks again for the help! I applied all suggestions in a new commit.