On Fri, Aug 26, 2011 at 8:51 PM, Sam Jansen <sam.jan...@starleaf.com> wrote:
> ** > On 26/08/11 19:18, Andreas Fritiofson wrote: > > On Fri, Aug 26, 2011 at 7:10 PM, Sam Jansen <sam.jan...@starleaf.com>wrote: > > At this stage I got the libftdi driver giving the same error message as >> the libftd2xx driver: trying to read 3 bytes, only got 2 bytes. This seemed >> like progress so I moved on to diagnosing this error. >> >> I guessed it was just an off-by-one error, and found the following lines, >> which looked suspicious: >> >> if (type != SCAN_OUT) >> thisrun_read += 1; >> >> I commented these two lines out, with again no basis other than >> guess-work. >> > > ft2322_large_scan is broken to the point where I've doubt that it's ever > used in practice. I could never get it to run using a CPU target, but with a > 27 Mb scan from an SVF file I guess it will. Thanks for the idea, I didn't > think of that. From your description it seems your SDR is an inout scan? One > problem with ft2232_large_scan is that, as far as I can tell, the data read > back is completely discarded. Maybe the SVF code doesn't support TDO > verification, because I doubt it would work. Also there's a memory leak, > buffer's never getting free'd. > > > Actually, this SDR is out only; purely sending data to program an FPGA and > not expecting anything back. > Then I guess the SVF interpreter maps it to an inout scan anyway, which is a waste. Otherwise you wouldn't be helped by commenting out the "if (type != SCAN_OUT) ..." code. /Andreas
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
