Actions
Forum Thread Details
  • State Not Answered
  • Replies 12 replies
  • Subscribers 374 subscribers
  • Views 1369 views
  • Users 0 members are here
Related

no PHY setup on Zedboard using petalinux 2014.2

e14 Contributor

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

Parents
  • 0

    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.

Reply
  • 0

    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.

Children