michaelh/zephyr
1
0
Fork 0
Code Releases Activity

doc: Update TF-M documentation to match current TF-M version

Browse source 
Update TF-M documentation to match the current integrated TF-M version.
Include mention of the Platform secure partition that can be enabled.

Signed-off-by: Joakim Andersson <joakim.andersson@nordicsemi.no>
This commit is contained in:
Joakim Andersson 2021-11-04 16:04:24 +01:00 • committed by Carles Cufí
commit ba85663a42
2 changed files with 4 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

5
doc/guides/tfm/overview.rst
View file

@ -8,7 +8,7 @@ It defines and implements an architecture and a set of software components
that aim to address some of the main security concerns in IoT products.
Zephyr RTOS has been PSA Certified since Zephyr 2.0.0 with TF-M 1.0, and
is currently integrated with TF-M 1.3.0.
is currently integrated with TF-M 1.4.1.
What Does TF-M Offer?
*********************
@ -196,12 +196,13 @@ within a default Zephyr west workspace.)
Secure Services
---------------
As of TF-M 1.3.0, the following secure services are available:
As of TF-M 1.4.1, the following secure services are generally available (although vendor support may vary):
* Audit Logging (Audit)
* Crypto (Crypto)
* Firmware Update (FWU)
* Initial Attestation (IAS)
* Platform (Platform)
* Secure Storage, which has two parts:
* Internal Trusted Storage (ITS)

2
samples/tfm_integration/psa_protected_storage/README.rst
View file

@ -17,7 +17,7 @@ Using the PS API, this sample stores data to non-volatile storage. The sample sh
be stored to and read from UIDs, and how overwrite protection can be enabled using flags.
TF-M includes a maximum number of PS records, set via ``PS_NUM_ASSETS`` (default 10 as of
TF-M 1.3), and a maximum record size, set via ``PS_MAX_ASSET_SIZE`` (default of 2048 as of
TF-M 1.3.0), and a maximum record size, set via ``PS_MAX_ASSET_SIZE`` (default of 2048 as of
TF-M 1.3.0). These defaults may be different depending on the platform being used, the current
value will be printed by the build system during the TF-M compilation step.