Re: [Openocd-development] run algorithm problems - and irq fiq
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 notice though that the ARM11 does not turn this on. arm11.c - line 1464 Odd.. I don't understand the details there. -Duane. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] run algorithm problems - and irq fiq
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: > > 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 don't see it. > Same for arm7/9. > > I seem to be missing something.. > > -Duane. > > ___ > Openocd-development mailing list > Openocd-development@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/openocd-development > ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] run algorithm problems - and irq fiq
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_code") > > Does something do that? I don't see it. > Same for arm7/9. > > I seem to be missing something.. > > -Duane. > > ___ > Openocd-development mailing list > Openocd-development@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/openocd-development > Hey all, I wanted to second a look into this. I have some code that uses interrupts and I was doing a flash verify on an ARM7. It failed and this might be one of the reasons. // Dean Glazeski ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] run algorithm problems - and irq fiq
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 don't see it. Same for arm7/9. I seem to be missing something.. -Duane. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development