ping command packet loss

sandeep_c — Tue, 04 Apr 2023 12:43:41 GMT

hi everyone iam developing the driver for ksz 8851snli by using lwip stack which spi to ethernet and vice versa

IDE DETAILS:

i.MX RT1170 First GHz Crossover MCU with Arm® Cortex®-M7 and Cortex-M4 Cores

MCUXpresso IDE v11.6.0 [Build 8187] [2022-07-13]

problem:

iam trying ping between pc to mc and vice versa during this time i will get all for responses and sometimes i will loss 3 or 2 or 1 packets or all packets please refer the document .

i havent found at what frequency clock will generated by the laptop (pc) for request or reply

what are the procedure or how can i solve this issue i need some insight from the community.

my processor clock configured as 500khz

Microsoft Windows [Version 10.0.19045.2728]
(c) Microsoft Corporation. All rights reserved.
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Reply from 192.168.0.100: Destination host unreachable.
Reply from 192.168.0.100: Destination host unreachable.
Reply from 192.168.0.100: Destination host unreachable.
Reply from 192.168.0.100: Destination host unreachable.
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Reply from 192.168.0.100: Destination host unreachable.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 192.168.0.102: bytes=32 - MISCOMPARE at offset 30 - time=1746ms TTL=255
Request timed out.
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 1746ms, Maximum = 1746ms, Average = 1746ms
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.102: bytes=32 - MISCOMPARE at offset 30 - time=2574ms TTL=255
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 2574ms, Maximum = 2574ms, Average = 2574ms
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Reply from 192.168.0.102: bytes=32 - MISCOMPARE at offset 30 - time=2773ms TTL=255
Request timed out.
Request timed out.
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 2773ms, Maximum = 2773ms, Average = 2773ms
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.100: Destination host unreachable.
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Reply from 192.168.0.100: Destination host unreachable.
Request timed out.
Reply from 192.168.0.100: Destination host unreachable.
Request timed out.
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Reply from 192.168.0.100: Destination host unreachable.
Request timed out.
Reply from 192.168.0.100: Destination host unreachable.
Request timed out.
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
General failure.
Reply from 192.168.0.100: Destination host unreachable.
Reply from 192.168.0.102: bytes=32 - MISCOMPARE at offset 30 - time=2039ms TTL=255
Reply from 192.168.0.102: bytes=32 - MISCOMPARE at offset 30 - time=2056ms TTL=255
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 2039ms, Maximum = 2056ms, Average = 2047ms
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Reply from 192.168.0.102: bytes=32 - MISCOMPARE at offset 30 - time=919ms TTL=255
Reply from 192.168.0.102: bytes=32 - MISCOMPARE at offset 30 - time=1229ms TTL=255
Reply from 192.168.0.102: bytes=32 - MISCOMPARE at offset 30 - time=1783ms TTL=255
Reply from 192.168.0.102: bytes=32 - MISCOMPARE at offset 30 - time=3489ms TTL=255
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 919ms, Maximum = 3489ms, Average = 1855ms
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 192.168.0.102: bytes=32 - MISCOMPARE at offset 30 - time=869ms TTL=255
Reply from 192.168.0.102: bytes=32 - MISCOMPARE at offset 30 - time=1410ms TTL=255
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 869ms, Maximum = 1410ms, Average = 1139ms
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.102: bytes=32 - MISCOMPARE at offset 30 - time=2085ms TTL=255
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 2085ms, Maximum = 2085ms, Average = 2085ms
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Reply from 192.168.0.102: bytes=32 - MISCOMPARE at offset 30 - time=1253ms TTL=255
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 1253ms, Maximum = 1253ms, Average = 1253ms
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 192.168.0.100: Destination host unreachable.
Request timed out.
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Reply from 192.168.0.102: bytes=32 - MISCOMPARE at offset 30 - time=811ms TTL=255
Reply from 192.168.0.102: bytes=32 - MISCOMPARE at offset 30 - time=1160ms TTL=255
Request timed out.
Request timed out.
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 811ms, Maximum = 1160ms, Average = 985ms
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Reply from 192.168.0.102: bytes=32 - MISCOMPARE at offset 30 - time=3658ms TTL=255
Request timed out.
Request timed out.
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 3658ms, Maximum = 3658ms, Average = 3658ms
C:\Users\admin>ping 192.168.0.102
Pinging 192.168.0.102 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.102:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

@Ethernet @tcp_ipstack @EthernetHelp @ethernet1

thank you

Re: ping command packet loss

jingpan — Thu, 13 Apr 2023 02:31:14 GMT

Hi @sandeep_c ,

It seems there is either software problem or hardware problem. The link is not established at all.

Regards,

Jing

i.MX ProcessorsのトピックRe: ping command packet loss

ping command packet loss

Re: ping command packet loss