On Wed, Jul 13, 2011 at 10:55 PM, Xiaofan Chen <xiaof...@gmail.com> wrote: > Under Linux, ftd2xx 1.04 (based on libusb-1.0.8) does not seem to offer > any advantage than libftdi (tested with 0.19)
This is the same as reported last time. > mcuee@Ubuntu:~/Desktop/build/openocd/lm3s1968$ openocd-d2xx -f > board/ek-lm3s1968.cfg > Open On-Chip Debugger 0.5.0-dev-00954-g0ea76bc (2011-07-13-20: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: 4 "2232C" > Info : deviceID: 67353817 > Info : SerialNumber: 070200A1A > Info : Description: Stellaris Evaluation Board A > 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: 0x0001e340 msp: 0x20000200 > flash 'stellaris' found at 0x00000000 > auto erase enabled > wrote 262144 bytes from file ./demo.bin in 50.572987s (5.062 KiB/s) > 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: 0x0001e340 msp: 0x20000200 > 1200 kHz > flash 'stellaris' found at 0x00000000 > auto erase enabled > wrote 262144 bytes from file ./demo.bin in 42.674957s (5.999 KiB/s) > ^C > > mcuee@Ubuntu:~/Desktop/build/openocd/lm3s1968$ openocd -f > board/ek-lm3s1968.cfg > Open On-Chip Debugger 0.5.0-dev-00954-g0ea76bc (2011-07-13-20:21) > 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 : 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: 0x0001e340 msp: 0x20000200 > 1200 kHz > flash 'stellaris' found at 0x00000000 > auto erase enabled > wrote 262144 bytes from file ./demo.bin in 42.677986s (5.998 KiB/s) > ^C Then I did similar test under Windows with libftdi-0.19 (with Liminary's FTDI driver and libusb-win32 filter driver). The speed is faster than under Linux. Kind of interesting. I will try the ftd2xx Windows build later. D:\work\openocd\build_cxf\openocd_14Jul2011_mingw32\bin>openocd.exe -f board\ek-lm3s1968.cfg Open On-Chip Debugger 0.5.0-dev-00954-g0ea76bc-dirty (2011-07-14-21:37) 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 : 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: 0x0001e340 msp: 0x20000200 1200 kHz flash 'stellaris' found at 0x00000000 auto erase enabled wrote 123904 bytes from file ./demo.bin in 11.093000s (10.908 KiB/s) -- Xiaofan _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
