Does anyone have any objections to getting rid of the
concept of a default JTAG clock rate?
Basically, I'd like OpenOCD to refuse to start until the
script defines the clock rate.
The actual mechanism needs a bit of though, because it
is possible to set jtag clock rate in reset-start and in my
book that counts as not using the default clock rate.
Bad! For me.
For me, JTAG is just a transport layer for debugging programming ...
Also, the openocd users should not need to play with any JTAG setting as TCK frequency ... The user want to debug their target board, not the JTAG transport layer or JTAG communication !!! ...
The best, for me, is to fix a low 1MHz frequency as default frequency without
the use of RTCK (disabling RTCK) at the startup of OpenOCD server (example :
set the 1MHz frequency and disable RTCK in Amontec JTAGkey-2 (instead 30MHZ
with RTCK)).
After this default frequency, the scripts may down or up the frequency
depending on the specific job. Or the script could call a function able to
auto-detect the max frequency and to auto-detect the 'yes' or 'no' of the RTCK
use...
If there are no specific frequency set in the script, we run at 1MHZ without
RTCK. This will minimize the troubles for end users.
This 1MHz should not be set by the specific dongle driver itself, but at higher level -> JTAG API.
Laurent
http://www.amontec.com
USB JTAG Adapter Dongle
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
