[meta-xilinx] Ethernet PHY problems

Thu Sep 10 09:38:06 PDT 2015

I have managed to do this, unfortunately the amount of information we get from the Xilinix EMACPS driver is pretty limited:

[    0.362148] xemacps e000b000.ps7-ethernet: BASEADDRESS hw: e000b000 virt: e0834000
[    0.370503] libphy: XEMACPS mii bus: probed
[    0.375038] xemacps e000b000.ps7-ethernet: MAC 0x00350a00, 0x00000001, 00:0a:35:00:01:00
[    0.383186] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 150

Examination of the source code pretty much confirms that there is nothing else there.

The Marvell PHY takes sparseness to a new extreme since it does not generate any debugging messages at all. I am looking (somewhat reluctantly at the moment) at patching some additional messages into both drivers and seeing what I get,

Alan

-----Original message-----
From:Alan Levy <alan.levy at plextek.com>
Sent:Thu 10-09-2015 13:55
Subject:RE: [meta-xilinx] Ethernet PHY problems
To:Alan Hughes <alanhughes at e2eservices.co.uk>; Nathan Rossi <nathan at nathanrossi.com>; 
CC:meta-xilinx at yoctoproject.org; 

The dmesg command prints out the entire contents of the kernel log so if the driver is actually generating debug messages they will appear there.

You can specify “loglevel=9” on the kernel command line to get it to display debug messages on the console in real time. 

Alternatively if you build the kernel with CONFIG_MAGIC_SYSRQ=y you can use the following shell command to achieve the same effect:

        echo 9 > /proc/sysrq-trigger

From: Alan Hughes [mailto:alanhughes at e2eservices.co.uk] 
 Sent: 10 September 2015 13:37
 To: Nathan Rossi
 Cc: meta-xilinx at yoctoproject.org
 Subject: Re: [meta-xilinx] Ethernet PHY problems

Nathan

I have just noticed that the code already includes the following lines (at about line 85 or thereabouts):

#ifundef DEBUG

#define DEBUG

.... loads of additional definitions ...

#endif

So it looks like debuggng code is already enabled.

I am still tryig to work out how to get the debigging messages from the kernel (I am not a kernel expert, so am still learning how to do things).

Alan

-----Original message-----
 From: Nathan Rossi <nathan at nathanrossi.com>
 Sent: Thu 10-09-2015 10:11
 Subject: Re: [meta-xilinx] Ethernet PHY problems
 To: Alan Hughes <alanhughes at e2eservices.co.uk>; 
 CC: meta-xilinx at yoctoproject.org; 
 On Thu, Sep 10, 2015 at 6:19 PM, 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 :-).

 I dont see any issues in the device-tree and your boot log looks fine.

 For further diagnosis setup debug output for the emacps driver, adding
 "#define DEBUG" to the top of the file should be enough:
 https://github.com/analogdevicesinc/linux/blob/2015_R1/drivers/net/ethernet/xilinx/xilinx_emacps.c

 Also it is worth adding the program ethtool to your rootfs, this is
 very useful for getting info about the link status and phy info of the
 device.

 Regards,
 Nathan

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/80feb023/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 11149 bytes
Desc: not available
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20150910/80feb023/attachment.bin>