tests: drivers: can: Add test for CAN stats init

CAN stats shall be initialized during driver initialization.

Add test which confirms that CAN stats are zeroed before
any start/stop operation.

Signed-off-by: Sebastian Głąb <[email protected]>

Author: nordic-segl

CODEOWNERS

@@ -855,6 +855,7 @@
 /tests/bluetooth/tester/                  @carlescufi @nrfconnect/ncs-paladin
 /tests/crypto/                            @magnev
 /tests/drivers/audio/                     @nrfconnect/ncs-low-level-test
+/tests/drivers/can/                       @nrfconnect/ncs-low-level-test
 /tests/drivers/flash/flash_rpc/           @nrfconnect/ncs-eris
 /tests/drivers/flash_patch/               @nrfconnect/ncs-eris
 /tests/drivers/fprotect/                  @nrfconnect/ncs-eris

scripts/ci/tags.yaml

@@ -1865,3 +1865,7 @@ ci_tests_subsys_rtt:
 ci_tests_subsys_swo:
   files:
     - nrf/tests/subsys/swo/
+
+ci_tests_drivers_can:
+  files:
+    - zephyr/drivers/can/

tests/drivers/can/can_stats_init/CMakeLists.txt

@@ -0,0 +1,13 @@
+#
+# Copyright (c) 2025 Nordic Semiconductor ASA
+#
+# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
+#
+
+cmake_minimum_required(VERSION 3.20.0)
+
+find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
+project(can_stats_init)
+
+FILE(GLOB app_sources src/*.c)
+target_sources(app PRIVATE ${app_sources})

tests/drivers/can/can_stats_init/prj.conf

@@ -0,0 +1,4 @@
+CONFIG_CAN=y
+CONFIG_STATS=y
+CONFIG_CAN_STATS=y
+CONFIG_ZTEST=y

tests/drivers/can/can_stats_init/src/can_stats_init.c

@@ -0,0 +1,51 @@
+/*
+ * Copyright (c) 2025 Nordic Semiconductor ASA
+ *
+ * SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
+ */
+
+#include <zephyr/device.h>
+#include <zephyr/drivers/can.h>
+#include <zephyr/kernel.h>
+
+#include <zephyr/ztest.h>
+
+#define EXPECTED  0
+
+static const struct device *const can_dev = DEVICE_DT_GET(DT_CHOSEN(zephyr_canbus));
+
+/* Test that CAN statistics are cleared during driver initialization.
+ *
+ * Since CAN start/stop will clear CAN stats, it's crucial this test
+ * is executed immediately after CAN driver initialization.
+ */
+ZTEST_USER(can_stats_init, test_can_stats_cleared_during_driver_init)
+{
+	uint32_t val;
+
+	val = can_stats_get_bit_errors(can_dev);
+	zassert_true(val == EXPECTED, "CAN bit errors are too high (%u)", val);
+	val = can_stats_get_bit0_errors(can_dev);
+	zassert_true(val == EXPECTED, "CAN bit0 errors are too high (%u)", val);
+	val = can_stats_get_bit1_errors(can_dev);
+	zassert_true(val == EXPECTED, "CAN bit1 errors are too high (%u)", val);
+	val = can_stats_get_stuff_errors(can_dev);
+	zassert_true(val == EXPECTED, "CAN stuff errors are too high (%u)", val);
+	val = can_stats_get_crc_errors(can_dev);
+	zassert_true(val == EXPECTED, "CAN crc errors are too high (%u)", val);
+	val = can_stats_get_form_errors(can_dev);
+	zassert_true(val == EXPECTED, "CAN form errors are too high (%u)", val);
+	val = can_stats_get_ack_errors(can_dev);
+	zassert_true(val == EXPECTED, "CAN ack errors are too high (%u)", val);
+	val = can_stats_get_rx_overruns(can_dev);
+	zassert_true(val == EXPECTED, "CAN rx overruns are too high (%u)", val);
+}
+
+void *suite_setup(void)
+{
+	zassert_true(device_is_ready(can_dev), "CAN device not ready");
+
+	return NULL;
+}
+
+ZTEST_SUITE(can_stats_init, NULL, suite_setup, NULL, NULL, NULL);

tests/drivers/can/can_stats_init/testcase.yaml

@@ -0,0 +1,12 @@
+common:
+  tags:
+    - drivers
+    - can
+    - ci_tests_drivers_can
+  platform_allow:
+    - nrf54h20dk/nrf54h20/cpuapp
+  integration_platforms:
+    - nrf54h20dk/nrf54h20/cpuapp
+
+tests:
+  drivers.can.can_stats_init: {}