On Tue, Jun 23, 2009 at 6:01 AM, Duane Ellis<open...@duaneellis.com> wrote:
> Freddie,
>
> I want to understand what you are working on.
>
> I believe there are 3 or 4 things needed to make OpenOCD work with a
> "universal inf file" for LibUSB really work.
>
> I think of it this way:
>
> (a)   We have a simple "text file" - with 4 columns.
>
> Column 1 - Vendor ID
> Column 2 - Product ID
> Column 3 - Product Root Device Type, ie:  ft2232 - or - other
> Column 4 - "Human Friendly Name".
>
> (b) Perhaps that text file supports "#" comments.
>
> (c)  Question:  Given the above, how hard would it be to create a
> *SIMPLE* perl, shell, awk, whatever script to create a generic LibUSB
> "windows inf" file - that *LIST* *ALL*  items listed in the simple text
> file.

I do not use perl. But I think the above is not that difficult for the
programmers here.

It is not that necessary though. The INF file generated by
libusb-win32 is very easy to understand and the modification
is not that bad even with Notepad. ;-)

> (d) If the above is simple - and I believe it is - then "packagers" of
> OpenOCD *could* - then package "LibUSB0.sys" with the INF file.. and the
> more general problem would be solved.

The libusb0.dll file is also necessary. I think the cat file is necessary
as well.

> (d) In effect, a packager *could* only need to "copy" a pre-built
> "libusb0.sys" file into the same directory as the "generic
> openocd-libusb.inf" file above.
>
> *THEN* - a "prebuilt cygwin" user (or mingw user) *could* - re-install
> the "usb driver" for their dongle - and specify the 'openocd-libusb.inf'
> file instead of the default one that came with/from the dongle vendor.
>

As experienced by Gene Smith and I, sometimes Windows will not
allow this INF file to be installed. In that case, I used the command
line installation method. But Gene Smith mentioned that it may
not survive the reboot. I had not such problem under XP and Vista
32bit.


-- 
Xiaofan http://mcuee.blogspot.com
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to