On Monday 06 July 2009 20:19:54 Øyvind Harboe wrote:
> On Mon, Jul 6, 2009 at 7:06 PM, Dominic<dominic.r...@gmx.de> wrote:
> > On Monday 06 July 2009 16:57:24 Øyvind Harboe wrote:
> >> On Mon, Jul 6, 2009 at 4:25 PM, Dominic Rath<dominic.r...@gmx.de> wrote:
> >> > I can run some tests later today when I get home (~2 hours from now).
> >> > I have a arm926ejs board.
> >>
> >> That would be great!
> >>
> >> It would be especially helpful if you could also read over
> >> arm926ejs.c/arm926ejs_examine_debug_reason() w.r.t. interpretation
> >> of unknown/undocumented MOE values.
> >
> > Any examples of sequences that should fail?
>
> I get MOE=0xe upon "reset run" of i.MX27.

"reset run" works just fine here, but "reset halt" fails, and only a power 
cycle gets the target in a cooperative state after this. The target halt times 
out, and JTAG communication is obviously broken afterwards. Halting isn't 
possible, and I get a bogus debug reason (MOE) 0xf.

------------------
> reset halt
JTAG tap: at91sam9260.cpu tap/device found: 0x0792603f (mfg: 0x01f, part: 
0x7926, ver: 0x0)
JTAG Tap/device matched
timed out while waiting for target halted
Runtime error, file "embedded:startup.tcl", line 226:
    expected return code but got 'TARGET: at91sam9260.cpu - Not halted'
in procedure 'ocd_process_reset'
called at file "embedded:startup.tcl", line 208
called at file "embedded:startup.tcl", line 209
called at file "embedded:startup.tcl", line 225
Runtime error, file "command.c", line 469:
------------------

Regards,

Dominic
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to