Steve Bennett wrote:
On 21/06/2011, at 3:59 PM, Laurent Gauch wrote:

On 21/06/2011, at 1:07 AM, Laurent Gauch wrote:

/ />>/ >/ On Mon, Jun 20, 2011 at 1:00 PM, Steve Bennett <steveb at workware.net.au 
<https://lists.berlios.de/mailman/listinfo/openocd-development>> wrote:
/>>/ />>/ On 20/06/2011, at 8:54 PM, Øyvind Harboe wrote:
/>>/ />>/ />>>/ On Mon, Jun 20, 2011 at 12:50 PM, Steve Bennett <steveb at 
workware.net.au <https://lists.berlios.de/mailman/listinfo/openocd-development>> wrote:
/>>/ />>>>/ Instead, just produce a warning
/>>/ />>>/ />>>/ Why?
/>>/ />>>/ />>>/ It merits a comment at least?
/>>/ />>/ />>/ Seems self-evident to me.
/>>/ />>/ Why should it be fatal just because a value couldn't be read?
/>>/ />>/ Doesn't stop anything from working.
/>>/ />/ />/ Why should we support broken hardware or drivers?
/>>/ />/ />/ Better the user is told to toss his busted dongle / hardware than 
to tangle
/>>/ />/ with subtle followon errors?
/>>/ /
/>>/ Nothing to do with hardware. It's a problem with the driver.
/>>/ See 
http://www.mail-archive.com/[email protected]/msg15945.html
/>>/ />>/ >/ /
/>/ Objection !
/>/ />/ If we cannot read this value back, this means we reach trouble with 
driver or device somewhere.
/>/ Also, this trouble could affect following access ...
/>/ This is why we stop with fatal error.
/
OK. So what alternative solution would you suggest to make this driver work?

What version of the driver do you use. If it really come from the driver and if 
this is the last official driver, then ask the writer of the driver to correct.
If no correction are done quickly by the writer of the driver, then yes, you 
may just produce a warning.

http://www.ftdichip.com/Drivers/D2XX.htm

Latest version, 1.0.4. Same behaviour on both MacOSX and Linux.

Sure. I'll ask if they would like to fix this problem.
I will let you know what useful response I get.
Great.

But are you sure to have the correct libusb version. On linux and mac, the libusb is the kernel driver for the d2xx.

Regards,
Laurent Gauch
http://www.amontec.com
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