Errors
Normative
The error and return codes a conformant MCU driver reports, plus the reset-reason value set.
Development errors are only raised when development error reporting is enabled (see
enable_development_error_reporting in Configuration Reference). Governed by CHI-MCU-MUST-11,
CHI-MCU-MUST-12, and CHI-MCU-MUST-08 (runtime) in Mcu — Requirements.
Development errors
When development error reporting is enabled, each API detects the conditions below and raises the listed error via LogM_Report with development-error level.
API |
Condition |
Error id |
|---|---|---|
|
Driver not in |
|
|
|
|
|
Driver not in |
|
|
|
|
Development error type
Available via: Mcu_DriverTypes.h. Vendor-specific error definitions MUST be provided
via Mcu.h instead.
Runtime errors
Runtime errors are reported via LogM_Report with runtime-error level.
Runtime error type
Defines
-
MCU_RTERR_CLOCK (1U)
Clock setting failure. Typically detected during Mcu_InitClock, Mcu_PollFunction, and an interrupt if supported.
-
MCU_RTERR_CLOCK (1U)
MCU_RTERR_CLOCK is typically detected during Mcu_InitClock, Mcu_PollFunction, or a
supporting interrupt. Available via: Mcu_DriverTypes.h.
Reset reason values
The bit values that make up the uint32 returned by Mcu_GetResetRawValue. A vendor MAY add
more, and MUST omit any reason the hardware cannot detect.