On Tue, Jun 23, 2009 at 3:36 PM, Xiaofan Chen<[email protected]> wrote:
> On Tue, Jun 23, 2009 at 1:48 AM, Freddie Chopin<[email protected]> wrote:
>> Xiaofan Chen pisze:
>>>
>>> In this case, I think you do not need the master entry. Please
>>> try it again with the master entry deleted.
>>
>> The master entry (the one without &MI00 and &MI01) is not necessary.
>>
>> I attach a changed driver file.
>
>> [Devices]
>> "FTDI FT2232 (Channel A)"=LIBUSB_DEV, USB\VID_0403&PID_6001&MI_00
>> "FTDI FT2232 (Channel B)"=LIBUSB_DEV, USB\VID_0403&PID_6001&MI_01
>>
>> "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
>>
>> "egnite Turtelizer 2 (Channel A)"=LIBUSB_DEV, USB\VID_0403&PID_bdc8&MI_00
>> "egnite Turtelizer 2 (Channel B)"=LIBUSB_DEV, USB\VID_0403&PID_bdc8&MI_01
>>
>> [Devices.NT]
>> "FTDI FT2232 (Channel A)"=LIBUSB_DEV, USB\VID_0403&PID_6001&MI_00
>> "FTDI FT2232 (Channel B)"=LIBUSB_DEV, USB\VID_0403&PID_6001&MI_01
>>
>> "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
>>
>> "egnite Turtelizer 2 (Channel A)"=LIBUSB_DEV, USB\VID_0403&PID_bdc8&MI_00
>> "egnite Turtelizer 2 (Channel B)"=LIBUSB_DEV, USB\VID_0403&PID_bdc8&MI_01
>>
>
> What if you remove Channel B from the INF file? Will the USB virtual COM port
> appear again? Will it affect the JTAG channel A for OpenOCD?
>
> This will need the SVN version of libusb0.sys according to Freddie.
>
> I hope this works. Then it can solve the problems of losing the COM port.
> Please try it (Michael, Freddie, Gene and others). Thanks.
>
It seems to work for me under Vista 32bit. I do not have a JTAG debugger
supported by OpenOCD. But I have a Infineon XE166 demo board which has
a FT2232D based JTAG debugger.
Now it is listed as a libusb-win32 device (originally listed as Infineon
XC166E/XC2000 USB Debug ) and a Infineon XC/166E/XC2000
USB to serial port.
DLL version: 0.1.12.1
Driver version: 0.1.12.1
The output of testlibusb-win.exe: Now you can see there is only
one interface listed.
bus/device idVendor/idProduct
bus-0/\\.\libusb0-0002--0xffff-0x0005 FFFF/0005
- Manufacturer : LPCUSB
- Product : USBSerial
- Serial Number: DEADC0DE
wTotalLength: 32
bNumInterfaces: 1
bConfigurationValue: 1
iConfiguration: 0
bmAttributes: c0h
MaxPower: 50
bInterfaceNumber: 0
bAlternateSetting: 0
bNumEndpoints: 2
bInterfaceClass: 255
bInterfaceSubClass: 0
bInterfaceProtocol: 0
iInterface: 0
bEndpointAddress: 06h
bmAttributes: 0dh
wMaxPacketSize: 128
bInterval: 1
bRefresh: 0
bSynchAddress: 0
bEndpointAddress: 83h
bmAttributes: 0dh
wMaxPacketSize: 128
bInterval: 1
bRefresh: 0
bSynchAddress: 0
Hopefully this will work for other JTAG debuggers.
[Version]
Signature = "$Chicago$"
provider = %manufacturer%
DriverVer = 07/11/2007,0.1.12.1
CatalogFile = ftdi_libusb_Interface0.cat
CatalogFile.NT = ftdi_libusb_Interface0.cat
CatalogFile.NTAMD64 = ftdi_libusb_Interface0_x64.cat
Class = LibUsbDevices
ClassGUID = {EB781AAF-9C70-4523-A5DF-642A87ECA567}
[ClassInstall]
AddReg=libusb_class_install_add_reg
[ClassInstall32]
AddReg=libusb_class_install_add_reg
[libusb_class_install_add_reg]
HKR,,,,"LibUSB-Win32 Devices"
HKR,,Icon,,"-20"
[Manufacturer]
%manufacturer%=Devices,NT,NTAMD64
;--------------------------------------------------------------------------
; Files
;--------------------------------------------------------------------------
[SourceDisksNames]
1 = "Libusb-Win32 Driver Installation Disk",,
[SourceDisksFiles]
libusb0.sys = 1,,
libusb0.dll = 1,,
libusb0_x64.sys = 1,,
libusb0_x64.dll = 1,,
[DestinationDirs]
libusb_files_sys = 10,system32\drivers
libusb_files_sys_x64 = 10,system32\drivers
libusb_files_dll = 10,system32
libusb_files_dll_wow64 = 10,syswow64
libusb_files_dll_x64 = 10,system32
[libusb_files_sys]
libusb0.sys
[libusb_files_sys_x64]
libusb0.sys,libusb0_x64.sys
[libusb_files_dll]
libusb0.dll
[libusb_files_dll_wow64]
libusb0.dll
[libusb_files_dll_x64]
libusb0.dll,libusb0_x64.dll
;--------------------------------------------------------------------------
; Device driver
;--------------------------------------------------------------------------
[LIBUSB_DEV]
CopyFiles = libusb_files_sys, libusb_files_dll
AddReg = libusb_add_reg
[LIBUSB_DEV.NT]
CopyFiles = libusb_files_sys, libusb_files_dll
[LIBUSB_DEV.NTAMD64]
CopyFiles = libusb_files_sys_x64, libusb_files_dll_wow64, libusb_files_dll_x64
[LIBUSB_DEV.HW]
DelReg = libusb_del_reg_hw
AddReg = libusb_add_reg_hw
[LIBUSB_DEV.NT.HW]
DelReg = libusb_del_reg_hw
AddReg = libusb_add_reg_hw
[LIBUSB_DEV.NTAMD64.HW]
DelReg = libusb_del_reg_hw
AddReg = libusb_add_reg_hw
[LIBUSB_DEV.NT.Services]
AddService = libusb0, 0x00000002, libusb_add_service
[LIBUSB_DEV.NTAMD64.Services]
AddService = libusb0, 0x00000002, libusb_add_service
[libusb_add_reg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,libusb0.sys
; Older versions of this .inf file installed filter drivers. They are not
; needed any more and must be removed
[libusb_del_reg_hw]
HKR,,LowerFilters
HKR,,UpperFilters
; Device properties
[libusb_add_reg_hw]
HKR,,SurpriseRemovalOK, 0x00010001, 1
;--------------------------------------------------------------------------
; Services
;--------------------------------------------------------------------------
[libusb_add_service]
DisplayName = "LibUsb-Win32 - Kernel Driver 07/11/2007, 0.1.12.1"
ServiceType = 1
StartType = 3
ErrorControl = 0
ServiceBinary = %12%\libusb0.sys
;--------------------------------------------------------------------------
; Devices
;--------------------------------------------------------------------------
[Devices]
"FTDI Channel A"=LIBUSB_DEV, USB\VID_058b&PID_002b&MI_00
[Devices.NT]
"FTDI Channel A"=LIBUSB_DEV, USB\VID_058b&PID_002b&MI_00
[Devices.NTAMD64]
"FTDI Channel A"=LIBUSB_DEV, USB\VID_058b&PID_002b&MI_00
;--------------------------------------------------------------------------
; Strings
;--------------------------------------------------------------------------
[Strings]
manufacturer = "FTDI"
--
Xiaofan http://mcuee.blogspot.com
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
