Menu
▾
▴
Re: [Openocd-development] ftd2xx -> libftdi
|
From: Ronald V. <yah...@li...> - 2009-06-26 17:44:01
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
-------- Original Message --------<br>
Subject: [Openocd-development] ftd2xx -> libftdi<br>
From: Xiaofan Chen <a class="moz-txt-link-rfc2396E" href="mailto:xia...@gm..."><xia...@gm...></a><br>
To: <a class="moz-txt-link-abbreviated" href="mailto:op...@du...">op...@du...</a><br>
Cc: openocd-development <a class="moz-txt-link-rfc2396E" href="mailto:ope...@li..."><ope...@li...></a><br>
Date: Fri Jun 26 2009 17:27:36 GMT+0200 (Romance Standard Time)<br>
<blockquote
cite="mid:a27...@ma..."
type="cite">
<pre wrap="">On Fri, Jun 26, 2009 at 11:15 PM, Duane Ellis<a class="moz-txt-link-rfc2396E" href="mailto:op...@du..."><op...@du...></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Zach Welch wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Only libusb+libftdi serves our long-term interests.
</pre>
</blockquote>
<pre wrap="">Wrong.
"libusb" is a *blocking* issue that we cannot control, fix, nor
whatever. LIBUSB is not supported by *newer* windows platforms. Unless
and until it is supported it becomes a dead end solution, period, end of
story.
I believe the "WinUSB" solution is a solution, that for some reason
keeps being left off your list.
<a class="moz-txt-link-freetext" href="http://msdn.microsoft.com/en-us/library/aa476426.aspx">http://msdn.microsoft.com/en-us/library/aa476426.aspx</a>
</pre>
</blockquote>
<pre wrap=""><!---->
I agree with you that WinUSB is a solution for OpenOCD.
It is actually a solution for libusb-win32 as well. ;-)
On the other hand, libusb-win32+libftdi may still need to be
the solution for Windows 2000 users (and maybe 98SE
and Win ME).
</pre>
</blockquote>
<br>
I have only taken a quick look at WinUSB, but if I understand the
concept correctly there might be an issue. I'm not sure of what I'm
saying here so shout if it's complete nonsense. To work with WinUSB,
your USB device has to indicate that WinUsb.sys is its driver. In the
case of e.g. a Luminary eval board this can probably be done by making
the correct .inf file or whatever (again, I'm not an expert in this).
The problem I see is that all other tools using FTD2xx (like the
Luminary Flash tool (I suppose)) will no longer be able to connect to
the board as it is not "linked" to the FTD2xx driver. Does this make
sense? And does this apply to libusb+libftdi as well?<br>
<br>
My apologies if you wasted 2 minutes of your life and want them back ;-)<br>
<br>
gr.<br>
<br>
Ronald<br>
</body>
</html>
|
