Overview of ChorusOS Reboot Process

The ChorusOS operating system supports three system reboot scenarios:

• Cold reboot

• Hot reboot

• Boot of the system image loaded by the ChorusOS bootMonitor (equivalent to booting a new system image that is loaded by the one that is running).

A system reboot can be initiated by either the operating system sysShutdown() call, by the system failure recovery procedure, or by some special system applications such as bootMonitor.

All system reboot scenarios will use the sysReboot() microkernel call. sysReboot() calls the emergency stop services of all registered drivers and then transfers control to a board-specific reboot program.

When performing a cold reboot, the reboot program will reset the hardware and the system lifecycle will be restarted from the power-up initialization program.

In the case of a hot reboot, the system boots from the system image, originally deployed by the cold reboot (that is, it boots from itself). For further information on this, see the Chapter 5, The ChorusOS Reboot Program.

Finally, if one ChorusOS system (that is, bootMonitor) boots another ChorusOS system (that is, the system image loaded by bootMonitor) then the new system image is installed at the required address and the reboot program will jump to it. For further information on this, see Chapter 5, The ChorusOS Reboot Program.

For more information on booting a ChorusOS operating system, see Chapter 4, The ChorusOS Boot Program.