>>> [ targetname & tapnames are the same, and is confusing]
Yea, ugh, that is my fault, I did all that last year, I set the
example. What I did not consider well was the TAP names when I setup my
examples after creating the "tcl-target-as-an-object-command.
FYI - The original idea was to support multi-core targets with different
names, for example:
mdw - works on the current target, what ever that is...
$TARGETNAME mdw
That said, I think there is an easy fix - by means of 'enforcement' of
naming convention.
step 1: a 1 line change @ 'jtag.c' -line 1360
===========
FROM:
sprintf( cp, "%s.%s", pTap->chip, pTap->tapname );
TO:
sprintf( cp, "%s.%s.tap", pTap->chip, pTap->tapname );
This *forces* all tapnames to have the suffix ".tap".
============
Step 2, there are 2 options, if (1) is done, I think (B) should be done.
============
(A) a purely mechanical change on all "-chain-position" options in the
"CFG" files, adding the ".tap" suffix.
============
(B) Hidden in C code... effectively enforced, like above, see target.c
- line 3444..3456
It's important to do that *THERE* - not inside: "jtag_tap_by_jim_obj()"
Reason is we want to add ".tap" when we *configure* a target.
============
Step 3. is cleanup, I think only applies to the OMAP3530 (beagle board)
ie: "opmap3530.cfg" - the various "irscan" and "drscan" commands
would need tweaks.
ie: From: "irscan omap3.jrc ..." To: "irscan omap3.jrc.tap ...."
In total, I think (1) and (2)(B) - make the most amount of sense, ie:
"taps" are named with ".tap" at the end, there is no other way to do so,
and makes it very clear to the the user/victim,
ie: If it *ENDS* with *TAP* - it is the *TAP* ...
-Duane.
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
