Hi all,
Sorry if this is more vxWorks related, but I'm in a pinch and
know some of you might have been here before. I've been part of
a new spectrograph upgrade in our lab for the last couple years.
Now it's moving to operations, and I may no longer have the
luxury of a network bootbar. (Sometimes the science requirements
seem to miss the needs of a lowly software engineer. =) )
I have an MVME6100 with Epics 3.14.12.2 running vxWorks 5.5.
Sometimes when testing changes to a new vxworks kernel or just
an update to a new epics module, my shell stops hard, and Ctrl-x
doesn't work. Power cycling is my best friend in that case, but
is it my only option?
Can a modified reboot handler help with any of these occurrences?
Thanks for any insight.
-Matt
- Replies:
- Re: VxWorks VME Ctrl-X vs. Power Cycle Andrew Johnson
- Re: VxWorks VME Ctrl-X vs. Power Cycle Hartman, Steven M.
- Navigate by Date:
- Prev:
RE: using C# dll's Roehrig, Christian
- Next:
PicoScope support? Brown, Garth
- 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:
Battery Cycler tom.cobb
- Next:
Re: VxWorks VME Ctrl-X vs. Power Cycle Andrew Johnson
- 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
|