| 01 | Logic capacity | Look for the device’s logic-cell or LUT count and confirm how the supplier defines those figures. | Logic-cell counts are not directly comparable across architectures; benchmark the intended design. |
| 02 | Embedded memory and DSP | Check block-memory capacity, supported memory modes, and the number and capabilities of DSP blocks in the exact part. | These resources can reduce logic use in buffering, signal processing, and arithmetic-heavy designs. |
| 03 | I/O and interface support | Review the datasheet for I/O standards, bank voltage limits, pin count, and any supported high-speed interface blocks. | Board compatibility depends on voltage, pin assignment, signal integrity, and interface requirements. |
| 04 | Configuration and startup | Determine whether configuration is SRAM-based, flash-based, or supported through an external configuration memory, and check startup requirements. | Configuration architecture affects boot behavior, board design, and the need for external components. |
| 05 | Development tools | Confirm supported operating systems, synthesis and implementation flows, simulation options, licensing terms, and tool update policy. | Tool availability and workflow maturity influence development time and long-term maintenance. |
| 06 | Package and thermal limits | Compare package options, pinout, power requirements, and the specified operating-temperature range for the selected device. | A suitable die may still be unsuitable if the package, thermal design, or temperature rating does not fit the product. |
| 07 | Documentation and design support | Request current datasheets, reference designs, application notes, errata, and a defined channel for technical support. | Complete, current documentation helps teams validate designs and resolve implementation issues. |
| 08 | Qualification and compliance | Verify the exact part’s applicable quality, environmental, and industry qualification documents rather than relying on family-level descriptions. | Qualification requirements differ by end market and may apply only to specific devices or production sites. |
| 09 | Supply continuity | Ask for product status, lifecycle-change notification practices, authorized distribution channels, and written lead-time information. | Availability and lifecycle planning are important for production schedules and long-lived equipment. |
| 10 | Samples and production validation | Evaluate the target design on the exact device and package; confirm test coverage, programming flow, and production traceability. | Prototype success alone does not establish production readiness or compatibility across device revisions. |