| commit | 5373085b4d7ab600d0325634f3adc846f92169af | |
| author | Matthias Welwarsky <matthias@welwarsky.de> | |
| Mon, 28 Dec 2015 21:33:51 +0000 (28 22:33 +0100) | ||
| committer | Paul Fertser <fercerpav@gmail.com> | |
| Fri, 22 Jan 2016 13:00:27 +0000 (22 13:00 +0000) | ||
| tree | 574b1b26523b99812b87969749bfad3621df0bf4 | treesnapshot (tar.gz zip) |
| parent | a185eaad9d2fd25e3e53398a235e08f07f360e74 | commitdiff |
adiv5: introduce optional dap_sync() function
dap_sync() executes all commands in the JTAG queue and then checks
if a WAIT condition happened inside the last batch. If yes, a recovery
is invoked. If not, processing continues without checking for
errors. This function should be called in long AP read or writes, e.g.
while uploading a new application binary, at intermediate points within
the transfer where the cost of flushing the JTAG queue and checking the
journal doesn't affect performance too much.
Change-Id: I99eeaf47cdf951e15e589a04e74b90b5ce911386
Signed-off-by: Matthias Welwarsky <matthias@welwarsky.de>
Reviewed-on: http://openocd.zylin.com/3181
Tested-by: jenkins
Reviewed-by: Paul Fertser <fercerpav@gmail.com>
dap_sync() executes all commands in the JTAG queue and then checks
if a WAIT condition happened inside the last batch. If yes, a recovery
is invoked. If not, processing continues without checking for
errors. This function should be called in long AP read or writes, e.g.
while uploading a new application binary, at intermediate points within
the transfer where the cost of flushing the JTAG queue and checking the
journal doesn't affect performance too much.
Change-Id: I99eeaf47cdf951e15e589a04e74b90b5ce911386
Signed-off-by: Matthias Welwarsky <matthias@welwarsky.de>
Reviewed-on: http://openocd.zylin.com/3181
Tested-by: jenkins
Reviewed-by: Paul Fertser <fercerpav@gmail.com>
| src/target/adi_v5_jtag.c | diffblobblamehistory | |
| src/target/arm_adi_v5.h | diffblobblamehistory |