Re: [Openocd-development] run algorithm problems - and irq fiq

2009-05-25 Thread Duane Ellis
duane>[about irqs during resume] Magnus Lundin> [look here] > int arm7_9_debug_entry(target_t *target) > Look for buf_set_u32(dbg_ctrl->value, EICE_DBG_CONTROL_INTDIS, ... > and the debug_execution flag. Yes, I see that now, thank you. it is the last parameter to the RESUME function. I notic

Re: [Openocd-development] run algorithm problems - and irq fiq

2009-05-24 Thread Magnus Lundin
Duane Ellis wrote: > I have a observation/question > > When "run algorithm" occurs - what/where - etc are interrupts disabled? > > int arm7_9_debug_entry(target_t *target) Look for buf_set_u32(dbg_ctrl->value, EICE_DBG_CONTROL_INTDIS, ... and the debug_execution flag. > For instance: > > Lo

Re: [Openocd-development] run algorithm problems - and irq fiq

2009-05-24 Thread Dean Glazeski
Duane Ellis wrote: > I have a observation/question > > When "run algorithm" occurs - what/where - etc are interrupts disabled? > > For instance: > > Looking at for instance the armv7 code to "blank check" a flash. >No where does that code *disable* interrupts > > (grep for "erase_check_co

[Openocd-development] run algorithm problems - and irq fiq

2009-05-24 Thread Duane Ellis
I have a observation/question When "run algorithm" occurs - what/where - etc are interrupts disabled? For instance: Looking at for instance the armv7 code to "blank check" a flash. No where does that code *disable* interrupts (grep for "erase_check_code") Does something do that? I do