Skip to content

Plumbing for Arm Example Runnner to use Zephyr Toolchain #12078

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

BujSet
Copy link
Contributor

@BujSet BujSet commented Jun 27, 2025

Summary

Once setup.sh and PATH have been set to point to Arm Zephyr toolchain, the run.sh script and its child processes must use the specified toolchain. This change adds the plumbing needed to support this. A new file, examples/arm/ethos-u-setup/arm-zephyr-eabi-gcc.cmake is introduced to make the command line options easy and consistent.

Test plan

After picking the changes in this PR, the following can be run to produce the same results as in the Arm Ethos-U tutorial, now utilizing the Arm Zephyr toolchain instead of the bare metal:

examples/arm/run.sh --toolchain=arm-zephyr-eabi-gcc --model_name=add --no_quantize --target=ethos-u55-128

Which still produces the following output:

I [executorch:arm_executor_runner.cpp:747 main()] Model executed successfully.
I [executorch:arm_executor_runner.cpp:751 main()] 1 outputs:
Output[0][0]: (int) 2
Output[0][1]: (int) 2
Output[0][2]: (int) 2
Output[0][3]: (int) 2
Output[0][4]: (int) 2
I [executorch:arm_executor_runner.cpp:874 main()] Program complete, exiting.
I [executorch:arm_executor_runner.cpp:878 main()] ♦
Info: /OSCI/SystemC: Simulation stopped by user.
[warning ][main@0][3440 ns] Simulation stopped by user
[backends/arm/scripts/run_fvp.sh] Simulation complete, 0
Checking for problems in log:
No problems found!
+ set +x

Copy link

pytorch-bot bot commented Jun 27, 2025

🔗 Helpful Links

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

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

❌ 1 New Failure, 2 Cancelled Jobs, 4 Unrelated Failures

As of commit 8b18e8b with merge base 2a2d757 (image):

NEW FAILURE - The following job has failed:

CANCELLED JOBS - The following jobs were cancelled. Please retry:

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

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

@BujSet BujSet self-assigned this Jun 27, 2025
@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jun 27, 2025
@BujSet
Copy link
Contributor Author

BujSet commented Jun 27, 2025

@pytorchbot label "release notes: none"

@pytorch-bot pytorch-bot bot added the release notes: none Do not include this in the release notes label Jun 27, 2025
@BujSet
Copy link
Contributor Author

BujSet commented Jun 27, 2025

@digantdesai @zingo @perheld Similar to the PR here. This PR splits part of the Arm Zephyr cmake Preset PR. This PR relates to the changes need for the run.sh script.

cc @larryliu0820

@BujSet BujSet added ciflow/trunk ciflow/binaries module: arm Issues related to arm backend labels Jun 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ciflow/binaries ciflow/trunk CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. module: arm Issues related to arm backend release notes: none Do not include this in the release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants