doc: Post NCS 3.2.0 release updates

Post NCS 3.2.0 release updates.

Signed-off-by: Francesco Domenico Servidio <francesco.servidio@nordicsemi.no>

Author: FrancescoSer

applications/nrf_desktop/bootloader_dfu.rst

@@ -207,7 +207,7 @@ The application image is always built for the RAM address space in only one vari
 
 You can use the RAM load mode of the MCUboot bootloader to speed up the code execution for the application image, as code execution from the RAM is generally faster than from the NVM.
 This can improve the device performance during the activities that require high CPU usage.
-As an example, the nRF Desktop application uses the RAM load mode for the ``nrf54lm20dk/nrf54lm20a/cpuapp`` board target to achieve 8 kHz report rate over USB in the ``release_ram_load`` configuration variant (the second configuration variant - ``ram_load`` - is used for debugging purposes only).
+As an example, the nRF Desktop application uses the RAM load mode for the ``nrf54lm20dk/nrf54lm20a/cpuapp`` board target to improve the HID report rate over USB.
 
 To set the MCUboot mode of operations to the RAM load mode, enable the :kconfig:option:`SB_CONFIG_MCUBOOT_MODE_RAM_LOAD` Kconfig option in the sysbuild configuration.
 

doc/CMakeLists.txt

@@ -338,7 +338,7 @@ add_docset(tfm "2.2.0")
 #-------------------------------------------------------------------------------
 # docset: matter
 
-add_docset(matter "1.4.1")
+add_docset(matter "1.5.0")
 
 #-------------------------------------------------------------------------------
 # docset: nrfxlib

doc/nrf/dev_model_and_contributions/adding_code.rst

@@ -162,7 +162,7 @@ This is demonstrated by the following code, that would be placed somewhere in yo
        - name: nrf
          repo-path: sdk-nrf
          remote: ncs
-         revision: v3.1.0
+         revision: v3.2.0
          import: true
      self:
        path: application
@@ -190,7 +190,7 @@ For example:
        - name: nrf
          repo-path: sdk-nrf
          remote: ncs
-         revision: v3.1.0
+         revision: v3.2.0
          import: true
        # Example for how to override a repository in the nRF Connect SDK with your own:
        - name: mcuboot

doc/nrf/links.txt

@@ -250,7 +250,7 @@
 
 .. _`Zephyr hostap fork`: https://github.com/zephyrproject-rtos/hostap
 
-.. _`tfm_secure_peripheral_partition.yaml`: https://github.com/nrfconnect/sdk-nrf/blob/main/samples/tfm/tfm_secure_peripheral/secure_peripheral_partition/tfm_secure_peripheral_partition.yaml
+.. _`tfm_secure_peripheral_partition.yaml`: https://github.com/nrfconnect/sdk-nrf/blob/main/samples/tfm/tfm_secure_peripheral/secure_peripheral_partition/tfm_secure_peripheral_partition.yaml.in
 
 .. ### Source: github.io
 
@@ -325,6 +325,7 @@
 
 .. _`Nordic nRF9151 DK`:
 .. _`nRF9151 DK product page`: https://www.nordicsemi.com/Products/Development-hardware/nRF9151-DK
+.. _`nRF9151 SMA DK product page`: https://www.nordicsemi.com/Products/Development-hardware/nRF9151-SMA-DK
 .. _`nRF9151 DK Downloads`: https://www.nordicsemi.com/Products/Development-hardware/nRF9151-DK/Download?lang=en#infotabs
 
 .. _`Nordic nRF9151 SMA DK`:
@@ -413,6 +414,7 @@
 
 .. #### Source: www.nordicsemi.com/Events/, https://www.nordicsemi.com/Resources/, https://webinars.nordicsemi.com/events
 
