-
Notifications
You must be signed in to change notification settings - Fork 3k
TF-M: Switch to vanilla TF-M's OS wrapper #14396
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
Conversation
@LDong-Arm, 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.
Looks good
CI started |
Jenkins CI Test : ❌ FAILEDBuild Number: 1 | 🔒 Jenkins CI Job | 🌐 Logs & ArtifactsCLICK for Detailed Summary
|
Jenkins CI Test : ❌ FAILEDBuild Number: 2 | 🔒 Jenkins CI Job | 🌐 Logs & ArtifactsCLICK for Detailed Summary
|
@LDong-Arm looks like we may have some genuine failures... |
See my comment in another PR: #14362 (comment) |
Jenkins CI Test : ✔️ SUCCESSBuild Number: 3 | 🔒 Jenkins CI Job | 🌐 Logs & ArtifactsCLICK for Detailed Summary
|
needs: preceding PR set for now. Let us know once it's ready |
Previous, we patched TF-M to replace its OS wrapper with CMSIS RTOS to resolve manage management issue when integrated with Mbed OS. But as of TF-M v1.2, the OS wrapper has been reworked in the vanilla TF-M, and now it makes identical calls to its underlying CMSIS RTOS as our patches do. So, we remove our patches and use vanilla TF-M's OS wrapper instead to avoid extra maintenance overhead. This commit re-imports TF-M files associated with the OS wrapper.
The Arm Compiler is case sensitive and unable to distinguish between `Thread.h` from Mbed OS RTOS and `thread.h` from TF-M's OS wrapper, for example. This resolves compilation failures due to wrong includes. To resolve this, use the fully-qualified include paths for the RTOS API.
0ed289f
to
6c405d2
Compare
Pull request has been modified.
b61abe8
to
a6081e5
Compare
CI started |
Jenkins CI Test : ✔️ SUCCESSBuild Number: 4 | 🔒 Jenkins CI Job | 🌐 Logs & ArtifactsCLICK for Detailed Summary
|
Summary of changes
The following PRs are related, we should coordinate to get them in roughly at the same time:
ARMmbed/trusted-firmware-m#16
ARMmbed/tf-m-tests#3
ARMmbed/mbed-os-tf-m-regression-tests#93
#14396
Previous, we patched TF-M to replace its OS wrapper with CMSIS RTOS to resolve manage management issue when integrated with Mbed OS. But as of TF-M v1.2, the OS wrapper has been reworked in the vanilla TF-M, and now it makes identical calls to its underlying CMSIS RTOS as our patches do. So, we remove our patches and use vanilla TF-M's OS wrapper instead to avoid extra maintenance overhead.
Note: The OS wrapper files were imported by ARMmbed/mbed-os-tf-m-regression-tests#93, using ARMmbed/trusted-firmware-m#16 and ARMmbed/tf-m-tests#3.
Impact of changes
This is a kind of refactoring - it has no impact on applications or other parts of Mbed OS.
Migration actions required
None.
Documentation
None.
Pull request type
Test results
Reviewers