Lpc2000

--- In lpc2000@yahoogroups.com, "brendanmurphy37" <brendan.murphy@...> wrote:
 > > The TRM does say is that when an interrupt exhibits transient
 > behaviour,
 > > "the priority logic of VIC is not set".  What does "not set" means?
 > >
 > > Set to 0?  1?  ... 15? 16?
 >
 > It doesn't matter what the priority is set to, as the solution
 > doesn't make use of the priority in any way.

I and like minded people who rely in interrupt service handler getting it 
right each and every time do think it matters.

It is this UNDEFINED priority that is acknowledged by the read and write to 
VICVECTADDR in your blindly acknowledging all spurious interrupts.

If you are happy with serving an interrupt the second time around, or 
random preemption of one interrupt with another (totally defeating priority 
levels) then go ahead an ignore these events.

Jaya

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