EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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

Subject: Re: whether abvisable to use win32 to host EPICS development
From: Andrew Johnson <[email protected]>
To: [email protected]
Date: Thu, 11 Nov 2010 11:30:22 -0500
On Thursday 11 November 2010 09:30:45 çæ wrote:
> My task is to port a LLRF system to EPICS, I use vxWorks5.5.1 and
> EPICS-3.14.8.2, but the CPU board has not been finally determined, probably
> CPCI6200 or CPCI6190. A recommended CPU board is CPCI6200 with high
> performance and a MPC8572 dual core processor,

Does vxWorks 5.5.1 support dual-core processors, I thought the first vxWorks 
release that can make use of SMP is vxWorks 6.7 or 6.8?  I do know that the 
EPICS operating-system-dependent interface software for vxWorks was not 
designed for or tested on SMP systems, so I think that the only way this 
combination might work would be if the second core was turned off or only used 
for non-EPICS code.

> which the crossgcc2.9.6 from
> SNS does not support. So I think I can use win32 as EPICS development
> environment, OPI and server(such as ftp and tftp), tornado2.2.1(supports
> MPC8572) on win32 as the cross compiler. But I am not sure whether it is an
> advisable choice, since I have no experience of developing EPICS
> application on win32, I don't know whether win32 is suitable as EPICS host,
> and what problem may occur frequently. I need advice.

I have recently been helping another user to cross-compile EPICS for vxWorks 
on a Windows system.  He is using the cygwin-x86 target architecture for the 
host build rather than win32-x86 or win32-x86-mingw and has had several 
problems with that combination (related to Cygwin's /cygdrive/... paths), but 
he has finally managed to get this to work.  As a result I would recommend 
that you choose win32-x86 or win32-x86-mingw for your host architecture, but I 
don't foresee any major problems with using Windows like that.

I would recommend that you upgrade your Base version though, 3.14.8.2 came out 
almost 5 years ago in January 2006.  There is no technical reason to stick 
with the same version across all your IOCs, and there could be issues that we 
have fixed since then which might make building the older version hard or even 
impossible on newer compilers.

- Andrew
-- 
If a man is offered a fact which goes against his instincts, he will
scrutinize it closely, and unless the evidence is overwhelming, he will
refuse to believe it.  If, on the other hand, he is offered something
which affords a reason for acting in accordance to his instincts, he
will accept it even on the slightest evidence.  -- Bertrand Russell



References:
whether abvisable to use win32 to host EPICS development 王林

Navigate by Date:
Prev: Unexpected BURT incompatibility after Timing upgrade Michael Abbott
Next: Patch to subArray record Michael Abbott
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: whether abvisable to use win32 to host EPICS development Ernest L. Williams Jr.
Next: Unexpected BURT incompatibility after Timing upgrade Michael Abbott
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 12 Nov 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·