P4080ds cannot find eth0 interface

cancel
Showing results for 
Search instead for 
Did you mean: 

P4080ds cannot find eth0 interface

Jump to solution
450 Views
peterzheng
Contributor II

Hello,

I am trying to set up the DHCP ethernet connection of my p4080ds board. I am using the core image. I use a switch to connect host system and my board.

After boot up, the board alerts the following message:

WARNING: adjusting available memory to 30000000                                
Wrong Image Format for bootm command                                           
ERROR: can't get kernel image!

So I use "pix altbank" to boot up in alternative bank. After I enter the system, I type ifconfig. But it seems there is no eth0 interface.

root@p4080ds:~# ifconfig -a
fm1-10g   Link encap:Ethernet  HWaddr 00:e0:0c:00:d7:04 
          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)
          Memory:fe4f0000-fe4f0fff

fm1-gb1   Link encap:Ethernet  HWaddr 00:e0:0c:00:d7:01 
          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)
          Memory:fe4e2000-fe4e2fff

fm2-10g   Link encap:Ethernet  HWaddr 00:e0:0c:00:d7:09 
          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)                              
          Memory:fe5f0000-fe5f0fff                                            
                                                                              
fm2-gb2   Link encap:Ethernet  HWaddr 00:e0:0c:00:d7:07                       
          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)                              
          Memory:fe5e4000-fe5e4fff                                            
                                                                              
fm2-gb3   Link encap:Ethernet  HWaddr 00:e0:0c:00:d7:08                       
          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)                              
          Memory:fe5e6000-fe5e6fff                                            
                                                                              
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:16436  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:0                                           
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)                              
                                                                              
sit0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-
          NOARP  MTU:1480  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:0                                           
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)                              
                                                                              
tunl0     Link encap:IPIP Tunnel  HWaddr                                      
          NOARP  MTU:1480  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:0                                           
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


How can I solve this? Thanks, have a great day!

Regards,

Peter Zheng

Labels (1)
Tags (2)
0 Kudos
1 Solution
139 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello Peter,

Please refer to "3.2.23.2.3.1.4 SerDes Protocol 0xe, P4080 Rev 2, Total Capacity 23 Gbps" in SDK document, please check whether the physical network connection is correct, then configure IP address for "fm*-gb*".

Thanks,

Yiping

View solution in original post

0 Kudos
4 Replies
139 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello Peter,

On P4080DS Linux System, Ethernet ports on PCIe Network interface (XAUI) card are name as eth* interface.

Thanks,

Yiping

139 Views
peterzheng
Contributor II

Hi Yiping,

Do you know how could I set up the internet to make P4080DS connect to internet?

Regards,

Peter

0 Kudos
140 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello Peter,

Please refer to "3.2.23.2.3.1.4 SerDes Protocol 0xe, P4080 Rev 2, Total Capacity 23 Gbps" in SDK document, please check whether the physical network connection is correct, then configure IP address for "fm*-gb*".

Thanks,

Yiping

View solution in original post

0 Kudos
139 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello Peter,

On DPAA(including P4080DS) target board, we don't use eth* naming convention, we use fm*-gb* in Linux Kernel instead, which means the ethernet ports connecting to FMAN, please refer to the following port mapping for the RCW which you are use on this bank.

U-boot                Port i        Linux FMAN Address

FM1@DTSEC2    fm1-gb1      0xffe4e2000

FM1@TGEC1      fm1-10g      0xffe4f0000

FM2@DTSEC3    fm2-gb2      0xffe5e4000

FM2@DTSEC4    fm2-gb3      0xffe5e6000

FM2@TGEC1      fm2-10g      0xffe5f0000

You could get detailed information in p4080ds.dts,

fman0: fman@400000 {

              ... ...

              enet1: ethernet@e2000 {

                                tbi-handle = <&tbi1>;

                                phy-handle = <&phy1>;

                                phy-connection-type = "sgmii";

                };

              ... ...

              enet4: ethernet@f0000 {

                                phy-handle = <&phy10>;

                                phy-connection-type = "xgmii";

              };

}

        

fman1: fman@500000 {

                        ... ...

                                enet7: ethernet@e4000 {

                                tbi-handle = <&tbi7>;

                                phy-handle = <&phy7>;

                                phy-connection-type = "sgmii";

                                };

                 enet8:ethernet@e6000 {
                           tbi-handle = <&tbi8>;
                           phy-handle = <&phy8>;
                           phy-connection-type = "sgmii";
                   };

                   enet9: ethernet@f0000 {
                           phy-handle = <&phy11>;
                           phy-connection-type = "xgmii";
                  

};

}


Have a great day,
Yiping

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