lwip-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] bare metal rtp application


From: John Coffey
Subject: [lwip-devel] bare metal rtp application
Date: Wed, 20 Apr 2022 12:33:32 -0400

I am trying to get started with lwip running in bare metal (NO_SYS==1) mode.  To this end and especially to learn how lwip works under the covers, I built lwip using the contrib/ports/win32 solution. I changed 'lwip/contrib/examples/example_app/lwipopts.h' to have NO_SYS set to 1.

After installing npcap (in pcap mode), and installing the npcap sdk 1.2 (and adding an environment variable PCAP_DIR that points to this sdk location), I can single step in bare metal mode on windows.  This works as the w

The 'lwip/contrib/examples/example_app/test.c' file example works well and prints out the following:

Starting lwIP, local interface IP is dhcp-enabled
 0: NPF_{15A80AE8-8763-41F6-9FD5-48679C001987}
     Desc: "WAN Miniport (Network Monitor)"
 1: NPF_{0118A172-5B42-4CAF-9E49-8BD25939888C}
     Desc: "WAN Miniport (IPv6)"
 2: NPF_{78A6D491-D3BE-4A30-8148-140363AC5DAB}
     Desc: "WAN Miniport (IP)"
 3: NPF_{9F0260A3-1AB8-467E-813F-318AB73F2AB5}
     Desc: "Intel(R) Ethernet Connection I217-LM"
 4: NPF_Loopback
     Desc: "Adapter for loopback traffic capture"
 5: NPF_{3CA2B6C7-E440-4901-87B8-CF3A8042ABC1}
     Desc: "TAP-Win32 Adapter V9 #2"
 6: NPF_{CDAE33E7-4AFF-4458-8702-6E9473BB17B0}
     Desc: "TAP-Win32 Adapter V9"
 7: NPF_{E2E817B7-54F1-4A41-BAD9-4BF568DE5B52}
     Desc: "Intel(R) Gigabit CT Desktop Adapter"
Using adapter_num: 1
Using adapter: "WAN Miniport (IPv6)"
status_callback==UP, local interface IP is 0.0.0.0

I eventually need to port the lwip stack and write an accompanying ethernet driver for a bare metal target (Analog Devices SHARC core).  The bare metal rtp application will send and receive rtp packets through the lwip stack as part of its main loop.  I have no idea how to go about making a minimal main loop with appropriate options.   From what I can tell the existing rtp example code uses the sequential API, however bare metal systems need to use the RAW api. 

I would like to develop the main loop in windows as long as possible while waiting for the SHARC netif ethernet driver which is being developed in parallel.

Thanks
 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]