Errors
Normative
The error and return codes a conformant LIN driver reports. Development errors are only raised
when development error reporting is enabled (see enable_development_error_reporting in
Configuration Reference). Governed by CHI-LIN-MUST-16 and CHI-LIN-MUST-17 in
Lin — Requirements.
Development errors
When development error reporting is enabled, each API detects the conditions below and raises the listed error via LogM_Report.
API |
Condition |
Error id |
|---|---|---|
|
Driver not in |
|
|
|
|
|
Driver / channel not initialized |
|
|
|
|
|
Channel not in |
|
Development error type
Defines
-
LIN_DEVERR_INVALID_CH_STATE (4U)
Invalid state transition for the current state
-
LIN_DEVERR_INVALID_CH_STATE (4U)
Available via: LinIf_DriverTypes.h. Vendor-specific error definitions MUST be provided
via Lin.h instead.
Bus errors
Bus errors detected while processing a header or response are reported to the upper layer via
LinIf_OnError(channelId, error) with a value of Lin_ErrorType.
Error id |
Reported when |
|---|---|
|
The received sync field is invalid. |
|
Stop-bit error in the received sync byte or PID byte. |
|
Invalid PID parity bits (optional, hardware-dependent). |
|
Bit error detected during transmission. |
|
Stop-bit error in the transmitted or received response. |
|
Invalid response checksum. |
|
The response is completely missing (optional, hardware-dependent). |
|
The response was only partly received (optional, hardware-dependent). |