Since debugging USB devices is a common use case (I've certainly done it innumerable times), it is imo reasonable to have workarounds in OpenOCD and other debug tools to ensure this use case actually works reliably. Whether or not moving the two devices to separate USB controllers works (and it's a good idea to try!), that option won't necessarily be available to all users (eg debugging with a laptop that has only 1 USB controller).
Making the timeout a configuration is an option, but is that really necessary? It's not like the workaround timeout is 10 minutes. :) --- ** [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:59 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.
