MOTOROLA
Chapter 2. Signal Descriptions
2-17
Signal Summary
MPIO32B0 / VF0 / MDO1
1
I/O
MPIO32B0
unless the
Nexus (READI)
port is enabled,
then MDO1.
MIOS14 GPIO 0. Allows the signals to be used as
general-purpose inputs/outputs.
O
Visible Instruction Queue Flush Status 0. These signals
output by the MPC561/MPC563 when program instruction
flow tracking is required. VF reports the number of
instructions flushed from the instruction queue in the internal
core. VF signals are also multiplexed with the development
and debug signals VF0 / LWP1 / BG, VF1 / IWP2 / BR, and
VF2 / IWP3 / BB.
O
READI Message Data Out. Message data out (MDO1) is an
output signal used for uploading OTM, BTM, DTM, and
read/write accesses. External latching of MDO occurs on
rising edge of MCKO. Eight MDO signals are implemented.
MPIO32B1 / VF1 / MCKO
1
I/O
MPIO32B1
unless the
Nexus (READI)
port is enabled,
then
MCKO.
MIOS14 GPIO 1. Allows the signals to be used as
general-purpose inputs/outputs.
O
Visible Instruction Queue Flush Status 1. These signals
output by the MPC561/MPC563 when program instruction
flow tracking is required. VF reports the number of
instructions flushed from the instruction queue in the internal
core. VF signals are also multiplexed with the development
and debug signals VF0 / LWP1 / BG, VF1 / IWP2 / BR, and
VF2 / IWP3 / BB.
O
MCKO. Message clock-out (MCKO) is a free-running output
clock to development tools for timing of MDO and MSEO
signal functions. MCKO is the same as the
MPC561/MPC563 system clock.
MPIO32B2 / VF2 / MSEI
1
I/O
MPIO32B2
unless the
Nexus (READI)
port is enabled,
then MSEI.
MIOS14 GPIO 2. Allows the signals to be used as
general-purpose inputs/outputs.
O
Visible Instruction Queue Flush Status 2. These signals
output by the MPC561/MPC563 when program instruction
flow tracking is required. VF reports the number of
instructions flushed from the instruction queue in the internal
core. VF signals are also multiplexed with the development
and debug signals VF0 / LWP1 / BG, VF1 / IWP2 / BR, and
VF2 / IWP3 / BB.
I
MSEI. Message Start/End Input. The MSEI input is a Nexus
input signal that indicates when a message on the MDI
signals has started, when a variable length packet has
ended, and when the message has ended. Internal latching
of MSEI occurs on rising edge of MCKI.
Table 2-1. MPC561/MPC563 Signal Descriptions (continued)
Signal Name
No. of
Signals
Type
Function after
Reset 1
Description