OpenOCD 0.3.1 - Windows installer

Development Boards MicroMod
1

Shortly after [final source code release, [OpenOCD 0.3.1 compiled for Windows was posted on my website ( www.freddiechopin.info ) in Download > Programs > OpenOCD. The package - as usual - comes in a convenient form of *.msi installer (Microsoft Installer). The installer conditionally removes previous versions (since 0.2.0, inclusive), so one doesn’t have to do that manually.

OpenOCD can communicate with ARM cores via many different ARM JTAGs and it can be used in any opensource toolchain which uses GDB for debugging. New version brings early (but stable) support for processors with [ARM Cortex-A8 cores. This software can also work with the most recent [NXP processors from [LPC17xx ([ARM Cortex-M3) and [LPC29xx ([ARM968) series. Communication with [FT2232H and [FT4232H was also improved. There are many more improvements and additions, which are summarized in [NEWS file that comes with [this version.

Version 0.3.1 fixes a [critical bug that was present in 0.3.0, which made it completely useless.

Due to alleged [GPLv2 license incompatibility of using [ftd2xx.dll libraries, this version was compiled to use [libftdi + [libusb-win32 libraries. Details: [#1, [#2.](OpenOCD - Open On-Chip Debugger - berlios.de)](OpenOCD - Open On-Chip Debugger - berlios.de)](http://libusb-win32.sourceforge.net/)](libFTDI » FTDI USB driver with bitbang mode)](http://www.ftdichip.com/Drivers/D2XX.htm)](GNU General Public License v2.0 - GNU Project - Free Software Foundation)](OpenOCD - Open On-Chip Debugger - berlios.de)](OpenOCD - Open On-Chip Debugger / Git tools)](OpenOCD - Open On-Chip Debugger / Git tools)](http://www.ftdichip.com/Products/FT4232H.htm)](http://www.ftdichip.com/Products/FT2232H.htm)](Microprocessor Cores and Processor Technology – Arm®)](http://www.standardics.nxp.com/products/lpc2000/)](Cortex-M3)](http://www.standardics.nxp.com/products/lpc1000/lpc17xx/)](http://www.nxp.com/)](Microprocessor Cores and Processor Technology – Arm®)](http://openocd.berlios.de/)](berlios.de)

2

Thanks for providing this.

I’ve had trouble installing the included drivers for an Olimex ARM-USB-OCD device on Windows 7 x64. I’ve plugged the device in, waited until the automatic installation finished unsuccessfully, then tried to update the drivers manually pointing to the unzipped libusb-win32_ft2232_driver-091105 folder.

I get the message “Windows found driver software for your device but encountered an error while attempting to install it - A service installation section in this INF is invalid” and the device then turns to an “Unknown Device” in the device manager. The following messages are left in the atupapi.app.log in WINDOWS/inf

[Boot Session: 2009/11/18 14:35:43.125]

>>>  [Build Driver List - USB\VID_15BA&PID_0003&MI_00\7&22BEA1C6&4&0000]
>>>  Section start 2009/11/18 17:39:21.631
      cmd: C:\Windows\system32\svchost.exe -k netsvcs
     cpy: Policy is set to make all digital signatures equal.
<<<  Section end 2009/11/18 17:39:21.692
<<<  [Exit status: SUCCESS]


>>>  [DIF_SELECTBESTCOMPATDRV - USB\VID_15BA&PID_0003&MI_00\7&22BEA1C6&4&0000]
>>>  Section start 2009/11/18 17:39:21.692
      cmd: C:\Windows\system32\svchost.exe -k netsvcs
!    dvi: Selecting driver failed(0xe0000228)
!    dvi: Default installer: failed!
!    dvi: Error 0xe0000228: There are no compatible drivers for this device.
<<<  Section end 2009/11/18 17:39:21.694
<<<  [Exit status: FAILURE(0xe0000228)]


>>>  [Build Driver List - USB\VID_15BA&PID_0003&MI_01\7&22BEA1C6&4&0001]
>>>  Section start 2009/11/18 17:39:33.596
      cmd: C:\Windows\system32\svchost.exe -k netsvcs
     cpy: Policy is set to make all digital signatures equal.
<<<  Section end 2009/11/18 17:39:33.657
<<<  [Exit status: SUCCESS]


>>>  [DIF_SELECTBESTCOMPATDRV - USB\VID_15BA&PID_0003&MI_01\7&22BEA1C6&4&0001]
>>>  Section start 2009/11/18 17:39:33.657
      cmd: C:\Windows\system32\svchost.exe -k netsvcs
!    dvi: Selecting driver failed(0xe0000228)
!    dvi: Default installer: failed!
!    dvi: Error 0xe0000228: There are no compatible drivers for this device.
<<<  Section end 2009/11/18 17:39:33.659
<<<  [Exit status: FAILURE(0xe0000228)]


>>>  [Build Driver List - USB\VID_15BA&PID_0003&MI_00\7&22BEA1C6&4&0000]
>>>  Section start 2009/11/18 17:39:44.055
      cmd: "C:\Windows\system32\mmc.exe" "C:\Windows\system32\compmgmt.msc" /s
     cpy: Policy is set to make all digital signatures equal.
<<<  Section end 2009/11/18 17:39:44.056
<<<  [Exit status: SUCCESS]


>>>  [Build Driver List - USB\VID_15BA&PID_0003&MI_00\7&22BEA1C6&4&0000]
>>>  Section start 2009/11/18 17:39:44.062
      cmd: "C:\Windows\system32\mmc.exe" "C:\Windows\system32\compmgmt.msc" /s
     cpy: Policy is set to make all digital signatures equal.
!    sig: Verifying file against specific (valid) catalog failed! (0x00000057)
!    sig: Error 87: The parameter is incorrect.
!    sig: Verifying file against specific Authenticode(tm) catalog failed! (0x80092003)
!    sig: Error 0x80092003: An error occurred while reading or writing to a file.
<<<  Section end 2009/11/18 17:39:44.068
<<<  [Exit status: SUCCESS]


>>>  [DIF_SELECTBESTCOMPATDRV - USB\VID_15BA&PID_0003&MI_00\7&22BEA1C6&4&0000]
>>>  Section start 2009/11/18 17:39:44.068
      cmd: "C:\Windows\system32\mmc.exe" "C:\Windows\system32\compmgmt.msc" /s
<<<  Section end 2009/11/18 17:3

9:44.069

<<< [Exit status: SUCCESS]

[/code]

Please let me know if there’s a better place to report these issues or if I can provide any other information that might be helpful. Thanks again.

3

From what I know it is impossible to “just install” those drivers on Win7 and 64-bit Vista. You need to perform the steps described in this thread - viewtopic.php?t=17649 - the .inf file itself should be fine, but - just to be sure - for the first time try with the .inf file with that other package

4/3!!

4

Hi Freddie!

First of all thanks for the precompiling work you do for quite a while.

I had used some older versions that did not recognize the lib-ftdi gnu problematics. They worked well.

Seems that some day something had installed some new USB drivers, don’t know if MS supplied an update or some of the cellphon suites did, but now using this old 0.2.0SR1 installation results in a silent hangup of my 32-Bit XP machine.

So I tried upgrading:

Using your 0.3.1 version without modifying the ftdi drivers results in a silent hangup of my 32 Bit XP workstation again.

I (re-)installed libusb-win32 drivers and got through to the telnet console vi port 4444. But access is horrybly slow. Typing characters in the console is sort of 1 character per second.

I read through the forum and used the driver manager to uninstall the Channel A (COM3) device and the general usb device related to it.

By the way I use openocd-usb dongle.

I left the channel B and the related COM4 untouched.

Then I tried some of the manual selectaed drivers from your INF file and had no luck as the openocd couldn’t identify the device. So I added my openocd-usb by doing some copy’n’paste and renaming.

The device is found and the openocd-usb.cfg attaches to the device.

And with the first one or two accesses to the JTAG via openocd the system hangs up again. Again without bluescreen, just a silent death.

What can I do to find the issue, figure out the problem, help to solve it, whatever. Pease, help, all my private projects a relaying on this openocd.

EDIT:

I found the documentation how to build your own ftd2xx based version of openocd using cygwin. I did that and it works quite fine. It communicates through the dongle but doesn’t flash due to script problems. But it doesn’t shoot my XP any longer.

Best regards and thanks in advance

Ulrich

5

Beside uninstalling the driver for serial port you need to uninstall the corresponding device from the “Universal Serial Bus …” (sorry, my Windows is not in English). Have you done that too before installing libusb-win32 drivers?

4/3!!