← Back to roadmap
Stub

OTP / eFuse

Priority 0 - Memory System

$0 / $6,7500% funded
Fund$6,750
$0 / $6,750 - 0%
As a firmware developer, I want vemu to finish its OTP / eFuse model, so that I can depend on secure provisioning, IDs for production firmware, not just the common path.

Why it matters

Secure provisioning, IDs

Summary

Write-once locked fuses

Scope of work

Currently a register-only stub. Replace it with a working model of OTP / eFuse that actually exhibits the hardware behavior. What it is: Write-once locked fuses. Why it matters: Secure provisioning, IDs.

Current state

Status: Stub only (registers, no behavior). Notes / evidence: Writes freely; no lock/write-once.

Blocked by 1

Fund these first - this work can't be completed until they ship.

  • Done
Unblocks 2

Funding this also clears the way for the work below.

Activity log

  1. Feature defined and added to the roadmap

  2. Funding goal set to $6,750

  3. Implementation status: Stub