How havenoverflow/cr50 works
This repository is Cr50 security-chip firmware, forked to include custom firmware and reverse-engineered support for other Google security chips. The product spans ROM startup, a signed-image loader, firmware runtime, cryptography, TPM services, and board-level interfaces. The sampled loader and ROM sources establish their image-verification and setup dependencies; the index also identifies major firmware subsystems, but does not expose their runtime wiring. Consequently, several important capabilities are shown as components without speculative call edges.
Main entry points: loader/main.c Image loader · signed_header.h Signed headers · rom/main.c ROM startup · common/main.c Firmware startup
Components 17
Boot and images
- ROM startup
chip/haven/rom/main.c - Image loader
chip/haven/loader/main.c - Signed headers
chip/haven/signed_header.h
Firmware runtime
- Firmware startup
common/main.c - Boot parameters
boot_param/boot_param.c
Security services
- Hardware crypto
board/smiko/dcrypto - TPM 2 services
board/smiko/tpm2 - TPM NVM
board/smiko/tpm_nvmem_ops.c - U2F support
board/smiko/dcrypto/u2f.c - RMA authorization
common/rma_auth.c - Pinweaver integration
board/smiko/pinweaver_tpm_imports.c
Board interfaces
- Smiko board
board/smiko/board.c - SPI controller
chip/smiko/spi_controller.c - I2C controller
common/i2c_controller.c - USB SPI bridge
board/smiko/usb_spi.c - USB I2C bridge
board/smiko/usb_i2c.c
Other components
- Chip startup
Connections 4
- ROM startup → Signed headers: reads header
chip/haven/rom/main.c - Image loader → Signed headers: verifies image
chip/haven/loader/main.c - Image loader → Chip startup: starts from
- Firmware startup → Chip startup: initializes firmware