Give feedback

How would you rate this Learning Path?

Review frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
Which core should I target when flashing and debugging the firmware?
Use the Cortex-M55 High-Performance (HP) core to orchestrate inference on the Ethos-U85. The steps assume this core for building, flashing, and running the application.
What artifacts should I expect after compiling on the Arm cloud instance?
You’ll have ExecuTorch static libraries and a compiled MobileNetV2 model targeted for the Ethos-U85. These outputs are linked into the mv2_runner firmware project.
After duplicating the Blinky example, which project files need to be updated?
Rename blinky.cproject.yml to mv2_runner.cproject.yml and replace internal references from blinky to mv2_runner. This establishes a new CMSIS project for the application.
Where do I place the provided `main.cpp` and how do I verify it works?
Place main.cpp in the mv2_runner project directory as instructed. When you flash and run the firmware, check the SEGGER RTT console for the printed classification result.
What memory changes are required for the model and runtime to fit?
Increase MRAM allocation for the embedded model (about 3.7 MB) and code (around 800 KB), and provision approximately 7.6 MB of SRAM for inference buffers. Update stack and heap sizes, and the linker script in the CMSIS project accordingly.

Share

Tell others about this Learning Path.

Back
Return to Embedded and Microcontrollers