Meaning
A permanent array of microscopic on-chip fuses stores permanent hardware version data to control system boot behaviour. Hardware designers use efuse revision bits to lock down security states and register the precise revision of the silicon. Once blown, these electrical connections are severed forever, establishing an unalterable history of the chip configuration.
This physical state protects the connected system against security downgrades and unauthorised firmware rollbacks. It acts as an unbypassable gatekeeper that defines the absolute trust boundary of the platform.
Hardware Configuration
Electronic structures utilize electromigration to transition individual fuse elements from a low-resistance state to a high-resistance state. The system firmware reads the efuse revision bits during the early boot phase to determine the hardware capability of the system-on-chip. Because the transition is irreversible, there is no software exploit that can restore a blown fuse to its original factory state.
Security Policy
Secure bootloaders compare the compiled firmware version against the hardware limits. The boot sequence terminates immediately if the software version does not match the threshold defined by the efuse revision bits.
Factory Programming
Production automated test systems apply a precise overvoltage to program these values. During this test phase, the programmer blows the efuse revision bits according to the finalized hardware errata and product type. The tester then verifies the change by reading the internal register over a dedicated testing protocol.