SparkFun Electronics Forum

As promised, please find a fully GPL compliant binary version of OpenOCD (v0.3.0-dev 2009.10.12) for Windows 64 bit systems.

DOWNLOAD HERE

README: Note that since it is still a bit experimental, it was compiled with debug information, so that you can use WPG System64's gdb in case of problems

I will post the compilation steps later on.

Enjoy!

Hi,

I need 32 bit windows version, but i can't pass the compile, may you help?

forgot to say, i need the --enable-jlink option for configure, thanks

wxzzzh wrote:I need 32 bit windows version, but i can't pass the compile, may you help?

Trouble reading?

viewtopic.php?t=16422

4\/3!!

Are you going to support parallel port devices like wiggler in 64-bit releases? Giveio is 32bit only, but there are other direct hardware access drivers like InpOutx64 or WinRing0 that supports 64-bit windows systems.

Hi,

I'm not planning on becoming a maintainer of Win x64 OpenOCD binary releases I'm afraid. My goal was, since people seemed to have some trouble getting a working OpenOCD for Win x64 and FTDI devices, to show one way to do just that. The binaries I released were just a byproduct of this.

Now that the Win x64 patches have been integrated in both libftdi and OpenOCD, I'm hoping that the regular distributors of the Windows binaries can provide both a 32 and 64 bit version for people who don't want to recompile their own.
Otherwise, with WPG System64 providing everything you need to compile in a single zip file, producing 64 bit binaries should no longer be a major headache.

If GiveIO-32 is open source as libusb-win32 is, you can probably apply the same trick to get a working 64 bit Windows driver (that you'll have to self-sign to install, but that's a different issue). Else, I'm pretty sure that someone with a Wiggler and running 64-bit Windows will be as annoyed as I was with the FTDI thing and post a tutorial.

el_nihilo wrote: Else, I'm pretty sure that someone with a Wiggler and running 64-bit Windows will be as annoyed as I was with the FTDI thing and post a tutorial.

However I've found temporary workaround - install MS Virtual PC on 64 bit machine, run Win XP 32 bit in virtual machine and run OpenOCD 32-bit there. This will setup TCP server for GDB. GDB will work fine on 64 bit system with a TCP connection to OpenOCD.

el_nihilo wrote:Now that the Win x64 patches have been integrated in both libftdi and OpenOCD, I'm hoping that the regular distributors of the Windows binaries can provide both a 32 and 64 bit version for people who don't want to recompile their own.

Actually there's noone else but me providing Windows binaries.

If you'd be willing to test the installers that I could produce, then I could post x64 version along with 32-bit one on my website. I don't have a 64-bit system to test whether everything is fine.

If GiveIO-32 is open source as libusb-win32 is, you can probably apply the same trick to get a working 64 bit Windows driver (that you'll have to self-sign to install, but that's a different issue). Else, I'm pretty sure that someone with a Wiggler and running 64-bit Windows will be as annoyed as I was with the FTDI thing and post a tutorial.

If the Wiggler cannot be used right now, than we must wait for someone to test and fix that <:

4\/3!!

Hi Freddie,

Freddie Chopin wrote:Actually there's noone else but me providing Windows binaries.

Yeah, I feared as much...

If you'd be willing to test the installers that I could produce, then I could post x64 version along with 32-bit one on my website.

I'm fine with that. It is of course preferable to provide both 32 and 64 bit Windows binaries in one place, and your site is the logical choice. If you're willing to produce the x64 binaries yourself, then I'll help out as much as I can.
Right now, I only have a Vista x64 machine (no Windows 7 yet), and the only JTAG interface I have is FTDI based, so I hope that's OK.

I replied to your latest post in the OpenOCD mailing list, so that you have my e-mail.

I would like to include libftdi and libusb with WPG System64 (the portable development environment (i.e. gcc) used to build these binaries.) Hosting of OpenOCD binaries is not really relevant, but I can give things a head start with the appropriate libraries. I have built a ton of libraries for ffmpeg implementation(s) as well, might be relevant.

I haven't touched libftdi, heard it was not an easy build, however I have tried building libusb and gave up (quickly, at that time decided it wasn't worth the time.)

Let me know what is appropriate to include and any key issues to build it. (I am lost on the GPL version >=2 vs. 3 as well, I am still unsure if I can use GPL v3, I haven't been.)

Thanks!

Hi xenofears,

I think having the 1.x version of libusb working with mingw (64 bit or not) would be a worthwhile endeavour indeed. I started looking at it myself, and after a few patches, I got to a stage where all that's needed is writing the windows OS wrapper for all the USB I/O (still a major undertaking!).
With WPG System64 including pthread-win32, the most troublesome part is picking up some emulation code for poll() and pipe(), which the git-core guys already seem to have worked around. Hopefully, that'll be good enough for libusb.

Of course getting libusb compile with an empty OS wrapper is not much of an achievement, and, apart from the time it's likely to take to get someone to write a libusb 1.x compatible wrapper, there might be some nasty surprises, as it might not be possible to avoid the need to write a custom driver (as in libusb-win32 0.1.x).

Oh, and libftdi compiles and works just fine with WPG System64, especially after they included one of the patches I submitted. The only real issue is with libusb, which libftdi requires.

Well, unfortunately, this process does not work for me. I'm using Windows 7 64-bit (build 6.1.7600).

There are at least three failure mechanisms that I've encountered (I was running the scripts as Administrator in all cases):

1. the windows_enable_test_mode.cmd script looks for the string "Version 6", but although VER does in fact contain that string (outputting:
Microsoft Windows [Version 6.1.7600], the test fails, and the script doesn't run.
I bypassed the test to get the script to run, leading to:


2. bcdedit /store c:\boot\bcd /set testsigning yes
would fail in every case (I was running in a cmd.exe shell, running as administrator).
Finally, I just skipped the store part, and just ran
bcdedit /set testsigning yes
which succeeded, and then I rebooted, leading to:

3. after rebooting, the screen displays "test mode"
I followed the instructions and proceeded until 'Update Driver Software"...
I browsed to the openocd/drivers/ directory, selected Next, and Windows says
"there are no valid drivers in this location".

I don't know how to hack this process any further. Is there any way to actually get this to work??