6-6
MPC8260 PowerQUICC II User’s Manual
MOTOROLA
Part III. The Hardware Interface
WT
BADDR30
IRQ3
Write through—Output used for L2 cache control. For each core-initiated MPC8260 60x
transaction, the state of this pin indicates if the transaction should be cached using write-through or
copy-back mode. Assertion of WT indicates that the transaction should be cached using the
write-through mode.
Burst address 30—There are five burst address output pins. These pins are outputs of the 60x
memory controller. These pins are used in external master configuration and are connected directly
to memory devices controlled by MPC8260’s memory controller.
Interrupt request 3—This input is one of the eight external lines that can request (by means of the
internal interrupt controller) a service routine from the core.
L2_HIT
IRQ4
L2 cache hit—(Input). It is used for L2 cache control. Assertion of this pin indicates that the 60x
transaction will be handled by the L2 cache. In this case, the memory controller will not start an
access to the memory it controls.
Interrupt request 4—This input is one of the eight external lines that can request (by means of the
internal interrupt controller) a service routine from the core.
CPU_BG
BADDR31
IRQ5
CPU bus grant—(Output) The value of the 60x core bus grant is driven on this pin for the use of an
external MPC2605GA L2 cache. The driven bus grant is non qualified, that is, in case of external
arbiter the user should qualify this signal with the bus grant input to the MPC8260 before
connecting it to the L2 cache.
Burst address 31—There are five burst address output of the 60x memory controller used in
external master configuration and are connected directly to the memory devices controlled by
MPC8260’s memory controller.
Interrupt Request 5—This input is one of the eight external lines that can request (by means of the
internal interrupt controller) a service routine from the core.
CPU_DBG
CPU bus data bus grant—(Output) The value of the 60x core data bus grant is driven on this pin for
the use of an external MPC2605GA L2 cache.
CPU_DBG
CPU data bus grant—(Output). The OR of all data bus grant signals for internal masters from the
internal arbiter is driven on CPU_DBG. CPU_DBG should be connected to the CPU_DBG input of
an external MPC2605GA L2 cache if the internal arbiter is used (BCR[EARB] = 0). If an external
arbiter is used in this MPC8260, the CPU_DBG input of the L2 cache should be connected to the
DBG driven from the external arbiter to this MPC8260.
CPU_BR
CPU bus request—(Output) The value of the 60x core bus request is driven on this pin for the use
of an external MPC2605GA L2 cache.
CS[0–9]
Chip select—These are output pins that enable specific memory devices or peripherals connected
to MPC8260 buses.
CS[10]
BCTL1
DBG_DIS
Chip select—These are output pins that enable specific memory devices or peripherals connected
to MPC8260 buses.
Buffer control 1—Output signal whose its function is controlling buffers on the 60x data bus. Usually
used with BCTL0. The exact function of this pin is defined by the value of SIUMCR[BCTLC]. See
Section 4.3.2.6, “SIU Module Configuration Register (SIUMCR),” for details.
Data bus grant disable—This is an output when the MPC8260 is in external arbiter mode and an
input when the MPC8260 is in internal arbiter mode. When this pin is asserted, the 60x bus arbiter
should negate all of its DBG outputs to prevent data bus contention.
CS[11]
AP[0]
Chip select—Output that enable specific memory devices or peripherals connected to MPC8260
buses.
Address parity 0—(Input/output)The 60x master that drives the address bus, drives also the
address parity signals. The value driven on address parity 0 pin should give odd parity (odd number
of ‘1’s) on the group of signals that includes address parity 0 and A[0–7].
Table 6-1. External Signals (Continued)
Signal
Description