Re: [OpenOCD-user] irscan on multiple taps

[Yuan, S. <she...@gm...>]

Apologize about the question
I found the first working version, the drscan result is actually the same
as my so-called non-working version, just need to shift 1 bit :-)

Working:  00298226 = ‭001010011000001000100110‬
Debug: 574 71253 core.c:954 default_interface_jtag_execute_queue(): JTAG DR
SCAN to RUN/IDLE
Debug: 575 71253 core.c:961 default_interface_jtag_execute_queue():   32b
out: 00000000
Debug: 576 71253 core.c:966 default_interface_jtag_execute_queue():   32b
 in: 00298226
Debug: 577 71253 core.c:961 default_interface_jtag_execute_queue():   2b
out: 00
Debug: 578 71253 core.c:966 default_interface_jtag_execute_queue():   2b
 in: 00

My so-called not-working: 0014c113 = ‭000101001100000100010011‬
Debug: 580 67434 core.c:954 default_interface_jtag_execute_queue(): JTAG DR
SCAN to RUN/IDLE
Debug: 581 67434 core.c:961 default_interface_jtag_execute_queue():   32b
out: 00000000
Debug: 582 67434 core.c:966 default_interface_jtag_execute_queue():   32b
 in: 0014c113

On Wed, Mar 9, 2022 at 9:55 AM Yuan, Shengquan <she...@gm...>
wrote:

>
> On Tue, Mar 8, 2022 at 11:26 PM Andreas Fritiofson <
> and...@gm...> wrote:
>
>> What if you manually do whatever you need to connect the full scan chain,
>> then kill openocd and restart it in auto-detection mode?
>>
> I got your point, after connect the taps, and do a re-start of openocd
> with auto probe configure, I got:
> It looks only the first TAP is probed:
>
> Info : Listening on port 6666 for tcl connections
> Info : Listening on port 4444 for telnet connections
> Info : clock speed 10 kHz
> Warn : There are no enabled taps.  AUTO PROBING MIGHT NOT WORK!!
> Info : JTAG tap: auto0.tap tap/device found: 0x0014c113 (mfg: 0x089
> (Nchip), part: 0x014c, ver: 0x0)
> Warn : AUTO auto0.tap - use "jtag newtap auto0 tap -irlen 12 -expected-id
> 0x0014c113"
> Warn : gdb services need one or more targets defined
>
>
>> I imagined using the correct IR lengths, but in the reverse order:
>>
>> jtag newtap cltap tap -irlen 12
>> jtag newtap linker tap -irlen 4 -disable
>> jtag newtap central tap -irlen 5 -disable
>>
> I paste the wrong content. I use the one as you listed above.
>
> Using wrong lengths will not work, unless you feel like manually managing
>> the additional taps and parsing out the correct data, and then you don't
>> need to define multiple TAPs at all.
>>
> Yes, for now the working configure uses the wrong irlen (the irlen is the
> sum irlen of chain)  and each command, it annually constructs the bit
> sequence.  Although we define multiple TAPs, It actually looks like a
> TAP and only enables one TAP  always.
>
> I compared the mpsse sequence, the working configure and the non-working
> configure sends same bit sequence, I am thinking for now the problem is not
> in "irscan" command, and I am checking if the following "drscan" has
> something that I can look into
>
> --
> Thanks
> -Austin
>


-- 
Thanks
-Austin