adi_v5_jtag: reduce verbosity on persistent WAIT
In case of AP not responding, e.g. not clocked, the first WAIT reply is logged as: DAP transaction stalled (WAIT) - slowing down then OpenOCD retries the transaction few times, until it timeouts. At each retry it prints the message: DAP transaction stalled during replay (WAIT) - resending Depending on JTAG speed and transport latency, the amount of log messages can be quite annoying and not relevant. The last printed line is at timeout: Timeout during WAIT recovery Reduce the verbosity. Change-Id: I5a7a337527c98b2450de59066b13713511c2894f Signed-off-by: Antonio Borneo <borneo.antonio@gmail.com> Reviewed-on: https://review.openocd.org/c/openocd/+/6814 Tested-by: jenkins Reviewed-by: Tomas Vanek <vanekt@fbl.cz> Reviewed-by: Daniel Goehring <dgoehrin@os.amperecomputing.com>
This commit is contained in:
parent
d796f5929c
commit
a785ca315b
|
@ -532,7 +532,7 @@ static int jtagdp_overrun_check(struct adiv5_dap *dap)
|
|||
|
||||
/* check for overrun condition in the last batch of transactions */
|
||||
if (found_wait) {
|
||||
LOG_INFO("DAP transaction stalled (WAIT) - slowing down");
|
||||
LOG_INFO("DAP transaction stalled (WAIT) - slowing down and resending");
|
||||
/* clear the sticky overrun condition */
|
||||
retval = adi_jtag_scan_inout_check_u32(dap, JTAG_DP_DPACC,
|
||||
DP_CTRL_STAT, DPAP_WRITE,
|
||||
|
@ -574,7 +574,7 @@ static int jtagdp_overrun_check(struct adiv5_dap *dap)
|
|||
retval = ERROR_JTAG_DEVICE_ERROR;
|
||||
break;
|
||||
}
|
||||
LOG_INFO("DAP transaction stalled during replay (WAIT) - resending");
|
||||
LOG_DEBUG("DAP transaction stalled during replay (WAIT) - resending");
|
||||
/* clear the sticky overrun condition */
|
||||
retval = adi_jtag_scan_inout_check_u32(dap, JTAG_DP_DPACC,
|
||||
DP_CTRL_STAT, DPAP_WRITE,
|
||||
|
|
Loading…
Reference in New Issue