On Sat, 2009-05-23 at 00:18 +0200, Magnus Lundin wrote: > Zach Welch wrote: > > On Tue, 2009-05-19 at 16:53 +0200, Magnus Lundin wrote: > > > >> Hi > >> > >> > >>> Info : J-Link compiled Feb 20 2006 18:20:20 -- Update -- > >>> Info : JLink caps 0x3 > >>> Error: J-Link command EMU_CMD_GET_MAX_MEM_BLOCK failed (-110) > >>> > >> Open OCD seems to get reasonable ansvers from first two JLink commands. > >> > >> The /* query hardware maximum memory block */ should not be run for this > >> version, I had removed it in my patch. Next patch will use results from > >> JLink caps to select what info to query. > >> > >> I am waiting for more info from Segger about version diffrences and > >> endpoints. > >> > > > > How are we doing with this patch? It looks like we have made some good > > progress this week, so I don't want the effort to stall. > > > > What are the thoughts about committing your latest version? Even if > > more changes may be pending, it seems that your work has improved things > > for folks with some devices, so I think we have made constructive > > progress from where we were before now. If nothing else, we should get > > some more testing feedback. ;) > > > > Cheers, > > > > Zach > > > There is a set of new patches that has been tested by Michael Fischer, > as far as i know there were no problems. > > There are still things that should be fixed in the resethandling in > jtag_add_reset and minimizing the differences between ft2232 and jlink > behaviour. > But still would suggest that the following patcches are commited. They > are not untested.
I will apply them here and see if they magically cure my own woes. Regardless, I think these changes should be committed in some for, though I can see various ways that I would like to clean your code. Would you mind my taking a pass over them before I commit them? Incidentally, do you think this might also solve the problem that was just reported by Dylan Reid? I have cc'd him in the hope that he will try your patches and report the latest results. Cheers, Zach _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
