Difference between revisions of "OpenBMC/StepsToIPL"

From RCS Wiki
Jump to navigation Jump to search
(Initial page)
 
m (Most of the bmc scripts use '-' instead of '_', so for searching for the incorrect script name can result in confusion.)
Line 5: Line 5:
 
== poweron ==
 
== poweron ==
 
# Disable OCC
 
# Disable OCC
## occ_active.sh disable
+
## occ-active.sh disable
 
# Bind FSI Driver (once per BMC boot)
 
# Bind FSI Driver (once per BMC boot)
 
# ScanFSI
 
# ScanFSI
Line 13: Line 13:
 
# Fan daemon is started
 
# Fan daemon is started
 
# AVSBus stuff
 
# AVSBus stuff
## avsbus_workaround.sh
+
## avsbus-workaround.sh
## avsbus_disable.sh
+
## avsbus-disable.sh
## vrm_control.sh
+
## vrm-control.sh
## avsbus_enable.sh
+
## avsbus-enable.sh
 
# startHost
 
# startHost
 
## openpower-proc-control's startHost procedure is run
 
## openpower-proc-control's startHost procedure is run
 
# Wait for IPL
 
# Wait for IPL
 
# Enable OCC
 
# Enable OCC
## occ_active.sh watchdog
+
## occ-active.sh watchdog

Revision as of 15:15, 4 August 2019

The BMC takes a number of steps to start the IPL process and boot the main CPU. Due to OpenBMC's complex boot procedure that relies on a tangled mess of systemd targets and dbus, the exact steps taken to boot and their ordering is not always clear. This page attempts to clearly document them.

poweron

  1. Disable OCC
    1. occ-active.sh disable
  2. Bind FSI Driver (once per BMC boot)
  3. ScanFSI
    1. openpower-proc-control's ScanFSI procedure is run
  4. CFAMOverride
    1. openpower-proc-control's CFAMOverride procedure is run
  5. Fan daemon is started
  6. AVSBus stuff
    1. avsbus-workaround.sh
    2. avsbus-disable.sh
    3. vrm-control.sh
    4. avsbus-enable.sh
  7. startHost
    1. openpower-proc-control's startHost procedure is run
  8. Wait for IPL
  9. Enable OCC
    1. occ-active.sh watchdog