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 USB connector should I use for the serial console, and what do I need on macOS?
Use the DEBUG USB-C connector on the board. On macOS, install the Silicon Labs USB-to-UART driver and a serial terminal such as picocom (for example, install it with brew install picocom).
Why build ExecuTorch inside a Docker container on macOS?
Building inside a Docker container provides an Ubuntu build environment that matches the toolchains used in this Learning Path, and avoids gaps in macOS-native cross-compilers. The container is only for building and produces prebuilt ExecuTorch libraries and .pte files that you’ll copy to the FRDM i.MX 93.
After installing ExecuTorch, how do I confirm the package is available?
Run pip list | grep executorch and check that executorch appears in the output.
What artifacts must be present before starting the firmware with Linux RemoteProc?
Copy the U65-compiled .pte model and the executor_runner ELF to the board. The runner loads the .pte, prepares buffers, and invokes the NPU or CPU backend on the Cortex-M33.
What output should I expect when the MobileNet V2 model compiles successfully?
The compilation output reports the number of NPU operators and their coverage. For the example MobileNet V2 model, expect an output reporting 100% NPU utilization.

Share

Tell others about this Learning Path.

Back
Return to Embedded and Microcontrollers