arm: extend CMSIS-Pack smoke test to Cortex-M

[ricardoasouz]

Summary

Extend the CMSIS-Pack smoke consumer to exercise a Cortex-M operator instead of only a Portable operator.

This change:

• adds the CMSIS-NN component to the smoke project;
• selects Cortex-M quantized_add;
  uses ARM::CMSIS-NN@7.0.0 to keep the smoke test on the currently supported CMSIS-NN major version;
• copies the smoke project into a writable container-local directory so the test does not depend on host bind-mount ownership.

This directly exercises the Cortex-M / CMSIS-NN path on the ARMCM55 target.

Testing

python -m pytest \
  backends/arm/cmsis_pack/test/test_generate_register_all_kernels.py \
  backends/arm/cmsis_pack/test/all_ops/test_gen_cproject.py -q

21 passed

DOCKER_IMAGE=ghcr.io/arm-software/avh-mlops/arm-mlops-docker-licensed-community:latest-amd64 \
bash backends/arm/cmsis_pack/test/smoke/run.sh

Build summary: 1 succeeded, 0 failed
=== PASS ===

Related to #14880.

cc @digantdesai @freddan80 @per @zingo @oscarandersson8218 @mansnils @Sebastian-Larsson @robell @rascani

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/22113

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

⚠️ 15 Awaiting Approval

As of commit e42d97b with merge base b8b5e0f ():

AWAITING APPROVAL - The following workflows need approval before CI can run:

• Build CMSIS Pack (gh)
• Build documentation (gh)
• Build Presets (gh)
• Lint (gh)
• periodic (gh)
• pull (gh)
• Test ARM Backend (gh)
• Test CoreML Backend (gh)
• Test Cortex-M Backend (gh)
• Test NXP Backend (gh)
• Test QNN Backend (gh)
• Test QNN Windows MSVC build (gh)
• Test Vulkan Backend (gh)
• Test WebGPU Backend (gh)
• Test XNNPACK Backend (gh)

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[meta-cla]

Hi @ricardoasouz!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: ricardoasouz / name: Ricardo Alves de Souza (e42d97b)

[pytorch-bot]

The following ciflow label(s) have been added but CI has not been triggered yet because the workflows are awaiting approval:

• ciflow/trunk

Once a maintainer approves the workflows (scroll to the bottom of the PR page), the corresponding CI jobs will be triggered automatically. Please ping one of the reviewers if you do not have access to approve and run workflows.

[rascani]

CC @MatthiasHertelArm

[meta-cla]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[ricardoasouz]

@pytorchbot label "release notes: none"