1. Purpose of the gate
Beta release is the first time the software stack leaves the building on silicon. Early-access customers have had the SDK and toolchain since Early-access SDK, but only on models or on boards they could not yet use in earnest. With the beta, sampling customers receive firmware, drivers, the board support package and the SDK that have run on the actual part, so they can start porting their own software, evaluating performance and finding the issues that only appear in their systems.
The gate tests three things. The beta release itself must be built by the pipeline, signed with development keys and tagged, so that every customer report can be traced to an exact build. The release notes and known issues list must be published to beta customers, honestly stating what does not yet work. And the hardware-in-the-loop rigs must be running the regression on silicon, because from here every change has to be checked on the part customers are using.
In the SoC lifecycle, Engineering samples waits for this gate: samples ship with beta software and an SDK, and without them customers cannot evaluate the chip. A beta that slips holds back the whole sampling program, while a beta shipped too early wastes customer effort on known problems and damages confidence in the product. The review exists to strike that balance deliberately.
10 more sections for registered members.