+.. _`nRF Connect SDK v3.2.0 webinar`:
 .. _`nRF Connect SDK v3.0.0 webinar`:
 .. _`nRF Connect SDK v2.9.0 webinar`:
 .. _`nRF Connect SDK v2.8.0 webinar`: https://webinars.nordicsemi.com/events
@@ -512,6 +514,7 @@
 .. _`Serial Modem`: https://docs.nordicsemi.com/bundle/addon-serial_modem-latest/page/index.html
 
 .. _`known issues page on the main branch`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/known_issues.html
+.. _`known issues for nRF Connect SDK v3.2.0`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/known_issues.html?v=v3-2-0
 .. _`known issues for nRF Connect SDK v3.1.1`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/known_issues.html?v=v3-1-1
 .. _`known issues for nRF Connect SDK v3.1.0`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/known_issues.html?v=v3-1-0
 .. _`known issues for nRF Connect SDK v3.0.2`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/known_issues.html?v=v3-0-2
@@ -562,6 +565,7 @@
 .. _`known issues for nRF Connect SDK v1.4.1`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/known_issues.html?v=v1-4-1
 .. _`known issues for nRF Connect SDK v1.4.0`: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/known_issues.html?v=v1-4-0
 
+.. _`Repositories and revisions for v3.2.0`: https://docs.nordicsemi.com/bundle/ncs-3.2.0/page/nrf/releases_and_maturity/repository_revisions.html
 .. _`Repositories and revisions for v3.1.1`: https://docs.nordicsemi.com/bundle/ncs-3.1.1/page/nrf/releases_and_maturity/repository_revisions.html
 .. _`Repositories and revisions for v3.1.0`: https://docs.nordicsemi.com/bundle/ncs-3.1.0/page/nrf/releases_and_maturity/repository_revisions.html
 .. _`Repositories and revisions for v3.0.2`: https://docs.nordicsemi.com/bundle/ncs-3.0.2/page/nrf/releases_and_maturity/repository_revisions.html
@@ -601,6 +605,7 @@
 .. _`Repositories and revisions for v1.9.1`: https://docs.nordicsemi.com/bundle/ncs-1.9.1/page/nrf/introduction.html#repositories_and_revisions
 .. _`Repositories and revisions`: https://docs.nordicsemi.com/bundle/ncs-1.9.0/page/nrf/introduction.html#repositories_and_revisions
 
+.. _`Modem library changelog for v3.2.0`: https://docs.nordicsemi.com/bundle/ncs-3.2.0/page/nrfxlib/nrf_modem/doc/CHANGELOG.html#nrf-modem-changelog
 .. _`Modem library changelog for v3.1.1`: https://docs.nordicsemi.com/bundle/ncs-3.1.1/page/nrfxlib/nrf_modem/doc/CHANGELOG.html#nrf-modem-changelog
 .. _`Modem library changelog for v3.1.0`: https://docs.nordicsemi.com/bundle/ncs-3.1.0/page/nrfxlib/nrf_modem/doc/CHANGELOG.html#nrf-modem-changelog
 .. _`Modem library changelog for v3.0.2`: https://docs.nordicsemi.com/bundle/ncs-3.0.2/page/nrfxlib/nrf_modem/doc/CHANGELOG.html#nrf-modem-changelog
@@ -639,6 +644,7 @@
 .. _`Modem library changelog for v1.9.1`: https://docs.nordicsemi.com/bundle/ncs-1.9.1/page/nrfxlib/nrf_modem/doc/CHANGELOG.html
 .. _`Modem library changelog for v1.9.0`: https://docs.nordicsemi.com/bundle/ncs-1.9.0/page/nrfxlib/nrf_modem/doc/CHANGELOG.html
 
