OLIMEX© 2015
ARM-USB-OCD user's manual
3.5.2 Changing the VID and PID of the debugger
DISCLAIMER: CHANGING THE VID AND PID IS NOT RECOMMENDED FOR
BEGINNERS. IT MIGHT LEAVE YOUR DEBBUGER IN INRECOVARABLE STATE. SUCH A
CHANGE IS NOT NEEDED FOR TYPICAL USAGE OF THE TOOL AND WE DO NOT
ENCOURAGE IT.
There is a software way to change the VID and PID and the firmware information. It doesn't require
additional hardware tools.
Remember that changing the PID (product ID) would also require to change the definitions in the
drivers and the script in OpenOCD. Changing the VID and PID requires new drivers!
To change any of the FTDI information on ARM-USB-OCD you would need a program called
MPROG which might be found here:
http://www.ftdichip.com/Support/Utilities/MProg3.5.zip
MPROG works only with D2XX drivers. For Windows users: please go to “Windows Device
Manager” and uninstall and delete all drivers associated with ARM-USB-OCD (you might need to
do it multiple times; you might need to disable automatic driver update and installation) until there
are simply two unrecognized interfaces listed. Then download the FTD2XX drivers (from here:
https://www.olimex.com/Products/ARM/JTAG/_resources/driver-ftd2xx.zip
), extract them
somewhere and point manually the installer to that location.
How to use MProg:
1. You need to be sure that you are using FTDI D2XX drivers (not libUSB, not WinUSB, etc).
2. Start MProg
3. Select the FT223H tab in the list in the right part of the interface
4. Under "Programming Options", near the bottom, remove the tick "Only Program Blank Devices".
5. Click "Scan and Parse". If no device shows up – you are not using D2XX drivers. Read above.
6. Click "Edit mode" - until you save the original template the program would not allow you to edit
anything
7. Edit the PID
8. Click "Program All Existing Devices".
At this point, if you are using Windows, the debugger would disappear from the list in “Windows
Device Manager”. Use Zadig or edit the inf files to make the required drivers (just replace the old
PID with the new PID).
3.6 IAR Embedded Workbench for ARM
After installation of the drivers you need to establish a basic connection between the target and
OpenOCD via a command line (as explained in chapter ''3.3.1 Simple target connection via FTDI
drivers''). Finally, you need edit the project settings to be able to use ARM-USB-OCD successfully
(Project properties → GDB server).
Please note that IAR Embedded Workbench is a commercial product not available for free use.
However, there are packages with either time-limited functionality or size-limited binary code
which may be used for evaluation purposes of the described configuration.
Page 25 of 33
