over first
[6] Is first
failing test
raw data
printed twice
Yes
failing test,
test in force
CLEAR DIAGNOSTIC FAILURE BY LOOPING OVER FIRST FAILING TEST
[2] Is first
failing test
raw data printed
[3] Verify loop
start and end
addresses are on
[4] Is first
failing test in
[5] Set up loop
No
Yes
No
TABLE A — MESSAGES TO ESTABLISH LOOP
terminal 104. Using raw data analysis information obtained
index words
Response:
SUSPENDED
Response:
SUSPENDED
Response:(raw data)
d = address of first failing test statement index word
g = address of next index word following first
[TABLE A (d and g)]
printed twice. Resend last TABLE A message with RPT option
deleted for infinite loop. Set up scope. If SYNC option is
used, attach external sweep trigger to 0/1-60-36
automatic
path of failing bits to isolate and clear fault
in TAP-105, SDs/CDs, and circuit pack SDs, trace signal
1a.
EX:SCLK O,
{
CONTR
a
|IPUB
b
|NCSU 0
}
;START
!
twice
a = failing controller member number
b = failing IPUB member number
e = first failing test number
f = first failing phase number
SUMMARY
failing test index word
c = failing chain
3a.
EX:SCLK 0;RPT 2:PH
f
,ADR
d-g!
2a.
EX:SCLK 0:[SYNC
d]
,ENABLE
e!
[1] See CAUTION 1.
Set up loop over first
failing test and
repeat test twice
using appropriate SCLK
or NCLK messages
[TABLE A]
Enter TABLE A messages. Verify first failing test raw data
Enter a or b messages:
1b.
EX:NCLK 0,CHAIN
c
; START
!
2b.
EX:NCLK 0:[SYNC
d]
,ENABLE
e!
3b.
EX:NCLK 0;RPT 2:PH
f
,ADR
d-g!
No
assistance from
in setting up
loop
RWC or NESAC
[7] Seek
Yes
CAUTION 1
Always remove
NCSU from service
and disable all
oscillators (using
switch) before
working on any
network clock
problem
ENABLE/DISABLE
106
TAP
PAGE 1 of 3
234-151-013
DEC 1995
Issue 8
