AM4376: Ping Loss or Ping response timeout happening while pinging the device from the laptop.

Gaurav More

Part Number: AM4376

Tool/software:

Hello All,

We are using AM4376 processor for one of our product development. We are using processor SDK 8.02 with RT Linux version . we have developed the application with out custom board and found issue of ping losses while pinging the device from the laptop.

Initially we thought that it is due to our application of Bridge STP which we are using currently in our application, Although testing is still going on. But When we simply load u-boot, MLO , kernel and file system and then after booting the system we got the command prompt.

Then we assigned IP address to eth0 port. Not we are not running application, so there is no bridge right now. then while pinging we found ping timeout and ARP malformed packet . what could be the reason for the same?

I have attached the logs for reference. due to this issue our production level testing is halted. So please consider this as a higher priority.

7245.capture.zip

unzip the file and check for the Wireshark capture for the malformed packets. Also find the kernel configuration file used for our development.

. tisdk_am437x-evm-rt_defconfig.zip

this is on very high priority.. Please provide inputs regarding the same. This issue has stopped our final testing as well.

Thanks

Gaurav More

over 1 year ago

0 Paula Carrillo over 1 year ago

TI__Mastermind 38820 points

Hi Gaurav, I will loop our Linux experts. In the meantime, let me ask you few questions.

- Is this CPSW right? can you add Board console logs?

- Are you testing in a direct connection between laptop and Board?

- Which PHY are you using in your board design? wondering if there is any timing issue and if using a scope to probe PHY signals is an option

thank you,

Paula

0 Gaurav More over 1 year ago in reply to Paula Carrillo

Intellectual 340 points

Hello Paula,

Thanks for the quick response.

Is this CPSW right? can you add Board console logs?

-- No We are using PRU ICSS. Regarding the Logs what is expected? boot logs?

Are you testing in a direct connection between laptop and Board?

-- Yes

Which PHY are you using in your board design?

-- PHY Part no: DP83822HFRHBT

Thanks

Gaurav More

0 Schuyler Patton over 1 year ago in reply to Gaurav More

TI__Mastermind 40080 points

Hi,

Please provide a topology diagram of the subnet that the wireshark capture is from. There are a lot of malformed packets but we are not able to see the where the AM437 is network, is it the one issuing malformed packets for example.

What does ethtool -S <interface name> show? Seeing malformed packets I am expecting to see for CRC.

The console logs Paula is asking is we would like to serial console log that shows the ping command being run.

Best Regards,

Schuyler

0 Gaurav More 11 months ago in reply to Schuyler Patton

Intellectual 340 points

Hello Schuyler,

Thanks for the quick response,

I have connected my laptop to the AM4376 device which is our custom board . Please find the connection diagram for your reference.

Laptop Configuration : Custom Board Configuration

ethtool -S eth0

root@am437x-evm:~# ethtool -S eth0 
NIC statistics:
     txBcast: 1
     txMcast: 29
     txUcast: 323
     txOctets: 29230
     rxBcast: 9
     rxMcast: 31
     rxUcast: 325
     rxOctets: 26299
     tx64byte: 22
     tx65_127byte: 319
     tx128_255byte: 9
     tx256_511byte: 3
     tx512_1023byte: 0
     tx1024byte: 0
     rx64byte: 58
     rx65_127byte: 306
     rx128_255byte: 0
     rx256_511byte: 1
     rx512_1023byte: 0
     rx1024byte: 0
     lateColl: 0
     singleColl: 0
     multiColl: 0
     excessColl: 0
     rxMisAlignmentFrames: 0
     stormPrevCounterBC: 0
     stormPrevCounterMC: 0
     stormPrevCounterUC: 0
     macRxError: 0
     SFDError: 0
     defTx: 0
     macTxError: 0
     rxOverSizedFrames: 0
     rxUnderSizedFrames: 0
     rxCRCFrames: 0
     droppedPackets: 0
     txHWQOverFlow: 0
     txHWQUnderFlow: 0
     vlanDropped: 0
     multicastDropped: 27

TCP dump for your reference:

