On Tue, Mar 29, 2011 at 9:40 PM, Xiaofan Chen <[email protected]> wrote: > On Tue, Mar 29, 2011 at 9:34 PM, Drasko DRASKOVIC > <[email protected]> wrote: >> 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 see. But I have read similar errors in the libftdi/openocd mailing > list. It seems to me libftdi-1.0 can help to solve this issue.
Indeed I do not have issues with OpenOCD/libftdi-1.0 for the LPC-P2148 board and Amontec Jtagkey2. > arm7_9 fast_memory_access enable fast memory access is enabled > arm7_9 dcc_downloads enable dcc downloads are enabled > flash erase_sector 0 0 26 erased sectors 0 through 26 on flash bank 0 in 0.516995s > flash write_image lpc2148_demo.hex 0x0 Verification will fail since checksum in image (0xe59ff004) to be written to flash is different from calculated vector checksum (0xb9205f88). To remove this warning modify build tools on developer PC to inject correct LPC vector checksum. wrote 232748 bytes from file lpc2148_demo.hex in 12.190239s (18.645 KiB/s) >> 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. >> > > You should take a look at libftdi-1.0 which is based on libusb-1.0. -- Xiaofan _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
