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: | Re: VME Bus Error handling on MVME3100 and 6100 boards |
From: | Andrew Johnson <[email protected]> |
To: | Kate Feng <[email protected]> |
Cc: | Till Straumann <[email protected]>, EPICS tech-talk <[email protected]> |
Date: | Thu, 24 Aug 2006 11:11:37 -0500 |
Discovery deos not have the necessary capability or connections to the MCP. I was told that
on the boards which use a Discovery system controller, the MCP signal is connected to a
pull-up and therefore not used as it is on other boards. That's the design on the
MVME5500 and MVME6100 boards. I do not see it as a big problem for the
MVME5500 board because ......
Till Straumann wrote :
(currently, a PCI error such as target abort is routed to the one and only EE interrupt of the powerpc).
The MCP, if available, is routed to the EE interrupt as well.
For the MVME6100, I am more concerned with the
"making use of the dud all-1's read data in the process"
that Andrew mentioned earlier. I do'nt seem to get the answer from the
http://www.aps.anl.gov/epics/tech-talk/2006/msg00892.php, which was posted by Till.
Is it in the "vmeTsi148ClearVMEBusErrors(&erraddr);" ? How is it programmed?
We have one application that could be optimied by the PCI bandwidth that MVME61000 offers ( 800 MHZ). Also, I am still not sure about the "MBLT" transfer of the VME backplane, whih was posted at http://www.aps.anl.gov/epics/tech-talk/2006/msg00888.php. I assumed it was limited by the capability of the DMA controller instead of the bus speed because I assume a simple test could be done easily by using two MVME6100s on a VME320 crate. Perhaps Till can verify this ??
Andrew Johnson wrote: > Anyone interested in MicroTCA to replace the now aging VMEbus?
Why do you think VMEbus is aging ? I was researching the VXS bus for a short while and comapred it with the MVME6100 solution for our application. VMEbus does not seem to be aging for me.
- Andrew -- There is considerable overlap between the intelligence of the smartest bears and the dumbest tourists. -- Yosemite National Park Ranger