| 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 | 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 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | bringing up EPICS 3.14.8.2 on VxWorks for a Xilinx VirtexII FPGA with a PPC405 core |
| From: | "Jeff Hill" <[email protected]> |
| To: | "'Chris Timossi'" <[email protected]> |
| Cc: | "'TECHTALK'" <[email protected]> |
| Date: | Tue, 30 May 2006 14:58:51 -0600 |
Hello Chris, Referring to Mantis 259: The first question to ask is what might be different between this and a more conventional PPC. Is it a site specific vxWorks BSP? It says "Exception current instruction address". Do we know what type of exception it is (this presumably can be decoded from the machine status register value)? Could it be a floating point exception? Are the floating point registers saved by ISR that use floating point? Does this happen only if CA clients are connected? You might also try the following: O Use the "i" command to see if any of the TCBs (task control blocks) are corrupted and or if any other threads are suspended (in a failed state). O Use the memShow command to detect corrupted pool. Jeff __________________________________________________________ Jeffrey O. Hill Mail [email protected] LANL MS H820 Voice 505 665 1831 Los Alamos NM 87545 USA Fax 505 665 5107