Hi,
I have been running vxWorks 6.0 and EPICS R3.14.7 for a couple of weeks
now. Of course, EPICS is running in vxWorks 6.0 kernel space. I have
not experimented with the Real-Time Process (RTP) space yet.
There were very few changes to make; mainly due to the new GCC compiler.
I also had to modify "$(EPICS_BASE)/configure/*" to build the new
architecture/vxWorks combination.
I have encountered differences in the shell environment that the startup
scripts executes in -- versus the target shell. This is a big
difference from the way things worked in vxWorks 5.5.1.
Bad News: The mv2100 BSP is currently not supported in vxWorks 6.0.
WRS says we will have to port that one on our own.
Good News: EPICS runs great so far.
Has anyone else tried vxWorks 6.0?
My setup:
Host: Linux (Now a supported WRS platform)
Target BSP: mv5100 (not modified except for EPICS recommended
INCLUDES_XXX_YYY)
Target hardware: MVME5110
EPICS: Release 3.14.7
Thanks,
Ernest L. Williams Jr.
SNS Control Systems Group
ORNL
- Navigate by Date:
- Prev:
Re: Strict aliasing Eric Norum
- Next:
Standalone Sequencer Program - Inactive Console Steven . Banks
- 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:
New module versions Tim Mooney
- Next:
Standalone Sequencer Program - Inactive Console Steven . Banks
- 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
|