ARM-USB-OCD-H : Unabe to establish JTAG communication

[Nathan]

Hi all,
        Below are the details of my set-up:

        Host - Windows 7 32 bit
        JTAG adapter - Olimex ARM-USB-OCD-H
        Target - Custom made fpga bitfile having Corte-M4 core,flashed on Xilinx FPGA.

        I am using Openocd0.9.0,compiled with libftdi1.0. According to this link   (https://www.olimex.com/forum/index.php?topic=3318.0) ,I understand that WinUSB is the defaut driver and installed the same using Zadig tool.In the Device Manager, i see my device detected as
   i) Olimex OpenOCD JTAG ARM-USB-OCD-H (Interface 0)
   ii) Olimex OpenOCD JTAG ARM-USB-OCD-H (Interface 1)
       
   
        Below is my config file:       
        telnet_port 4445
        interface_list
        interface ftdi
        ftdi_device_desc  "Olimex OpenOCD JTAG ARM-USB-OCD-H (Interface 0)"
        ftdi_vid_pid 0x15ba 0x002b

        ftdi_layout_init 0x0908 0x0b1b
        ftdi_layout_signal nSRST -oe 0x0200
        ftdi_layout_signal nTRST -data 0x0100
        ftdi_layout_signal LED -data 0x0800
       
        I am actually trying to get my TAP id read so as to confirm JTAG connectivity is working properly.
        But when i run Openocd,i  get the below error.

        Error: no device found  ftdi
        Error: unable to open ftdi device with vid 15ba, pid 002b, description 'Olimex ARM-USB-OCD-H' and serial '*'
   
        I googled, but i was not able to get a solution for this.
        Can anyone point out what am i doing wrong ?

        Thanks           
                   

[Nathan]

A point to add.
Tried out using the below config file as well

interface ftdi
ftdi_device_desc "Olimex OpenOCD JTAG ARM-USB-OCD-H"
ftdi_vid_pid 0x15ba 0x002b

ftdi_layout_init 0x0c08 0x0f1b
ftdi_layout_signal nSRST -oe 0x0200
ftdi_layout_signal nTRST -data 0x0100 -noe 0x0400
ftdi_layout_signal LED -data 0x0800

But getting the same error in both cases...

[JohnS]

You'd do a lot better to ask on oocd ML I think.

John

[LubOlimex]

Hey there,

Try the easiest connection possible as described in the user's manual! Go to page 21 "3.4.1 Simple target connection via FTDI drivers".

Avoid using the scripts for now. Its a single command line that you need to edit to fit your directory structure and exact target configuration script.

Best regards,
Lub/OLIMEX