Skip to content

Configuration Options for different hardware and compiler toolchains #11

Closed

Description

@ReinhardKeil

https://github.com/Arm-Examples/CMSIS-Executorch/blob/main/model/aot_model.py#L26 uses different configuration options for Ethos hardware:

  • These options should be documented.
  • Options should be configurable in a consistent way and potentially exported from the IDE project

https://github.com/Arm-Examples/CMSIS-Executorch/blob/main/.docker/Dockerfile uses GCC.

  • Compiler toolchain should be configurable to ATfE (CLANG) and potentially exported from the IDE project

Activity

  1. MatthiasHertelArm commented on Oct 6, 2026

    @MatthiasHertelArm
    Contributor

    Addressed by the three-step flow on main:

    • 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).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions