T89C51CC02UA-SISIM Atmel, T89C51CC02UA-SISIM Datasheet - Page 74
![IC 8051 MCU FLASH 16K 28PLCC](/photos/6/70/67044/453-28-plcc_sml.jpg)
T89C51CC02UA-SISIM
Manufacturer Part Number
T89C51CC02UA-SISIM
Description
IC 8051 MCU FLASH 16K 28PLCC
Manufacturer
Atmel
Series
AT89C CANr
Datasheets
1.T89C51CC02CA-TDSIM.pdf
(159 pages)
2.T89C51CC02CA-TDSIM.pdf
(33 pages)
3.T89C51CC02CA-TDSIM.pdf
(29 pages)
4.T89C51CC02CA-TDSIM.pdf
(148 pages)
Specifications of T89C51CC02UA-SISIM
Core Processor
8051
Core Size
8-Bit
Speed
40MHz
Connectivity
CAN, UART/USART
Peripherals
POR, PWM, WDT
Number Of I /o
20
Program Memory Size
16KB (16K x 8)
Program Memory Type
FLASH
Eeprom Size
2K x 8
Ram Size
512 x 8
Voltage - Supply (vcc/vdd)
3 V ~ 5.5 V
Data Converters
A/D 8x10b
Oscillator Type
External
Operating Temperature
-40°C ~ 85°C
Package / Case
28-PLCC
For Use With
AT89STK-06 - KIT DEMOBOARD 8051 MCU W/CAN
Lead Free Status / RoHS Status
Contains lead / RoHS non-compliant
Other names
T89C51CC02UASISIM
Available stocks
Company
Part Number
Manufacturer
Quantity
Price
Buffer Mode
IT CAN Management
74
T89C51CC02
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 34. 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.
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 3
message object 2
message object 1
message object 0
buffer 1
buffer 0
Block buffer
4126F–CAN–12/03