Upgrading from Upstream LiteRT
heliaRT is a drop-in replacement for upstream LiteRT for Micro, formerly TensorFlow Lite for Microcontrollers / TFLM. The API surface is identical, so switching requires only changing where the library comes from.
What Changes
| Aspect | Before (upstream LiteRT) | After (heliaRT) |
|---|---|---|
| Source / archive | tensorflow/tflite-micro |
AmbiqAI/helia-rt |
| Additional backend | Reference + CMSIS-NN | Reference + CMSIS-NN + HELIA |
| Build variants | Single | SPEED and SIZE |
| Toolchain support | GCC, armclang | GCC, armclang, ATfE |
| Ambiq-specific tuning | None | heliaCORE kernel paths |
What Stays the Same
.tflitemodel format — no retraining or re-quantization neededMicroInterpreterlifecycle (AllocateTensors→Invoke→ read output)MicroMutableOpResolverregistration pattern- Tensor arena sizing and static memory planning
- All upstream Reference and CMSIS-NN kernels remain available
Step-by-Step: Zephyr
Replace the upstream LiteRT module with heliaRT in your west.yml:
# west.yml — projects:
- name: helia-rt
url: https://github.com/AmbiqAI/helia-rt
revision: main # or pin to a release tag
path: modules/lib/helia-rt
Update prj.conf:
Download the latest release archive from GitHub Releases and point your west.yml at the extracted directory. See the Zephyr getting-started guide for details.
Step-by-Step: Makefile / Source Build
-
Clone heliaRT instead of upstream LiteRT:
-
Build with the HELIA backend:
-
Link the resulting
libtensorflow-microlite.ainto your project exactly as before.
Step-by-Step: neuralSPOT
neuralSPOT already bundles heliaRT. If you're using ns_autodeploy, you're already on heliaRT — no migration needed.
Verifying the Upgrade
After building, confirm heliaRT is active:
Next Steps
- Why heliaRT — the full pitch
- Kernel Selection — how the backend is chosen at build time
- Operator Coverage — what HELIA adds