Spencer Oliver wrote:
>> But I still think it's slow. When I write the same image to a 
>> STM Primer using RFlasher 7, it only takes ~3 seconds.
>>
>> I also tried to use OpenOCD's RLink interface: 7.241484 kb/s. 
>> Much slower than the native RFlasher application.

> You could try the following patch - it will add a couple of K to the speed
> (my tests anyway 13-14kb/sec).

Which one? The archive-link and the one attached to your mail seem to be 
for some other problem?

> Also increasing the stm32 driver (stm32x_write_block buffer_size) to 16k (if
> you have enough target ram)

Ok, increasing the buffer did help a bit:

default 8192:

   wrote 112328 byte from file main.elf in 12.496000s (8.778434 kb/s)

vs. 16384:

   wrote 112328 byte from file main.elf in 7.855000s (13.965030 kb/s)

I think, 16384 (or even 65536?) should be made the default buffer_size, 
because stm32x_write_block will already try smaller values until it can 
allocate a buffer.  Or perhaps it should just use the value from the 
config file?

Possible bug:  The default target/stm32.cfg script assumes a device with 
16384 bytes of working area -- doesn't that break support for smaller 
CPUs with 10k or 6k of memory?


Greetings from Germany!
-- 
Thomas Kindler <m...@t-kindler.de>
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to