AT90CAN128-15AZ Atmel, AT90CAN128-15AZ Datasheet - Page 238

• Manufacturer Part Number: AT90CAN128-15AZ
• Description: MCU AVR 128K FLASH 15MHZ 64TQFP
• Manufacturer: Atmel
• Series: AVR® 90CANr

Specifications of AT90CAN128-15AZ

• Package / Case: 64-TQFP, 64-VQFP
• Voltage - Supply (vcc/vdd): 2.7 V ~ 5.5 V
• Operating Temperature: -40°C ~ 125°C
• Speed: 16MHz
• Number Of I /o: 53
• Eeprom Size: 4K x 8
• Core Processor: AVR
• Program Memory Type: FLASH
• Ram Size: 4K x 8
• Program Memory Size: 128KB (128K x 8)
• Data Converters: A/D 8x10b
• Oscillator Type: Internal
• Peripherals: Brown-out Detect/Reset, POR, PWM, WDT
• Connectivity: CAN, I²C, SPI, UART/USART
• Core Size: 8-Bit
• Processor Series: AT90CANx
• Core: AVR8
• Data Bus Width: 8 bit
• Data Ram Size: 4 KB
• Interface Type: CAN, SPI, UART
• Maximum Clock Frequency: 16 MHz
• Number Of Programmable I/os: 53
• Number Of Timers: 4
• Maximum Operating Temperature: + 125 C
• Mounting Style: SMD/SMT
• 3rd Party Development Tools: EWAVR, EWAVR-BL
• Development Tools By Supplier: ATAVRDRAGON, ATSTK500, ATSTK600, ATAVRISP2, ATDVK90CAN1, ATADAPCAN01
• Minimum Operating Temperature: - 40 C
• On-chip Adc: 10 bit, 8 Channel
• Cpu Family: 90C
• Device Core: AVR
• Device Core Size: 8b
• Frequency (max): 16MHz
• Total Internal Ram Size: 4KB
• # I/os (max): 53
• Number Of Timers - General Purpose: 4
• Operating Supply Voltage (typ): 3.3/5V
• Operating Supply Voltage (max): 5.5V
• Operating Supply Voltage (min): 2.7V
• Instruction Set Architecture: RISC
• Operating Temp Range: -40C to 125C
• Operating Temperature Classification: Automotive
• Mounting: Surface Mount
• Pin Count: 64
• Package Type: TQFP
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

19.2.3.8
19.2.3.9
19.2.3.10
19.2.3.11
19.2.3.12
19.2.4
238
AT90CAN32/64/128
Arbitration
Bit Lengthening
Bit Shortening
Synchronization Jump Width
Programming the Sample Point
Synchronization
The IPT begins at the sample point, is measured in TQ and is fixed at 2TQ for the Atmel CAN.
Since Phase Segment 2 also begins at the sample point and is the last segment in the bit time,
PS2 minimum shall not be less than the IPT.
As a result of resynchronization, Phase Segment 1 may be lengthened or Phase Segment 2
may be shortened to compensate for oscillator tolerances. If, for example, the transmitter oscilla-
tor is slower than the receiver oscillator, the next falling edge used for resynchronization may be
delayed. So Phase Segment 1 is lengthened in order to adjust the sample point and the end of
the bit time.
If, on the other hand, the transmitter oscillator is faster than the receiver one, the next falling
edge used for resynchronization may be too early. So Phase Segment 2 in bit N is shortened in
order to adjust the sample point for bit N+1 and the end of the bit time
The limit to the amount of lengthening or shortening of the Phase Segments is set by the Resyn-
chronization Jump Width.
This segment may not be longer than Phase Segment 2.
Programming of the sample point allows "tuning" of the characteristics to suit the bus.
Early sampling allows more Time Quanta in the Phase Segment 2 so the Synchronization Jump
Width can be programmed to its maximum. This maximum capacity to shorten or lengthen the
bit time decreases the sensitivity to node oscillator tolerances, so that lower cost oscillators such
as ceramic resonators may be used.
Late sampling allows more Time Quanta in the Propagation Time Segment which allows a
poorer bus topology and maximum bus length.
Hard synchronization occurs on the recessive-to-dominant transition of the start bit. The bit time
is restarted from that edge.
Re-synchronization occurs when a recessive-to-dominant edge doesn't occur within the Syn-
chronization Segment in a message.
The CAN protocol handles bus accesses according to the concept called “Carrier Sense Multiple
Access with Arbitration on Message Priority”.
During transmission, arbitration on the CAN bus can be lost to a competing device with a higher
priority CAN Identifier. This arbitration concept avoids collisions of messages whose transmis-
sion was started by more than one node simultaneously and makes sure the most important
message is sent first without time loss.
The bus access conflict is resolved during the arbitration field mostly over the identifier value. If a
data frame and a remote frame with the same identifier are initiated at the same time, the data
frame prevails over the remote frame (c.f. RTR bit).
7679H–CAN–08/08