Situation before
I’m working under Win7 Pro.
I’m also owning a DP FT2232H breakout board.
By the way the initial situation is that default FTDI drivers are installed on my computer, either for my old FT232HL serial converter or for the FT2232H dual converter.
Nota : I use USBDeview (see here) (http://http://www.nirsoft.net/utils/usb_devices_view.html) to get a synthetic view of the USB environment on my PC. A nice freeware!
All devices with VID=0403 (FTDI)
(http://http://openbox4.perso.neuf.fr/LIBUSB/USBDEVIEW_STD.jpg)
I’ve 3 virtual COM ports when I look to Device manager (click to see the screen copy) (http://http://openbox4.perso.neuf.fr/LIBUSB/DEVMNGR_STD.jpg)
That’s normal!
More details thanks to USBDeview:
Generic Microsoft parent for FT2232H (click to see the screen copy) (http://http://openbox4.perso.neuf.fr/LIBUSB/PROP_DC_STD.jpg)
Interface A (click to see the screen copy) (http://http://openbox4.perso.neuf.fr/LIBUSB/PROP_DC_A_STD.jpg)
Interface B (click to see the screen copy) (http://http://openbox4.perso.neuf.fr/LIBUSB/PROP_DC_B_STD.jpg)
Serial converter FT232HL (click to see the screen copy) (http://http://openbox4.perso.neuf.fr/LIBUSB/PROP_SC_STD.jpg)
Everything is working fine…
The issue…
I’ve received my DP BusBlaster (V2.0a) a couple of weeks ago.
Need first to adapt connectors to try to de-brick a Dockstar (Seagate Pogoplug) device and I decided to go with OpenOCD.
I installed the required USB environment, according to the WIKI setup (http://http://dangerousprototypes.com/docs/Bus_Blaster_OpenOCD_guide)
1. Install a driver (libUSB)
2. …
So did I, using the libusb documentation here (http://http://www.libusb.org/wiki/libusb-win32).
The last version is 1.2.4.0 (dated April 12th). See here (http://https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/).
“Starting from version 1.2.1.0, the inf-wizard.exe has embedded driver binaries and provide an option to install the driver at the end of the process.â€
Fine, a few clicks and the driver is installed for both interfaces of FT2232H.
Interface 0 (click to see the screen copy) (http://http://openbox4.perso.neuf.fr/LIBUSB/PROP_DC_A_LUSB.jpg)
Interface 1 (click to see the screen copy) (http://http://openbox4.perso.neuf.fr/LIBUSB/PROP_DC_B_LUSB.jpg)
This is confirmed by testlibusb (click to see the screen copy) (http://http://openbox4.perso.neuf.fr/LIBUSB/TESTLUSB.jpg)
Looking to Device Manager, I’m not happy however: the corresponding virtual ports have disappeared.
(http://http://openbox4.perso.neuf.fr/LIBUSB/DEVMNGR_LUSB.jpg)
Note : the drivers are in a specific libusb-win32 devices group.
Which means that I can’t use the DP FT2232H breakout board.
But what about OpenOCD?
Just download (here) (http://http://www.freddiechopin.info/index.php/en/download/category/4-openocd) and install it…
The first strange and contradictory information is :
“OpenOCD 0.4.0 for Windows. An msi installer of complete package and it's md5 checksum. Due to alleged GPLv2 license incompatibility of using ftd2xx.dll libraries, this version was compiled to use libftdi + libusb-win32 libraries.â€
Hmmm. DP wiki says that libusb is required but OpenOCD says that libftdi is required too.
What about libftdi?
As a result of the OpenOCD installation, a libftdi.dll and a libusb0.dll are included in the same directory of openocd.exe.
Fine, but this libfdti.dll may be a little old.
Let’s go here (http://http://www.intra2net.com/en/developer/libftdi/)
Last version is from yesterday : 2011-05-23: Version 0.19 of libftdi released
No libftdi.dll is included and I did not find a way to generate it.
The good point is that at the end, I start openocd which seems to work (even with some difficulties at this time, but on the board side, ie. Dockstar)
Questions :
1 - I’ve lost the virtual ports for all the VID=0403 PID=6010 devices. How to fix this issue ?
2 – How to run with the last libftdi under windows ?
I may have some wrong understanding, but up to now, I do not find how.
Any idea ?
Regards
Marc
The problem is , that you reinstalled the Virtual COM ports to use the libusb.
If you want the serial ports back, you need to reinstall the old driver back.
(delete the device from device manager, remove the oem47.inf oem48.inf from windows/infs, and replug the device)
Tnks, but ...this means that we have to "swap" the drivers according to the usage we have of a FT2232H device. Not really optimal.
And more, it is not possible to have at the same time Busblaster AND another FT2232H for a native virtual port.
I had expected the ability to change (using eprom ?) the the PID of the busblaster. Could it be possible ?
[quote author="cuagn"]I had expected the ability to change (using eprom ?) the the PID of the busblaster. Could it be possible ?[/quote]
Hi Cuagn,
I also find this annoying. libftdi for windows is build on libusb, I think you get both with the installer you used. I believe that is how I installed them in the past.
You can change the PID of the Bus Blaster using the FTDI utility (FT_PROG) here:
http://www.ftdichip.com/Support/Utilities.htm (http://www.ftdichip.com/Support/Utilities.htm)
I will apply for a PID for the Bus Blaster from FTDI if you like.
Hi ian,
I did not test (up to now) your solution with FT_PROG as I just wanted to unbrick my Dockstar.
It seems to be the solution to my question and ... our problem.
By the way, I think that this issue (and solution) may be documented in the Wiki as many people may have the same problem.
From my point of view, I don't see (own usage) an advantage of having a specific PID allocated by FTDI.
You may have another view with a DP global business approach.
Thank you for your answer.
Marc
PS : not terminated, but unbrick of Dockstar is on the way. Very efficient data transfer through BusBlaster with OpenOCD. Thank you.
PS2 : any idea with libftdi version ?
Thanks for the update. I added a link to FT_PROG on the wiki, but there should really be a tutorial. I'll also apply for the ID so there is an open ID anyone can use to reprogram the Bus Blaster and avoid this issue.
Sorry, not sure about FTDI version. I just ran the installer that you describe, and allowed it to install the .inf at the end of the process.
Hi Ian,
We have allocated an additional 8 PIDs to your company from 8878 through 887F (hex).
The PIDs must be used with VID 0403.
To reprogram the EEPROM use MPROG (http://www.ftdichip.com/Support/Utilities/MProg3.5.zip (http://www.ftdichip.com/Support/Utilities/MProg3.5.zip) ) or FT_PROG (http://www.ftdichip.com/Support/Utiliti ... _v1.10.zip (http://www.ftdichip.com/Support/Utilities/FT_Prog_v1.10.zip) )
You can easily create customized INF files by using our FT_INF utility:
http://www.ftdichip.com/Support/Utilities/FT_INF.zip (http://www.ftdichip.com/Support/Utilities/FT_INF.zip)
NOTE 1: Editing the driver for your new identity will invalidate any current driver certification.
NOTE 2: It will be necessary for you to maintain your own edited driver release for distribution to your customers.
NOTE 3: Please send us a copy of your INF files when you have completed your changes to them. We will review them for you.
Please reference the following application and technical notes:
http://www.ftdichip.com/Support/Documen ... elines.pdf (http://www.ftdichip.com/Support/Documents/TechnicalNotes/TN_100_USB_VID-PID_Guidelines.pdf)
http://www.ftdichip.com/Support/Documen ... oducts.pdf (http://www.ftdichip.com/Support/Documents/TechnicalNotes/TN_102_OEM_Technical_Support_Requirements_for_FTDI_Products.pdf)
http://www.ftdichip.com/Support/Documen ... rocess.pdf (http://www.ftdichip.com/Support/Documents/AppNotes/AN_101_WHQL_Certified_Driver_Process.pdf)
Regards,
Savyasaachi Keshava Murthy
Applications Engineer
I applied for and received some PIDs for the Bus Blaster. You can use these as dedicated PIDs if you need something other than the default. Suggested use:
0403 8878 for Bus Blaster v2 serial channel A
0403 8879 for Bus Blaster v2 serial channel B
Other PIDs are reserved for future projects. We will not release custom .infs for the time being, but the libftdi install package will create a custom .inf you can use.
Perfect! :)
Also added to the wiki here: http://dangerousprototypes.com/docs/Bus ... ID_and_PID (http://dangerousprototypes.com/docs/Bus_Blaster_custom_USB_VID_and_PID)