Ethernet is not running in Zedboard

Hi Seetharam,

We have a Getting Started Guide posted in the Documents section on ZedBoard.org which contains a section on using the ZedBoard Ethernet.

http://zedboard.org/sites/default/files/documentations/GS-AES-Z7EV-7Z020-G-14.1-V6%5B1%5D.pdf

Although it does not cover usage of the ping command, it does cover the http, ftp, and ssh support that should be available using the out of box SD card content.

Have you checked this document to see if any of these Linux features are operational over your Ethernet connection?

Regards,

-Kevin

Hi Kevin,
Thanks for the prompt reply.
I ran as per the document and it is working fine(except the SSH client I tried the http & ftp from my browser) and then  ping the PC from the Zedboard. Only the self pinging is not working. Self Pinging(Loop back) is working on the ZC702 board. I tried with the IP address(192.168.1.10) using the straight cable between PC and zedboard and after changing the IP address to match with the LAN setup through hub. Both way no differences
I wasn't sure any other settings(I like to get some explanation why self pinging is working on EZ702 and not in ZedBoard) causes the ethernet chip not working. I see the error as DHCP server not responding but the static one also not picking up.

Seetharam,

Can you please elaborate on what you mean by the self-pinging?  Are you talking about pinging the address of lo or eth0 adapters? 

I tried pinging both adapters on my ZedBoard and there was no response which seems to match what you are seeing. 

i did some experimenting since I noticed that lo was not even listed.  First I brought lo up using the following command:

zynq> ifconfig lo up

Then I was able to ping 127.0.0.1 successfully.

For grins, I brought eth0 down and then back up using the following commands:

zynq> ifconfig eth0 down
zynq> ifconfig eth0 up

Then I was able to ping 192.168.1.10 successfully.

Not sure if I have a good explanation for this behavior though.  Maybe this has something to do with the order that things are brought up in /dev/init.d/rcS?

Please let me know if you see the same thing on your end.

Regards,

-Kevin

Kevin,
Yep. I see the same over here.
Once I enable the loop back(ifconfig lo up) I can ping the 127.0.0.1 or the IP address of Zedboard.The other command is not required.Explanation could be ZC702 it is enabled and Zedboard it is not enabled by default.
Looks like I am missing some setting still in driver level at BSP code.Do you have any suggestions other than the PHY address any other specific settings required for Marvell 88E1518 chip compare to 88E111R?

Seetharam,

I am glad that we are both seeing the same behavior even though it might not be the expected behavior.

I don't think that there were any changes made within the Ethernet driver itself for ZedBoard.  I would suggest taking a look at the device tree entry for the Ethernet driver and see if there are any differences from the device tree entry used for ZC702. 

This may help you isolate a chip specific setting that you might need for your BSP code.

Here is the Ethernet device entry for ZedBoard out-of-box demos:

eth@e000b000 {
    compatible = "xlnx,ps7-ethernet-1.00.a";
    reg = <0xe000b000 0x1000>;
    interrupts = <0x0 0x16 0x0>;
    interrupt-parent = <0x1>;
    phy-handle = <0x2>;
    #address-cells = <0x1>;
    #size-cells = <0x0>;
    xlnx,ptp-enet-clock = <0x69f6bc7>;
    xlnx,slcr-div0-1000Mbps = <0x8>;
    xlnx,slcr-div0-100Mbps = <0x8>;
    xlnx,slcr-div0-10Mbps = <0x8>;
    xlnx,slcr-div1-1000Mbps = <0x1>;
    xlnx,slcr-div1-100Mbps = <0x5>;
    xlnx,slcr-div1-10Mbps = <0x32>;

    mdio {
        #address-cells = <0x1>;
        #size-cells = <0x0>;

        phy@0 {
            compatible = "marvell,88e1510";
            device_type = "ethernet-phy";
            reg = <0x0>;
            marvell,reg-init = <0x3 0x10 0xff00 0x1e 0x3 0x11 0xfff0 0xa>;
            linux,phandle = <0x2>;
            phandle = <0x2>;
        };
    };
};

Please let us know if you find something useful.

Regards,

-Kevin

P.S.  Sorry about the code snippet formatting, the forum editor seems to enjoy chewing these up.

I have followed all instructions noted in http://www.zedboard.org/zh-hant/content/zedboard-network-bring but no luck.
1. Do I need any specific settings on my Win7-64 laptop?
2. I tried to turn off "Windows Firewall", still no luck
Any other suggestions? I am not a network expert which makes it a little harder. Please help!!!

Hi Seetharam,

I know this thread is a little old but I figure it's worth a shot.

I'm currently trying to accomplish something similar to you in that I'd like to port a QNX BSP from the ZC702 to the Zedboard.

Like you, I changed the PHY address to 0 in my source code and still had no luck.

After some more digging, I noticed that the ZC702 has a reset line connected to the PHY from MIO11 (this signal is AND'ed with the POR signal). On the Zedboard, there is only the POR signal connected to the PHY reset line meaning the SoC can't reset the PHY. So if the driver attempts to reset the PHY in software during configuration (which the QNX driver does when it's started), it will fail.

I also noticed that the Ethernet frequencies (ENET0_FREQ and ENET1_FREQ in ps7_init.h) are different between the ZC702 and the Zedboard. I don't know if these frequencies are PHY specific as I haven't been able to find the datasheets for the 88E1518 or 88E111R (I believe you need an NDA signed with Marvell to access them and I haven't gotten that desperate yet).

Have you happened to make any new discoveries since you posted last September?


Best regards,
Chris

I'm posting for anyone else who happens across this thread. Hopefully, this will be useful for somebody.

There are a few things that need to be addressed to port Ethernet connectivity from a ZC702 board support package to the Zedboard. Here are the changes I had to make to get Ethernet up and running:

1) Hardcode the PHY address to 0
2) The ZC702 seems to store the PHY MAC address in an I2C EEPROM. I had to eliminate any EEPROM code to make sure nothing hangs/fails in trying to access it and then hardcode the MAC address to 00:0a:35:00:01:22
3) I eliminated any code that attempted to reset the PHY through MIO 11 as this connection is not wired on the Zedboard
3) I didn't actually need this, but you may need to change the PHY ID to 0x1410dd1

The good news is that the lacking reset line wiring won't prevent you from getting everything talking nicely.


Best,
Chris

The out of box image shipped with ZedBoard works but I am seeing the behaviour described above on
Zynq 14.6 / 2013.2 Release (latest)
Zynq 14.5 / 2013.1 Release
None of the suggestions above fix the issue. Has anyone had any luck with this?

I've run into this issue with Xilinx Zynq-7000 AP SoC ZC706 Evaluation Kit.

Issue:
DHCP was working after running dhclient. The tx packet counter increases to 1, but I could not send any other packets. Receiving packets seems to work as the rx packet counter increases. It isn't a hardware problem as DHCP was working.
I tried replacing the kernel, modified the device tree and changed kernel args, but no luck.

Solution:
I downloaded the prebuilt FSBL.elf from
http://www.wiki.xilinx.com/Zynq+14.6-2013.2+Release
and created a new boot.bin.
Now everything works.

For reference see here:
http://forums.xilinx.com/t5/Xilinx-Boards-and-Kits/zc706-ethernet-does-not-work/td-p/347803