Modules
An NSX app is a thin project plus the modules it depends on. The registry pins each module to
a project and a revision, and every module ships an nsx-module.yaml manifest declaring its
type, what it provides, what it depends on, and which boards, SoCs and toolchains it is
compatible with. These pages are generated from exactly that data, so they report what
nsx module list and nsx module describe report.
The registry pins 50 modules across 7 types, and NSX ships 17 board descriptors covering 11 SoCs.
Start here
Section titled “Start here”Module types
Section titled “Module types”Every module declares one type. The type is what decides where a module sits in an app: a board or SoC module supplies a target, an SDK provider supplies the vendor SDK, and the rest are the libraries an app actually calls.
Adding a module
Section titled “Adding a module”Every module page carries the command that adds it to an app, and nsx resolves the
dependency closure from the same manifests:
nsx module add nsx-audioThe snapshot the pages are built from is published at /neuralspotx/modules/catalog.json.