SNIP_CLASSIC_CAN_SECTION_7_3_1_CAN_Controller_State_Description

7.3.1 CAN Controller State Description This chapter describes the required hardware behavior for the different controller states. CAN controller state UNINIT The CAN controller is not initialized. All registers belonging to the CAN module are in reset state, CAN interrupts are disabled. The CAN Controller is not participating on the CAN bus. CAN controller state STOPPED In this state the CAN Controller is initialized but does not participate on the bus. In addition, error frames and acknowledges must not be sent. (Example: For many controllers entering an ’initialization’-mode causes the controller to be stopped.) CAN controller state STARTED The controller is in a normal operation mode with complete functionality, which means it participates in the network. For many controllers leaving the ’initialization’-mode causes the controller to be started. CAN controller state SLEEP The hardware settings only differ from state STOPPED for CAN hardware that support a sleep mode (wake-up over CAN bus directly supported by CAN hardware). [SWS_Can_00257] Upstream requirements: SRS_SPAL_12067 ⌈When the CAN hardware supports sleep mode and is triggered to transition into SLEEP state, the Can module shall set the controller to the SLEEP state from which the hardware can be woken over CAN Bus.⌋ [SWS_Can_00258] ⌈When the CAN hardware does not support sleep mode and is triggered to transition into SLEEP state, the Can module shall emulate a logical SLEEP state from which it returns only, when it is triggered by software to transition into STOPPED state.⌋ [SWS_Can_00404] ⌈The CAN hardware shall remain in state STOPPED, while the logical SLEEP state is active.⌋