Arm backend: Move zephyr example to zephyr/samples folder

Move zephyr example from examples/arm/zephyr to zephyr/samples folder

Signed-off-by: Zingo Andersen <Zingo.Andersen@arm.com>
Change-Id: Ic16cb567ddbd0fbddb3906fb002a4bac5631b847

Author: zingo

.lintrunner.toml

@@ -265,6 +265,8 @@ exclude_patterns = [
     'kernels/portable/cpu/op_lt.cpp',
     'kernels/portable/cpu/op_ne.cpp',
     'runtime/kernel/thread_parallel_interface.h',
+    # Zephyr sample application can use std::vector in the sample code
+    'zephyr/samples/**',
     'scripts/**',
     'third-party/**',
     'util/**',

zephyr/README.md

@@ -2,7 +2,7 @@
 
 **ExecuTorch** is PyTorch's unified solution for deploying AI models on-device—from smartphones to microcontrollers—built for privacy, performance, and portability. It powers Meta's on-device AI across **Instagram, WhatsApp, Quest 3, Ray-Ban Meta Smart Glasses**, and [more](https://docs.pytorch.org/executorch/main/success-stories.html).
 
-This folder adds ExecuTorch so it can be build and run in the Zephyr project as a external module. This includes an example under examples/arm/zephyr of running executor runners with Arm® Ethos™-U backend on a Corstone™ FVP, targeting the Zephyr RTOS.
+This folder adds ExecuTorch so it can be build and run in the Zephyr project as a external module. This includes an example under zephyr/samples/hello-executorch of running executor runners with Arm® Ethos™-U backend on a Corstone™ FVP, targeting the Zephyr RTOS.
 
 # Requirements
 
@@ -113,7 +113,7 @@ export ARMFVP_EXTRA_FLAGS="-C mps3_board.uart0.shutdown_on_eot=1 -C ethosu.num_m
 Prepare the Ethos-U55 PTE model
 <!-- RUN test_ethos-u55_generate_pte -->
 ```
-python -m modules.lib.executorch.examples.arm.aot_arm_compiler --model_name=modules/lib/executorch/examples/arm/example_modules/add.py --quantize --delegate -t ethos-u55-128 --output=add_u55_128.pte
+python -m modules.lib.executorch.examples.arm.aot_arm_compiler --model_name=modules/lib/executorch/zephyr/samples/hello-executorch/models/add.py --quantize --delegate --target=ethos-u55-128 --output=add_u55_128.pte
 ```
 
 `--delegate` tells the aot_arm_compiler to use Ethos-U backend and `-t ethos-u55-128` specify the used Ethos-U variant and numbers of macs used, this must match you hardware or FVP config.
@@ -123,7 +123,7 @@ python -m modules.lib.executorch.examples.arm.aot_arm_compiler --model_name=modu
 Run the Ethos-U55 PTE model
 <!-- RUN test_ethos-u55_build_and_run -->
 ```
-west build -b mps3/corstone300/fvp modules/lib/executorch/examples/arm/zephyr -t run -- -DET_PTE_FILE_PATH=add_u55_128.pte
+west build -b mps3/corstone300/fvp modules/lib/executorch/zephyr/samples/hello-executorch -t run -- -DET_PTE_FILE_PATH=add_u55_128.pte
 ```
 
 ### Cortex-M55
@@ -133,7 +133,7 @@ west build -b mps3/corstone300/fvp modules/lib/executorch/examples/arm/zephyr -t
 Prepare the Cortex-M55 PTE model
 <!-- RUN test_cortex-m55_generate_pte -->
 ```
-python -m modules.lib.executorch.examples.arm.aot_arm_compiler --model_name=modules/lib/executorch/examples/arm/example_modules/add.py --quantize --target=cortex-m55+int8 --output=add_m55.pte
+python -m modules.lib.executorch.examples.arm.aot_arm_compiler --model_name=modules/lib/executorch/zephyr/samples/hello-executorch/models/add.py --quantize --target=cortex-m55+int8 --output=add_m55.pte
 ```
 
 `--target=cortex-m55+int8` selects the Cortex-M/CMSIS-NN portable kernel path (no NPU delegation). This produces a `.pte` optimised for Cortex-M55 with INT8 quantisation.
@@ -143,7 +143,7 @@ python -m modules.lib.executorch.examples.arm.aot_arm_compiler --model_name=modu
 Run the Cortex-M55 PTE model
 <!-- RUN test_cortex-m55_build_and_run -->
 ```
-west build -b mps3/corstone300/fvp modules/lib/executorch/examples/arm/zephyr -t run -- -DET_PTE_FILE_PATH=add_m55.pte
+west build -b mps3/corstone300/fvp modules/lib/executorch/zephyr/samples/hello-executorch -t run -- -DET_PTE_FILE_PATH=add_m55.pte
 ```
 
 ## Corstone&trade; 320 FVP (Ethos&trade;-U85)
@@ -168,7 +168,7 @@ export ARMFVP_EXTRA_FLAGS="-C mps4_board.uart0.shutdown_on_eot=1 -C mps4_board.s
 Prepare the Ethos-U85 PTE model
 <!-- RUN test_ethos-u85_generate_pte -->
 ```
-python -m modules.lib.executorch.examples.arm.aot_arm_compiler --model_name=modules/lib/executorch/examples/arm/example_modules/add.py --quantize --delegate -t ethos-u85-256 --output=add_u85_256.pte
+python -m modules.lib.executorch.examples.arm.aot_arm_compiler --model_name=modules/lib/executorch/zephyr/samples/hello-executorch/models/add.py --quantize --delegate --target=ethos-u85-256 --output=add_u85_256.pte
 ```
 
 `--delegate` tells the aot_arm_compiler to use Ethos-U backend and `-t ethos-u85-256` specify the used Ethos-U variant and numbers of macs used, this must match you hardware or FVP config.
@@ -178,7 +178,7 @@ python -m modules.lib.executorch.examples.arm.aot_arm_compiler --model_name=modu
 Run the Ethos-U85 PTE model
 <!-- RUN test_ethos-u85_build_and_run -->
 ```
-west build -b mps4/corstone320/fvp modules/lib/executorch/examples/arm/zephyr -t run -- -DET_PTE_FILE_PATH=add_u85_256.pte
+west build -b mps4/corstone320/fvp modules/lib/executorch/zephyr/samples/hello-executorch -t run -- -DET_PTE_FILE_PATH=add_u85_256.pte
 ```
 
 ## STM Nucleo n657x0_q
@@ -210,7 +210,7 @@ export PATH=$PATH:~/STMicroelectronics/STM32Cube/STM32CubeProgrammer/bin
 
 Prepare the Cortex-M55 PTE model
 ```
-python -m modules.lib.executorch.examples.arm.aot_arm_compiler --model_name=modules/lib/executorch/examples/arm/example_modules/add.py --quantize --target=cortex-m55+int8 --output=add_m55.pte
+python -m modules.lib.executorch.examples.arm.aot_arm_compiler --model_name=modules/lib/executorch/zephyr/samples/hello-executorch/models/add.py --quantize --target=cortex-m55+int8 --output=add_m55.pte
 ```
 
 `--target=cortex-m55+int8` selects the Cortex-M/CMSIS-NN portable kernel path (no NPU delegation).
@@ -219,7 +219,7 @@ python -m modules.lib.executorch.examples.arm.aot_arm_compiler --model_name=modu
 
 Run the Cortex-M55 PTE model
 ```
-west build -b nucleo_n657x0_q modules/lib/executorch/examples/arm/zephyr -- -DET_PTE_FILE_PATH=add_m55.pte
+west build -b nucleo_n657x0_q modules/lib/executorch/zephyr/samples/hello-executorch -- -DET_PTE_FILE_PATH=add_m55.pte
 west flash
 ```
 This will run the simple add model on your hardware one and print the output on the serial consol.

examples/arm/zephyr/CMakeLists.txt …/samples/hello-executorch/CMakeLists.txtexamples/arm/zephyr/CMakeLists.txt renamed to zephyr/samples/hello-executorch/CMakeLists.txt examples/arm/zephyr/CMakeLists.txt renamed to zephyr/samples/hello-executorch/CMakeLists.txt

@@ -0,0 +1,30 @@
+# Copyright 2026 Arm Limited and/or its affiliates.
+#
+# This source code is licensed under the BSD-style license found in the
+# LICENSE file in the root directory of this source tree.
+#
+# Example of an external model for the Arm AOT Compiler
+#
+# Example of an external Python file to be used as a module by the `run.sh`
+# (and the `aot_arm_compiler.py`) scripts in `examples/arm` directory.
+#
+# Just pass the path of the `add.py` file as `--model_name`
+#
+# These two variables are picked up by the `aot_arm_compiler.py` and used:
+# `ModelUnderTest` should be a `torch.nn.module` instance.
+# `ModelInputs` should be a tuple of inputs to the forward function.
+#
+
+import torch
+
+
+class myModelAdd(torch.nn.Module):
+    def __init__(self):
+        super().__init__()
+
+    def forward(self, x):
+        return x + x
+
+
+ModelUnderTest = myModelAdd()
+ModelInputs = (torch.ones(5),)

examples/arm/zephyr/Kconfig zephyr/samples/hello-executorch/Kconfigexamples/arm/zephyr/Kconfig renamed to zephyr/samples/hello-executorch/Kconfig

@@ -28,7 +28,7 @@ CONFIG_EXECUTORCH_BUILD_PORTABLE_OPS=n
 # and use the hardware instance exposed by the board DTS is controlled with
 # CONFIG_ETHOS_U=y
 # This is handled in board specific .conf files, e.g.:
-# examples/arm/zephyr/boards/mps4_corstone320_fvp.conf
+# zephyr/samples/hello-executorch/boards/mps4_corstone320_fvp.conf
 # To be able to build the example for different HW, in your own project you can
 # copy the relevant lines from those files into your own prj.conf
 

…/zephyr/boards/mps3_corstone300_fvp.conf …cutorch/boards/mps3_corstone300_fvp.confexamples/arm/zephyr/boards/mps3_corstone300_fvp.conf renamed to zephyr/samples/hello-executorch/boards/mps3_corstone300_fvp.conf examples/arm/zephyr/boards/mps3_corstone300_fvp.conf renamed to zephyr/samples/hello-executorch/boards/mps3_corstone300_fvp.conf

@@ -22,7 +22,7 @@
 #include <zephyr/sys/printk.h>
 #include <cstring>
 #include <memory>
-#include <vector>
+#include <vector> /* @lint-ignore NOSTDINC */
 
 /**
  * This header file is generated by the build process based on the .pte file
@@ -84,9 +84,8 @@ unsigned char __attribute__((
  * For Shared_Sram, ET_ARM_BAREMETAL_SCRATCH_TEMP_ALLOCATOR_POOL_SIZE is
  * 2MB and the linker script places the .bss.tensor_arena symbol in the SRAM.
  * For Dedicated_Sram, the .bss.tensor_arena symbol is placed in the DDR in the
- * linker script. The examples/arm/zephyr/prj.conf contains the logic for the
- * sizes of:
- * CONFIG_EXECUTORCH_METHOD_ALLOCATOR_POOL_SIZE and
+ * linker script. The zephyr/samples/hello-executorch/prj.conf contains the
+ * logic for the sizes of: CONFIG_EXECUTORCH_METHOD_ALLOCATOR_POOL_SIZE and
  * CONFIG_EXECUTORCH_TEMP_ALLOCATOR_POOL_SIZE
  */