i.MX ProcessorsのトピックRe: mx6 ethernet ping fail

mx6 ethernet ping fail

xiaoqiangyang — Mon, 20 Apr 2015 09:15:08 GMT

Hi all,

We designed a new mx6q board based on i.MX6Q-SDP. We replaced the PHY chip AR8031 with RTL8211F.

Our IOMUX is the same as the reference board :

MX6Q_PAD_ENET_MDIO__ENET_MDIO,

MX6Q_PAD_ENET_MDC__ENET_MDC,

MX6Q_PAD_RGMII_TXC__ENET_RGMII_TXC,

MX6Q_PAD_RGMII_TD0__ENET_RGMII_TD0,

MX6Q_PAD_RGMII_TD1__ENET_RGMII_TD1,

MX6Q_PAD_RGMII_TD2__ENET_RGMII_TD2,

MX6Q_PAD_RGMII_TD3__ENET_RGMII_TD3,

MX6Q_PAD_RGMII_TX_CTL__ENET_RGMII_TX_CTL,

MX6Q_PAD_ENET_REF_CLK__ENET_TX_CLK,

MX6Q_PAD_RGMII_RXC__ENET_RGMII_RXC,

MX6Q_PAD_RGMII_RD0__ENET_RGMII_RD0,

MX6Q_PAD_RGMII_RD1__ENET_RGMII_RD1,

MX6Q_PAD_RGMII_RD2__ENET_RGMII_RD2,

MX6Q_PAD_RGMII_RD3__ENET_RGMII_RD3,

MX6Q_PAD_RGMII_RX_CTL__ENET_RGMII_RX_CTL,

In u-boot, after I set mac addr and ipaddr, I use ping command to test the ethernet:

MX6Q U-Boot > ping 192.168.2.1

FEC: Link is Up 79ad

Using FEC0 device

ping failed; host 192.168.2.1 is not alive

I can get a standard 125M Hz clock on CLK_OUT pin as ETH_REF_CLK. And the green led on RJ45 flashed very fast.

I can't get any packets using wireshark.

Below is the return of mii info command--->

MX6Q U-Boot > mii info

PHY 0x00: OUI = 0x0732, Model = 0x11, Rev = 0x06, 100baseT, FDX

PHY 0x01: OUI = 0x0732, Model = 0x11, Rev = 0x06, 100baseT, FDX

I can access RTL8211 with either adress 0 or 1, Why there are two devices?

In linux it have the same result, it indicated "PHY: 1:00 - Link is Up - 100/Full" and "PHY: 1:00 - Link is Down"

when I connect or disconnect it to network.(Our network switch is 100baseT)

The network environment is OK and the reference board's ethernet is OK with the same setting.

Who can help me?

Any advice will be appreciated.

Best Regargs

Xiaoqiang

Re: mx6 ethernet ping fail

alejandrolozan1 — Wed, 22 Apr 2015 23:43:28 GMT

Hi,

Have you tried to set this?

#define CONFIG_PHY_REALTEK

On my side I lack of that transciever but it is worth trying.

Please keep us informed.

/Alejandro

Re: mx6 ethernet ping fail

xiaoqiangyang — Thu, 23 Apr 2015 02:08:58 GMT

Yes, I have included this setting to kernel, it seems the mac have send data to phy but phy didn't send date out.

root@freescale ~$ ping 192.168.2.1

PING 192.168.2.1 (192.168.2.1): 56 data bytes

It stoped here until I type ctrl+C:

--- 192.168.2.1 ping statistics ---

279 packets transmitted, 0 packets received, 100% packet loss

root@freescale ~$ ifconfig

eth0 Link encap:Ethernet HWaddr 1E:ED:19:27:1A:B3

inet addr:192.168.2.66 Bcast:192.168.2.255 Mask:255.255.255.0

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:464 errors:0 dropped:0 overruns:0 frame:0

TX packets:285 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:35444 (34.6 KiB) TX bytes:27594 (26.9 KiB)

It tell me ethernet have sent and received packets but I can't catch any packets on out LAN.

From: Alejandro Lozano Lozano

Date: 2015-04-23 07:43

To: Xiaoqiang Yang

Subject: Re: - mx6 ethernet ping fail

mx6 ethernet ping fail

reply from Alejandro Lozano Lozano in i.MX Community - View the full discussion

Hi,

Have you tried to set this?

#define CONFIG_PHY_REALTEK

On my side I lack of that transciever but it is worth trying.

Please keep us informed.

/Alejandro

Did your question get answered?

If so, say thanks by clicking Correct Answer in the community thread!

Reply to this message by replying to this email, or go to the message on Freescale Community

Start a new discussion in i.MX Community by email or at Freescale Community

Following mx6 ethernet ping fail in these streams: Inbox

Re: mx6 ethernet ping fail

alejandrolozan1 — Thu, 23 Apr 2015 03:51:34 GMT

In fact I meant to enable that in uboot. Because you mentioned you had problems in uboot too.