Init Attach

During the init attach phase, DR diagnoses and configures the selected board, preparing it and its devices for attachment to the operating environment. During this phase, DR performs the following tasks:

• Adds the board to the board list of the target domain in the domain_config(4) file on the SSP.

• Runs hpost -H on the board to configure it. hpost(1M) isolates the board on the Sun Enterprise 10000 system centerplane by placing it into a single-board hardware domain (refer to the hpost(1M) man page).

  ---

  Note -

  Depending on the presence on memory and I/O devices on the board, the hpost testing level could be different for subsequent attach operations.

  ---

• Runs obp_helper -H which loads download_helper to the board, and takes the processors on the board out of reset mode, allowing them to spin in download_helper.

• Reconfigures the centerplane and board domain mask registers, placing the board in the target hardware domain.

DR displays the output of these hpost(1M) and obp_helper(1M) operations, including the steps that succeeded and those that caused exceptions.

If hpost(1M) and obp_helper(1M) succeed, the operating system is notified and requests OBP to probe the board. The operating environment then scans the OBP device tree and adds the devices to its configuration, but the drivers are not loaded.

After the init attach phase is completed, the OBP board configuration can be displayed to confirm which devices are present on the board. You can then enter the complete attach phase, or you can abort the operation.

If you abort the operation, DR removes the board configuration from the operating environment data structures and removes the board from the domain_config(4) file, leaving the board in a state where it is not assigned to any domain. The board can then be removed from the system by using hot swap, left in the system unattached, or attached at a later time.