This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

RTOS/AM5728: Ping with packet size above 1472 fails

Part Number: AM5728


Tool/software: TI-RTOS

Hi there,

I'm using AM5728 IDK, SDK version is 5.03.

and testing NIMU_BasicExample_idkAM572x_armExampleproject

When I ping the board with packet size of 1472 bytes I get a good response.

$ ping 192.168.1.4 -s 1472 -c 1
PING 192.168.1.4 (192.168.1.4) 1472(1500) bytes of data.
1480 bytes from 192.168.1.4: icmp_seq=1 ttl=255 time=0.179 ms

--- 192.168.1.4 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.179/0.179/0.179/0.000 ms
$

$ sudo tcpdump -i enp2s0 icmp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on enp2s0, link-type EN10MB (Ethernet), capture size 262144 bytes
09:12:18.931858 IP 192.168.1.5 > 192.168.1.4: ICMP echo request, id 7384, seq 1, length 1480
09:12:18.932000 IP 192.168.1.4 > 192.168.1.5: ICMP echo reply, id 7384, seq 1, length 1480

When trying packet size > 1472 I don't see anything coming back from RTOS.

$ ping 192.168.1.4 -s 1473 -c 1
PING 192.168.1.4 (192.168.1.4) 1473(1501) bytes of data.

--- 192.168.1.4 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

$

$ sudo tcpdump -i enp2s0 icmp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on enp2s0, link-type EN10MB (Ethernet), capture size 262144 bytes
09:14:30.802962 IP 192.168.1.5 > 192.168.1.4: ICMP echo request, id 7525, seq 1, length 1480
09:14:30.802983 IP 192.168.1.5 > 192.168.1.4: icmp

According to tcpdump output the large packet is fragmented and sent over two frames, but RTOS doesn't seem to respond.

Any suggestions?

Thanks,

Nir.

  • Hi,

    I tested pdk_am57xx_1_0_14\packages\MyExampleProjects\NIMU_BasicExample_idkAM572x_armExampleproject, with various ping size up to 2000 bytes, I saw when ping >1472 bytes, the packets are segmented in both directions, as the PC host has a MTU size setting of 1500. This is no issue for AM572x to respond.

    192.168.1.11 is my Windows PC

    192.168.1.4 is the AM572x IDK EVM

    Also wireshark:

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/ping_5F00_am572x.pcapng

    Regards, Eric

  • Yep.

    I screwed up the NDK stack. After fixing it, ping is working properly.

    My bad. sorry

    Nir.