IMX-RMII-BRPHY : how to enable kernel drivers

[Poons]

Hello NxP Team,

Board : IMX8QXP MEK

Yocto : imx-5.4.24-2.1.0

Could you please provide steps to enable kernel drivers for IMX-RMII-BRPHY Daughter Card.

Thanks in advance.

Thanks,

Poons.

[Poons]

Hello Igor,

Thanks for your inputs.

I have checked Kernel menu configs and dts/dtb files as recommended. still network interface fails to connect.

Logs:

[ 2.535640] fec 5b050000.ethernet: Invalid MAC address: 00:00:00:00:00:00
[ 2.542493] fec 5b050000.ethernet: Using random MAC address: ca:0c:b1:92:23:44
[ 2.550661] libphy: fec_enet_mii_bus: probed
[ 2.555097] mdio_bus 5b050000.ethernet-1: MDIO device at address 2 is missing.
[ 2.563163] fec 5b050000.ethernet eth0: registered PHC device 0

[ 7.221637] fec 5b050000.ethernet eth0: Unable to connect to phy

could you please suggest what was the issue here. Thanks in advance.

Thanks,

Poons.

[igorpadykov]

Hi Poons

may be recommended to try latest Linux L5.4.70_2.3.0
https://source.codeaurora.org/external/imx/linux-imx/tree/?h=imx_5.4.70_2.3.0

Check uboot output of  command 'mdio list'.

The PHY address should be checked in both hardware and device tree, for TJA1100, PHYADn pins set the PHY address.

Best regards
igor

[Poons]

Hello Igor,

Thanks for your inputs.

--------------------------------------------------------------------------------

DTS Configuration:

&fec2 {
pinctrl-0 = <&pinctrl_fec2_rmii>;
clocks = <&enet1_lpcg 4>,
<&enet1_lpcg 2>,
<&clk IMX_SC_R_ENET_1 IMX_SC_C_DISABLE_50>,
<&enet1_lpcg 0>,
<&enet1_lpcg 1>;
phy-mode = "rmii";
phy-handle = <&ethphy2>;
/delete-property/ phy-supply;

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

ethphy2: ethernet-phy@0 {
compatible = "ethernet-phy-ieee802.3-c22";
reg = <0>;
tja110x,refclk_in;
};
};
};

Log output:

[ 2.511308] fec 5b050000.ethernet: Invalid MAC address: 00:00:00:00:00:00
[ 2.518161] fec 5b050000.ethernet: Using random MAC address: 56:05:b7:06:72:1a
[ 2.526319] libphy: fec_enet_mii_bus: probed
[ 2.532189] fec 5b050000.ethernet eth0: registered PHC device 0

[ 7.465834] NXP TJA1100 5b050000.ethernet-1:00: attached PHY driver [NXP TJA1100] (mii_bus:phy_addr=5b050000.ethernet-1:00, irq=POLL)

root@imx8qxpc0mek:~# ifconfig
eth0 Link encap:Ethernet HWaddr 56:05:B7:06:72:1A
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:82 errors:0 dropped:0 overruns:0 frame:0
TX packets:82 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6220 (6.0 KiB) TX bytes:6220 (6.0 KiB)

---------------------------------------------------------------------------

1. "eth0"  interface is up from ifconfig command, kindly confirm.

2. How to test eth0 interface, (at present we have 1 imx8qxp CPU + 1 BB + 1 imx-rmii-brphy only). Do we need to buy any switch/connectors to test imx-rmii-brphy interface ethernet connectivity. If yes please provide the details.

Thanks in advance.

Thanks,

Poons.

[igorpadykov]

Hi Poons

one can try to use appropriate dts file

https://source.codeaurora.org/external/imx/linux-imx/tree/arch/arm64/boot/dts/freescale/imx8qxp-mek-...

NXP linux documentation:

https://www.nxp.com/design/software/embedded-software/i-mx-software/embedded-linux-for-i-mx-applicat...

Best regards
igor

[Poons]

Hello Igor,

Thank you for your reply.

As you suggested, I have used appropriate dts file (imx8qxp-mek-enet2-tja1100.dts file in kernel args), once Linux boots, there is no network interface available, also default eth0 is not working.

to make RMII working, are there any kernel configs to be enabled? if yes please provide the details.

Thank in advance.

Thanks,

Poons

[igorpadykov]

Hi Poons

kernel configuration is described in sect.4.4.5 Menu Configuration Options Linux Manual,

also one can recheck dts/dtb usage in Linux Guide included in 

Documentation

Best regards
igor