MPC555CME Freescale Semiconductor, MPC555CME Datasheet - Page 602

• Manufacturer Part Number: MPC555CME
• Description: KIT EVALUATION FOR MPC555
• Manufacturer: Freescale Semiconductor
• Type: Microcontrollerr

Specifications of MPC555CME

• Contents: Module Board, Installation Guide, Power Supply, Cable, Software and more
• Processor To Be Evaluated: MPC555
• Data Bus Width: 32 bit
• Interface Type: RS-232
• For Use With/related Products: MPC555
• Lead Free Status / RoHS Status: Contains lead / RoHS non-compliant

16.7 Programmer’s Model
MPC555
USER’S MANUAL
Table 16-10
register name represents “A” or “B” for the TouCAN_A or TouCAN_B module, respec-
tively. Refer to
in the MPC555 / MPC556 address map.
The column labeled “Access” indicates the privilege level at which the CPU must be
operating to access the register. A designation of “S” indicates that supervisor mode
is required. A designation of “S/U” indicates that the register can be programmed for
either supervisor mode access or unrestricted access.
The address space for each TouCAN module is split, with 128 bytes starting at the
base address, and an extra 256 bytes starting at the base address +128. The upper
256 are fully used for the message buffer structures. Of the lower 128 bytes, some are
not used. Registers with bits marked as “reserved” should always be written as logic 0.
Typically, the TouCAN control registers are programmed during system initialization,
before the TouCAN becomes synchronized with the CAN bus. The configuration reg-
isters can be changed after synchronization by halting the TouCAN module. This is
done by setting the HALT bit in the TouCAN module configuration register (CANMCR).
The TouCAN responds by asserting the CANMCR NOTRDY bit. Additionally, the con-
trol registers can be modified while the MCU is in background debug mode.
ILBS [1:0]
IMB3 CLOCK
IMB3 IRQ [7:0]
/
MPC556
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.
shows the TouCAN address map. The lowercase “x” appended to each
1.3 MPC555 / MPC556 Address Map
Figure 16-5 Interrupt levels on IRQ with ILBS
00
CAN 2.0B CONTROLLER MODULE
01
IRQ
7:0
Rev. 15 October 2000
10
IRQ
15:8
NOTE
11
23:16
IRQ
31:24
00
IRQ
to locate each TouCAN module
01
IRQ
7:0
10
11
MOTOROLA
16-20