AT89C51CC02CA-RATUM datasheet(81/156 Pages) ATMEL

81 / 156 page

AT/T89C51CC02

4126J–CAN–05/06

Buffer Mode

Any message object can be used to define one buffer, including non-consecutive mes-

sage objects, and with no limitation in number of message objects used up to 4.

Each message object of the buffer must be initialized CONCH2 = 1 and CONCH1 = 1;

Figure 38. Buffer Mode

The same acceptance filter must be defined for each message objects of the buffer.

When there is no mask on the identifier or the IDE, all messages are accepted.

A received frame will always be stored in the lowest free message object.

When the flag RxOk is set on one of the buffer message objects, this message object

can then be read by the application. This flag must then be cleared by the software and

the message object re-enabled in buffer reception in order to free the message object.

The OVRBUF flag in the CANGIT register is set when the buffer is full. This flag can

generate an interrupt.

The frames following the buffer-full interrupt will not be stored and no status will be over-

written in the CANSTCH registers involved in the buffer until at least one of the buffer

message objects is re-enabled in reception.

This flag must be cleared by the software in order to acknowledge the interrupt.

IT CAN Management

The different interrupts are:

•

Transmission interrupt

•

Reception interrupt

•

Interrupt on error (bit error, stuff error, crc error, form error, acknowledge error)

•

Interrupt when Buffer receive is full

•

Interrupt on overrun of CAN Timer

message object 0

message object 1

message object 2

message object 3

Block buffer

buffer 0

buffer 1

AT89C51CC02CA-RATUM 데이터시트(PDF) 81 Page - ATMEL Corporation