From 8ae66d0d6f97485be980744ee75ee971eab8a533 Mon Sep 17 00:00:00 2001 From: Paul Fertser Date: Thu, 12 Jun 2014 18:56:32 +0400 Subject: [PATCH] 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 Reviewed-on: http://openocd.zylin.com/2169 Tested-by: jenkins Reviewed-by: Spencer Oliver --- src/jtag/drivers/jlink.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) 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; } -- 2.39.5