summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorzwelch <zwelch@b42882b7-edfa-0310-969c-e2dbd0fdcd60>2009-06-29 20:03:59 +0000
committerzwelch <zwelch@b42882b7-edfa-0310-969c-e2dbd0fdcd60>2009-06-29 20:03:59 +0000
commitf0fd28a66ca5866de557941113b35de5b55b554d (patch)
treeb1418e73450edfad19ce2d82ee6281bb192dfa32 /doc
parent54ffd82a1a3f90dfc0a81e777d0638998f122a90 (diff)
downloadopenocd_libswd-f0fd28a66ca5866de557941113b35de5b55b554d.tar.gz
openocd_libswd-f0fd28a66ca5866de557941113b35de5b55b554d.tar.bz2
openocd_libswd-f0fd28a66ca5866de557941113b35de5b55b554d.tar.xz
openocd_libswd-f0fd28a66ca5866de557941113b35de5b55b554d.zip
David Brownell <david-b@pacbell.net>:
Warn when people (or scripts) use numeric identifiers for TAPs, instead of dotted.name values. We want this usage to go away, so that for example adding more TAPs doesn't cause config scripts to break because some sequence number changed. It's been deprecated since late 2008, but putting a warning on this should help us remove it (say, in June 2010) by helping to phase out old (ab)usage in config scripts. Other than in various config files, the only code expecting such a number was the almost unused str9xpec driver. This code was changed to use the TAP it was passed, instead of making its own dubious lookup and ignoring that TAP. git-svn-id: svn://svn.berlios.de/openocd/trunk@2415 b42882b7-edfa-0310-969c-e2dbd0fdcd60
Diffstat (limited to 'doc')
-rw-r--r--doc/openocd.texi5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/openocd.texi b/doc/openocd.texi
index fa17cfe4..c55ae482 100644
--- a/doc/openocd.texi
+++ b/doc/openocd.texi
@@ -2397,8 +2397,9 @@ and underscores are OK; while others (including dots!) are not.
In older code, JTAG TAPs were numbered from 0..N.
This feature is still present.
However its use is highly discouraged, and
-should not be counted upon.
-Update all of your scripts to use TAP names rather than numbers.
+should not be relied on; it will be removed by mid-2010.
+Update all of your scripts to use TAP names rather than numbers,
+by paying attention to the runtime warnings they trigger.
Using TAP numbers in target configuration scripts prevents
reusing those scripts on boards with multiple targets.
@end quotation