Enet Lwip UDP IGMP Server Example

Introduction

Note

LwIP features are made available as is from public lwIP project. SDK configuration may only enable and exercise a subset of these features.

This example shows about how to implement a simple UDP IGMP-Server on LwIP networking stack using BSD-Socket API coupled with ethernet driver (ENET)

On AM62PX, we can do ethernet based communication using CPSW as HW mechanism

  • CPSW is a standard ethernet switch + port HW

  • It uses ethernet driver underneath with LwIP TCP/IP networking stack

  • CPSW can be configured in two modes: Switch or MAC. For more details, Basic Layer 2 Switching

The example does the following:

  • Initializes the ethernet driver for the underlying HW

  • Initializes the LwIP stack for TCP/UDP IP and Starts UDP (echo) IGMP Server task.

  • UDP Server task waits for a msg to the multicast IP address from client on port 2638 and echoes back the same message.

Supported Combinations

Configuring Syscfg

  • Following Syscfg option allows flexibility to configure memory foot print based on required use case like: Number of DMA descriptors and buffering.

  • Supported Options with default configuration

Feature Section Description Remarks/Default Setting
Mdio Manual Mode Enable TI Networking / Enet (CPSW) Flag to enable MDIO manual mode in example. Driver support for Manual mode is enabled, so this parameter configures manual mode in the example. Default is true. If your silicon is affected with errata i2329— MDIO interface corruption, then TI suggests to use MDIO_MANUAL_MODE as software workaround.
Enable Packet Pool Allocation TI Networking / Enet (CPSW) / Packet Pool Config Flag to enable packet buffer memory allocation from enet utils library. It should be disabled to avoid utils memory wastage, in case application allots packet via other mechanism. Default is true. If enabled size of pkt pool size depends on 'Large Pool Packet Size', 'Large Pool Packet Count', 'Medium Pool Packet Size', 'Medium Pool Packet Count', 'Small Pool Packet Size' and 'Small Pool Packet Count'. EnetMem_allocEthPkt API uses this memory to allocate the DMA Ethernet packet.
Only Enable Packet Info Allocation TI Networking / Enet (CPSW) / Packet Pool Config Flag to allocate only the DMA Packet Info structures, this does not include the buffer memory. This is useful when the buffer memory is internally allocated by the application. (Ex- Lwip pools) Default is true. If enabled "PktInfoMem Only Count" determines the number of additional DMA Packet Info structures allocated. EnetMem_allocEthPktInfoMem uses this memory to allocate empty DMA Packet Info structures.
Number of Tx Packet TI Networking / Enet (CPSW) / DMA channel config No of Tx packets required for DMA channel Default is 16. For LwIP example, the Tx packet buffer memory is internally allocated in lwippools.h. Only the DMA Pkt Info structures are allocated via sysCfg, so this number should match the "PktInfoMem Only Count" described in the above item. To increase the Tx packet count, user needs to update the number correspondingly at "PktInfoMem Only Count" and lwippools.h and build the libs.
Number of Rx Packet TI Networking / Enet (CPSW) / DMA channel config No of Rx packets required for DMA channel Default is 32. It contributes to the size of Pkt Mem Pool, DMA ring buffer and accessories size. Rx packet buffer memory is completely mananged with application sysCfg, this is done by using Rx custom Pbuf in LwIP.
Netif instance TI Networking / Enet (CPSW) / LWIP Interface config No of netifs allocated by the example Only one netif should be set to default when more than one netif is allocated.

UDP Client using ncat tool

