diff options
| author | Tomas Vanek <vanekt@fbl.cz> | 2024-12-10 08:53:49 +0100 |
|---|---|---|
| committer | Tomas Vanek <vanekt@fbl.cz> | 2025-01-09 20:15:59 +0000 |
| commit | cf115c1e2b670ea8b4606cde0c9b5db735a08742 (patch) | |
| tree | c46a16379891b91de15ccd1083cf8797ec347ce5 /contrib/rpc_examples/ocd_rpc_example.py | |
| parent | 23796efa38019515e6338bb4beaa793a537a00e0 (diff) | |
| download | riscv-openocd-cf115c1e2b670ea8b4606cde0c9b5db735a08742.zip riscv-openocd-cf115c1e2b670ea8b4606cde0c9b5db735a08742.tar.gz riscv-openocd-cf115c1e2b670ea8b4606cde0c9b5db735a08742.tar.bz2 | |
drivers/cmsis_dap_usb_bulk: allow waiting for bulk write
No driver directly working with the USB hardware needs additional
time to complete the write op, they always return transfer complete
status immediately after submitting the transfer.
Although there is implemented correct waiting path in cmsis_dap_usb_write()
it was marked by error logs to catch any suspicious behaviour during
debugging of asynchronous libusb transfers.
However there are drivers which need waiting to finish write op:
at least usbipd-win, IP tunnelled USB driver, was reported
to flood the log with the related errors.
Change LOG_ERROR to LOG_DEBUG_IO in the code waiting to finish write op.
Reported-by: Quentis Ghyll <quentisgh@gmail.com>
Signed-off-by: Tomas Vanek <vanekt@fbl.cz>
Change-Id: Iedf2c96d851f22e694efaf13a2d6a2a408cee1ad
Reviewed-on: https://review.openocd.org/c/openocd/+/8640
Tested-by: jenkins
Diffstat (limited to 'contrib/rpc_examples/ocd_rpc_example.py')
0 files changed, 0 insertions, 0 deletions