pub enum ErrorKind {
Show 20 variants
AssertFailure = 246,
BadOpcode = 242,
BadParam = 226,
CommFail = 240,
ConfigZoneLocked = 1,
DataZoneLocked = 4,
FuncFail = 224,
InvalidId = 227,
InvalidSize = 228,
NotLocked = 248,
ResyncWithWakeup = 232,
RxCrcError = 229,
RxFail = 230,
SmallBuffer = 237,
Timeout = 241,
TooManyCommRetries = 236,
TxFail = 247,
Unimplemented = 245,
UseFlagsConsumed = 252,
WakeFailed = 208,
}
Expand description
A list of specific error causes. Each kind is converted into Error
type.
Variants§
AssertFailure = 246
Code failed run-time consistency check
BadOpcode = 242
opcode is not supported by the device
BadParam = 226
bad argument (out of range, null pointer, etc.)
CommFail = 240
Communication with device failed. Same as in hardware dependent modules.
ConfigZoneLocked = 1
DataZoneLocked = 4
FuncFail = 224
Function could not execute due to incorrect condition / state.
InvalidId = 227
invalid device id, id not set
InvalidSize = 228
Count value is out of range or greater than buffer size.
NotLocked = 248
required zone was not locked
ResyncWithWakeup = 232
Re-synchronization succeeded, but only after generating a Wake-up
RxCrcError = 229
Crc error in data received from device
RxFail = 230
Timed out while waiting for response. Number of bytes received is > 0.
SmallBuffer = 237
Supplied buffer is too small for data required
Timeout = 241
Timed out while waiting for response. Number of bytes received is 0.
TooManyCommRetries = 236
Device did not respond too many times during a transmission. Could indicate no device present.
TxFail = 247
Failed to write
Unimplemented = 245
Function or some element of it hasn’t been implemented yet
UseFlagsConsumed = 252
Use flags on the device indicates its consumed fully
WakeFailed = 208
Device did not respond to wake call as expected