On 2009-10-16, Redirect "Slash" NIL wrote:
> Any ideas how to fix that?
My guess is you've you've got DOS line endings instead of Unix
line endings.
--
Grant
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.ber
On 2009-10-05, ??yvind Harboe wrote:
> "Migrate away from Berlios" committe wants an alternative to
> Berlios mailing lists.
>
> Some alternatives so far:
[...]
Anything so long as it works with gmane.org.
--
Grant Edwards grante Yow!
ought mercurial would be an
easier transition than git.
I would give a few points to mercurial for being written in
Python. I would expect it to be a lot more stable than
something written in C. However, my opinion shouldn't be
weighted very heavily since I'm just a user
nize the availabilty of the ""
version.
So anyway, it turns out that the 0.1.0 ebuild works fine with
0.2.0 sources, and the resulting openocd recognizes the board
and is able halt the CPU and examine memory and CPU registers.
It still doesn't connect on every attempt, but other
Has anybody gotten OpenOCD to work with an Atmel AT91SAM9G20?
I found a thread from about 6 months ago that indicated it was
partially working with an Amontek JTAG interface, but there
were problems and the thread contained no indication that the
problems had ever been resolved.
I'm trying to use
