mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-13 22:21:57 +00:00
cdb94d6425
Unlike assertions, these APIs are active at all times. The kernel will treat these errors in the same way as fatal CPU exceptions. Ultimately, the policy of what to do with these errors is implemented in _SysFatalErrorHandler. If the archtecture supports it, a real CPU exception can be triggered which will provide a complete register dump and PC value when the problem occurs. This will provide more helpful information than a fake exception stack frame (_default_esf) passed to the arch-specific exception handling code. Issue: ZEP-843 Change-Id: I8f136905c05bb84772e1c5ed53b8e920d24eb6fd Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
88 lines
2.1 KiB
C
88 lines
2.1 KiB
C
/*
|
|
* Copyright (c) 2014 Wind River Systems, Inc.
|
|
*
|
|
* SPDX-License-Identifier: Apache-2.0
|
|
*/
|
|
|
|
/**
|
|
* @file
|
|
* @brief Fatal fault handling
|
|
*
|
|
* This module implements the routines necessary for handling fatal faults on
|
|
* ARCv2 CPUs.
|
|
*/
|
|
|
|
#include <kernel_structs.h>
|
|
#include <offsets_short.h>
|
|
#include <toolchain.h>
|
|
#include <arch/cpu.h>
|
|
#include <misc/printk.h>
|
|
|
|
const NANO_ESF _default_esf = {
|
|
0xdeaddead, /* placeholder */
|
|
};
|
|
|
|
/**
|
|
*
|
|
* @brief Kernel fatal error handler
|
|
*
|
|
* This routine is called when fatal error conditions are detected by software
|
|
* and is responsible only for reporting the error. Once reported, it then
|
|
* invokes the user provided routine _SysFatalErrorHandler() which is
|
|
* responsible for implementing the error handling policy.
|
|
*
|
|
* The caller is expected to always provide a usable ESF. In the event that the
|
|
* fatal error does not have a hardware generated ESF, the caller should either
|
|
* create its own or use a pointer to the global default ESF <_default_esf>.
|
|
*
|
|
* @return This function does not return.
|
|
*/
|
|
FUNC_NORETURN void _NanoFatalErrorHandler(unsigned int reason,
|
|
const NANO_ESF *pEsf)
|
|
{
|
|
switch (reason) {
|
|
case _NANO_ERR_INVALID_TASK_EXIT:
|
|
printk("***** Invalid Exit Software Error! *****\n");
|
|
break;
|
|
|
|
#if defined(CONFIG_STACK_CANARIES)
|
|
case _NANO_ERR_STACK_CHK_FAIL:
|
|
printk("***** Stack Check Fail! *****\n");
|
|
break;
|
|
#endif
|
|
|
|
case _NANO_ERR_ALLOCATION_FAIL:
|
|
printk("**** Kernel Allocation Failure! ****\n");
|
|
break;
|
|
|
|
case _NANO_ERR_KERNEL_OOPS:
|
|
printk("***** Kernel OOPS! *****\n");
|
|
break;
|
|
|
|
case _NANO_ERR_KERNEL_PANIC:
|
|
printk("***** Kernel Panic! *****\n");
|
|
break;
|
|
|
|
default:
|
|
printk("**** Unknown Fatal Error %d! ****\n", reason);
|
|
break;
|
|
}
|
|
printk("Current thread ID = %p\n"
|
|
"Faulting instruction address = 0x%lx\n",
|
|
k_current_get(),
|
|
_arc_v2_aux_reg_read(_ARC_V2_ERET));
|
|
|
|
/*
|
|
* Now that the error has been reported, call the user implemented
|
|
* policy
|
|
* to respond to the error. The decisions as to what responses are
|
|
* appropriate to the various errors are something the customer must
|
|
* decide.
|
|
*/
|
|
|
|
_SysFatalErrorHandler(reason, pEsf);
|
|
|
|
for (;;)
|
|
;
|
|
}
|