nrfconnect · rlubos · Oct 27, 2024 · Oct 24, 2024 · Oct 25, 2024 · Oct 24, 2024
@@ -14,7 +14,7 @@ jobs:
 
       - name: Install extra python dependencies
         run: |
-          pip3 install west
+          pip3 install --upgrade pip setuptools west
           pip3 install -r ncs/nrf/scripts/requirements-extra.txt
 
       - name: Set upsteam

@@ -60,7 +60,9 @@ jobs:
             mkvirtualenv pip-fixed-venv  > /dev/null 2>&1 || true
             workon pip-fixed-venv  > /dev/null 2>&1
 
-            pip3 install pip-compile-cross-platform==1.4.2 --upgrade > /dev/null 2>&1
+            pip3 install \
+              --extra-index-url https://files.nordicsemi.com/artifactory/api/pypi/nordic-pypi/simple \
+              pip-compile-cross-platform==1.4.2+nordic --upgrade > /dev/null 2>&1
             pip-compile-cross-platform \
               bootloader/mcuboot/scripts/requirements.txt \
               nrf/scripts/requirements-ci.txt \

@@ -49,6 +49,7 @@ jobs:
       - name: Install requirements
         shell: bash
         run: |
+          python3 -m pip install -U pip
           pip3 install -r nrf/scripts/requirements-west-ncs-sbom.txt
           pip3 install -r nrf/scripts/requirements-extra.txt
       - name: Test ncs-sbom with asset tracker sample

@@ -98,6 +98,8 @@
 /doc/nrf/drivers/sensor_sim.rst           @nrfconnect/ncs-si-muffin-doc
 /doc/nrf/drivers/sensor_stub.rst          @nrfconnect/ncs-si-muffin-doc
 /doc/nrf/drivers/uart_ipc.rst             @nrfconnect/ncs-doc-leads
+/doc/nrf/drivers/wifi/                    @sachinthegreen @krish2718
+/doc/nrf/drivers/wifi.rst                 @nrfconnect/ncs-wifi-doc
 /doc/nrf/drivers/uart_nrf_sw_lpuart.rst   @nrfconnect/ncs-doc-leads
 /doc/nrf/external_comp/avsystem.rst       @nrfconnect/ncs-iot-oulu-tampere-doc
 /doc/nrf/external_comp/bt_fast_pair.rst   @nrfconnect/ncs-si-bluebagel-doc
@@ -266,6 +268,7 @@
 /doc/nrf/templates/                       @nrfconnect/ncs-doc-leads
 /doc/nrf/test_and_optimize/               @nrfconnect/ncs-doc-leads
 /doc/nrf/test_and_optimize/optimizing/power_nrf91.rst @nrfconnect/ncs-cia-doc
+/doc/wifi/                                @sachinthegreen @krish2718
 
 /doc/**/*.svg                             @nrfconnect/ncs-doc-leads
 /doc/**/*.png                             @nrfconnect/ncs-doc-leads
@@ -400,7 +403,7 @@
 /samples/app_event_manager/               @nrfconnect/ncs-si-muffin @nrfconnect/ncs-si-bluebagel
 /samples/app_event_manager_profiler_tracer/ @nrfconnect/ncs-si-muffin @nrfconnect/ncs-si-bluebagel
 /samples/benchmarks/coremark/             @nrfconnect/ncs-si-bluebagel
-/samples/bluetooth/broadcast_config_tool/ @nrfconnect/ncs-audio
+/samples/bluetooth/nrf_auraconfig/        @nrfconnect/ncs-audio
 /samples/bluetooth/central_and_peripheral_hr/ @nrfconnect/ncs-si-muffin
 /samples/bluetooth/central_bas/           @nrfconnect/ncs-si-muffin
 /samples/bluetooth/central_hids/          @nrfconnect/ncs-si-bluebagel
@@ -514,13 +517,14 @@
 /samples/wifi/softap/                     @D-Triveni @krish2718
 /samples/wifi/monitor/                    @D-Triveni
 /samples/wifi/promiscuous/                @D-Triveni
