On Saturday 27 June 2009 11:30:07 David Brownell wrote:
> > Pavel's explanation matches with what I remember about this issue. I'm
> > preparing a test setup to verify the numbers just now.
>
> ISTR Nicolas Pitre reported almost-the-same-speed too.
>
> At least, on Linux.  I believe MS-Windows does have a
> speed difference, but that's not at issue here.
>
> - Dave

Here are my test results:

Target: AT91SAM9260 on a Olimex SAM9-L9260 (ARM926EJ-S)
JTAG: Amontec JTAG-Key
OS: (K)Ubuntu 9.04
Host: Core2Duo @ 2.6 GHz
OpenOCD: SVN 2405, built just an hour ago

libftdi: /usr/lib/libftdi.so.1.13.0 (9.04 stock version)
--------------------------------------------------------

> dump_image /home/vmaster/test.img 0x20000000 1048576                          
>            
dumped 1048576 byte in 43.130390s (24.311 KB/s)

> arm7_9 fast_memory_access enable
fast memory access is enabled

> dump_image /home/vmaster/test.img 0x20000000 1048576
dumped 1048576 byte in 33.895313s (30.935 KB/s)

> load_image /home/vmaster/test.img 0x20000000 bin
1048576 byte written at address 0x20000000
downloaded 1048576 byte in 12.915277s (81.188 KB/s)

> arm7_9 dcc_downloads enable
dcc downloads are enabled

> load_image /home/vmaster/test.img 0x20000000 bin
1048576 byte written at address 0x20000000
downloaded 1048576 byte in 4.363197s (204.322 KB/s)


libftdi: /usr/local/lib/libftdi.so.1.16.0 (--with-async-mode)
-------------------------------------------------------------
> dump_image /home/vmaster/test.img 0x20000000 1048576
dumped 1048576 byte in 43.382168s (24.170 KB/s)

> arm7_9 fast_memory_access enable
fast memory access is enabled

> dump_image /home/vmaster/test.img 0x20000000 1048576
dumped 1048576 byte in 34.004364s (30.836 KB/s)

> load_image /home/vmaster/test.img 0x20000000 bin
1048576 byte written at address 0x20000000
downloaded 1048576 byte in 12.834919s (81.697 KB/s)

> arm7_9 dcc_downloads enable
dcc downloads are enabled                                                    

> load_image /home/vmaster/test.img 0x20000000 bin
1048576 byte written at address 0x20000000
downloaded 1048576 byte in 4.368081s (240.054 KB/s)


FTD2XX: /usr/local/lib/libftd2xx.so.0.4.13
------------------------------------------

> dump_image /home/vmaster/test.img 0x20000000 1048576
dumped 1048576 byte in 41.470509s (25.284 KB/s)

> arm7_9 fast_memory_access enable
fast memory access is enabled

> dump_image /home/vmaster/test.img 0x20000000 1048576
dumped 1048576 byte in 31.890425s (32.880 KB/s)

> load_image /home/vmaster/test.img 0x20000000 bin
1048576 byte written at address 0x20000000
downloaded 1048576 byte in 14.818524s (70.761 KB/s)

> arm7_9 dcc_downloads enable
dcc downloads are enabled                                                    

> load_image /home/vmaster/test.img 0x20000000 bin
1048576 byte written at address 0x20000000
downloaded 1048576 byte in 5.044282s (207.874 KB/s)

These tests show libftdi ahead of ftd2xx or only very slightly behind. This is 
by no means a complete performance evaluation and the devil might be in the 
details, but I think it shows that these days libftdi is on par with ftd2xx, 
at least on Linux.

The libftdi 1.13 that comes with (K)Ubuntu 9.04 is already compiled --with--
async-mode. I don't have an older version that lacks this feature lying 
around.

Regards,

Dominic
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to