Home/Glossary/ASIC Verification and Testing
Semiconductor knowledge

ASIC Verification and Testing

Complementary activities used to assess a chip. Design verification checks whether a design meets its specification; manufacturing test screens fabricated devices for targeted defects, while characterization measures actual silicon behavior.

← All glossary termsTechnical guide · 5 min read
In this article

Complementary activities used to assess a chip. Design verification checks whether a design meets its specification; manufacturing test screens fabricated devices for targeted defects, while characterization measures actual silicon behavior.

An iterative ASIC development flow
Reviews and feedback connect the stages. This conceptual flow is not a fixed project schedule.

Two different questions

Design verification asks whether the intended design behaves correctly against its requirements. Manufacturing test asks whether a fabricated device has defects or falls outside the defined test criteria. Both are essential, but one does not replace the other. A logically incorrect design can be manufactured consistently, and a correctly verified design can produce a defective physical device. Keep the objectives and evidence separate while coordinating their requirements. Testability features often need to be designed early, and verification must cover the behavior introduced by those features.

Verification follows the specification

Create a plan that traces important requirements to checks. Simulation, assertions, formal methods and system-level platforms can address different questions. Include corner cases, invalid inputs, reset, backpressure and error recovery. Coverage metrics help show what has been exercised or analyzed, but their meaning depends on the plan and implementation. A high percentage is not a universal proof of correctness. Review uncovered behavior and exclusions explicitly, and make sure the tests are checking expected results rather than merely generating activity.

Manufacturing test needs access

Scan structures, memory self-test and other design-for-test techniques improve the ability to control and observe internal circuitry. Their suitability depends on the design and fault models being targeted. Test patterns, hardware and production limits require development and validation. An at-speed test addresses different conditions from a slow functional check. Plan package pins, power and clock requirements for test mode alongside normal operation. Security-sensitive devices also need a deliberate policy for controlling test and debug access throughout their lifecycle.

Use failures as information

When a test fails, preserve the configuration, revision and conditions needed to reproduce it. Distinguish a design issue from a testbench defect, incorrect limit, setup problem or manufacturing fault. During silicon bring-up, compare behavior with pre-silicon expectations using consistent definitions. Production data can expose patterns that guide yield improvement and failure analysis. The value of verification and test comes from trustworthy evidence and actionable diagnosis, not simply the number of tests run or the presence of a test feature in the block diagram.

Questions about verification and test

Does full code coverage prove the ASIC is correct?

No. It shows activity against a particular metric. Requirement coverage, meaningful checks, assumptions and the quality of the test plan still matter.

Can production testing find every design bug?

No. Manufacturing tests target specified defects and limits. Design verification and system validation address broader functional behavior that production screening may not exercise.

Requirements that can be checked

Turn each important behavior into a requirement with an observable result. Describe valid inputs, invalid inputs, ordering rules, throughput expectations and the response to interrupted transactions. Identify which clocks and resets are involved. A good review asks whether another engineer could write an independent test from the description. Where the answer is unclear, improve the requirement before adding more implementation detail. Keep assumptions about the surrounding system visible, including how long an interface can stall and whether input data can arrive while a block is unavailable. These details determine whether the implementation and its test environment are solving the same problem.

Verification across normal and unusual operation

Check ordinary workloads alongside stressful combinations of events. Reset during activity, a full queue, simultaneous requests and an error response can expose behavior that an ideal sequence misses. Use appropriate simulation, assertions or formal methods for the properties being examined. Preserve reproducible inputs and expected results. If a check is excluded, record why and who reviewed the decision. Coverage helps organize evidence, but its interpretation depends on what the tests actually check. A regression that executes many cycles without observing meaningful outcomes can provide less confidence than a smaller set of well-targeted checks tied to requirements.

Implementation handover

The source design needs constraints, technology assumptions and integration context before a receiving team can use it reliably. Include the intended operating modes, clock relationships, IP versions and any known limitations. Check that source files, models and reports describe the same configuration. Define how changes are communicated while implementation is in progress. When physical results challenge an assumption, route the finding back to the responsible architecture or logic owner. A controlled handover keeps the project from optimizing an obsolete version or interpreting an undocumented exception as an intentional requirement.

Evidence for the next decision

Separate predicted results from measured behavior and state the conditions behind both. An early synthesis estimate can support architecture exploration, but it is not equivalent to a final implemented result. A prototype can support software integration without proving final ASIC timing. Before a release, identify the evidence required for the particular stage and list unresolved issues with owners. Preserve the approved revision and enough context to reproduce the relevant checks. This makes later debugging, engineering changes and product maintenance more efficient than relying on a single successful run whose inputs are no longer clear.

Primary reference for further reading

A practical cross-discipline review

Before committing the next stage, bring the design, verification and product-engineering owners together around the same revision. Confirm the assumptions that pass between them: operating modes, interfaces, test access and the evidence expected at release. List unresolved issues with a responsible owner and a concrete way to close them. An open question is easier to manage when its consequence is understood than when it is hidden inside a general progress estimate. Preserve the decision record so a later change can be evaluated against the original reasoning. This review is useful even for a narrow specialist task, because the surrounding product still determines whether the delivered result is usable.

Include the receiving team's acceptance question in the review: what must be demonstrated before this result can be used safely in the next engineering stage? Agree how that demonstration will be recorded and how a subsequent change triggers a focused reassessment of the affected evidence.

Explore the related Avnet offering or discuss your project requirements.

Let's talk about your next project.

Explore design, technology enablement and manufacturing with Avnet ASIC Solutions.

Contact our team →