summaryrefslogtreecommitdiff
path: root/src/jtag/jtag.h
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 /src/jtag/jtag.h
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 'src/jtag/jtag.h')
-rw-r--r--src/jtag/jtag.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/jtag/jtag.h b/src/jtag/jtag.h
index 35635cd8..0126b331 100644
--- a/src/jtag/jtag.h
+++ b/src/jtag/jtag.h
@@ -689,6 +689,7 @@ extern void jtag_sleep(uint32_t us);
#define ERROR_JTAG_DEVICE_ERROR (-107)
#define ERROR_JTAG_STATE_INVALID (-108)
#define ERROR_JTAG_TRANSITION_INVALID (-109)
+#define ERROR_JTAG_INIT_SOFT_FAIL (-110)
/**
* jtag_add_dr_out() is a version of jtag_add_dr_scan() which