- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am trying to get one of the make targets downloaded to a Murata SN8200 module using a Segger J-Link JTAG probe but I only get the error message starting with:
**** OpenOCD failed - ...
There seems to be some configuration info missing for using J-Link.
I have tried this on both OS X and Windows and get the same kind of error message. My JTAG i a J-Link Ultra+.
- Labels:
-
Debug
- Tags:
- configuration
- download
- downloaded
- error
- failed
- info
- j-link
- jtag
- jtag=jlink
- kind
- make
- message
- missing
- module
- murata
- openocd
- probe
- segger
- sn8200
- starting
- targets
- ultra+
- windows
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I used Olimex unit no problems
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Ulso
Were you able to resolve the J-Link issue? Curious as to whether the JTAG=jlink parameter is actually supported, even though there's a JLINK header on the BCM943362WCD4 board...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Justin,
I gave up and ordered an Olimex dongle.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Changing the line in the file wiced_toolchain_common.mk from:
JTAG ?= BCM9WCD1EVAL1
to
JTAG ?= jlink
did the trick, as well as adding the parameter JTAG=jlink to the make target. Got it running on a Segger J-Link this way.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi all,
same problem with JLink... I tried to change also JTAG line as Justin suggested, but I cannot connect to to the board yet. I have tested that JLink connects in the right way to board, because, with Segger J-Flash utility, I can read the entire chip memory! I have Jlink v.4.84d.
May it be a problem with Segger drivers and openOCD? I got the following message on openocd_log.txt:
cortex_m3 reset_config vectreset
Error: Cannot find jlink Interface! Please check connection and permissions.
Runtime Error: ./Tools/OpenOCD/stm32f2x-flash-app.cfg:10:
in procedure 'script'
at file "embedded:startup.tcl", line 58
in procedure 'init' called at file "./Tools/OpenOCD/stm32f2x-flash-app.cfg", line 10
Open On-Chip Debugger 0.7.0-dev-00227-g9d47214-dirty (2013-04-16-10:43)
Bye,
Andrea
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi All,
Anybody can help? I have the same problem. WICED cannot connect target via JLINK.
I use JLINK and Segger, too.
I have changed JTAG=jlink both in command line and wiced_toolchain_common.mk
Question A, I use segger driver
openocd_log.txt said:
jtag_init
Error: Cannot find jlink Interface! Please check connection and permissions.
Runtime Error: ./tools/OpenOCD/stm32f2x-flash-app.cfg:10:
Question B, I tried Olimex driver to replace current segger driver,
the error information changed:
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
Warn : target name is deprecated use: 'cortex_m'
jtag_init
Info : J-Link initialization started / target CPU reset initiated
Info : J-Link ARM V8 compiled Nov 25 2013 19:20:08
Info : J-Link caps 0xb9ff7bbf
Info : J-Link hw version 80000
Info : J-Link hw type J-Link
Info : J-Link max mem block 9296
Info : J-Link configuration
Info : USB-Address: 0x0
Info : Kickstart power on JTAG-pin 19: 0xffffffff
Info : Vref = 3.306 TCK = 1 TDI = 0 TDO = 1 TMS = 0 SRST = 0 TRST = 0
Info : J-Link JTAG Interface ready
Info : clock speed 1000 kHz
Polling target stm32f2xxx.cpu failed, GDB will be halted. Polling again in 100ms
Error: BUG: can't assert SRST
in procedure 'transport'
Runtime Error: ./tools/OpenOCD/stm32f2x-flash-app.cfg:10:
in procedure 'script'
at file "embedded:startup.tcl", line 58
in procedure 'init' called at file "./tools/OpenOCD/stm32f2x-flash-app.cfg", line 10
Question C:
can WICED IDE use directly the SEGGER J-Link GDB server?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm using a cloned j-link(v8), no problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
The problem there is with Segger J-Link, not with "cloned j-link(v8)"...
Bye
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Sir, what’s the cloned j-link(v8) here refer to? Its prototype is what kind of jtag? Thanks!
Cheers!
James Sun
Office: +86 21 61958367|Cell: 86 189-3096-5899<tel:86%20189%203096%205899>
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well,
1.I'm just tying to say, j-link works fine, even a cloned one.
2.I do have both Segger and cloned , and tried both of them, they all working fine.
3.The cloned j-link came form "taobo", I think you know my words.
4.Thanks for all of your response.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have the same problem.Do u solved?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
no....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ok Solved.
1.download libusb driver - link (http://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-bin-1....)
2.extract
3.run the app "inf-wizard" in libusb-win32-bin-1.2.6.0\bin
4.select jlink
5.complete driver installation.
Now it works fine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I guess it's related to Jlink reset config so I checked and copied reset config of other jtag adapter:
add this line to jlink.cfg :
reset_config trst_and_srst srst_push_pull srst_nogate connect_assert_srst
And it works for me.