[meta-xilinx] Ethernet PHY problems

[Alan Levy]

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<mailto: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<mailto:alanhughes at e2eservices.co.uk>>;
CC: meta-xilinx at yoctoproject.org<mailto:meta-xilinx at yoctoproject.org>;
On Thu, Sep 10, 2015 at 6:19 PM, Alan Hughes
<alanhughes at e2eservices.co.uk<mailto: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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20150910/6041463c/attachment.html>