-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Mbed-OS build fails for LPC546XX and FF_LPC546XX targets with ARM Compiler 6.11 #9402
Labels
Comments
Tagging @ARMmbed/team-nxp |
Adding - @OPpuolitaival @deepikabhavnani @kjbracey-arm |
Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-673 |
@mmahadevan108 - Thanks for your quick response on this. I'll go ahead close this now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Mbed OS will be upgrading to ARMc6 Toolchain with upcoming releases(Currently we are using ARM Compiler 5). We are in the process of ensuring that all currently supported targets successfully compiles/passes tests with ARMC6 toolchain but we do have some targets currently failing the build with ARMc6 toolchain. The failures are in source code under targets folder and thus needs to be updated.
Please notice that __align() needs to be updated/changed to use ARMc6 equivalent in fsl_common.h header files.
Targets Affected: LPC546XX, FF_LPC546XX
Toolchain used: ARM Compiler 6.11 (Version 6.11)
Note that there may be other changes required to make build successful for ARMc6, so please address them as well.
How to reproduce the issue?
mbed config --global ARMC6_PATH
Note that you may see an "Error" when trying to use ARMc6 with "mbed compile". This is expected, but the compilation process should continue to proceed. We will be removing this Error/Warning once we switch to ARMc6 completely.
How to generate Pull Request to fix ARMc6 issues?
Please generate your pull requests addressing ARMc6 build issues with feature-armc6 as the target branch(not master branch).
Issue request type
The text was updated successfully, but these errors were encountered: