But what do you suggest, what should I change in the inf file?
First it was tested without the "&MI_00" and "&MI_01". Only
ine line. But this was not working too.

Regards,

Michael

-----Ursprüngliche Nachricht-----
Von: Xiaofan Chen [mailto:[email protected]]
Gesendet: Montag, 15. Juni 2009 14:53
An: Michael Fischer
Cc: Openocd-Dev
Betreff: Re: [Openocd-development] Problem to run r2240 with
libusb/libftdi and a JTAGkey


On Mon, Jun 15, 2009 at 8:51 PM, Xiaofan Chen<[email protected]> wrote:
> On Sun, Jun 14, 2009 at 10:01 PM, Michael Fischer<[email protected]>
wrote:
>> I want to create a debug version to find the problem. Attached is the inf
>> file from the JTAGkey. It looks that the problem is inside the
>> ftdi_usb_open_desc function. Here the bus->devices is 0 every time.
>>
>
> Actually now looking at your inf and I think you have a problem with the
inf
> file. You are using libusb-win32 for the individual device, not the whole
> device. The correct way is to use libusb-win32 for the whole device.

I meant to say "You are using libusb-win32 for the individual interface
(which is part of the two interfaces configured), not the whole device".

>
;--------------------------------------------------------------------------
> ; Devices
>
;--------------------------------------------------------------------------
>
> [Devices]
> "Amontec JTAGkey ( Channel A )"=LIBUSB_DEV, USB\VID_0403&PID_cff8&MI_00
> "Amontec JTAGkey ( Channel B )"=LIBUSB_DEV, USB\VID_0403&PID_cff8&MI_01
>
> [Devices.NT]
> "Amontec JTAGkey ( Channel A )"=LIBUSB_DEV, USB\VID_0403&PID_cff8&MI_00
> "Amontec JTAGkey ( Channel B )"=LIBUSB_DEV, USB\VID_0403&PID_cff8&MI_01
>
> [Devices.NTAMD64]
> "Amontec JTAGkey ( Channel A )"=LIBUSB_DEV, USB\VID_0403&PID_cff8&MI_00
> "Amontec JTAGkey ( Channel B )"=LIBUSB_DEV, USB\VID_0403&PID_cff8&MI_01
>
>
> Reference:
> http://article.gmane.org/gmane.comp.lib.libusb.devel.windows/2088


--
Xiaofan http://mcuee.blogspot.com

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

Reply via email to