6 Replies Latest reply on Aug 15, 2016 8:19 PM by xavier@candyhouse

    migrating from BCM EVAL board using FTDI to target board using J-link

    wmjbrown

      I have been pulling my hair out (which I can ill-afford) trying to get my j-link Pro to download firmware to my target board.

       

      I developed some working software that sends telemetry to Azure IoT hub using a Broadcom Eval board.  Now I need to move onto the actual hardware which has a SWD interface. Segger recognized the CEL WiFi module so I know thats working.

      I installed the CEL module platform files in the platforms folder.

       

      I installed the Segger J-link plug-in into WICED.  The configurations window shows J-link features under the debugger and the Startup tabs.

       

      I carefully followed the directions at this link:  Re: Jlink support for wiced sdk not working.

       

      The make target references the CEL WiFi module  ( Telemetry-CEL_WB4343WF3SP2  JTAG=jlink download )

      The program compiles and links without error.

      But when it comes time to download it to the target board I get the now infamous:

            "**** OpenOCD failed - ensure to have installed the driver from the drivers directory ..." error message.

       

      The drivers directory only has one entry and it is BCM9WCE1EVAL which is the Eval board that I used successfully.  This is a bit suspicious as I don't know how to (or if I need to) include a driver entry for my CEL module.

       

      My .gdbinit file looks like this...

      shell start /B ./tools/OpenOCD/Win32/openocd-all-brcm-libftdi.exe -f ./tools/OpenOCD/Jlink.cfg -f ./tools/OpenOCD/stm32f4x.cfg -f ./tools/OpenOCD/stm32f4x_gdb_jtag.cfg -l build/openocd_log.txt

       

      The first entry in the openocd_log.txt looks like this....

      Open On-Chip Debugger 0.9.0-00029-gafd5db2-dirty (2015-05-29-18:47)

      Licensed under GNU GPL v2

      For bug reports, read

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

      adapter speed: 1000 kHz

      adapter_nsrst_delay: 100

      Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.

      jtag_ntrst_delay: 100

      Warn : target name is deprecated use: 'cortex_m'

      jtag_init

      Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED

      Error: Cannot find jlink Interface! Please check connection and permissions.

       

      I've been at this for almost a week and it is frustrating fighting my tools rather than using them to do my job.

       

      Any thought would be gratefully received.

       

      Bill