How to enable ethernet(dhcp) on lx2160

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

How to enable ethernet(dhcp) on lx2160

ソリューションへジャンプ
2,156件の閲覧回数
m_kei
Contributor III

I am booting TinyLinux using SD boot with lx2160ardb_rev2.

However, eth0 cannot be enabled on this Linux.
"ifconfig -a" shows only "lo" and "sit0" (disabled at startup).
Since u-boot is able to do ethernet communication, I am assuming that Linux either does not have a driver or needs to be configured in some way.

What do you need?

0 件の賞賛
返信
1 解決策
2,134件の閲覧回数
yipingwang
NXP TechSupport
NXP TechSupport

Please apply DPL file before booting up Linux.

=> sf read 0x80d00000 0xd00000 0x100000
device 0 offset 0xd00000, size 0x100000
SF: 1048576 bytes @ 0xd00000 Read: OK
=> fsl_mc lazyapply dpl 0x80d00000
=> tftp 0xa0000000 b25805/lx2160/lsdk2108_yocto_tiny_LS_arm64.itb

=> bootm 0xa0000000#lx2160ardb

Please refer to the following log in Linux.

root@TinyLinux:~# ifconfig -a
eth0: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 68:05:ca:2b:3c:0c txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 120 memory 0x90400c0000-90400e0000

eth1: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 00:04:9f:05:84:45 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth2: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 00:04:9f:05:84:4a txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

sit0: flags=128<NOARP> mtu 1480
unspec 00-00-00-00-30-30-3A-30-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

root@TinyLinux:~# ls-listni
dprc.1/dpni.1 (interface: eth1, end point: dpmac.2)
dprc.1/dpni.0 (interface: eth2, end point: dpmac.17)
root@TinyLinux:~# ls-addni dpmac.18
[ 219.093029] fsl_mc_allocator dpbp.2: Adding to iommu group 10
[ 219.102597] fsl_mc_allocator dpmcp.36: Adding to iommu group 10
[ 219.111525] fsl_mc_allocator dpcon.47: Adding to iommu group 10
[ 219.119372] fsl_mc_allocator dpcon.46: Adding to iommu group 10
[ 219.127559] fsl_mc_allocator dpcon.45: Adding to iommu group 10
[ 219.135393] fsl_mc_allocator dpcon.44: Adding to iommu group 10
[ 219.144783] fsl_mc_allocator dpcon.43: Adding to iommu group 10
[ 219.152562] fsl_mc_allocator dpcon.42: Adding to iommu group 10
[ 219.160303] fsl_mc_allocator dpcon.41: Adding to iommu group 10
[ 219.167410] fsl_mc_allocator dpcon.40: Adding to iommu group 10
[ 219.175401] fsl_mc_allocator dpcon.39: Adding to iommu group 10
[ 219.184652] fsl_mc_allocator dpcon.38: Adding to iommu group 10
[ 219.191523] fsl_mc_allocator dpcon.37: Adding to iommu group 10
[ 219.199572] fsl_mc_allocator dpcon.36: Adding to iommu group 10
[ 219.208956] fsl_mc_allocator dpcon.35: Adding to iommu group 10
[ 219.216667] fsl_mc_allocator dpcon.34: Adding to iommu group 10
[ 219.224454] fsl_mc_allocator dpcon.33: Adding to iommu group 10
[ 219.231414] fsl_mc_allocator dpcon.32: Adding to iommu group 10
[ 219.239983] fsl_dpaa2_eth dpni.2: Adding to iommu group 10
Created interface: eth3 (object:dpni.2, endpoint: dpmac.18)
root@TinyLinux:~#

元の投稿で解決策を見る

0 件の賞賛
返信
3 返答(返信)
2,135件の閲覧回数
yipingwang
NXP TechSupport
NXP TechSupport

Please apply DPL file before booting up Linux.

=> sf read 0x80d00000 0xd00000 0x100000
device 0 offset 0xd00000, size 0x100000
SF: 1048576 bytes @ 0xd00000 Read: OK
=> fsl_mc lazyapply dpl 0x80d00000
=> tftp 0xa0000000 b25805/lx2160/lsdk2108_yocto_tiny_LS_arm64.itb

=> bootm 0xa0000000#lx2160ardb

Please refer to the following log in Linux.

root@TinyLinux:~# ifconfig -a
eth0: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 68:05:ca:2b:3c:0c txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 120 memory 0x90400c0000-90400e0000

eth1: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 00:04:9f:05:84:45 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth2: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 00:04:9f:05:84:4a txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

sit0: flags=128<NOARP> mtu 1480
unspec 00-00-00-00-30-30-3A-30-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

root@TinyLinux:~# ls-listni
dprc.1/dpni.1 (interface: eth1, end point: dpmac.2)
dprc.1/dpni.0 (interface: eth2, end point: dpmac.17)
root@TinyLinux:~# ls-addni dpmac.18
[ 219.093029] fsl_mc_allocator dpbp.2: Adding to iommu group 10
[ 219.102597] fsl_mc_allocator dpmcp.36: Adding to iommu group 10
[ 219.111525] fsl_mc_allocator dpcon.47: Adding to iommu group 10
[ 219.119372] fsl_mc_allocator dpcon.46: Adding to iommu group 10
[ 219.127559] fsl_mc_allocator dpcon.45: Adding to iommu group 10
[ 219.135393] fsl_mc_allocator dpcon.44: Adding to iommu group 10
[ 219.144783] fsl_mc_allocator dpcon.43: Adding to iommu group 10
[ 219.152562] fsl_mc_allocator dpcon.42: Adding to iommu group 10
[ 219.160303] fsl_mc_allocator dpcon.41: Adding to iommu group 10
[ 219.167410] fsl_mc_allocator dpcon.40: Adding to iommu group 10
[ 219.175401] fsl_mc_allocator dpcon.39: Adding to iommu group 10
[ 219.184652] fsl_mc_allocator dpcon.38: Adding to iommu group 10
[ 219.191523] fsl_mc_allocator dpcon.37: Adding to iommu group 10
[ 219.199572] fsl_mc_allocator dpcon.36: Adding to iommu group 10
[ 219.208956] fsl_mc_allocator dpcon.35: Adding to iommu group 10
[ 219.216667] fsl_mc_allocator dpcon.34: Adding to iommu group 10
[ 219.224454] fsl_mc_allocator dpcon.33: Adding to iommu group 10
[ 219.231414] fsl_mc_allocator dpcon.32: Adding to iommu group 10
[ 219.239983] fsl_dpaa2_eth dpni.2: Adding to iommu group 10
Created interface: eth3 (object:dpni.2, endpoint: dpmac.18)
root@TinyLinux:~#

0 件の賞賛
返信
2,146件の閲覧回数
m_kei
Contributor III

As a follow-up report, when I connected an intel LAN card on hand to PCIe as a test, the LAN card was recognized as eth0 and worked fine with DHCP.

However, I still need an answer because it has to be the Ethernet port on the lx2160 board.

0 件の賞賛
返信
2,154件の閲覧回数
m_kei
Contributor III

I forgot to mention that I am using LSDK-21.08 mkfw installed using flex-installer.

0 件の賞賛
返信