The challenge

Reach builds wireless power-beaming systems that deliver safe, targeted RF energy over distance. Its technology keeps drones, sensors, robots, and other devices running without cables or battery swaps for partners including the U.S. Armed Forces, NASA, and Panasonic.

A system like Reach’s is fundamentally hard to test. It spans many modules that must work together precisely, while firmware, hardware, and RF engineers need a shared understanding of the complete product. In R&D, speed depends on two questions: how quickly the team can prototype an idea, and how quickly it can build enough confidence in the result.

Before BootLoop, a single full-system test could take hours, sometimes days, to set up. Knowledge was concentrated across a few engineers: one owned the flashing scripts, another the key instruments, and another knew how to run the system end to end. Shared hardware created a constant coordination bottleneck.

“We were looking for a competitive AI solution to support our firmware team and start integrating AI tools into our hardware teams’ workflows. BootLoop allows us to move faster and more confidently with support for our HITL setup and custom tools projects.”

Marine Dunoguier

VP of Engineering, Reach

The solution

Reach started with the firmware team. BootLoop Develop helped engineers bring up new hardware and drivers and investigate timing problems across single boards and connected devices.

With development moving faster, testing became the bottleneck. Reach used BootLoop Test to build a full-system bench coordinating more than 16 instruments and devices. It verifies timing precision, firmware behavior, hardware operation, and performance against specification. The bench can run dozens of automated tests each day on the full system or any subsystem, and any team can start a run with one click.

BootLoop’s agents turn specifications, interface descriptions, and design documents into deterministic automated test plans. The resulting tests are portable: they run on any bench in the company with the same result, whether today or years from now. Tests written during bring-up or validation can move into CI without a separate harness, while engineers and agents review the same stored results.

“Our system has a lot of moving parts, and getting the timing right across all of them is critical. BootLoop gave us an early win: we could test every subsystem and component quickly and thoroughly, without building custom tooling for each one.”

Sam Rastovich

Lead Software Engineer, Reach

Each new test locks in expected behavior. As more of the system is covered, Reach can move faster and run work in parallel, with deterministic tests catching drift and regressions.

The workflow then scaled across the company. Smaller desk setups reuse test suites, instrument configurations, and procedures from the main bench. Hardware engineers automated previously supervised procedures such as battery discharge with electronic loads and high-power converter load-response and efficiency testing. Reach now uses the same platform to maintain RF testing.

Results

• Days of setup reduced to one click for full-system integrated tests.

• Long, supervised bench procedures now run unattended.

• The same deterministic tests run in development, validation, and CI on any bench.

• Every run captures the precise code and configuration, making regressions, performance changes, and requirements coverage traceable.

• Firmware, hardware, and RF teams share one reusable test library and a common record of results.

Is this your team?

Most hardware teams accumulate scripts that only one engineer can run and benches that only work when their owner is available. That is manageable at first, but it eventually limits delivery speed. BootLoop turns these one-off workflows into repeatable benches and tests the whole team can use.

Book a call

Follow Reach on LinkedIn