Paul,
Paul Sichta wrote:
>
> We've just built EPICS 3.13.2 under Solaris 8, without errors. Unlike out
> R3.13.beta11 release, we do not see the vxWorks and vxWorks.sym files in the
> ~base/bin/mv177 directory. makeBaseApp.pl does not populate our
> <top>/iocBoot/iocxxx directory with the vxWorks and vxWorks.sym either
> (presumably because they are not in base). ca_test works fine as well as an
> example application from the new build.
Ever since we realized that the object files installed in the bin
directory don't actually depend on the BSP (only on the CPU type, so mv162
and mv167 binaries are identical) we've stopped installing the boot files
into base and the application directories. Here at APS we use many mv162
boards but now tell EPICS that they're mv167s, the only difference being
the boot file (an mv162lc is a different CPU though).
> Is it now S.O.P. to boot operational IOC's from the vxWorks files that are
> in the ~vw/tornado101 subdirectory, and not those under <top> ? Did we
> forget a 'switch' in the build?
It is T.R.O.P (The Recommended Operating Practice), although you have to
manually ensure that the IOC is booting from the same version of Tornado
(1.0.1, 2.0 etc.) that the software was built for (usually not a problem).
- Andrew
--
Every great idea appears crazy to start with.
- Replies:
- Re: where to load vxWorks.sym Ralph Lange
- References:
- where to load vxWorks.sym Paul Sichta
- Navigate by Date:
- Prev:
Re: Callbacks and the PCAS question. Brian Tieman
- Next:
Re: where to load vxWorks.sym Ralph Lange
- 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:
where to load vxWorks.sym Paul Sichta
- Next:
Re: where to load vxWorks.sym Ralph Lange
- 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
|