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
Avnet Boards General no PHY setup on Zedboard using petalinux 2014.2
  • 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 12 replies
  • Subscribers 374 subscribers
  • Views 1368 views
  • Users 0 members are here
Related

no PHY setup on Zedboard using petalinux 2014.2

e14 Contributor
e14 Contributor over 11 years ago

I have made a simple Zedboard configuration using Vivado 2014.2 and Petalinux 2014.2 under SUSE enterprise. The configuration just has the switches, buttons and LEDu2019s.
After exporting things from Vivado I run through the following

petalinux-create --type project --template <CPU_TYPE> --name <PROJECT_NAME>
cd <directory which contains hardware description file>
petalinux-config --get-hw-description -p <plnx-proj-root>

I use the menu to select SD card booting then run;

petalinux-build

Finally I do;

petalinux-package --boot --fsbl <FSBL image> --fpga <FPGA bitstream> --uboot

After copying the BOOT.bin and image.ub files onto and SD card the board boots up and runs my little test app ok.

I tried ifconfig 192.168.1.3 and that was OK but I get no response from a ping on the Ethernet. Looking at the boot results is appears I have the following error
u201CConfiguring network interfaces... xemacps e000b000.ps7-ethernet: eth0: no PHY setupu201D

Apparently this means I have no Ethernet driver, so my question is simple, what do I have to change in the build configuration to get this driver built for the Zedboard?

Thanks in advance for your help

  • Sign in to reply
  • Cancel
  • e14 Contributor
    0 e14 Contributor over 11 years ago

    This is almost certainly an issue with the devicetree.  Tske a look at the bsp package for 2014.2 under the zedboard reference designs for the correct entry.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • e14 Contributor
    0 e14 Contributor over 11 years ago in reply to e14 Contributor

    You are correct the system-top.dts under subsystems/linux/configs needs this adding

    &ps7_ethernet_0 {
    tphy-handle = <&phy0>;
    tmdio {
    tt#address-cells = <1>;
    tt#size-cells = <0>;
    ttphy0: phy@0 {
    tttcompatible = "marvell,88e1510";
    tttdevice_type = "ethernet-phy";
    tttreg = <0>;
    tt} ;
    t} ;
    };

    I donu2019t understand why this is not added automatically as the marvell option in selected in the kernel configuration PHY Device support and infrastructure menu so maybe this is a bug.

    Thank you for your help the my Ethernet works fine after I manually add the above and rebuild.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • bkamen
    0 bkamen over 11 years ago in reply to e14 Contributor

    I'm running into the same problem on the microZed -- which has a Marvell 88e1512.

    I've implemented this in either ps.dtsi and system-top.dts (adjusting the "compatible" line accordingly)

    Neither location changes anything.

    My kernal has all the MDIO options set...

    Always the same:

    "Configuring network interfaces... xemacps e000b000.ps7-ethernet: eth0: no PHY setup"


    uBoot works fine. (I realize that's different)

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • e14 Contributor
    0 e14 Contributor over 11 years ago in reply to bkamen

    I would suggest trying PetaLinux 2014.4, which seems to have corrected some ethernet issues.

     

    That said, this post might be helpful if you need to stay with PetaLinux 2014;2: http://zedboard.org/content/device-tree-fo-zynq-20144-linux-317

     

    -Gary

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • bkamen
    0 bkamen over 11 years ago

    (shaking head)

    I'll try that in the morning.

    What a nightmare this project/product has been.

    Nothing seems to work 100%.

    The ocean of documentation is filled with bugs.

    Every next step is hours of fighting a problem that probably shouldn't exist in the first place.

    I'll be back to report my results.

    -Ben

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • bkamen
    0 bkamen over 11 years ago

    I downloaded but decided to spool up the BSP for 2014.2 for the microZed020 and realized the Ethernet fixes that go in system-top.dts go OUTSIDE the top set of lines.

    I wasn't getting a warning/error -- and that was the why the entry wasn't making it to the .dtb file.

    So no need to jump to Vivado/Petalinux 2014.4 just yet.

    I'm finding version jumping is a precarious thing.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • e14 Contributor
    0 e14 Contributor over 11 years ago in reply to bkamen

    Thanks for letting us know how you resolved the issue.

     

    I would still encourage you to move to PetaLinux 2014.4. In long term testing of Ethernet on the MicroZed we, and several customers, have observed occasional errors using PetaLinux 2014.2 that do not appear in the same testing with PetaLinux 2014.4. We don't have a root cause for the errors but have been able to reproduce the results.

     

    -Gary

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • bkamen
    0 bkamen over 11 years ago in reply to e14 Contributor

    And I will eventually...

    I'd like to get my base image working first.

    Now that Ethernet is working (not sure the LED's are correct. Only the YEL LED shows up on a 1Gb connection), I need to get I2C-0 working on the PMOD connector (will post separately - it's not working)

    Would you happen to have the datasheet (or can provide guidance) on the 88e1512 used on the uZed-020?

    Thanks,

    -Ben

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • e14 Contributor
    0 e14 Contributor over 11 years ago

    Here is a forum post on the issue of MicroZed Ethernet LEDs that might be helpful:

     http://zedboard.org/content/ethernet-leds-constant-and-not-blinking

     

    As mentioned in that post the Marvell PHY data sheet is under an NDA (Non Disclosure Agreement). You can work with your local Avnet/Silica FAE to request access to the data sheet from Marvell.

     

    -Gary

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • bkamen
    0 bkamen over 11 years ago in reply to bkamen

    (SOLVED)

    As a follow-up on the LEDs, I'm guessing they're ok.

    It seems:

    GRN     = 10Mb/s
    YEL/GRN = 100Mb/s
    YEL     = 1Gb/s

    For anyone else who'd like to know.

    -Ben

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

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube