samples: matter: Switch Application Watchdog to wdt31 for nRF54l15

wdt30 is reserved for Secure purposes and we need to switch to
the wdt31 instance for application purposes.

Signed-off-by: Arkadiusz Balys <arkadiusz.balys@nordicsemi.no>

doc/nrf/protocols/matter/end_product/test_event_triggers.rst

@@ -203,7 +203,7 @@ For example the ``0xFFFFFFFF00011234`` activation code stands for a trigger ID e
 
 .. note::
 
-Activation codes in range from ``0x0000000000000000`` to ``0xFFFFFFFF00000000`` are reserved for Matter stack purposes and should not be defined as custom event triggers.
+   Activation codes in range from ``0x0000000000000000`` to ``0xFFFFFFFF00000000`` are reserved for Matter stack purposes and should not be defined as custom event triggers.
 
 A new event trigger consists of two fields: ``Mask``, and ``Callback``.
 
@@ -262,7 +262,7 @@ To register a new test event trigger, follow these steps:
 
    If the returning `CHIP_ERROR` code is equal to `CHIP_ERROR_NO_MEMORY`, you need to increase the :kconfig:option:`NCS_SAMPLE_MATTER_TEST_EVENT_TRIGGERS_MAX` kconfig option to the higher value.
 
-   Here's an example to handle the ``0xFFFFFFFF00010000`` activation code, where 1234 is the event trigger value field:
+   Here's an example to handle the ``0xFFFFFFFF00011234`` activation code, where 1234 is the event trigger value field:
 
    .. code-block:: c++
 

samples/matter/light_bulb/boards/nrf54l15pdk_nrf54l15_cpuapp_0_2_1.overlay

@@ -11,6 +11,9 @@
 
 		// Configure PWM module for led1 (LED2 on the board)
 		pwm-led1 = &pwm_led1;
+
+		// Use watchdog wdt31 as the application watchdog
+		watchdog0 = &wdt31;
 	};
 
 	pwmleds {
@@ -72,6 +75,6 @@
 	};
 };
 
-&wdt30 {
+&wdt31 {
 	status = "okay";
 };

samples/matter/light_bulb/boards/nrf54l15pdk_nrf54l15_cpuapp_0_3_0.overlay

@@ -12,6 +12,9 @@
 
 		// Configure PWM module for led1 (LED2 on the board)
 		pwm-led1 = &pwm_led1;
+
+		// Use watchdog wdt31 as the application watchdog
+		watchdog0 = &wdt31;
 	};
 
 	pwmleds {
@@ -73,6 +76,6 @@
 	};
 };
 
-&wdt30 {
+&wdt31 {
 	status = "okay";
 };

samples/matter/light_switch/boards/nrf54l15pdk_nrf54l15_cpuapp.overlay

@@ -8,6 +8,9 @@
 	aliases {
 		factory-data = &factory_data;
 		factory-data-memory-region = &rram0;
+
+		// Use watchdog wdt31 as the application watchdog
+		watchdog0 = &wdt31;
 	};
 };
 
@@ -41,6 +44,6 @@
 	};
 };
 
-&wdt30 {
+&wdt31 {
 	status = "okay";
 };

samples/matter/template/boards/nrf54l15pdk_nrf54l15_cpuapp.overlay

@@ -8,6 +8,9 @@
 	aliases {
 		factory-data = &factory_data;
 		factory-data-memory-region = &rram0;
+
+		// Use watchdog wdt31 as the application watchdog
+		watchdog0 = &wdt31;
 	};
 };
 
@@ -41,6 +44,6 @@
 	};
 };
 
-&wdt30 {
+&wdt31 {
 	status = "okay";
 };

samples/matter/thermostat/boards/nrf54l15pdk_nrf54l15_cpuapp.overlay

@@ -8,6 +8,9 @@
 	aliases {
 		factory-data = &factory_data;
 		factory-data-memory-region = &rram0;
+
+		// Use watchdog wdt31 as the application watchdog
+		watchdog0 = &wdt31;
 	};
 };
 
@@ -41,6 +44,6 @@
 	};
 };
 
-&wdt30 {
+&wdt31 {
 	status = "okay";
 };

samples/matter/window_covering/boards/nrf54l15pdk_nrf54l15_cpuapp_0_2_1.overlay

@@ -12,6 +12,9 @@
 		// Configure PWM module for led1 (LED2 on the board)
 		pwm-led1 = &pwm_led1;
 		pwm-led2 = &pwm_led2;
+
+		// Use watchdog wdt31 as the application watchdog
+		watchdog0 = &wdt31;
 	};
 
 	pwmleds {
@@ -76,6 +79,6 @@
 	};
 };
 
-&wdt30 {
+&wdt31 {
 	status = "okay";
 };

samples/matter/window_covering/boards/nrf54l15pdk_nrf54l15_cpuapp_0_3_0.overlay

@@ -12,6 +12,9 @@
 		// Configure PWM module for led1 (LED2 on the board)
 		pwm-led1 = &pwm_led1;
 		pwm-led2 = &pwm_led2;
+
+		// Use watchdog wdt31 as the application watchdog
+		watchdog0 = &wdt31;
 	};
 
 	pwmleds {
@@ -76,6 +79,6 @@
 	};
 };
 
-&wdt30 {
+&wdt31 {
 	status = "okay";
 };