Duane Ellis pisze:
> 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
On Tue, Jun 23, 2009 at 6:01 AM, Duane Ellis 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"
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
Colu
Gene Smith pisze:
> How do I add olimex-arm-usb-ocd device to this inf? And once I have
> added it, how do you install the driver so it remains permanent (i.e.,
> survives a winXP reboot)?
Just copy the entries for Turtelizer of JTAGkey and change the
description and VID/PID combinations. Add t
Michael Fischer wrote:
> Hello List,
>
> here is the driver which was build from the SVN r161 (libusb).
> Please test it, it should work with composite devices too.
>
> The zip contains the driver for the "user". The library
> is the new one which was create by the build process.
>
> I have remo
On Mon, Jun 22, 2009 at 12:19 AM, Freddie Chopin wrote:
> Michael Fischer pisze:
>> here is the driver which was build from the SVN r161 (libusb).
>> Please test it, it should work with composite devices too.
>
> Works here.
>
Now it is clear to me. Thanks. The SVN 161 version works. The released
Michael Fischer pisze:
> here is the driver which was build from the SVN r161 (libusb).
> Please test it, it should work with composite devices too.
Works here.
4\/3!!
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lis
