-
Notifications
You must be signed in to change notification settings - Fork 3k
M2351: Support IAR #12353
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
M2351: Support IAR #12353
Conversation
1. On M2351, SYS/CLK registers are hard-wired to secure. Define MBED_TZ_DEFAULT_ACCESS to 1 so that all non-secure user threads have access to call secure functions to control these registers. 2. MBED_TZ_DEFAULT_ACCESS is only meaningful for non-secure target. Define it only for non-secure target in targets.json. 3. On TFM target, MBED_TZ_DEFAULT_ACCESS has defined in mbed_lib.json. Avoid duplicate definition which IAR assembler doesn't allow.
1. Enable IAR on non-secure targets 2. Disable IAR on secure targets because: (1) IAR toolchain bug: As of IAR 8.32, cmse_nonsecure_caller() is not always inlined. (2) TFM hasn't supported IAR yet.
@ccli8, thank you for your changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
CI started |
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
Not related to this PR, I am looking for an offender. Build failed, but not visible in the PR itself. There are errors:
I saw this in another PR today, I am now looking at offender. Looks like CI failed to report correct status and master might have an issue. cc @ARMmbed/mbed-os-test |
Summary of changes
This PR adds support for IAR toolchain on M2351 targets:
cmse_nonsecure_caller()
is not always inlined.Pull request type
Test results