1. Purpose of the gate
Software bring-up complete marks the point at which the software stack stops being an experiment on new silicon and becomes something other teams can build on. Since First silicon boot, the bring-up team has moved from the boot ROM handing over to the first loader, through firmware on the internal cores, to drivers and a full operating system on the reference board. Along the way every failure has had to be sorted: is it a silicon bug, a board fault, a model that did not match the silicon, or a software defect that the models simply never exercised?
The gate asks whether that sorting is finished well enough to move on. Its criteria are an operating system boot on every supported reference board, a silicon bring-up report written and reviewed, an errata list that names a software workaround for each known silicon issue, and a model-to-silicon correlation in which the differences are explained. A pass means validation can run real regressions on silicon and the beta release can be assembled from software that has actually run on the part.
Several hardware gates depend on this one. In the SoC lifecycle, Silicon validated waits for it, because most of the chip can only be validated with firmware and drivers running. In the AI accelerator lifecycle, Software stack running on silicon waits for it, since the runtime and compiler cannot run workloads until the firmware and drivers do. In the FPGA lifecycle the review is held together with Hardware and software integrated, because configuration, boot, firmware and the operating system come up with the board as one piece of work.
10 more sections for registered members.