element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • 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 Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • 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 Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
Ultrazed Hardware Design UltraZed Ethernet MAC ID
  • 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 Suggested Answer
  • Replies 4 replies
  • Answers 3 answers
  • Subscribers 326 subscribers
  • Views 1547 views
  • Users 0 members are here
Related

UltraZed Ethernet MAC ID

jdehaven
jdehaven over 6 years ago

The UltraZed EG SOM documentation has the following note about the Ethernet MAC ID:

image

However, page 5 of the IO carrier card schematic shows the MAC ID - EEPROM, but does not explain how the ID is implemented.

image

 

Does the UltraZed SOM come with a unique MAC ID that can be used by the customer, or does the customer carrier card need to supply a unique MAC ID to the UltraZed SOM?

 

Thanks,

John

  • Sign in to reply
  • Cancel
  • clem57
    0 clem57 over 6 years ago

    Look at ZedBoard MAC Address | Zedboard .

     

    The MAC address is defined within the kernel device tree on PetaLinux systems.  This means, once you define it once for one board, it is the same for every other board that you load that PetaLinux build onto.

     

    Here is the Xilinx official response for customers looking to assign MAC address across their boards:

     

    https://www.xilinx.com/support/answers/53476.html

    Hope that helps.

    Clem

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • jdehaven
    0 jdehaven over 6 years ago in reply to clem57

    To clarify, the UltraZed SOM and Zynq UltraScale+ SoC on the SOM do not have a unique MAC address.

     

    The Avnet IO Carrier Card for the UltraZed SOM has a Microchip EEPROM with a unique Ethernet MAC, and this Ethernet Mac is then used by the software running on the Zynq US+ to set the Ethernet MAC address(es) in the PS side of the SoC.  In otherwords, putting an inexpensive MAC ID chip on the customer carrier board is an alternative to the procedure outlined in AR#53476, correct?

     

    Thanks,

    John

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • clem57
    0 clem57 over 6 years ago in reply to jdehaven

    Here is the skinny. Petalinux stores the MAC in the DTB. It will recognize a hardware MAC in early boot phase and warn a mismatch. Later you can resolve this with:

    ZynqMP> setenv ethaddr xx:xx:xx:xx:xx:xx

    ZynqMP> saveenv

    This should save the environment and override DTB for the next boot.

    REF: https://forums.xilinx.com/t5/Embedded-Boot-and-Configuration/ZCU102-Mac-Address/m-p/958079

     

    Clem

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • zedhed
    0 zedhed over 5 years ago

    Hi John,

     

    I also wrote a blog article that touches on this topic:

     

    Homestretch To Production - MAC Address Programming Approaches

     

    My article also proposes an alternative to the U-Boot MAC ID programming method clem57 pointed out above.  The method I used boots the system with the default MAC ID, but then reassigned the network interface to the MAC ID read off the EEPROM.  Here is the script that I used on UltraZed-EG to read from the MAC ID EEPROM:

     

    https://github.com/Avnet/petalinux/blob/master/configs/meta-user/uz3eg_iocc/recipes-apps/mac-eeprom-config/files/mac_eep…

     

    The only other way I have seen this done elsewhere for systems booting from SPI Flash is to parse the QSPI Flash partition for U-Boot and overwrite the ethaddr environment variable so that the next time the system boots, U-Boot has already loaded the unique MAC address which is now also stored in NVM.

     

    Best Regards,

     

    -Kevin

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