Andreas, list, On 04.08.2011 09:46, Simon Barner wrote: > On 04.08.2011 09:30, Simon Barner wrote: >> Some further benchmarks (OpenOCD compiled without any additional logging): >> >> @ 32 KHz: 1.9 kb/s >> @ 64 KHz: 3.4 kb/s >> @ 125 KHz: 5.6 kb/s >> @ 250 KHz: 8.1 kb/s >> @ 500 KHz: 10.2 kb/s >> @ 1MHz: 11.8 kb/s >> @ 2MHz: 12.9 kb/s >> @ 4MHz: 13.4 kb/s >> @ 6MHz: 13.6 kb/s > > Note that I used the following command to program my (47kb) image: > flash write_image erase image.bin 0x8000000 bin > > However, when I explicitly erase the flash before, I yield even higher > speeds: > > flash erase_address 0x8000000 0x40000 > erased address 0x08000000 (length 262144) in 0.044003s (5817.785 KiB/s) > > flash write_image image.bin 0x8000000 bin > wrote 47984 bytes from file image.bin in 2.623150s (17.864 KiB/s)
> Next, I will try out the async. write patch mentioned here: > <https://lists.berlios.de/pipermail/openocd-development/2011- > July/020261.html> (and related posts). I applied the patches 1/5 - 5/5 against my fixed ARM-JTAG-EW driver and yield now (STM32F107, JTAG @ 6 MHz). Also, debugging the target seems to work decently. flash erase_address 0x08000000 0x40000 erased address 0x08000000 (length 262144) in 0.063400s (4037.855 KiB/s) flash write_image image.bin 0x08000000 bin wrote 47984 bytes from image.bin in 1.778403s (26.349 KiB/s) Here, the performance penalty of auto-erase becomes even more visible. monitor flash write_image erase image.bin 0x08000000 bin wrote 49152 bytes from file image.bin in 2.932805s (16.367 KiB/s) Or, could it be the case the time required for the explicit erase is reported to low? One more question: In the above patch (5/5), there is a change to the flash loader in the contrib directory. As far as I understand, this Cortex-Code is not used in the above programming method. Could you please point me to some documentation how to use it or briefly explain what it is good for? Best regards, Simon _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
