You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Configuration Options for different hardware and compiler toolchains #11
The NPU and Vela configuration lives in the mlops: node of cmsis-executorch.csolution.yml. cbuild setup exports it to *.cbuild-mlops.yml, and create_ai_layer.py passes it to ExecuTorch's EthosUCompileSpec; vela: misc: forwards any further Vela option (Pass every Vela option of the mlops: node to Vela #23). The model parameters (input shape, calibration samples) are under mlops: model: as well (Use the implicit simulator target and model parameters in mlops: #28). It is documented in the README and in documentation/mlops-flow.md.
There is no Docker/GCC library build any more: the runtime is part of the CMSIS build, and the compiler is chosen with cbuild --toolchain. CI builds and runs with AC6, GCC and CLANG (ATfE).
Activity
MatthiasHertelArm commentedon Oct 6, 2026
Addressed by the three-step flow on
main:mlops:node ofcmsis-executorch.csolution.yml.cbuild setupexports it to*.cbuild-mlops.yml, andcreate_ai_layer.pypasses it to ExecuTorch'sEthosUCompileSpec;vela: misc:forwards any further Vela option (Pass every Vela option of the mlops: node to Vela #23). The model parameters (input shape, calibration samples) are undermlops: model:as well (Use the implicit simulator target and model parameters in mlops: #28). It is documented in the README and indocumentation/mlops-flow.md.cbuild --toolchain. CI builds and runs with AC6, GCC and CLANG (ATfE).