On 21/06/2011, at 5:22 PM, Steve Bennett wrote:

> 
> On 21/06/2011, at 5:18 PM, Laurent Gauch wrote:
> 
>> Steve Bennett wrote:
>>> On 21/06/2011, at 5:01 PM, Xiaofan Chen wrote:
>>> 
>>> 
>>>> On Tue, Jun 21, 2011 at 2:55 PM, Xiaofan Chen <[email protected]> wrote:
>>>> 
>>>>>> But are you sure to have the correct libusb version. On linux and mac, 
>>>>>> the
>>>>>> libusb is the kernel driver for the d2xx.
>>>>>> 
>>>>> This has been discussed before and I think in this case an exception 
>>>>> should
>>>>> be granted and the patch should be accepted.
>>>>> 
>>>>> Thread:
>>>>> http://lists.berlios.de/pipermail/openocd-development/2011-March/018422.html
>>>>> 
>>>>> I was suggesting the user to use the open source libftdi and libftdi-1.0
>>>>> under Linux instead but D2XX might still have some benefits so that
>>>>> users may still want to use it.
>>>>> 
>>>>> 
>>>> It is a long thread but I was able to reproduce the error.
>>>> http://lists.berlios.de/pipermail/openocd-development/2011-March/018434.html
>>>> "I think the latest d2xx library needs some fix from the OpenOCD
>>>> side or from the d2xx side."
>>>> 
>>>> It is more difficult to ask FTDI for a fix so it may better to fix this 
>>>> from
>>>> OpenOCD side. Therefore I think the patch should be accepted.
>>>> 
>>>> When FTDI fixes D2xx, then probably the patch can be reverted.
>>>> 
>>> 
>>> I have reported the problem to FTDI, but in my experience we can not
>>> expect a response soon, if ever.
>>> I think there are two options, either apply the patch as a workaround
>>> (note that the returned value is *never* used), or remove support for D2XX.
>>> 
>> Thank you Steve,
>> 
>> If you do not get any reply on next Monday, please let me know I will ask 
>> them. Amontec has good contacts to FTDI team.
> 
> Will do.
> 
>> Please apply the patch as a workaround.
> 
> It is on the list. Perhaps some kind maintainer will do so.
> 
>> 
>> But if the returned value is never used, there are no reason to give a 
>> warning !
> 
> Agreed. But it seemed less of a step from fatal error to warning than 
> ignoring it
> completely.

I take it all back!
I got a very prompt reply from FTDI with a new version
of the D2XX driver to test (1.0.5) which resolves this problem.
Hopefully this version will become generally available soon.

Cheers,
Steve
--
µWeb: Embedded Web Framework - http://uweb.workware.net.au/
WorkWare Systems Pty Ltd
W: www.workware.net.au      P: +61 434 921 300
E: [email protected]   F: +61 7 3391 6002





_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to