2.11.1 CAN Module Action in SUSPEND
www.ti.com
Master Control Register (CANMC)
1. If there is no traffic on the CAN bus and SUSPEND mode is requested, the node goes into SUSPEND
mode.
2. If there is traffic on the CAN bus and SUSPEND mode is requested, the node goes into SUSPEND
mode when the ongoing frame is over.
3. If the node was transmitting, when SUSPEND is requested, it goes to SUSPEND state after it gets the
acknowledgment. If it does not get an acknowledgment or if there are some other errors, it transmits an
error frame and then goes to SUSPEND state. The TEC is modified accordingly. In the second case,
i.e., it is suspended after transmitting an error frame, the node re-transmits the original frame after
coming out of suspended state. The TEC is modified after transmission of the frame accordingly.
4. If the node was receiving, when SUSPEND is requested, it goes to SUSPEND state after transmitting
the acknowledgment bit. If there is any error, the node sends an error frame and go to SUSPEND
state. The REC is modified accordingly before going to SUSPEND state.
5. If there is no traffic on the CAN bus and SUSPEND removal is requested, the node comes out of
SUSPEND state.
6. If there is traffic on the CAN bus and SUSPEND removal is requested, the node comes out after the
bus goes to idle. Therefore, a node does not receive any "partial" frame, which could lead to
generation of error frames.
7. When the node is suspended, it does not participate in transmitting or receiving any data. Thus neither
acknowledgment bit nor any error frame is sent. TEC and REC are not modified during SUSPEND
state.
SPRU074F – May 2002 – Revised January 2009
eCAN Registers
39