1 Reply Latest reply on Oct 1, 2015 11:51 AM by mkochhal

    Connecting the Olimex JTAG ARM-USB-OCD-H

    mkochhal

      With the Olimex-JTAG-USB-OCD-H, I get the following errors. I build the application with the command:  make.exe snip.uart-ISM43341_M4G_L44 JTAG=Olimex_ARM-USB-OCD-H download run

       

      Also, I have modified the wiced_toolchain_common.mk under tools\makefiles\ has the line for JTAG set as:

       

      JTAG         ?= Olimex_ARM-USB-OCD

       

      Finally, my drivers on Windows side have been installed using zadig installer …

       

       

      Making .gdbinitC:\MyFiles\mkochhal\workspaces\wiced_3.4.0_latest_ws\WICED-SDK-MFi-3.4.0>make.exe snip.uart-ISM43341_M4G_L44 JTAG=Olimex_ARM-USB-TINY-H download

       

      Applying changes made to: tools/makefiles/wiced_toolchain_common.mk

      +-----------------------------------------------------------------------------------------------------+

      | IMPORTANT NOTES                                                                                     |

      +-----------------------------------------------------------------------------------------------------+

      | Wi-Fi MAC Address                                                                                   |

      |    The target Wi-Fi MAC address is defined in <WICED-SDK>/generated_mac_address.txt                 |

      |    Ensure each target device has a unique address.                                                  |

      +-----------------------------------------------------------------------------------------------------+

      | MCU & Wi-Fi Power Save                                                                              |

      |    It is *critical* that applications using WICED Powersave API functions connect an accurate 32kHz |

      |    reference clock to the sleep clock input pin of the WLAN chip. Please read the WICED Powersave   |

      |    Application Note located in the documentation directory if you plan to use powersave features.   |

      +-----------------------------------------------------------------------------------------------------+

      Building Bootloader

      Finished Building Bootloader


      snip.uart-ISM43341_M4G_L44

      ----------------------------------|---------|---------|

                                        |         |  Static |

                    Module              |  Flash  |   RAM   |

      ----------------------------------+---------+---------|

      App                               |     247 |      88 |

      Host MCU-family library           |    4448 |     356 |

      Interrupt Vectors                 |     388 |       0 |

      libc                              |   21844 |    3064 |

      platform                          |    1176 |     264 |

      RAM Initialisation                |    2252 |       0 |

      Ring_Buffer                       |      94 |       0 |

      ThreadX                           |    5000 |     396 |

      WICED                             |     156 |       0 |

      WWD                               |     299 |      56 |

      ----------------------------------+---------+---------|

      TOTAL (bytes)                     |   33652 |    4224 |

      ----------------------------------|---------|---------|


      Downloading Bootloader ...

      "**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual

      machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"

      Downloading DCT ...

      "**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual

      machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"

      Downloading Application ...

      "**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual

      machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"

      Build complete

       

      The  openocd_log.txt under build/ shows the following:

       

       

      Open On-Chip Debugger 0.9.0-00029-g9f797a3-dirty (2015-09-16-09:22)

       

      Licensed under GNU GPL v2

      For bug reports, read

        http://openocd.org/doc/doxygen/bugs.html

      Info : only one transport option; autoselect 'jtag'

      trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst

      adapter speed: 1000 kHz

      adapter_nsrst_delay: 100

      jtag_ntrst_delay: 100

      Warn : target name is deprecated use: 'cortex_m'

      jtag_init

      Warn : Using DEPRECATED interface driver 'ft2232'

      Info : Consider using the 'ftdi' interface driver, with configuration files in interface/ftdi/...

      Error: unable to open ftdi device: device not found

       

        • 1. Re: Connecting the Olimex JTAG ARM-USB-OCD-H
          mkochhal

          Hi.

           

          I finally got the Olimex JTAG ARM-USB-OCD-H to work.

           

          Basically, the instructions are as follows:

           

          (1) Disable Driver Signing (Windows 8 and beyond, have to do this every time you restart machine)

            (a) PC Settings

            (b) Troubleshoot/Recovery

            (c) Advanced Settings/Startup Options

            (d) Restart

            (e) Option 7 to disable driver signing

            (f) Restart

           

          (2) Install OpenOcd (if needed)

          (3) Install Olimex driver FTDI Drivers (CDM v2.12.04 Olimex). Make sure VID = 0x15BA and PID = 0x002B

          (4) Use libusb to select and install

          (5) Run testlibusb.exe to verify that libusb identifies these Olimex interfaces as USB driver interfaces

            (a) if libusb is not installed right, it will show up as:

           

                        C:\libusb-win32-bin-1.2.6.0\bin\amd64>testlibusb.exe

                              Dev #0: 0000 - 0000

           

          (b) If it is installed right, it will show up as:

                        C:\libusb-win32-bin-1.2.6.0\bin\x86>testlibusb.exe

                              Dev #0: 0000 - 0000

                              Dev #1: Olimex - Olimex OpenOCD JTAG ARM-USB-OCD-H

                              Dev #2: Olimex - Olimex OpenOCD JTAG ARM-USB-OCD-H

          (6) Modify wiced_toolchain_common.mk to include

              JTAG        ?= Olimex_ARM-USB-OCD-H

          (7) Make sure you have the latest versions of the cfg files for Olimex and STF4

          (8) If it complains about SRST signal not being set/reset, put the following config option at the end of the olimex config file

          reset_config trst_and_srst srst_open_drain

           

          Please find attached openocd_log.txt, output of the make command for downloading through JTAG, FTDI drivers and libusb I used and the cfg files for STF4 and Olimex

          1 of 1 people found this helpful