This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: spurious_IRQ on ARM7
- From: Ilko Iliev <iliev at caretec dot at>
- To: Jonathan Larmour <jlarmour at redhat dot com>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Mon, 25 Feb 2002 14:29:57 +0100
- Subject: Re: [ECOS] spurious_IRQ on ARM7
- References: <5.1.0.14.2.20020222140606.00a89c10@mbox>
> > I have custom board with ARM7 CPU (Atmel AT91M55800) and eCos.
> > I use JEENI and BDI2000 debug interface units with gdb. OS is Linux.
> >
> > My programs work, but every time when a internal/external interrupt appear,
> > spurious IRQ is generated.
> > There is no matter what kind of interrupt is: timer, spi or serial.
> >
> > Is it normal?
>
>Nope. Looks like there might be something about the port which doesn't fit
>your hardware.
For test purpose I got the last eCos snapshot with port for Atmel AT91 CPUs
and Atmel's EB01 evaluation board.
I make a simple test example - the spurious interrupt is generated every
time when the timer interrupt appear.
Which options from "ROM monitor support" (in eCos configuration tool) must
be activated to work the target with JEENI (or BDI2000) without ROM monitor?
When all option in "ROM monitor support" are deactivated the program
crashed in hal_if_diag_init() (in hal_if.c) by
CYGACC_CALL_IF_SET_CONSOLE_COMM macro - the virtual vector table is not
initialized maybe.
My test example work only if I activate "Initialize whole of virtual table".
Do I need virtual vector table to debug with JEENI without ROM monitor?
Why is the spurious interrupt generated?
best regards
Ilko
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss