1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 <2022> 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 <2022> 2023 2024 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Interrupt problem. |
From: | "Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov> |
To: | Francisco Ramos <framoslandaeta at gmail.com> |
Cc: | EPICS tech-talk <tech-talk at aps.anl.gov> |
Date: | Tue, 25 Jan 2022 00:26:17 +0000 |
Hi Francisco,
On Jan 24, 2022, at 2:53 PM, Francisco Ramos via Tech-talk <tech-talk at aps.anl.gov> wrote:
The error “spurious interrupt: 32” would imply to me that the CPU was seeing an interrupt on vector 32 but that it doesn’t have an interrupt service routine associated with that vector number. Does your macro BC635VEC expand out to 32? Has your bc635IntEnable()
routine actually been run at the point when you are seeing the error message?
I assume you have already applied the patch to the epicsEvent API found in the GitHub PR #206 which is essential to be able to call
epicsEventSignal() from an ISR on RTEMS-5.1. I just merged that PR into the 7.0 branch earlier today.
HTH,
- Andrew
--
Complexity comes for free, simplicity you have to work for.
|