Argonne National Laboratory

Experimental Physics and
Industrial Control System

<19941995  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  Index <19941995  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 
<== Date ==> <== Thread ==>

Subject: Re: DSP
From: jbk@aps.anl.gov (Jim B. Kowalkowski)
Date: Wed, 15 Jun 94 10:11:36 CDT
>To: anc@fel.duke.edu
>Subject: Re:  DSP
>In-Reply-To: Mail from 'Abhijit Nagchaudhuri <anc@fel.duke.edu>'
>     dated: Wed, 15 Jun 1994 10:25:54 -0400
>Status: R


The Pentek board I have has a C30 (TI) in it.  I think they have a version
with the C40 also.  I haven't done any research on other boards that
use the C30/C40 processors, so I am not promoting this board as being
THE board to use - even though it does look very reasonable and it
was chosen by a group that needs high performance.

I chose to map the Pentek card into A32 on the VME backplane.  The MV167
memory is mapped on the backplane.  I reserved a section of Pentek
memory for interprocess communication and am using a VME interrupt to 
signal the MV167 that the Pentek card need servicing.  I am creating a loader
that runs under vxWorks, in the startup.cmd file the user can invoke the
this loader.  The loader copies the C30 execuable into the Pentek module's
memory in A32 on the VME backplane and signals the Pentek to start executing.

Here is the general scheme:
1) load Pentek memory with program from vxWorks on the MV167

2) initialize a interprocess communication control block
   - the control contains a buffer address for pentek module to deposite
   data when it completes an operation and some flags.

2) start the program executing

3) the  pentek completes an operation
   - copy the results (over VMEbus) to the address in the control block
   - interrupt (VME) the MV167/vxWorks

4) vxWorks interrupt handler alerts record processing (EPICS) that data
   is available.

5) record suppport runs and does things that record support normally does -
   set alarms, trigger monitors, forward link, etc..


This is a fairly simple system, all transfers are done over the VME A32
address space and controlled by a small control block in the Pentek module's
memory.

Jim K.


Navigate by Date:
Prev: Re: DSP Abhijit Nagchaudhuri
Next: Re: DSP edward moler
Index: <19941995  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 
Navigate by Thread:
Prev: Re: DSP Abhijit Nagchaudhuri
Next: Re: DSP edward moler
Index: <19941995  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 
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 ·