ahasztag · ahasztag · Sep 15, 2025 · Sep 15, 2025 · Sep 2, 2025 · Sep 16, 2025
diff --git a/.github/test-spec.yml b/.github/test-spec.yml
@@ -646,3 +646,4 @@
   - "include/nfc/ndef/text_rec.h"
   - "include/dk_buttons_and_leds.h"
   - "include/app_event_manager/app_event_manager.h"
+  - "scripts/west_commands/ncs_ironside_se_update.py"
diff --git a/CODEOWNERS b/CODEOWNERS
@@ -504,6 +504,7 @@
 /samples/debug/ppi_trace/                 @nordic-krch
 /samples/dect/dect_phy/dect_shell/        @nrfconnect/ncs-modem-tre
 /samples/dect/dect_phy/hello_dect/        @nrfconnect/ncs-modem
+/samples/dfu/ab/                          @nrfconnect/ncs-charon
 /samples/dfu/dfu_target/                  @nrfconnect/ncs-charon
 /samples/dfu/dfu_multi_image/             @nrfconnect/ncs-charon
 /samples/edge_impulse/                    @nrfconnect/ncs-si-muffin
@@ -629,6 +630,7 @@
 /samples/debug/ppi_trace/*.rst            @nrfconnect/ncs-doc-leads
 /samples/dect/dect_phy/dect_shell/*.rst   @nrfconnect/ncs-iot-positioning-doc
 /samples/dect/dect_phy/hello_dect/*.rst   @nrfconnect/ncs-modem-doc
+/samples/dfu/ab/*.rst                     @nrfconnect/ncs-charon-doc
 /samples/dfu/dfu_target/*.rst             @nrfconnect/ncs-charon-doc
 /samples/dfu/dfu_multi_image/*.rst        @nrfconnect/ncs-charon-doc
 /samples/esb/**/*.rst                     @nrfconnect/ncs-si-muffin-doc
@@ -784,6 +786,7 @@
 /subsys/debug/                            @nordic-krch
 /subsys/debug/coredump/                   @nrfconnect/ncs-protocols-serialization
 /subsys/dfu/                              @nrfconnect/ncs-pluto
+/subsys/dfu/dfu_target/                   @nrfconnect/ncs-pluto @nrfconnect/ncs-charon
 /subsys/dfu/dfu_multi_image/              @Damian-Nordic @nrfconnect/ncs-charon
 /subsys/dm/                               @nrfconnect/ncs-si-muffin
 /subsys/dult/                             @nrfconnect/ncs-si-bluebagel

diff --git a/applications/machine_learning/VERSION b/applications/machine_learning/VERSION
@@ -1,5 +1,5 @@
 VERSION_MAJOR = 3
-VERSION_MINOR = 0
+VERSION_MINOR = 1
 PATCHLEVEL = 99
 VERSION_TWEAK = 0
 EXTRAVERSION =
diff --git a/applications/matter_bridge/VERSION b/applications/matter_bridge/VERSION
@@ -1,5 +1,5 @@
 VERSION_MAJOR = 3
-VERSION_MINOR = 0
+VERSION_MINOR = 1
 PATCHLEVEL = 99
 VERSION_TWEAK = 0
 EXTRAVERSION =
diff --git a/applications/matter_bridge/doc/matter_bridge_description.rst b/applications/matter_bridge/doc/matter_bridge_description.rst
@@ -382,23 +382,15 @@ Configuration options
 
 Check and configure the following configuration options:
 
-.. _CONFIG_BRIDGED_DEVICE_IMPLEMENTATION:
+.. _CONFIG_BRIDGED_DEVICE_SIMULATED:
 
-CONFIG_BRIDGED_DEVICE_IMPLEMENTATION
-   ``bool`` - Select bridged device implementation.
-   See the :ref:`matter_bridge_app_bridged_support_configs` section for more information.
-   Accepts the following values:
+CONFIG_BRIDGED_DEVICE_SIMULATED
+   ``bool`` - Implement a simulated bridged device.
 
-   .. _CONFIG_BRIDGED_DEVICE_SIMULATED:
+.. _CONFIG_BRIDGED_DEVICE_BT:
 
-   CONFIG_BRIDGED_DEVICE_SIMULATED
-      ``bool`` - Implement a simulated bridged device.
-      You must also configure :ref:`CONFIG_BRIDGED_DEVICE_SIMULATED_ONOFF_IMPLEMENTATION <CONFIG_BRIDGED_DEVICE_SIMULATED_ONOFF_IMPLEMENTATION>`
-
-   .. _CONFIG_BRIDGED_DEVICE_BT:
-
-   CONFIG_BRIDGED_DEVICE_BT
-      ``bool`` - Implement a Bluetooth LE bridged device.
+CONFIG_BRIDGED_DEVICE_BT
+   ``bool`` - Implement a Bluetooth LE bridged device.
 
 .. _CONFIG_BRIDGE_HUMIDITY_SENSOR_BRIDGED_DEVICE:
 
@@ -410,21 +402,15 @@ CONFIG_BRIDGE_HUMIDITY_SENSOR_BRIDGED_DEVICE
 CONFIG_BRIDGE_ONOFF_LIGHT_BRIDGED_DEVICE
    ``bool`` - Enable support for OnOff Light bridged device.
 
-.. _CONFIG_BRIDGE_SWITCH_BRIDGED_DEVICE:
-
-CONFIG_BRIDGE_SWITCH_BRIDGED_DEVICE
-   ``bool`` - Enable support for a switch bridged device.
-   Accepts the following values:
+.. _CONFIG_BRIDGE_GENERIC_SWITCH_BRIDGED_DEVICE:
 
-   .. _CONFIG_BRIDGE_GENERIC_SWITCH_BRIDGED_DEVICE:
+CONFIG_BRIDGE_GENERIC_SWITCH_BRIDGED_DEVICE
+   ``bool`` - Enable support for Generic Switch bridged device.
 
-   CONFIG_BRIDGE_GENERIC_SWITCH_BRIDGED_DEVICE
-      ``bool`` - Enable support for Generic Switch bridged device.
+.. _CONFIG_BRIDGE_ONOFF_LIGHT_SWITCH_BRIDGED_DEVICE:
 
-   .. _CONFIG_BRIDGE_ONOFF_LIGHT_SWITCH_BRIDGED_DEVICE:
-
-   CONFIG_BRIDGE_ONOFF_LIGHT_SWITCH_BRIDGED_DEVICE
-      ``bool`` - Enable support for OnOff Light Switch bridged device.
+CONFIG_BRIDGE_ONOFF_LIGHT_SWITCH_BRIDGED_DEVICE
+   ``bool`` - Enable support for OnOff Light Switch bridged device.
 
 .. _CONFIG_BRIDGE_TEMPERATURE_SENSOR_BRIDGED_DEVICE:
 
@@ -443,23 +429,17 @@ CONFIG_BRIDGE_MIGRATE_VERSION_1
 
    If you selected the simulated device implementation using the :ref:`CONFIG_BRIDGED_DEVICE_SIMULATED <CONFIG_BRIDGED_DEVICE_SIMULATED>` Kconfig option, also check and configure the following option:
 
-.. _CONFIG_BRIDGED_DEVICE_SIMULATED_ONOFF_IMPLEMENTATION:
-
-CONFIG_BRIDGED_DEVICE_SIMULATED_ONOFF_IMPLEMENTATION
-   ``bool`` - Select the simulated OnOff device implementation.
-   Accepts the following values:
+.. _CONFIG_BRIDGED_DEVICE_SIMULATED_ONOFF_AUTOMATIC:
 
-   .. _CONFIG_BRIDGED_DEVICE_SIMULATED_ONOFF_AUTOMATIC:
+CONFIG_BRIDGED_DEVICE_SIMULATED_ONOFF_AUTOMATIC
+   ``bool`` - Automatically simulated OnOff device.
+   The simulated device automatically changes its state periodically.
 
-   CONFIG_BRIDGED_DEVICE_SIMULATED_ONOFF_AUTOMATIC
-      ``bool`` - Automatically simulated OnOff device.
-      The simulated device automatically changes its state periodically.
+.. _CONFIG_BRIDGED_DEVICE_SIMULATED_ONOFF_SHELL:
 