+.. _`LwM2M carrier library changelog for v3.2.0`: https://docs.nordicsemi.com/bundle/ncs-3.2.0/page/nrf/libraries/bin/lwm2m_carrier/CHANGELOG.html#liblwm2m-carrier-changelog
 .. _`LwM2M carrier library changelog for v3.1.1`: https://docs.nordicsemi.com/bundle/ncs-3.1.1/page/nrf/libraries/bin/lwm2m_carrier/CHANGELOG.html#liblwm2m-carrier-changelog
 .. _`LwM2M carrier library changelog for v3.1.0`: https://docs.nordicsemi.com/bundle/ncs-3.1.0/page/nrf/libraries/bin/lwm2m_carrier/CHANGELOG.html#liblwm2m-carrier-changelog
 .. _`LwM2M carrier library changelog for v3.0.2`: https://docs.nordicsemi.com/bundle/ncs-3.0.2/page/nrf/libraries/bin/lwm2m_carrier/CHANGELOG.html#liblwm2m-carrier-changelog
@@ -919,6 +925,7 @@
 .. _`Product specification for nRF70 Series devices`: https://docs.nordicsemi.com/bundle/ps_nrf7002/page/keyfeatures_html5.html
 .. _`nRF7002 DK Hardware`: https://docs.nordicsemi.com/bundle/ug_nrf7002_dk/page/UG/nrf7002_DK/intro.html
 .. _`nRF70 Series hardware documentation`:
+.. _`nRF7002 Expansion Board II`: https://www.nordicsemi.com/Products/Development-hardware/nRF7002-EBII
 
 .. _`Measuring current`: https://docs.nordicsemi.com/bundle/ug_nrf7002_dk/page/UG/nrf7002_DK/hw_measure_current.html
 .. _`nRF70 Series`:
@@ -1039,6 +1046,7 @@
 .. _`GPS interface and antenna`: https://docs.nordicsemi.com/bundle/nwp_033/page/WP/nwp_033/nwp_033_gps.html
 .. _`Security protocol for cellular IoT`: https://docs.nordicsemi.com/bundle/nwp_044/page/WP/nwp_044/security_protocols.html
 .. _`Wi-Fi Alliance Certification for nRF70 Series`: https://docs.nordicsemi.com/bundle/nwp_045/page/WP/nwp_045/intro.html
+.. _`Wi-Fi Alliance Enterprise Certification for WPA2 and WPA3 on nRF7002 DK`: https://api.cert.wi-fi.org/api/certificate/download/public?variantId=143751
 .. _`nWP049 - Matter over Thread: Power consumption and battery life`: https://docs.nordicsemi.com/bundle/nwp_049/page/WP/nwp_049/intro.html
 .. _`nWP044 - Best practices for cellular IoT development LTE technology`: https://docs.nordicsemi.com/bundle/nwp_044/page/WP/nwp_044/lte_technology.html
 .. _`nWP044 - Best practices for cellular IoT development`: https://docs.nordicsemi.com/bundle/nwp_044/page/WP/nwp_044/intro.html
@@ -1102,6 +1110,8 @@
 
 .. ### Source: files.nordicsemi.com
 
+.. _`Twister test report for nRF Connect SDK v3.2.0`: https://files.nordicsemi.com/ui/api/v1/download/contentBrowsing/NCS/external/release/v3.2.0/test-report/twister_test_results_report.html?isNativeBrowsing=true
+.. _`Hardware test report for nRF Connect SDK v3.2.0`: https://files.nordicsemi.com/ui/api/v1/download/contentBrowsing/NCS/external/release/v3.2.0/test-report/common_ncs_test_results_report.html?isNativeBrowsing=true
 .. _`Twister test report for nRF Connect SDK v3.1.0`: https://files.nordicsemi.com/ui/api/v1/download/contentBrowsing/NCS/external/release/v3.1.0/test-report/twister_test_results_report.html?isNativeBrowsing=true
 .. _`Hardware test report for nRF Connect SDK v3.1.0`: https://files.nordicsemi.com/ui/api/v1/download/contentBrowsing/NCS/external/release/v3.1.0/test-report/common_ncs_test_results_report.html?isNativeBrowsing=true
 .. _`Twister test report for nRF Connect SDK v3.0.0`: https://files.nordicsemi.com/ui/api/v1/download/contentBrowsing/NCS/external/release/v3.0.0/test-report/twister_test_results_report.html?isNativeBrowsing=true
