diff options
author | dbrownell <dbrownell@b42882b7-edfa-0310-969c-e2dbd0fdcd60> | 2009-09-26 19:08:34 +0000 |
---|---|---|
committer | dbrownell <dbrownell@b42882b7-edfa-0310-969c-e2dbd0fdcd60> | 2009-09-26 19:08:34 +0000 |
commit | 2e210ee48fa5a2dfc1ddc3b47c1aef4da814ca25 (patch) | |
tree | 75919eddc5172f5519d806fa5d5c6b440471bc5e /tcl/target/ti_dm355.cfg | |
parent | ad43374c7fe781ede0f5472f9cbdc55fc9486a6d (diff) | |
download | openocd_libswd-2e210ee48fa5a2dfc1ddc3b47c1aef4da814ca25.tar.gz openocd_libswd-2e210ee48fa5a2dfc1ddc3b47c1aef4da814ca25.tar.bz2 openocd_libswd-2e210ee48fa5a2dfc1ddc3b47c1aef4da814ca25.tar.xz openocd_libswd-2e210ee48fa5a2dfc1ddc3b47c1aef4da814ca25.zip |
Streamline Capture-IR handling and integrity test.
Change the handling of the "-ircapture" and "-irmask" parameters
to be slightly more sensible, given that the JTAG spec describes
what is required, and that we already require that conformance in
one place. IR scan returns some bitstring with LSBs "01".
- First, provide and use default values that satisfy the IEEE spec.
Existing TAP configs will override the defaults, but those parms
are no longer required.
- Second, warn if any TAP gets set up to violate the JTAG spec.
It's likely a bug, but maybe not; else this should be an error.
Improve the related diagnostics to say which TAP is affected.
And associated minor fixes/cleanups to comments and diagnostics.
git-svn-id: svn://svn.berlios.de/openocd/trunk@2758 b42882b7-edfa-0310-969c-e2dbd0fdcd60
Diffstat (limited to 'tcl/target/ti_dm355.cfg')
0 files changed, 0 insertions, 0 deletions