Skip to content

feat(build): add ESP32-C5 boards to default build targets#2564

Open
r13xr13 wants to merge 1 commit into
BruceDevices:mainfrom
r13xr13:feat/esp32-c5-targets
Open

feat(build): add ESP32-C5 boards to default build targets#2564
r13xr13 wants to merge 1 commit into
BruceDevices:mainfrom
r13xr13:feat/esp32-c5-targets

Conversation

@r13xr13

@r13xr13 r13xr13 commented Jun 18, 2026

Copy link
Copy Markdown

Summary

Adds three ESP32-C5 (RISC-V) board targets to the default platformio build environments so they build alongside the standard Xtensa targets.

Changes

  • platformio.ini: Uncomment esp32-c5, esp32-c5-tft, and nm-cyd-c5 in default_envs
  • Also uncommented several previously-disabled Xtensa targets: m5stack-sticks3, m5stack-cplus2, CYD-2432S028, lilygo-t-embed-cc1101, lilygo-t-deck

Notes

Adds esp32-c5, esp32-c5-tft, and nm-cyd-c5 to default_envs in platformio.ini. These boards use the RISC-V ESP32-C5 chip and were previously excluded from default builds.

@Ninja-jr Ninja-jr left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Nice initiative, but if they were excluded from CI builds, there's probably a reason. Shouldn't we first ensure all is resolved in the boards folder for those or if full compatibility with them is ensured before re-enabling things on Platformio.ini?
That's how we ended up with nimble 2.5 and had to sort quite a mess a few months back cause someone decided it was better to change things to let it update past the stable and working 2.3.7.

By the way for future reference, the nimble version on platformio.ini shall be left at absolute 2.5.

@r13xr13

r13xr13 commented Jun 26, 2026

Copy link
Copy Markdown
Author

Nice initiative, but if they were excluded from CI builds, there's probably a reason. Shouldn't we first ensure all is resolved in the boards folder for those or if full compatibility with them is ensured before re-enabling things on Platformio.ini?
That's how we ended up with nimble 2.5 and had to sort quite a mess a few months back cause someone decided it was better to change things to let it update past the stable and working 2.3.7.

By the way for future reference, the nimble version on platformio.ini shall be left at absolute 2.5.

Yes I understand, this might create some issues, until libs get sorted and updated. But honestly nimble is a more modern lib. image

@Ninja-jr

Copy link
Copy Markdown
Contributor

Yes nimble is what we use and I get your point. What i was saying is we better keep it at 2.5 which is a recent working version.

For the rest, we'll better to see with the maintainers why those boards were commented on platformio.ini and if it's safe to re-enable them at this point.

@r13xr13

r13xr13 commented Jun 26, 2026

Copy link
Copy Markdown
Author

Yes nimble is what we use and I get your point. What i was saying is we better keep it at 2.5 which is a recent working version.

For the rest, we'll better to see with the maintainers why those boards were commented on platformio.ini and if it's safe to re-enable them at this point.

Understood

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants