Manuel

Isn't there a button GPIO in the [config](https://github.com/meshtastic/firmware/blob/46f797c40dedb28d90898817f403e7e80c318c53/bin/config-dist.yaml#L173)?

> but the built "program" fails to run with a Exec format error. It's clearly not building for a Pi but I'm now at the limit of my knowledge. `native`...

> OK. So the other platforms cross compile but native doesn't (just checking my understanding). yes, esp32 / nrf / rp2040 / stm are all cross-compiling using the respective build...

Switching to V5.x also requires migrating all I2C clients (and those of external libraries) to the new I2C API as a mix of both old and new API in a...

> Huh, that looks really great - what help do you need with finishing this part? I can extend and test it for Heltec V3. The CI build adaptations for...

> What adaptations and features are you talking specifically? For the CI it obviously has to use [pioarduino](https://github.com/pioarduino/platformio-core) instead of platformio. Things that have been implemented in pioarduino python scripts...

> I'll pull your branch and see - when I did my proof of concept hacky migration - VS Code upload worked perfectly fine did you replace (remove/disable) the vscode...

@phaseloop > https://github.com/Jason2866/platform-espressif32 Although by the same author this is not pioarduino. The pioarduino framework is much more advanced, e.g. it allows configuring esp-idf and building the arduino-libs and does...

There's already a similar PR: https://github.com/meshtastic/firmware/issues/8571

This has been fixed already in 2.7.16 by https://github.com/meshtastic/firmware/pull/8601 (and related bugfix https://github.com/meshtastic/firmware/pull/8884) .