Lines Matching refs:exception

407                             to support dynamic installation of exception
533 FreeRTOS provides a complete set of efficient exception and first-level
534 interrupt handlers installed at the appropriate exception and interrupt
547 usually in RAM. The exception and interrupt handlers are defined in
567 are handled. During interrupt and exception handling, the processor's
579 The following subsections describe the handling of each class of exception
586     exception vector.  The exception type is identified by the EXCCAUSE
588     general exception). This port sets up PS to direct all such exceptions
600     Having allocated the exception stack frame, the user exception handler
606     returned to the code that caused the exception. The user-defined handler
635     'exception mode' bit in the processor status word (PS.EXCM).
648     global 'exception mode' bit in the processor status word (PS.EXCM).
672     processor should a kernel exception occur.
697     A co-processor exception is generated when a task accesses a
703     exception handler performs the context-switch and manages ownership.
706     task. A co-processor exception triggered by code that is not part
714     A debug exception is caused as a result of running code, such as by
728     A double exception is a general exception that happens while the
729     processor is in exception mode (PS.EXCM set), and thus indicates a
730     bug in kernel code. The double exception vector handler triggers
742     Optional hooks are provided in the user exception and low level
748     them. The interrupt/exception hooks are described in xtensa_rtos.h .