-   .. _CONFIG_BRIDGED_DEVICE_SIMULATED_ONOFF_SHELL:
-
-   CONFIG_BRIDGED_DEVICE_SIMULATED_ONOFF_SHELL
-      ``bool`` - Shell-controlled simulated OnOff device.
-      The state of the simulated device is changed using shell commands.
+CONFIG_BRIDGED_DEVICE_SIMULATED_ONOFF_SHELL
+   ``bool`` - Shell-controlled simulated OnOff device.
+   The state of the simulated device is changed using shell commands.
 
 If you selected the Bluetooth LE device implementation using the :ref:`CONFIG_BRIDGED_DEVICE_BT <CONFIG_BRIDGED_DEVICE_BT>` Kconfig option, also check and configure the following options:
 
@@ -490,6 +470,41 @@ CONFIG_BRIDGE_BT_RECOVERY_SCAN_TIMEOUT_MS
 CONFIG_BRIDGE_BT_SCAN_TIMEOUT_MS
    ``int`` - Set the Bluetooth LE scan timeout in milliseconds.
 
+.. _CONFIG_BRIDGE_FORCE_BT_CONNECTION_PARAMS:
+
+CONFIG_BRIDGE_FORCE_BT_CONNECTION_PARAMS
+   ``bool`` - Determines whether the Matter bridge forces connection parameters or accepts the Bluetooth LE peripheral device selection.
+
+.. _CONFIG_BRIDGE_BT_SCAN_WINDOW:
+
+CONFIG_BRIDGE_BT_SCAN_WINDOW
+   ``int`` - Duration of a central actively scanning for devices within scan interval, equal to ``CONFIG_BRIDGE_BT_SCAN_WINDOW`` * 0.625 ms.
+
+.. _CONFIG_BRIDGE_BT_SCAN_INTERVAL:
+
+CONFIG_BRIDGE_BT_SCAN_INTERVAL
+   ``int`` - Time between consecutive Bluetooth scan windows, equal to ``CONFIG_BRIDGE_BT_SCAN_INTERVAL`` * 0.625 ms.
+
+.. _CONFIG_BRIDGE_BT_CONNECTION_INTERVAL_MIN:
+
+CONFIG_BRIDGE_BT_CONNECTION_INTERVAL_MIN
+   ``int`` - The minimum duration of time requested by central after the peripheral device should wake up to communicate, equal to ``CONFIG_BRIDGE_BT_CONNECTION_INTERVAL_MIN`` * 1.25 ms.
+
+.. _CONFIG_BRIDGE_BT_CONNECTION_INTERVAL_MAX:
+
+CONFIG_BRIDGE_BT_CONNECTION_INTERVAL_MAX
+   ``int`` - The maximum duration of time requested by central after the peripheral device should wake up to communicate, equal to ``CONFIG_BRIDGE_BT_CONNECTION_INTERVAL_MAX`` * 1.25 ms.
+
+.. _CONFIG_BRIDGE_BT_CONNECTION_TIMEOUT:
+
+CONFIG_BRIDGE_BT_CONNECTION_TIMEOUT
+   ``int`` - The time since the last packet was successfully received until the devices consider the connection lost, equal to ``CONFIG_BRIDGE_BT_CONNECTION_TIMEOUT`` cs.
+
+.. _CONFIG_BRIDGE_BT_CONNECTION_LATENCY:
+
+CONFIG_BRIDGE_BT_CONNECTION_LATENCY
+   ``int`` - The number of connection events the peripheral can skip waking up for if it does not have any data to send.
+
 The following options affect how many bridged devices the application supports.
 See the :ref:`matter_bridge_app_bridged_support_configs` section for more information.
 
