AmpvelisPropulsion & electronics
Home / Component library
Buying guide / Applications

Keep firmware compatibility in the hardware purchase

A board can be physically unchanged while the supported firmware or peripheral behavior changes. The purchase record should identify the intended software environment.

The purchasing decision

Request the supported target and documentation for the exact board revision. Avoid an unqualified latest-version instruction when a fleet depends on a validated configuration. Put update approval and replacement substitution in the change process.

Keep these records

  1. Supported board target.
  2. Validated configuration reference.
  3. Update and substitution approval.

Give each record an owner and a revision or date. If a supplier proposes a different part or test condition, record it as an exception for review before treating the quotation as equivalent.

Turn the review into a sourcing request

Start with the linked component checklist, add the actual platform and part identity, and state quantity, destination and timing. List unresolved requirements explicitly so the first discussion can focus on those gaps.

Flight-controller hardware — requirement checklist

Related technical interface

GNSS and RTK receiver hardware — Datumelis