Skip to content

[Feature request] Build test firmware that can do basic testing #342

Open

Description

@LeeNX

Is this related to a problem?

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.

Describe alternatives you've considered

No response

Which area does this touch?

  • Buttons / special buttons
  • Axes / sliders / simulation controls
  • Hats (D-pad)
  • HID descriptor / report configuration
  • Battery level / power state
  • Nordic UART Service (NUS)
  • Pairing / connection management
  • Other

Additional context

No response

Activity

  1. LeeNX commented on Aug 27, 2026

    @LeeNX
    CollaboratorAuthor

    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?

  2. LeeNX commented on Sep 18, 2026

    @LeeNX
    CollaboratorAuthor

    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.

  3. lemmingDev commented on Sep 21, 2026

    @lemmingDev
    Owner

    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

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions