Hey Tomas, On Fri, Mar 13, 2015 at 07:37:00AM +0100, Tomas Vanek wrote: > So poll is off and ordinary user retries reset. > Now reset fails and keeps failing just because target is not examined.
I was thinking about the issues and came to about the same conclusions. Reset should just try resetting, by whatever means, and then it should be as potent in connecting to a target as a fresh OpenOCD restart. Forcing polling doesn't seem to be a good thing, I agree with you here. > Reset should really do a reset, I thing it is a legitimate requirement. Indeed. > Paul, I do not know OpenOCD internals enough to change the code without > problems. Please please can you take that task? I do not have access to problematic boards at all. And I'm not sure why, but when I'm trying to fix issues like that, it always takes several iterations to get it right. Your testing and feedback helped me a lot already. I do not know in advance how much time I will be able to devote to this task, and typical 12+ (at best) hours testing cycle (I think, I write, I push, you see, you build, you test, you report, I look at your reports) feels inadequate. I will try to do more work on this, but I need more help. Please next time you're sending logs, do not truncate them at all, full text allows me to be less confused about the commands an options used. And please every time you test, save the logs, and push to somewhere so we can all take a look. E.g. I still have no clue at all why sam4l might be failing with ftdi (with sysresetreq) now, even though it works with EDBG (according to the reports). And I'd say, to hell with srst support for sam4l; if we make sysresetreq work reliably, that's enough. > Maybe priority for 0.9.0, what do you thing? So far we know only about two problematic targets: psoc4 and sam4l. I think if we concentrate on these, we'll be able to make them work good enough, but no promises here. I do not have this hardware, and TBH I'm already tired of it (especially regarding sam4l where some crude hacks were added to the codebase instead of properly investigating and fixing just because nobody really cared to dig deep enough). Your psoc4 reset_inner_procedure looks fine to me, it seems like it's the most sensible solution for such an odd target. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:[email protected] ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
