![]() If CONFIG_ESP_PANIC_HANDLER_IRAM is disabled (disabled by default), the panic handler code is placed in flash memory, not IRAM. If the Core Dump feature is enabled, then the system state (task stacks and registers) will be dumped to either Flash or UART, for later analysis. In this case, registers and backtrace are not dumped to the console, and GDBStub / Core Dump functions are not used. If it is, execution will be halted and control will be passed to the debugger. If CONFIG_ESP_DEBUG_OCDAWARE is enabled (which is the default), the panic handler will detect whether a JTAG debugger is connected. The behavior of the panic handler is affected by three other configuration options. ![]() This option allows the user to debug a program at run time and set break points, alter the execution, etc. Start GDB server which can communicate with GDB over console UART port. Invoke dynamic GDB Stub ( ESP_SYSTEM_GDBSTUB_RUNTIME) This option will only provide read-only debugging or post-mortem debugging. Invoke GDB Stub ( CONFIG_ESP_SYSTEM_PANIC_GDBSTUB) Silent reboot ( CONFIG_ESP_SYSTEM_PANIC_SILENT_REBOOT)ĭon’t print registers or backtrace, restart the chip immediately. External reset is required to restart the program. Similar to the above option, but halt instead of rebooting. Print registers and halt ( CONFIG_ESP_SYSTEM_PANIC_PRINT_HALT) This will print register values at the point of the exception, print the backtrace, and restart the chip. Print registers and reboot ( CONFIG_ESP_SYSTEM_PANIC_PRINT_REBOOT) - default option. Subsequent behavior of the panic handler can be set using CONFIG_ESP_SYSTEM_PANIC configuration choice. See Guru Meditation Errors for a list of possible error causes. In all cases, the error cause will be printed in parentheses. Exception was unhandled.įor some of the system level checks (interrupt watchdog, cache access error), the message will be similar to Guru Meditation Error: Core 0 panic'ed (Cache disabled but cached memory region accessed). For CPU exceptions, the message will be similar to Guru Meditation Error: Core 0 panic'ed (IllegalInstruction). The panic handler will start by printing the cause of the error to the console. Panic Handler Įvery error cause listed in the Overview will be handled by the panic handler. This guide explains the procedure used in ESP-IDF for handling these errors, and provides suggestions on troubleshooting the errors. Undefined behavior sanitizer (UBSAN) checksįailed assertions, via assert, configASSERT and similar macros. Task watchdog timeout (only fatal if CONFIG_ESP_TASK_WDT_PANIC is set) In ESP-IDF, these situations include:ĬPU Exceptions: Illegal Instruction, Load/Store Alignment Error, Load/Store Prohibited error, Double Exception. In certain situations, execution of the program can not be continued in a well defined way.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |