On Mon, Jun 21, 2010 at 4:01 PM, David Brownell wrote:
>
>
> --- On Mon, 6/21/10, Øyvind Harboe wrote:
>
> > From: Øyvind Harboe
> > Subject: Re: [Openocd-development] TI AM3517 status
> > Looks like I'm talking
> > to the CPU at least as it seems to b
--- On Mon, 6/21/10, Øyvind Harboe wrote:
> From: Øyvind Harboe
> Subject: Re: [Openocd-development] TI AM3517 status
> Looks like I'm talking
> to the CPU at least as it seems to be able to figure out
> that
> the CPU has 6 breakpoints and 2 watchpoints, whi
Even more progress...
Connecting to the target, resetting it and stepping seems to
work well enough for alpha testing...
Note that I've got a number of patches for basic error handling
posted that I'm running with, I don't think it will have any effect
unless there are communication problems(e.g.
I think I've made some more progress... Looks like I'm talking
to the CPU at least as it seems to be able to figure out that
the CPU has 6 breakpoints and 2 watchpoints, which sounds
about right I suppose.
oyv...@titan:~/workspace/openocd$ openocd -f ../ti.cfg
Open On-Chip Debugger 0.5.0-dev-003
Results from auto probing.
1. Power cycle
2. run the test twice, second time the result is different...
oyv...@titan:~/workspace/openocd$ openocd -c "interface ZY1000" -c
"zy1000_server 10.0.0.69" -c "reset_config trst_only" -c init -c reset
-c shutdown
Open On-Chip Debugger 0.5.0-dev-00357-g2d
I've hooked it up and fixed some error handling problems in OpenOCD.
Now I'm stuck until I can find documentation on the JTAG chain for
this part. (Or rather I don't particularly enjoy the prospect of resorting
to reverse engineering...). Hopefully I've just overlooked some obvious
resource that i