+/samples/wifi/offloaded_raw_tx/           @kapbh @sachinthegreen
 /samples/zigbee/                          @nrfconnect/ncs-zigbee
 
 /samples/app_event_manager/*.rst          @nrfconnect/ncs-si-muffin-doc @nrfconnect/ncs-si-bluebagel-doc
 /samples/app_event_manager_profiler_tracer/*.rst @nrfconnect/ncs-si-muffin-doc
 /samples/benchmarks/coremark/*.rst        @nrfconnect/ncs-si-bluebagel-doc
 /samples/bluetooth/**/*.rst               @nrfconnect/ncs-dragoon-doc @nrfconnect/ncs-si-muffin-doc
-/samples/bluetooth/broadcast_config_tool/*.rst @nrfconnect/ncs-audio-doc
+/samples/bluetooth/nrf_auraconfig/*.rst   @nrfconnect/ncs-audio-doc
 /samples/bluetooth/fast_pair/**/*.rst     @nrfconnect/ncs-si-bluebagel-doc
 /samples/bluetooth/mesh/**/*.rst          @nrfconnect/ncs-paladin-doc
 /samples/bootloader/*.rst                 @nrfconnect/ncs-pluto-doc
@@ -593,12 +597,14 @@
 /scripts/west_commands/genboard/          @gmarull
 /scripts/west_commands/sbom/              @nrfconnect/ncs-si-muffin
 /scripts/west_commands/thingy91x_dfu.py   @nrfconnect/ncs-cia
+/scripts/west_commands/ncs-provision.py   @nrfconnect/ncs-pluto
 /scripts/bootloader/                      @nrfconnect/ncs-pluto
 /scripts/ncs-docker-version.txt           @nrfconnect/ncs-ci
 /scripts/print_docker_image.sh            @nrfconnect/ncs-ci
 /scripts/print_toolchain_checksum.sh      @nrfconnect/ncs-ci
 /scripts/sdp/                             @nrfconnect/ncs-ll-ursus
 
+/scripts/docker/*.rst                     @nrfconnect/ncs-doc-leads
 /scripts/hid_configurator/*.rst           @nrfconnect/ncs-si-bluebagel-doc
 /scripts/memfault/*.rst                   @nrfconnect/ncs-cia-doc
 /scripts/nrf_provision/fast_pair/*.rst    @nrfconnect/ncs-si-bluebagel-doc
@@ -611,7 +617,7 @@
 
 # Snippets
 /snippets/ci-shell/                       @nrfconnect/ncs-protocols-serialization
-/snippets/emulated*/                      @nrfconnect/ncs-ll-ursus
+/snippets/sdp/                            @nrfconnect/ncs-ll-ursus
 /snippets/hw-flow-control/                @nrfconnect/ncs-low-level-test @miha-nordic
 /snippets/matter-diagnostic-logs/         @nrfconnect/ncs-matter
 /snippets/nordic-bt-rpc/                  @ppryga-nordic
@@ -708,6 +714,7 @@
 /tests/bluetooth/tester/                  @carlescufi @nrfconnect/ncs-paladin
 /tests/crypto/                            @stephen-nordic @magnev
 /tests/drivers/gpio/egpio_basic_api/      @nrfconnect/ncs-ll-ursus
+/tests/drivers/gpio/gpio_more_loops/      @nrfconnect/ncs-low-level-test
 /tests/drivers/flash/flash_rpc/           @nrfconnect/ncs-pluto
 /tests/drivers/flash_patch/               @nrfconnect/ncs-pluto
 /tests/drivers/fprotect/                  @nrfconnect/ncs-pluto
@@ -763,6 +770,7 @@
 /tests/subsys/emds/                       @balaklaka @nrfconnect/ncs-paladin
 /tests/subsys/event_manager_proxy/        @nrfconnect/ncs-si-muffin
 /tests/subsys/fw_info/                    @nrfconnect/ncs-pluto
+/tests/subsys/kmu/                        @nrfconnect/ncs-pluto
 /tests/subsys/mpsl/                       @nrfconnect/ncs-dragoon
 /tests/subsys/net/lib/aws_*/              @nrfconnect/ncs-cia
 /tests/subsys/net/lib/azure_iot_hub/      @nrfconnect/ncs-cia

