MC68376BAMFT20 Freescale Semiconductor, MC68376BAMFT20 Datasheet - Page 259

• Manufacturer Part Number: MC68376BAMFT20
• Manufacturer: Freescale Semiconductor

Specifications of MC68376BAMFT20

• Cpu Family: 68K/M683xx
• Device Core: ColdFire
• Device Core Size: 32b
• Frequency (max): 20MHz
• Interface Type: QSPI/SCI
• Program Memory Type: ROM
• Program Memory Size: 8KB
• Total Internal Ram Size: 7.5KB
• # I/os (max): 18
• Number Of Timers - General Purpose: 2
• Operating Supply Voltage (typ): 5V
• Operating Supply Voltage (max): 5.25V
• Operating Supply Voltage (min): 4.75V
• On-chip Adc: 16-chx10-bit
• Instruction Set Architecture: RISC
• Operating Temp Range: -40C to 125C
• Operating Temperature Classification: Automotive
• Mounting: Surface Mount
• Pin Count: 160
• Package Type: PQFP
• Lead Free Status / Rohs Status: Not Compliant

13.4 TouCAN Architecture
13.4.1 TX/RX Message Buffer Structure
MC68336/376
USER’S MANUAL
Programming the TouCAN control registers is typically done during system initializa-
tion, prior to the TouCAN becoming synchronized with the CAN bus. The configuration
registers can be changed after synchronization by halting the TouCAN module. This
is done when the user sets the HALT bit in the TouCAN module configuration register
(CANMCR). The TouCAN responds by asserting the CANMCR NOTRDY bit. Addition-
ally, the control registers can be modified while the MCU is in background debug
mode.
The TouCAN module utilizes a flexible design which allows each of its 16 message
buffers to be assigned either as a transmit (TX) buffer or a receive (RX) buffer. In ad-
dition, to reduce the CPU32 overhead required for message handling each message
buffer is assigned an interrupt flag bit to indicate successful completion of transmission
or reception, respectively.
Figure 13-3 displays the extended (29 bit) ID message buffer structure. Figure 13-4
displays the standard (11 bit) ID message buffer structure.
$A
$C
$E
$0
$2
$4
$6
$8
The TouCAN has no hard-wired protection against invalid bit/field
programming within its registers. Specifically, no protection is provid-
ed if the programming does not meet CAN protocol requirements.
15
Figure 13-3 Extended ID Message Buffer Structure
TIME STAMP
DATA BYTE 0
DATA BYTE 2
DATA BYTE 4
DATA BYTE 6
CAN 2.0B CONTROLLER MODULE (TouCAN)
ID[28:18]
8 7
ID[14:0]
RESERVED
CODE
SRR
4 3
NOTE
DATA BYTE 1
DATA BYTE 3
DATA BYTE 5
DATA BYTE 7
IDE
LENGTH
ID[17:15]
RTR ID_LOW
0
CONTROL/STATUS
ID_HIGH
MOTOROLA
13-3