imx6ull custom board with eth0 down

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

imx6ull custom board with eth0 down

1,481 Views
fabio_poiatti
Contributor III

Hi,

my custombord with IMX6ULL designed on EVK bases, has now the eth0 not working.

This is the behaviours

root@imx6ull14x14evk:~# ifdown eth0
root@imx6ull14x14evk:~# ifup eth0
Micrel KSZ8081 or KSZ8091 2188000.ethernet-1:01: attached PHY driver [Micrel KSZ8081 or KSZ8091] (mii_bus:phy_addr=2188000.ethernet-1:01, irq=POLL)
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc: started, v1.27.2
udhcpc: sending discover
fec 2188000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
udhcpc: sending discover
udhcpc: sending discover
udhcpc: no lease, forking to background

with this DTS file 

&fec1 {
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_enet1>;
phy-mode = "rmii";
phy-handle = <&ethphy0>;
status = "okay";

mdio {
#address-cells = <1>;
#size-cells = <0>;

ethphy0: ethernet-phy@2 {
compatible = "ethernet-phy-ieee802.3-c22";
reg = <1>;
micrel,led-mode = <1>;
clocks = <&clks IMX6UL_CLK_ENET_REF>;
clock-names = "rmii-ref";
};
};

};

and

pinctrl_enet1: enet1grp {
fsl,pins = <
MX6UL_PAD_ENET1_RX_EN__ENET1_RX_EN 0x1b0b0
MX6UL_PAD_ENET1_RX_ER__ENET1_RX_ER 0x1b0b0
MX6UL_PAD_ENET1_RX_DATA0__ENET1_RDATA00 0x1b0b0
MX6UL_PAD_ENET1_RX_DATA1__ENET1_RDATA01 0x1b0b0
MX6UL_PAD_ENET1_TX_EN__ENET1_TX_EN 0x1b0b0
MX6UL_PAD_ENET1_TX_DATA0__ENET1_TDATA00 0x1b0b0
MX6UL_PAD_ENET1_TX_DATA1__ENET1_TDATA01 0x1b0b0
MX6UL_PAD_ENET1_TX_CLK__ENET1_REF_CLK1 0x4001b031

/* modification for custom board */
MX6UL_PAD_ENET2_RX_DATA0__ENET1_MDIO 0x1b0b0
MX6UL_PAD_ENET2_RX_DATA1__ENET1_MDC 0x1b0b0
MX6UL_PAD_GPIO1_IO06__GPIO1_IO06 0x80000000
MX6UL_PAD_GPIO1_IO07__GPIO1_IO07 0x80000000

/* modification for custom board */
>;
};

Any suggestion?

Thanks

Fabio

0 Kudos
Reply
10 Replies

1,203 Views
igorpadykov
NXP Employee
NXP Employee

Hi Fabio

one can test it in uboot, pay attention to clock configuration in

function setup_fec() by ENET_CLK_SEL, ENET_CLK_DIR, register IOMUXC_GPR_GPR1

mx6ullevk.c\mx6ullevk\freescale\board - uboot-imx - i.MX U-Boot 

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos
Reply

1,203 Views
fabio_poiatti
Contributor III

I checked ans all it seems well configured ...

What else can I check?

thanks

0 Kudos
Reply

1,203 Views
igorpadykov
NXP Employee
NXP Employee

please check with nxp uboot, link

uboot-imx - i.MX U-Boot 

~igor

0 Kudos
Reply

1,203 Views
fabio_poiatti
Contributor III

I think it is not possible because in our board we use MDIO and MDC coming

from ENET2 pin and not as default

MX6UL_PAD_ENET2_RX_DATA0__ENET1_MDIO 0x1b0b0
MX6UL_PAD_ENET2_RX_DATA1__ENET1_MDC 0x1b0b0

Thanks

0 Kudos
Reply

1,203 Views
fabio_poiatti
Contributor III

some other clarification ...

in the EVB when eths are working I see on the log ...

Net:
Warning: ethernet@020b4000 using MAC address from ROM
eth1: ethernet@020b4000 [PRIME]
Warning: ethernet@02188000 using MAC address from ROM
, eth0: ethernet@02188000

while in my custom board (only eth0 is physically connected) I see

Net: Ethernet@0x20b4000 is fused, disable it
No ethernet found.

It seem the boot is looking only for 0x20b4000 but my eth is ENET1 so 0x21880000

During the startup sequence, the log trace (in my custom board)

fec 2188000.ethernet: 2188000.ethernet supply phy not found, using dummy regulator
pps pps0: new PPS source ptp0
fec 2188000.ethernet (unnamed net_device) (uninitialized): Invalid MAC address: 00:00:00:00:00:00
fec 2188000.ethernet (unnamed net_device) (uninitialized): Using random MAC address: 3e:ac:03:d9:0d:3a
libphy: fec_enet_mii_bus: probed
fec 2188000.ethernet eth0: registered PHC device 0

and at the end ...

Configuring network interfaces... Micrel KSZ8081 or KSZ8091 2188000.ethernet-1:01: attached PHY driver [Micrel KSZ8081 or KSZ8091] (mii_bus:phy_addr=2188000.ethernet-1:01, irq=POLL)
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc: started, v1.27.2
udhcpc: sending discover
fec 2188000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
udhcpc: sending discover
udhcpc: sending discover
udhcpc: no lease, forking to background
done.

I hope these information can help you to help me ...

0 Kudos
Reply

1,203 Views
igorpadykov
NXP Employee
NXP Employee

if this part with one enet (no ENET2) seems no possible to

use ENET2 MDIO and default GPIO1_IO06/7 should be used.

Best regards
igor

0 Kudos
Reply

1,203 Views
fabio_poiatti
Contributor III

Are you sure enough about this behaviour?

Is not possible to use enet1 with ENET2_MDIO without enet2 configuration?

Thanks

0 Kudos
Reply

1,203 Views
igorpadykov
NXP Employee
NXP Employee

what is full part number of used device ?

0 Kudos
Reply

1,203 Views
fabio_poiatti
Contributor III

Hi,

he made some hw modification and now eth0 is working connected directly with default MDIO and MDC.

But another question regards MAC ... how is possible to have fixed MAC? where the MAC in written in the boot?

We have this message during the startup ...

fec 2188000.ethernet: 2188000.ethernet supply phy not found, using dummy regulator
pps pps0: new PPS source ptp0
fec 2188000.ethernet (unnamed net_device) (uninitialized): Invalid MAC address: 00:00:00:00:00:00
fec 2188000.ethernet (unnamed net_device) (uninitialized): Using random MAC address: ce:10:be:1d:a5:c0
libphy: fec_enet_mii_bus: probed
fec 2188000.ethernet eth0: registered PHC device 0
PPP generic driver version 2.4.2

Thanks

Fabio

0 Kudos
Reply

1,203 Views
igorpadykov
NXP Employee
NXP Employee

Hi Fabio

 

for MAC please create new thread.

 

Best regards
igor

0 Kudos
Reply