diff options
| author | zwelch <zwelch@b42882b7-edfa-0310-969c-e2dbd0fdcd60> | 2009-06-16 12:17:12 +0000 |
|---|---|---|
| committer | zwelch <zwelch@b42882b7-edfa-0310-969c-e2dbd0fdcd60> | 2009-06-16 12:17:12 +0000 |
| commit | 491083a248a24c4b7d246e8f2c73b8ba1542d233 (patch) | |
| tree | d4939150b5ada95212fcd44187a60905c3535fad /tools | |
| parent | 0de478618a048dc5abd0d54f878721d7e2901eac (diff) | |
| download | openocd_libswd-491083a248a24c4b7d246e8f2c73b8ba1542d233.tar.gz openocd_libswd-491083a248a24c4b7d246e8f2c73b8ba1542d233.tar.bz2 openocd_libswd-491083a248a24c4b7d246e8f2c73b8ba1542d233.tar.xz openocd_libswd-491083a248a24c4b7d246e8f2c73b8ba1542d233.zip | |
David Brownell <david-b@pacbell.net>:
Tighten error handling on TAP enable/disable paths a bit:
- Don't enable/disable unless it's necessary. Those event
handlers could have nasty side effects...
- Don't *succeed* enables/disables if there was no code which
could have implemented that action. This prevents bugs like
wrongly acting as if the scan chain changed.
- Minor whitespace cleanup in enable/disable command code.
The big problem is still the lack of code to verify scan chains
were actually updated as requested; this adds a comment on that.
I suspect the best we can do near term will be to verify IDCODE.
git-svn-id: svn://svn.berlios.de/openocd/trunk@2250 b42882b7-edfa-0310-969c-e2dbd0fdcd60
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions