[ECOS] problem about interrupt end
Thu Nov 23 03:34:00 GMT 2006
thank you for answering my question...
I trace the interrupt progress, and I found the number is changed when the
code is going from assembly code to c codeÂ£Â¨call isr through
it's the first time for timer to interrupt and then the program breaks
do you mean there are some other interrupts or the same intererupts
happened during this period(from system bootup to the time of the first
timer interrupt happening)?
and I adjust the stack size ,but it seems it doesn't work :(
thank you again
>From: Nick Garnett <email@example.com>
>To: "jiang jet" <firstname.lastname@example.org>
>Subject: Re: [ECOS] problem about interrupt end
>Date: 22 Nov 2006 10:50:29 +0000
>"jiang jet" <email@example.com> writes:
> > hello everyone:
> > When I am transplating ecos to a board based on mips r3k , I met
> > an interrupt problem: when rtc interrupt is enabled, and isr is
> > called, then go through to interrupt end, here when unlock, the lock
> > number is changed, now it's a very big number:80000730,sometimes it
> > can change to other number such as 800007ec... before the
> > interrupt,the number looks correct which is 1..and suddenly changed to
> > such a big number ,what's reason?
>This looks like memory corruption. 0x80000730 would be a resonable
>data or code address on MIPS.
>Perhaps you are not cancelling the interrupt properly and getting
>interrupt stack overflow.
>Nick Garnett eCos Kernel Architect
>http://www.ecoscentric.com The eCos and RedBoot experts
>Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
>and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
ÃÃÃÃÃÃÂ½Ã§ÃÃÃÃ®Â´Ã³ÂµÃÂµÃ§ÃÃÃÃÂ¼Ã¾ÃÂµÃÂ³Â¡Âª MSN HotmailÂ¡Â£ http://www.hotmail.com
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
More information about the Ecos-discuss