The address you referenced (0x7fffe2ae) is in the boot loader area. Somehow your program must have jumped there or ran up to there. The boot loader is in Thumb code, so if the rest of your code was ARM, you might have generated a Data Abort or Invalid Instruction exception when you ran into the thumb code. Jim --- In lpc2000@yahoogroups.com, "digtalfreak" <digitalfreak@n...> wrote: > I solved the Problem, it was a wrong startupcode that blocked the > modus change. > > But now I have the problem that the interrupt causes an exaption, I > think. The ISR is never reached and if I stop the programm the pc is > pointing to 0x7fffe2ae, this must be somewhere in the RAM-mapped > bootloader, how could this happen and how could I fix this? > > --- In lpc2000@yahoogroups.com, "digtalfreak" <digitalfreak@n...> wrote: > > I am using gcc and insignt and have problems using Interrupts. > > I'm trying to use Timer0 to generate a Interrupt, similar to the Keil > > example "blinky", but the interupt is never generatet because the cpsr > > register seems to be allways switched back to 0xd0. Looks like my "msr > > cpsr_c, #0x10" is ingored or overwriten. > > btw... the precompiled keil example works with insight, timer is > > running and genarating interrupts. > > > > please help...
Message
Re: Interrupt Question
2004-05-06 by jim_e_dallas
Attachments
- No local attachments were found for this message.