Rick Altherr a écrit :
>
>> Does anyone
>> ever get an IAR jlink to work with openocd? If so, please post the
>> configuration files.
>
I got it to work but only with the latest yellow ones from IAR. It
doesn't work at all with the slightly older ones that are black.
It has serious issues though,
A target without a tap is useless since a tap defines how to talk to
that position on the chain. It should be an error if a target doesn't
specify a -chain-position.
Rick
On Jan 27, 2009, at 6:26 PM, Subscriber wrote:
I found problem:
it crashes at this point:
targets.c:1383
comm
I found problem:
it crashes at this point:
targets.c:1383
command_print(cmd_ctx, "%2d: %-10s %-10s %-10s %10d %14s %s",
target->target_number,
target->cmd_name,
target->type->name,
Jim_Nvp_value2name_si
Hello,
I compiled openocd (svn revision 1361) on Ubuntu 8.04 with gcc:
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v
--enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr
--enable-shared --with-system-zlib --libexecdir=/usr/lib
--without-includ
On Jan 27, 2009, at 10:08 AM, Daniel Franzini wrote:
Hi all
I'm able to build and link openocd with the jlink patch enabled.
What patch? JLink support is part of the main openocd source base.
But
it does not work. I also loaded libusb correctly and openocd indeed
finds out and comunicate
Hi all
I'm able to build and link openocd with the jlink patch enabled. But
it does not work. I also loaded libusb correctly and openocd indeed
finds out and comunicates with jlink. But it returns a lot of errors
messages about wrong commands and wrong values returned by functions.
Important fact
