Re: Why do some jtag drivers insert a transition to TAP_IR_PAUSE or TAP_DR_PAUSE in *_execute_scan function?

[Neil S. <nl...@ya...>]

 On Wednesday, October 22, 2025 at 09:17:47 AM PDT, Paul Fertser <fer...@gm...> wrote:

> Looks like it's an artifact of very early years of development, see
> e.g. 4411c2643e41d023a1909b1040361912422be6c0 which supports your idea
> that developers thought every scan should end in a stable state.
> 
> All the drivers you mentioned are very rarely used for JTAGing these
> days and there's hardly much motivation anyone has to try to improve
> their performance.
> 
> I see I removed that code from J-Link driver 10 years ago:
> ae8cdc139e12a851107e8f882c5a166a21103ad4 hah :) so it's not just a
> performance issue but also a problem for FPGA/CPLD interactions.

Thank you for your insight. What is the most commonly used JTAG hardware these days with OpenOCD?

Neil.