********************************************************** EVM ifconfig ********************************************************** eth1 Link encap:Ethernet HWaddr 02:18:31:7E:3E:00 inet addr:192.168.0.101 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::18:31ff:fe7e:3e00%132688/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:22 errors:0 dropped:0 overruns:0 frame:0 TX packets:16 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3500 (3.4 KiB) TX bytes:1758 (1.7 KiB) ********************************************************** Laptop ifconfig ********************************************************** zumi@zumi-HP-Pavilion-dv6-Notebook-PC:~$ ifconfig eno1 Link encap:Ethernet HWaddr 10:1f:74:17:25:4f inet addr:192.168.0.139 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::e3d7:8e50:6e93:e015/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:90414 errors:0 dropped:0 overruns:0 frame:0 TX packets:43456 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:92168837 (92.1 MB) TX bytes:4843157 (4.8 MB) ********************************************************** PC ifconfig ********************************************************** enp2s0 Link encap:Ethernet HWaddr e0:d5:5e:38:66:88 inet addr:192.168.0.137 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::46d5:a151:ac8d:6758/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:117500 errors:0 dropped:0 overruns:0 frame:0 TX packets:56940 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:83752445 (83.7 MB) TX bytes:7655915 (7.6 M) ############### Dear Aravind, Before running PA example application, We able to capture packets on EVM ################# root@AM5K2E04:~# tcpdump -i eth1 -c500 -nn src 192.168.0.139 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 262144 bytes 05:49:46.511251 IP 192.168.0.139.1234 > 192.168.0.101.5678: UDP, length 16 05:49:46.675711 IP 192.168.0.139.1234 > 192.168.0.101.5678: UDP, length 16 05:49:46.860345 IP 192.168.0.139.1234 > 192.168.0.101.5678: UDP, length 16 05:49:46.996085 IP 192.168.0.139.1234 > 192.168.0.101.5678: UDP, length 16 05:49:47.210452 IP 192.168.0.139.1234 > 192.168.0.101.5678: UDP, length 16 05:49:47.479990 IP 192.168.0.139.1234 > 192.168.0.101.5678: UDP, length 16 05:49:47.659450 IP 192.168.0.139.1234 > 192.168.0.101.5678: UDP, length 16 05:49:47.809057 IP 192.168.0.139.1234 > 192.168.0.101.5678: UDP, length 16 05:49:47.979311 IP 192.168.0.139.1234 > 192.168.0.101.5678: UDP, length 16 05:49:48.173019 IP 192.168.0.139.1234 > 192.168.0.101.5678: UDP, length 16 05:49:48.352578 IP 192.168.0.139.1234 > 192.168.0.101.5678: UDP, length 16 05:49:48.632373 IP 192.168.0.139.1234 > 192.168.0.101.5678: UDP, length 16 ^C 12 packets captu[ 68.293816] device eth1 left promiscuous mode red 12 packets received by filter 0 packets dropped by kernel root@AM5K2E04:~# root@AM5K2E04:~# root@AM5K2E04:~# tcpdump -i eth1 -c500 -nn src 192.168.0.137 [ 70.774952] device eth1 entered promiscuous mode tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 262144 bytes 05:49:59.963605 IP 192.168.0.137.1234 > 192.168.0.101.5678: UDP, length 15 05:50:05.051432 IP 192.168.0.137.1234 > 192.168.0.101.5678: UDP, length 15 05:50:07.651410 IP 192.168.0.137.1234 > 192.168.0.101.5678: UDP, length 15 05:50:09.755292 IP 192.168.0.137.1234 > 192.168.0.101.5678: UDP, length 15 05:50:09.795410 IP 192.168.0.137.1234 > 192.168.0.101.5678: UDP, length 15 05:50:10.307306 IP 192.168.0.137.1234 > 192.168.0.101.5678: UDP, length 15 ^C 12 packets captu[ 93.086096] device eth1 left promiscuous mode red 12 packets received by filter 0 packets dropped by kernel root@AM5K2E04:~# ############### Dear Aravind, Now we running PA example application with Laptop & EVM rules ################# root@AM5K2E04:~# rmServer.out /usr/bin/device/k2e/global-resource-list.dtb /usr/bin/device/k2e/policy_dsp_arm.dtb Starting rmServer.out Daemon returned 0 as return value. root@AM5K2E04:~# ./paMCExample.out No command line given. Forking off 4 tasks ************************************************ ************************************************ *** PA Multi Core Example Started on Core 0 *** *** PA Multi Core Example Started on Core 1 *** ************************************************ ************************************************ Waiting for global config (core 1) ... Initialized RM_Client0 ************************************************ *** PA Multi Core Example Started on Core 3 *** ************************************************ Waiting for global config (core 3) ... ************************************************ *** PA Multi Core Example Started on Core 2 *** Initializing Free Descriptors. ************************************************ QMSS successfully initialized Waiting for global config (core 2) ... Unable to open below cppi tx channels...presuming linux has already enabled it 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 20 Unable to open below cppi Rx channels...presuming linux has already enabled it 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 5 CPPI successfully initialized PASS successfully initialized Tx setup successfully done Qmss_getqueueNumber queue[0] 1 Qmss_queueOpening queue 6472 rxQinfo[0] = 1 Rx setup successfully done Add_MAC successful for Laptop:0 Add_MAC2 successful for PC:0 Add_IP successful for LAPTOP:0 Add_IP successful for PC:0 Core number 0 Add_Port RxQueue[0] = 6472 Destination for the packet Rx queue: 6472 (Core 0) Add_Port successful for corenum:0 PASS setup successfully done Publishing global config Done from SYSINIT Core... Publishing local config done from core num: 0... Waiting for all cores to reach the barrier before transmission starts ... Initialized RM_Client1 QMSS Local successfully initialized CPPI Local successfully initialized Initialized RM_Client3 PA Local successfully initialized QMSS Local successfully initialized CPPI Local successfully initialized Initialized RM_Client2 PA Local successfully initialized QMSS Local successfully initialized CPPI Local successfully initialized PA Local successfully initialized Qmss_getqueueNumber queue[0] 1 Qmss_queueOpening queue 6472 rxQinfo[0] = 1 Rx setup successfully done Qmss_getqueueNumber queue[0] 1 Qmss_queueOpening queue 6472 rxQinfo[0] = 1 Core number 1 Add_Port RxQueue[0] = 6472 Destination for the packet Rx queue: 6472 (Core 1) Add_Port successful for corenum:1 PASS setup successfully done Publishing local config done from core num: 1... Waiting for all cores to reach the barrier before transmission starts ... Rx setup successfully done Qmss_getqueueNumber queue[0] 1 Qmss_queueOpening queue 6472 rxQinfo[0] = 1 Core number 3 Add_Port RxQueue[0] = 6472 Destination for the packet Rx queue: 6472 (Core 3) Add_Port successful for corenum:3 PASS setup successfully done Publishing local config done from core num: 3... Waiting for all cores to reach the barrier before transmission starts ... Rx setup successfully done Core number 2 Add_Port RxQueue[0] = 6472 Destination for the packet Rx queue: 6472 (Core 2) Add_Port successful for corenum:2 PASS setup successfully done Publishing local config done from core num: 2... Waiting for all cores to reach the barrier before transmission starts ... Packet Transmission Start ... core id: 2 Packet Transmission Done. Wait for all packets to be Received ... core num: 2 Packet Transmission Start ... core id: 0 Packet Transmission Done. Wait for all packets to be Received ... core num: 0 Packet Transmission Start ... core id: 1 Packet Transmission Done. Wait for all packets to be Received ... core num: 1 Packet Transmission Start ... core id: 3 Packet Transmission Done. Wait for all packets to be Received ... core num: 3 [ 151.954906] sched: RT throttling activated ^C ############### Dear Aravindh after succesfully added MAC, IP & Ports using PA application, capturing packets on using tcpdump ################# root@AM5K2E04:~# tcpdump -i eth1 -c500 -nn src 192.168.0.139 [ 166.774939] device eth1 entered promiscuous mode tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 262144 bytes ^C 0 packets captur[ 279.517096] device eth1 left promiscuous mode ed 0 packets received by filter 0 packets dropped by kernel root@AM5K2E04:~# tcpdump -i eth1 -c500 -nn src 192.168.0.137 [ 282.114935] device eth1 entered promiscuous mode tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 262144 bytes ############### Dear Aravindh, Here if we added PA rules with both Laptop & PC, Not able to receive Packets #################