-
Notifications
You must be signed in to change notification settings - Fork 3k
Additions to TF-M source integration #9772
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
@mikisch81, thank you for your changes. |
"value": 20 | ||
}, | ||
"message_pool_size": { | ||
"help": "maximum number of RoT services allowed", |
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.
help - typo? same as previous one
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.
fixed
} | ||
} | ||
"name": "tfm-s", | ||
"macros": ["MBED_FAULT_HANDLER_DISABLED", "BYPASS_NVSTORE_CHECK=1"] |
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.
Is it appropriate to disable the fault handler in a library? I looked for a justification for this change in the commit message but I didn't find one.
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.
when building TFM we are not using parts of mbed-os
Some of those parts are the fault handlers, and this is because TFM implements their own
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.
Good enough for me!
@ARMmbed/mbed-os-maintainers can this start CI please ? |
} | ||
} | ||
"name": "tfm-s", | ||
"macros": ["MBED_FAULT_HANDLER_DISABLED", "BYPASS_NVSTORE_CHECK=1"] |
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.
Good enough for me!
CI started |
Test run: SUCCESSSummary: 12 of 12 test jobs passed |
@0xc0170 , this has now passed CI, please re-review the fix for your comments so this can be "ready" |
], | ||
"config": { | ||
"level": { | ||
"help": "TFM security level", |
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.
What is this suppose to mean?
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.
This is one TFM properties
security level is corresponding with PSA memory separation level desired
This is an internal TFM config, and a prep for the future when we will have a greater level of memory separation.
Added another commit which was cherry-picked from #9221. |
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.
It's generally ok since I've already reviewed these files. However, my understanding is these scripts are scraping addresses from a flash_layout.h
file. We do not scrape info from source files in Mbed OS. We use the configuration system for this and then generate the macros that can be used in the code base. If the intention is to reuse these scripts across targets, I think this needs to be revisited in the future.
if m is not None: | ||
ramLoadAddress = int(m.group(1), 0) | ||
print("**[INFO]** Writing load address from the macro in " | ||
"flash_layout.h to the image header.. " |
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.
In the future, if this script is going to be reused by other targets, we should be moving "configuration" into the targets.json
/mbed_lib.json
, not scraping it from the flash_layout.h
file.
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.
I absolutely agree, this is something we are aware of and will try to use this in the Musca PR
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.
@mikisch81 @orenc17 Can y'all make and link a Jira issue so that we don't lose this conversation?
We'll start CI in the meanwhile.
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.
@cmonr @bridadan @orenc17 @alzix Created IOTSEC-1104 for that.
CI started |
Test run: SUCCESSSummary: 12 of 12 test jobs passed |
Description
Pull request type
Reviewers
@orenc17
Release Notes