SPNA248 March 2021 TM4C1292NCPDT , TM4C1292NCPDT , TM4C1292NCZAD , TM4C1292NCZAD , TM4C1294KCPDT , TM4C1294KCPDT , TM4C1294NCPDT , TM4C1294NCPDT , TM4C1294NCZAD , TM4C1294NCZAD , TM4C1299KCZAD , TM4C1299KCZAD , TM4C1299NCZAD , TM4C1299NCZAD , TM4C129DNCPDT , TM4C129DNCPDT , TM4C129DNCZAD , TM4C129DNCZAD , TM4C129EKCPDT , TM4C129EKCPDT , TM4C129ENCPDT , TM4C129ENCPDT , TM4C129ENCZAD , TM4C129ENCZAD , TM4C129LNCZAD , TM4C129LNCZAD , TM4C129XKCZAD , TM4C129XKCZAD , TM4C129XNCZAD , TM4C129XNCZAD
lwIP provides three styles of Application Programming Interface (API) for programs to use for communication with the TCP/IP code:
All examples demonstrated in this application report are based on the Raw API interface only. The Raw API provides a callback style interface to the application. The application first registers callback functions to different core events. Typical TCP events are:
The user-supplied callback functions are called from the lwIP core when the corresponding event occurs. When using the Raw API interface, the TCP/IP code and the application program can both run in the same thread in a non-OS environment. The raw TCP/IP interface is faster in terms of code execution time and is also less memory intensive at the expense of coding complexity. The other two API styles are currently not supported by the TivaWare library. However, the BSD socket-based APIs are supported through the TI-RTOS NDK. Various socket-based Ethernet examples can be downloaded from the Code Composer Studio™ (CCS) Resource Explorer.