Skip to content

feat(p4): Add 32MB Flash Partitions to ESP32-P4 #11453

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 2 commits into from
Jun 10, 2025
Merged

feat(p4): Add 32MB Flash Partitions to ESP32-P4 #11453

merged 2 commits into from
Jun 10, 2025

Conversation

me-no-dev
Copy link
Member

@me-no-dev me-no-dev commented Jun 10, 2025 •
edited by P-R-O-C-H-Y
Loading

This pull request updates the boards.txt file to add new partition schemes and flash size option for the esp32p4 board, enabling support for larger flash configurations with different file systems.

Added Partition Schemes:

  • 32M Flash (4.8MB APP/22MB FATFS): Added app5M_fat24M_32MB partition scheme with a maximum upload size of 4718592 bytes.
  • 32M Flash (4.8MB APP/22MB LittleFS): Added app5M_little24M_32MB partition scheme with a maximum upload size of 4718592 bytes.
  • 32M Flash (13MB APP/6.75MB SPIFFS): Added app13M_data7M_32MB partition scheme with a maximum upload size of 13107200 bytes.

Flash Size Option:

  • 32MB (256Mb)

@me-no-dev me-no-dev requested a review from P-R-O-C-H-Y as a code owner June 10, 2025 07:12
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Jun 10, 2025 •
edited
Loading

Messages
📖 🎉 Good Job! All checks are passing!

👋 Hello me-no-dev, 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 0544341

@me-no-dev me-no-dev added the Status: Pending Merge Pull Request is ready to be merged label Jun 10, 2025
@me-no-dev me-no-dev merged commit 0007815 into master Jun 10, 2025
16 checks passed
@me-no-dev me-no-dev deleted the feature/32mb_p4_flash branch June 10, 2025 08:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@lucasssvaz lucasssvaz lucasssvaz approved these changes

@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
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@me-no-dev @lucasssvaz @P-R-O-C-H-Y