Hi, On Thu, Sep 19, 2013 at 06:13:49PM +0200, Nicolas Produit wrote: > it looks good. > Nothing burned.
Nothing could have been burned just because RPi should be using stronger pulls to drive the GPIO lines :) It would be nice if you confirmed that with a 'scope as I do not have neither RPi nor oscilloscope handy. > This time it is running since at least 30 minutes... > Veeeeery slow! The svf file is 17M. That's very slow indeed. I've seen RPi fetching data from an stm32 with 88.538 kibibytes/s rate. If you're sure your SVF file doesn't set the frequency too low (you can play with the value by hand-editing it), you can try profiling openocd itself. For that use CFLAGS="-pg" ./configure --enable-bcm2835gpio And feed it some smaller SVF file (you can probably just use the first N lines from your 17M one). After OpenOCD finishes, a gmon.out file will be generated which can later be processed with "gprof" (it needs both the binary and the output file). My runs showed all the time was spent preparing and executing the bitbanging functions. With zero busy-looping delays I was getting about 4MHz TCK frequency which should be enough to flash your FPGA in reasonable time. HTH -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ------------------------------------------------------------------------------ LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
