Cliff Brake

i.MX6UL single ethernet interface

Discussion created by Cliff Brake on Jun 29, 2016
Latest reply on Jul 1, 2016 by Cliff Brake


Hi, we have a custom design that uses the Dart-6UL (i.mx6ul) from Variscite.  The development board has two Ethernet interfaces, and our custom hardware has a single Ethernet interface with a phy connected to the 2nd port.  When in u-boot, the link lights work fine, we can ping sites from u-boot, and tftpboot works.  When in Linux, the phy registers, but never detects when an ethernet cable is plugged in.  Because ethernet works in u-boot, we think the hardware is OK.  Could the lack of a phy on eth0 cause the phy on eth1 not to work?  I've tried modifying the device tree file, but have not found any changes that work yet.  I'm also a bit puzzled by the fec configure in the device tree files (copied below).  Why are both phys listed in the fec2 section, instead of one in each section?

 

&fec1 {

  pinctrl-names = "default";

  pinctrl-0 = <&pinctrl_enet1>;

  phy-mode = "rmii";

  phy-handle = <&ethphy0>;

  status = "okay";

};

 

 

&fec2 {

  pinctrl-names = "default";

  pinctrl-0 = <&pinctrl_enet2>;

  phy-mode = "rmii";

  phy-handle = <&ethphy1>;

  status = "okay";

 

 

  mdio {

  #address-cells = <1>;

  #size-cells = <0>;

 

 

  ethphy0: ethernet-phy@2 {

  compatible = "ethernet-phy-ieee802.3-c22";

  reg = <2>;

  };

 

 

  ethphy1: ethernet-phy@1 {

  compatible = "ethernet-phy-ieee802.3-c22";

  reg = <1>;

  };

  };

};

Outcomes