On Mar 21, 2014, at 3:21 PM, Matt Rippa <[email protected]> wrote:
> Can a modified reboot handler help with any of these occurrences?
With VxWorks, you can definitely get yourself into enough trouble that ^X or reboot() won't be enough. A SYSRESET or perhaps even a power cycle is needed. If you just have a terminal shell, you are out of luck. SNS built an option for sending a reset through the timing system to the timing receiver board which issues a SYSRESET on the backplane (although this is almost never used). Some VME crates have their own network interface which can be used to send a reset or power cycle. A network power cycler is another option. If you don't have something like that, and the crate is far away, you best option is careful coding.
--
Steven Hartman
[email protected]
- Replies:
- Re: VxWorks VME Ctrl-X vs. Power Cycle Matt Rippa
- References:
- VxWorks VME Ctrl-X vs. Power Cycle Matt Rippa
- Navigate by Date:
- Prev:
Re: VxWorks VME Ctrl-X vs. Power Cycle Andrew Johnson
- Next:
Re: VxWorks VME Ctrl-X vs. Power Cycle Maren Purves
- 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:
RE: VxWorks VME Ctrl-X vs. Power Cycle Mark Rivers
- Next:
Re: VxWorks VME Ctrl-X vs. Power Cycle Matt Rippa
- 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
| 
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·