On Fri, Jul 22, 2011 at 12:29 AM, Peter Horn <[email protected]> wrote:
> Am 19.07.2011 22:43, schrieb Peter Horn: > >> >> > Last time I've used OpenOCD with RLink stepping was awfully slow, > > about 3 seconds or more per step. This was some weeks ago and on > > Windows / Mingw. On Linux, stepping is considerably faster both with > > and without your patches, so I have to try the current version again > > on Windows. > > > > Stepping is still slow on Windows. > Stepping speed is not affected much by these patches since it depends largely on latency, not throughput. These patches fixes a throughput problem. Cortex-M3 stepping is really dependent on latency because, for some reason, each register is read atomically upon debug entry, plus one atomic restore of a debug register (for DCC purposes) per register. Just reading core registers takes ~0.3 s on my linux system using the primer. > I have now also applied the RLink "RLink interface speedup and fixes" > patch series and run into some problems: > > > On Linux with the standalone RLink I get: > > Open On-Chip Debugger 0.5.0-dev-00959-gd6c42bf-dirty (2011-07-21-23:47) > Licensed under GNU GPL v2 > For bug reports, read > > http://openocd.berlios.de/doc/**doxygen/bugs.html<http://openocd.berlios.de/doc/doxygen/bugs.html> > Warn : Adapter driver 'rlink' did not declare which transports it > allows; assuming legacy JTAG-only > Info : only one transport option; autoselect 'jtag' > 1000 kHz > adapter_nsrst_delay: 100 > jtag_ntrst_delay: 100 > cortex_m3 reset_config sysresetreq > Info : clock speed 375 kHz > Error: Read of endpoint 2 returned -75, expected 17 > Error: dtc_run_download: Value too large for defined data type > > > Patches 1/7 to 4/7 work ok, the problem is caused by patch 5/7 > > > > On Windows using the embedded RLink, OpenOCD: > > > Open On-Chip Debugger 0.5.0-dev-snapshot (2011-07-21-07:10) > Licensed under GNU GPL v2 > For bug reports, read > > http://openocd.berlios.de/doc/**doxygen/bugs.html<http://openocd.berlios.de/doc/doxygen/bugs.html> > Warn : Adapter driver 'rlink' did not declare which transports it > allows; assuming legacy JTAG-only > Info : only one transport option; autoselect 'jtag' > 1000 kHz > adapter_nsrst_delay: 100 > jtag_ntrst_delay: 100 > cortex_m3 reset_config sysresetreq > Error: USB read error: libusb0-dll:err [_usb_reap_async] timeout error > > in procedure 'init' > > Can you post debug logs (add -d on command line)? > There seems to be an known issue with libusb-win32: > > <http://permalink.gmane.org/**gmane.comp.lib.libusb.devel.**windows/505<http://permalink.gmane.org/gmane.comp.lib.libusb.devel.windows/505> > > > > > BTW I'm using libusb-win32 1.2.4.0 > > > Peter > > > >
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
