Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: spurious interrupts on LPC

2006-03-14 by Jayasooriah

Dear Robert,

In the FAQ you referred to, on "ARM7DTMI-S Core", to the FAQ:

"Can spurious interrupts occur in the LPC200?",

Your answer is:

"Yes, spurious interrupts can occur in any ARM7 device that has implemented 
the ARM Primecell Vectored Interrupt Controller (VIC)."

I tried looking for a reference to this in the ARM site but cannot find any.

A search on "spurious" at the ARM web site yields 11 hits but these appear 
not relevant to the VIC and spurious interrupt problem with the ARM design 
that you seem to allude us to.

I also did a brief search for information on the web relating to spurious 
interrupts, and all the examples seem to point to LPC one way or another.

A spurious interrupt is a hardware interrupt which is generated by system 
errors (http://www.answers.com/topic/interrupt-1), and systems with 
spurious interrupts in general do not meet compliance requirements.

Please clarify:

1/  Is this spurious interrupt problem an error in LPC implementation of 
VIC or is it an error in ARM Primecell VIC specifications itself?

2/  Can you tell us if there are any other ARM cores with VIC that also 
suffer from spurious interrupts problem that the LPC suffers from?

Kind regards,

Jaya

PS:  I realise there has been discussion previously on spurious interrupts, 
but none seem to throw any light on whether this is a problem specific to 
LPC or it has to do with with ARM VIC design itself.

--- In lpc2000@yahoogroups.com, "philips_apps" <philips_apps@...> wrote:
 >
 > Hi,
 >
 > have a look at the FAQ here:
 >
 > http://www.standardics.philips.com/support/faq/microcontrollers/
 >
 > I also added a link in the link section named
 > "Philips FAQ for LPC2000 devices"
 >
 > Regards, Robert

Send instant messages to your online friends http://au.messenger.yahoo.com

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.