AnsweredAssumed Answered

AD-FMCOMMS-3EBZ VC707 ADI example Embedded linux newtwork issues

Question asked by AnhDat on Mar 26, 2015
Latest reply on Mar 27, 2015 by rgetz

Using the ready to load .bit and linux kernel from the wiki site I have always had issues with network connectivity.

I noticed this when trying to use the IIO Oscilloscope software and I could connect but network would time out usually when running fft's in the plot display.

After much testing, and different configurations, I believe it may be the embedded linux kernels setup of it's MAC interface as seen below?

The PHY is an SGMII PHY on the VC707 but the network service always shows an MII PHY?

The NIC usually doesn't seem to autonegotiate correctly?


I think this may explain why on rare occasions I am able to restart services and get things to work ok, but usually it fails.

Is there a newer latest out of the box .bit and kernel build for the VC707 / AD-FMCOMMS3-EBZ to try?


/etc/init.d # ./S41network restart

Stopping network...Starting network...

udhcpc (v1.22.1) started

net eth0: Promiscuous mode disabled.

net eth0: PHY already attached

net eth0: Promiscuous mode disabled.

Sending discover...

xilinx_axienet eth0: Link is Down

Sending discover...

xilinx_axienet eth0: Link is Up - 1Gbps/Full - flow control off

Sending discover...

No lease, failing

Using the default interface 'eth0'.

Using the specified MII PHY index 1.

Restarting negotiation...

Basic registers of MII PHY #1: 1140 01d8 0000 0000 0001 d801 0004 0000.

The autonegotiated capability is 0000.

No common media type was autonegotiated!

This is extremely unusual and typically indicates a configuration error.

Perhaps the advertised capability set was intentionally limited.

Basic mode control register 0x1140: Auto-negotiation enabled.

Basic mode status register 0x01d8 ... 01c8.

  Link status: not established.

Remote fault detected!

Your link partner advertised d801:.

  End of basic transceiver information.


/etc/init.d #