On Wed, May 9, 2012 at 7:49 AM, Andreas Fritiofson <[email protected]> wrote: > On Sun, May 6, 2012 at 4:18 AM, Xiaofan Chen <[email protected]> wrote: >>> Now I only tested TI/Luminary LM3S1968 and the speed increase >>> is quite impressive compared to last time. >>> >>> Last time's result: the flash write is never above 18KB/sec for >>> LM3S1968. That was about a year ago. >>> http://comments.gmane.org/gmane.comp.debugging.openocd.devel/17877 >>> >>> But I am not so sure if this is because of your mpsse driver or >>> the improvement in the main line. So I will report the result >>> using the vanilla git tree. >>> >> >> Hmm, the vanilla git tree is also very good, even slightly better. >> So in this case, probably the flash writing speed is approaching >> the limit for the Cortex M3 based LM3S1968 > > If I'm not mistaken, Spencer recently rewrote the stellaris flash > driver to use my asynchronous algorithm patch, which more or less does > away with latency-related performance issues. You should get better > download speed though, but you're running with a rather slow JTAG > clock (any reason why?) and your figures may be throughput bound.
I have not tried to push up the JTAG clock. This is the EK-LM3S1968 demo board and it comes with the on-board FTDI based JTAG debug HW. > Just a check... You're using the same board config file both times. > Are you changing it to use the ftdi driver instead of the old ft2232? > Both can be configured in the same OpenOCD binary and only the > configuration files select which one to use. There's a complete new > set of files in the interface/ftdi/ subdir that selects my driver > instead of the old one. I installed the official version to /usr/local and the mpsse version to ~/bin so that I can compared the two. But now I know the problem. I thought I edited the configure file to add --enable-ftdi for the mpsse version but I just checked and I did not. And then I was using the same board file without creating a version of the board file for the mpsse (use interface/ftdi/luminary.cfg instead of interface/luminary.cfg). So I need to redo the build and the test. Sorry about the noise. >> mymacmini:lm3s1968 xiaofanc$ openocd -f board/ek-lm3s1968.cfg >> Open On-Chip Debugger 0.6.0-dev-00543-g908ee4d (2012-05-05-20:28) >> Licensed under GNU GPL v2 >> For bug reports, read >> http://openocd.sourceforge.net/doc/doxygen/bugs.html >> Info : only one transport option; autoselect 'jtag' >> 500 kHz >> Info : clock speed 500 kHz >> Error: couldn't read enough bytes from FT2232 device (70 < 81) >> Error: couldn't read from FT2232 >> Error: Trying to use configured scan chain anyway... > > These errors highlight the need for a new driver. It's not about performance. I will test about the performance again. The above often happens, especially when using libftdi-0.1x driver. -- Xiaofan ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