@@ -1,4 +1,4 @@
-@Library("CI_LIB") _
+@Library("CI_LIB@v2.8-branch") _
 
 def pipeline = new ncs.sdk_nrf.Main()
 

@@ -16,6 +16,10 @@ config SECURE_BOOT_APPCORE
 config WIFI_NRF70
 	default y if BOARD_THINGY91X_NRF9151_NS
 
+choice WIFI_NRF70_OPER_MODES
+	default WIFI_NRF70_SCAN_ONLY if BOARD_THINGY91X_NRF9151_NS
+endchoice
+
 config PM_EXTERNAL_FLASH_MCUBOOT_SECONDARY
 	default y if BOARD_NRF9151DK_NRF9151_NS || BOARD_NRF9161DK_NRF9161_NS
 	default y if BOARD_NRF9160DK_NRF9160_NS \

@@ -29,3 +29,6 @@ CONFIG_DEBUG_MODULE=y
 # Increase the event storage size so that all metrics generated by the asset tracker application
 # are reliably sent to the memfault cloud.
 CONFIG_MEMFAULT_EVENT_STORAGE_SIZE=2048
+
+# Memfault depends on POSIX, disable unneeded POSIX features
+CONFIG_POSIX_FILE_SYSTEM=n
@@ -57,7 +57,6 @@ CONFIG_BRIDGE_LOG_POWER_DOWN_EVENT=n
 
  # UART
 CONFIG_SERIAL=y
-CONFIG_UART_NRFX_UARTE_LEGACY_SHIM=n
 CONFIG_UART_INTERRUPT_DRIVEN=y
 CONFIG_UART_0_INTERRUPT_DRIVEN=n
 CONFIG_UART_1_INTERRUPT_DRIVEN=n

@@ -98,6 +98,7 @@ config BRIDGE_BUF_SIZE
 
 config BRIDGE_UART_BUF_COUNT
 	int "UART buffer block count"
+	default 16 if BOARD_THINGY91X_NRF5340_CPUAPP
 	default 3
 	range 3 255
 	help

@@ -26,7 +26,7 @@ config PM_EXTERNAL_FLASH_MCUBOOT_SECONDARY
 
 config ML_APP_INCLUDE_REMOTE_IMAGE
 	bool "Include remote image build"
-	depends on SOC_NRF54H20_CPUAPP
+	depends on SOC_NRF54H20_CPUAPP || SOC_NRF54H20_ENGB_CPUAPP
 
 config ML_APP_REMOTE_BOARD
 	string "The name of the board to be used by remote image"

@@ -34,6 +34,9 @@ By default, the following sensors are used by the application:
 * nRF5340 DK - Simulated sensor (:ref:`sensor_sim`).
   The simulated sensor generates predefined waves as acceleration.
   This development kit does not have a built-in accelerometer.
+* nRF54L15 DK - Simulated sensor (:ref:`sensor_sim`).
+  The simulated sensor generates predefined waves as acceleration.
+  This development kit does not have a built-in accelerometer.
 * nRF54H20 DK - The development kit does not have a built-in accelerometer.
   However, it supports the following configurations:
 
@@ -52,6 +55,7 @@ By default, the following transports are used:
 * Thingy:53 uses :ref:`nus_service_readme`.
 * The nRF52840 DK uses :ref:`zephyr:uart_api`.
 * The nRF5340 DK uses :ref:`zephyr:uart_api`.
+* The nRF54L15 DK uses :ref:`zephyr:uart_api`.
 * The nRF54H20 DK uses :ref:`nus_service_readme`.
 
 Machine learning model
@@ -72,7 +76,7 @@ By default, the application uses pre-trained machine learning models deployed in
   * ``tap`` - The device is tapped while placed on a flat surface.
 
   Unknown gestures, such as shaking the device, are recognized as anomalies.
