My understanding is: on the USB of your Linux PC are connected both one MCU and the openocd adapter DAPLink. With OpenOCD you halt the target. This blocks the Linux USB stack so also the DAPLink cannot be accessed. Is this correct?
Do you get some error message in Linux log? Can the problem be bypassed moving the target on another USB port? "lsusb --tree" should report the USB buses and on which bus the devices are plugged. --- ** [tickets:#343] Increase CMSIS_DAP usb timeout value** **Status:** new **Milestone:** 0.10.0 **Created:** Fri Mar 18, 2022 10:08 AM UTC by Gabor **Last Updated:** Fri Mar 18, 2022 12:26 PM UTC **Owner:** nobody The linux USB stack locks up for 5 seconds if there's an unreponsive USB device, while linux is trying to reconnect. If I halt my device under test, it causes the above linux usb stack bug and my openOCD connection with my DAPLink breaks. The best solution I've found is increasing the USB_TIMEOUT to 6000ms in cmsis_dap.c. What do you think about submitting this fix? If there's an easy way for me to create the CL, I'm happy to do so. --- Sent from sourceforge.net because openocd-devel@lists.sourceforge.net is subscribed to https://sourceforge.net/p/openocd/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/openocd/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
