T1024 ehernet interface doesn't up

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

T1024 ehernet interface doesn't up

Jump to solution
462 Views
kriptonus
Contributor I

Hi everyone!

I've tried to compile an image for the t1024 based board. For the building I've used a Buildroot tools and fresh kernel 6.1.44. But ethernet interfaces doesn't up although

 

 ip a

 

show me a list of interfaces

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000                 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00                       
    inet 127.0.0.1/8 scope host lo                                              
       valid_lft forever preferred_lft forever                                  
    inet6 ::1/128 scope host                                                    
       valid_lft forever preferred_lft forever                                  
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000                    
    link/ether 00:00:00:00:01:00 brd ff:ff:ff:ff:ff:ff                          
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000                    
    link/ether 00:00:00:00:01:01 brd ff:ff:ff:ff:ff:ff                          
4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000                    
    link/ether 00:00:00:00:01:02 brd ff:ff:ff:ff:ff:ff                          
5: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000                    
    link/ether 00:00:00:00:01:03 brd ff:ff:ff:ff:ff:ff                          
6: tunl0@NONE: <NOARP> mtu 1480 qdisc noop qlen 1000                            
    link/ipip 0.0.0.0 brd 0.0.0.0                                               
7: sit0@NONE: <NOARP> mtu 1480 qdisc noop qlen 1000                             
    link/sit 0.0.0.0 brd 0.0.0.0

trying

 

ip link set dev eth0 up 

 

give me an error  

fsl_dpaa_mac ffe4e0000.ethernet eth0: init_phy() failed

During a boot log I can watch this:

mdio_bus 0x0000000ffe4fc000: MDIO device at address 2 is missing.               
mdio_bus 0x0000000ffe4fc000: MDIO device at address 6 is missing.               
mdio_bus 0x0000000ffe4fd000: MDIO device at address 1 is missing.               
mdio_bus 0x0000000ffe4fd000: MDIO device at address 2 is missing.               
platform ffe488000.port: Adding to iommu group 15                               
platform ffe489000.port: Adding to iommu group 16                               
platform ffe48a000.port: Adding to iommu group 17                               
platform ffe48b000.port: Adding to iommu group 18                               
fsl_dpaa_mac ffe4e0000.ethernet: FMan MEMAC                                     
fsl_dpaa_mac ffe4e0000.ethernet: FMan MAC address: 00:00:00:00:01:00            
fsl_dpaa_mac ffe4e2000.ethernet: FMan MEMAC                                     
fsl_dpaa_mac ffe4e2000.ethernet: FMan MAC address: 00:00:00:00:01:01            
fsl_dpaa_mac ffe4e4000.ethernet: FMan MEMAC                                     
fsl_dpaa_mac ffe4e4000.ethernet: FMan MAC address: 00:00:00:00:01:02            
fsl_dpaa_mac ffe4e6000.ethernet: FMan MEMAC                                     
fsl_dpaa_mac ffe4e6000.ethernet: FMan MAC address: 00:00:00:00:01:03            
fsl_dpaa_mac ffe4e0000.ethernet eth0: Probed interface eth0                     
fsl_dpaa_mac ffe4e2000.ethernet eth1: Probed interface eth1                     
fsl_dpaa_mac ffe4e4000.ethernet eth2: Probed interface eth2                     
fsl_dpaa_mac ffe4e6000.ethernet eth3: Probed interface eth3

Is it true that the MDIO is not configured correctly?  I use a device tree from kernel source, Uboot has been kept from previous image (kernel version 3.12.27). I've loaded a new rootfs, dtb and uImage into ram and ran from there.

ethtool show me the next:

 ethtool eth0                                                                  
