| commit | 8ae66d0d6f97485be980744ee75ee971eab8a533 | |
| author | Paul Fertser <fercerpav@gmail.com> | |
| Thu, 12 Jun 2014 14:56:32 +0000 (12 18:56 +0400) | ||
| committer | Andreas Fritiofson <andreas.fritiofson@gmail.com> | |
| Sun, 22 Jun 2014 09:25:15 +0000 (22 09:25 +0000) | ||
| tree | 9de6a16c5d6be818f3179ed8c66e438fe9b4492c | treesnapshot (tar.gz zip) |
| parent | eea49ce509d8d7747feca972c22f2d8bc8e638e5 | commitdiff |
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>
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>
| src/jtag/drivers/jlink.c | diffblobblamehistory |