From ef0d41dece8667d58ded926fb68b8eb86e414698 Mon Sep 17 00:00:00 2001 From: Nordic Builder Date: Mon, 24 Nov 2025 09:22:00 +0000 Subject: [PATCH 1/2] manifest: Update sdk-zephyr revision (auto-manifest PR) Automatically created by action-manifest-pr GH action from PR: https://github.com/nrfconnect/sdk-zephyr/pull/3527 Signed-off-by: Nordic Builder --- west.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/west.yml b/west.yml index b8165f67fd9..ddcd3667b14 100644 --- a/west.yml +++ b/west.yml @@ -64,7 +64,7 @@ manifest: # https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/guides/modules.html - name: zephyr repo-path: sdk-zephyr - revision: 044d5a0445fea6efc85c7f15617c3d57b18cd850 + revision: 3b0588e9fd9fec29fca3a85b8a840bc5ee4315bf import: # In addition to the zephyr repository itself, NCS also # imports the contents of zephyr/west.yml at the above From 11ee57be98b3c492a1906ea4905e139d0c894328 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andrzej=20G=C5=82=C4=85bek?= Date: Mon, 24 Nov 2025 10:24:33 +0100 Subject: [PATCH 2/2] Revert "samples: bluetooth: Fix event_trigger sample on 54h" MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This reverts commit 7d2aca3594059b57a826fe363e11679b7ff9bb57. The workaround is no longer needed as the root cause of the problem (incorrect runtime device PM in the UARTE driver) was fixed. Signed-off-by: Andrzej Głąbek --- .../event_trigger/boards/nrf54h20dk_nrf54h20_cpurad.conf | 2 -- 1 file changed, 2 deletions(-) diff --git a/samples/bluetooth/event_trigger/boards/nrf54h20dk_nrf54h20_cpurad.conf b/samples/bluetooth/event_trigger/boards/nrf54h20dk_nrf54h20_cpurad.conf index a3532aaf681..163e7e35ca6 100644 --- a/samples/bluetooth/event_trigger/boards/nrf54h20dk_nrf54h20_cpurad.conf +++ b/samples/bluetooth/event_trigger/boards/nrf54h20dk_nrf54h20_cpurad.conf @@ -9,5 +9,3 @@ CONFIG_PSA_CRYPTO_DRIVER_OBERON=n CONFIG_PSA_SSF_CRYPTO_CLIENT=y CONFIG_MBEDTLS_PSA_CRYPTO_C=y CONFIG_NRF_SECURITY=y - -CONFIG_PM=n