@@ -1212,7 +1222,7 @@
 .. _`Profile Tuning Suite (PTS)`: https://www.bluetooth.com/develop-with-bluetooth/qualification-listing/qualification-test-tools/profile-tuning-suite/
 .. _`Bluetooth Qualification Listing`: https://launchstudio.bluetooth.com/Listings/Search/
 .. _`Qualification process with no required testing`: https://www.bluetooth.com/develop-with-bluetooth/qualification-listing/qualification-process-with-no-required-testing/
-.. _`Qualification process with required testing`: https://www.bluetooth.com/develop-with-bluetooth/qualification-listing/qualification-process-with-required-testing/
+.. _`Qualification process with required testing`: https://www.bluetooth.com/bluetooth-qualification-process-quick-start-guide/
 .. _`Qualifications and listings`: https://support.bluetooth.com/hc/en-us/categories/360004202331-Qualifications-and-Listings/
 .. _`Bluetooth Qualification Consultants`: https://www.bluetooth.com/develop-with-bluetooth/qualification-listing/qualification-consultants/
 .. _`Bluetooth product types`: https://support.bluetooth.com/hc/en-us/articles/360049018712/
@@ -1601,6 +1611,7 @@
 
 .. _`Matter 1.3 CSA blog post`: https://csa-iot.org/newsroom/matter-1-3-specification-released/
 .. _`CSA press release for Matter 1.4`: https://csa-iot.org/newsroom/matter-1-4-enables-more-capable-smart-homes/
+.. _`CSA press release for Matter 1.5`: https://csa-iot.org/newsroom/matter-1-5-introduces-cameras-closures-and-enhanced-energy-management-capabilities/
 
 .. ### Source: Chocolatey
 
@@ -1734,7 +1745,7 @@
 
 .. _`Coiote Device Management`: https://www.avsystem.com/products/coiote-iot-device-management-platform/
 .. _`Coiote Device Management server`: https://eu.iot.avsystem.cloud/
-.. _`Viewing device location in Coiote Device Management`: https://iotdevzone.avsystem.com/docs/Cloud_integrations/nRF_Cloud_Location_services/Configure_nRF_Cloud_integration/#view-device-location-in-coiote-dm
+.. _`Viewing device location in Coiote Device Management`: https://iotdevzone.avsystem.com/docs/Coiote_IoT_DM/Cloud_integrations/cloud-integrations/#nrf-cloud-location-services
 .. _`nRF9160 Anjay integration`: https://iotdevzone.avsystem.com/docs/LwM2M_Client/Nordic/nRF9160DK/
 .. _`Thingy:91 integration`: https://iotdevzone.avsystem.com/docs/LwM2M_Client/Nordic/Thingy91/#thingy91
 
@@ -1775,8 +1786,7 @@
 .. _`BME688`: https://www.bosch-sensortec.com/products/environmental-sensors/gas-sensors/bme688/
 .. _`BME680`: https://www.bosch-sensortec.com/products/environmental-sensors/gas-sensors/bme680/
 .. _`BMI270`: https://www.bosch-sensortec.com/products/motion-sensors/imus/bmi270/
-.. _`Bosch BSEC`: https://www.bosch-sensortec.com/software-tools/software/bsec/
-.. _`BSEC license`: https://www.bosch-sensortec.com/media/boschsensortec/downloads/software/bme688_development_software/2023_04/license_terms_bme688_bme680_bsec.pdf
+.. _`BSEC license`: https://www.bosch-sensortec.com/media/boschsensortec/downloads/software/bme688_development_software/2024_12/20241219_clickthrough_license_terms_bsec_bme680_bme688_bme690.pdf
 
 .. ### Source: wireshark.org
 