root@am437x-evm:~#  tcpdump 
[  951.347215] Bluetooth: Core ver 2.22
[  951.358868] NET: Registered protocol family 31
[  951.358905] Bluetooth: HCI device and connection manager initialized
[  951.358958] Bluetooth: HCI socket layer initialized
[  951.358983] Bluetooth: L2CAP socket layer initialized
[  951.359059] Bluetooth: SCO socket layer initialized
[  951.457705] device eth0 entered promiscuous mode
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
09:57:05.840439 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 436, length 40
09:57:05.840643 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 436, length 40
09:57:06.852225 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 437, length 40
09:57:06.852431 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 437, length 40
09:57:07.868567 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 438, length 40
09:57:07.868746 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 438, length 40
09:57:08.872343 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 439, length 40
09:57:08.872583 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 439, length 40
09:57:09.890300 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 440, length 40
09:57:09.890494 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 440, length 40
09:57:10.896575 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 441, length 40
09:57:10.896749 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 441, length 40
09:57:11.903099 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 442, length 40
09:57:11.903282 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 442, length 40
09:57:12.922671 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 443, length 40
09:57:12.922864 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 443, length 40
09:57:13.938400 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 444, length 40
09:57:13.938576 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 444, length 40
09:57:14.955530 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 445, length 40
09:57:14.955697 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 445, length 40
09:57:15.974484 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 446, length 40
09:57:15.974677 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 446, length 40
09:57:16.988333 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 447, length 40
09:57:16.988518 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 447, length 40
09:57:18.001886 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 448, length 40
09:57:18.002063 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 448, length 40
09:57:19.014389 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 449, length 40
09:57:19.014585 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 449, length 40
09:57:19.806606 ARP, Request who-has am437x-evm (68:5e:1c:0a:bc:90 (oui Unknown)) tell 192.168.2.245, length 46
09:57:19.806728 ARP, Reply am437x-evm is-at 68:5e:1c:0a:bc:90 (oui Unknown), length 28
09:57:20.028405 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 450, length 40
09:57:20.028592 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 450, length 40
09:57:21.033253 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 451, length 40
09:57:21.033425 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 451, length 40
09:57:22.039036 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 452, length 40
09:57:22.039229 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 452, length 40
09:57:23.045112 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 453, length 40
09:57:23.045291 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 453, length 40
09:57:24.061261 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 454, length 40
09:57:24.061435 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 454, length 40
09:57:25.076400 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 455, length 40
09:57:25.076594 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 455, length 40
09:57:26.094540 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 456, length 40
09:57:26.094718 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 456, length 40
09:57:27.111949 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 457, length 40
09:57:27.112132 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 457, length 40
09:57:28.125327 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 458, length 40
09:57:28.125521 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 458, length 40
09:57:29.138572 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 459, length 40
09:57:29.138745 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 459, length 40
09:57:30.142901 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 460, length 40
09:57:30.143060 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 460, length 40
09:57:31.157887 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 461, length 40
09:57:31.158082 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 461, length 40
09:57:32.164855 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 462, length 40
09:57:32.165041 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 462, length 40
09:57:33.170497 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 463, length 40
09:57:33.170680 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 463, length 40
09:57:34.186748 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 464, length 40
09:57:34.186940 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 464, length 40
09:57:35.191897 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 465, length 40
09:57:35.192064 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 465, length 40
09:57:36.208700 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 466, length 40
09:57:36.208866 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 466, length 40
09:57:37.226019 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 467, length 40
09:57:37.226224 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 467, length 40
09:57:38.243676 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 468, length 40
09:57:38.243856 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 468, length 40
09:57:39.246992 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 469, length 40
09:57:39.247167 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 469, length 40
09:57:40.252024 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 470, length 40
09:57:40.252223 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 470, length 40
09:57:41.268442 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 471, length 40
09:57:41.268615 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 471, length 40
09:57:42.242648 ARP, Request who-has 192.168.2.245 tell am437x-evm, length 28
09:57:42.243164 ARP, Reply 192.168.2.245 is-at 8c:8c:aa:61:53:57 (oui Unknown), length 46
09:57:42.274388 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 472, length 40
09:57:42.274571 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 472, length 40
09:57:43.289499 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 473, length 40
09:57:43.289695 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 473, length 40
09:57:44.298902 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 474, length 40
09:57:44.299074 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 474, length 40
09:57:45.311373 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 475, length 40
09:57:45.311539 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 475, length 40
09:57:46.322300 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 476, length 40
09:57:46.322495 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 476, length 40
09:57:47.338153 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 477, length 40
09:57:47.338338 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 477, length 40
09:57:48.346929 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 478, length 40
09:57:48.347102 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 478, length 40
09:57:49.363382 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 479, length 40
09:57:49.363578 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 479, length 40
09:57:50.374165 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 480, length 40
09:57:50.374339 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 480, length 40
09:57:51.384222 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 481, length 40
09:57:51.384386 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 481, length 40
09:57:52.300763 ARP, Request who-has am437x-evm (68:5e:1c:0a:bc:90 (oui Unknown)) tell 192.168.2.245, length 46
09:57:52.300895 ARP, Reply am437x-evm is-at 68:5e:1c:0a:bc:90 (oui Unknown), length 28
09:57:52.393065 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 482, length 40
09:57:52.393234 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 482, length 40
09:57:53.412056 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 483, length 40
09:57:53.412248 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 483, length 40
09:57:54.427617 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 484, length 40
09:57:54.427784 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 484, length 40
09:57:55.442055 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 485, length 40
09:57:55.442250 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 485, length 40
09:57:56.450294 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 486, length 40
09:57:56.450464 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 486, length 40
09:57:57.462755 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 487, length 40
09:57:57.462943 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 487, length 40
09:57:58.473374 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 488, length 40
09:57:58.473569 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 488, length 40
09:57:59.491570 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 489, length 40
09:57:59.491743 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 489, length 40
09:58:00.503455 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 490, length 40
09:58:00.503615 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 490, length 40
09:58:01.516647 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 491, length 40
09:58:01.516853 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 491, length 40
09:58:02.527572 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 492, length 40
09:58:02.527755 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 492, length 40
09:58:03.546667 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 493, length 40
09:58:03.546851 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 493, length 40
09:58:04.561597 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 494, length 40
09:58:04.561791 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 494, length 40
09:58:05.579977 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 495, length 40
09:58:05.580145 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 495, length 40
09:58:06.597209 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 496, length 40
09:58:06.597405 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 496, length 40
09:58:07.608350 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 497, length 40
09:58:07.608544 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 497, length 40
09:58:08.621475 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 498, length 40
09:58:08.621657 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 498, length 40
09:58:09.635274 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 499, length 40
09:58:09.635446 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 499, length 40
09:58:10.651399 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 500, length 40
09:58:10.651597 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 500, length 40
09:58:11.664035 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 501, length 40
09:58:11.664205 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 501, length 40
09:58:12.680564 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 502, length 40
09:58:12.680751 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 502, length 40
09:58:13.697083 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 503, length 40
09:58:13.697276 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 503, length 40
09:58:14.711304 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 504, length 40
09:58:14.711477 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 504, length 40
09:58:15.727025 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 505, length 40
09:58:15.727191 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 505, length 40
09:58:16.739243 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 506, length 40
09:58:16.739438 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 506, length 40
09:58:17.756313 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 507, length 40
09:58:17.756487 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 507, length 40
09:58:18.767383 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 508, length 40
09:58:18.767590 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 508, length 40
09:58:19.778439 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 509, length 40
09:58:19.778638 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 509, length 40
09:58:20.794686 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 510, length 40
09:58:20.794856 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 510, length 40
09:58:21.814938 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 511, length 40
09:58:21.815124 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 511, length 40
09:58:22.820128 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 512, length 40
09:58:22.820309 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 512, length 40
09:58:23.824344 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 513, length 40
09:58:23.824517 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 513, length 40
09:58:23.842639 ARP, Request who-has 192.168.2.245 tell am437x-evm, length 28
09:58:23.843129 ARP, Reply 192.168.2.245 is-at 8c:8c:aa:61:53:57 (oui Unknown), length 46
09:58:24.831638 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 514, length 40
09:58:24.831823 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 514, length 40
09:58:25.306770 ARP, Request who-has am437x-evm (68:5e:1c:0a:bc:90 (oui Unknown)) tell 192.168.2.245, length 46
09:58:25.306900 ARP, Reply am437x-evm is-at 68:5e:1c:0a:bc:90 (oui Unknown), length 28
09:58:25.836597 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 515, length 40
09:58:25.836783 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 515, length 40
09:58:26.852603 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 516, length 40
09:58:26.852787 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 516, length 40
09:58:27.867413 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 517, length 40
09:58:27.867613 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 517, length 40
09:58:28.874983 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 518, length 40
09:58:28.875166 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 518, length 40
09:58:29.881066 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 519, length 40
09:58:29.881233 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 519, length 40
09:58:30.890792 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 520, length 40
09:58:30.890984 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 520, length 40
09:58:31.908165 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 521, length 40
09:58:31.908355 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 521, length 40
09:58:32.913901 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 522, length 40
09:58:32.914076 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 522, length 40
09:58:33.933014 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 523, length 40
09:58:33.933211 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 523, length 40
09:58:34.948572 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 524, length 40
09:58:34.948749 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 524, length 40
09:58:35.953935 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 525, length 40
09:58:35.954103 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 525, length 40
09:58:36.969936 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 526, length 40
09:58:36.970132 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 526, length 40
09:58:37.974418 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 527, length 40
09:58:37.974595 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 527, length 40
09:58:38.992092 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 528, length 40
09:58:38.992261 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 528, length 40
09:58:39.999886 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 529, length 40
09:58:40.000080 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 529, length 40
09:58:41.005834 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 530, length 40
09:58:41.006004 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 530, length 40
^[[B09:58:42.023800 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 531, length 40
09:58:42.023983 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 531, length 40
09:58:43.040410 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 532, length 40
09:58:43.040603 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 532, length 40
09:58:44.045547 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 533, length 40
09:58:44.045722 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 533, length 40
09:58:45.052645 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 534, length 40
09:58:45.052807 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 534, length 40
09:58:46.068893 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 535, length 40
09:58:46.069085 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 535, length 40
09:58:47.075256 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 536, length 40
09:58:47.075457 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 536, length 40
09:58:48.090516 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 537, length 40
09:58:48.090692 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 537, length 40
09:58:49.104311 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 538, length 40
09:58:49.104506 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 538, length 40
09:58:50.121571 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 539, length 40
09:58:50.121744 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 539, length 40
09:58:51.126248 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 540, length 40
09:58:51.126412 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 540, length 40
09:58:52.130415 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 541, length 40
09:58:52.130609 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 541, length 40
09:58:53.147791 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 542, length 40
09:58:53.147972 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 542, length 40
09:58:54.159150 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 543, length 40
09:58:54.159336 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 543, length 40
09:58:55.165287 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 544, length 40
09:58:55.165483 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 544, length 40
09:58:56.179647 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 545, length 40
09:58:56.179827 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 545, length 40
09:58:57.197208 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 546, length 40
09:58:57.197394 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 546, length 40
09:58:57.804854 ARP, Request who-has am437x-evm (68:5e:1c:0a:bc:90 (oui Unknown)) tell 192.168.2.245, length 46
09:58:57.804972 ARP, Reply am437x-evm is-at 68:5e:1c:0a:bc:90 (oui Unknown), length 28
09:58:58.209948 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 547, length 40
09:58:58.210148 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 547, length 40
09:58:59.202628 ARP, Request who-has 192.168.2.245 tell am437x-evm, length 28
09:58:59.202877 ARP, Reply 192.168.2.245 is-at 8c:8c:aa:61:53:57 (oui Unknown), length 46
09:58:59.216267 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 548, length 40
09:58:59.216446 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 548, length 40
09:59:00.221736 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 549, length 40
09:59:00.221891 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 549, length 40
09:59:01.233182 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 550, length 40
09:59:01.233378 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 550, length 40
09:59:02.251900 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 551, length 40
09:59:02.252087 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 551, length 40
09:59:03.268558 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 552, length 40
09:59:03.268732 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 552, length 40
09:59:04.283564 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 553, length 40
09:59:04.283762 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 553, length 40
09:59:05.290110 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 554, length 40
09:59:05.290281 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 554, length 40
09:59:06.295076 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 555, length 40
09:59:06.295263 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 555, length 40
09:59:07.310396 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 556, length 40
09:59:07.310595 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 556, length 40
09:59:08.322504 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 557, length 40
09:59:08.322710 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 557, length 40
09:59:09.335743 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 558, length 40
09:59:09.335915 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 558, length 40
09:59:10.350593 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 559, length 40
09:59:10.350788 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 559, length 40
09:59:11.365710 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 560, length 40
09:59:11.365886 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 560, length 40
09:59:12.379981 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 561, length 40
09:59:12.380164 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 561, length 40
09:59:13.387635 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 562, length 40
09:59:13.387828 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 562, length 40
09:59:14.398187 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 563, length 40
09:59:14.398358 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 563, length 40
09:59:15.407292 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 564, length 40
09:59:15.407450 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 564, length 40
09:59:16.414832 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 565, length 40
09:59:16.415028 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 565, length 40
09:59:17.430298 IP 192.168.2.245 > am437x-evm: ICMP echo request, id 1, seq 566, length 40
09:59:17.430484 IP am437x-evm > 192.168.2.245: ICMP echo reply, id 1, seq 566, length 40

In the above dump data there is certain logs out of which I have highlighted the one which I found while the malformed packet came.

Also find the capture file for your reference.

Malformpackets_10Sep2024_2.zip

with respect to the above capture file please find the information of the device

In the above details below are the device mac address and identifiers in the Wireshark;

AM4376: TexasInstrum_0a:bc:90 (68:5e:1c:0a:bc:90),

Laptop: LCFCElectron_61:53:57 (8c:8c:aa:61:53:57)

Also we recieve host unreachable as well in between.

With respect to the data requested by Paula TCP dump will be ok? or required some other information as well.

Please revert with your inputs and let us know if required any more analysis details.

BR,

Gaurav More

0 Gaurav More 11 months ago in reply to Schuyler Patton

Intellectual 340 points

Hello Schuyler,

Any update regarding the issue?. please revert since we are facing issue regarding the functional testing of our product.

BR,

Gaurav More

0 Schuyler Patton 11 months ago in reply to Gaurav More

TI__Mastermind 40080 points

Hi,

One thing I am noticing is that both link partners are two different subnets. One of the captures as you are pointing out is indicating host unreachable. One device is 192.168.3 subnet and the other is 192.168.2. They are expecting to find a gateway to access the other subnet. I would recommend setting both to the same subnet. I will assume these subnets are assigned statically?

Best Regards,

Schuyler

0 Gaurav More 11 months ago in reply to Schuyler Patton

Intellectual 340 points

Hello,

With respect to our input I also checked for the below IP configuration. I change the Device(Custom Board) configuration to

IP addr: 192.168.2.50 Netmask: 255.255.240.0, No Gate Way

But still the same observation. Please find attached capture for reference,

Malformedpackets_12Sep2024.zip

I have a query regarding the below screenshot

In this you can see device is initiating the ARP request. and the malformed packets are from the device and not from the laptop. But if laptop has initiated pinging then laptop is master and then it should only initiate the ARP request. Why our device (custom board) is initiating the request?. I think there it is making issue.

Even though I changed the IP configuration we have the same observations. while searching on the new I got to know that we should flush the ARP cache since this could be one of the reason for the malformed packet. But while searching for the same in the ARP code in the kernel module I cannot find the same.

Also can we stop the device to initiate ping request? to check whether this is the issue? Also is there a possibility that there might be corruption at the sending side. Since we observed the even when we got the request from the laptop it sends the malformed packets. I think it is not waiting for the creation of the ARP response or request. Also one more observation is every time it is sending header packets while sending the malformed packers. refer the screen shot below

so these are my observations till date . I am also looking in to the issue from myside but not able to locate the code where it initiate the ARP request from the custom board.

Even I have tried with the Default file system and the older version with default kernel configuration but still the result is same.

You can also replicate the same with you evaluation board of AM4376 with any network configurations.

kindly revert with your observations and solution for the same since it has been quiet a while we are trying to find the root cause for the issue. since we are also using the RSTP configuration for it above and also observing the same issue with that as well.

May be resolving one issue will solve other issues related to communication protocol as well since when we are connecting multiple device with bridge (STP enabled) configuration and when we tried to ping the device then we are getting more ping response timeout.

Please revert if required further more information so that I will provide it immediately.

BR,

Gaurav More

0 Schuyler Patton 11 months ago in reply to Gaurav More

TI__Mastermind 40080 points

Hi,

Is the laptop a Linux PC?

For your board what does ethtool -S eth0 return? I am looking for CRC errors or something similar. If the laptop is a Linux machine please do the ethtool -S for the connected interface.

Best Regards,

Schuyler

0 Gaurav More 11 months ago in reply to Schuyler Patton

Intellectual 340 points

Hello,

Thanks for the response,

Is the laptop a Linux PC?

The laptop we are using is windows laptop.

For your board what does ethtool -S eth0 return?

ethtool -S eth0 data is already shared in the above thread. Still refer the below log shared before. This is taken communication is in progress between laptop and our custom board

root@am437x-evm:~# ethtool -S eth0 
NIC statistics:
     txBcast: 1
     txMcast: 29
     txUcast: 323
     txOctets: 29230
     rxBcast: 9
     rxMcast: 31
     rxUcast: 325
     rxOctets: 26299
     tx64byte: 22
     tx65_127byte: 319
     tx128_255byte: 9
     tx256_511byte: 3
     tx512_1023byte: 0
     tx1024byte: 0
     rx64byte: 58
     rx65_127byte: 306
     rx128_255byte: 0
     rx256_511byte: 1
     rx512_1023byte: 0
     rx1024byte: 0
     lateColl: 0
     singleColl: 0
     multiColl: 0
     excessColl: 0
     rxMisAlignmentFrames: 0
     stormPrevCounterBC: 0
     stormPrevCounterMC: 0
     stormPrevCounterUC: 0
     macRxError: 0
     SFDError: 0
     defTx: 0
     macTxError: 0
     rxOverSizedFrames: 0
     rxUnderSizedFrames: 0
     rxCRCFrames: 0
     droppedPackets: 0
     txHWQOverFlow: 0
     txHWQUnderFlow: 0
     vlanDropped: 0
     multicastDropped: 27

I am looking for CRC errors or something similar.

Where to check this so that I will check at my side for it and confirm.

If the laptop is a Linux machine please do the ethtool -S for the connected interface.

Since we are using laptop which is connected to the device(custom board ). Will check whether it support windows PC.

BR,

Gaurav More

0 Schuyler Patton 11 months ago in reply to Gaurav More

TI__Mastermind 40080 points

Hi,

Thanks for the ethtool results from your board. I do not know how to look at MAC statistics for the Windows machine. The ethtool results indicate no errors, so from a basic send and receive I do not see an issue with the AM437 board. You may be up against a network firewall issue on the windows laptop. Do you have two of your boards that you directly connect? or a TI EVM? If so I would try the ping test between the two boards and not the windows laptop.

Best Regards,

Schuyler

0 Gaurav More 11 months ago in reply to Schuyler Patton

Intellectual 340 points

Hi,

Thanks for the response,

Will check ping between 2 boards. but then how to check with the Wireshark? since the testing is with the laptop. I would suggest that you can also try at your end by connecting the TI EVM board with your windows laptop. You can also get the issue related to the same. You can use the default configuration of kernel and U-boot.

Also connect the device as mentioned in the above threads. There you can debug the same. I think that will help you to understand. But following should be the codes,

processor SDK 437x Ver8.02

kernel - ver 5.10.100

uboot Ver 2019

Kindly check for the same and revert ASAP so that we will on the same platform. Only difference in our case is the modification w.r.t our custom board. Also let me know what else it needed from our side for your reference,

Also in the mean time I will also check the TCP packet communication using the windows PC. TCP client and server connection between Laptop and custom board.

We can have call regarding the same. If possible today only. Please revert with the same.

BR,

Gaurav More

0 Schuyler Patton 11 months ago in reply to Gaurav More

TI__Mastermind 40080 points

Hi,

Currently I am on business travel and I am not able to do any testing.

I rarely use a windows laptop. I typically use a PC running Ubuntu that has wireshark installed. There are switches that you can purchase that have port mirroring that allow the sniffing of traffic. You can also use tcpdump in the TI filesystem to dump the traffic to a file that be taken from the SD card of the EVM analyzed on a machine that has wireshark.

Best Regards,

Schuyler

0 Gaurav More 11 months ago in reply to Schuyler Patton

Intellectual 340 points

Thanks for the response,

I have already shared the details in the previous threads regarding the TCP dump taken from the TI filesystem. Also I implemented the TCP client server communication between the Laptop and the Device. Please refer the log attached.

TCP_ClientCapture.zip

TCPCLient_2.zip

There is a similar observation. Now since our Validation team and pre-compliance team is using the windows laptop only for the testing and so as per there input it is not acceptable to see any malformed packet.

We need to know whether the issue is due to kernel or application . But since we are not running any application so possibly it could be kernel side only. This is what my understanding but need your inputs.

Please let us know what we can do from our side since that is stopping our further testing of our device.

BR,

Gaurav More

0 Schuyler Patton 11 months ago in reply to Gaurav More

TI__Mastermind 40080 points

Hi,

As I mentioned I am out of the office on business travel. I will review early next week when I am back. I will check with colleague for suggestions.

Best Regards,

Schuyler

0 Gaurav More 11 months ago in reply to Schuyler Patton

Intellectual 340 points

Any update regarding the issue ?

We are not able to proceed further for testing due to this issue. This will clarify whether the communication loss , ping loss and when we connect the devices in daisy chain with STP enable then also we found multiple loss, it is the same reason.

Also do we have latest PRU firmware and ca we replace it with new one in our case?

BR,

Gaurav More

0 Schuyler Patton 10 months ago in reply to Gaurav More

TI__Mastermind 40080 points

Hi,

I am not able to directly reproduce the problem. I do not see malformed packets. I have set up a direct connect between a AM437 IDK board and a Ubuntu laptop. With Wireshark I do not see malformed packets, I do see error packets being detected by the Laptop NIC card. These seem to happen when there is both traffic and no traffic.

When I run ping I am not seeing dropped ping packets. I know you mentioned that there are missing ping packets, is this loss being reported by the ping application?

I will ask for comment from the development team on how to confirm is these error packets are coming from the AM437.

Best Regards,

Schuyler

0 Gaurav More 10 months ago in reply to Schuyler Patton

Intellectual 340 points

Hi,

Thanks for the response,

You may not see the malformed packets on Linux PC on Wireshark but you can definitely see then on Window PC. This is reported by our functional pre-compliance team and V&V team since they are using Windows PC only for testing,

Also in addition to that the is one more observation added by then that ARP Packet is not initiated by the device unless ping command or any communication is established with the device through PC or any other tool. When there is no activity on the device the device should also broadcast the ARP packet request.

Also when we are using any switch be it a normal one or STP or RSTP switch then also you will not be able to see the malformed packets. But the device is sending it ,its just may be the switch is blocking it at the backend.

Yes they are using some tool name (profi shark ) to check the ping loss as well. When I was testing then I observed that when MDNS packet transmission happens in between then this ping loss comes. It you checking it with one device then it is very rare but it is there. But if you connect more then 2 devices in daisy chain with Bridge configuration enabled then this ping loss issue.

Also refer the capture attached where the malformed packets are sent in case of LLDP and STP .Also check when device is connected in the daisy chain.

These observations are share by the V&V and pre-compliance team.

malformed packet of stp.zip Fw27_Test_1_Daisy_chain_8_Tera_41_to_57_Wireshark (File Sync.).pcapng.zip

Please check and revert of need any more details.

BR,

Gaurav More

0 Schuyler Patton 10 months ago in reply to Gaurav More

TI__Mastermind 40080 points

Hi,

Thank you for the additional details. I am using what I call a direct connect to between the TI EVM and the laptop, nothing in-between. Knowing that a Profishark tool was used would give probably a better look at the line. I will check to see we can this tool to look at the line.

You did not mention, when a ping loss is detected is it that ping utility reporting the loss?

Best Regards,

Schuyler

0 Gaurav More 10 months ago in reply to Schuyler Patton

Intellectual 340 points

Yes they used Profishark tool to test the ping loss. From there they got to know that the ping loss is there.

BR,

Gaurav More

0 Gaurav More 10 months ago in reply to Schuyler Patton

Intellectual 340 points

Hi,

Is there update regarding the issue raised. Any other inputs needed since we are waiting whether there is any modifications.

BR,

Gaurav More

0 Gaurav More 9 months ago in reply to Schuyler Patton

Intellectual 340 points

Hi,

Any update or any finding regarding the issue rasied? Please respond since it is on very high priority.

BR,

Gaurav More

Processors

Processors forum

AM4376: Ping Loss or Ping response timeout happening while pinging the device from the laptop.