On Fri, Jul 15, 2011 at 10:24 PM, Xiaofan Chen <[email protected]> wrote:
>> I think Freddie is probably right. There is still a bit of speed bump
>> compared to the
>> on-board ftdi2232C based Luminary-ICDI interface.
>>
>> jtag_khz = 1200 KHz, 11.820 KiB/s versus 11.016 KiB/s
>> jtag_khz = max supported, 12.729 KiB/s versus 11.524 KiB/s (10% faster)
>
> For the USB 2.0 Jtagkey2, using the WHQL driver and ftd2xx is
> only about 5% faster than using libftdi and libusb-win32 filter driver
> on top of the WHQL driver.
>
> jtag_khz = 1200 KHz, 11.826 KiB/s (ftd2xx) versus 11.296 KiB/s
> (libftdi), (4.7% faster)
> jtag_khz = 3000 KHz, 12.729 KiB/s (ftd2xx) versus 12.096 KiB/s
> (libftdi), (5.2% faster)
>
> Probably I will try another target to see the flash download difference.
>
But I will finish the test under Linux first. Since I got not good result
under Ubuntu Linux (which still uses libusb-0.1), I switched to
Arch Linux which is usually a bit faster than Ubuntu (but Gnome
3 is in the same league as Unity, both are worse than Gnome 2).
I will probably go back to Ubuntu to see whether I might have
done something differently.
Then I get similar result as Windos under Linux. Interestingly
the speed is almost the same in Arch Linux as compared
to Windows 7. ftd2xx-1.04 is faster than libftdi-0.19 by
about 5%. That is what I expected since ftd2xx-1.04 uses
libusb-1.0.8's async API feature under Linux.
jtag_khz = 1200 KHz, 11.826 KiB/s (ftd2xx) versus 11.296 KiB/s
(libftdi), (4.7% faster)
jtag_khz = 3000 KHz, 12.729 KiB/s (ftd2xx) versus 12.093 KiB/s
(libftdi), (5.2% faster)
[mcuee@myhost lm3s1968]$ openocd -f ek-lm3s1968_jtagkey2.cfg
Open On-Chip Debugger 0.5.0-dev-00956-ge7269e3 (2011-07-16-08:25)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
500 kHz
Info : max TCK change to: 30000 kHz
Info : clock speed 500 kHz
Info : JTAG tap: lm3s1968.cpu tap/device found: 0x3ba00477 (mfg:
0x23b, part: 0xba00, ver: 0x3)
Info : lm3s1968.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : accepting 'telnet' connection from 4444
500 kHz
cortex_m3 reset_config sysresetreq
Info : JTAG tap: lm3s1968.cpu tap/device found: 0x3ba00477 (mfg:
0x23b, part: 0xba00, ver: 0x3)
target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x0001df0c msp: 0x20000300
1200 kHz
flash 'stellaris' found at 0x00000000
auto erase enabled
wrote 123904 bytes from file demo.bin in 10.711820s (11.296 KiB/s)
3000 kHz
flash 'stellaris' found at 0x00000000
auto erase enabled
wrote 123904 bytes from file demo.bin in 10.005830s (12.093 KiB/s)
[mcuee@myhost lm3s1968]$ openocd-d2xx -f ek-lm3s1968_jtagkey2.cfg
Open On-Chip Debugger 0.5.0-dev-00956-ge7269e3 (2011-07-16-08:28)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
500 kHz
Error: unable to get latency timer: 0
Error: ftd2xx 1.04 detected - this has known issues with
FT_GetLatencyTimer, upgrade to a newer version
Info : device: 6 "2232H"
Info : deviceID: 67358712
Info : SerialNumber: 53T9XDR4A
Info : Description: Amontec JTAGkey-2 A
Info : max TCK change to: 30000 kHz
Info : clock speed 500 kHz
Info : JTAG tap: lm3s1968.cpu tap/device found: 0x3ba00477 (mfg:
0x23b, part: 0xba00, ver: 0x3)
Info : lm3s1968.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : accepting 'telnet' connection from 4444
500 kHz
cortex_m3 reset_config sysresetreq
Info : JTAG tap: lm3s1968.cpu tap/device found: 0x3ba00477 (mfg:
0x23b, part: 0xba00, ver: 0x3)
target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x0001df0c msp: 0x20000300
1200 kHz
flash 'stellaris' found at 0x00000000
auto erase enabled
wrote 123904 bytes from file demo.bin in 10.231838s (11.826 KiB/s)
3000 kHz
flash 'stellaris' found at 0x00000000
auto erase enabled
wrote 123904 bytes from file demo.bin in 9.505806s (12.729 KiB/s)
500 kHz
cortex_m3 reset_config sysresetreq
Info : JTAG tap: lm3s1968.cpu tap/device found: 0x3ba00477 (mfg:
0x23b, part: 0xba00, ver: 0x3)
--
Xiaofan
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
