# Component selection and firmware data

> Use Probe's cited part data for component selection and firmware: parametric search, register maps and where a part is already used.

_Source: E-Sharp (esharp.se) · Probe guide_


Probe's datasheet corpus isn't only for review — it's a cited knowledge source you can use when you choose components and write firmware.

## Parametric search

Search for parts of a certain type that meet numeric conditions (e.g. current, voltage, tolerance). Each hit is served with the value it met, its source and corroboration, plus **how many boards already use the part** — all cited from datasheets. Units are normalised so the conditions are comparable.

## Zero hits means "nothing stored"

An empty search means nothing is *stored* for those conditions, not that no parts exist. The corpus fills per part on ingested boards — see [the datasheet corpus lifecycle](/en/probe/support/datasheet-corpus-lifecycle).

## Prefer a part that's already used

Before you choose a new part you can see where a part is already used across the fleet (where-used). Preferring a part E-Sharp already runs lowers risk and simplifies procurement.

## Register maps for firmware

For a part with a register interface, the register map gives address, reset value and bitfields (bit range → name → meaning → R/W), read from the datasheet's register tables and page-cited. It answers "what address does register X have" and "how do I interpret the bytes I read over I²C/SPI".

---

Related: [ask the board](/en/probe/support/ask-the-board).

*Probe is E-Sharp's design-review engine. Part data is cited from datasheets — cite or abstain.*
