This website uses cookies. By using this site, you consent to the use of cookies. For more information, please take a look at our Privacy Policy.
Home > FPGA Technical Tutorials > FPGA-Based Prototyping Methodology > Getting the design ready for the prototype > Design implementation: place & route

TABLE OF CONTENTS

Xilinx FPGA FPGA Forum

Design implementation: place & route

FONT SIZE : AAA

Place & route tools take the FPGA-level netlist, implementation constraints, and  tool-specific directives generated by the synthesis tool, and perform mapping, and  place & route to produce a bitfile to download into the FPGA on the board. If the  design was properly constrained in the synthesis phase all implementation  constraints will flow from the synthesis tool to the place and route tools. The user  can provide a number of tool directives such as operational modes, effort levels, and  reporting details to optimize its operation and reporting.

During the place & route process, the tools provide various intermediate status  reports. Since for large designs the place & route process can take hours to  complete, it is recommended that we review these intermediate reports as they  become available and determine if the process is progressing as expected or if an  intervention is needed. The following is a list of the critical reports typically  generated through the place & route process:

• Mapping and utilization reports: these reports provide an account of the  resources found in the design. These reports may indicate problems in the  design if logic was unexpectedly removed etc. This can happen due to  improper inclusion of cores as black boxes, or a cascading effect due to the  removal of other blocks. To rectify such situations we should go back to  the design and verify that the removed blocks are properly connected to the  design after synthesis, that all cores are properly instantiated and all cores’  netlist files are available to the place & route tools.  

• Preliminary timing report: usually before the full place & route process  takes place, the tools estimate if the timing constraints are possible for the  design. If for example, the number of combinatorial logic levels between  two FFs is such that the time it will take to propagate through them is  greater than the requested clock period, even with minimal routing delays,  the tool may stop processing the design. In such case we need to  understand the critical timing violations and determine if paths can be  multi-cycle paths or make design changes to shorten them.  

• Final timing report: this is the ultimate timing report for the design after  the place & route process is complete. This report should be used to  determine if the design meets the desired timing. If the timing results do  not meet the requirements, the prototyping engineer needs to understand  which paths are too long and rectify the issues either through tools’  performance parameters, tighter constraints, or design changes. It’s  important to note that the timing reports are for each FPGA in isolation,  and external timing analysis needs to be done, such as FPGA to FPGA and  FPGA to other hardware. As mentioned in the “Design modifications due  to prototyping system” section in this chapter, inserting FFs at all FPGA  IOs will significantly optimize and simplify board-level timing  calculations.  

There are other manuals regarding the place and route of FPGA designs,  including those in the references. In general, the default operation of place  and route may suffice for some projects but as with all tool flows,  exceptions will occur that require us to “roll up our sleeves” and become  expert in some aspects of some tools. As discussed in chapter 4, FPGA based prototyping is most successful when performed by FPGA experts.



  • XC2C512-10FG324C

    Manufacturer:Xilinx

  • CPLD CoolRunner -II Family 12K Gates 512 Macro Cells 128MHz 0.18um Technology 1.8V 324-Pin FBGA
  • Product Categories: CPLDs

    Lifecycle:Active Active

    RoHS:

  • XC2C512-10FT256C

    Manufacturer:Xilinx

  • CPLD CoolRunner -II Family 12K Gates 512 Macro Cells 128MHz 0.18um Technology 1.8V 256-Pin FTBGA
  • Product Categories: Embedded - CPLDs (Complex Programmable Logic Devices)

    Lifecycle:Active Active

    RoHS: No RoHS

  • XC5215-5HQ208C

    Manufacturer:Xilinx

  • FPGA XC5200 Family 23K Gates 1936 Cells 83MHz 0.5um Technology 5V 208-Pin HSPQFP EP
  • Product Categories: FPGAs

    Lifecycle:Obsolete -

    RoHS: No RoHS

  • XC3S50-5VQ100C

    Manufacturer:Xilinx

  • FPGA Spartan-3 Family 50K Gates 1728 Cells 725MHz 90nm Technology 1.2V 100-Pin VTQFP
  • Product Categories: FPGAs

    Lifecycle:Active Active

    RoHS: No RoHS

  • XC3S50A-4FTG256I

    Manufacturer:Xilinx

  • FPGA Spartan-3A Family 50K Gates 1584 Cells 667MHz 90nm Technology 1.2V 256-Pin FTBGA
  • Product Categories: FPGAs

    Lifecycle:Active Active

    RoHS:

Need Help?

Support

If you have any questions about the product and related issues, Please contact us.