Nexus3/ Module
e200z3 Power Architecture Core Reference Manual, Rev. 2
10-48
Freescale Semiconductor
10.11.1 Pins Implemented
The Nexus3/ module implements one nex_evti_b and either one nex_mseo_b or two
nex_mseo_b[1:0]. It also implements a configurable number of nex_mdo[n:0] pins, nex_rdy_b pin,
nex_evto_b pin, and one clock output pin, nex_mcko. The output pins are synchronized to the
Nexus3/ output clock, nex_mcko.
All Nexus3/ input functionality is controlled through the JTAG/OnCE port, in compliance with
IEEE 1149.1. (See
Section 10.5, “Nexus3/ Register Access Through JTAG/OnCE,”
for details.)
The JTAG pins are incorporated as I/O to the e200z3 processor and are further described in
The auxiliary pins are used to send and receive messages and are described in
Table 10-30. JTAG Pins for Nexus3/
JTAG Pin
I/O
Description of JTAG Pins (included in e200z3 Nexus1)
j_tdo
O
Test data output.
j_tdo is the serial output for test instructions and data. It is
three-statable and is actively driven in the shift-IR and shift-DR controller states. It
changes on the falling edge of
j_tclk.
j_tdi
I
Test data input.
j_tdi receives serial test instruction and data. TDI is sampled on the
rising edge of
j_tclk.
j_tms
I
Test mode select. Input pin used to sequence the OnCE controller state machine.
j_tms
is sampled on the rising edge of
j_tclk.
j_tclk
I
Test clock. Input pin used to synchronize the test logic and control register access
through the JTAG/OnCE port.
j_trst_b
I
Test reset. Input pin used to asynchronously initialize the JTAG/OnCE controller.
Table 10-31. Nexus3/ Auxiliary Pins
Auxiliary Pin
I/O
Description of Auxiliary Pins
nex_mcko
O
Message clock out. A free running output clock to development tools for timing of
nex_mdo[n:0] and nex_mseo_b[1:0] pin functions. nex_mcko
is programmable
through the DC1 register.
nex_mdo[n–0]
O
Message data out. Used for OTM, BTM, and DTM. External latching of
nex_mdo[n:0]
occurs on the rising edge of the Nexus3/ clock (
nex_mcko).
nex_mseo_b[1–0]
O
Message start/end out. Indicate when a message on the
nex_mdo[n:0] pins has
started, when a variable length packet has ended, and when the message has ended.
External latching of
nex_mseo_b[1–0]
occurs on the rising edge of the
Nexus3/ clock (
nex_mcko). One- or two-pin MSEO functionality is
determined at integration time according to the SOC implementation
nex_rdy_b
O
Ready. Used to indicate to the external tool that the Nexus block is ready for the next
read/write access. If Nexus is enabled, this signal is asserted upon successful
completion (without error) of an AHB system bus transfer (Nexus read or write) and is
held asserted until the JTAG/OnCE state machine reaches the capture_dr state.
Upon exit from system reset or if Nexus is disabled,
nex_rdy_b remains de-asserted.
Содержание e200z3
Страница 1: ...e200z3 Power Architecture Core Reference Manual Supports e200z3 e200z335 e200z3coreRM Rev 2 06 2008 ...
Страница 32: ...e200z3 Power Architecture Core Reference Manual Rev 2 xii Freescale Semiconductor ...
Страница 50: ...Register Model e200z3 Power Architecture Core Reference Manual Rev 2 2 2 Freescale Semiconductor ...
Страница 238: ...Memory Management Unit e200z3 Power Architecture Core Reference Manual Rev 2 5 16 Freescale Semiconductor ...
Страница 332: ...Power Management e200z3 Power Architecture Core Reference Manual Rev 2 8 4 Freescale Semiconductor ...
Страница 424: ...Revision History e200z3 Power Architecture Core Reference Manual Rev 2 A 2 Freescale Semiconductor ...