Each time that the Coprocessor is reset, and the reset is not caused by a fault or tamper event, the Coprocessor runs through "Miniboot", its power-on self-test (POST), code-loading, and status routines. During this process the Coprocessor attempts to coordinate with a host-system device driver. Coprocessor resets can occur because of power-on, a reset command sent from the device driver, or because of Coprocessor internal activity such as completion of code updates. The Coprocessor can also reset if the Coprocessor's fault or tamper detection circuitry reset the Coprocessor. The Coprocessor device driver monitors the status of its communication with the Coprocessor and the Coprocessor hardware status registers.

Programs such as the Coprocessor Load Utility (CLU), and the host parts of the CCA and PKCS #11 Support Program can receive unusual status in the form of a 4-byte return code from the device driver. There are a very large number of possible 4-byte codes, all of which are of the form 8xxxxxxx (in hexadecimal). The most likely codes that may be encountered are described in the following table.