From ce83cc86452f49b28b28366b35e7e5b9e70eb8f7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sebastian=20B=C3=B8e?= Date: Fri, 4 Aug 2023 13:12:40 +0200 Subject: [PATCH] doc: security: Don't document how to flash a TF-M MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Don't document how to flash TF-M as it is the same as for any NCS build. This documentation is expensive to maintain as it is referencing development environment specifics that are unrelated to TF-M and subject to change. Signed-off-by: Sebastian Bøe --- doc/nrf/security/tfm.rst | 9 --------- 1 file changed, 9 deletions(-) diff --git a/doc/nrf/security/tfm.rst b/doc/nrf/security/tfm.rst index 5ccf7cbf463..4b3b489563e 100644 --- a/doc/nrf/security/tfm.rst +++ b/doc/nrf/security/tfm.rst @@ -83,15 +83,6 @@ When :kconfig:option:`CONFIG_TFM_PROFILE_TYPE_MINIMAL` is set, the configurabili Hence, it is not possible to modify the TF-M minimal configuration to create your own variant of the minimal configuration. Instead, the default configuration must be used as a starting point. -Programming -*********** - -The procedure for programming an application with TF-M is the same as for other multi-image applications in |NCS|. - -After building the application, a :file:`merged.hex` file is created that contains MCUboot, TF-M, and the application. -The :file:`merged.hex` file can be then :ref:`programmed using nRF Connect for Visual Studio Code `. -When using the command line, the file is programmed automatically when you call ``ninja flash`` or ``west flash``. - Logging *******