Global Sources
EE Times-India
Stay in touch with EE Times India
EE Times-India > Embedded

Address issues in embedding TCP/IP (Part 5)

Posted: 15 May 2013     Print Version  Bookmark and Share

Keywords:TCP-IP  CPU  RAM 

In Part 5, we discuss the add-on options data footprint. Here are the links to the previous instalments: Part 1, Part 2, Part 3 and Part 4.

The RAM data usage for theµC/TCP-IP add-on options is provided for planning assistance. In the following table, we use the definition of the size of CPU_STK as being 4 bytes.

Several considerations are necessary when adding a TCP/IP stack to an embedded system. Most of these are performance related, including:

 • The CPU's ability to process all of the packets to be transmitted or received
 • The Ethernet Controller type has an impact on the driver
 • The transfer method between the Ethernet Controller and the TCP/IP stack has an impact on performance
 • Byte copy from one location to another via the CPU
 • DMA transfer
 • The Zero-Copy architecture of the TCP/IP stack has an impact on performance
 • The code and data footprints:
- Code footprint depends on what protocols are used and this depends on what the specific goal of the application.
- A data footprint is largely affected by the number of network buffers required.

Ethernet driver development and test represent challenges the embedded engineer must face. We will then move up through the layers on our way to the Application layer, finding additional obstacles to overcome in order to efficiently embed a TCP/IP stack into a product.

About the author
Christian Legare is from Micrium.

To download the PDF version of this article, click here.

Comment on "Address issues in embedding TCP/IP (..."
*  You can enter [0] more charecters.
*Verify code:


Visit Asia Webinars to learn about the latest in technology and get practical design tips.


Go to top             Connect on Facebook      Follow us on Twitter      Follow us on Orkut

Back to Top