On Fri, Jul 15, 2011 at 6:29 PM, Xiaofan Chen <xiaof...@gmail.com> wrote:
> On Fri, Jul 15, 2011 at 6:02 PM, Xiaofan Chen <xiaof...@gmail.com> wrote:
>> On Fri, Jul 15, 2011 at 5:36 PM, Laurent Gauch
>> <laurent.ga...@amontec.com> wrote:
>>> Do you have a Amontec JTAGkey-2 (High-speed USB 2.0) ?
>>
>> Yes.
>>
>>> If yes, please do the same comparaison with libusb and d2xx on Linux and
>>> windows, and with the Amontec JTAGkey D2XX device driver package WHQL
>>> certified .
>>
>> No problem. I will do it after I build the d2xx binary for Windows.
>>
>
> Anyway here is the test with libftdi driver first.
>
> 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.
D:\work\openocd\build_cxf\openocd_15Jul2011\bin>openocd_libftdi_mingw.exe
-f ek-lm3s1968_jtagkey2.cfg
Open On-Chip Debugger 0.5.0-dev-00956-ge7269e3-dirty (2011-07-15-22:00)
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.712000s (11.296 KiB/s)
3000 kHz
flash 'stellaris' found at 0x00000000
auto erase enabled
wrote 123904 bytes from file demo.bin in 10.003000s (12.096 KiB/s)
D:\work\openocd\build_cxf\openocd_15Jul2011\bin>openocd_mingw_d2xx.exe
-f ek-lm3s1968_jtagkey2.cfg
Open On-Chip Debugger 0.5.0-dev-00956-ge7269e3-dirty (2011-07-15-21:46)
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 : 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.232000s (11.826 KiB/s)
3000 kHz
flash 'stellaris' found at 0x00000000
auto erase enabled
wrote 123904 bytes from file demo.bin in 9.506000s (12.729 KiB/s)
--
Xiaofan
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
