| /Zephyr-latest/tests/ztest/error_hook/ |
| D | README.txt | 1 Title: A common fatal error and assert fail handler
6 code writing for fatal and assert handler for error case testing. They can
28 (a) Usage for dealing with fatal error:
53 If you use none of them, you can still define your own fatal or assert handler
60 This test verifies if the common fatal error and assert fail handler works.
69 the (expected) fatal error.
71 the (expected) fatal error.
73 the (expected) fatal error.
74 - start a thread to call k_oops() then catch the (expected) fatal error.
75 - start a thread to call k_panel() then catch the (expected) fatal error.
[all …]
|
| /Zephyr-latest/include/zephyr/ |
| D | fatal.h | 8 * @brief Fatal error functions
24 * @defgroup fatal_apis Fatal error APIs
30 * @brief Halt the system on a fatal error
35 * @param reason Fatal exception reason code
40 * @brief Fatal error policy handler
64 * @param reason The reason for the fatal error
71 * @brief Called by architecture code upon a fatal error.
80 * @param reason The reason for the fatal error
|
| D | fatal_types.h | 8 * @brief Fatal base type definitions
19 * @defgroup fatal_types Fatal error base types
40 /** Arch specific fatal errors */
|
| /Zephyr-latest/subsys/testsuite/ztest/include/zephyr/ |
| D | ztest_error_hook.h | 18 * @brief Set the flag that treat fatal error happened as expected
20 * @details This is used for negative test cases which triggers a fatal
22 * fatal error happened. For normal test case, set it false makes it back
29 /* @brief A hook after fatal error handler
32 * order to deal with some special case when catching the expected fatal
36 * you want to do after fatal error handler.
|
| /Zephyr-latest/doc/kernel/services/other/ |
| D | fatal.rst | 3 Fatal Errors
9 Zephyr provides several methods for inducing fatal error conditions through
49 perform optional runtime checks which will induce a fatal error if the
66 ASSERTION FAIL [foo == 0xF0CACC1A] @ ZEPHYR_BASE/tests/kernel/fatal/src/main.c:367
72 [00:00:00.000,000] <err> os: >>> ZEPHYR FATAL ERROR 4: Kernel panic
147 tests/kernel/fatal/src/main.c: In function 'test_main':
151 tests/kernel/fatal/src/main.c:370:2: note: in expansion of macro 'BUILD_ASSERT'
158 A kernel oops is a software triggered fatal error invoked by
162 The fatal error reason code generated will be ``K_ERR_KERNEL_OOPS``.
167 A kernel error is a software triggered fatal error invoked by
[all …]
|
| /Zephyr-latest/tests/kernel/fatal/message_capture/ |
| D | README | 1 This test case verifies that kernel fatal error logging message can be captured.
3 When the fatal error is triggered, if the debugging message function is turned on,
|
| /Zephyr-latest/samples/posix/eventfd/src/ |
| D | main.c | 15 #define fatal(msg) \ macro
36 fatal("write"); in writer()
52 fatal("read"); in reader()
73 fatal("eventfd"); in main()
|
| /Zephyr-latest/arch/arm/core/cortex_a_r/ |
| D | fault.c | 209 * @return Returns true if the fault is fatal
225 /* Might not be fatal if GDB stub placed it in the code. */ in z_arm_fault_undef_instruction()
236 /* Invoke kernel fatal exception handler */ in z_arm_fault_undef_instruction()
239 /* All undefined instructions are treated as fatal for now */ in z_arm_fault_undef_instruction()
246 * @return Returns true if the fault is fatal
269 /* Fatal */ in z_arm_fault_prefetch()
285 /* Invoke kernel fatal exception handler */ in z_arm_fault_prefetch()
288 /* All prefetch aborts are treated as fatal for now */ in z_arm_fault_prefetch()
324 * @return Returns true if the fault is fatal
343 /* return false - non-fatal error */ in z_arm_fault_data()
[all …]
|
| D | exc_exit.S | 198 * If exiting a nested or non-fatal exception, the exit routine restores the
201 * If exiting a non-nested fatal exception, the exit routine, assuming that the
206 * void z_arm_exc_exit(bool fatal)
208 * @param fatal True if exiting from a fatal fault; otherwise, false
217 /* If the fault is not fatal, return to the current thread context */
222 * If the fault is fatal, the current thread must have been aborted by
|
| /Zephyr-latest/tests/kernel/mem_protect/mem_protect/src/ |
| D | common.c | 15 printk("fatal error expected as part of test case\n"); in k_sys_fatal_error_handler()
18 printk("fatal error was unexpected, aborting\n"); in k_sys_fatal_error_handler()
|
| /Zephyr-latest/tests/net/conn_mgr_conn/src/ |
| D | test_conn_impl.h | 50 /* If nonzero, the implementation should fail to connect and raise this fatal error. */
93 * @brief Simulate a fatal error on the target iface
97 * @param target - iface to simulate fatal error on.
98 * @param reason - Reason to be given for the fatal error.
|
| /Zephyr-latest/kernel/ |
| D | fatal.c | 15 #include <zephyr/fatal.h>
95 /* twister looks for the "ZEPHYR FATAL ERROR" string, don't in z_fatal_error()
98 LOG_ERR(">>> ZEPHYR FATAL ERROR %d: %s on CPU %d", reason, in z_fatal_error()
121 /* If the system fatal error handler returns, then kill the faulting in z_fatal_error()
124 * Policy for fatal errors in ISRs: unconditionally panic. in z_fatal_error()
143 "Attempted to recover from a fatal error in ISR"); in z_fatal_error()
|
| /Zephyr-latest/subsys/testsuite/ztest/src/ |
| D | ztest_error_hook.c | 11 /* This is a flag indicate if treating fatal error as expected, then take
57 printk("Fatal error expected as part of test case.\n"); in k_sys_fatal_error_handler()
62 /* do some action after expected fatal error happened */ in k_sys_fatal_error_handler()
65 printk("Fatal error was unexpected, aborting...\n"); in k_sys_fatal_error_handler()
|
| /Zephyr-latest/soc/raspberrypi/rpi_pico/common/ |
| D | soc.c | 19 #include <zephyr/fatal.h>
25 * Some pico-sdk drivers call panic on fatal error.
|
| /Zephyr-latest/tests/kernel/fatal/message_capture/src/ |
| D | main.c | 32 printk("Fatal error expected as part of test case.\n"); in k_sys_fatal_error_handler()
38 * @brief This test case verifies when fatal error
42 * - When the fatal error is triggered, if the debugging message function
|
| /Zephyr-latest/tests/arch/arm/arm_interrupt/ |
| D | README.txt | 65 E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
72 E: >>> ZEPHYR FATAL ERROR 1: Unhandled interrupt on CPU 0
79 E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
88 E: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
100 E: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
112 E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
123 E: >>> ZEPHYR FATAL ERROR 2: Stack overflow on CPU 0
136 E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
|
| /Zephyr-latest/arch/posix/ |
| D | Kconfig | 39 bool "Raise a SIGTRAP on fatal error"
41 Raise a SIGTRAP signal on fatal error before exiting.
|
| /Zephyr-latest/modules/hal_nordic/nrfs/backends/ |
| D | nrfs_backend_ipc_service.c | 62 * @param fatal true if fatal error and needs special handling
64 __weak void nrfs_backend_error_handler(enum nrfs_backend_error error_id, int error, bool fatal) in nrfs_backend_error_handler() argument
88 if (fatal) { in nrfs_backend_error_handler()
227 LOG_ERR("Fatal error: %d rebooting...", error_id); in nrfs_backend_fatal_error_handler()
|
| /Zephyr-latest/cmake/toolchain/xcc/ |
| D | common.cmake | 18 … message(FATAL "Environment variable TOOLCHAIN_VER must be set or given as -DTOOLCHAIN_VER=<var>")
27 # Not having XTENSA_CORE is not necessarily fatal as
|
| /Zephyr-latest/tests/kernel/sched/schedule_api/src/ |
| D | user_api.c | 94 * the api will trigger a fatal exception
114 * will trigger a fatal error.
155 * will trigger a fatal error.
196 * NULL will trigger a fatal error.
237 * NULL will trigger a fatal error.
269 /* set valid priority value outside the priority range will invoke fatal error */ in thread_priority_set_overmax()
364 * will trigger a fatal error
|
| /Zephyr-latest/samples/arch/mpu/mpu_test/ |
| D | README.rst | 59 <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
75 <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
89 <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
117 <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
130 <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
|
| /Zephyr-latest/tests/kernel/fatal/no-multithreading/ |
| D | README | 1 This test case verifies that kernel fatal error handling works correctly
|
| /Zephyr-latest/tests/arch/riscv/pmp/no-multithreading/src/ |
| D | main.c | 18 TC_PRINT("Fatal error was unexpected, aborting...\n"); in k_sys_fatal_error_handler()
66 * @details Manually write to the protected stack region to trigger fatal error.
|
| /Zephyr-latest/subsys/secure_storage/include/psa/ |
| D | internal_trusted_storage.h | 45 * @retval PSA_ERROR_STORAGE_FAILURE The physical storage has failed (fatal error).
71 * @retval PSA_ERROR_STORAGE_FAILURE The physical storage has failed (fatal error).
92 * @retval PSA_ERROR_STORAGE_FAILURE The physical storage has failed (fatal error).
113 * @retval PSA_ERROR_STORAGE_FAILURE The physical storage has failed (fatal error).
|
| /Zephyr-latest/tests/kernel/fatal/exception/ |
| D | README | 1 This test case verifies that kernel fatal error handling works correctly.
|