-* Both the nRF52840 DK and the nRF5340 DK use the `nRF Connect SDK simulated sensor machine learning model`_.
+* The nRF52840, nRF5340 and nRF54L15 DKs use the `nRF Connect SDK simulated sensor machine learning model`_.
   The model uses simulated sensor data to recognize the following simulated wave types:
 
   * ``sine``
@@ -232,6 +236,11 @@ By default, the following buttons are used by the application:
       * **Button 1** switches between data forwarding and running a machine learning model.
       * **Button 3** changes the signal generated by the simulated sensor.
 
+   .. group-tab:: nRF54L15 DK
+
+      * **Button 0** switches between data forwarding and running a machine learning model.
+      * **Button 2** changes the signal generated by the simulated sensor.
+
    .. group-tab:: nRF54H20 DK
 
       **Button 0** button switches between data forwarding and running the machine learning model.
@@ -266,30 +275,51 @@ By default, the application uses the following LED effects:
          The LED effect is overridden on the next successful detection.
       * If the device forwards data, the LED color turns red and uses the following blinking patterns:
 
-         * LED blinks slowly if it is not connected.
-         * LED blinks with an average frequency if it is connected but is not actively forwarding data.
-         * LED blinks rapidly if it is connected and is actively forwarding data.
+         * Blinks slowly if it is not connected.
+         * Blinks with an average frequency if it is connected but is not actively forwarding data.
+         * Blinks rapidly if it is connected and is actively forwarding data.
 
    .. group-tab:: nRF52840 and nRF5340 DKs
 
       Both nRF5340 DK and nRF52840 DK use monochromatic LEDs to display the application state.
-      The **LED1** displays the application state, and the **LED2** displays the signal generated by the simulated sensor.
+      The **LED1** displays the application state and the **LED2** displays the signal generated by the simulated sensor.
 
       * If the device is returning the machine learning prediction results, the **LED1** blinks for a predefined number of times and then turns off for a period of time.
         Then the sequence is repeated.
         The machine learning result is represented by the number of blinks:
 
-         * ``sine`` - 1 blink
-         * ``triangle`` - 2 blinks
-         * ``square`` - 3 blinks
-         * ``idle`` - 4 blinks
+         * ``sine`` - one blink
+         * ``triangle`` - two blinks
+         * ``square`` - three blinks
+         * ``idle`` - four blinks
 
          If the machine learning model is running but has not detected anything yet or has detected an anomaly, the **LED1** is breathing.
       * If the device forwards data, the **LED1** has the following blinking patterns:
 
-         * LED blinks slowly if it is not connected.
-         * LED blinks with an average frequency if it is connected but is not actively forwarding data.
-         * LED blinks rapidly if it is connected and is actively forwarding data.
+         * Blinks slowly if it is not connected.
+         * Blinks with an average frequency if it is connected but is not actively forwarding data.
+         * Blinks rapidly if it is connected and is actively forwarding data.
+
+   .. group-tab:: nRF54L15 DK
+
+      The nRF54L15 DK uses monochromatic LEDs to display the application state.
+      The **LED1** displays the application state and the **LED3** displays the signal generated by the simulated sensor.
+
+      * If the device is returning the machine learning prediction results, the **LED1** blinks for a predefined number of times and then turns off for a period of time.
+        Then the sequence is repeated.
+        The machine learning result is represented by the number of blinks:
+
+         * ``sine`` - one blink
+         * ``triangle`` - two blinks
+         * ``square`` - three blinks
+         * ``idle`` - four blinks
+
+         If the machine learning model is running but has not detected anything yet or has detected an anomaly, the **LED1** is breathing.
+      * If the device forwards data, the **LED1** has the following blinking patterns:
+
+         * Blinks slowly if it is not connected.
+         * Blinks with an average frequency if it is connected but is not actively forwarding data.
+         * Blinks rapidly if it is connected and is actively forwarding data.
 
    .. group-tab:: nRF54H20 DK
       nRF54H20 DK uses monochromatic LEDs to display the application state.
@@ -306,9 +336,9 @@ By default, the application uses the following LED effects:
          If the machine learning model is running, but it has not detected anything yet or the ``idle`` state is detected, **LED0**, **LED1**, and **LED2**, keep blinking.
       * If the device forwards data, **LED0**, **LED1** and **LED2** has the following blinking patterns:
 
