![](http://datasheet.mmic.net.cn/370000/UPD30181AYF1-131-GA3_datasheet_16743708/UPD30181AYF1-131-GA3_21.png)
Data Sheet U16277EJ1V0DS
21
μ
PD30181A, 30181AY
(16) Debug interface signals
Signal Name
I/O
Function
Alternate Function
JTCK
I
N-Wire clock
–
JTMS
I
N-Wire mode select signal
This signal selects N-Wire serial transfer mode.
–
JTDI/RMODE#
I
N-Wire input data/N-Wire reset mode select signal
This pin functions alternately as RMODE# and JTDI. When JTRST# is
active it functions as RMODE#, and when JTRST# is inactive it functions
as JTDI.
RMODE# input
When JTRST# is active, this pin is the reset mode pin. The initial value
for a debug reset is determined by the level of this signal. A debug
reset is a reset of the processor, and there are two types: a debug cold
reset and a debug soft reset. This serves the same function as Cold
Reset input and Soft Reset input from various target systems.
0: Sets debug reset as valid and resets CPU core
1: Sets debug reset as invalid and does not reset CPU core
JTDI input
When the JTRST# signal is inactive, this pin operates as the N-Wire
serial data input.
–
JTDO
O
N-Wire serial data output
–
JTRST#
I
N-Wire reset signal
–
BKTGIO#
I/O
N-Wire break trigger I/O
BKTGIO#: When used for input setting
When JTRST# is inactive and BKTGIO# is used for input setting, this
pin is the event trigger/break request input pin. When break requests
are valid, setting BKTGIO# to low level stops execution of user
programs in normal mode and forcibly shifts the processor to debug
mode. After BKTGIO# goes to low level in debug mode, break requests
are retained until the processor is restored to normal mode.
0: Requests break and forcibly shifts processor to debug mode
1: Retains current status of processor
BKTGIO#: When used for output setting
When JTRST# is inactive and BKTGIO# is used for output setting, this
pin is the event trigger/break output pin. When the processor is
operating in normal mode and an event is detected that meets any of
the conditions for a hardware breakpoint (instruction address breakpoint
or data access breakpoint), an event trigger is output from BKTGIO# as
a low level signal (one pulse) and detection of the event is reported to
the external debugging tool. Finally, after the event trigger is output, all
detected events are reported as one event trigger. When the processor
is shifted to debug mode, output continues at low level and all
previously non-reported events are not reported.
0: Hardware breakpoint was detected
The processor is shifted to debug mode.
1: The processor is in normal mode.
–