Jeff Williams a écrit :
If MC1322x standard then good luck getting it to work. Trust me, this
is not a trivial matter. It took me almost a month to figure it out,
and this is after smart, seasoned people had already broken their
picks on it.
But there's no point in debating - the
Hey guys,
The recent jtag.[h,c] and jlink.c churn has totally hosed all of my
pending patches. BTW: these changes included a lot more than just
fixes to the TAP handling for significant improvement in efficiency
and increased device support. I'd also included a whole bunch of
changes to
If MC1322x standard then good luck getting it to work. Trust me, this
is not a trivial matter. It took me almost a month to figure it out,
and this is after smart, seasoned people had already broken their
picks on it.
But there's no point in debating - the fact is that increased
Hello List,
I think it is very tricky to get the jlink to work with openocd.
In the last time, a year ago, I think the r717 was working with
STR710, SAM7S but not with LPC2148. With the lat version, I tested
started at r1454 I had no success with the STR710 anymore.
Therefore I was happy to hear
You know in the old days source code control systems (SCCS) would
require a developer to check out a copy of the code, and while it was
checked out, nobody else could modify the code. This was before the
merge routines were as smart as they are today.
There has been a LOT of traffic on this
On Tue, 2009-04-21 at 09:13 -0700, Jeff Williams wrote:
Hey guys,
The recent jtag.[h,c] and jlink.c churn has totally hosed all of my
pending patches. BTW: these changes included a lot more than just
fixes to the TAP handling for significant improvement in efficiency
and increased