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 Custom ethernet MAC pin problems when generating a bitstream.
  • 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 359 subscribers
  • Views 305 views
  • Users 0 members are here
Related

Custom ethernet MAC pin problems when generating a bitstream.

Former Member
Former Member over 13 years ago

Hi there,
  I've been working on a project where I have had to implement a custom MAC (basically a heavily modified version of the ethernet tri mac from OpenCores.org).
 
  The design in XPS passes DRC and generates a netlist with no errors but when it comes to generating a bitstream, I get the errors, shown below, on the 4 transmit pins and clock.
 
  I have disabled the internal Eth0 device and added the specific RGMII pins to system.ucf as shown below the error log.
 
  I have made these ports external in XPS and connected the Xilinx gmii_to_rgmii(v1.00.a) adapters RGMII interface to those pins and then connected the GMII interface to the custom MAC.
 
  Does anyone know what I might need to do to configure the pins correctly? Is there a setting I'm missing somewhere?
 

  Please forgive the messy text, there doesn't seem to be a <code> tag on this forum that I'm aware of.
 
------------------------- Start of Error Log ------------------------- 
ERROR:Pack:1107 - Pack was unable to combine the symbols listed below into a
   single IOB component because the site type selected is not compatible.

   Further explanation:
   The component type is determined by the types of logic and the properties and
   configuration of the logic it contains. In this case an IO component of type
   IOB was chosen because the IO contains symbols and/or properties consistent
   with input, output, or bi-directional usage and contains no other symbols or
   properties that require a more specific IO component type. Please double
   check that the types of logic elements and all of their relevant properties
   and configuration options are compatible with the physical site type of the
   constraint.

   Summary:
   Symbols involved:
   tBUF symbol "ETH_RGMII_TXD_0_OBUF" (Output Signal = ETH_RGMII_TXD<0>)
   tPAD symbol "ETH_RGMII_TXD<0>" (Pad Signal = ETH_RGMII_TXD<0>)
   Component type involved: IOB
   Site Location involved: E9
   Site Type involved: IOPAD
-------------------------  End of Error Log  ------------------------- 
  
 

------------------- Start of System.ucf additions --------------------
net ETH_RGMII_RXD<0> tLOC = E11 | IOSTANDARD = LVCMOS18;
net ETH_RGMII_RXD<1> tLOC = B7  | IOSTANDARD = LVCMOS18;
net ETH_RGMII_RXD<2> tLOC = F12 | IOSTANDARD = LVCMOS18;
net ETH_RGMII_RXD<3> tLOC = A13 | IOSTANDARD = LVCMOS18;
net ETH_RGMII_RX_CTRLtLOC = D7  | IOSTANDARD = LVCMOS18;
net ETH_RGMII_RX_CLKtLOC = A14 | IOSTANDARD = LVCMOS18;
net ETH_RGMII_TXD<0> tLOC = E9  | IOSTANDARD = LVCMOS18;
net ETH_RGMII_TXD<1> tLOC = A7  | IOSTANDARD = LVCMOS18;
net ETH_RGMII_TXD<2> tLOC = E10 | IOSTANDARD = LVCMOS18;
net ETH_RGMII_TXD<3> tLOC = A8  | IOSTANDARD = LVCMOS18;
net ETH_RGMII_TX_CTRL   LOC = F11 | IOSTANDARD = LVCMOS18;
net ETH_RGMII_TX_CLK    LOC = D6  | IOSTANDARD = LVCMOS18;
net ETH_RGMII_MDIO      LOC = C12 | IOSTANDARD = LVCMOS18;
net ETH_RGMII_MDC       LOC = D10 | IOSTANDARD = LVCMOS18;
------------------- End of System.ucf additions ----------------------

 
 
 
 

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

    Looking at the diagram in UG585 (Zynq 7000 TRM) section 16.1.3 it looks like the GMII signals might be accessed via the PL but it would seem there is no way to enable the EMIO MUX for these signals but keep the actual MAC disabled.


    I've no idea why the recieve pins didn't generate any errors but it looks like the only way is to add a second PHY chip and RJ45 connector via the FMC or PMOD connectors.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • Former Member
    0 Former Member over 13 years ago

    Looking at the diagram in UG585 (Zynq 7000 TRM) section 16.1.3 it looks like the GMII signals might be accessed via the PL but it would seem there is no way to enable the EMIO MUX for these signals but keep the actual MAC disabled.


    I've no idea why the recieve pins didn't generate any errors but it looks like the only way is to add a second PHY chip and RJ45 connector via the FMC or PMOD connectors.

    • 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 © 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