T89C51CC02CA-TDSIM Atmel, T89C51CC02CA-TDSIM Datasheet - Page 73

IC 8051 MCU FLASH 16K 24SOIC

T89C51CC02CA-TDSIM

Manufacturer Part Number
T89C51CC02CA-TDSIM
Description
IC 8051 MCU FLASH 16K 24SOIC
Manufacturer
Atmel
Series
AT89C CANr

Specifications of T89C51CC02CA-TDSIM

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
24-SOIC (7.5mm Width)
For Use With
AT89STK-06 - KIT DEMOBOARD 8051 MCU W/CAN
Lead Free Status / RoHS Status
Contains lead / RoHS non-compliant
Other names
T89C51CC02CATDSIM
CAN Controller
CAN Protocol
Principles
Message Formats
Can Standard Frame
Figure 32. CAN Standard Frames
4126L–CAN–01/08
Interframe
Interframe
Data Frame
Remote Frame
Space
Space
Bus Idle
Bus Idle
SOF
SOF
SOF
SOF
11-bit identifier
11-bit identifier
The CAN Controller provides all the features required to implement the serial communi-
cation protocol CAN as defined by BOSCH GmbH. The CAN specification as referred to
by ISO/11898 (2.0A & 2.0B) for high speed and ISO/11519-2 for low speed. The CAN
Controller is able to handle all types of frames (Data, Remote, Error and Overload) and
achieves a bitrate of 1-Mbit/s at 8 MHz
Note:
The CAN protocol is an international standard defined in the ISO 11898 for high speed
and ISO 11519-2 for low speed.
CAN is based on a broadcast communication mechanism. This broadcast communica-
tion is achieved by using a message oriented transmission protocol. These messages
are identified by using a message identifier. Such a message identifier has to be unique
within the whole network and it defines not only the content but also the priority of the
message.
The priority at which a message is transmitted compared to another less urgent mes-
sage is specified by the identifier of each message. The priorities are laid down during
system design in the form of corresponding binary values and cannot be changed
dynamically. The identifier with the lowest binary number has the highest priority.
Bus access conflicts are resolved by bit-wise arbitration on the identifiers involved by
each node observing the bus level bit for bit. This happens in accordance with the "wired
and" mechanism, by which the dominant state overwrites the recessive state. The com-
petition for bus allocation is lost by all nodes with recessive transmission and dominant
observation. All the "losers" automatically become receivers of the message with the
highest priority and do not re-attempt transmission until the bus is available again.
The CAN protocol supports two message frame formats, the only essential difference
being in the length of the identifier. The CAN standard frame, also known as CAN 2.0 A,
supports a length of 11 bits for the identifier, and the CAN extended frame, also known
as CAN 2.0 B, supports a length of 29 bits for the identifier.
A message in the CAN standard frame format begins with the "Start Of Frame (SOF)",
this is followed by the "Arbitration field" which consist of the identifier and the "Remote
Transmission Request (RTR)" bit used to distinguish between the data frame and the
data request frame called remote frame. The following "Control field" contains the "IDen-
tifier Extension (IDE)" bit and the "Data Length Code (DLC)" used to indicate the
ID10..0
ID10..0
Arbitration
Arbitration
Field
Field
1. At BRP = 1 sampling point will be fixed.
RTR IDE r0
RTR IDE r0
Control
Control
Field
Field
4-bit DLC
4-bit DLC
DLC4..0
DLC4..0
15-bit CRC
CRC
Field
0 - 8 bytes
Data
Field
CRC
del.
ACK
ACK
Field
1
ACK
del.
Crystal frequency in X2 Mode.
End of
Frame
7 bits
15-bit CRC
CRC
Field
Intermission
3 bits
CRC
del.
AT/T89C51CC02
Interframe
ACK
Space
Field
ACK
(Indefinite)
ACK
Bus Idle
del.
End of
Frame
7 bits
Intermission
3 bits
Interframe
Space
(Indefinite)
Bus Idle
73

Related parts for T89C51CC02CA-TDSIM