I have abandoned trying to use my J-link in favor of an Olimex JTAG_ARM-USB-OCD-H dongle.
I am trying to configure WICED to use it but I am still getting the OpenOCD failure at the boot-load stage.
I have loaded the requisite drivers and my device manager shows…
WICED USB JTAG Devices
Olimex OpenOCD AMR-USB-TINY-H
Olimex OpenOCD JTAG ARM USB-TINY-H (Interface 0)
I am reasonably sure that my Olimex dongle is properly wired because I can start OpenOCD as follows:
openocd -f ./interface/ftdi/olimex-arm-usb-tiny-h.cfg
-f interface/ftdi/olimex-arm-jtag-swd.cfg
-f ./target/stm32f4x.cfg <NL>
Open On-Chip Debugger 0.9.0-rc1 (2015-04-24-22:09)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : FTDI SWD mode enabled
adapter speed: 2000 kHz
adapter_nsrst_delay: 100
none separate
cortex_m reset_config sysresetreq
Info : clock speed 2000 kHz
Info : SWD IDCODE 0x2ba01477
Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints
You may have noticed, I am using the SWD interface and not JTAG. I have the Olimex SWD adapter in between the dongle and the target.
In addition, I can start a PuTTY telnet session and manually interact with OpenOCD on the target board.
First questions:
- Must I start OpenOCD prior to running WICED ?
- If so is so is there a way to make WICED do that for me?
- Is there something I need to do in WICED since I am using the SWD interface?
In WICED my Make Target entry is:
MyProgram CEL_WB4343WF3SP2 JTAG=Olimex_ARM-USB-TINY-H download
Next questions:
What settings do I need in each of the debug configuration tabs?
In Main I have:
C/C++ Applictions: build/eclipse_debug/last_built.elf
Project: WICED_SDK
In the Debugger Tab I have:
<path> \WICED\WICED-SDK-3.5.2\WICED-SDK\tools\ARM_GNU\bin\Win32\arm-none-eabi-gdb.exe
Under remote target, in the JTAG device pull-down I chose OpenOCD (via pipe)
In the Startup Tab
In the checked box under Halt I have:
add-symbol-file build/eclipse_debug/last_bootloader.elf 0x8000000
This worked before I switched to the Olimex dongle and was using a Broadcom BCM Eval module prior to my target hardware.
"Load Image" is checked using project binary.
The first entry of the openocd_log.txt file after a download attempt is...
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
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
Sorry for all the exposition but I wanted to give as much information as possible to perhaps reduce some back and forth.
Any help convincing WICED to download my compiled program into my target via the Olimex dongle will get you included in my will.
Thanks
