Re: [openocd:tickets] #343 Increase CMSIS_DAP usb timeout value

[Dave M. <da...@ma...>]

That would be the careful approach, but it brings in something else that 
folks have to understand before tweaking. Personally I don't see any 
downside to extending to 6000mS for any current use cases, perhaps with 
a parameter to tweak back down for any edge cases that get missed?

Regards

DAVE


On 18/03/2022 12:26, Tommy Murphy wrote:
>
> Would it be better to add a command to allow the USB_TIMEOUT to be 
> configured rather than hardcoding a specific fixed value?
>
> ------------------------------------------------------------------------
>
> *[tickets:#343] <https://sourceforge.net/p/openocd/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 10:08 AM 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 ope...@li... 
> 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.
>
>