-
Notifications
You must be signed in to change notification settings - Fork 974
Zephyr: External module documentation #17653
Copy link
Copy link
Closed
Labels
module: armIssues related to arm backendIssues related to arm backendmodule: microcontrollersFor embedded MCUs like Cortex-M, or RTOS like Zephyr, does not track NPU backend like Arm Ethos.For embedded MCUs like Cortex-M, or RTOS like Zephyr, does not track NPU backend like Arm Ethos.partner: armFor backend delegation, kernels, demo, etc. from the 3rd-party partner, ArmFor backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm
Metadata
Metadata
Assignees
Labels
module: armIssues related to arm backendIssues related to arm backendmodule: microcontrollersFor embedded MCUs like Cortex-M, or RTOS like Zephyr, does not track NPU backend like Arm Ethos.For embedded MCUs like Cortex-M, or RTOS like Zephyr, does not track NPU backend like Arm Ethos.partner: armFor backend delegation, kernels, demo, etc. from the 3rd-party partner, ArmFor backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm
Type
Projects
Status
Done
Status
Done
Submit documentation to the Zephyr external projects/modules registry describing how to integrate ExecuTorch with a Zephyr project. Validate the integration on a single board and provide at least one basic inference sample.
Upstream module acceptance is not on the table (see zephyrproject-rtos/zephyr#92981), so the goal is a well-documented external module path.
cc @digantdesai @SS-JIA @freddan80 @per @zingo @oscarandersson8218 @mansnils @Sebastian-Larsson @robell @psiddh @AdrianLundell