@@ -1904,8 +1914,6 @@
 
 .. _`Semantic versioning`: https://semver.org/
 
-.. _`mbedtls_memory_buffer_alloc_init`: https://tls.mbed.org/api/memory__buffer__alloc_8h.html#ac70d134be54133c272d8eab2cb85dfbf
-
 .. _`HERE Positioning`: https://www.here.com/platform/positioning
 
 .. _`dfu-util tool`: http://dfu-util.sourceforge.net/

doc/nrf/protocols/matter/index.rst

@@ -23,11 +23,13 @@ For a full list of |NCS| and Matter versions, view the following table:
    +--------------------------+-----------------------------------------------------+------------------------+
    | nRF Connect SDK version  | Matter specification version                        | Matter SDK version     |
    +==========================+=====================================================+========================+
-   | v3.1.99 (latest)         | :ref:`1.5.0 <ug_matter_overview_dev_model_support>` | 1.5.0.0                |
+   | v3.2.99 (latest)         | :ref:`1.5.0 <ug_matter_overview_dev_model_support>` | 1.5.0.0                |
+   +--------------------------+                                                     |                        |
+   | |release|                |                                                     |                        |
    +--------------------------+-----------------------------------------------------+------------------------+
    | v3.1.1                   | :ref:`1.4.2 <ug_matter_overview_dev_model_support>` | 1.4.2.0                |
    +--------------------------+                                                     |                        |
-   | |release|                |                                                     |                        |
+   | 3.1.0                    |                                                     |                        |
    +--------------------------+-----------------------------------------------------+------------------------+
    | v3.0.2                   | :ref:`1.4.1 <ug_matter_overview_dev_model_support>` | 1.4.1.0                |
    +--------------------------+                                                     |                        |

doc/nrf/releases_and_maturity/abi_compatibility.rst

@@ -82,8 +82,8 @@ Fixed
 -----
 
 * L2CACHE now prefetches several cache lines when an L2 cache miss occurs. (HM-26346)
-  This will improve L2 cache performance in some situations and reduce L2 cache performance in other situations.
-* Fixed unintentional behavior of ``psa_copy_key()`` when it was used in an attempt to create a revocable key. (NCSDK-36369)
+  This improves L2 cache performance in some situations and reduces it in others.
+* Fixed an unintentional behavior of ``psa_copy_key()`` when used to create a revocable key. (NCSDK-36369)
 
 IronSide Secure Element (IronSide SE) v23.1.0+19
 ================================================

doc/nrf/releases_and_maturity/migration/migration_guide_3.2.rst

@@ -1,7 +1,7 @@
 .. _migration_3.2:
 
-Migration guide for |NCS| v3.2.0 (Working draft)
-################################################
+Migration guide for |NCS| v3.2.0
+################################
 
 .. contents::
    :local:
@@ -47,7 +47,7 @@ nRF54H20 IronSide SE binaries
 
 .. toggle::
 
-   * The nRF54H20 IronSide SE binaries have been updated to version v23.1.0+19.
+   * The nRF54H20 IronSide SE binaries have been updated to version v23.1.1+20.
      Starting from the |NCS| v3.2.0, you should always upgrade your nRF54H20 IronSide SE binaries to the latest version.
 
      For more information, see:
@@ -60,9 +60,13 @@ nRF54H20 power management
 
 .. toggle::
 
-   * The Kconfig options :kconfig:option:`PM_S2RAM` and :kconfig:option:`PM_S2RAM_CUSTOM_MARKING` have been reworked to be managed automatically based on the suspend-to-ram ``power-states`` in the devicetree.
+   * The Kconfig options :kconfig:option:`CONFIG_PM_S2RAM` and :kconfig:option:`CONFIG_PM_S2RAM_CUSTOM_MARKING` have been reworked to be managed automatically based on the suspend-to-ram ``power-states`` in the devicetree.
      Any occurrences of ``CONFIG_PM_S2RAM=y`` and ``CONFIG_PM_S2RAM_CUSTOM_MARKING=y`` must be removed.
