Biometrics include architecture

flowchart LR
  Host[niseCore sensor and PAL] --> Core[vcsfw_v4 core protocol]
  Host --> Priv[private and parameter extensions]
  Host --> Fido[FIDO operations]
  Host --> Test[module-test commands]
  Host --> Tune[clock / WOVAR tuning]
  Host --> Identity[USB and flexible device IDs]
  Core --> Wire[Packed command / reply ABI]
  Priv --> Wire
  Fido --> Wire
  Test --> Wire
  Tune --> Wire
  Wire --> Firmware[Fingerprint sensor firmware]
  Identity -. selects device behavior .-> Host

Boundaries

ComponentSourceArchitectural responsibility
Core protocolvcsfw_v4.hDefines firmware command IDs and primary packed command/reply structures.
Private/parameter extensionsvcsfw_v4priv.hDefines private parameters for capture, finger detect, calibration, WOF/WOVAR, clocks and sensor-specific behavior.
FIDO operationsvcsfw_v4fido.hDefines firmware-side FIDO operation IDs and payload contracts.
Module testvcsfw_v4moduletest.hDefines module-test command contracts.
Clock/tuningvcsfw_v4clocktune.h and vcsfw_v4wovar.hDefines clock tuning and wake-on-variance controls.
VIP/extended tagsvcsfw_v4vip.h and vcsfw_extag.hDefines additional command/tag namespaces.
Device identityusbid.h and flexid.hMaps hardware/device identities used by host components.
Whitney commandswhitney_commands.hAdds Whitney-family command definitions.

Change-safety rules

  • Follow calls and data across component boundaries; a changed header or customer property can affect multiple binaries.
  • Keep source revision and branch explicit because configured branches differ substantially.
  • Validate both the component and its direct consumers.
  • Treat optional/customer-selected components as conditional, not universally deployed.