Subject: |
FW: VME Bus Error handling on MVME3100 and 6100 boards |
From: |
"Thompson, David H." <[email protected]> |
To: |
[email protected] |
Date: |
Thu, 17 Aug 2006 11:47:52 -0400 |
Our V124s don't have to be smoked to cause a bus error.
I don't have to be able to debug it to know what is going on.
I do want to know that something happened rather than passing 0xffff up
into the control loop.
========== Response from Motorola below ===============================
Motorola has received the fiollowing response from an engineer that was
involved with the TEMPE and from Tundra:
Tundra states that "the error handling with respect to a BERR
termination as a VMEbus master works as described in the Users Manual.
Tundra has no plans of changing this." If the customer doesn't feel
that signaling via an interrupt is insufficient then we have no
recourse. Please note that both Mac and Tundra agree that a failed read
of a valid VME address would likely occur only as a result of a
catastrophic system failure, i.e. the target board smoked. The
probability that a failed read, when (or if) retried would return data
is essentially zero.
========================================================================
Not sure, what to make out of that initial response?
- Navigate by Date:
- Prev:
RE: VME Bus Error handling on MVME3100 and 6100 boards Thompson, David H.
- Next:
EPICS Web Mirror How-To Ralph Lange
- 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
- Navigate by Thread:
- Prev:
Re: VME Bus Error handling on MVME3100 and 6100 boards Andrew Johnson
- Next:
Porting EPICS to NetBSD David Dudley
- 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
|