Re: [OpenOCD-user] Error "unable to get latency timer" with a cheap USB-Blaster clone

[Spencer O. <sp...@sp...>]

On 7 March 2013 14:09, Xiaofan Chen <xia...@gm...> wrote:
> On Thu, Mar 7, 2013 at 8:36 PM, R. Diez <rdi...@ya...> wrote:
>>>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.
>
> I do not think it will get any chance of being merged in its
> current form. Firstly you need to rework the patch and
> submit to Gerrit for review. And then I think since these
> are clones and that API call is necessary for real non-clone
> ones. So you may need to create a new config option
> like  --enable-usb_blaster_clone_libftdi.
>

Probably simpler to add a user runtime cmd.

Spen