You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature request] Build test firmware that can do basic testing #342
While helping with ESP32-BLE-Gamepad issues, I have seen issue where local build differences could cause problems
Describe the solution you'd like
Having a set of flushable firmware for the base ESP32 MCU, that only connects with BLE and presses a set button every few seconds and possible ramps the battery and/or plugs in the power and out to simulate some functions of the BLE Gamepad, that can be flashed without any other external dependancies.
I think we add a CI step that builds the four MCU devices and keep the assets for users have trouble to download and test, to make sure it's not their local dev environment that is the problem.
We could add USB monitoring, possible LED blinking and maybe we can flash/clear the NVS?
I am wondering if we should merge the code and build process for this test firmware, which could support the Serial/FTDI and NuS interface, to do testing. I have added to my own build systems MCU temp. This could be a source of truth for testing. At the moment my HIL project builds testing firmware on almost every run.
Down side, could have more moving parts, that could be a problem to look after, but I think there would be less drift.
Good news: most of this already exists — test/ci_build is exactly that firmware (button cycling, stick sweep, battery ramp, Serial + NuS, no deps), CI builds it for esp32dev/s3/c3 on every push and attaches the binaries to releases (see v0.8.0's assets). So the "download and test" story is live.
The genuinely missing bits from your list: LED blinking, NVS wipe, and MCU temp — all small additions to src/main.cpp, happy to add them.
On merging the HIL per-run builds into this - It's up to you; ci_build as the single source of truth kills the drift you're worried about.
Activity
LeeNX commentedon Aug 27, 2026
I think we add a CI step that builds the four MCU devices and keep the assets for users have trouble to download and test, to make sure it's not their local dev environment that is the problem.
We could add USB monitoring, possible LED blinking and maybe we can flash/clear the NVS?
ci: self-simulating BLE test firmware with flashable artifacts
LeeNX commentedon Sep 18, 2026
I am wondering if we should merge the code and build process for this test firmware, which could support the Serial/FTDI and NuS interface, to do testing. I have added to my own build systems MCU temp. This could be a source of truth for testing. At the moment my HIL project builds testing firmware on almost every run.
Down side, could have more moving parts, that could be a problem to look after, but I think there would be less drift.
lemmingDev commentedon Sep 21, 2026
Hey
Good news: most of this already exists — test/ci_build is exactly that firmware (button cycling, stick sweep, battery ramp, Serial + NuS, no deps), CI builds it for esp32dev/s3/c3 on every push and attaches the binaries to releases (see v0.8.0's assets). So the "download and test" story is live.
The genuinely missing bits from your list: LED blinking, NVS wipe, and MCU temp — all small additions to src/main.cpp, happy to add them.
On merging the HIL per-run builds into this - It's up to you; ci_build as the single source of truth kills the drift you're worried about.
Up to you