-         * LED blinks slowly if it is not connected.
-         * LED blinks with an average frequency if it is connected, but is not actively forwarding data.
-         * LED blinks rapidly if it is connected and is actively forwarding data.
+         * Blinks slowly if it is not connected.
+         * Blinks with an average frequency if it is connected, but is not actively forwarding data.
+         * Blinks rapidly if it is connected and is actively forwarding data.
 
 .. _nrf_machine_learning_app_configuration:
 
@@ -525,14 +555,14 @@ After programming the application, perform the following steps to test the nRF M
 
 1. Turn on the development kit.
    The application starts in a mode that runs the machine learning model.
-   Initially, **LED2** displays the LED effect representing ``sine`` wave (1 blink), and **LED1** is breathing, because the signal was not yet recognized by the machine learning model.
+   Initially, **LED2** displays the LED effect representing ``sine`` wave (one blink), and **LED1** is breathing, because the signal was not yet recognized by the machine learning model.
    After a brief delay, the machine learning model recognizes the simulated signal.
    **LED1** and **LED2** display the same LED effect.
 #. Press **Button 3** to change the generated acceleration signal.
    Right after the signal change, the effects displayed by LEDs are different.
-   After a brief delay, the machine learning model recognizes the ``triangle`` wave, and the same effect (2 blinks) is displayed by both LEDs.
+   After a brief delay, the machine learning model recognizes the ``triangle`` wave, and the same effect (two blinks) is displayed by both LEDs.
 #. Press **Button 3** to again change the generated acceleration signal.
-   The ``square`` wave (3 blinks) is displayed only by the **LED2**.
+   The ``square`` wave (three blinks) is displayed only by the **LED2**.
    This signal is marked as an anomaly by the machine learning model, and **LED1** starts breathing.
 #. Press and hold **Button 1** for more than five seconds to switch to the data forwarding mode.
    After the mode is switched, **LED1** starts to blink rapidly.
@@ -545,6 +575,33 @@ After programming the application, perform the following steps to test the nRF M
 Optionally, you can also connect to the device using `Edge Impulse's data forwarder`_ and forward data to `Edge Impulse studio`_ (after logging in).
 See `Forwarding data to Edge Impulse studio`_ for details.
 
+Testing with the nRF54L15 DK
+---------------------------------------
+
+After programming the application, perform the following steps to test the nRF Machine Learning application on the DK:
+
+1. Turn on the development kit.
+   The application starts in a mode that runs the machine learning model.
+   Initially, **LED3** displays the LED effect representing ``sine`` wave (one blink), and **LED1** is breathing, because the signal was not yet recognized by the machine learning model.
+   After a brief delay, the machine learning model recognizes the simulated signal.
+   **LED1** and **LED3** display the same LED effect.
+#. Press **Button 2** to change the generated acceleration signal.
+   Right after the signal change, the effects displayed by LEDs are different.
+   After a brief delay, the machine learning model recognizes the ``triangle`` wave, and the same effect (two blinks) is displayed by both LEDs.
+#. Press **Button 2** to again change the generated acceleration signal.
+   The ``square`` wave (three blinks) is displayed only by the **LED3**.
+   This signal is marked as an anomaly by the machine learning model, and **LED1** starts breathing.
+#. Press and hold **Button 0** for more than five seconds to switch to the data forwarding mode.
+   After the mode is switched, **LED1** starts to blink rapidly.
+#. Connect to the development kit with a terminal emulator (for example, `nRF Connect Serial Terminal`_).
+   See :ref:`test_and_optimize` for the required settings.
+#. Observe the sensor readouts represented as comma-separated values.
+   Every line represents a single sensor readout.
+#. Turn off the terminal emulator to ensure that only one program has access to the data on UART.
+
+Optionally, you can also connect to the device using `Edge Impulse's data forwarder`_ and forward data to `Edge Impulse studio`_ (after logging in).
+See `Forwarding data to Edge Impulse studio`_ for details.
+
 Testing with the nRF54H20 DK
 -----------------------------