Hi Jim, On Fri, Sep 11, 2015 at 05:27:58PM -0400, Jim Paris wrote: > I suspect that this is just some edge case / race condition being hit > that needs to be handled correctly in the stlink-v2 code, similar to > SWD_AP_WAIT and SWD_DP_WAIT (but just returning ERROR_WAIT for the > unknown codes I'm seeing doesn't help). Do we have any knowledge of > what those status codes mean?
FWIW I wouldn't be surprised if this is the case. When I did the nrf51 async support on stlink it exposed the wait handling stuff and some other error handling stuff in the driver that had probably never been needed before. It'd be interesting to know if a newer stlink firmware update changes the behaviour at all, too. The only suggestion I can think of is to take a logic capture of the SWD lines, if you can. There's an SWD decoder in sigrok (that was written as part of debugging the async support as well), that might provide some insight into what set of conditions triggers those status responses. Angus ------------------------------------------------------------------------------ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
