Zach Welch wrote:
> On Tue, 2009-05-12 at 17:59 -0400, Gene Smith wrote: 
>> Someone loaned me an IAR evaluation board STR712 (made by Olimex) and a 
>> yellow IAR J-link (marked J-LINK-ARM-KS on bottom). I had seen quite a 
>> bit of mention on this list about jlink and thought I would give it a 
>> try. I was at r1567 on my initial try (after rebuilding with 
>> --enable-jlink configured).
>>
>> I am starting openocd like this:
>> sudo ./openocd -f target/interface/jlink -f target/target/str710.cfg
>>
>> str710.cfg seems as close to the actual str712 as there is in the cfg files.
>>
>> When it starts I see:
>> Error: J-Link Command 0x01 failed (-2)
>> Error: J-Link command EMU_CMD_VERSION failed (-110)
>> <repeated 3 times>
> 
> The ENOENT error (translated via errno.h) seems to indicate that the
> device is not connected.  I remember having similar problems, but I do
> not immediately recall what the problem was.  It may have been an
> improper connections (e.g. a pair of reversed pins) between the J-Link
> header and my target device, or it might have been a configuration issue
> with my host system.  I do not believe it was directly OpenOCD's fault,
> but I do wish it could more informative here.
> 
> Cheers,
> 
> Zach

I finally got a chance to load the official IAR "Kickstart" software 
that is with the board and jlink and it works fine through the yellow 
jlink.

I tried playing with the jtag speed in the str710.cfg file and it made 
no difference. Don't know what else to do.

I did notice when installing the IAR tools that it mentioned that the 
license key could be "associated with the dongle." I chose not to. 
However, the person who loaned me the jlink and board had used it on 
their PC. Could this license key somehow be disabling the jlink when 
used by non-IAR software (openocd on linux) depending on how they set it 
up on windows? (I know nothing about the internals of the jlink.)

_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to