Ncat is a general-purpose command-line tool for reading, writing, redirecting, and encrypting data across a network. It aims to be your network Swiss Army knife, handling a wide variety of security testing and administration tasks. Ncat is suitable for interactive use or as a network-connected back end for other tools.

  • Ncat is started as server to which EVM connects.

  • The version used for this example Version 7+ ( https://nmap.org/ncat )

Steps to Run the Example

To Configure Static IP

Please refer to To Configure Static IP.

Build the example

  • When using CCS projects to build, import the CCS project for the required combination and build it using the CCS project menu (see Using SDK with CCS Projects).

  • When using makefiles to build, note the required combination and build using make command (see Using SDK with Makefiles)

Note: For UDP transmission on LwIP based application, application should perform cache coherency operation on payload before submitting the packet for transmission. This is because zero copy is enabled for UDP packet transmission and cache operation in driver are disabled for UDP payload portions. This example application does this using CacheP_wbInv.

HW Setup

Note

Make sure you have setup the EVM with cable connections. In addition do below steps.

EVM Setup

AM64X-EVM

For CPSW based example

  • Connect a ethernet cable to the EVM from host PC as shown below

    \imageStyle{am64x_evm_lwip_example_00.png,width:30%} \image html am64x_evm_lwip_example_00.png Ethernet cable for CPSW based ethernet

AM62X-SK

For CPSW based example

  • Connect a ethernet cable to the EVM from host PC as shown below

Ethernet cable for CPSW based ethernet

AM243X-EVM

For CPSW based example

  • Connect a ethernet cable to the EVM from host PC as shown below

    \imageStyle{am64x_evm_lwip_example_00.png,width:30%} \image html am64x_evm_lwip_example_00.png Ethernet cable for CPSW based ethernet

AM243X-LP

Note

AM243X-LP has two ethernet Ports which can be configured as both CPSW ports.

For CPSW based examples

  • Connect a ethernet cable to the AM243X-LP from host PC as shown below

    \imageStyle{am243x_lp_lwip_example_00.png,width:30%} \image html am243x_lp_lwip_example_00.png Ethernet cable for CPSW based ethernet

Create a network between EVM and host PC

  • The EVM will get an IP address using DHCP, so make sure to connect the other end of the cable to a network which has a DHCP server running.

  • To get started one can create a simple local network between the EVM and the host PC by using a home broadband/wifi router as shown below. Most such routers run a DHCP server

Local network between PC and EVM

  • To check the router connection with host PC, recommend to disconnect all other networking conenctions on the PC, sometimes you may need to disable firewall SW, and make sure the router is able to assign a IP address to your host PC

  • After we run the example on the EVM (next step), the EVM will similarly be assigned a IP address, and then host can communicate with the EVM using the assigned IP address.

  • To enable static IP, set the static IP in the ipAddr variable in the App_setupNetif() before passing it as arguement to initiate the netif, and stop the dhcp from starting in the App_allocateIPAddress() function.

Run the example

Attention

If you need to reload and run again, a CPU power-cycle is MUST

  • You will see logs in the UART terminal as shown in the next section.

  • Note the IP address seen in the log, this is what we will use to communicate with the EVM.

Sample output for CPSW example


============================
  CPSW LWIP IGMP UDP SERVER
============================
EnetPhy_bindDriver:1718
PHY 3 is alive
PHY 12 is alive
Starting lwIP, local interface IP is dhcp-enabled
Host MAC address: 34:08:e1:77:fb:0c
[LWIPIF_LWIP] Enet has been started successfully
[LWIPIF_LWIP] NETIF INIT SUCCESS
Enet IF UP Event. Local interface IP:0.0.0.0
Waiting for network UP ...
Cpsw_handleLinkUp:1320
MAC Port 1: link up
Network Link UP Event
Waiting for network UP ...
Enet IF UP Event. Local interface IP:10.24.69.14
Network is UP ...
UDP server: Port 2638
UDP server: joined Multicast group
     10.107s : CPU load =   2.25 %
     15.108s : CPU load =   1.70 %
     20.109s : CPU load =   1.82 %
     25.110s : CPU load =   1.79 %
     30.111s : CPU load =   1.75 %
     35.112s : CPU load =   1.72 %
     40.113s : CPU load =   1.71 %
     45.114s : CPU load =   1.68 %
     50.115s : CPU load =   1.71 %
     55.116s : CPU load =   1.66 %
     60.117s : CPU load =   1.65 %
     65.118s : CPU load =   1.70 %
     70.119s : CPU load =   1.65 %
     75.120s : CPU load =   1.71 %
     80.121s : CPU load =   1.74 %
     85.122s : CPU load =   1.73 %
     90.123s : CPU load =   1.69 %
     95.124s : CPU load =   1.66 %
    100.125s : CPU load =   1.70 %
    105.126s : CPU load =   1.67 %
    110.127s : CPU load =   1.69 %
    115.128s : CPU load =   1.70 %
    120.129s : CPU load =   1.70 %
    125.130s : CPU load =   1.75 %
    130.131s : CPU load =   1.72 %
    135.132s : CPU load =   2.07 %
    140.133s : CPU load =   1.77 %
    145.134s : CPU load =   1.82 %
    150.135s : CPU load =   1.70 %
    155.136s : CPU load =   1.73 %
    160.137s : CPU load =   1.76 %
    165.138s : CPU load =   1.72 %
    170.139s : CPU load =   1.70 %
    175.140s : CPU load =   1.75 %
    180.141s : CPU load =   1.82 %
    185.142s : CPU load =   1.81 %
    190.143s : CPU load =   1.72 %
    195.144s : CPU load =   1.70 %
    200.145s : CPU load =   1.71 %
    205.146s : CPU load =   1.70 %
    210.147s : CPU load =   1.72 %
    215.148s : CPU load =   1.68 %
    220.149s : CPU load =   1.76 %
    225.150s : CPU load =   1.73 %
    230.151s : CPU load =   1.73 %
    235.152s : CPU load =   1.69 %
    240.153s : CPU load =   1.69 %
    245.154s : CPU load =   1.70 %
    250.155s : CPU load =   1.83 %
    255.156s : CPU load =   1.77 %
    260.157s : CPU load =   1.82 %
    265.158s : CPU load =   1.72 %
    270.159s : CPU load =   1.69 %
    275.160s : CPU load =   1.73 %
    280.161s : CPU load =   1.76 %
    285.162s : CPU load =   1.68 %
    290.163s : CPU load =   1.75 %
    295.164s : CPU load =   1.69 %
    300.165s : CPU load =   1.70 %
    305.166s : CPU load =   1.71 %
Packet recieved
Client: Hi

Echo pkt completed
    310.167s : CPU load =   1.73 %
    315.168s : CPU load =   1.72 %
    320.169s : CPU load =   1.69 %
    325.170s : CPU load =   1.67 %
    330.171s : CPU load =   1.68 %
    335.172s : CPU load =   1.68 %
    340.173s : CPU load =   1.84 %
    345.174s : CPU load =   1.76 %
    350.175s : CPU load =   1.71 %
    355.176s : CPU load =   1.70 %
    360.177s : CPU load =   1.68 %
    365.178s : CPU load =   1.68 %
    370.179s : CPU load =   1.67 %
    375.180s : CPU load =   1.68 %
    380.181s : CPU load =   1.70 %
    385.182s : CPU load =   1.70 %
    390.183s : CPU load =   1.66 %
    395.184s : CPU load =   1.72 %
    400.185s : CPU load =   1.71 %
    405.186s : CPU load =   1.69 %
    410.187s : CPU load =   1.70 %
    415.188s : CPU load =   1.66 %
    420.189s : CPU load =   1.68 %
    425.190s : CPU load =   1.68 %
Packet recieved
Client:
Echo pkt completed
    430.191s : CPU load =   1.69 %
    435.192s : CPU load =   1.68 %
    440.193s : CPU load =   1.69 %
    445.194s : CPU load =   1.69 %
    450.195s : CPU load =   1.68 %

Steps to execute

  1. Run example on EVM

  2. Try to reach the EVM using ping as shown below, using a command shell on the host PC

    $ping 192.168.1.10

    “192.168.1.10” should be replaced with IP of EVM.

  3. Start UDP client using ‘ncat’ cmds as shown below. Below steps have been tried with a Linux Ubuntu 18.04 host PC running bash shell

    Install ‘ncat’ if not installed by doing below

    $sudo apt install ncat

    Invoke ‘ncat’ to connect to Multicast IP ‘224.0.1.129’ on port 2638

    $ncat -u 224.0.1.129 2638
$

  4. Send any msg in ncat terminal and observe that it is recieved in EVM

  5. Close the ncat using Ctrl + C.

Troubleshooting issues

  • If you see a valid, non-zero MAC address and continuosly seieing “Waiting for network UP…” prints in UART terminal

    • Make sure you see Enet IF UP Event. message, if not check the ethernet cable

    • Check the local network and check if the DHCP server is indeed running as expected

    • When using a home broadband/wifi router, its possible to check the clients connected to the DHCP server via a web browser. Check your router user manual for more details.

See Also