Hi ,
I have enabled ethernet in my custon imx6ull based board using 4.9.11 imx linux kernel and the ethernet was working fine. Below are the dtb changes
&fec1 {
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_enet1>;
phy-mode = "rmii";
phy-handle = <ðphy0>;
status = "okay";
//phy-reset-gpios = <&gpio2 14 GPIO_ACTIVE_LOW>;
//phy-reset-duration = <1>;
mdio {
#address-cells = <1>;
#size-cells = <0>;
ethphy0: ethernet-phy@2 {
compatible = "ethernet-phy-ieee802.3-c22";
reg = <2>;
clocks = <&clks IMX6UL_CLK_ENET_REF>;
clocknames = "rmii-ref";
};
};
};
pinctrl_enet1: enet1grp {
fsl,pins = <
MX6UL_PAD_ENET1_TX_DATA0__ENET1_TDATA00 0x120b0
MX6UL_PAD_ENET1_TX_DATA1__ENET1_TDATA01 0x120b0
MX6UL_PAD_ENET1_TX_EN__ENET1_TX_EN 0x120b0
MX6UL_PAD_ENET1_TX_CLK__ENET1_REF_CLK1 0x4001b031
MX6UL_PAD_ENET1_RX_DATA0__ENET1_RDATA00 0x120b0
MX6UL_PAD_ENET1_RX_DATA1__ENET1_RDATA01 0x120b0
MX6UL_PAD_ENET1_RX_EN__ENET1_RX_EN 0x120b0
MX6UL_PAD_ENET1_RX_ER__ENET1_RX_ER 0x120b0
MX6UL_PAD_ENET2_TX_CLK__GPIO2_IO14 0x120b0
MX6UL_PAD_ENET2_RX_DATA0__ENET1_MDIO 0x120b0
MX6UL_PAD_ENET2_RX_DATA1__ENET1_MDC 0x120b0
MX6UL_PAD_ENET2_RX_ER__GPIO2_IO15 0x120b0
>;
};
But now when i port these changes to imx 4.14.98 kernel, i get error in probing like below:
fec 2188000.ethernet: fec clock (0) too fast to get right mii speed
fec: probe of 2188000.ethernet failed with error -22
Please help. igorpadykov kunal.kotecha@volansystech.com
Thanks,
Pankaj Joshi
Hi Pankaj
if it is working on L4.9.11 kernel, one can run two boards: good and not good
and dump enet related registers: in particular IOMUXC_GPR_GPR1, check
enet clock with oscilloscope. Pay attention to CCM_ANALOG_PLL_ENETn, CCM_CCGR0
registers.
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
in general yes, each linux version should be aligned with uboot version,
for example Uboot v2018.03 <--> Linux L4.14.98_2.1.0:
I migrated to the suggested u-boot verison. Patched everything for my board, but now i am getting major issue of not able to boot from mmc. with my old patches on 4.9.11 mcc used to work great
MMC:
Loading Environment from MMC... MMC Device 1 not found
Any idea how i can debug this.
Thanks,
Pankaj Joshi
Do you think it may be a problem of old version of uboot. What can be the reason for that. If absolutely required I will update bootloader as well
Does it has anything to do with Kernel version upgrade. Ideally the internal MAC clock frequency shall remain same. shouldn't it?