MOTOROLA
MPC8241 Integrated Processor Hardware Specifications
49
PRELIMINARY—SUBJECT TO CHANGE WITHOUT NOTICE
System Design Information
7.5 PCI Reference Voltage—LVDD
The MPC8241 PCI reference voltage (LVDD) pins should be connected to 3.3 ± 0.3 V power supply if
interfacing the MPC8241 into a 3.3-V PCI bus system. Similarly, the LVDD pins should be connected to
5.0 V ± 5% power supply if interfacing the MPC8241 into a 5-V PCI bus system. For either reference
voltage, the MPC8241 always performs 3.3-V signaling as described in the PCI Local Bus Specification
manual (Rev. 2.2). The MPC8241 tolerates 5-V signals when interfaced into a 5-V PCI bus system. (See
Errata No. 18 in the MPC8245/MPC8241 Integrated Processor Chip Errata).
7.6 JTAG Configuration Signals
Boundary scan testing is enabled through the JTAG interface signals. The TRST signal is optional in the
IEEE 1149.1 specification, but is provided on all processors that implement the PowerPC architecture.
While it is possible to force the TAP controller to the reset state using only the TCK and TMS signals, more
reliable power-on reset performance will be obtained if the TRST signal is asserted during power-on reset.
Because the JTAG interface is also used for accessing the common on-chip processor (COP) function,
simply tying TRST to HRESET is not practical.
The COP function of these processors allows a remote computer system (typically, a PC with dedicated
hardware and debugging software) to access and control the internal operations of the processor. The COP
interface connects primarily through the JTAG port of the processor, with some additional status monitoring
signals. The COP port requires the ability to assert HRESET or TRST independently to control the processor
completely. If the target system has independent reset sources, such as voltage monitors, watchdog timers,
power supply failures, or push-button switches, the COP reset signals must be merged into these signals with
logic.
The arrangement shown in
Figure 29 allows the COP to assert HRESET or TRST independently while
ensuring that the target can drive HRESET as well. If the JTAG interface and COP header are not used,
TRST should be tied to HRESET so that it is asserted when the system reset signal (HRESET) is asserted
to ensure that the JTAG scan chain is initialized during power-on. The COP header shown in
Figure 29 adds
many benefits—breakpoints, watchpoints, register and memory examination/modification, and other
standard debugger features are possible through this interface—and can be as inexpensive as an unpopulated
footprint for a header to be added when needed.
The COP interface has a standard header for connection to the target system, based on the 0.025"
square-post, 0.100" centered header assembly (often called a 'Berg header'). The connector typically has
pin 14 removed as a connector key.
Numbering for the COP header shown in
Figure 29 is not standardized; consequently, many different pin
numbers have been observed from emulator vendors. Some are numbered top-to-bottom followed by
left-to-right, while others use left-to-right followed by top-to-bottom. Others number the pins counter
clockwise from pin 1 (as with an IC). Regardless of the numbering, the signal placement recommended in