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
    About the element14 Community
  • 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
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet & Tria Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
ZedBoard Hardware Design Vivado 2015.3 issue with Zedboard
  • 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 Not Answered
  • Replies 1 reply
  • Subscribers 353 subscribers
  • Views 482 views
  • Users 0 members are here
Related

Vivado 2015.3 issue with Zedboard

Former Member
Former Member over 10 years ago

I posted this also on the Xilinx forums, but it looks more related to the board definition file of the Zedboard in Vivado 2015.3


I discovered several unexpected warnings in Vivado when making a basic design with the Zedboard :

just doing these basic steps :

1) create new project, select Zedboard
2) add Zynq
3) run block automation & connection automation
4) connect FCLK_CLK0 to M_AXI_GP0_ACLK
5) create wrapper
6) generate bitstream

In 2014.4 &  2015.2 this worked just fine, howver in 2015.3 :

I get 3 sysnthesis warnings :

[Synth 8-992] S_AXI_GP0_ACLK_temp is already implicitly declared earlier

[Synth 8-992] S_AXI_GP1_ACLK_temp is already implicitly declared earlier

[Synth 8-350] instance 'inst' of module 'processing_system7_v5_5_processing_system7' requires 685 connections, but only 672 given

A placement warning :

[Place 30-12] An IO Bus FIXED_IO_mio with more than one IO standard is found. Components associated with this bus are:

A Route desing warning :

[DRC 23-20] Rule violation (PLIO-7) Placement Constraints Check for IO constraints - An IO Bus FIXED_IO_mio[53:0] with more than one IO standard is found. Components associated with this bus are: LVCMOS18 (FIXED_IO_mio[53], ...

Also, when trying to test a basic LwIP, I get no ethernet communication, so there's definitely something wrong with this

  • Sign in to reply
  • Cancel
  • Former Member
    0 Former Member over 10 years ago

    Hello Ronny,

     

    I took a look at your issue by running the same procedure you outline with both Vivado 2015.2 and Vivado 2015.3. As a note I did not see the option for Connection Automation in a basic design with only the Zynq system block, only Block Automation.

     

    The synthesis warnings:

      Synth 8-350] instance 'inst' of module 'processing_system7_v5_5_processing_system7' requires 685 connections, but only 672 given 

     

    and the placement and route warnings:

    A placement warning :

    [Place 30-12] An IO Bus FIXED_IO_mio with more than one IO standard is found. Components associated with this bus are:

    A Route desing warning :

    [DRC 23-20] Rule violation (PLIO-7) Placement Constraints Check for IO constraints - An IO Bus FIXED_IO_mio[53:0] with more than one IO standard is found. Components associated with this bus are: LVCMOS18 (FIXED_IO_mio[53], ...

     

    were both present in Vivado 2015.2 as well. They appear innocuous (even if annoying) and one was discussed in this previous post:

    http://zedboard.org/content/warning-tutorial-01-04-solutions

     

    The other two synthesis warning are new to Vivado 2015.3 but appear harmless as well:

    [Synth 8-992] S_AXI_GP0_ACLK_temp is already implicitly declared earlier

    [Synth 8-992] S_AXI_GP1_ACLK_temp is already implicitly declared earlier

     

    I implemented the designs in both 2015.2 and 2015.3, exported to SDK and  generated the LWIP echo server example application. I downloaded the design via JTAG and both the 2015.2 and the 2015.3 LWIP echo servers seems to work properly for me. Can you verify that there is an issue on your end? I did notice that, when connected to a router, the LWIP echo server did not use the 192.168.1.10 IP address it lists in the LWIP header but one assigned by the router.

     

    We are bringing the issue to Xilinx's attention but you may want to pursue a support case with Xilinx as well. The ZedBoard board definition file is included as part of the Vivado 2015.x tools by Xilinx and not Avnet, so that is a Xilinx issue as well.

     

    -Gary

    • Cancel
    • Vote Up 0 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 © 2026 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