Case Study: BootLoop x LURA

Accelerating Medical Device Validation with Agentic Hardware Testing

The Problem

Lura Health is building something that has never existed before: a continuous salivary diagnostic sensor that sits inside your mouth, monitors biomarkers in real time, and streams data to your phone over BLE. The device is built around a Silicon Labs EFR32, with an I2C temperature sensor, a low-power analog frontend for electrochemical sensing, and tight power sequencing to keep everything running on a battery you would barely notice. The whole thing is roughly 2x3mm. Small enough to embed in a retainer.

That size creates a serious engineering constraint. The device is too small to probe directly in production, so Lura designed a manufacturing-only carrier board and a separate testing breakout board to get observability into the system. Every unit that ships needs its firmware validated across three dimensions: low-power mode behaviour (the device has to last without frequent charging), sensor calibration accuracy (this is clinical-grade diagnostics), and BLE connection stability (continuous, reliable data transfer to the companion app).

Before BootLoop, validating a single unit meant an engineer manually running one-off tests or writing repetitive test scripts, flashing code, configuring bench equipment, and running through every test by hand. For a lean team trying to hit an FDA submission window, that process was burning time they did not have.

What Changed

BootLoop's agent ingested Lura's schematics and datasheets for the BG22 system, then generated a full hardware-in-the-loop test suite for their production-line validation. Three things happened:

The agent built a complete EOL testing rig in hours, not weeks. It created a customised test suite covering power sequencing, sensor calibration, and BLE connectivity. It wrote the test firmware for the actual DUT and a series of hardware drivers that ran on the host PC for the test breakout, simulating inputs and outputs for every sensor on the system, including Lura's specialised outboard sensors. What would have taken their team weeks of manual scripting was running the same day.

Every unit gets validated automatically before it ships. The code BootLoop generated exercises every device's firmware and hardware through every scenario: cold boot, sensor drift under thermal load, BLE reconnection after signal loss. BootLoop's test suite exercises the firmware hard enough to surface these before production, not after a device reaches a patient.

Their engineers stopped configuring bench equipment by hand. BootLoop's CLI automation interface eliminated the manual setup that was eating hours out of every engineer's week. Their team went from wrestling with test equipment to reviewing results.

Results

• 10 hours/week saved per engineer across Lura's firmware team. A lean team operating with the throughput of a department three times its size.

• Shipping timeline accelerated by weeks. The EOL rig was operational in hours, pulling the release schedule forward and giving Lura breathing room on their FDA submission window.

• Auditable, reproducible validation. For a medical device headed toward FDA authorisation, exhaustive per-unit validation is not optional. BootLoop gave Lura automated testing they can audit and reproduce for every production run.

"Our firmware team is only one person. BootLoop gave us testing infrastructure that would normally take a dedicated test engineering hire months to build. We had it running the same week"

Bryan McLaughlin, Chief Technology Officer, Lura Health

If your team is hand-scripting EOL validation, you are leaving hours on the table every week.

Lura Health went from manual test scripts to automated, production-line firmware validation in hours. BootLoop handles the rest.