Stub
Input capture
Priority 2 - Microcontroller & SoC Peripherals / 2.1 Digital I/O & timing
$0 / $8,7500% funded
$0 / $8,750 - 0%
As a device-driver developer, I want vemu to finish its Input capture model, so that I can depend on frequency/pulse measure for production firmware, not just the common path.
Why it matters
Frequency/pulse measure
Summary
Timestamp external edges
Scope of work
Currently a register-only stub. Replace it with a working model of Input capture that actually exhibits the hardware behavior. What it is: Timestamp external edges. Why it matters: Frequency/pulse measure.
Current state
Status: Stub only (registers, no behavior). Notes / evidence: STM32: CCR/CCMR stored, no capture.
Activity log
Feature defined and added to the roadmap
Funding goal set to $8,750
Implementation status: Stub