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 - th
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 increa
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 thi
On Tue, Apr 21, 2009 at 8:06 PM, Dean Glazeski wrote:
> Jeff,
>
> I think we all need to take a deep breath for a second. The project is
> managed in SVN, there can be a revert of changes to a different revision and
> Zach or some one else can repeat the warning removal process. Warning
> remova
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
Jeff,
I think we all need to take a deep breath for a second. The project is
managed in SVN, there can be a revert of changes to a different revision
and Zach or some one else can repeat the warning removal process.
Warning removal is much more trackable than the stuff you have
accomplished
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
efficien
Hi
Yes there are significant changes, I can not comment about the
improvements in efficency. The BIG problem is that it broke existing
code, mainly the ftdi2232 interface. This is not perfect by any means
and needs work, but it is a main workhorse in OpenOCD. Duane has put
work into getting
Please post a patch against the version you have
been working.
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berl
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
10 matches
Mail list logo
