Error descriptions
Enter the error code you are looking for in the search field:
1: DET
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | ERROR_MEMORY_FULL | Error memory is full, no further error entries can be stored | - |
| 2 | WRITE_ERROR_NEW | Error while writing a new error entry to NVM | ID of the module whose error entry can't be created |
| 3 | WRITE_ERROR_MODIFY | Error while modifying an error entry in the NVM | ID of the module whose error entry can't be modified |
| 4 | WRITE_ERROR_DELETE | Error while deleting an error entry from NVM | ID of the module whose error entry can't be deleted |
2: BSW
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
3: CAN_CFG
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
4: FLASH_IF
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | ERASING | Error while erasing memory block | Status which leads to this error |
| 2 | ERASE_VERIFY | Error while verify erased memory block | Status which leads to this error |
| 3 | PROGRAMMING | Error while programming memory chunk | Start address of the memory chunk that causes the error |
| 4 | PROGRAM_VERIFY | Error while verify programmed memory chunk | 0xFFFFFFFF = At programming end: To less or to much bytes programmed Else = Address where verify failed |
5: PAR_IF_COMMON
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | WRITE_EEPROM | Write to Eeprom/NonVolatileMemory failed |
0 = StayInBootloader flag 1 = Bootloader parameter |
| 2 | VERIFY_EEPROM | Write to Eeprom/NonVolatileMemory failed |
0 = StayInBootloader flag 1 = Bootloader parameter |
6: PAR_IF_BL
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | STAY_IN_BL | "Stay in bootloader" flag can't be set | - |
7: BOOT
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | START_PROGRAM | Problem starting application | - |
| 2 | VERSION_TO_OLD | Firmware version is to old | Old / stored firmware version |
8: CMS_GATEWAY
| Reason ID | Reason | Description | Additional Data |
|
0 |
ASSERT |
Used by the assert function |
Line number in which the assert happened |
|
1 |
TIMEOUT_NONE_EMPTY_RB |
Forward timeout happened while still messages in buffer |
Number of entries in buffer |
|
2 |
SENDING_ERROR |
Error while sending a CAN message |
Error reason (status_t) |
|
3 |
RB_FULL |
Ring buffer is full |
Ring buffer instance (0 =VCU, 1 = CMS) |
|
4 |
UNKNOWN_CAN_ID |
Gateway detected an unknown CAN ID |
The unknown CAN ID |
9: UDS
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | NOT_SUPPORTED_RESET_REQUESTED | Used by the assert function | Reset type which leads to this error |
10: ISO_TP_IF
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | RECEPTION_ERROR | Error while receiving an IsoTP message | Reason for this error |
11: ISO_TP
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
12: VERSION
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
13: OS_TASKS
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | CLOCK | Error while initialize system clock |
1 = INITIALITATION_ERROR 2 = UPDATE_ERROR |
| 2 | SBC_ERROR | Read out of SBC errors is not equals zero | Error count |
| 3 | WDOG_TRG_IN_INIT_LATE | Watchdog was not triggered in time while initialization. |
Byte 0-1: Time since last watchdog trigger Byte 2-3: Number of calls of watchdog trigger |
14: EEPROM_IF
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | INIT_PARTITIONING_FAILED | Unable to partition FlexNVM for Eeprom emulation | Status which leads to this error |
| 2 | INIT_ENABLE_EEE | Unable to configure FlexRAM for Eeprom emulation | Status which leads to this error |
| 3 | INIT_EEPROM_NOT_READY | Unable to configure FlexRAM for Eeprom emulation | Status which leads to this error |
| 4 | WRITE_FAILED | Write to Eeprom failed | Status code of the operation |
| 5 | VERIFY_DISABLE_EEE | Disabling Eeprom emulation while verify failed | Status code of the operation |
| 6 | VERIFY_ENABLE_EEE | Enabling Eeprom emulation while verify failed | Status code of the operation |
| 7 | VERIFY_COMPARE | Data compare failed. Source and destination differ | Address of the destination |
| 8 | QUERY_EEE_STATUS | Querying Eeprom emulation status failed | Status code of the operation |
| 9 | MAINTENANCE_FAILED | Maintenance of quick write data failed | Status code of the operation |
| 10 | QUICK_WRITE_DATA_LOSS | Data loss due to brown out while quick write | - |
| 11 | NORMAL_WRITE_DATA_LOSS | Data loss due to brown out while normal write | - |
| 12 | UNKNOWN_EEE_STATUS | Eeprom emulation status is unknown | Unknown status value |
| 13 | QUICK_WRITE_MAINTENANCE_NECESSARY | Quick Write maintenance required, although Quick Write is never used | - |
| 14 | VERIFY_WAIT_TIMEOUT | Waiting for Eeprom emulation ready timed out while verify failed | - |
| 15 | JTAG_UNLOCK_FAILED | Unlocking the JTAG failed | - |
| 16 | REINIT_EEPROM_NOT_READY | Unable to re-enable Eeprom emulation | - |
| 17 | REINIT_ENABLE_EEE | Unable to configure FlexRAM to re-enable Eeprom emulation | Status which leads to this error |
15: PLATFORM_IF_BL
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | RESTART_MCU_FAILED | Restart of microcontroller via SBC auto wake-up failed | SPI response code (status_t) |
| 2 | HW_CODE_INVALID | Not supported hardware | Measured hardware code resistor value |
| 3 | ADC_CONVERSION_TIMEOUT | HWCode_VFB ADC conversion timeout | - |
16: SECURITY_IF
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | CSEC_UNINITIALIZED | The CSEc is not correctly initialized |
byte 3 & 2: status_t of the function call that failed byte 1 & 0: The line number in which the error occurred |
| 2 | KEY_SLOT_WRITE_FAILED | Writing one of the CSEc's key slots failed |
byte 3 & 2: status_t of the function call that failed byte 1 & 0: The line number in which the error occurred |
| 3 | RANDOM_FAILED | Generating a random value failed |
byte 3 & 2: status_t of the function call that failed byte 1 & 0: The line number in which the error occurred |
| 4 | AES_FAILED | A AES crypto operation failed |
byte 3 & 2: status_t of the function call that failed byte 1 & 0: The line number in which the error occurred |
| 5 | NO_VALID_RS256_KEY_FOUND | No RS256 key for signature validation has been found or the key is invalid |
byte 3 & 2: status_t of the function call that failed byte 1 & 0: The line number in which the error occurred |
17: EEPROM_MANU_IF
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
18: SBC
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | INIT_PARTITIONING_FAILED | Unable to partition FlexNVM for Eeprom emulation | Status which leads to this error |
| 2 | INIT_ENABLE_EEE | Unable to configure FlexRAM for Eeprom emulation | Status which leads to this error |
| 3 | INIT_EEPROM_NOT_READY | Unable to configure FlexRAM for Eeprom emulation | Status which leads to this error |
| 4 | WRITE_FAILED | Write to Eeprom failed | Status code of the operation |
| 5 | VERIFY_DISABLE_EEE | Disabling Eeprom emulation while verify failed | Status code of the operation |
| 6 | VERIFY_ENABLE_EEE | Enabling Eeprom emulation while verify failed | Status code of the operation |
| 7 | VERIFY_COMPARE | Data compare failed. Source and destination differ | Address of the destination |
| 8 | FW_TRIGGER_OS_REGULAR | FW: Triggering of SBC in normal process failed | SPI response code (status_t) |
| 9 | FW_TRIGGER_EEPROM | FW: Triggering of SBC while EEPROM process failed | SPI response code (status_t) |
| 10 | FW_RESET_MCU | FW: Restart of microcontroller via SBC auto wake-up failed | SPI response code (status_t) |
| 11 | FW_GET_FAULT_COUNTER | FW: Read of SBC fault counter failed | SPI response code (status_t) |
| 12 | FW_RELEASE_FS0B | FW: Releasing of FS0B of SBC failed | SPI response code (status_t) |
| 13 | FW_REQUEST_FS0B | FW: Requesting of FS0B of SBC failed | SPI response code (status_t) |
| 14 | FW_SET_LOW_POWER_MODE | FW: Setting of low power mode of SBC failed | SPI response code (status_t) |
| 15 | FW_SET_WAKE_UP_SRC | FW: Setting of wake up sources of SBC failed |
Byte 0 ... 1: SPI response code (status_t) Byte 2 ... 3: Line number in which the error happened |
40: INLET_CTRL
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | NOT_OPEN_IN_OPEN_STATE | Lock feedback is not open in open state | Lock state determined by the ADC feedback values |
| 2 | NOT_CLOSE_IN_CLOSE_STATE | Lock feedback is not close in close state | - |
| 3 | LOCKING_TIMEOUT | Timeout error while closing | - |
| 4 | RELEASING_TIMEOUT | Timeout error while releasing | 0 = Single feedback / single diag feedback 1 = Endstop diag feedback |
| 5 | LOCKFBK_SHORT_TO_GND | Short to GND between fbk+ fbk- |
Byte 0-1: ADC value of LockFbk_CFB Byte 2-3: ADC value of LockFbk_VFB |
| 6 | LOCKFBK_SHORT_TO_BAT_OR_OL | Short to BAT or open load between fbk+ fbk- |
Byte 0-1: ADC value of LockFbk_CFB Byte 2-3: ADC value of LockFbk_VFB |
| 7 | LOCKFBK_OUT_OF_RANGE | Measured resistance is out of range of the configured parameters |
Byte 0-1: ADC value of LockFbk_CFB Byte 2-3: ADC value of LockFbk_VFB |
| 8 | LOCKFBK_PARAMETER_OVERLAP | Configured parameters do overlap | - |
| 9 | LOCKFBK_PARAMETER_MIN_GREATER_OR_EQUAL_MAX | Configured parameter MIN >= MAX | - |
| 10 | LOCKFBK_PARAMETER_NOT_DIAGNOSABLE | Configured parameter < 500Ohm and therefore cannot be diagnosed | - |
| 11 | SELFTEST | Error detected in selftest |
Byte 0-1: ADC value of LockFbk_CFB Byte 2: 0: Parameter invalid 1: Parameter valid |
| 12 | STATE_MACHINE | Error processing a state machine |
0 = Default state activated Else = Line in which the error happened |
| 13 | LOCKFBK_MALFUNCTION | Lock feedback measurement is faulty. |
Byte 0-1: ADC value of LockFbk_CFB Byte 2-3: ADC value of LockFbk_VFB |
41: LED_CTRL
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | INTENSITY_INVALID | Led intensity is invalid | intensity in 1 per mill |
42: SWITCH_CTRL
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 2 | STATE_MACHINE | Error while process a state machine | Line number in which the error happened |
| 3 | UNKWON_CONNECTION_TYPE | Unknown connection type (Not directly nor via CAN) | Value which leads to this error |
| 4 | SWITCH1_SHORT_TO_BAT_HS | HV-Switch 1: Short to battery (probably on the high side) | Byte 0-1: ADC value of HS_VFB Byte 2-3: ADC value of LS_VFB |
| 5 | SWITCH2_SHORT_TO_BAT_HS | HV-Switch 2: Short to battery (probably on the high side) | Byte 0-1: ADC value of HS_VFB Byte 2-3: ADC value of LS_VFB |
| 6 | SWITCH1_SHORT_TO_BAT_LS | ||
| 7 | SWITCH2_SHORT_TO_BAT_LS | ||
| 8 | SWITCH1_OPEN_LOAD | ||
| 9 | SWITCH2_OPEN_LOAD | ||
| 10 | SWITCH1_SHORT_TO_GND_HS | ||
| 11 | SWITCH2_SHORT_TO_GND_HS | ||
| 12 | SWITCH1_SHORT_TO_GND_LS | ||
| 13 | SWITCH2_SHORT_TO_GND_LS | ||
| 14 | SWITCH1_DIAG_DEFECT_HS | ||
| 15 | SWITCH2_DIAG_DEFECT_HS | ||
| 16 | SWITCH1_NO_POWER_SUPPLY | ||
| 17 | SWITCH2_NO_POWER_SUPPLY | ||
| 18 | SWITCH1_FS0B_NOT_RELEASED | ||
| 19 | SWITCH2_FS0B_NOT_RELEASED | ||
| 20 | SWITCH1_SBC_COM_ERROR | ||
| 21 | SWITCH2_SBC_COM_ERROR | ||
| 22 | SWITCH1_OVER_LOAD | ||
| 23 | SWITCH2_OVER_LOAD | ||
| 24 | SWITCH1_STATE_COMBINATION | ||
| 25 | SWITCH2_STATE_COMBINATION | ||
| 26 | SWITCH1_WELDED | ||
| 27 | SWITCH2_WELDED | ||
| 28 | SWITCH1_REPORTED | ||
| 29 | SWITCH2_REPORTED | ||
| 30 | SWITCH1_OPEN_LOAD_OR_SHORT_TO_BAT | ||
| 31 | SWITCH2_OPEN_LOAD_OR_SHORT_TO_BAT | ||
| 32 | SWITCH1_OPEN_LOAD_OR_SHORT_TO_GND | ||
| 33 | SWITCH2_OPEN_LOAD_OR_SHORT_TO_GND | ||
| 34 | SWITCH1_UNKNOWN_ERROR_REASON | ||
| 35 | SWITCH2_UNKNOWN_ERROR_REASON |
43: TEMP_CTRL
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 2 | STATE_MACHINE | Error while process a state machine | Line number in which the error happened |
| 3 | UNKWON_CONNECTION_TYPE | Unknown connection type (Not directly nor via CAN) | Value which leads to this error |
| 4 | SWITCH1_SHORT_TO_BAT_HS | HV-Switch 1: Short to battery (probably on the high side) | Byte 0-1: ADC value of HS_VFB Byte 2-3: ADC value of LS_VFB |
| 5 | SWITCH2_SHORT_TO_BAT_HS | HV-Switch 2: Short to battery (probably on the high side) | Byte 0-1: ADC value of HS_VFB Byte 2-3: ADC value of LS_VFB |
| 6 | SWITCH1_SHORT_TO_BAT_LS | ||
| 7 | SWITCH2_SHORT_TO_BAT_LS | ||
| 8 | SWITCH1_OPEN_LOAD | ||
| 9 | SWITCH2_OPEN_LOAD | ||
| 10 | SWITCH1_SHORT_TO_GND_HS | ||
| 11 | SWITCH2_SHORT_TO_GND_HS | ||
| 12 | SWITCH1_SHORT_TO_GND_LS | ||
| 13 | SWITCH2_SHORT_TO_GND_LS | ||
| 14 | SWITCH1_DIAG_DEFECT_HS | ||
| 15 | SWITCH2_DIAG_DEFECT_HS | ||
| 16 | SWITCH1_NO_POWER_SUPPLY | ||
| 17 | SWITCH2_NO_POWER_SUPPLY | ||
| 18 | SWITCH1_FS0B_NOT_RELEASED | ||
| 19 | SWITCH2_FS0B_NOT_RELEASED | ||
| 20 | SWITCH1_SBC_COM_ERROR | ||
| 21 | SWITCH2_SBC_COM_ERROR | ||
| 22 | SWITCH1_OVER_LOAD | ||
| 23 | SWITCH2_OVER_LOAD | ||
| 24 | SWITCH1_STATE_COMBINATION | ||
| 25 | SWITCH2_STATE_COMBINATION | ||
| 26 | SWITCH1_WELDED | ||
| 27 | SWITCH2_WELDED | ||
| 28 | SWITCH1_REPORTED |
44: ADC_IF
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | STATEMACHINE | Error while process a state machine | State which leads to this error |
| 2 | PROCESS | Start next ADC conversion before the previous is finished |
0 = ADC 0 1 = ADC 1 |
45: PIN_IF
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
46: PWM_IF
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Execution disrupted from assert | Line number in which the assert happened |
| 1 | WRONG_DUTY_CYCLE_MEASURED | Wrong duty cycle (or frequency) measured | Measured duty cycle |
| 2 | WRONG_FREQUENCY_SET | Invalid duty cycle set | Frequency to be set |
| 3 | WRONG_DUTY_CYCLE_SET | Invalid duty cycle set | Duty cycle to be set |
47: CMS_COM
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Execution disrupted from assert | Line number in which the assert happened |
| 1 | MAILBOX_FULL | Tx mailbox is full, sending not possible | CAN message ID which can't be sent |
| 2 | SEND_EMPTY_MSG | Try to send an empty CAN message | CAN ID of the empty message to be sent |
| 3 | CAN_ERROR_HAPPENED | CAN controller reports error | Content of CAN error and status register 1 (ESR1) |
48: DIAGNOSTIC_COM
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Execution disrupted from assert | Line number in which the assert happened |
| 1 | MAILBOX_FULL | Tx mailbox is full, sending not possible | CAN message ID which can't be sent |
| 2 | SEND_EMPTY_MSG | Try to send an empty CAN message | CAN ID of the empty message to be sent |
49: VCU_COM
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Execution disrupted from assert | Line number in which the assert happened |
| 1 | MAILBOX_FULL | Tx mailbox is full, sending not possible | CAN message ID which can't be sent |
| 2 | SEND_EMPTY_MSG | Try to send an empty CAN message | CAN ID of the empty message to be sent |
| 3 | CAN_ERROR_HAPPENED | CAN controller reports error | Content of CAN error and status register 1 (ESR1) |
50: APP_CRG_CTRL
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Execution disrupted from assert | Line number in which the assert happened |
| 1 | WELDING_BY_SEQ_DENIED | Start of "welding detection by sequence" denied | - |
| 2 | SWITCH_WELDED | At least one contactor is welded | - |
| 8 | PARAMETER_ERROR_REDPWR_TEMPERATURE | Reduce power Parameter mismatch Min Value > Max Value. | none |
51: ADC_CFG
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
52: FTM_CFG
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
53: PWM_CFG
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
54: PILOT_CTRL
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | FREQUENCY | Frequency out of range | Measured frequency |
| 2 | UNKNOWN_INLET | Incorrect inlet type parameterized | Inlet type which leads to this error |
| 3 | PP_DECTECTION_ERROR | PP resistor is in invalid range |
Byte 0-1: ADC value of PP_CFB Byte 2-3: ADC value of PP_VFB |
| 4 | DUTY_CYCLE | Duty cycle out of range | Measured duty cycle |
| 5 | SELFTEST_FAILED | PP Self test failed (values not low in case of disabled) |
Byte 0-1: Measured ADC current at PP Byte 2-3: Measured ADC voltage at PP |
| 6 | CP_INVALID_VFB | No valid ADC values for CP_VFB | CP_VFB |
| 7 | CP_VOLTAGE_OUT_RANGE | CP voltage out of range | CP_VFB |
| 8 | PP_ADC_INVALID | No valid ADC values for PP_VFB or PP_CFB |
Byte 0-1: ADC value of PP_CFB Byte 2-3: ADC value of PP_VFB |
| 9 | OPEN_LOAD |
ProximityPilot: Open load was detected. PP_VFB is smaller then PP_CFB. This is an indicator that the PP resistor is not connected. |
Byte 0-1: ADC value of PP_CFB Byte 2-3: ADC value of PP_VFB |
55: PAR_IF_APP
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | STRUCT | The parameter structures of the application and NVM are not compatible | Hash of the parameter set stored in EEPROM |
| 2 | CHECKSUM | Parameter checksum is bad | Calculated checksum |
| 3 | STAY_IN_BL | "Stay in bootloader" flag can't be set | - |
| 4 | SET_QUALI_OPERATION_STATE | Error while writing quali operation state to EEPROM | - |
| 5 | RANGE_CHECK_FAILED |
Parameter range check failed. At least one parameter is not in range: - Boolean is not true or false - Enum is larger as its last enum value - Integer is smaller as minimum value or larger as maximum value |
Byte 0: Last boolean parameter which failed Byte 1: Last enum parameter which failed Byte 2: Last signed integer parameter which failed Byte 3: Last unsigned integer parameter which failed |
| 6 | WRITE_DEFAULT_PARAMETER | Default parameter set can't be written to EEPROM | - |
56: BTN_CTRL
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | NO_ERROR | No error; should not be reported | - |
| 2 | STATE_MACHINE | Programming failure in state machine | State which leads to this error |
| 3 | PARMAETER_BTNTYPE_INVALID | Programming failure in btnCtrl_DetermineButtonState | Button type which leads to this error |
| 4 | PARAMETER_OVERLAP | Parameter ranges overlap, therefore no detection of the button possible | - |
| 5 | PARAMETER_OUT_OF_RANGE | Parameter out of range, therefore no detection of open load, short to ground possible | - |
| 6 | PARAMETER_LOW_GREATER_HIGH | Parameter low > high | - |
| 7 | OPEN_LOAD | Open load detected | ADC value of BTN_VFB |
| 8 | SHORT_TO_GROUND | Short circuit to ground detected | ADC value of BTN_VFB |
| 9 | OUT_OF_RANGE | Measured values out of range / invalid | ADC value of BTN_VFB |
| 10 | SENSOR_MALFUNCTION | Button sensor malfunction detected | VFB as ADC value |
57: DEBOUNCED_PIN_IF
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
58: MAIN
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | NO_ERROR | Cycle time was exceeded | Time which leads to this error |
| 2 | STATE_MACHINE | OsTasks_Input was not called | - |
| 3 | PROCESS_NOT_CALLED | OsTasks_Process was not called | - |
| 4 | OUTPUT_NOT_CALLED | OsTasks_Output was not called | - |
| 5 | WRONG_HW_DETECTED | Wrong hardware (e.g. B-Sample) detected | Detected hardware (numerical representation) |
59: SAFETY_CTRL
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | STATE_MACHINE | Programming failure in state machine | State which leads to this error |
| 2 | RESET_TYPE_NOT_SUPPORTED | UDS Reset type not supported | Value of reset type |
| 3 | E2E_PROTECTION_PARAM_INVALID | E2E Protection parameter error | - |
| 4 | E2E_PROTECTION_CRC_WRONG | E2E Protection: checksum wrong |
Byte 0: received checksum Byte 1: calculated checksum |
| 5 | E2E_PROTECTION_SEQ_WRONG | E2E Protection: sequence counter wrong |
Byte 0: received sequence counter Byte 1: previous sequence counter |
60: AVG_ADC_IF
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | UNABLE_TO_MEASURE_CP_VOLTAGE | Although a CP signal was detected, it was not possible to measure it. | - |
61: RTV
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
62: CRG_COM
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | MAILBOX_FULL | Tx mailbox is full, sending not possible | CAN message ID which can't be sent |
| 2 | SEND_EMPTY_MSG | Try to send an empty CAN message | CAN ID of the empty message to be sent |
| 3 | CAN_ERROR_HAPPENED | CAN controller reports error | Content of CAN error and status register 1 (ESR1) |
63: DIAGNOSTIC_COM_CMS
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | MAILBOX_FULL | Tx mailbox is full, sending not possible | CAN message ID which can't be sent |
| 2 | SEND_EMPTY_MSG | Try to send an empty CAN message | CAN ID of the empty message to be sent |
64: SHB
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | OPEN_LOAD | Open load between Motor+ Motor- | Read error status |
| 2 | SHORT_TO_GND_OUTPUT_1 | Short to GND Motor+ | Read error status |
| 3 | SHORT_TO_GND_OUTPUT_2 | Short to GND Motor- | Read error status |
| 4 | SHORT_TO_POWER_OUTPUT_1 | Short to BAT Motor+ | Read error status |
| 5 | SHORT_TO_POWER_OUTPUT_2 | Short to BAT Motor- | Read error status |
| 6 | VPWR_OVERVOLTAGE | VPWR over voltage | Read error status |
| 7 | VPWR_UNDERVOLTAGE | VPWR undervoltage | Read error status |
| 8 | CHARGE_PUMP_UNDERVOTALGE | Charge pump undervoltage | Read error status |
| 9 | SPI_FRAMING_ERROR | SPI framing error | Read error status |
| 10 | OVERCURRENT | Overcurrent | Read error status |
| 11 | THERMAL_WARNING | Thermal warning | Read error status |
| 12 | OVERTEMPERATURE_SHUTDOWN | Overtemperature shutdown | Read error status |
| 13 | SPI_ERROR | Error while SPI communication with SHB | Status which leads to this error |
| 14 | STATE_MACHINE | Error processing a state machine | State which leads to this error |
65: PLATFORM_IF
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | CL30_OVER_VOLTAGE | CL30 over voltage | CL30 ADC VFB |
| 2 | CL30_CRITICAL_OVER_VOLTAGE | CL30 critical over voltage that can damage HW | CL30 ADC VFB |
| 3 | CL30_UNDER_VOLTAGE | CL30 under voltage | CL30 ADC VFB |
| 4 | CL30_OVER_CURRENT | CL30 over current | CL30 ADC VFB |
| 5 | HMI_SUPPLY | Internal power distribution detected an error at HMISupply output | - |
| 6 | SENSOR_SUPPLY | Internal power distribution detected an error at SenosorSupply output | - |
| 7 | POWER_SUPPLY | Internal power distribution detected an error for internal supply | - |
| 8 | SBC_OVER_TEMPERATURE | Over temperature of SBC | SBC temperature [°C] |
| 9 | NTC_OVER_TEMPERATURE | Over temperature NTC | NTC temperature [°C] |
| 10 | HW_CODE_INVALID | Not supported hardware | Measured hardware code resistor value |
| 11 | RESTART_MCU_FAILED | Restart of microcontroller via SBC auto wake-up failed | SPI response code (status_t) |
| 12 | ADC_CONVERSION_TIMEOUT | HWCode_VFB ADC conversion timeout. | - |
66: QUALI
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | TEMP1_OUT_OF_RANGE | Temperature Value out or Range | Actually measured temperature |
| 2 | TEMP2_OUT_OF_RANGE | Temperature Value out or Range | Actually measured temperature |
| 3 | TEMP3_OUT_OF_RANGE | Temperature Value out or Range | Actually measured temperature |
| 4 | TEMP4_OUT_OF_RANGE | Temperature Value out or Range | Actually measured temperature |
| 5 | PP_OUT_OF_RANGE | Temperature Value out or Range | PP state |
| 6 | BTN_OUT_OF_RANGE | Temperature Value out or Range | Button state |
| 7 | PLC_ERROR | CMS PLC CAN error | CMS error number except 0, 1, 5 (always active with multiple PLCs) |
| 8 | SELFTEST_INTERRUPT | Selftest execution was interrupted | Index of last executed test. |
| 9 | SELFTEST_FAILED | At least one selftest test failed | Index of last executed test |
| 10 | SELFTEST_RANGE | Selftest called with wrong range. | - |
| 11 | SELFTEST_STIMULATED | Selftest found successful stimulation but stimulation is disabled. | Index of last executed test |
| 12 | IL1_CFB_OUT_OF_RANGE | Interlock 1 CFB measurement out of range for active or inactive state | Actual ADC value |
| 13 | IL1_VFB_OUT_OF_RANGE | Interlock 1 VFB measurement out of range for active or inactive state | Actual ADC value |
| 14 | IL2_CFB_OUT_OF_RANGE | Interlock 2 CFB measurement out of range for active or inactive state | Actual ADC value |
| 15 | IL2_VFB_OUT_OF_RANGE | Interlock 2 VFB measurement out of range for active or inactive state | Actual ADC value |
| 16 | SM_TIMEOUT | State machine timeout | code line of occurrence |
| 17 | CHARGE_CAN | Charging CAN communication error | actual received value |
| 18 | LED_ERROR | LED Status error |
Byte 0: Status LEDCTRL_TPS92518_LED_3_4 Byte 1: Status LEDCTRL_TPS92518_LED_1_2 |
| 19 | TEMP1_STATUS_NOK | Temperature sensor 1 status is not ok | Error reason (see TempCtrl_Status_t) |
| 20 | TEMP2_STATUS_NOK | Temperature sensor 2 status is not ok | Error reason (see TempCtrl_Status_t) |
| 21 | TEMP3_STATUS_NOK | Temperature sensor 3 status is not ok | Error reason (see TempCtrl_Status_t) |
| 22 | TEMP4_STATUS_NOK | Temperature sensor 4 status is not ok | Error reason (see TempCtrl_Status_t) |
67: STACK_MONITOR
| Reason ID | Reason | Description | Additional Data |
| 0 | STACK_UNDERFLOW | A stack underflow was detected | - |
| 1 | STACK_OVERFLOW | A stack overflow was detected | - |
68: IRQ_MONITOR
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | ADC0 | Interrupt handler for ADC0 was called unintentionally. | - |
| 2 | ADC1 | Interrupt handler for ADC1 was called unintentionally. | - |
| 3 | CAN0_WARNING | Interrupt handler for CAN0 (bus off, Tx/Rx warning) was called unintentionally. | - |
| 4 | CAN0_ERROR | Interrupt handler for CAN0 (Error) was called unintentionally. | - |
| 5 | CAN0_WAKE_UP | Interrupt handler for CAN0 (WakeUp) was called unintentionally. | - |
| 6 | CAN0_0_15_MB | Interrupt handler for CAN0 (Mailbox 0 ... 15) was called unintentionally. | - |
| 7 | CAN0_16_31_MB | Interrupt handler for CAN0 (Mailbox 16 ... 31) was called unintentionally. | - |
| 8 | CAN1_WARNING | Interrupt handler for CAN1 (bus off, Tx/Rx warning) was called unintentionally. | - |
| 9 | CAN1_ERROR | Interrupt handler for CAN1 (Error) was called unintentionally. | - |
| 10 | CAN1_0_15_MB | Interrupt handler for CAN1 (Mailbox 0 ... 15) was called unintentionally. | - |
| 11 | CAN1_16_31_MB | Interrupt handler for CAN1 (Mailbox 16 ... 31) was called unintentionally. | - |
| 12 | CAN2_WARNING | Interrupt handler for CAN2 (bus off, Tx/Rx warning) was called unintentionally. | - |
| 13 | CAN2_ERROR | Interrupt handler for CAN2 (Error) was called unintentionally. | - |
| 14 | CAN2_0_15_MB | Interrupt handler for CAN2 (Mailbox 0 ... 15) was called unintentionally. | - |
| 15 | FTM2_CH2_CH3 | Interrupt handler for FTM2 Channel2/3 was called unintentionally. | - |
| 16 | ADC0_SEQUENCE | ADC0: Problem with the conversion sequence in this conversion group |
Byte 0: Index of the conversion group Byte 1: Enable channel mask Byte 2: Complete channel mask Byte 3: Error channel mask |
| 17 | ADC1_SEQUENCE | ADC1: Problem with the conversion sequence in this conversion group |
Byte 0: Index of the conversion group Byte 1: Enable channel mask Byte 2: Complete channel mask Byte 3: Error channel mask |
| 18 | ADC0_STATUS | ADC0: Error in status register SC2 | Content of ADC.SC2 |
| 19 | ADC1_STATUS | ADC1: Error in status register SC2 | Content of ADC.SC2 |
| 20 | ADC0_COCO | ADC0: A conversion complete flag of a configured ADC channel is not set |
Byte 0: Conversion group Byte 1: Index of configured channel |
| 21 | ADC1_COCO | ADC1: A conversion complete flag of a configured ADC channel is not set |
Byte 0: Conversion group Byte 1: Index of configured channel |
| 22 | NMI_FAULT | NMI fault | Content of the Configurable Fault Status Register |
| 23 | HARD_FAULT | Hard fault | Content of Hard Fault Status Register |
| 24 | MEMORY_MANAGEMENT | Memory Management fault | Address causing the bus MemManage fault |
| 25 | BUS_FAULT | Bus fault | Address causing the bus fault |
| 26 | USAGE_FAULT | Usage fault | Content of the Configurable Fault Status Register |
| 27 | ERM_DOUBLE_FAULT | ECC fault in SRAM_L or SRAM_U (ERM ECC double bit fault) | Address where the ECC fault happened 0xFFFFFFFF = Fault address can't be determined. |
| 28 | UNUSED_INTERRUPT | Unused Interrupt executed | Interrupt number |
| 29 | FTFC_DOUBLE_FAULT | FTFC ECC double bit fault | - |
| 30 | MPU_FAULT | MPU detected an address violation | The address causing the violation |
| 31 | UNKNOWN_BUS_FAULT | Bus fault happened but reason is unknown | - |
69: SPI
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | SLEEP_WAKE | SPI driver returned an error in module sleep wake |
Byte 0 ... 1: Status of SPI communication (status_t) Byte 2 ... 3: Line number in which the error was reported |
70: INTERLOCKCTRL
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | IL1_MALFUNCTION | Malfunction of the interlock 1 circuit |
Byte 0-1: Measured CFB Byte 2-3: Measured VFB |
| 2 | IL2_MALFUNCTION | Malfunction of the interlock 2 circuit |
Byte 0-1: Measured CFB Byte 2-3: Measured VFB |
| 3 | IL1_S2BAT | Open load or short to battery detected at il1 |
Byte 0-1: Measured CFB Byte 2-3: Measured VFB |
| 4 | IL2_S2BAT | Open load or short to battery detected at il2 |
Byte 0-1: Measured CFB Byte 2-3: Measured VFB |
| 5 | IL1_S2GND | Short to GND detected at il1 |
Byte 0-1: Measured CFB Byte 2-3: Measured VFB |
| 6 | IL2_S2GND | Short to GND detected at il2 |
Byte 0-1: Measured CFB Byte 2-3: Measured VFB |
| 7 | IL1_OUT_OF_RANGE | Measured resistor is out of range at il1 | Measured resistor value |
| 8 | IL2_OUT_OF_RANGE | Measured resistor is out of range at il2 | Measured resistor value |
| 9 | IL2_CROSSCONNECTION | Cross connection detected |
Byte 0-1: Measured CFB Byte 2-3: Measured VFB |
| 10 | SEQUENCE_STATE_ERROR | Invalid interlock sequence state | - |
71: TPS92518
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | LED_1_BOOTUV_ERROR | Under voltage reported by TPS92518. Also signals an open load. | Which chip was selected |
| 2 | LED_2_BOOTUV_ERROR | Under voltage reported by TPS92518. Also signals an open load. | Which chip was selected |
| 3 | THERMAL_WARNING | Thermal warning reported by TPS92518 | Which chip was selected |
| 4 | SPI_FRAME_ERROR | SPI frame error reported by TPS92518 | Which chip was selected |
| 5 | POWER_CYCLED | Power cycle occurred since last read of the status register | Which chip was selected |
| 6 | SPI | SPI driver returned an error in module Tps92518If | Line number in which the error was reported |
72: CORE_MONITOR
| Reason ID | Reason | Description | Additional Data |
| 0 | INTERRUPTED | Selftest execution was interrupted | |
| 1 | FAILED | At least one selftest test failed | |
| 2 | RANGE | Selftest called with wrong range. | |
| 3 | STIMULATED | Selftest found successful stimulation but stimulation is disabled. | |
| 4 | NVIC_ERROR | Restore of NVIC registers didn't happened | Index of last executed test. |
73: ADC_MONITOR
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | BANDGAP_ADC0 | Bandgap voltage measured by ADC0 is out of range | ADC value of bandgap |
| 2 | BANDGAP_ADC1 | Bandgap voltage measured by ADC1 is out of range | ADC value of bandgap |
| 3 | VREF_HIGH | VRefH voltage is out of range | ADC value of VRefH |
| 4 | VREF_LOW | VRefL voltage is out of range | ADC value of VRefL |
| 5 | START_UP_CHECK_NOT_EXECUTED | Start up check not executed | Status of the start up check |
| 6 | START_UP_CHECK_VREFH_FAILED_1 | VRefH voltage in start up test is to low | ADC value of VRefH |
| 7 | START_UP_CHECK_VREFH_FAILED_2 | VRefH voltage in start up test is to low | ADC value of VRefH |
| 8 | START_UP_CHECK_VREFL_FAILED_1 | VRefL voltage in start up test is to high | ADC value of VRefL |
| 9 | START_UP_CHECK_VREFL_FAILED_2 | VRefL voltage in start up test is to high | ADC value of VRefL |
| 10 | START_UP_CHECK_EXT_REF_FAILED_1 | CL30_VFB voltage in start up test is out of range | ADC value of CL30_VFB |
| 11 | START_UP_CHECK_EXT_REF_FAILED_2 | CL30_VFB voltage in start up test is out of range | ADC value of CL30_VFB |
74: REG_MONITOR
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | WRONG_REG_VALUE | A register has a wrong value | Address of the register with wrong value |
| 2 | WRONG_REG_VALUE_ADDITIONALDATA | Extension of the error entry WRONG_REG_VALUE. | Content of the register with the pale values. |
75: SAFETY_SUPERVISOR
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | BOOTLOADER_INCOMPATIBLE | Bootloader and firmware versions are incompatible | First 4 byte of the git hash of the incompatible bootloader |
76: ECC_MONITOR
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | RAM_ONE_BIT_ERROR | Test for one-bit errors in RAM failed | Byte 0: detected error event (0 = None, 1 = one-bit, 2 = two-bit) |
| 2 | RAM_ONE_BIT_ADDRESS | Location of one-bit error in RAM is wrong | Address / location, where the one-bit error happened |
| 3 | RAM_TWO_BIT_ERROR | Test for two-bit errors in RAM failed |
Byte 0: detected error event (0 = None, 1 = one-bit, 2 = two-bit) Byte 1: boolean flag, if the two-bit error ISR was called |
| 4 | RAM_TWO_BIT_ADDRESS | Location of two-bit error in RAM is wrong | Address / location, where the two-bit error happened |
| 5 | FLASH_TWO_BIT_ERROR | Test for two-bit errors in flash failed | - |
77: CLOCK_MONITOR
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | PLL_FREQUENCY_ERROR | PLL frequency test detected an error | FTM1 value after overflow of FTM4 |
78: MPU_MONITOR
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | ERROR_INIT | Initialization of the MPU failed | Error status |
| 2 | ERROR_INSIDE_START | MPU test "inside start address" failed | Checked address |
| 3 | ERROR_INSIDE_END | MPU test "inside end address" failed | Checked address |
| 4 | ERROR_OUTSIDE_START | MPU test "outside start address" failed | Checked address |
| 5 | ERROR_OUTSIDE_END | MPU test "outside end address" failed | Checked address |
79: IVT
| Reason ID | Reason | Description | Additional Data |
| 0 | ASSERT | Used by the assert function | Line number in which the assert happened |
| 1 | INVALID_WIRING_PARAMETER | IVT-S wiring parameter is invalid | Set invalid value |
| 2 | PARAMETER_ERROR_NO_CHARGING_CAN_AVAILABLE | One of the following parameters is set to charging CAN on a Hardware without one: PAR_VehicleVoltageSource, PAR_InletVoltageSource, PAR_ChargingCurrentSource | - |
| 3 | ERROR | Either the IVT reported an error for the last 100ms or we didn't received messages. |
Byte 0: Measurement which leads to the error ( 0 = Current, 1 = InletVoltage, 2 = VehicleVoltage, 3 = Temperature ) Byte 1: Error status send by IVT bit 0: set if OCS is true bit 1: set if - this result is out of (spec-) range, - this result has reduced precision - this result has a measurement-error bit 2: set if - any result has a measurement-error bit 3: set if - system-error, sensor functionality is not ensured! |
| 4 | PARAMETER_ERROR_CHARGING_CAN_BITRATE_NOT_CONFIGURED | Charging CAN bitrate is configured as SNA while IVT is configured on Charging CAN. | - |