Docs: Rearrange TF-M building instructions
- move the building instructios to a dedicated folder, reflecting main TOC
- adjust links in the documentation
Signed-off-by: Anton Komlev <anton.komlev@arm.com>
Change-Id: I335de95061938d619a47cd813020121809e1459b
diff --git a/docs/integration_guide/index.rst b/docs/integration_guide/index.rst
index 703c4f7..b68558c 100644
--- a/docs/integration_guide/index.rst
+++ b/docs/integration_guide/index.rst
@@ -23,12 +23,12 @@
*****************
How to build TF-M
*****************
-Follow the :doc:`Build instructions </technical_references/instructions/tfm_build_instruction>`.
+Follow the :doc:`Build instructions </building/tfm_build_instruction>`.
********************************************************
How to export files for building non-secure applications
********************************************************
-Explained in the :doc:`Build instructions </technical_references/instructions/tfm_build_instruction>`.
+Explained in the :doc:`Build instructions </building/tfm_build_instruction>`.
*************************
How to add a new platform
diff --git a/docs/integration_guide/os_migration_guide_armv8m.rst b/docs/integration_guide/os_migration_guide_armv8m.rst
index 198df9d..8c5b400 100644
--- a/docs/integration_guide/os_migration_guide_armv8m.rst
+++ b/docs/integration_guide/os_migration_guide_armv8m.rst
@@ -17,7 +17,7 @@
- If the OS manipulates directly the Link Register, the default Link Register
value used in Handler mode transitions needs to be differentiated between
Secure and Non Secure builds, i.e. ``0xFD`` and ``0xBC``, respectively.
-- If the OS manages the non-secure client identification, pelase check the
+- If the OS manages the non-secure client identification, please check the
:doc:`Non-secure Client Extension Integration Guide </integration_guide/non-secure_client_extension_integration_guide>`.
--------------
diff --git a/docs/integration_guide/platform/porting_TFM_to_a_new_hardware.rst b/docs/integration_guide/platform/porting_TFM_to_a_new_hardware.rst
index 1a5f63b..e7a330d 100644
--- a/docs/integration_guide/platform/porting_TFM_to_a_new_hardware.rst
+++ b/docs/integration_guide/platform/porting_TFM_to_a_new_hardware.rst
@@ -19,7 +19,7 @@
======================
Make sure you have a working build environnement and that you can build
TF-M on AN521 following the
-:doc:`Build instructions </technical_references/instructions/tfm_build_instruction>`.
+:doc:`Build instructions </building/tfm_build_instruction>`.
Toolchains and software requirements
====================================
@@ -59,7 +59,7 @@
#. Running the regression tests
- - See :doc:`Running TF-M on Arm platforms </technical_references/instructions/run_tfm_examples_on_arm_platforms>`
+ - See :doc:`Running TF-M on Arm platforms </building/run_tfm_examples_on_arm_platforms>`
as an example
diff --git a/docs/integration_guide/services/tfm_attestation_integration_guide.rst b/docs/integration_guide/services/tfm_attestation_integration_guide.rst
index 244ed5d..0bd907d 100644
--- a/docs/integration_guide/services/tfm_attestation_integration_guide.rst
+++ b/docs/integration_guide/services/tfm_attestation_integration_guide.rst
@@ -625,9 +625,9 @@
- Build TF-M with any of the ``ConfigRegression*.cmake`` build configurations
for MPS2 AN521 platform. More info in
- :doc:`tfm_build_instruction </technical_references/instructions/tfm_build_instruction>`.
+ :doc:`tfm_build_instruction </building/tfm_build_instruction>`.
- Lunch FVP model in DS-5. More info in
- :doc:`Run TF-M examples on Arm platforms </technical_references/instructions/run_tfm_examples_on_arm_platforms>`.
+ :doc:`Run TF-M examples on Arm platforms </building/run_tfm_examples_on_arm_platforms>`.
- Set a breakpoint in ``test/secure_fw/suites/attestation/attest_token_test.c``
in ``decode_test_internal(..)`` after the ``token_main_alt(..)`` returned,
i.e. on line 859. Execute the code in the model until the breakpoint hits