diff options
| author | Paul Fertser <fercerpav@gmail.com> | 2014-06-12 18:56:32 +0400 |
|---|---|---|
| committer | Andreas Fritiofson <andreas.fritiofson@gmail.com> | 2014-06-22 09:25:15 +0000 |
| commit | 8ae66d0d6f97485be980744ee75ee971eab8a533 (patch) | |
| tree | 9de6a16c5d6be818f3179ed8c66e438fe9b4492c /src | |
| parent | eea49ce509d8d7747feca972c22f2d8bc8e638e5 (diff) | |
jtag/drivers/jlink: better diagnostics for RCLK problems
The JLink protocol description doesn't really specify it for
JTAG-level commands but the real life evidence is that 0x01 error code
means "Adaptive clocking timeout" as it does for e.g. WRITE_MEM_ARM79.
Change-Id: I4e3b568742814271919f92d202713968c8fcccfb
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
Reviewed-on: http://openocd.zylin.com/2169
Tested-by: jenkins
Reviewed-by: Spencer Oliver <spen@spen-soft.co.uk>
Diffstat (limited to 'src')
| -rw-r--r-- | src/jtag/drivers/jlink.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/src/jtag/drivers/jlink.c b/src/jtag/drivers/jlink.c index 029db38c..632dcee4 100644 --- a/src/jtag/drivers/jlink.c +++ b/src/jtag/drivers/jlink.c @@ -1430,7 +1430,8 @@ static int jlink_tap_execute(void) result = use_jtag3 ? usb_in_buffer[byte_length] : 0; if (result != 0) { - LOG_ERROR("jlink_tap_execute failed, result %d", result); + LOG_ERROR("jlink_tap_execute failed, result %d (%s)", result, + result == 1 ? "adaptive clocking timeout" : "unknown"); jlink_tap_init(); return ERROR_JTAG_QUEUE_FAILED; } |