wolfBoot on the NXP LPC55S69 can now root the device identity in the chip’s SRAM PUF (Physically Unclonable Function). The attestation secret is never stored in flash and never leaves the PUF, which rebuilds it from the silicon on every boot.
Why a PUF
Factory injected keys are seen by the factory, the programmer, and the key database. The public UID is readable by anyone with a debugger. A PUF key comes from physical differences between dies, so nobody ever holds it and flash holds nothing secret.
What Changed
- wolfSSL #11700: wolfCrypt PUF port for 128, 192, and 256-bit keys.
- wolfBoot #787: first boot provisioning and a PUF derived UDS for DICE and PSA attestation.
- wolfBoot #950: PUF, flash, and RNG isolated in the secure world, plus emulator tests and a board guide.
Measured Cost
LPCXpresso55S69 at 96 MHz with ECC-384 and SHA-256:
| Step | Cost |
|---|---|
| First boot provisioning | 163 ms, once |
| UDS recovery on each boot | 64 ms |
| 404-byte attestation token, end to end | 1.54 s |
| Added wolfBoot code size for PUF | +2.2 KB |
The PUF in Action
The device identity (UEID) stays the same across boots and changes only after re-enrollment:
boot 1: 01b57481835d1eacad376f1f5f31c431f3bac16c118c3f5ef8db2ba6fdc0aabe05 boot 2: 01b57481835d1eacad376f1f5f31c431f3bac16c118c3f5ef8db2ba6fdc0aabe05 after re-enroll: 015f476bed263b42c2046263f7c9859d499003f854d54ffca03461b3944013be7d
Copying the full flash to another device is useless. The same image booted in the m33mu emulator fails attestation because its PUF does not match. Setup steps are in the wolfBoot targets guide.
If you have questions about any of the above, please contact us at facts@wolfssl.com or call us at +1 425 245 8247.
Download wolfSSL Now

