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>
This commit is contained in:
Paul Fertser 2014-06-12 18:56:32 +04:00 committed by Andreas Fritiofson
parent eea49ce509
commit 8ae66d0d6f
1 changed files with 2 additions and 1 deletions

View File

@ -1430,7 +1430,8 @@ static int jlink_tap_execute(void)
result = use_jtag3 ? usb_in_buffer[byte_length] : 0; result = use_jtag3 ? usb_in_buffer[byte_length] : 0;
if (result != 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(); jlink_tap_init();
return ERROR_JTAG_QUEUE_FAILED; return ERROR_JTAG_QUEUE_FAILED;
} }