> But alas, it wasn't supported by my build of OpenOCD.

FWIW, as you probably know already, the default for this adapter is "disabled" 
so it's not enabled unless explicitly enabled at configuration/build time.
Whoever built the OpenOCD that you're using presumably didn't enable it?

> This is strange, because file BUGS distributed with OpenOCD states:
>
> "If OpenOCD is crashing, there are two very effective things you can do to 
> improve your chances of getting help on the development mailing list. Try to 
> reproduce the problem using the dummy JTAG interface to allow other 
> developers to replicate your problem robustly and use GDB to get a trace"

If I had to guess I would presume that the idea is that the Dummy Adapter is 
only really useful for debugging/diagnostic purposes so it's not enabled by 
default and if you hit  a problem that needs it then you configure and build 
OpenOCD yourself with it enabled?

One could argue that there's no point in carrying the load of a rarely used 
adapter in all builds. But a counter argument might be that this adapter is 
most likely pretty lightweight so it's not really much of a penalty if it's 
always enabled...

> Therefore, I would turn on support for the dummy adapter in the configure 
> script by default, even if that means compiling support for 'bitbang' by 
> default too.

I checked the mailing lists but could not find any discussion of how the 
default of "disabled" was arrived at. I couldn't find much specific discussion 
of the Dummy Adapter at all since it was originally added:

* https://sourceforge.net/p/openocd/mailman/message/28331676/

I'm curious about your mention of "bitbang" above - what specifically are you 
referring to there? The "Bitbang mode of FT232R based devices" or "Linux GPIO 
bitbang through libgpiod" adapters? I don't see anything to indicate that the 
Dummy Adapter depends on either of these.

> Therefore, I would turn on support for the dummy adapter

I guess that you could submit a patch to do this and it would get discussed and 
reviewed as per the usual change processes?

* https://github.com/openocd-org/openocd/blob/master/HACKING


Reply via email to