-     Any occurrence of ``CONFIG_PM_S2RAM=n`` or when the code requires S2RAM state to be disabled (the default value of :kconfig:option:`PM_S2RAM` has changed from ``n`` to ``y``) must be replaced by disabling the ``s2ram`` power state in the devicetree.
+
+     The default value of :kconfig:option:`CONFIG_PM_S2RAM` has changed from ``n`` to ``y``.
+     If your application explicitly disables S2RAM or relies on S2RAM being disabled, remove any instance of ``CONFIG_PM_S2RAM=n`` and instead disable the ``s2ram`` power state in the devicetree.
+
+     To disable the ``s2ram`` power state, see the following DTS example:
 
      .. code-block:: dts
 
@@ -462,13 +466,16 @@ This section provides detailed lists of changes by :ref:`integration <integratio
 Memfault integration
 --------------------
 
-* The options have changed for the ``CONFIG_MEMFAULT_NCS_DEVICE_ID_*`` choice, which sets the Memfault Device Serial:
+.. toggle::
+
+   * The options have changed for the ``CONFIG_MEMFAULT_NCS_DEVICE_ID_*`` choice, which sets the Memfault Device Serial:
 
-  * :kconfig:option:`CONFIG_MEMFAULT_NCS_DEVICE_ID_HW_ID` (new, and default) - Use ``hw_id`` provided device ID, which is also what nRF Cloud uses for device identity. See the :ref:`lib_hw_id` library for options for device ID source.
-  * :kconfig:option:`CONFIG_MEMFAULT_NCS_DEVICE_ID_STATIC` - Used to set a custom build-time defined static device ID, primarily useful for testing.
-  * :kconfig:option:`CONFIG_MEMFAULT_NCS_DEVICE_ID_RUNTIME` - Use a runtime-applied device ID, commonly used when the serial number of the device is written into settings at manufacturing time, for example.
-  * :kconfig:option:`CONFIG_MEMFAULT_NCS_DEVICE_ID_IMEI` (deprecated) - Use the LTE modem IMEI as the device ID.
-  * :kconfig:option:`CONFIG_MEMFAULT_NCS_DEVICE_ID_NET_MAC` (deprecated) - Use the network interface MAC address as the device ID.
+     * :kconfig:option:`CONFIG_MEMFAULT_NCS_DEVICE_ID_HW_ID` (new, and default) - Use ``hw_id`` provided device ID, which is also what nRF Cloud uses for device identity.
+       See the :ref:`lib_hw_id` library for options for device ID source.
+     * :kconfig:option:`CONFIG_MEMFAULT_NCS_DEVICE_ID_STATIC` - Used to set a custom build-time defined static device ID, primarily useful for testing.
+     * :kconfig:option:`CONFIG_MEMFAULT_NCS_DEVICE_ID_RUNTIME` - Use a runtime-applied device ID, commonly used when the serial number of the device is written into settings at manufacturing time, for example.
+     * :kconfig:option:`CONFIG_MEMFAULT_NCS_DEVICE_ID_IMEI` (deprecated) - Use the LTE modem IMEI as the device ID.
+     * :kconfig:option:`CONFIG_MEMFAULT_NCS_DEVICE_ID_NET_MAC` (deprecated) - Use the network interface MAC address as the device ID.
 
 Drivers
 =======

doc/nrf/releases_and_maturity/release_notes.rst

@@ -21,6 +21,7 @@ This page is included only in the latest documentation, because it might contain
    :caption: Subpages:
 
    releases/release-notes-changelog
+   releases/release-notes-3.2.0
    releases/release-notes-3.2.0-preview3
    releases/release-notes-3.2.0-preview2
    releases/release-notes-3.2.0-preview1