Very good comments from Dave, I will think about them, do some testing
on vector catch and the state after reset.
For now I have commited but the omap3_reset function is removed, since
this is handled by "reset halt"
Regards,
Magnus
___
Openocd-develo
On Thursday 01 October 2009, John Rigby wrote:
> Any ideas? This is all new to me, how does one figure out irlen's and
> masks? The only thing I found in the reference manual was the cpu tap id
> and some vague illustrations but no real details.
Using *current* code it's safe to forget about the
On Wednesday 30 September 2009, Magnus Lundin wrote:
> David Brownell wrote:
> > I think that's not quite following the model which the code in
> > the src/helper/startup.tcl file is expecting ... a closer match
> > would use reset-assert-pre (or maybe "post") not reset-start.
>
> I have done some
Minor ETB and ETM bugfixes and doc updates
- ETB
* report _actual_ hardware status, not just expected status
* add a missing diagnostic on a potential ETB setup error
* prefix any diagnostics with "ETB"
- ETM
* make "etm status" show ETM hardware status too, instead of
just
On Thursday 01 October 2009, Magnus Lundin wrote:
>
> For testing and comments
As for the latter ... this looks sufficiently generic that
I don't see why it should even be needed. IMO the core
code *should* do all of this without needing a method!
The fact that cache validation *isn't* automati
