On Tue, Mar 29, 2011 at 3:28 PM, Xiaofan Chen <[email protected]> wrote: > On Tue, Mar 29, 2011 at 8:24 PM, Drasko DRASKOVIC > <[email protected]> wrote: >> On Tue, Mar 29, 2011 at 2:19 PM, Xiaofan Chen <[email protected]> wrote: >>> Just wondering why you prefer to use d2xx under Linux. I remember >>> the tests done in the past shows that it does not have real advantages >>> over libftdi or libftdi-1.0. Under Windows, yes. But under Linux, seems no. >> >> I do not. Actually, I hate the fact that I have to use closed source >> software (as you see errors like this can not be inspected nor >> corrected, as they are somewhere in the closed binary). >> But I have to, because Amontec uses this as their official driver, and >> I noticed that new D2XX resolves : >> Error: couldn't read enough bytes from FT2232 device (0 < 5) >> that I have been seeing with both libftdi and previous D2XX. That is >> the main reason. Otherwise, it sucks. > > I just built OpenOCD with libftdi-1.0 and it works fine. > > mcuee@ubuntu:~/Desktop/build/openocd/lpc2148$ openocd-libftdi1 -f > interface/jtagkey2.cfg -f board/olimex_lpc_h2148.cfg > Open On-Chip Debugger 0.5.0-dev-00809-gbe14e8c (2011-03-29-20:41) > Licensed under GNU GPL v2 > For bug reports, read > http://openocd.berlios.de/doc/doxygen/bugs.html > Info : only one transport option; autoselect 'jtag' > init_targets > Warning - assuming default core clock 12MHz! Flashing may fail if > actual core clock is different. > trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain > adapter_nsrst_delay: 100 > jtag_ntrst_delay: 100 > 1500 kHz > Info : clock speed 1500 kHz > Info : JTAG tap: lpc2148.cpu tap/device found: 0x4f1f0f0f (mfg: 0x787, > part: 0xf1f0, ver: 0x4) > Info : Embedded ICE version 4 > Info : lpc2148.cpu: hardware has 2 breakpoint/watchpoint units
Hi Xiaofan, I obderved this erroor : Error: couldn't read enough bytes from FT2232 device (0 < 5) recently, and only on my 14Kc MIPS based FPGA. Prevoisly I used ARM SoC, and it worked fine. So, this error is not easily reproducible, and I doubt that you will see it. I wanted to test new D2XX, v. 1.0.4, to see if it will remove these errors, and it did. Old D2XX, v.0.4.16 has the same error (as does libftdi). So I will now try to take a small look at libftdi, to se if there is something suspicious. BR, Drasko _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
