element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet & Tria Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
PicoZed Hardware Design PicoZed 7020 Package flight times
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Avnet Boards Forums to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Verified Answer
  • Replies 4 replies
  • Subscribers 339 subscribers
  • Views 695 views
  • Users 0 members are here
Related

PicoZed 7020 Package flight times

Former Member
Former Member over 9 years ago

Hello all,

 

Is it possible to get a copy of the picozed 7020 package flight times - specifically for the DDR3 interface nets?

Thanks!

  • Sign in to reply
  • Cancel
Parents
  • bhfletcher
    0 bhfletcher over 9 years ago

    Xilinx makes it possible for you to generate these for yourself. See UG899:

     

    Package Trace Length
    Instead of giving trace length data, Vivado Design Suite provides trace delay data, which is
    the most accurate way to estimate package delay.
    1. Open a design in Vivado, either RTL, netlist or implemented.
    2. Select Export > I/O Ports > CSV to see the min and max package delays for each pin.
    The min/max trace delays are also displayed in the Package Pins window for every
    package pin within two separate columns.
    Alternatively, you can select File > Export I/O ports for a CSV type spreadsheet that
    includes delays.
    3. The following TCL commands can be used is there is no project:
    link_design -part <part_number>
    write_csv <file_name>
    For Example:
    link_design -part xc7k410tffg900-2
    write_csv flight_time
     
    I have also created a TCL script that will do this as well.
     
      set part_name "xc7z020-clg400"
       
      create_project ExportPKG -part $part_name
      create_bd_design "design_1"
      generate_target all [get_files  ./ExportPKG.srcs/sources_1/bd/design_1/design_1.bd]
      make_wrapper -files [get_files ./ExportPKG.srcs/sources_1/bd/design_1/design_1.bd] -top
      add_files -norecurse ./ExportPKG.srcs/sources_1/bd/design_1/hdl/design_1_wrapper.v
      update_compile_order -fileset sources_1
      update_compile_order -fileset sim_1
      launch_runs synth_1
      wait_on_run synth_1
      open_run synth_1 -name netlist_1
      write_csv ./${part_name}.csv
     
    I am not able to attach a file here, but if you still need it, reply and I will post online somewhere.
     
    Bryan
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • bhfletcher
    0 bhfletcher over 9 years ago

    Xilinx makes it possible for you to generate these for yourself. See UG899:

     

    Package Trace Length
    Instead of giving trace length data, Vivado Design Suite provides trace delay data, which is
    the most accurate way to estimate package delay.
    1. Open a design in Vivado, either RTL, netlist or implemented.
    2. Select Export > I/O Ports > CSV to see the min and max package delays for each pin.
    The min/max trace delays are also displayed in the Package Pins window for every
    package pin within two separate columns.
    Alternatively, you can select File > Export I/O ports for a CSV type spreadsheet that
    includes delays.
    3. The following TCL commands can be used is there is no project:
    link_design -part <part_number>
    write_csv <file_name>
    For Example:
    link_design -part xc7k410tffg900-2
    write_csv flight_time
     
    I have also created a TCL script that will do this as well.
     
      set part_name "xc7z020-clg400"
       
      create_project ExportPKG -part $part_name
      create_bd_design "design_1"
      generate_target all [get_files  ./ExportPKG.srcs/sources_1/bd/design_1/design_1.bd]
      make_wrapper -files [get_files ./ExportPKG.srcs/sources_1/bd/design_1/design_1.bd] -top
      add_files -norecurse ./ExportPKG.srcs/sources_1/bd/design_1/hdl/design_1_wrapper.v
      update_compile_order -fileset sources_1
      update_compile_order -fileset sim_1
      launch_runs synth_1
      wait_on_run synth_1
      open_run synth_1 -name netlist_1
      write_csv ./${part_name}.csv
     
    I am not able to attach a file here, but if you still need it, reply and I will post online somewhere.
     
    Bryan
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
No Data
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube