Home
last modified time | relevance | path

Searched refs:fault (Results 1 – 25 of 86) sorted by relevance

1234

/Zephyr-latest/include/zephyr/arch/x86/
Dintel_vtd.h168 #define VTD_FRCD_FR(fault) \ argument
169 ((uint8_t)((fault & VTD_FRCD_FR_MASK) >> VTD_FRCD_FR_POS))
172 #define VTD_FRCD_SID(fault) \ argument
173 ((uint16_t)(fault & VTD_FRCD_SID_MASK))
178 #define VTD_FRCD_FI(fault) \ argument
179 ((fault & VTD_FRCD_FI_MASK) >> VTD_FRCD_FI_POS)
183 #define VTD_FRCD_FI_IR(fault) \ argument
184 ((fault & VTD_FRCD_FI_IR_MASK) >> VTD_FRCD_FI_IR_POS)
/Zephyr-latest/arch/arm/core/cortex_m/
Dfault.c101 static void fault_show(const struct arch_esf *esf, int fault) in fault_show() argument
103 PR_EXC("Fault! EXC #%d", fault); in fault_show()
120 static void fault_show(const struct arch_esf *esf, int fault) in fault_show() argument
123 (void)fault; in fault_show()
784 static void reserved_exception(const struct arch_esf *esf, int fault) in reserved_exception() argument
789 fault < 16 ? "Reserved Exception (" : "Spurious interrupt (IRQ ", in reserved_exception()
790 fault - 16); in reserved_exception()
794 static uint32_t fault_handle(struct arch_esf *esf, int fault, bool *recoverable) in fault_handle() argument
800 switch (fault) { in fault_handle()
828 reserved_exception(esf, fault); in fault_handle()
[all …]
DCMakeLists.txt7 fault.c
/Zephyr-latest/drivers/sensor/maxim/max31790/
DKconfig20 bool "MAX31790 fan fault sensor"
25 Enable driver for the MAX31790 fan fault sensor.
/Zephyr-latest/subsys/bluetooth/mesh/shell/
Dhealth.c325 SHELL_CMD_ARG(fault-get, NULL, "<CID>", cmd_fault_get, 2, 0),
326 SHELL_CMD_ARG(fault-clear, NULL, "<CID>", cmd_fault_clear, 2, 0),
327 SHELL_CMD_ARG(fault-clear-unack, NULL, "<CID>", cmd_fault_clear_unack, 2, 0),
328 SHELL_CMD_ARG(fault-test, NULL, "<CID> <TestID>", cmd_fault_test, 3, 0),
329 SHELL_CMD_ARG(fault-test-unack, NULL, "<CID> <TestID>", cmd_fault_test_unack, 3,
/Zephyr-latest/boards/st/nucleo_l552ze_q/
DKconfig.defconfig12 # This currently conflicts with TF-M MPU setting, resulting in a hard fault.
/Zephyr-latest/arch/arm/core/cortex_a_r/
DCMakeLists.txt7 fault.c
/Zephyr-latest/samples/sensor/thermometer/boards/
Dnucleo_h7a3zi_q.overlay30 consecutive-fault-measurements = <4>;
/Zephyr-latest/arch/arc/core/
DCMakeLists.txt10 fault.c
/Zephyr-latest/boards/st/stm32l562e_dk/
DKconfig.defconfig37 # This currently conflicts with TF-M MPU setting, resulting in a hard fault.
/Zephyr-latest/tests/kernel/common/
Dmultilib.txt19 Fatal fault in essential task ! Spinning...
/Zephyr-latest/boards/nxp/common/
Dsegger-ecc-systemview.rst16 control block a fault will occur, provided that ECC is enabled and the RAM
/Zephyr-latest/tests/arch/arm/arm_interrupt/
DREADME.txt1 Title: Test to verify code fault handling in ISR execution context
9 The first test verifies that we can handle system fault conditions
16 - the ability of the Cortex-M fault handling mechanism to detect
23 the irq_lock() and irq_unlock() functions without triggering a CPU fault,
/Zephyr-latest/tests/arch/x86/static_idt/
DREADME.txt31 Fatal fault in thread 0x001028e0! Aborting.
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dhealth_cli.rst20 fault values.
/Zephyr-latest/boards/renesas/da1469x_dk_pro/
DKconfig.defconfig42 # Increase stack size to avoid raising usage-fault
/Zephyr-latest/samples/arch/mpu/mpu_test/
DREADME.rst16 fault.
96 running the ``mpu run`` command, Zephyr's hard fault handler for AArch32 tries to
97 dereference the program counter from the exception stack frame, causing a second fault
/Zephyr-latest/tests/kernel/mem_protect/stackprot/
DREADME.txt44 Fatal fault in thread 0x00103180! Aborting.
/Zephyr-latest/subsys/logging/
DCMakeLists.txt55 # Cortex-M0 would result in hard fault in mipi_catalog_formatter()
/Zephyr-latest/boards/arm/v2m_beetle/doc/
Dindex.rst101 | 3 | Hard fault | | system fatal error |
103 | 4 | MemManage | MPU fault | system fatal error |
108 | | fault | instruction, | |
/Zephyr-latest/boards/arduino/due/doc/
Dindex.rst85 | 3 | Hard fault | | system fatal error |
87 | 4 | MemManage | MPU fault | system fatal error |
92 | | fault | instruction, | |
/Zephyr-latest/boards/arm/mps2/doc/
Dmps2_an385.rst111 | 3 | Hard fault | | system fatal error |
113 | 4 | MemManage | MPU fault | system fatal error |
118 | | fault | instruction, | |
/Zephyr-latest/drivers/usb_c/tcpc/
Dps8xxx.c609 uint8_t fault; in ps8xxx_alert_work_cb() local
611 tcpci_read_reg8(&cfg->bus, TCPC_REG_FAULT_STATUS, &fault); in ps8xxx_alert_work_cb()
612 tcpci_write_reg8(&cfg->bus, TCPC_REG_FAULT_STATUS, fault); in ps8xxx_alert_work_cb()
614 LOG_DBG("PS8xxx fault: %02x", fault); in ps8xxx_alert_work_cb()
/Zephyr-latest/doc/services/storage/nvs/
Dnvs.rst127 MPU fault while using NVS, or ``-ETIMEDOUT`` error returned
131 disabled, the NVS application will get an MPU fault if it references
133 multi-threaded application, another thread might intercept the fault
/Zephyr-latest/doc/hardware/arch/
Darm_cortex_m.rst29 | Programmable fault | | | |…
221 By design, system fault exceptions have the highest priority level. In
223 is the only available processor fault exception, and its priority is
226 In *Mainline* Cortex-M, the available fault exceptions (e.g. MemManageFault,
229 that the Cortex-M implementation supports configurable fault priorities.)
233 ISRs will be handled by the corresponding fault handler and will not escalate to
244 HardFault. Additional logic in the fault handling routines ensures that such
248 is only shared with the fault exceptions of configurable priority. This simplifies the
249 fault handling routines in Mainline Cortex-M architecture, since runtime kernel errors
296 Mainline Cortex-M fault handling is designed and configured in a way that all processor
[all …]

1234