Getting started

For model deployment, start with heliaAOT or heliaRT. Both use heliaCORE for supported operations. heliaAOT is the recommended starting point for latency, power, and memory efficiency. Choose heliaRT when you want an optimized LiteRT for Microcontrollers runtime integration.

These guides are for developers integrating kernels directly into firmware or a custom runtime. Start with Requirements, choose one integration below, then run your first kernel.

1. Requirements→

Check your target, compiler, and build prerequisites.

2. Integration→

Add the library through your project’s build system.

3. First kernel→

Execute a small example and check its output.

Before you begin

Have a board application that you can already build, flash, and debug. These guides add heliaCORE to that application; your board SDK continues to provide startup code, device support, and the linker configuration.

Choose a source build if you need custom operator selection or compiler settings. A prebuilt library is suitable when its target, compiler, ABI, and kernel features match your application. Requirements explains how to check.

Choose an integration

Use the guide that matches the build system already in your project. These are alternative paths; you do not need to complete all four.

CMake→

Link a prebuilt package or build from source with the operator groups and data types you select.

CMSIS-Pack→

Add the Ambiq component through your IDE or CMSIS tooling, using source or prebuilt kernels.

Zephyr→

Add the module to your workspace and configure kernel support through Kconfig.

neuralSPOT-X→

Use the SDK’s existing heliaCORE integration and verify the dependency and target settings.

For a custom CMake firmware project, start with CMake. If your SDK already supplies heliaCORE, use its integration instead of adding a second copy.

Verify execution

The integration guides check that the headers and library are part of your build. First kernel adds a small activation example with an expected result so you can check execution on your target. At the end, your application should build with one matching set of heliaCORE headers and kernels, execute the example, and return the expected result.

From there, use the User guide to select operators, configure data types, and understand acceleration and performance. The API reference documents individual function contracts.