On 2009-08-11, Gary Carlson <[email protected]> wrote:
> I am using the same board you are using (except with a J-link
> debugger instead of the Olimex) without too many problems.
>
> You may want to consider moving up to the latest OpenOCD
> software since my recollection is that a number of problems
> were fixed between version 1.0 and 2.0 using that interface.
Doh! I completely overlooked the fact that 0.2.0 was out. I
had tried Gentoo's openocd-9999 ebuild (which builds from the
svn trunk), and I couldn't get it to build for some reason:
emerge wouldn't even recognize the availabilty of the "9999"
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 than that
it's bascially working now.
--
Grant Edwards grante Yow! If elected, Zippy
at pledges to each and every
visi.com American a 55-year-old
houseboy ...
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
