doc: ironside: Consolidate release archive info

Programming steps are discussed in the update docs, as that process
is either part of the manual update or provisioning; the latter
being documented elsewhere.

Describing the ZIP archive is expanded into a release deliverable
section and moved into the update context.

Default configurations aren't strictly related to either but are still
important to discuss in general ISE.

Ref: NCSDK-33336

Signed-off-by: Stephen Stauts <stephen.stauts@nordicsemi.no>

Author: kyberdin

doc/nrf/app_dev/device_guides/nrf54h/ug_nrf54h20_ironside.rst

@@ -30,48 +30,34 @@ See the following pages for details on some |ISE| features and subsystems.
 
    ug_nrf54h20_ironside_update
 
-.. _ug_nrf54h20_ironside_se_programming:
+Default policies
+****************
 
-Programming |ISE| on the nRF54H20 SoC
-*************************************
-
-|ISE| is released independently of the |NCS| release cycle and is provided as a ZIP archive that contains the following components:
+By default, |ISE| uses the following memory and access configurations on the nRF54H20 SoC:
 
 .. list-table::
    :header-rows: 1
    :widths: auto
 
-   * - Component
-     - File
-     - Description
-   * - IronSide SE firmware
-     - :file:`ironside_se.hex`
-     - Used when bringing up a new DK and programming both the recovery firmware and |ISE| for the first time.
-   * - IronSide SE update firmware
-     - :file:`ironside_se_update.hex`
-     - Used when updating |ISE|.
-   * - IronSide SE Recovery update firmware
-     - :file:`ironside_se_recovery_update.hex`
-     - The recovery firmware, reserved for future recovery operations. Currently, it does not provide user-facing functionality. Used when updating the recovery firmware.
-   * - Update application
-     - :file:`update_application.hex`
-     - The local domain :zephyr:code-sample:`update application <nrf_ironside_update>` that is used to perform an |ISE| update. See :ref:`ug_nrf54h20_ironside_se_update_manual`.
-
-For instructions on how to program |ISE|, see :ref:`ug_nrf54h20_SoC_binaries`.
-
-By default, the nRF54H20 SoC uses the following memory and access configurations:
-
-* MRAMC configuration: MRAM operates in Direct Write mode with READYNEXTTIMEOUT disabled.
-* MPC configuration: All memory not reserved by Nordic firmware is accessible with read, write, and execute (RWX) permissions by any domain.
-* TAMPC configuration: The access ports (AP) for the local domains are enabled, allowing direct programming of all the memory not reserved by Nordic firmware in the default configuration.
-
+   * - Configuration
+     - Policy
+   * - MRAMC
+     - MRAM operates in Direct Write mode with READYNEXTTIMEOUT disabled.
+   * - MPC
+     - All memory not reserved by Nordic firmware is accessible with read, write, and execute (RWX) permissions by any domain.
+   * - TAMPC
+     - Access ports (AP) for the local domains are enabled, allowing direct programming of all the memory not reserved by Nordic firmware in the default configuration.
 
 .. note::
    * The Radio Domain AP is only usable when the Radio domain has booted.
    * Access to external memory (EXMIF) requires a non-default configuration of the GPIO.CTRLSEL register.
 
-You can protect global domain memory from write operations by configuring the UICR registers.
-To remove these protections and disable all other protection mechanisms enforced through UICR settings, perform an ``ERASEALL`` operation.
+Restricting default memory access
+=================================
+
+Global domain memory can be protected from write operations by configuring the :ref:`UICR.PROTECTEDMEM <ug_nrf54h20_ironside_se_protected_memory>` registers.
+
+Performing an ``ERASEALL`` operation will remove the memory protections and disable all other protection mechanisms enforced through default UICR settings.
 
 .. _ug_nrf54h20_ironside_se_uicr:
 
@@ -311,6 +297,8 @@ However, it does not prevent erase operations initiated through other means, suc
    If this configuration is enabled and :kconfig:option:`CONFIG_GEN_UICR_LOCK` is also set, it is no longer possible to modify the UICR in any way.
    Therefore, this configuration should only be enabled during the final stages of production.
 
+.. _ug_nrf54h20_ironside_se_protected_memory:
+
 UICR.PROTECTEDMEM
 =================
 
@@ -1123,6 +1111,8 @@ See the following table for a summary of the available boot commands:
 
 The following chapters describe each command in detail.
 
+.. _ug_nrf54h20_ironside_se_eraseall:
+
 ``ERASEALL`` command
 ====================
 

doc/nrf/app_dev/device_guides/nrf54h/ug_nrf54h20_ironside_update.rst

@@ -11,6 +11,39 @@ Updating the |ISE| is possible after it has been initially :ref:`provisioned <ug
 
 The update operation is initiated through its :ref:`update service <ug_nrf54h20_ironside_se_update_service>` at runtime by application firmware.
 
+.. _ug_nrf54h20_ironside_se_deliverables:
+
+Release package
+***************
+
+The |ISE| is released independently of the |NCS| release cycle and is provided as a ZIP archive.
+
+The archive is used to update the existing |ISE| firmware on the nRF54H20 and consists of the following components:
+
+.. list-table::
+   :header-rows: 1
+   :widths: auto
+
+   * - Component
+     - File
+     - Description
+   * - IronSide SE firmware
+     - :file:`ironside_se.hex`
+     - Used when bringing up a new DK and programming both the recovery firmware and |ISE| for the first time.
+   * - IronSide SE update firmware
+     - :file:`ironside_se_update.hex`
+     - Used when updating |ISE|.
+   * - IronSide SE Recovery update firmware
+     - :file:`ironside_se_recovery_update.hex`
+     - The recovery firmware, reserved for future recovery operations. Currently, it does not provide user-facing functionality. Used when updating the recovery firmware.
+   * - Update application
+     - :file:`update_application.hex`
+     - The local domain :zephyr:code-sample:`update application <nrf_ironside_update>` that is used to perform an |ISE| update. See :ref:`ug_nrf54h20_ironside_se_update_architecture` for details on its role.
+
+For more information on |ISE| release binaries, see :ref:`abi_compatibility`.
+
+For instructions on how to provision the nRF54H20 with |ISE| for the first time, see :ref:`ug_nrf54h20_SoC_binaries`.
+
 .. _ug_nrf54h20_ironside_se_updating:
 
 Performing an update