helia-platforms
helia-platforms is the shared catalog of Ambiq SoC and board facts (cores,
memories, clocks, NPU, debug-probe identifiers) consumed by heliaAOT,
helia-profiler and helia-estimator. Every value carries a provenance record:
the datasheet page, SDK file or measurement it came from, and who checked it.
- Import name:
helia_platforms - CLI entry point:
helia-platforms
Status
Alpha. The built-in data covers apollo3, apollo3p, apollo4l, apollo4p,
apollo510, apollo510b, apollo510L, apollo330P and atomiq110, with their parts
and boards; helia-platforms list prints what it holds. The file format, the
Python API and the CLI may change between 0.x releases.
Linker windows, the regions an SDK's linker scripts declare, are not in this
package. It gives the hardware facts they sit within: physical memory regions,
boot reservations, image slots and the NVM left for an application
(Target.usable_nvm()).
Install
pip install helia-platforms
or, in a uv project, uv add helia-platforms. Python 3.11 or later.
Use
From the CLI:
helia-platforms list
helia-platforms show apollo510_evb # every value with its provenance status
helia-platforms show apollo510_evb --provenance # and the full record under each row
helia-platforms show my_board --overlay my_board.yaml
From Python:
from helia_platforms import resolve
target = resolve("apollo510_evb")
target.soc.id # "apollo510"
target.jlink_device # "AP510NFA-CBR"
target.cpu_mhz() # 96, at the default operating point
target.flash_load_address() # 0x410000
target.placement_ranges() # {"itcm": (0x0, 0x40000), ...}: base and size per region
A private catalog, such as a board of your own, loads over the built-in one
with --overlay on the CLI or load_overlay in Python.
Upgrade notes
- apollo510b_evb's
jlink_deviceisAP510BFA-CBR, the Apollo510B ordering number, which SEGGER lists as its own J-Link device. SEGGER added it in J-Link V8.94 (2025-12-10), so update an older J-Link, or pass the SDK's defaultAP510NFA-CBRyourself.
Development
Requires uv.
uv sync --group dev && uv run pre-commit install && uv run pytest
In the repository:
docs/rfcs/: design RFCs (the model and API are RFC 0002)docs/adr/: architecture decision recordsdocs/research/: source inventoriesHANDOFF.md: current state of in-flight work
See CONTRIBUTING.md to contribute, and report security issues as described
in SECURITY.md.
Metadata
Release files for helia-platforms 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| helia_platforms-0.1.0.tar.gz | 135.1 kB | With provenance | Details for helia_platforms-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| helia_platforms-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for helia_platforms-0.1.0-py3-none-any.whl |
Total release size: 297.5 kB
Release files / helia_platforms-0.1.0.tar.gz
| Download URL | helia_platforms-0.1.0.tar.gz |
|---|---|
| Size | 135.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
14212f1f660e7641db87b0b6238144bbff99b24476ec7e190e3f039636897a98
|
|
BLAKE2b-256 checksum How to use checksums |
8a6b13c9cf4a098b83c08d3f05cff29fc9d154d16a2e4b3f33206cf7f37d0168
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logRelease files / helia_platforms-0.1.0-py3-none-any.whl
| Download URL | helia_platforms-0.1.0-py3-none-any.whl |
|---|---|
| Size | 162.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0583653555efb3df88c8fe47d6cfe80e57f9db0633de43276af98975b8f639a3
|
|
BLAKE2b-256 checksum How to use checksums |
53db2892c38294c2fb54c38a64683028aef00ee916db65f6e751596b19616fa2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logSecurity for helia-platforms 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for helia_platforms-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.