Merge branch 'v4.0.99-ncs1-branch' into backport-2743-to-v4.0.99-ncs1-branch

Author: nordic-krch

.github/workflows/manifest-PR.yml

@@ -3,7 +3,7 @@ on:
   pull_request_target:
     types: [opened, synchronize, closed]
     branches:
-      - main
+      - v4.0.99-ncs1-branch
 
 
 jobs:
@@ -15,3 +15,4 @@ jobs:
         with:
           token: ${{ secrets.NCS_GITHUB_TOKEN }}
           manifest-pr-title-details: ${{ github.event.pull_request.title }}
+          base-branch: v3.0-branch

boards/nordic/nrf5340_audio_dk/nrf5340_audio_dk_nrf5340_cpuapp_ns.yaml

@@ -16,3 +16,4 @@ supported:
   - watchdog
   - usb_device
 vendor: nordic
+sysbuild: true

boards/nordic/nrf54l15dk/nrf54l15dk_nrf54l15_cpuapp_ns.yaml

@@ -9,7 +9,6 @@ toolchain:
   - gnuarmemb
   - xtools
   - zephyr
-sysbuild: true
 ram: 256
 flash: 1524
 supported:
@@ -21,3 +20,5 @@ supported:
   - watchdog
   - adc
   - i2s
+vendor: nordic
+sysbuild: true

boards/nordic/nrf7002dk/nrf5340_cpuapp_common.dtsi

@@ -134,6 +134,11 @@
 	status = "okay";
 };
 
+&lfxo {
+	load-capacitors = "internal";
+	load-capacitance-picofarad = <7>;
+};
+
 &adc {
 	status = "okay";
 };

boards/nordic/nrf9131ek/nrf9131ek_nrf9131_ns.yaml

@@ -13,3 +13,5 @@ supported:
   - pwm
   - watchdog
   - netif:modem
+vendor: nordic
+sysbuild: true

boards/nordic/nrf9151dk/nrf9151dk_nrf9151_ns.yaml

@@ -18,3 +18,4 @@ supported:
   - watchdog
   - netif:modem
 vendor: nordic
+sysbuild: true

boards/nordic/nrf9161dk/nrf9161dk_nrf9161_ns_0_7_0.yaml

@@ -18,3 +18,4 @@ supported:
   - watchdog
   - netif:modem
 vendor: nordic
+sysbuild: true

boards/nordic/nrf9161dk/nrf9161dk_nrf9161_ns_0_9_0.yaml

@@ -18,3 +18,4 @@ supported:
   - watchdog
   - netif:modem
 vendor: nordic
+sysbuild: true

boards/nordic/thingy53/thingy53_nrf5340_cpuapp_ns.yaml

@@ -16,3 +16,4 @@ supported:
   - usb_device
   - netif:openthread
 vendor: nordic
+sysbuild: true

doc/connectivity/networking/api/wifi.rst

@@ -42,31 +42,16 @@ Test certificates in PEM format are committed to the repo at :zephyr_file:`sampl
 build process the certificates are converted to a C header file that is included by the Wi-Fi shell
 module.
 
-If you want to use your own certificates, you can replace the existing certificates with your own certificates in the same directory.
-
 .. code-block:: bash
 
-    $ export WIFI_TEST_CERTS_DIR=samples/net/wifi/test_certs/rsa3k
-    $ cp client.pem $WIFI_TEST_CERTS_DIR
-    $ cp client-key.pem $WIFI_TEST_CERTS_DIR
-    $ cp ca.pem $WIFI_TEST_CERTS_DIR
-    $ cp client2.pem $WIFI_TEST_CERTS_DIR
-    $ cp client-key2.pem $WIFI_TEST_CERTS_DIR
-    $ cp ca2.pem $WIFI_TEST_CERTS_DIR
+    $ cp client.pem samples/net/wifi/test_certs/
+    $ cp client-key.pem samples/net/wifi/test_certs/
+    $ cp ca.pem samples/net/wifi/test_certs/
+    $ cp client2.pem samples/net/wifi/test_certs/
+    $ cp client-key2.pem samples/net/wifi/test_certs/
+    $ cp ca2.pem samples/net/wifi/test_certs/
     $ west build -p -b <board> samples/net/wifi -S wifi-enterprise
 
-or alternatively copy ``rsa2k`` certificates by changing the ``WIFI_TEST_CERTS_DIR`` environment variable.
-
-.. code-block:: bash
-
-    $ export WIFI_TEST_CERTS_DIR=samples/net/wifi/test_certs/rsa2k
-
-or you can set the :envvar:`WIFI_TEST_CERTS_DIR` environment variable to point to the directory containing your certificates.
-
-.. code-block:: bash
-
-    $ west build -p -b <board> samples/net/wifi -S wifi-enterprise -- -DWIFI_TEST_CERTS_DIR=<path_to_your_certificates>
-
 Run time certificates
 ---------------------
 
@@ -77,7 +62,7 @@ To facilitate installation of the certificates, a helper script is provided in t
 
 .. code-block:: bash
 
-    $ samples/net/wifi/test_certs/install_certs.py -p samples/net/wifi/test_certs/rsa2k
+    $ ./scripts/utils/wifi_ent_cert_installer.py -p samples/net/wifi/test_certs/rsa2k
 
 The script will install the certificates in the ``rsa2k`` directory to the TLS credentials store in the device over UART and using TLS credentials shell commands.