SDK Upstream Model¶
This document describes how the AmbiqSuite SDK is sourced and provisioned for NSX board and SoC modules.
Status: unified
NSX originally planned one upstream repo per AmbiqSuite major line. That
plan has been superseded: all AmbiqSuite SoCs now resolve from a single
unified SDK repo,
nsx-ambiq-sdk, through a
single provider module. The historical per-major plan is summarized at the
end for context.
Current Model¶
One repo, nsx-ambiq-sdk, vendors
the AmbiqSuite drop, the HAL/BSP wrappers, and the shared NSX module set for
every supported SoC (Apollo2 through Apollo5). Stable resolution uses the
immutable v5.2.24 release.
The provider and wrapper modules NSX resolves are thin metadata views onto that one project:
| Provider / wrapper module | Project | Revision |
|---|---|---|
nsx-ambiqsuite |
nsx-ambiq-sdk |
v5.2.24 |
nsx-ambiq-hal |
nsx-ambiq-sdk |
v5.2.24 |
nsx-ambiq-bsp |
nsx-ambiq-sdk |
v5.2.24 |
v5.2.24 is the immutable provenance-correction release titled
nsx-ambiq-sdk 5.2.24 — AmbiqSuite stable-2026.06.18.
Its annotated tag peels to commit
a9f4ec25a162f6f3700623feb691423bb5a51132,
and it preserves the ABI-correct binary HAL/BSP archive payload from
v5.2.23 byte-for-byte. The source tree also carries provenance metadata and
versioned BLE DIS corrections, so its full git content hash is intentionally
new. The correction records the already validated ACfE ABI provenance and fixes 22
stale ACfE manifest hashes; v5.2.23 remains published and immutable.
Board profiles depend on the provider module for their SoC family, and NSX vendors the resolved SDK content into the generated app. See SDK Provider Model for how providers are selected and SDK Provider Selection for the user-facing controls.
Why a Single Repo¶
- one provenance story to explain, audit, and update
- no cross-repo version skew between the SDK drop, HAL/BSP wrappers, and shared module sources
- release lines are selected through module metadata, not through separate upstreams or branch pinning
Apollo510L¶
Apollo510L is exposed through the board name apollo510dL_evb. The unified SDK
provides the CMSIS device files, system source, board headers, and prebuilt
HAL/BSP libraries that board requires.
Historical Plan (superseded)¶
The original intent was one upstream repo per major line, with NSX board
defaults pinned to SDK-aligned release tags (for example r5.2.0):
- an Apollo3 / Apollo3 Plus provider
- an Apollo4 Lite / Apollo4 Plus provider
- an Apollo510 / Apollo510B / Apollo510L / Apollo330P provider
The unified nsx-ambiq-sdk repo replaced this approach, removing the need for
per-major repos and per-release tag pinning.