From 40c9668b703389890d30ab5a410e39f6f1e5251e Mon Sep 17 00:00:00 2001 From: David Brownell Date: Thu, 8 Oct 2009 09:16:01 -0700 Subject: 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 --- src/jtag/jtag.h | 1 + 1 file changed, 1 insertion(+) (limited to 'src/jtag/jtag.h') 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 -- cgit v1.2.3