FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [November 2006 Threads] ARM spurious IRQ/FIQPosted 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 peripherals.
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:
MRSR0, CPSR ORRR0, R0, #0xC0 MSRCPSR, R0
to
MRSR0, CPSR ORRR0, R0, #0x80 MSRCPSR, R0 ORRR0, R0, #0x40 MSRCPSR, R0
Glen
RE: ARM spurious IRQ/FIQPosted 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) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|