1.3.1. Create detailed design specifications 1.3.2. Create detailed functional verification or test plan 1.3.3. Select IP that affects system design, especially I/O interfaces 1.3.4. Ensure your board design supports the Intel® FPGA IP Evaluation Mode tethered mode 1.3.5. Review available system development tools
1.4.1. Consider the available device variants 1.4.2. Estimate the required logic, memory, and multiplier density 1.4.3. Consider vertical device migration availability and requirements 1.4.4. Review resource utilization reports of similar designs 1.4.5. Reserve device resources for future development and debugging 1.4.6. Estimate the number of I/O pins that you require 1.4.7. Consider the I/O pins you need to reserve for debugging 1.4.8. Verify that the number of LVDS channels are enough 1.4.9. Verify the number of PLLs and clock routing resources 1.4.10. Determine the device speed grade that you require 1.4.11. Determine the number of images supported for the device
22.214.171.124. Select a configuration scheme 126.96.36.199. Ensure board support the required features: 188.8.131.52. Plan for the Auto-restart after configuration error option 184.108.40.206. Estimating configuration file size 220.127.116.11. Review available on-chip debugging tools 18.104.22.168. Consider the guidelines to plan for debugging tools 22.214.171.124. Use the Early Power Estimator (EPE) to estimate power supplies and cooling solution
126.96.36.199. Design the board for power-up 188.8.131.52. Review the list of required supply voltages and the power supply options 184.108.40.206. Ensure I/O power pin compatibility with I/O standards 220.127.116.11. Ensure correct power pin connections 18.104.22.168. Determine power rail sharing 22.214.171.124. Use power distribution network (PDN) tool to plan for power distribution and decoupling capacitor selection 126.96.36.199. Review the following guidelines for PLL board design
188.8.131.52. Verify configuration pin connections and pull-up or pull-down resistors are correct for your configuration schemes 184.108.40.206. Design configuration TCK pin using the same technique as in designing high-speed signal or system clock 220.127.116.11. Verify the JTAG pins are connected to a stable voltage level if not in use 18.104.22.168. Verify the JTAG pin connections to the download cable header 22.214.171.124. Review the following JTAG pin connections guidelines: 126.96.36.199. Ensure the download cable and JTAG pin voltages are compatible 188.8.131.52. Buffer the JTAG signal according to the following guidelines: 184.108.40.206. Ensure all devices in the chain are connected properly 220.127.116.11. Determine if you need to turn on device-wide output enable
18.104.22.168. Specify the state of unused I/O pins 22.214.171.124. Refer to the Board Design Resource Center 126.96.36.199. Design VREF pins to be noise free 188.8.131.52. Refer to the Board Design Guideline Solution Center 184.108.40.206. Verify I/O termination and impedance matching 220.127.116.11. Perform full board routing simulation using IBIS models 18.104.22.168. Configure board trace models for Intel® Quartus® Prime advanced timing analysis 22.214.171.124. Review your pin connections
126.96.36.199. Determine if your system requires single-ended I/O signaling 188.8.131.52. Determine if your system requires voltage-referenced signaling 184.108.40.206. Determine if your system requires differential signaling 220.127.116.11. Select a suitable signaling type and I/O standard for each I/O pin 18.104.22.168. Verify that all output signals in each I/O bank are intended to drive out at the bank's assigned VCCIO voltage level 22.214.171.124. Verify that all voltage-referenced signals in each I/O bank are intended to use the bank's VREF voltage (for devices that support VREF pins) 126.96.36.199. Check the I/O bank support for LVDS features 188.8.131.52. Verify the usage of the VREF pins that are used as regular I/Os 184.108.40.206. Test pin connections with boundary-scan test 220.127.116.11. Use the UNIPHY IP core for each memory interface, and follow connection guidelines 18.104.22.168. Use dedicated DQ/DQS pins and DQ groups for memory interfaces 22.214.171.124. Make dual-purpose pin settings and check for any restrictions when using these pins as regular I/O 126.96.36.199. Review available device I/O features that can help I/O interfaces 188.8.131.52. Consider OCT features to save board space and verify that the required termination scheme is supported for all pin locations
184.108.40.206. Use the device PLLs for clock management 220.127.116.11. Ensure that you select the correct PLL feedback compensation mode 18.104.22.168. Check that the PLL offers the required number of clock outputs and use dedicated clock output pins 22.214.171.124. Use the clock control block for clock selection and power-down 126.96.36.199. Instantiate PLL with ADC
1.7.1. Use synchronous design practices 1.7.2. Consider the following recommendations to avoid clock signals problems: 1.7.3. Use IP cores with the parameter editor 1.7.4. Review the information on dynamic reconfiguration feature 1.7.5. Consider the Intel's recommended coding styles to achieve optimal synthesis results 1.7.6. Enable the chip-wide reset to clear all registers if required 1.7.7. Use device architecture-specific register control signals 1.7.8. Review recommended reset architecture 1.7.9. Review the synthesis options available in your synthesis tool 1.7.10. Consider resources available for register power-up and control signals 1.7.11. Consider Intel's recommendations for creating design partitions 1.7.12. Perform timing budgeting and resource balancing between partitions 1.7.13. Create a design floorplan for incremental compilation partitions
188.8.131.52. Specify your synthesis tool and use correct supported version 184.108.40.206. Review resource utilization reports after compilation 220.127.116.11. Review all Intel® Quartus® Prime messages, especially warning or error messages 18.104.22.168. Consider using incremental compilation 22.214.171.124. Ensure parallel compilation is enabled 126.96.36.199. Use the Compilation Time Advisor
188.8.131.52. Ensure timing constraints are complete and accurate 184.108.40.206. Review the Timing Analyzer reports after compilation 220.127.116.11. Ensure that the I/O timings are not violated when data is provided to the FPGA 18.104.22.168. Perform Early Timing Estimation before running a full compilation 22.214.171.124. Consider the following recommendations for timing optimization and analysis assignment: 126.96.36.199. Perform functional simulation at the beginning of your design flow 188.8.131.52. Perform timing simulation to ensure your design works in targeted device 184.108.40.206. Specify your simulation tool and use correct supported version
220.127.116.11. Provide accurate typical signal activities to get accurate power analysis result 18.104.22.168. Specify the correct operating conditions for power analysis 22.214.171.124. Analyze power consumption and heat dissipation in the Power Analyzer 126.96.36.199. Review recommended design techniques and Intel® Quartus® Prime options to optimize power consumption 188.8.131.52. Consider using a faster speed grade device 184.108.40.206. Optimize the clock power management 220.127.116.11. Reduce the number of memory clocking events 18.104.22.168. Consider I/O power guidelines 22.214.171.124. Reduce design glitches through pipelining and retiming 126.96.36.199. Review the information on power-driven compilation and Power Optimization Advisor 188.8.131.52. Reduce power consumption with architectural optimization
1.3.4. Ensure your board design supports the Intel® FPGA IP Evaluation Mode tethered mode
You can program your FPGA and verify your design in hardware before you purchase an IP license by using the Intel® FPGA IP Evaluation Mode feature available for many IP cores. Intel® FPGA IP Evaluation Mode supports the following modes:
- Untethered—your design runs for a limited time.
- Tethered—your design runs for the duration of the hardware evaluation period. This mode requires an Intel FPGA download cable connected to the JTAG port on your board and a host computer that runs the Intel® Quartus® Prime Programmer. If you plan to use this mode, ensure that your board design supports this mode.
Did you find the information on this page useful?