Skip to question
asic.fyi
DesignVerificationSystemVerilogFirmwareArchitectureInterviews
asic.fyi/Interview questions/Combine Pre-Silicon Checks with FPGA Prototype Validation

Hardware interview practice

Combine Pre-Silicon Checks with FPGA Prototype Validation

MediumDesign VerificationSystemVerilog

An ASIC-oriented packet engine will also run on an FPGA prototype, where internal observation is limited and FPGA memories, clocks, and resets differ from the final ASIC implementation. Which verification strategy is strongest?

Try it in the question bankReason first. Then compare.

Keep this exact question selected while you check your answer and review the full solution.

Practice this question →
Choose one

Answer choices

  1. A. Probe every internal signal continuously on the FPGA, eliminating the need for assertions, scoreboards, trigger planning, or reproducible test seeds.
  2. B. Use lint, simulation, assertions, formal checks, scoreboards, and coverage before mapping; then run reproducible hardware traffic, clock/reset stress, and error cases with selected ILA probes, while treating FPGA-specific initialization, memories, clocks, and timing as prototype differences rather than ASIC signoff.
  3. C. Verify only the FPGA vendor wrappers because synthesizable user RTL behaves identically in every clock, reset, and unknown-state condition.
  4. D. Skip simulation once the RTL fits in the FPGA because passing long random traffic on hardware proves all internal corner cases and ASIC timing modes.
Continue practicing

Related questions

Design VerificationIdentify Simulation Defaults for Variables and Nets→Design VerificationDebug an X after reset release→UVM ComponentsBuild a reset-responsive nonblocking driver→
asic.fyi · Learn silicon end to end.info@asic.fyi