StepByStepGuide to build OpenOCD+FTD2XX_driver for Windows

StepByStepGuide to build OpenOCD+FTD2XX_driver for Windows#79297

By pieterc - Fri Aug 21, 2009 9:42 am

- Fri Aug 21, 2009 9:42 am #79297

Hi everyone,

I have created a step by step guide to build OpenOCD 0.2.0 for Windows using Cygwin (a Linux-like environment for Windows). It is linked against FTDI's proprietary (non-GPL) FTD2XX Driver to support FT2232x based JTAG interfaces.

Visit:
http://piconomic.berlios.de/build_openocd.html

Best regards,
Pieter

#79462

By dougm84 - Mon Aug 24, 2009 8:36 am

- Mon Aug 24, 2009 8:36 am #79462

Hi there,

I'm curious, do we need to edit the changes to the ftd*.inf files to match our product IDs and device IDs, or do your changes match all types of JTAG (i.e. the Olimex).

#79466

By pieterc - Mon Aug 24, 2009 9:53 am

- Mon Aug 24, 2009 9:53 am #79466

I'm not an expert with windows drivers and *.inf files, but here's my best guess.

The *.inf files can support multiple VID/PID combinations, but you have to add a line for each one. I don't think you can use a "*" wildcard. If you examine the standard CDM driver from FTDI, you will see that it supports VID_0403&PID_6001, VID_0403&PID_6010 and VID_0403&PID_6011.

You can find out your interface's VID/PID by examining the CFG file in the openocd/interface sub directory and searching for "ft2232_vid_pid".

Best regards,
Pieter

SparkFun Forums