summaryrefslogtreecommitdiff
path: root/tools
diff options
context:
space:
mode:
authorDavid Brownell <dbrownell@users.sourceforge.net>2009-10-08 09:16:01 -0700
committerDavid Brownell <dbrownell@users.sourceforge.net>2009-10-08 09:16:01 -0700
commit40c9668b703389890d30ab5a410e39f6f1e5251e (patch)
tree95cdd736454c2bfc69c17861f2e0ceffede7c150 /tools
parent22aff82cae0de384f931b4cea89c4f52ec976407 (diff)
downloadopenocd+libswd-40c9668b703389890d30ab5a410e39f6f1e5251e.tar.gz
openocd+libswd-40c9668b703389890d30ab5a410e39f6f1e5251e.tar.bz2
openocd+libswd-40c9668b703389890d30ab5a410e39f6f1e5251e.tar.xz
openocd+libswd-40c9668b703389890d30ab5a410e39f6f1e5251e.zip
Stop ignoring most scan chain validation errors
Among other things this causes startup errors to kick in the fallback "reset harder" logic during server startup. Comments are also updated a bit, explaining what the various error paths signify (in at least my observation). There's one class of validation error that we can still plausibly ignore: when wrong IDCODE values are observed. This change seems to have helped make an OMAP5912 behave much more reliably. There's still some post-reset flakiness, but it's unrelated to scan verification. Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions