doc: tfm: Improve documentation of non-secure firmware image

Explain when the TF-M nonsecure firmware image is used. Use non-secure consistently instead of nonsecure or ns. Signed-off-by: Joakim Andersson <[email protected]>
zephyrbot · Mar 9, 2022 · 84d15bb · 84d15bb
1 parent 3191191
commit 84d15bb
Showing 1 changed file with 5 additions and 2 deletions.
diff --git a/doc/guides/tfm/build.rst b/doc/guides/tfm/build.rst
@@ -23,7 +23,7 @@ Images Created by the TF-M Build
 The TF-M build system creates the following executable files:
 
 * tfm_s - TF-M secure firmware
-* tfm_ns - a nonsecure app which is discarded in favor of the Zephyr app
+* tfm_ns - TF-M non-secure app (only used by regression tests).
 * bl2 - TF-M MCUboot, if enabled
 
 For each of these, it creates .bin, .hex, .elf, and .axf files.
@@ -37,7 +37,10 @@ file which combines them:
 
 For each of these, only .bin files are created.
 
-The Zephyr build system usually signs both tfm_s and the Zephyr ns app itself.
+The TF-M non-secure app is discarded in favor of Zephyr non-secure app except
+when running the TF-M regression test suite.
+
+The Zephyr build system usually signs both tfm_s and the Zephyr non-secure app itself.
 See below for details.
 
 The 'tfm' target contains properties for all these paths.