@@ -593,12 +608,12 @@ You can disable configuring the parameters by setting the :kconfig:option:`CONFI
 
 Use the following Kconfig options to set the desired parameters:
 
-- :kconfig:option:`CONFIG_BRIDGE_BT_SCAN_WINDOW` - The duration a central actively scans for devices within the scan interval.
-- :kconfig:option:`CONFIG_BRIDGE_BT_SCAN_INTERVAL` - Time between consecutive Bluetooth LE scan windows.
-- :kconfig:option:`CONFIG_BRIDGE_BT_CONNECTION_INTERVAL_MIN` - The minimum time requested by the central (the bridge) after which the peripheral device should wake up to communicate.
-- :kconfig:option:`CONFIG_BRIDGE_BT_CONNECTION_INTERVAL_MAX` - The maximum time requested by the central (the bridge) after which the peripheral device should wake up to communicate.
-- :kconfig:option:`CONFIG_BRIDGE_BT_CONNECTION_TIMEOUT` - The time since the last packet was successfully received until the devices consider the connection lost.
-- :kconfig:option:`CONFIG_BRIDGE_BT_CONNECTION_LATENCY` - Allows the peripheral to skip waking up for a certain number of connection events if it does not have any data to send.
+- :ref:`CONFIG_BRIDGE_BT_SCAN_WINDOW` - The duration a central actively scans for devices within the scan interval.
+- :ref:`CONFIG_BRIDGE_BT_SCAN_INTERVAL` - Time between consecutive Bluetooth LE scan windows.
+- :ref:`CONFIG_BRIDGE_BT_CONNECTION_INTERVAL_MIN` - The minimum time requested by the central (the bridge) after which the peripheral device should wake up to communicate.
+- :ref:`CONFIG_BRIDGE_BT_CONNECTION_INTERVAL_MAX` - The maximum time requested by the central (the bridge) after which the peripheral device should wake up to communicate.
+- :ref:`CONFIG_BRIDGE_BT_CONNECTION_TIMEOUT` - The time since the last packet was successfully received until the devices consider the connection lost.
+- :ref:`CONFIG_BRIDGE_BT_CONNECTION_LATENCY` - Allows the peripheral to skip waking up for a certain number of connection events if it does not have any data to send.
 
 The parameters in this application have been selected based on the :ref:`multiprotocol_bt_thread` information in the :ref:`ug_multiprotocol_support` section.
 

diff --git a/applications/matter_bridge/sysbuild/mcuboot/prj.conf b/applications/matter_bridge/sysbuild/mcuboot/prj.conf
@@ -15,10 +15,9 @@ CONFIG_FPROTECT=y
 
 CONFIG_MBEDTLS_CFG_FILE="mcuboot-mbedtls-cfg.h"
 
-# Use minimal C library instead of the Picolib
-CONFIG_MINIMAL_LIBC=y
-
 # Bootloader size optimization
+CONFIG_CBPRINTF_NANO=y
+CONFIG_PRINTK=n
 CONFIG_CONSOLE=n
 CONFIG_SERIAL=n
 CONFIG_UART_CONSOLE=n

diff --git a/applications/matter_weather_station/VERSION b/applications/matter_weather_station/VERSION
@@ -1,5 +1,5 @@
 VERSION_MAJOR = 3
-VERSION_MINOR = 0
+VERSION_MINOR = 1
 PATCHLEVEL = 99
 VERSION_TWEAK = 0
 EXTRAVERSION =
diff --git a/applications/nrf_desktop/VERSION b/applications/nrf_desktop/VERSION
@@ -1,5 +1,5 @@
 VERSION_MAJOR = 3
-VERSION_MINOR = 0
+VERSION_MINOR = 1
 PATCHLEVEL = 99
 VERSION_TWEAK = 0
 EXTRAVERSION =
diff --git a/applications/nrf_desktop/application_kconfig.rst b/applications/nrf_desktop/application_kconfig.rst
@@ -52,6 +52,11 @@ You can enable the following HID reports:
 * HID system control report (:ref:`CONFIG_DESKTOP_HID_REPORT_SYSTEM_CTRL_SUPPORT <config_desktop_app_options>`)
 * HID consumer control report (:ref:`CONFIG_DESKTOP_HID_REPORT_CONSUMER_CTRL_SUPPORT <config_desktop_app_options>`)
 
+.. note::
+   nRF Desktop application allows you to modify the used HID input reports or introduce support for a new HID input report.
+   This can be achieved by implementing a custom HID report provider that can be used together with the :ref:`nrf_desktop_hid_state`.
+   For details, see the :ref:`nrf_desktop_hid_state_providing_hid_input_reports` documentation section.
+
 Apart from this, you can specify the supported HID boot protocol interface as one of the following:
 
 * mouse (:ref:`CONFIG_DESKTOP_HID_BOOT_INTERFACE_MOUSE <config_desktop_app_options>`)