Samples: Bluetooth: ISO time sync sample on 54h

Port the ISO time sync sample to 54h. This works out of the box and only
some additions are needed to the device tree configuration  set up the
DPPI connection between the GRTC and the LED.

Signed-off-by: Jan Müller <[email protected]>

Author: Tschet1

samples/bluetooth/conn_time_sync/README.rst

@@ -102,10 +102,10 @@ Hardware resource usage
 =======================
 
 This sample requires fewer hardware resources when it is run on an nRF54 Series device compared to the nRF52 or nRF53 Series devices.
-On an nRF54L Series device, only one GRTC channel and PPI channel is needed to set up accurate toggling of an LED.
+On an nRF54L Series device, only one GRTC channel and one PPI channel are needed to set up accurate toggling of an LED.
 On an nRF54H Series device, two local DPPI channels are used to connect the GRTC and the LED to the local PPIB instances.
 A PPIB channel is used to connect the two PPIB instances.
-On nRF52 and nRF53 Series devices, you also need one RTC peripheral, one TIMER peripheral, one EGU channel, three PPI channels, and one PPI group.
+On nRF52 and nRF53 Series devices, you need one RTC peripheral, one TIMER peripheral, one EGU channel, four PPI channels, and one PPI group.
 
 User interface
 **************

samples/bluetooth/iso_time_sync/CMakeLists.txt

@@ -39,8 +39,8 @@ if (CONFIG_SOC_COMPATIBLE_NRF52X)
     target_sources(app PRIVATE src/controller_time_nrf52.c)
 elseif (CONFIG_SOC_COMPATIBLE_NRF5340_CPUAPP)
     target_sources(app PRIVATE src/controller_time_nrf53_app.c)
-elseif (CONFIG_SOC_SERIES_NRF54LX)
-    target_sources(app PRIVATE src/controller_time_nrf54l.c)
+elseif (CONFIG_SOC_SERIES_NRF54LX OR CONFIG_SOC_SERIES_NRF54HX)
+    target_sources(app PRIVATE src/controller_time_nrf54.c)
 else()
     MESSAGE(FATAL_ERROR "Unsupported series")
 endif()

samples/bluetooth/iso_time_sync/Kconfig.sysbuild

@@ -8,3 +8,6 @@ source "${ZEPHYR_BASE}/share/sysbuild/Kconfig"
 
 config NRF_DEFAULT_BLUETOOTH
 	default y
+
+config NETCORE_IPC_RADIO_BT_HCI_IPC
+	default y

samples/bluetooth/iso_time_sync/README.rst

@@ -52,9 +52,12 @@ The sample demonstrates the following features:
       This allows you to measure the minimal end-to-end latency.
 
 .. note::
-   This sample requires less hardware resources when it is run on an nRF54L Series device compared to the nRF52 or nRF53 Series devices.
-   On an nRF54L Series device, only one GRTC channel and PPI channel is needed to set up accurate toggling of an LED.
-   On nRF52 and nRF53 Series devices, you also need one RTC peripheral, one TIMER peripheral, one EGU channel, three PPI channels, and one PPI group.
+   This sample requires fewer hardware resources when it is run on an nRF54 Series device compared to the nRF52 or nRF53 Series devices.
+
+   * On an nRF54L Series device, only one GRTC channel and one DPPI channel are needed to set up accurate toggling of an LED.
+   * On an nRF54H Series device, only one GRTC channel and two local DPPI channels are needed to connect the GRTC and the LED to the local PPIB instances.
+     Additionally, a PPIB channel is used to connect the two PPIB instances.
+   * On nRF52 and nRF53 Series devices, you need one RTC peripheral, one TIMER peripheral, one EGU channel, four PPI channels, and one PPI group.
 
 Configuration
 *************
@@ -209,7 +212,7 @@ The sample code is divided into multiple source files, which makes it easier to
       These files allow the application to read the current timestamp and set up a PPI trigger at a given point in time.
 
       The implementation for nRF52 and nRF53 Series devices is implemented by shadowing an RTC peripheral combined with a timer peripheral.
-      The implementation for nRF54L Series devices uses the GRTC and is simpler to use.
+      The implementation for nRF54 Series devices uses the GRTC and is simpler to use.
 
    .. group-tab:: nRF54 DKs
 
@@ -286,7 +289,7 @@ The sample code is divided into multiple source files, which makes it easier to
       These files allow the application to read the current timestamp and set up a PPI trigger at a given point in time.
 
       The implementation for nRF52 and nRF53 Series devices is implemented by shadowing an RTC peripheral combined with a timer peripheral.
-      The implementation for nRF54L Series devices uses the GRTC and is simpler to use.
+      The implementation for nRF54 Series devices uses the GRTC and is simpler to use.
 
 Building and running
 ********************

samples/bluetooth/iso_time_sync/boards/nrf54h20dk_nrf54h20_cpuapp.conf

@@ -0,0 +1,7 @@
+#
+# Copyright (c) 2024 Nordic Semiconductor
+#
+# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
+#
+
+CONFIG_BT_RX_STACK_SIZE=2048

samples/bluetooth/iso_time_sync/boards/nrf54h20dk_nrf54h20_cpuapp.overlay

@@ -0,0 +1,25 @@
+&dppic130 {
+	status = "okay";
+
+	// Use channel 4 to connect the PPIB to the LED/GPIO
+	owned-channels = <4>;
+	sink-channels = <4>;
+};
+
+&dppic132 {
+	status = "okay";
+
+	// Use channel 4 to connect the GRTC to the PPIB.
+	source-channels = < 4 >;
+	owned-channels = <4>;
+};
+
+&grtc {
+	status = "okay";
+
+	// Change channel 6 to be owned by the application (not child)
+	child-owned-channels = < 0x5>;
+	// Change channel 6 to be secure
+	nonsecure-channels = < 0x5>;
+	owned-channels = < 0x4 0x5 0x6>;
+};

samples/bluetooth/iso_time_sync/sample.yaml

@@ -12,11 +12,13 @@ tests:
       - nrf54l15dk/nrf54l05/cpuapp
       - nrf54l15dk/nrf54l10/cpuapp
       - nrf54l15dk/nrf54l15/cpuapp
+      - nrf54h20dk/nrf54h20/cpuapp
     platform_allow:
       - nrf52840dk/nrf52840
       - nrf52833dk/nrf52833
       - nrf5340dk/nrf5340/cpuapp
       - nrf54l15dk/nrf54l05/cpuapp
       - nrf54l15dk/nrf54l10/cpuapp
       - nrf54l15dk/nrf54l15/cpuapp
+      - nrf54h20dk/nrf54h20/cpuapp
     tags: bluetooth ci_build sysbuild