Settings for eth0:                                                              
        Supported ports: [ ]                                                    
        Supported link modes:   Not reported                                    
        Supported pause frame use: No                                           
        Supports auto-negotiation: No                                           
        Supported FEC modes: Not reported                                       
        Advertised link modes:  Not reported                                    
        Advertised pause frame use: No                                          
        Advertised auto-negotiation: No                                         
        Advertised FEC modes: Not reported                                      
        Speed: Unknown!                                                         
        Duplex: Half                                                            
        Port: Twisted Pair                                                      
        PHYAD: 0                                                                
        Transceiver: internal                                                   
        Auto-negotiation: off                                                   
        MDI-X: Unknown                                                          
        Current message level: 0x00002037 (8247)                                
                               drv probe link ifdown ifup hw                    
        Link detected: no   

Is there some tricks to use ethernet on T1024?

I tried to compile new image from QorIQ SDK 2.0, but it has a very old tools and stopped with a lot of errors.

Labels (1)
Tags (3)
0 Kudos
Reply
1 Solution
420 Views
yipingwang
NXP TechSupport
NXP TechSupport

Please modify the dts file arch/powerpc/boot/dts/fsl/t1024rdb.dts according to your custom board. Please modify "reg" values to your real PHY addresses at mdio@fc000  and mdio@fd000.


fman@400000 {
enet0: ethernet@e0000 {
phy-handle = <&xg_aqr105_phy3>;
phy-connection-type = "xgmii";
sleep = <&rcpm 0x80000000>;
};

enet1: ethernet@e2000 {
sleep = <&rcpm 0x40000000>;
};

enet2: ethernet@e4000 {
phy-handle = <&rgmii_phy2>;
phy-connection-type = "rgmii";
sleep = <&rcpm 0x20000000>;
};

enet3: ethernet@e6000 {
phy-handle = <&rgmii_phy1>;
phy-connection-type = "rgmii";
sleep = <&rcpm 0x10000000>;
};

mdio0: mdio@fc000 {
rgmii_phy1: ethernet-phy@2 {
reg = <0x2>;
};
rgmii_phy2: ethernet-phy@6 {
reg = <0x6>;
};
};

xmdio0: mdio@fd000 {
xg_aqr105_phy3: ethernet-phy@1 {
compatible = "ethernet-phy-ieee802.3-c45";
reg = <0x1>;
};
sg_2500_aqr105_phy4: ethernet-phy@2 {
compatible = "ethernet-phy-ieee802.3-c45";
reg = <0x2>;
};
};
};

View solution in original post

0 Kudos
Reply
2 Replies
421 Views
yipingwang
NXP TechSupport
NXP TechSupport

Please modify the dts file arch/powerpc/boot/dts/fsl/t1024rdb.dts according to your custom board. Please modify "reg" values to your real PHY addresses at mdio@fc000  and mdio@fd000.


fman@400000 {
enet0: ethernet@e0000 {
phy-handle = <&xg_aqr105_phy3>;
phy-connection-type = "xgmii";
sleep = <&rcpm 0x80000000>;
};

enet1: ethernet@e2000 {
sleep = <&rcpm 0x40000000>;
};

enet2: ethernet@e4000 {
phy-handle = <&rgmii_phy2>;
phy-connection-type = "rgmii";
sleep = <&rcpm 0x20000000>;
};

enet3: ethernet@e6000 {
phy-handle = <&rgmii_phy1>;
phy-connection-type = "rgmii";
sleep = <&rcpm 0x10000000>;
};

mdio0: mdio@fc000 {
rgmii_phy1: ethernet-phy@2 {
reg = <0x2>;
};
rgmii_phy2: ethernet-phy@6 {
reg = <0x6>;
};
};

xmdio0: mdio@fd000 {
xg_aqr105_phy3: ethernet-phy@1 {
compatible = "ethernet-phy-ieee802.3-c45";
reg = <0x1>;
};
sg_2500_aqr105_phy4: ethernet-phy@2 {
compatible = "ethernet-phy-ieee802.3-c45";
reg = <0x2>;
};
};
};

0 Kudos
Reply
414 Views
kriptonus
Contributor I
Thanks a lot. I've solved the issue.
0 Kudos
Reply