AnsweredAssumed Answered

Ethernet does not work on i.mx6 solo sabresd board.

Question asked by Hanseung Lee on Jan 5, 2017
Latest reply on Jan 12, 2017 by Carlos_Musich

Hi all.

I want to use kernel 4.1.15 BSP.

so i upgrade 3.0.35 LTIB -> 4.1.15 YOCTO  . It is success for mount on i.mx6 solo sabresd board.

But  do not run ping...

 

I was set below...

 

# ifconfig eth0 192.168.17.11 up   <== my sabresd board ip.

 

eth0      Link encap:Ethernet  HWaddr 5e:c9:69:76:94:b3
          inet addr:192.168.17.11  Bcast:192.168.17.255  Mask:255.255.255.0
          inet6 addr: fe80::5cc9:69ff:fe76:94b3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:678 errors:0 dropped:0 overruns:0 frame:0
          TX packets:493 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:88207 (86.1 KiB)  TX bytes:44150 (43.1 KiB)

 

It's OK.

 

BUT when input command below..

# ping 192.168.17.10 <== my pc ip.

PING 192.168.17.10 (192.168.17.10): 56 data bytes

 

it's then. stop.

 

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

compare i.mx6dl sabresd board. ( I have two board : i.mx6 solo sabresd board , i.mx6dl sabresd board)

Same kernel and files(rootfs , dts , zimage etc...) accept.

 

# ping 192.168.17.10 <== my pc ip.

 

64 bytes from 192.168.17.10: seq=0 ttl=64 time=1.724 ms
64 bytes from 192.168.17.10: seq=1 ttl=64 time=0.687 ms
64 bytes from 192.168.17.10: seq=2 ttl=64 time=0.586 ms
64 bytes from 192.168.17.10: seq=3 ttl=64 time=1.323 ms
64 bytes from 192.168.17.10: seq=4 ttl=64 time=0.453 ms

 

Oh.. my god.. it's run..!!

 

OTL...

Why does i.mx6dl sabresd work on the Ethernet ping?

I want to work on  i.mx6solo board ethernet ping....!!!

 

Why are the two machines operating differently?

 

If do you have soloution.. please share for me..

Outcomes