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
      • Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Vietnam
      • 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
FPGA
  • Technologies
  • More
FPGA
Forum How should I modify the constraints file for clock?
  • Blog
  • Forum
  • Documents
  • Quiz
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join FPGA to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Verified Answer
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 558 subscribers
  • Views 3050 views
  • Users 0 members are here
  • clock
  • xilinx
  • picoblaze
  • fpga
  • warning
Related

How should I modify the constraints file for clock?

rachit
rachit over 8 years ago

I am trying to implement the Picoblaze microprocessor on xc7k160tfbg676-2 FPGA (7 Series) using Vivado 14.2 on 64 bit Windows 7.  I was going through the provided "Picoblaze Design in Vivado" which is for the Kintex 7 KC705 Evaluation board. I modified the constraints file and substituted:

 

set_property PACKAGE_PIN AD12 [get_ports clk200_p]

set_property IOSTANDARD DIFF_SSTL15 [get_ports clk200_p]

#

set_property PACKAGE_PIN AD11 [get_ports clk200_n]

set_property IOSTANDARD DIFF_SSTL15 [get_ports clk200_n]

 

for

 

set_property PACKAGE_PIN MGTREFCLK0/1P [get_ports clk200_p]

set_property IOSTANDARD LVDS [get_ports clk200_p]

#

set_property PACKAGE_PIN MGTREFCLK0/1N [get_ports clk200_n]

set_property IOSTANDARD LVDS [get_ports clk200_n]

#

 

But it is showing crtical warning: "[Common 17-69] Command failed: 'MGTREFCLK0/1P' is not a valid site or package pin name. ["D:/vivado_projs_14p2/uart6_kc705/uart6_kc705.srcs/constrs_1/new/uart6_kc705.xdc":112]"

 

I tried changing the IOSTANDARD to LVDS_25 but same result.  Please assist.

  • Sign in to reply
  • Cancel

Top Replies

  • michaelkellett
    michaelkellett over 8 years ago +2 suggested
    Its because pins have PACKAGE_PIN properties like AA1 or W15. In the original constraint the pins are AD11 and AD12, look up the package references for the pins you want to use (and they will be similar…
  • michaelkellett
    michaelkellett over 8 years ago in reply to rachit +1 verified
    On page 57 of that document it tells you about the ASCII pinout files. You need to download one of these and look at it with Excel. You need the schematic diagram of your board. From the schematic you…
  • rachaelp
    rachaelp over 8 years ago in reply to rachit +1
    Rachit Ajitsaria wrote: Thanks for the help MK. I am currently an intern, so neither of the options apply to me. I did dig around. Found the schematics as per your advice and changed the pins to Y23 and…
  • michaelkellett
    0 michaelkellett over 8 years ago

    Its because pins have PACKAGE_PIN properties like AA1 or W15.

     

    In the original constraint the pins are AD11 and AD12, look up the package references for the pins you want to use (and they will be similar to A1 B2 etc)  and put them in the constraint.

     

    If you use the pin editor to generate the constraint it won't let you do wrong things. I'm not sure that LVDS is  a valid IOSTANDARD.

     

    What board are you using ?

     

    MK

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • rachit
    0 rachit over 8 years ago in reply to michaelkellett

    Hi.  I am still new to FPGA, so don't mind my ignorance.  I went through the user guide for KC705 and found this for AD11 and AD12.
    image

    And then I went through this https://www.xilinx.com/support/documentation/user_guides/ug475_7Series_Pkg_Pinout.pdf  and found this:

     

     

    image

    I thought that the pin definitions were similar and hence changed them.  I changed the IOSOURCE based on a few readings.

     

    The part number for my FPGA is XC7k160tFBG676-2.  Unfortunately, I don't know the board.  But it belongs to the 7 series.

     

    Thank you.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • michaelkellett
    0 michaelkellett over 8 years ago in reply to rachit

    On page 57 of that document it tells you about the ASCII pinout files. You need to download one of these and look at it with Excel. You need the schematic diagram of your board. From the schematic you can work out which pins the clock is connected to and the voltage at which the IO pins must be programmed to operate.

     

    Are you a student or is this for commercial work ?

     

    If  student then grab a tutor and ask a lot of questions, if commercial get your boss to send you on a Xilinx course - you'll learn as much in 1 week of a course as you will in 4 of experimenting so it will pay back.

     

    MK

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • rachit
    0 rachit over 8 years ago in reply to michaelkellett

    Thanks for the help MK.  I am currently an intern, so neither of the options apply to me.  I did dig around.  Found the schematics as per your advice and changed the pins to Y23 and AA24.  Worked.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • rachaelp
    0 rachaelp over 8 years ago in reply to rachit

    Rachit Ajitsaria wrote:

     

    Thanks for the help MK. I am currently an intern, so neither of the options apply to me. I did dig around. Found the schematics as per your advice and changed the pins to Y23 and AA24. Worked.

    Presumably as an intern you are not just left to your own devices, you must have a team leader or somebody to oversees what you are doing? They should be able to help you so ask them lots of questions just as you would a tutor at college. If there isn't anybody else there to help you then I think the 2nd option still applies, if the company wants an intern to do this work then they should consider training requirements and factor in this cost.

     

    Anyway, I'm glad michaelkellett was able to help you out and you've got this issue solved. Good luck with the rest of your project.

     

    Best Regards,

     

    Rachael

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • michaelkellett
    0 michaelkellett over 8 years ago in reply to rachit

    Happy it worked - I'm not so far ahead of you on Xilinx - I've been using Lattice parts and tools for years (the last 10 or so) but just started (March) a big project moving one customer over to Xlinx and Vivado. It's quite hard getting used to a very different way of working.

     

    MK

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • rachit
    0 rachit over 8 years ago in reply to rachaelp

    Thanks Rachel.  My advisor is very helpful, but cannot be present with me all the time.  So I need to figure things out or else I will have a very low productive day.  Thanks again.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
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