[meta-xilinx] Ethernet PHY problems

Thu Sep 10 06:16:23 PDT 2015

The PHY is connected to Ethernet 0 (address e000b000).

According to our board supplier the PHY address is 0, however I plan to try others just in case!

Alan

-----Original message-----
From:S viswanath reddy <s.viswa141 at gmail.com>
Sent:Thu 10-09-2015 14:03
Subject:RE: [meta-xilinx] Ethernet PHY problems
To:Alan Hughes <alanhughes at e2eservices.co.uk>; 

I saw your dts file .
 Ps7 Ethernet 0 
 Phy address is 0(zero)
 one  can you cross check phy address.

Is phy connect which Ethernet port

Ps7 Ethernet 0 or ps7 Ethernet 1 

Regards 
 Viswa

On 10 Sep 2015 18:09, "Alan Hughes" <alanhughes at e2eservices.co.uk> wrote:

The Marvell PHY is enabled using the CONFIG_MARVELL_PHY configuration parameter, which in turn is enabled by CONFIG_PHYLIB. The former is defined in line 1126 of the kernel configuration file, the latter a few lines above it.

Alan

-----Original message-----
From:S viswanath reddy <s.viswa141 at gmail.com>
Sent:Thu 10-09-2015 10:16
Subject:Re: [meta-xilinx] Ethernet PHY problems
To:Alan Hughes <alanhughes at e2eservices.co.uk>; 

Hi Alan

Alan once check Linux kernel configuration (make menuconfig)  Marvell phy driver enabled or not .

Thanks
 Viswa

On 10 Sep 2015 13:49, "Alan Hughes" <alanhughes at e2eservices.co.uk> wrote:

I am trying to build a BSP for a custom ZYNQ-7000 based board using Yocto 1.8 ("Fido") with the 3.19 Linux kernel based on the sources provided by Analogue Devices (2015.1 branch, see https://github.com/analogdevicesinc/linux/tree/2015_R1). The board has Marvell 88E1518 Gigabit PHY connected to one of theZYNQ's Ethernet controllers.

We do not see any unexpected messages when we boot the board; all devices seem to start up correctly. However during the kernel boot the PHY's indicator lights start to flash, which I assume means that there is some problem, although the kernel does not generate any error messages (even when debug output is enabled). Logging in to the BSP and entering the command "ip link set dev eth0 up" does not generate any error messages in the application or the kernel, however the interface remains in a "down" state.

We have confirmed that the PHY works by accessing it when in U-Boot; we've used DHCP to assign an address to the interface and ping'ed other devices on the local network. Also the PHY works with a test BSP provided by our board supplier; however the Linux kernel used by the supplier does not have the necessary device drivers available in it,

I have attached  BSP boot log and our device tree; both have been compressed to save bandwidth.

I would greatly appreciate any suggests as to what the problem might be, or alternately any ideas of approaches I can take to further diagnose the problem. I'm currently tearing my hair out on this one, which is a a bit of problem since I don't have a lot to tear out :-).

Thanks in advance

Alan Hughes

--------------------------------

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify the sender immediately and then delete the email from your system. 

 Internet communications are not secure and therefore e2E Services Ltd does not accept any liability for the contents of this message. Any views or opinions presented are solely those of the author and do not necessarily represent those of e2E Services Ltd. 

 Although this email and any attachments have been scanned for viruses, the success of scanning products is not guaranteed. The recipient(s) should therefore carry out any checks that they believe to be appropriate in this respect. 

 e2E Services Ltd. is a limited company re gistered in the UK, No. 3878701. Registered Office: e2E Services Ltd, George Court, Bartholomews Walk, Ely, Cambridgeshire, CB7 4JW

--
 _______________________________________________
 meta-xilinx mailing list
 meta-xilinx at yoctoproject.org
 https://lists.yoctoproject.org/listinfo/meta-xilinx

--------------------------------

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify the sender immediately and then delete the email from your system. 

 Internet communications are not secure and therefore e2E Services Ltd does not accept any liability for the contents of this message. Any views or opinions presented are solely those of the author and do not necessarily represent those of e2E Services Ltd. 

 Although this email and any attachments have been scanned for viruses, the success of scanning products is not guaranteed. The recipient(s) should therefore carry out any checks that they believe to be appropriate in this respect. 

 e2E Services Ltd. is a limited company re gistered in the UK, No. 3878701. Registered Office: e2E Services Ltd, George Court, Bartholomews Walk, Ely, Cambridgeshire, CB7 4JW

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify the sender immediately and then delete the email from your system. 

Internet communications are not secure and therefore e2E Services Ltd does not accept any liability for the contents of this message. Any views or opinions presented are solely those of the author and do not necessarily represent those of e2E Services Ltd.

Although this email and any attachments have been scanned for viruses, the success of scanning products is not guaranteed.  The recipient(s) should therefore carry out any checks that they believe to be appropriate in this respect.

e2E Services Ltd. is a limited company registered in the UK, No. 3878701. Registered Office: e2E Services Ltd, George Court, Bartholomews Walk,  Ely, Cambridgeshire, CB7 4JW 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20150910/ba75e727/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 9593 bytes
Desc: not available
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20150910/ba75e727/attachment.bin>