EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  <20032004  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  <20032004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: National Instruments VME-MXI-1 modules vs. modern VME CPU modules
From: Eric Norum <[email protected]>
To: [email protected]
Date: Fri, 14 Nov 2003 10:52:45 -0600
National Instruments VME-MXI-1 modules require that the VME A00-A31, AM0-AM5 and LWORD* bus lines remain stable until DS[AB]* have gone inactive. Unfortunately the VME specification has never guaranteed this. The specification allows address pipelining (a.k.a. "address rot") to change the state of these lines as soon as DTACK* has been asserted.

The APS has a rather large number of these modules. The flaw in the VME-MXI-1 has not caused problems because the modules have been used only with MVME167 CPU modules which do not perform address pipelining. We now want to upgrade some of these MVME167 IOCs to more modern CPU modules, but we've run into a problem. CPU modules with a UNIVERSE-II VME interface chip (all Motorola 2100, 5100 and 5500 series) do perform address pipelining which results in erratic data transfer from VME-MXI-1 modules. My guess is that it is likely that any modern CPU is going to cause the same problem.

We looked into fixing the problem by replacing some chips on the VME-MXI-1 but it appears that more than just minor surgery would be required.
--
Eric Norum                                 [email protected]
Advanced Photon Source                     Phone: (630) 252-4793
Argonne National Laboratory


Replies:
Re: National Instruments VME-MXI-1 modules vs. modern VME CPU modules Kazuro FURUKAWA
Re: National Instruments VME-MXI-1 modules vs. modern VME CPU modules Till Straumann

Navigate by Date:
Prev: Help about building a example under cygwin guobao shen
Next: EPICS periodic scan and sysClkRateSet() Steven Hartman
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  <20032004  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: Help about building a example under cygwin Eric Norum
Next: Re: National Instruments VME-MXI-1 modules vs. modern VME CPU modules Kazuro FURUKAWA
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  <20032004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·