|
From: R. D. <rdi...@ya...> - 2013-03-07 12:37:10
|
Hallo Xiaofan: >>> I tried searching the Internet for answers, and I came across this message: >>> http://www.mail-archive.com/ope...@li.../msg17192.html >>> However, >>> I couldn't make out the status of that patch. The other information I >>> have found was either not applicable (lib ftd2xx instead of libftdi) or >>> got me confused. >>> >Okay I think the issue is with your cheap clone of USB Blaster. > >Please refer to this thread and try the patch. >http://lists.berlios.de/pipermail/openocd-development/2011-June/019820.html >"The USB Blaster clone does not use the original FT245 chip, and so >it tries to emulate its behavior. >As it turns out, the API call FT_GetLatencyTimer is not properly >emulated by the clone, and this makes OpenOCD abort. In reality, this >API call is not necessary, so I have removed this call." Well, yes, that's the same message I already provided a link for above. Do you know the status of that patch? Any hopes that it could be applied? If that API call is not necessary, would it be possible to remove it from OpenOCD altogether? It is not ideal having to apply a patch to every new OpenOCD version. The world is full of those cheap USB Blaster clones, I would be nice if it worked with OpenOCD straight away. Is it a matter of money? If any OpenOCD developer volunteers, I can send him mine for research purposes, I don't need it back. > It could be the problem with libftdi 0.xx. Which version of libftdi are > you using? 0.20 is the latest one for the legacy libftdi-0.x release. The libftdi version that comes with my Ubuntu 12.04 is 0.19-4. I'll see if I can build OpenOCD against a newer version. Do you think 0.20 would suffice, or is it worth the trouble switching to the renamed 1.0 version? Thanks, rdiez |