ARM spurious IRQ/FIQ
Posted by Glen B.
on November 7, 2006
(I thought I posted this earlier, but it didn't appear so I am trying again)
Richard, et al
I have recently been addressing spurious interrupt
issues on an LPC2000 processor. There are a variety
of issues - related to the pipeline, the VIC, and some
The issue I bring to this forum is one in the ARM core
itself, due to the pipeline architecture. It involves
a scenario in which an IRQ can happen with IRQ/FIQ
interrupts disabled. This is discussed fairly well in
the Philips User Manuals - I used UM10114_1.pdf.
My concern is with the point that if such an interrupt
is processed without taking any special action, then FIQs
remain disabled during the whole IRQ processing. There
are several possible fixes, but for various reasons I
like the one in which interrupts are disabled by first
disabling IRQs, then disabling FIQs.
I have made this change in my version of FreeRTOS, but
I suggest it should be in the distributed code. This would
involve changing everywhere:
ORRR0, R0, #0xC0
ORRR0, R0, #0x80
ORRR0, R0, #0x40
RE: ARM spurious IRQ/FIQ
Posted by Nobody/Anonymous
on November 8, 2006
Thank you for your informative post. I think your suggestion should be adopted. Some ports use intrinsics to disable the interrupt __disable_interrupt() in IAR for example. I think these should be changed to assembly also for consistency.
Some demo apps install a spurious interrupt handler and some dont. Is there a reason for this?
Copyright (C) 2004-2010 Richard Barry. Copyright (C) 2010-2016 Real Time Engineers Ltd.
Any and all data, files, source code, html content and documentation included in the FreeRTOSTM distribution or available on this site are the exclusive property of Real Time Engineers Ltd..
See the files license.txt (included in the distribution) and this copyright notice for more information. FreeRTOSTM and FreeRTOS.orgTM are trade marks of Real Time Engineers Ltd.