Board matrix

NSX ships 17 board descriptors. Each one is a board.yaml in the package, and the order below is the order nsx board list uses.

Boards

Board	SoC	Tier	SDK provider	CPU	ABI	Toolchains
`apollo2_evb`	apollo2	evb	ambiqsuite	cortex-m4	thumbv7em-fpv4sp-hard	arm-none-eabi-gcc
`apollo3_evb`	apollo3	evb	ambiqsuite	cortex-m4	thumbv7em-fpv4sp-hard	arm-none-eabi-gcc
`apollo3_evb_cygnus`	apollo3	evb	ambiqsuite	cortex-m4	thumbv7em-fpv4sp-hard	arm-none-eabi-gcc
`apollo3p_evb`	apollo3p	evb	ambiqsuite	cortex-m4	thumbv7em-fpv4sp-hard	arm-none-eabi-gcc
`apollo3p_evb_cygnus`	apollo3p	evb	ambiqsuite	cortex-m4	thumbv7em-fpv4sp-hard	arm-none-eabi-gcc
`apollo4l_evb`	apollo4l	evb	ambiqsuite	cortex-m4	thumbv7em-fpv4sp-hard	arm-none-eabi-gcc, atfe
`apollo4l_blue_evb`	apollo4l	evb	ambiqsuite	cortex-m4	thumbv7em-fpv4sp-hard	arm-none-eabi-gcc, atfe
`apollo4p_evb`	apollo4p	evb	ambiqsuite	cortex-m4	thumbv7em-fpv4sp-hard	arm-none-eabi-gcc
`apollo4p_blue_kbr_evb`	apollo4p	evb	ambiqsuite	cortex-m4	thumbv7em-fpv4sp-hard	arm-none-eabi-gcc
`apollo4p_blue_kxr_evb`	apollo4p	evb	ambiqsuite	cortex-m4	thumbv7em-fpv4sp-hard	arm-none-eabi-gcc
`apollo4p_evb_disp_shield_rev2`	apollo4p	evb	ambiqsuite	cortex-m4	thumbv7em-fpv4sp-hard	arm-none-eabi-gcc
`apollo5b_evb`	apollo5b	evb	ambiqsuite	cortex-m55	thumbv8.1m-fpv5-hard	arm-none-eabi-gcc, armclang, atfe
`apollo510_evb`	apollo510	evb	ambiqsuite	cortex-m55	thumbv8.1m-fpv5-hard	arm-none-eabi-gcc, armclang, atfe
`apollo510b_evb`	apollo510b	evb	ambiqsuite	cortex-m55	thumbv8.1m-fpv5-hard	arm-none-eabi-gcc, armclang, atfe
`apollo330mP_evb`	apollo330P	evb	ambiqsuite	cortex-m55	thumbv8.1m-fpv5-hard	arm-none-eabi-gcc, armclang, atfe
`apollo510dL_evb`	apollo510L	evb	ambiqsuite	cortex-m55	thumbv8.1m-fpv5-hard	arm-none-eabi-gcc, armclang, atfe
`atomiq110_fpga_turbo`	atomiq110	fpga	ambiqsuite	cortex-m55	thumbv8.1m-fpv5-hard	arm-none-eabi-gcc, armclang, atfe

SoC families

The registry groups SoCs into families. A family names the SDK provider module and the project revision the family is pinned to, and the modules an app on that family resolves by default.

SoC	Provider module	Project	Revision	Family modules
apollo2	`nsx-ambiqsuite`	nsx-ambiq-sdk	v5.2.26	nsx-ambiqsuite, nsx-ambiq-hal, nsx-ambiq-bsp, nsx-soc-hal, nsx-cmsis-startup
apollo3	`nsx-ambiqsuite`	nsx-ambiq-sdk	v5.2.26	nsx-ambiqsuite, nsx-ambiq-hal, nsx-ambiq-bsp, nsx-soc-hal, nsx-cmsis-startup
apollo330P	`nsx-ambiqsuite`	nsx-ambiq-sdk	v5.2.26	nsx-ambiqsuite, nsx-ambiq-hal, nsx-ambiq-bsp, nsx-soc-hal, nsx-cmsis-startup
apollo3p	`nsx-ambiqsuite`	nsx-ambiq-sdk	v5.2.26	nsx-ambiqsuite, nsx-ambiq-hal, nsx-ambiq-bsp, nsx-soc-hal, nsx-cmsis-startup
apollo4l	`nsx-ambiqsuite`	nsx-ambiq-sdk	v5.2.26	nsx-ambiqsuite, nsx-ambiq-hal, nsx-ambiq-bsp, nsx-soc-hal, nsx-cmsis-startup
apollo4p	`nsx-ambiqsuite`	nsx-ambiq-sdk	v5.2.26	nsx-ambiqsuite, nsx-ambiq-hal, nsx-ambiq-bsp, nsx-soc-hal, nsx-cmsis-startup
apollo510	`nsx-ambiqsuite`	nsx-ambiq-sdk	v5.2.26	nsx-ambiqsuite, nsx-ambiq-hal, nsx-ambiq-bsp, nsx-soc-hal, nsx-cmsis-startup
apollo510L	`nsx-ambiqsuite`	nsx-ambiq-sdk	v5.2.26	nsx-ambiqsuite, nsx-ambiq-hal, nsx-ambiq-bsp, nsx-soc-hal, nsx-cmsis-startup
apollo510b	`nsx-ambiqsuite`	nsx-ambiq-sdk	v5.2.26	nsx-ambiqsuite, nsx-ambiq-hal, nsx-ambiq-bsp, nsx-soc-hal, nsx-cmsis-startup
apollo5b	`nsx-ambiqsuite`	nsx-ambiq-sdk	v5.2.26	nsx-ambiqsuite, nsx-ambiq-hal, nsx-ambiq-bsp, nsx-soc-hal, nsx-cmsis-startup
atomiq110	`nsx-ambiqsuite`	nsx-ambiq-sdk	v5.2.26	nsx-ambiqsuite, nsx-ambiq-hal, nsx-ambiq-bsp, nsx-soc-hal, nsx-cmsis-startup

Board modules

Each board is also a module, so an app depends on its board the same way it depends on anything else. The registry pins 17 of them: