feat(build): add ESP32-C5 boards to default build targets#2564
Conversation
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
left a comment
There was a problem hiding this comment.
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 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 |

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: Uncommentesp32-c5,esp32-c5-tft, andnm-cyd-c5indefault_envsm5stack-sticks3,m5stack-cplus2,CYD-2432S028,lilygo-t-embed-cc1101,lilygo-t-deckNotes
nimble_common.cppbtStop() change required for C5 BLE (PR fix(ble): remove deprecated NimBLEService::start() call, use btStop() on C5 #2560)