embOS/IP CPU independant TCP/IP stack for embedded applications User & Reference Guide Document: UM07001 Software version: 2.20 Revision: 0 Date: April 30, 2014 A product of SEGGER Microcontroller GmbH & Co. KG www.segger.com 2 Disclaimer Specifications written in this document are believed to be accurate, but are not guaranteed to be entirely free of error. The information in this manual is subject to change for functional or performance improvements without notice. Please make sure your manual is the latest edition. While the information herein is assumed to be accurate, SEGGER Microcontroller GmbH & Co. KG (SEGGER) assumes no responsibility for any errors or omissions. SEGGER makes and you receive no warranties or conditions, express, implied, statutory or in any communication with you. SEGGER specifically disclaims any implied warranty of merchantability or fitness for a particular purpose. Copyright notice You may not extract portions of this manual or modify the PDF file in any way without the prior written permission of SEGGER. The software described in this document is furnished under a license and may only be used or copied in accordance with the terms of such a license. (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG, Hilden / Germany Trademarks Names mentioned in this manual may be trademarks of their respective companies. Brand and product names are trademarks or registered trademarks of their respective holders. Contact address SEGGER Microcontroller GmbH & Co. KG In den Weiden 11 D-40721 Hilden Germany Tel.+49 2103-2878-0 Fax.+49 2103-2878-28 E-mail: support@segger.com Internet: http://www.segger.com UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 3 Manual versions This manual describes the current software version. If any error occurs, inform us and we will try to assist you as soon as possible. Contact us for further information on topics or routines not yet specified. Print date: April 30, 2014 Software Revision Date By Description 2.20 0 140430 Chapter "Core functions" updated. * IP_ConfigOffCached2Uncached() added. * IP_AddLoopbackInterface() added. * IP_AddStateChangeHook() added. * IP_Alloc() added. * IP_ARP_ConfigMaxPending() added. * IP_Connect() added. * IP_DisableIPRxChecksum() added. * IP_Disconnect() added. * IP_DNS_SetServerEx() added. * IP_EnableIPRxChecksum() added. * IP_Err2Str() added. * IP_Free() added. * IP_GetPrimaryIFace() added. * IP_IsExpired() added. * IP_ResolveHost() added. * IP_SetIFaceConnectHook() added. * IP_SetIFaceDisconnectHook() added. * IP_SetPrimaryIFace() added. * IP_SOCKET_ConfigSelectMultiplicator() added. * IP_ICMP_DisableRxChecksum() added. * IP_ICMP_EnableRxChecksum() added. * IP_TCP_DisableRxChecksum() added. * IP_TCP_EnableRxChecksum() added. * IP_UDP_DisableRxChecksum() added. * IP_UDP_EnableRxChecksum() added. OO * IP_ConfTCPSpace() renamed to IP_ConfigTCPSpace() Chapter "Socket interface" updated. * gethostbaname() parameter changed to "const char *" for standard BSD socket compatibility. Chapter "UDP zero-copy interface" updated. * IP_UDP_GetDestAddr() added. * IP_UDP_GetIFIndex() added. * IP_UDP_GetSrcAddr() added. Chapter "RAW zero-copy interface" updated. * IP_RAW_GetDataSize() added. * IP_RAW_GetDestAddr() added. * IP_RAW_GetIFIndex() added. Chapter "DHCP client" updated. * IP_DHCPC_ConfigOnActivate() added. * IP_DHCPC_ConfigOnFail() added. * IP_DHCPC_ConfigOnLinkDown() added. * IP_DHCPC_Renew() added. Chapter "PPP / PPPoE (Add-on)" updated. * IP_PPP_OnTxChar() return value changed. Chapter "Appendix A - File system application layer" updated. * pfIsFolder added to IP_FS_API structure. * pfMove added to IP_FS_API structure. Chapter "DHCP server (Add-on)" added. Chapter "Performance & resource usage" updated. * Values for ROM & RAM usage updated. Minor changes. 2.12g 0 131216 OO Chapter "Core functions" updated. * IP_ConfigOffCached2Uncached() added. 2.12f 0 130909 OO Chapter "Core functions" updated. * IP_AddAfterInitHook() added. Chapter "UDP zero-copy interface" updated. * IP_UDP_GetDataSize() added. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 4 Software Revision Date By Description 2.12c 0 130515 Chapter "Introduction to embOS/IP" updated. * Added information regarding task priorities. Chapter "Core functions" updated. * Added extended information to IP_DeInit() description. OO Chapter "Web server (Add-on)" updated. * IP_WEBS_GetURI() added. * IP_WEBS_Reset() added. 2.12b 0 130419 OO 130312 Minor updates and corrections. Chapter "Core functions" updated. * IP_PHY_DisableCheck() added. * IP_RAW_Add() added. * IP_DNS_GetServer() added. * IP_DNS_GetServerEx() added. Chapter "Socket interface" updated. * Information regarding usage of RAW sockets added. OO Chapter "Web server (Add-on)" updated. * IP_WEBS_AddVFileHook() updated. * IP_WEBS_Redirect() added. * IP_WEBS_StoreUserContext() added. * IP_WEBS_RetrieveUserContext() added. * IP_WEBS_GetDecodedStrLen() added. * IP_WEBS_METHOD_* API added. Chapter "RAW zero-copy interface" added. Chapter "SNTP client" added. 2.12 0 Chapter "FTP client (Add-on)" updated. * DELE command added for IP_FTPC_ExecCmd() . 2.10 0 120913 Minor updates and corrections. Chapter "UPnP (Add-on)" added. Chapter "VLAN" added. Chapter "Core functions" updated. * IP_NI_ForceCaps() added. * IP_ARP_ConfigAgeout() added. * IP_ARP_ConfigAgeoutNoReply() added. * IP_ARP_ConfigAgeoutSniff() added. * IP_ARP_ConfigAllowGratuitousARP() added. * IP_ARP_ConfigMaxRetries() added. * IP_ARP_ConfigNumEntries() added. * IP_IFaceIsReadyEx() added. * IP_IGMP_Add() added. * IP_IGMP_JoinGroup() added. * IP_IGMP_LeaveGroup() added. Chapter "UDP zero-copy interface" updated. * IP_UDP_GetFPort() added. Chapter "Web server (Add-on)" updated. * Information regarding file uploads added. OO * More detailed description about multiuple connections added. * IP_WEBS_AddFileTypeHook() added. * IP_WEBS_AddVFileHook() added. * IP_WEBS_ConfigSendVFileHeader() added. * IP_WEBS_ConfigSendVFileHookHeader() added. * IP_WEBS_GetParaValuePtr() added. * IP_WEBS_SendHeader() added. Chapter "PPP/PPPoE (Add-on)" updated. * IP_MODEM_Connect() added. * IP_MODEM_Disconnect() added. * IP_MODEM_GetResponse() added. * IP_MODEM_SendString() added. * IP_MODEM_SendStringEx() added. * IP_MODEM_SetAuthInfo() added. * IP_MODEM_SetConnectTimeout() added. * IP_MODEM_SetInitCallback() added. * IP_MODEM_SetInitString() added. * IP_MODEM_SetSwitchToCmdDelay() added. 2.02c 0 120706 OO Minor updates and corrections. 2.02a 0 120514 OO UM07001 User & Reference Guide for embOS/IP Chapter "AutoIP" added. Chapter "Address Collision Detection" added. (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 5 Software 2.02 Revision 0 Date By Description 120507 Documentation updated for embOS/IP V2 stack. Chapter "API functions" updated. * "IP_GetRawPacketInfo()" added. * "IP_ICMP_Add()" added. OO * "IP_TCP_Add()" added. * "IP_UDP_Add()" added. Chapter "PPP" added. Chapter "NetBIOS" added. 1.60 0 100324 SK Chapter "API functions" updated. * "IP_SetSupportedDuplexModes()" added. Chapter "FTP client" added. Minor updates and corrections. 1.58 0 100204 SK Chapter "SMTP client" updated. Chapter "Configuration" updated. * Section "Required buffers" updated. Minor updates and corrections. 1.56 0 090710 SK Chapter "API functions" updated. * "IP_DNSC_SetMaxTLL()" added. Chapter "Configuring embOS/IP" updated. * Macro "IP_TCP_ACCEPT_CHECKSUM_FFFF" added. 1.54b 0 090603 SK Chapter "Web server (Add-on)" updated. * "IP_WEBS_Process()" updated. * "IP_WEBS_ProcessLast()" added. * "IP_WEBS_OnConnectionLimit()" updated. SK Chapter "API functions" updated. * IP_GetAddrMask() updated. * IP_GetGWMask() updated. * IP_GetIPMask() updated. Chapter "Web server (Add-on)" updated. * Section "Changing the file system type" added. * Section "IP_WEBS_SetFileInfoCallback" updated. 1.54a 1 090520 1.54a 0 090508 SK Chapter "Web server (Add-on)" updated. * IP_WEBS_GetNumParas() added. * IP_WEBS_GetParaValue() added. * IP_WEBS_DecodeAndCopyStr() added. * IP_WEBS_DecodeString() added. * IP_WEBS_SetFileInfoCallback() added. * IP_WEBS_CompareFilenameExt() added. * Section "Dynamic content" added * Section "Common Gateway interface" moved into section "Dynamic content". Chapter "Socket interface" * getpeername() corrected. Chapter "Network interface drivers" updated. 1.54 0 090504 SK Chapter "UDP zero-copy" updated. 1.52 1 090402 SK Chapter "SMTP client" added. SK Chapter "API functions": * IP_SetTxBufferSize() added. * IP_GetIPAddr() updated. * IP_PrintIPAddr() updated. SK Chapter "API functions": * IP_ICMP_SetRxHook() added. * IP_SetRxHook() added. * IP_SOCKET_SetDefaultOptions() added. * IP_SOCKET_SetLimit() added. SK Chapter "Web server (Add-on)": * List of valid values for CGI parameter and values added. Chapter "FTP Server (Add-on)": * Section "FTP server system time" added. * pfGetTimeDate() added. 1.52 1.50 1.42 0 0 0 090223 081210 080821 UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 6 Software Revision Date By Description 1.40 0 080731 SK Chapter "API functions": * IP_TCP_SetConnKeepaliveOpt() added. * IP_TCP_SetRetransDelayRange() added. * IP_SendPacket() added. Chapter "Socket interface": * getsockopt() updated. * setsockopt() updated. Chapter "OS integration": * IP_OS_WaitItemTimed() added. 1.30 1 080610 SK Chapter "FTP server (Add-on)" section "Resource usage" added Chapter "Web server (Add-on)" section "Resource usage" added 1.30 0 080423 SK Chapter "FTP server (Add-on)" added. Chapter "Web server (Add-on)" updated. 1.24 3 080320 SK Chapter "Socket interface": * getpeername added. * getsockname added. 1.24 2 080222 SK Chapter "Device Driver": * NXP LPC23xx/24xx driver added. SK Chapter "HTTP server (Add-on)" updated. Chapter "API functions": * IP_UTIL_EncodeBase64() added. * IP_UTIL_DecodeBase64() added. SK Chapter "HTTP server (Add-on)" added: Chapter "API functions": * IP_AllowBackPressure() added. * IP_GetIPAddr() added. * IP_SendPing() added. * IP_SetDefaultTTL() added. SK Chapter "Introduction": * Section "Components of an Ethernet system" added. Chapter "API functions": * IP_IsIFaceReady() added. * IP_NI_ConfigPHYAddr() added. * IP_NI_ConfigPHYMode() added. * IP_NI_ConfigBasePtr () added. Chapter "Socket interface": * All functions: parameter description enhanced. Chapter "Device drivers" renamed to "Network interface drivers". Chapter "Network interface drivers": * Section "ATMEL AT91SAM7X" added. * Section "ATMEL AT91SAM9260"added. * Section "Davicom DM9000"added. * Section "ST STR912"added. SK Chapter "OS Integration": * IP_OS_Sleep() removed. * IP_OS_Wakeup() removed. * IP_OS_WaitItem added. * IP_OS_SignalItem added. Chapter "Running embOS/IP on target hardware" updated. SK Chapter "Socket interface": * gethostbyname() added. * Structure hostent added. Chapter "Core functions": * IP_PrintIPAddr() added. * IP_DNS_SetServer() added. SK Chapter "DHCP": * IP_DHCPC_Activate() updated. Chapter "Debugging": * Section "Testing stability" added. Chapter "Socket interface": * Section "Error codes" added. 1.24 1.24 1.22 1.22 1.22 1.22 1 0 4 3 2 1 080124 080124 071213 071126 071123 071122 UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 7 Software 1.22 1.00 Revision 0 2 Date 071114 071017 By Description SK Chapter "Introduction": * "Request for comments" enhanced. Chapter "API functions": * IP_AddLogFilter() added. * IP_AddWarnFilter() added. * IP_GetCurrentLinkSpeed() added. * IP_TCP_Set2MSLDelay() added. * select() added. Various function descriptions enhanced. Chapter "API functions" renamed to "core functions". Socket functions removed from chapter "API functions" Chapter "Socket interface" added. Chapter "DHCP" added. Chapter "UDP zero copy" added. Chapter "TCP zero copy" added. Chapter "Glossary" added. Chapter "Index" updated. SK Chapter "Introduction": * Section "Features" enhanced. * Section "Basic concepts" added. * Section "Task and interrupt usage" added. * Section "Further readings" added. Chapter "Running embOS/IP" enhanced. Chapter "API functions": * IP_Init() added. * IP_Task() added. * IP_RxTask() added. * IP_GetVersion() added. * IP_SetLogFilter() added. * IP_SetWarnFilter() added. * IP_Panic() removed. * Structure sockaddr added. * Structure sockaddr_in added. * Structure in_addr added. Chapter "Device driver". * General information updated. * Section "Writing your own driver" added. Chapter "Debugging" added. Chapter "Performance and resource usage" added. Chapter "OS integration" updated. 1.00 1 071002 SK Product name changed to "embOS/IP": Chapter "API functions": * IP_X_Prepare() renamed to IP_X_Config(). * IP_AddBuffers() added. * IP_ConfTCPSpace() added. 1.00 0 070927 SK Initial version. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 8 UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 9 About this document Assumptions This document assumes that you already have a solid knowledge of the following: * * * * The software tools used for building your application (assembler, linker, C compiler) The C programming language The target processor DOS command line If you feel that your knowledge of C is not sufficient, we recommend The C Programming Language by Kernighan and Richie (ISBN 0-13-1103628), which describes the standard in C-programming and, in newer editions, also covers the ANSI C standard. How to use this manual This manual explains all the functions and macros that the product offers. It assumes you have a working knowledge of the C language. Knowledge of assembly programming is not required. Typographic conventions for syntax This manual uses the following typographic conventions: Style Used for Body Body text. Keyword Text that you enter at the command-prompt or that appears on the display (that is system functions, file- or pathnames). Parameter Parameters in API functions. Sample Sample code in program examples. Sample comment Comments in programm examples. Reference Reference to chapters, sections, tables and figures or other documents. GUIElement Buttons, dialog boxes, menu names, menu commands. Emphasis Very important sections. Table 1.1: Typographic conventions UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 10 SEGGER Microcontroller GmbH & Co. KG develops and distributes software development tools and ANSI C software components (middleware) for embedded systems in several industries such as telecom, medical technology, consumer electronics, automotive industry and industrial automation. SEGGER's intention is to cut software development time for embedded applications by offering compact flexible and easy to use middleware, allowing developers to concentrate on their application. Our most popular products are emWin, a universal graphic software package for embedded applications, and embOS, a small yet efficient real-time kernel. emWin, written entirely in ANSI C, can easily be used on any CPU and most any display. It is complemented by the available PC tools: Bitmap Converter, Font Converter, Simulator and Viewer. embOS supports most 8/16/32-bit CPUs. Its small memory footprint makes it suitable for single-chip applications. Apart from its main focus on software tools, SEGGER develops and produces programming tools for flash micro controllers, as well as J-Link, a JTAG emulator to assist in development, debugging and production, which has rapidly become the industry standard for debug access to ARM cores. Corporate Office: http://www.segger.com EMBEDDED SOFTWARE (Middleware) emWin Graphics software and GUI emWin is designed to provide an efficient, processor- and display controller-independent graphical user interface (GUI) for any application that operates with a graphical display. embOS Real Time Operating System embOS is an RTOS designed to offer the benefits of a complete multitasking system for hard real time applications with minimal resources. embOS/IP TCP/IP stack embOS/IP a high-performance TCP/IP stack that has been optimized for speed, versatility and a small memory footprint. United States Office: http://www.segger-us.com SEGGER TOOLS Flasher Flash programmer Flash Programming tool primarily for micro controllers. J-Link JTAG emulator for ARM cores USB driven JTAG interface for ARM cores. J-Trace JTAG emulator with trace USB driven JTAG interface for ARM cores with Trace memory. supporting the ARM ETM (Embedded Trace Macrocell). J-Link / J-Trace Related Software Add-on software to be used with SEGGER's industry standard JTAG emulator, this includes flash programming software and flash breakpoints. emFile File system emFile is an embedded file system with FAT12, FAT16 and FAT32 support. Various Device drivers, e.g. for NAND and NOR flashes, SD/MMC and CompactFlash cards, are available. USB-Stack USB device/host stack A USB stack designed to work on any embedded system with a USB controller. Bulk communication and most standard device classes are supported. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 11 Table of Contents 1 Introduction to embOS/IP...............................................................................................17 1.1 1.2 1.3 1.3.1 1.3.2 1.4 1.5 1.5.1 1.6 1.6.1 1.6.2 1.7 What is embOS/IP ................................................................................... 18 Features................................................................................................. 18 Basic concepts ........................................................................................ 19 embOS/IP structure ................................................................................. 19 Encapsulation.......................................................................................... 20 Tasks and interrupt usage......................................................................... 21 Background information ........................................................................... 24 Components of an Ethernet system ............................................................ 24 Further reading ....................................................................................... 27 Request for Comments (RFC) .................................................................... 27 Related books ......................................................................................... 28 Development environment (compiler)......................................................... 29 2 Running embOS/IP on target hardware.........................................................................31 2.1 2.2 2.3 Step 1: Open an embOS start project......................................................... 33 Step 2: Adding embOS/IP to the start project.............................................. 34 Step 3: Build the project and test it ........................................................... 36 3 Example applications .....................................................................................................37 3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.1.5 3.1.6 3.1.7 3.1.8 41 Overview ................................................................................................ 38 embOS/IP DNS client (OS_IP_DNSClient.c) ................................................. 39 embOS/IP non-blocking connect (OS_IP_NonBlockingConnect.c).................... 39 embOS/IP ping (OS_IP_Ping.c).................................................................. 39 embOS/IP shell (OS_IP_Shell.c) ................................................................ 39 embOS/IP simple server (OS_IP_SimpleServer.c) ........................................ 40 embOS/IP speed client (OS_IP_SpeedClient_TCP.c) ..................................... 40 embOS/IP start (OS_IP_Start.c) ................................................................ 41 embOS/IP UDP discover (OS_IP_UDPDiscover.c / OS_IP_UDPDiscoverZeroCopy.c) 4 Core functions................................................................................................................43 4.1 4.2 4.3 4.4 4.5 4.6 API functions .......................................................................................... 44 Configuration functions............................................................................. 47 Management functions ............................................................................. 99 Network interface configuration and handling functions............................... 105 Other IP stack functions ......................................................................... 111 Stack internal functions, variables and data-structures ............................... 140 5 Socket interface ...........................................................................................................141 5.1 5.2 5.3 API functions ........................................................................................ 142 Socket data structures ........................................................................... 169 Error codes ........................................................................................... 173 6 TCP zero-copy interface ..............................................................................................175 6.1 6.1.1 6.1.2 6.2 TCP zero-copy ....................................................................................... 176 Allocating, freeing and sending packet buffers ........................................... 176 Callback function ................................................................................... 176 Sending data with the TCP zero-copy API.................................................. 177 UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 12 6.2.1 6.2.2 6.2.3 6.3 6.3.1 6.3.2 6.4 Allocating a packet buffer ........................................................................177 Filling the allocated buffer with data .........................................................177 Sending the packet.................................................................................177 Receiving data with the TCP zero-copy API ................................................178 Writing a callback function.......................................................................178 Registering the callback function ..............................................................178 API functions .........................................................................................179 7 UDP zero-copy interface..............................................................................................185 7.1 7.1.1 7.1.2 7.2 7.2.1 7.2.2 7.2.3 7.3 7.3.1 7.3.2 7.4 UDP zero-copy .......................................................................................186 Allocating, freeing and sending packet buffers............................................186 Callback function....................................................................................186 Sending data with the UDP zero-copy API ..................................................187 Allocating a packet buffer ........................................................................187 Filling the allocated buffer with data .........................................................187 Sending the packet.................................................................................187 Receiving data with the UDP zero-copy API................................................188 Writing a callback function.......................................................................188 Registering the callback function ..............................................................188 API functions .........................................................................................189 8 RAW zero-copy interface .............................................................................................205 8.1 8.1.1 8.1.2 8.2 8.2.1 8.2.2 8.2.3 8.3 8.3.1 8.3.2 8.4 RAW zero-copy ......................................................................................206 Allocating, freeing and sending packet buffers............................................206 Callback function....................................................................................206 Sending data with the RAW zero-copy API .................................................207 Allocating a packet buffer ........................................................................207 Filling the allocated buffer with data .........................................................207 Sending the packet.................................................................................207 Receiving data with the RAW zero-copy API ...............................................209 Writing a callback function.......................................................................209 Registering the callback function ..............................................................209 API functions .........................................................................................210 9 DHCP client .................................................................................................................223 9.1 9.2 DHCP backgrounds .................................................................................224 API functions .........................................................................................225 10 DHCP server (Add-on)...............................................................................................235 10.1 10.2 10.3 10.3.1 10.3.2 10.3.3 DHCP backgrounds .................................................................................236 API functions .........................................................................................237 DHCP server resource usage ....................................................................245 ROM usage on an ARM7 system ...............................................................245 ROM usage on a Cortex-M3 system ..........................................................245 RAM usage ............................................................................................245 11 AutoIP ........................................................................................................................247 11.1 11.2 11.3 11.3.1 11.3.2 11.3.3 embOS/IP AutoIP backgrounds ................................................................248 API functions .........................................................................................249 AutoIP resource usage ............................................................................254 ROM usage on an ARM7 system ...............................................................254 ROM usage on a Cortex-M3 system ..........................................................254 RAM usage ............................................................................................254 12 Address Collision Detection .......................................................................................255 12.1 12.2 12.3 12.4 embOS/IP ACD backgrounds....................................................................256 API functions .........................................................................................257 ACD data structures ...............................................................................260 ACD resource usage ...............................................................................261 UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 13 12.4.1 12.4.2 12.4.3 ROM usage on an ARM7 system............................................................... 261 ROM usage on a Cortex-M3 system .......................................................... 261 RAM usage ........................................................................................... 261 13 UPnP (Add-on)...........................................................................................................263 13.1 13.2 13.3 13.4 13.4.1 13.5 13.6 13.6.1 13.6.2 13.6.3 embOS/IP UPnP .................................................................................... 264 Feature list ........................................................................................... 265 Requirements........................................................................................ 266 UPnP backgrounds ................................................................................. 267 Using UPnP to advertise your service in the network................................... 267 API functions ........................................................................................ 275 UPnP resource usage.............................................................................. 277 ROM usage on an ARM7 system............................................................... 277 ROM usage on a Cortex-M3 system .......................................................... 277 RAM usage ........................................................................................... 277 14 VLAN..........................................................................................................................279 14.1 14.2 14.3 14.4 14.5 14.5.1 14.5.2 14.5.3 embOS/IP VLAN .................................................................................... 280 Feature list ........................................................................................... 281 VLAN backgrounds................................................................................. 282 API functions ........................................................................................ 283 VLAN resource usage ............................................................................. 285 ROM usage on an ARM7 system............................................................... 285 ROM usage on a Cortex-M3 system .......................................................... 285 RAM usage ........................................................................................... 285 15 Network interface drivers ...........................................................................................287 15.1 15.1.1 15.1.2 15.1.3 15.2 15.2.1 15.2.2 15.2.3 15.2.4 15.2.5 15.2.6 15.2.7 15.2.8 15.2.9 15.3 15.3.1 General information ............................................................................... 288 MAC address filtering ............................................................................. 288 Checksum computation in hardware ......................................................... 288 Ethernet CRC computation ...................................................................... 288 Available network interface drivers........................................................... 289 ATMEL AT91CAP9 .................................................................................. 290 ATMEL AT91RM9200 .............................................................................. 295 ATMEL AT91SAM7X................................................................................ 299 ATMEL AT91SAM9260 ............................................................................ 303 DAVICOM DM9000/DM9000A .................................................................. 306 FREESCALE ColdFire MCF5329 ................................................................. 309 NXP LPC17xx ........................................................................................ 312 NXP LPC23xx / 24xx .............................................................................. 314 ST STR912 ........................................................................................... 316 Writing your own driver .......................................................................... 318 Device driver functions ........................................................................... 320 16 Configuring embOS/IP ...............................................................................................325 16.1 16.1.1 16.1.2 16.1.3 16.2 16.2.1 16.2.2 Runtime configuration ............................................................................ 326 IP_X_Configure()................................................................................... 326 Driver handling ..................................................................................... 327 Memory and buffer assignment................................................................ 328 Compile-time configuration ..................................................................... 330 Compile-time configuration switches ........................................................ 330 Debug level .......................................................................................... 331 17 Web server (Add-on)..................................................................................................333 17.1 17.2 17.3 17.4 17.4.1 embOS/IP web server ............................................................................ 334 Feature list ........................................................................................... 335 Requirements........................................................................................ 336 HTTP backgrounds ................................................................................. 337 HTTP communication basics .................................................................... 337 UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 14 17.4.2 17.5 17.5.1 17.5.2 17.5.3 17.6 17.6.1 17.6.2 17.7 17.7.1 17.7.2 17.8 17.8.1 17.9 17.9.1 17.10 17.10.1 17.11 17.12 17.13 17.13.1 17.13.2 17.13.3 HTTP status codes ..................................................................................338 Using the web server sample ...................................................................339 Using the Windows sample ......................................................................340 Running the web server example on target hardware ..................................340 Changing the file system type ..................................................................341 Dynamic content ....................................................................................342 Common Gateway Interface (CGI) ............................................................342 Virtual files............................................................................................344 Authentication .......................................................................................346 Authentication example...........................................................................347 Configuration of the authentication ...........................................................348 Form handling .......................................................................................349 Simple form processing sample ................................................................350 File upload ............................................................................................353 Simple form upload sample .....................................................................353 Configuration.........................................................................................355 Compile time configuration switches .........................................................355 API functions .........................................................................................357 Web server data structures......................................................................393 Resource usage .....................................................................................403 ROM usage on an ARM7 system ...............................................................403 ROM usage on a Cortex-M3 system ..........................................................403 RAM usage:...........................................................................................403 18 SMTP client (Add-on).................................................................................................405 18.1 18.2 18.3 18.4 18.5 18.5.1 18.6 18.7 18.8 18.8.1 18.8.2 embOS/IP SMTP client ............................................................................406 Feature list............................................................................................407 Requirements ........................................................................................408 SMTP backgrounds .................................................................................409 Configuration.........................................................................................411 Compile time configuration switches .........................................................411 API functions .........................................................................................412 SMTP client data structures .....................................................................414 Resource usage .....................................................................................422 Resource usage on an ARM7 system .........................................................422 Resource usage on a Cortex-M3 system ....................................................422 19 FTP server (Add-on) ..................................................................................................423 19.1 19.2 19.3 19.4 19.4.1 19.4.2 19.4.3 19.4.4 19.5 19.5.1 19.5.2 19.6 19.7 19.7.1 19.7.2 19.8 19.9 19.10 19.10.1 19.10.2 19.10.3 embOS/IP FTP server..............................................................................424 Feature list............................................................................................425 Requirements ........................................................................................426 FTP basics .............................................................................................427 Active mode FTP ....................................................................................428 Passive mode FTP ..................................................................................429 FTP reply codes......................................................................................430 Supported FTP commands .......................................................................431 Using the FTP server sample ....................................................................432 Using the Windows sample ......................................................................432 Running the FTP server example on target hardware...................................432 Access control........................................................................................433 Configuration.........................................................................................439 Compile time configuration switches .........................................................439 FTP server system time...........................................................................440 API functions .........................................................................................442 FTP server data structures.......................................................................445 Resource usage .....................................................................................448 ROM usage on an ARM7 system ...............................................................448 ROM usage on a Cortex-M3 system ..........................................................448 RAM usage:...........................................................................................448 UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 15 20 FTP client (Add-on)....................................................................................................449 20.1 20.2 20.3 20.4 20.4.1 20.4.2 20.5 20.5.1 20.6 20.7 20.8 20.8.1 20.8.2 20.8.3 embOS/IP FTP client .............................................................................. 450 Feature list ........................................................................................... 451 Requirements........................................................................................ 452 FTP basics ............................................................................................ 453 Passive mode FTP .................................................................................. 454 Supported FTP client commands .............................................................. 455 Configuration ........................................................................................ 456 Compile time configuration switches......................................................... 456 API functions ........................................................................................ 457 FTP client data structures ....................................................................... 465 Resource usage ..................................................................................... 466 ROM usage on an ARM7 system............................................................... 466 ROM usage on a Cortex-M3 system .......................................................... 466 RAM usage: .......................................................................................... 466 21 TFTP client/server......................................................................................................467 21.1 21.2 21.3 21.4 21.4.1 21.5 21.6 21.6.1 21.6.2 21.6.3 embOS/IP TFTP ..................................................................................... 468 Feature list ........................................................................................... 469 TFTP basics........................................................................................... 470 Using the TFTP samples.......................................................................... 471 Running the TFTP server example on target hardware ................................ 471 API functions ........................................................................................ 472 Resource usage ..................................................................................... 477 ROM usage on an ARM7 system............................................................... 477 ROM usage on a Cortex-M3 system .......................................................... 477 RAM usage: .......................................................................................... 477 22 PPP / PPPoE (Add-on) ..............................................................................................479 22.1 22.2 22.3 22.4 22.5 22.6 22.7 22.8 22.9 22.10 22.10.1 22.10.2 22.10.3 22.11 22.11.1 22.11.2 embOS/IP PPP/PPPoE ............................................................................. 480 Feature list ........................................................................................... 481 Requirements........................................................................................ 482 PPP backgrounds ................................................................................... 483 API functions ........................................................................................ 484 PPPoE functions..................................................................................... 485 PPP functions ........................................................................................ 491 Modem functions ................................................................................... 497 PPP data structures................................................................................ 509 PPPoE resource usage ............................................................................ 515 ROM usage on an ARM7 system............................................................... 515 ROM usage on a Cortex-M3 system .......................................................... 515 RAM usage ........................................................................................... 515 PPP resource usage................................................................................ 516 ROM usage on an ARM7 system............................................................... 516 RAM usage ........................................................................................... 516 23 NetBIOS (Add-on)......................................................................................................517 23.1 23.2 23.3 23.4 23.5 23.6 23.6.1 23.6.2 23.6.3 embOS/IP NetBIOS................................................................................ 518 Feature list ........................................................................................... 519 Requirements........................................................................................ 520 NetBIOS backgrounds ............................................................................ 521 API functions ........................................................................................ 522 Resource usage ..................................................................................... 527 ROM usage on an ARM7 system............................................................... 527 ROM usage on a Cortex-M3 system .......................................................... 527 RAM usage ........................................................................................... 527 24 SNTP client (Add-on) .................................................................................................529 24.1 embOS/IP SNTP client ............................................................................ 530 UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 16 24.2 24.3 24.4 24.4.1 24.4.2 24.5 24.6 24.6.1 24.6.2 24.6.3 Feature list............................................................................................531 Requirements ........................................................................................532 SNTP backgrounds .................................................................................533 The NTP timestamp ................................................................................533 The epoch problem (year 2036 problem) ...................................................534 API functions .........................................................................................535 Resource usage .....................................................................................539 ROM usage on an ARM7 system ...............................................................539 ROM usage on a Cortex-M3 system ..........................................................539 RAM usage ............................................................................................539 25 Debugging..................................................................................................................541 25.1 25.2 25.3 25.4 25.5 Message output .....................................................................................542 Testing stability .....................................................................................543 API functions .........................................................................................544 Message types .......................................................................................550 Using a network sniffer to analyse communication problems ........................552 26 OS integration ............................................................................................................553 26.1 26.2 26.2.1 General information................................................................................554 OS layer API functions ............................................................................555 Examples ..............................................................................................555 27 Performance & resource usage .................................................................................557 27.1 27.1.1 27.1.2 27.2 27.2.1 27.2.2 Memory footprint ...................................................................................558 ARM7 system.........................................................................................558 Cortex-M3 system ..................................................................................559 Performance ..........................................................................................560 ARM7 system.........................................................................................560 Cortex-M3 system ..................................................................................561 28 Appendix A - File system abstraction layer................................................................563 28.1 28.2 28.2.1 28.2.2 28.2.3 28.2.4 File system abstraction layer....................................................................564 File system abstraction layer function table................................................565 emFile interface .....................................................................................567 Read-only file system .............................................................................568 Using the read-only file system ................................................................569 Windows file system interface ..................................................................570 29 Glossary.....................................................................................................................571 UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 17 Chapter 1 Introduction to embOS/IP This chapter provides an introduction to using embOS/IP. It explains the basic concepts behind embOS/IP. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 18 CHAPTER 1 1.1 Introduction to embOS/IP What is embOS/IP embOS/IP is a CPU-independent TCP/IP stack. embOS/IP is a high-performance library that has been optimized for speed, versatility and small memory footprint. 1.2 Features embOS/IP is written in ANSI C and can be used on virtually any CPU. Some features of embOS/IP: * * * * * * * * * * * * * * * * * * Standard socket interface. High performance. Small footprint. No configuration required. Runs "out-of-the-box". Very simple network interface driver structure. Works seamlessly with embOS in multitasking environment. Zero data copy for ultra fast performance. Non-blocking versions of all functions. Connections limited only by memory availability. Delayed ACKs. Handling gratuitous ARP packets Support for VLAN BSD style "keep-alive" option. Support for messages and warnings in debug build. Drivers for most common Ethernet controllers available. Support for driver side (hardware) checksum computation. Royalty-free. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 19 1.3 Basic concepts 1.3.1 embOS/IP structure embOS/IP is organized in different layers, as shown in the following illustration. Application layer DHCP, DNS, FTP, HTTP, POP3, SMTP, TELNET, SSL, ... Transport layer TCP / UDP Network layer IP, ICMP, IGMP, ARP, RARP, ... Link layer Ethernet (IEEE 802.3), ... A short description of each layer's functionality follows below. Application layer The application layer is the interface between embOS/IP and the user application. It uses the embOS/IP API to transmit data over an TCP/IP network. The embOS/IP API provides functions in BSD (Berkeley Software Distribution) socket style, such as connect(), bind(), listen(), etc. Transport layer The transport layer provides end-to-end communication services for applications. The two relevant protocols of the Transport layer protocol are the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP). TCP is a reliable connectionoriented transport service. It provides end-to-end reliability, resequencing, and flow control. UDP is a connectionless transport service. Internet layer All protocols of the transport layer use the Internet Protocol (IP) to carry data from source host to destination host. IP is a connectionless service, providing no end-toend delivery guarantees. IP datagrams may arrive at the destination host damaged, duplicated, out of order, or not at all. The transport layer is responsible for reliable delivery of the datagrams when it is required. The IP protocol includes provision for addressing, type-of-service specification, fragmentation and reassembly, and security information. Link layer The link layer provides the implementation of the communication protocol used to interface to the directly-connected network. A variety of communication protocols have been developed and standardized. The most commonly used protocol is Ethernet (IEEE 802.3). In this version of embOS/IP only Ethernet is supported. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 20 CHAPTER 1 1.3.2 Introduction to embOS/IP Encapsulation The four layers structure is defined in [RFC 1122]. The data flow starts at the application layer and goes over the transport layer, the network layer, and the link layer. Every protocol adds an protocol-specific header and encapsulates the data and header from the layer above as data. On the receiving side, the data will be extracted in the complementary direction. The opposed protocols do not know which protocol on the above and below layers are used. The following illustration shows the encapsulation of data within an UDP datagram within an IP packet. UDP header IP header Frame header Data Application layer UDP data Transport layer Network layer IP data Frame data UM07001 User & Reference Guide for embOS/IP Frame footer Link layer (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 21 1.4 Tasks and interrupt usage embOS/IP can be used in an application in three different ways. * * * One task dedicated to the stack (IP_Task) Two tasks dedicated to the stack (IP_Task, IP_RxTask) Zero tasks dedicated to the stack (Superloop) The default task structure is one task dedicated to the stack. The priority of the management tasks IP_Task (and IP_RxTask if available) should be higher then the priority of an application task which uses the stack. One task dedicated to the stack To use one task dedicated to the stack is the simplest way to use the TCP/IP stack. It is called IP_Task and handles housekeeping operations, resending and handling of incoming packets. The "Read packet" operation is performed from within the ISR. Because the "Read packet" operation is called directly from the ISR, no additional task is required. The length of the interrupt latency will be extended for the time period which is required to process the "Read packet" operation. Refer to IP_Task() on page 102 for more information and an example about how to include the IP_Task into your embOS project. Interrupt (ISR) embOS/IP Rx Task Routine / Action Application tasks IP stack IP_OnRx() IP stack / Driver App. task 1 ... App. t ask n IP_Task IP_Exec() UM07001 User & Reference Guide for embOS/IP Read packet (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 22 CHAPTER 1 Introduction to embOS/IP Two tasks dedicated to the stack Two tasks are dedicated to the stack. The first task is called the IP_Task and handles housekeeping operations, resends, and handling of incoming packets. The second is called IP_RxTask and handles the "Read packet" operation. IP_RxTask is waked up from the interrupt service routine, if new packets are available. The interrupt latency is not extended, because the "Read packet" operation has been moved from the interrupt service routine to IP_RxTask. Refer to IP_Task() on page 102 and IP_RxTask() on page 103 for more information. IP_RxTask has to have a higher priority as IP_Task as it is treated as interrupt in task form and might not be interrupted by IP_Task or any other IP task. Interrupt (ISR) embOS/IP Rx Task Routine / Action Application tasks IP stack IP_OnRx() IP stack / Driver App. task 1 ... UM07001 User & Reference Guide for embOS/IP App. t ask n IP_Task IP_RxTask IP_Exec() Read packet (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 23 Zero tasks dedicated to the stack (Superloop) embOS/IP can also be used without any additional task for the stack, if an application task calls IP_Exec() periodically. The "Read packet" operation is performed from within the ISR. Because the "Read packet" operation is called directly from the ISR, no additional task is required. The length of the interrupt latency will be extended for the time period which is required to process the "Read packet" operation. Interrupt (ISR) embOS/IP Rx Task Routine / Action Application tasks IP stack IP_OnRx() IP stack / Driver App. task 1 ... App. t ask n IP_Exec() Read packet Task priorities Task priorities are independent from other task priorities. However as soon as a task calls an IP API it has to obey the following priority rules: 1. 2. 3. The IP_RxTask (if used at all) has to have the highest priority of all tasks that make use of the IP API and has to have a higher priority than the IP_Task . The IP_Task has to have a higher task priority than any other task that makes use of the IP API. It has to have a lower priority than the IP_RxTask (if used at all). All tasks that make use of the IP API have to have a task priority below the IP_Task . Tasks that do not use the IP API do not have to obey these rules and their task priorities can be freely chosen. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 24 CHAPTER 1 1.5 Introduction to embOS/IP Background information 1.5.1 Components of an Ethernet system Main parts of an Ethernet system are the Media Access Controller (MAC) and the Physical device (PHY). The MAC handles generating and parsing physical frames and the PHY handles how this data is actually moved to or from the wire. MCUs with integrated MAC Some modern MCUs (for example, the ATMEL SAM7X or the ST STR912) include the MAC and use the internal RAM to store the Ethernet data. The following block diagram illustrates such a configuration. PHY MAC Connector CPU RAM External Ethernet controllers with MAC and PHY Chips without integrated MAC can use fully integrated single chip Ethernet MAC controller with integrated PHY and a general processor interface. The following schematic illustrates such a configuration. MAC PHY Connector CPU RAM UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 25 1.5.1.1 MII / RMII: Interface between MAC and PHY The MAC communicates with the PHY via the Media Independent Interface (MII) or the Reduced Media Independent Interface (RMII). The MII is defined in IEEE 802.3u. The RMII is a subset of the MII and is defined in the RMI specification. The MII/RMII can handle control over the PHY which allows for selection of such transmission criteria as line speed, duplex mode, etc. In theory, up to 32 PHYs can be connected to a single MAC. In praxis, this is never done; only one PHY is connected. In order to allow multiple PHYs to be connected to a single MAC, individual 5-bit addresses have to be assigned to the different PHYs. If only one PHY is connected, the embOS/IP driver automatically finds the address of it. The standard defines 32 16-bit PHY registers. The first 6 are defined by the standard. Register BMCR BSR PHYSID1 PHYSID2 ANAR LPAR Description Basic Mode Control Register Basic Mode Status Register PHYS ID 1 PHYS ID 2 Auto-Negotiation Advertisement Register Link Partner Ability register Table 1.1: Standardized registers of the MAC/PHY interface The drivers automatically recognize any PHY connected, no manual configuration of PHY address is required. The MII and RMII interface are capable of both 10Mb/s and 100Mb/s data rates as described in the IEEE 802.3u standard. TX_CLK TX_EN TXD 0-1 TXD 2-3 PHYCLK CRS COL MAC MDIO PHY MDC RX_CLK RXD 0-1 RXD 2-3 RX_DV RX_ER The intent of the RMII is to provide a reduced pin count alternative to the IEEE 802.3u MII. It uses 2 bits for transmit (TXD0 and TXD1) and two bits for receive (RXD0 and RXD1). There is a Transmit Enable (TX_EN), a Receive Error (RX_ER), a Carrier Sense (CRS), and a 50 MHz Reference Clock (TX_CLK) for 100Mb/s data rate. The pins used by the MII and RMII interfaces are described in the following table. Signal TX_CLK TX_EN TXD[0:1] TXD[2:3] PHYCLK MII Transmit Clock (25 MHz) Transmit Enable 4-bit Transmit Data PHY Clock Output RMII Reference Clock (50 MHz) Transmit Enable 2-bit Transmit Data N/A PHY Clock Output Table 1.2: MII / RMII comparison UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 26 CHAPTER 1 Signal CRS COL MDIO MDC RX_CLK RXD[0:1] RXD[2:3] RX_DV RX_ER MII RMII Carrier Sense Collision Detect Management data I/O Data Transfer Timing Reference Clock Receive Clock 4-bit Receive Data Data Valid Receive Error Introduction to embOS/IP N/A N/A Management data I/O Data Transfer Timing Reference Clock N/A 2-bit Receive Data N/A Carrier Sense/Data Valid Receive Error Table 1.2: MII / RMII comparison UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 27 1.6 Further reading This guide explains the usage of the embOS/IP protocol stack. It describes all functions which are required to build a network application. For a deeper understanding about how the protocols of the internet protocol suite works use the following references. The following Request for Comments (RFC) define the relevant protocols of the internet protocol suite and have been used to build the protocol stack. They contain all required technical specifications. The listed books are simpler to read as the RFCs and give a general survey about the interconnection of the different protocols. 1.6.1 Request for Comments (RFC) RFC# [RFC 768] [RFC 791] [RFC 792] [RFC 793] [RFC 821] [RFC 826] [RFC 951] [RFC 959] [RFC 1034] [RFC 1035] [RFC 1042] [RFC 1122] [RFC 1123] [RFC 1661] [RFC 1939] [RFC 2131] [RFC 2616] Description UDP - User Datagram Protocol Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc768.txt IP - Internet Protocol Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc791.txt ICMP - Internet Control Message Protocol Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc792.txt TCP - Transmission Control Protocol Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc793.txt SMTP - Simple Mail Transfer Protocol Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc826.txt ARP - Ethernet Address Resolution Protocol Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc826.txt BOOTP - Bootstrap Protocol Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc951.txt FTP - File Transfer Protocol Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc959.txt DNS - Domain names - concepts and facilities Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc1034.txt DNS - Domain names - implementation and specification Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc1035.txt IE-EEE - Transmission of IP datagrams over IEEE 802 networks Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc1042.txt Requirements for Internet Hosts - Communication Layers Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc1122.txt Requirements for Internet Hosts - Application and Support Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc1123.txt PPP - Point-to-Point Protocol Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc1661.txt POP3 - Post Office Protocol - Version 3 Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc1939.txt DHCP - Dynamic Host Configuration Protocol Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc2131.txt HTTP - Hypertext Transfer Protocol -- HTTP/1.1 Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc2616.txt UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 28 CHAPTER 1 1.6.2 * * * * * Introduction to embOS/IP Related books [Comer] - Computer Networks and Internets, Douglas E Comer and Ralph E. Droms - ISBN: 978-0131433519 [Tannenbaum] - Computer Networks, Andrew S. Tannenbaum ISBN: 978-0130661029 [StevensV1] - TCP/IP Illustrated, Volume 1, W. Richard Stevens ISBN: 978-0201633467. [StevensV2] - TCP/IP Illustrated, Volume 2, W. Richard Stevens and Gary R. Wright - ISBN: 978-0201633542. [StevensV3] - TCP/IP Illustrated, Volume 3, W. Richard Stevens ISBN: 978-0201634952. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 29 1.7 Development environment (compiler) The CPU used is of no importance; only an ANSI-compliant C compiler complying with at least one of the following international standard is required: * * * ISO/IEC/ANSI 9899:1990 (C90) with support for C++ style comments (//) ISO/IEC 9899:1999 (C99) ISO/IEC 14882:1998 (C++) If your compiler has some limitations, let us know and we will inform you if these will be a problem when compiling the software. Any compiler for 16/32/64-bit CPUs or DSPs that we know of can be used; most 8-bit compilers can be used as well. A C++ compiler is not required, but can be used. The application program can therefore also be programmed in C++ if desired. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 30 UM07001 User & Reference Guide for embOS/IP CHAPTER 1 Introduction to embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 31 Chapter 2 Running embOS/IP on target hardware This chapter explains how to integrate and run embOS/IP on your target hardware. It explains this process step-by-step. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 32 CHAPTER 2 Running embOS/IP on target hardware Integrating embOS/IP The embOS/IP default configuration is preconfigured with valid values, which matches the requirements of the most applications. embOS/IP is designed to be used with embOS, SEGGER's real-time operating system. We recommend to start with an embOS sample project and include embOS/IP into this project. We assume that you are familiar with the tools you have selected for your project (compiler, project manager, linker, etc.). You should therefore be able to add files, add directories to the include search path, and so on. In this document the IAR Embedded Workbench (R) IDE is used for all examples and screenshots, but every other ANSI C toolchain can also be used. It is also possible to use make files; in this case, when we say "add to the project", this translates into "add to the make file". Procedure to follow Integration of embOS/IP is a relatively simple process, which consists of the following steps: * * * Step 1: Open an embOS project and compile it. Step 2: Add embOS/IP to the start project Step 3: Compile the project UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 33 2.1 Step 1: Open an embOS start project We recommend that you use one of the supplied embOS start projects for your target system. Compile the project and run it on your target hardware. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 34 CHAPTER 2 2.2 Running embOS/IP on target hardware Step 2: Adding embOS/IP to the start project Add all source files in the following directory to your project: * * * Config IP UTIL (optional) The Config folder includes all configuration files of embOS/IP. The configuration files are preconfigured with valid values, which match the requirements of most applications. Add the hardware configuration IP_Config_<TargetName>.c supplied with the driver shipment. If your hardware is currently not supported, use the example configuration file and the driver template to write your own driver. The example configuration file and the driver template is located in the Sample\Driver\Template folder. The Util folder is an optional component of the embOS/IP shipment. It contains optimized MCU and/or compiler specific files, for example a special memcopy function. Replace BSP.c and BSP.h of your embOS start project Replace the BSP.c source file and the BSP.h header file used in your embOS start project with the one which is supplied with the embOS/IP shipment. Some drivers require a special functions which initializes the network interface of the driver. This function is called BSP_ETH_Init(). It is used to enable the ports which are connected to the network hardware. All network interface driver packages include the BSP.c and BSP.h files irrespective if the BSP_ETH_Init() function is implemented. Configuring the include path The include path is the path in which the compiler looks for include files. In cases where the included files (typically header files, .h) do not reside in the same directory as the C file to compile, an include path needs to be set. In order to build the project with all added files, you will need to add the following directories to your include path: * * * Config Inc IP UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 35 Select the start application For quick and easy testing of your embOS/IP integration, start with the code found in the folder Application. Add one of the applications to your project (for example OS_IP_SimpleServer.c). UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 36 2.3 CHAPTER 2 Running embOS/IP on target hardware Step 3: Build the project and test it Build the project. It should compile without errors and warnings. If you encounter any problem during the build process, check your include path and your project configuration settings. To test the project, download the output into your target and start the application. By default, ICMP is activated. This means that you could ping your target. Open the command line interface of your operating system and enter ping <TargetAddress>, to check if the stack runs on your target. The target should answer all pings without any error. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 37 Chapter 3 Example applications In this chapter, you will find a description of each embOS/IP example application. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 38 3.1 CHAPTER 3 Example applications Overview Various example applications for embOS/IP are supplied. These can be used for testing the correct installation and proper function of the device running embOS/IP. The following start application files are provided: File Description OS_IP_DNSClient.c Demonstrates the use of the integrated DNS client. OS_IP_NonBlockingConnect.c Demonstrates how to connect to a server using non-blocking sockets. OS_IP_Ping.c Demonstrates how to send ICMP echo requests and how to process ICMP replies in application. OS_IP_Shell.c Demonstrates using the IP-shell to diagnose the IP stack. OS_IP_SimpleServer.c Demonstrates setup of a simple server which simply sends back the target system tick for every character received. OS_IP_SpeedClient_TCP.c Demonstrates the TCP send and receive performance of the device running embOS/IP. Refer to embOS/IP speed client (OS_IP_SpeedClient_TCP.c) on page 40 for detailed information. OS_IP_Start.c Demonstrates use of the IP stack without any server or client program. To ping the target, use the command line: ping <target-ip> where <target-ip> represents the IP address of the target, which depends on the configuration and is usually 192.168.5.1 if the DHCP client is not enabled. OS_IP_UDPDiscover.c Demonstrates setup of a simple UDP application which replies to UDP broadcasts. The application sends an answer for every received discover packet. The related host application sends discover packets as UDP broadcasts and waits for the feedback of the targets which are available in the subnet. OS_IP_UDPDiscoverZeroCopy.c Demonstrates setup of a simple UDP application which replies to UDP broadcasts. The application uses the the embOS/IP zero-copy interface. It sends an answer for every received discover packet. The related host application sends discover packets as UDP broadcasts and waits for the feedback of the targets which are available in the subnet. Table 3.1: embOS/IP example applications The example applications for the target-side are supplied in source code in the Application directory. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 39 3.1.1 embOS/IP DNS client (OS_IP_DNSClient.c) The embOS/IP DNS client resolves a hostname (for example, segger.com) to an IP address and outputs the resolved address via terminal I/O. 3.1.2 embOS/IP non-blocking connect (OS_IP_NonBlockingConnect.c) The embOS/IP non-blocking connect sample demonstrates how to connect to a server using non-blocking sockets. The target tries to connect to TCP server with an non-blocking socket. The sample can be used with any TCP server independent of the application which is listening on the port. The client only opens a TCP connection to the server and closes it without any further communication. The terminal I/O output in your debugger should be similar to the following out: Connecting using non-blocking socket... Successfully connected after 2ms! 1 of 1 tries were successful. Connecting using non-blocking socket... Successfully connected after 1ms! 2 of 2 tries were successful. 3.1.3 embOS/IP ping (OS_IP_Ping.c) The embOS/IP ping sample demonstrates how to send ICMP echo requests and how to process received ICMP packets in your application. A callback function is implemented which outputs a message if an ICMP echo reply or an ICMP echo request has been received. To test the embOS/IP ICMP implementation, you have to perform the following steps: 1. 2. Customize the Local defines, configurable section of OS_IP_Ping.c. Change the macro HOST_TO_PING accordant to your configuration. For example, if the Windows host PC which you want to ping use the IP address 192.168.5.15, change the HOST_TO_PING macro to 0xC0A8050F. Open the command line interface and enter: ping [IP_ADDRESS _OF_YOUR_TARGET_RUNNING_EMBOSIP] The terminal I/O output in your debugger should be similar to the following out: ICMP ICMP ICMP ICMP ICMP ICMP ICMP ICMP ICMP ICMP 3.1.4 echo echo echo echo echo echo echo echo echo echo reply received! request received! reply received! reply received! reply received! reply received! request received! reply received! reply received! reply received! embOS/IP shell (OS_IP_Shell.c) The embOS/IP shell server is a task which opens TCP-port 23 (telnet) and waits for a connection. The actual shell server is part of the stack, which keep the application program nice and small. The shell server task can be added to any application and should be used to retrieve status information while the target is running. To connect UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 40 CHAPTER 3 Example applications to the target, use the command line: telnet <target-ip> where <target-ip> represents the IP address of the target, which depends on the configuration and is usually 192.168.5.230 if the DHCP client is not enabled. 3.1.5 embOS/IP simple server (OS_IP_SimpleServer.c) Demonstrates setup of a simple server which simply sends back the target system tick for every character received. It opens TCP-port 23 (telnet) and waits for a connection. To connect to the target, use the command line: telnet <target-ip> where <target-ip> represents the IP address of the target, which depends on the configuration and is usually 192.168.5.230 if the DHCP client is not enabled. 3.1.6 embOS/IP speed client (OS_IP_SpeedClient_TCP.c) The embOS/IP speed client is a small application to detect the TCP send and receive performance of embOS/IP on your hardware. 3.1.6.1 Running the embOS/IP speed client To test the embOS/IP performance, you have to perform the following steps: 1. 2. 3. 4. Start the Windows speed test server. The example application for the host-side is supplied as executable and in source code in the Windows\SpeedTestServer\ directory. To run the speed test server, simply start the executable, for example by double-clicking it or open the supplied Visual C project and compile and start the application. Add OS_IP_SpeedClient.c to your project. Customize the Local defines, configurable section of OS_IP_SpeedClient.c. Change the macro SERVER_IP_ADDR accordant to your configuration. For example, if the Windows host PC running the speed test server uses the IP address 192.168.5.15, change the SERVER_IP_ADDR macro to 0xC0A8050F. If you have changed the port which the Windows host application uses to listen, change the macro SERVER_PORT accordingly. Build and download the speed client into your target. The target connects to the UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 41 server and starts the transmission. 3.1.7 embOS/IP start (OS_IP_Start.c) Demonstrates use of the IP stack without any server or client program. To ping the target, use the command line: ping <target-ip> where <target-ip> represents the IP address of the target, which depends on the configuration and is usually 192.168.5.230 if the DHCP client is not enabled. 3.1.8 embOS/IP UDP discover (OS_IP_UDPDiscover.c / OS_IP_UDPDiscoverZeroCopy.c) To test the embOS/IP UDP discover example, you have to perform the following steps: 1. 2. 3. 4. Start the Windows UDP discover example application. The example application for the host-side is supplied as executable and in source code in the Windows\UDPDiscover\ directory. To run the UDP discover example, simply start the executable, for example by double-clicking it or open the supplied Visual C project and compile and start the application. Add OS_IP_UDPDiscover.c to your project. Customize the Local defines, configurable section of OS_IP_UDPDiscover.c. By default, the example uses port 50020. If you have changed the port that the Windows host application uses, change the macro PORT accordingly. Build and download the UDP discover example into your target. The target sends an answer for every received discover packet. The related host application sends discover packets as UDP broadcasts and waits for the feedback of the targets which are available in the subnet. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 42 UM07001 User & Reference Guide for embOS/IP CHAPTER 3 Example applications (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 43 Chapter 4 Core functions In this chapter, you will find a description of each embOS/IP core function. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 44 4.1 CHAPTER 4 Core functions API functions The table below lists the available API functions within their respective categories. Function Description Configuration functions IP_AddBuffers() Adds buffers to the TCP/IP stack. Adds an Ethernet interface to the IP_AddEtherInterface() stack. IP_AddLoopbackInterface() Adds an Ethernet loopback interface. IP_AllowBackpressure() Activates back pressure. IP_AssignMemory() Assigns memory. IP_ARP_ConfigAgeout() Configures the ARP cache timeout. Configures the ARP cache timeout for IP_ARP_ConfigAgeoutNoReply() request sent without a reply yet. Configures the ARP cache timeout for IP_ARP_ConfigAgeoutSniff() entries sniffed from incoming packets. Configures allow/disallow of using IP_ARP_ConfigAllowGratuitousARP() information from gratuitous ARP packets. Configure max. packets pending for IP_ARP_ConfigMaxPending() reply to an ARP entry. IP_ARP_ConfigMaxRetries() Configures max. ARP request resends. Configures number of ARP cache IP_ARP_ConfigNumEntries() entries. Configures the send and receive IP_ConfigTCPSpace() space. IP_ConfigOffCached2Uncached() Configures cached to uncached offset. IP_DisableIPRxChecksum() Disables IP checksum verification. Retrieves first DNS server from first IP_DNS_GetServer() interface. Retrieves a DNS server from an interIP_DNS_GetServerEx() face. IP_DNS_SetMaxTTL() Sets the maximum TTL of a DNS entry. IP_DNS_SetServer() Sets the DNS server. IP_DNS_SetServerEx() Sets a DNS server for an interface. IP_EnableIPRxChecksum() Enables ICMP checksum verification. IP_GetPrimaryIFace() Retrieves the stacks primary interface. IP_ICMP_Add() Adds ICMP to the stack. IP_ICMP_DisableRxChecksum() Disables ICMP checksum verification. IP_ICMP_EnableRxChecksum() Enables ICMP checksum verification. IP_IGMP_Add() Adds IGMP to the stack. IP_IGMP_JoinGroup() Joins an IGMP group. IP_IGMP_LeaveGroup() Leaves an IGMP group. Select polled mode for the network IP_NI_ConfigPoll() interface. Configures the Tx buffer size used by IP_NI_SetTxBufferSize() the network interface driver. IP_RAW_Add() Adds RAW socket support to the stack. Sets the address mask of the first IP_SetAddrMask() interface interface. Sets the address mask of the selected IP_SetAddrMaskEx() interface. Table 4.1: embOS/IP API function overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 45 Function Description Sets the gateway address of the selected interface. Sets the hardware address of the first IP_SetHWAddr() interface. Sets the hardware address of the IP_SetHWAddrEx() selected interface. Sets the maximum transmission unit IP_SetMTU() of an interface. IP_SetPrimaryIFace() Sets primary interface of the stack. IP_SetSupportedDuplexModes() Sets the supported duplex modes. IP_SetTTL() Sets the TTL of an IP packet. Configure the select() timeout multiIP_SOCKET_ConfigSelectMultiplicator() plicator. Sets the socket options which should IP_SOCKET_SetDefaultOptions() be enabled by default. Sets the maximum number of availIP_SOCKET_SetLimit() able sockets. IP_TCP_Add() Adds TCP to the stack. IP_TCP_DisableRxChecksum() Disables TCP checksum verification. IP_TCP_EnableRxChecksum() Enables TCP checksum verification. IP_TCP_Set2MSLDelay() Sets the maximum segment lifetime. IP_TCP_SetConnKeepaliveOpt() Sets the keepalive options. IP_TCP_SetRetransDelayRange() Sets retransmission delay range. IP_UDP_Add() Adds UDP to the stack. IP_UDP_DisableRxChecksum() Disables UDP checksum verification. IP_UDP_EnableRxChecksum() Enables UDP checksum verification. Management functions IP_DeInit() Deinitialization function of the stack. IP_Init() Initialization function of the stack. IP_Task() Main task for starting the stack. Reads all available packets and sleeps IP_RxTask() until a new packet is received. Checks if any packet has been IP_Exec() received and handles timers. Network interface configuration and handling functions IP_NI_ConfigPHYAddr() Configures the PHY address. IP_NI_ConfigPHYMode() Configures the PHY mode. Select polled mode for the network IP_NI_ConfigPoll() interface. Allows forcing of hardware capabiliIP_NI_ForceCaps() ties. Configures the Tx buffer size used by IP_NI_SetTxBufferSize() the network interface driver. Other IP stack functions Adds a hook that will be executed right IP_AddAfterInitHook() after IP_Init(). Adds a hook that will be executed if an IP_AddStateChangeHook() interface state changes from outside. IP_Alloc() Allocate memory from stack. IP_Connect() Calls a previously set callback. IP_Disconnect() Calls a previously set callback. IP_Err2Str() Converts error value to string. IP_SetGWAddr() Table 4.1: embOS/IP API function overview (Continued) UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 46 CHAPTER 4 Core functions Function IP_Free() IP_GetAddrMask() IP_GetCurrentLinkSpeed() IP_GetCurrentLinkSpeedEx() IP_GetGWAddr() IP_GetHWAddr() IP_GetIPAddr() IP_GetIPPacketInfo() IP_GetRawPacketInfo() IP_GetVersion() IP_ICMP_SetRxHook() IP_IFaceIsReady() IP_IFaceIsReadyEx() IP_IsExpired() IP_PrintIPAddr() IP_ResolveHost() IP_SendPacket() IP_SendPing() IP_SendPingEx() IP_SetIFaceConnectHook() IP_SetIFaceDisconnectHook() IP_SetRxHook() Description Free previously allocated memory. Returns the IP address and the subnet mask of the device. Returns the current link speed. Returns the current link speed of the selected interface. Returns the gateway address of the device. Returns the hardware address (MAC) of the device. Returns the IP address of the device. Returns the start address of the data part of an IP packet. Returns the start address of the raw data part of an IP packet. Returns the version number of embOS/IP. Sets a hook function which will be called if target receives a ping packet. Checks if the interface is ready. Checks if the specified interface is ready. Checks if a timestamp has expired. Convert an 4 byte IP address to a dots-and-number string. Resolves a host name via DNS server. Sends a user defined packet on the interface. Sends an ICMP Echo Request. Sends an ICMP Echo Request. Sets a connect callback. Sets a disconnect callback. Sets a hook function that handles all received packets. Table 4.1: embOS/IP API function overview (Continued) UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 47 4.2 Configuration functions UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 48 CHAPTER 4 4.2.1 Core functions IP_AddBuffers() Description Adds buffers to the TCP/IP stack. This is a configuration function, typically called from IP_X_Config(). It needs to be called 2 times, one per buffer size. Prototype void IP_AddBuffers ( int NumBuffers, int BytesPerBuffer ); Parameter Parameter NumBuffers BytesPerBuffer Description [IN] The number of buffers. [IN] Size of buffers in bytes. Table 4.2: IP_AddBuffers() parameter list Additional information embOS/IP requires small and large buffers. We recommend to define the size of the big buffers to 1536 to allow a full Ethernet packet to fit. The small buffers are used to store packets which encapsulates no or few application data like protocol management packets (TCP SYNs, TCP ACKs, etc.). We recommend to define the size of the small buffers to 256 bytes. Example IP_AddBuffers(20, 256); IP_AddBuffers(12, 1536); UM07001 User & Reference Guide for embOS/IP // 20 small buffers, each 256 bytes. // 12 big buffers, each 1536 bytes. (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 49 4.2.2 IP_AddEtherInterface() Description Adds an Ethernet interface. Prototype int IP_AddEtherInterface( const IP_HW_DRIVER * pDriver ); Parameter Parameter pDriver Description [IN] A pointer to a network interface driver structure. Table 4.3: IP_AddEtherInterface() parameter list Additional information Refer to Available network interface drivers on page 289 for a list of available network interface drivers. Return value Zero-based interface index of the newly created interface. Example IP_AddEtherInterface(&IP_Driver_SAM7X); UM07001 User & Reference Guide for embOS/IP // Add Ethernet driver for your hardware (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 50 CHAPTER 4 4.2.3 Core functions IP_AddLoopbackInterface() Description Adds a loopback Ethernet interface. Prototype int IP_AddLoopbackInterface( void ); Return value Zero-based interface index of the newly created interface. Additional information The loopback interface will be added with the pre-configured static IP addr. of 127.0.0.1/8 . Example IP_AddLoopbackInterface(); // Add an Ethernet loopback interface. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 51 4.2.4 IP_AllowBackpressure() Description Allows back pressure if the driver supports this feature. Prototype void IP_AllowBackpressure ( int v ); Parameter Parameter v Description [IN] Zero to disable, 1 to enable back pressure. Table 4.4: IP_AllowBackPressure() parameter list Additional information Back pressure is a window-based flow control mechanism for the half-duplex mode. It is a sort of feedback-based congestion control mechanism. The intent of this mechanism is to prevent loss by providing back pressure to the sending NIC on ports that are going too fast to avoid loss. Back pressure is enabled by default. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 52 CHAPTER 4 4.2.5 Core functions IP_AssignMemory() Description Assigns memory to the TCP/IP stack. Prototype void IP_AssignMemory ( U32 * pMem, U32 NumBytes ); Parameter Parameter pMem NumBytes Description [IN] A pointer to the start of the memory region which should be assigned. [IN] Number of bytes which should be assigned. Table 4.5: IP_AssignMemory() parameter list Additional information IP_AssignMemory() should be the first function which is called in IP_X_Config(). The amount of RAM required depends on the configuration and the respective application purpose. The assigned memory pool is required for the socket buffers, memory buffers, etc. Example #define ALLOC_SIZE 0x8000 U32 _aPool[ALLOC_SIZE / 4]; // Size of memory dedicated to the stack in bytes // Memory area used by the stack. IP_AssignMemory(_aPool, sizeof(_aPool)); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 53 4.2.6 IP_ARP_ConfigAgeout() Description Configures the timeout for cached ARP entries. Prototype void IP_ARP_ConfigAgeout ( U32 Ageout ); Parameter Parameter Ageout Description [IN] Timeout in ms after which an entry is deleted from the ARP cache. Default: 120s. Table 4.6: IP_ARP_ConfigAgeout() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 54 CHAPTER 4 4.2.7 Core functions IP_ARP_ConfigAgeoutNoReply() Description Configures the timeout for an ARP entry that has been added due to sending an ARP request to the network that has not been answered yet. Prototype void IP_ARP_ConfigAgeoutNoReply ( U32 Ageout ); Parameter Parameter Ageout Description [IN] Timeout in ms after which an entry is deleted in case we are still waiting for an ARP response. Default: 3s. Table 4.7: IP_ARP_ConfigAgeoutNoReply() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 55 4.2.8 IP_ARP_ConfigAgeoutSniff() Description Configures the timeout for cached ARP entries that have been cached from incoming packets instead from sending an ARP request. Prototype void IP_ARP_ConfigAgeoutSniff ( U32 Ageout ); Parameter Parameter Ageout Description [IN] Timeout in ms after which an entry is deleted from the ARP cache. Table 4.8: IP_ARP_ConfigAgeoutSniff() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 56 CHAPTER 4 4.2.9 Core functions IP_ARP_ConfigAllowGratuitousARP() Description Configures if gratuitous ARP packets from other network members are allowed to update the ARP cache. Prototype void IP_ARP_AllowGratuitousARP ( U8 OnOff ); Parameter Parameter OnOff Description [IN] 0: Off; 1: On. Default: On. Table 4.9: IP_ConfigAllowGratuitousARP() parameter list Additional information Gratuitous ARP packets allow the network to update itself by sending out informations about changes regarding IP and hardware ID assignments. As this behaviour helps the network to become more stable and helps to manage itself it is on by default. In case you consider gratuitous ARP packets as a security IP_ARP_ConfigAllowGratuitousARP() can be used to disallow this behaviour. UM07001 User & Reference Guide for embOS/IP risk (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 57 4.2.10 IP_ARP_ConfigMaxPending() Description Configures the maximum number packets that can be queued waiting for an ARP reply. Prototype void IP_ARP_ConfigMaxPending ( unsigned NumPackets ); Parameter Parameter NumPackets Description [IN] Maximum number of packets that can be pending for one ARP entry. Default: 3. Table 4.10: IP_ARP_ConfigMaxPending() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 58 CHAPTER 4 Core functions 4.2.11 IP_ARP_ConfigMaxRetries() Description Configures how often an ARP request is resent before considering the request failed. Prototype void IP_ARP_ConfigConfigMaxRetries ( unsigned Retries ); Parameter Parameter Retries Description [IN] Number of retries for sending an ARP request. Table 4.11: IP_ARP_ConfigMaxRetries() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 59 4.2.12 IP_ARP_ConfigNumEntries() Description Configures the maximum number of possible entries in the ARP cache. Prototype int IP_ARP_ConfigNumEntries ( unsigned NumEntries ); Parameter Parameter NumEntries Description [IN] Number of max. entries in ARP cache list. Table 4.12: IP_ARP_ConfigNumEntries() parameter list Retrurn value 0: O.K., the stack will try to allocate the requested number of entries. -1: Error, called after IP_Init(). Additional information IP_ARP_ConfigNumEntries() has to be called before IP_Init(). UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 60 CHAPTER 4 Core functions 4.2.13 IP_ConfigTCPSpace() Description Configures the size of the TCP send and receive window size. Prototype void IP_ConfigTCPSpace ( unsigned SendSpace, unsigned RecvSpace ); Parameter Parameter SendSpace RecvSpace Description [IN] Size of the send window. [IN] Size of the receive window. Table 4.13: IP_ConfTCPSpace() parameter list Additional information The receive window size is the amount of unacknowledged data a sender can send to the receiver on a particular TCP connection before it gets an acknowledgment. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 61 4.2.14 IP_ConfigOffCached2Uncached() Description Configures the offset from a cached memory area to its uncached equivalent for uncached access. Prototype void IP_ConfigOffCached2Uncached ( I32 Off ); Parameter Parameter Off Description [IN] Offset from cached to uncached area. Can be negative if uncached area is before cached area. Table 4.14: IP_ConfigOffCached2Uncached() parameter list Additional information This function needs to be called in case the microcontroller is utilizing a MMU setup with the data area that is used by default being cached. In this case the stack needs to know where it can bypass the cache to write hardware related data such as driver descriptors that will be accessed by a DMA. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 62 CHAPTER 4 Core functions 4.2.15 IP_DisableIPRxChecksum() Description Disables checksum verification of the checksum in the IP header for incoming packets. Prototype void IP_DisableIPRxChecksum ( U8 IFace ); Parameter Parameter IFace Description [IN] Zero-based interface index. Table 4.15: IP_DisableIPRxChecksum() parameter list Additional information In a typical network typically all data contained in a transferred frame has already been verified by the hardware checking the trasmitted frames checksum and it is unlikely that data within this frame is corrupted if the frame checksum was verified as being correct. Therefore for optimization reasons the checksum calculation might be disabled. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 63 4.2.16 IP_DNS_GetServer() Description Retrieves the first DNS server configured of the first interface. Prototype U32 IP_DNS_GetServer ( void ); Return value First DNS server address of first interface. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 64 CHAPTER 4 Core functions 4.2.17 IP_DNS_GetServerEx() Description Retrieves a DNS server configured for an interface. Prototype void IP_DNS_GetServerEx ( U8 IFace, U8 DNSIndex, U8 *pAddr, int *pAddrLen ); Parameter Parameter IFace DNSIndex pAddr pAddrLen Description [IN] Zero-based index of available network interfaces. -1 when out of range. [IN] Zero-based index of the server to retrieve from interface. -1 when out of range. [OUT] Pointer to U32 variable (for IPv4) to store the DNS addr. [OUT] Length of DNS addr. in bytes. Typically 4 for IPv4. Table 4.16: IP_DNS_GetServerEx() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 65 4.2.18 IP_DNS_SetMaxTTL() Description Sets the maximum Time To Live (TTL) of a DNS entry in seconds. Prototype void IP_DNS_SetMaxTTL( U32 TTL ); Parameter Parameter TTL Description [IN] Maximum TTL of a DNS entry in seconds. Table 4.17: IP_DNS_SetMaxTTL() parameter list Additional information The real TTL is the minimum of TTL and the TTL specified by the DNS server for the entry. The embOS/IP default for the maximum TTL of an DNS entry is 600 seconds. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 66 CHAPTER 4 Core functions 4.2.19 IP_DNS_SetServer() Description Sets the DNS server that should be used. Prototype void IP_DNS_SetServer ( U32 DNSServerAddr ); Parameter Parameter DNSServerAddr Description [IN] Address of DNS server. Table 4.18: IP_DNS_SetServer() parameter list Additional information If a DHCP server is used for configuring your target, IP_DNS_SetServer() should not be called. The DNS server settings are normally part of the DHCP configuration setup. The DNS server has to be defined before calling gethostbyname() to resolve an internet address. Refer to gethostbyname() on page 148 for detailed information about resolving an internet address. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 67 4.2.20 IP_DNS_SetServerEx() Description Sets one DNS server for an interface. Prototype void IP_DNS_SetServerEx ( U8 IFace, U8 DNSIndex, const U8 *pDNSAddr, int AddrLen ); Parameter Parameter IFace DNSIndex pDNSAddr AddrLen Description [IN] Zero-based interface index. [IN] Zero-based DNS server index of the interface. [IN] Pointer to memory location holding the DNS addr. to set. Typically an 4-byte IP addr. [IN] Length of IP addr. of server. Typically 4-bytes. Table 4.19: IP_DNS_SetServerEx() parameter list Additional information If a DHCP server is used for configuring your target, IP_DNS_SetServerEx() should not be called. The DNS server settings are normally part of the DHCP configuration setup. The DNS server has to be defined before calling gethostbyname() to resolve an internet address. Refer to gethostbyname() on page 148 for detailed information about resolving an internet address. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 68 CHAPTER 4 Core functions 4.2.21 IP_EnableIPRxChecksum() Description Enables checksum verification of the checksum in the IP header for incoming packets. Prototype void IP_EnableIPRxChecksum ( U8 IFace ); Parameter Parameter IFace Description [IN] Zero-based interface index. Table 4.20: IP_EnableIPRxChecksum() parameter list Additional information In a typical network typically all data contained in a transferred frame has already been verified by the hardware checking the trasmitted frames checksum and it is unlikely that data within this frame is corrupted if the frame checksum was verified as being correct. Therefore for optimization reasons the checksum calculation might be disabled. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 69 4.2.22 IP_GetPrimaryIFace() Description Retrieves the currently set primary interface index of the system. Prototype int IP_GetPrimaryIFace( void ); Return value Primary interface index set in the system. If not previously configured with IP_SetPrimaryIFace() on page 84 the default is 0. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 70 CHAPTER 4 Core functions 4.2.23 IP_ICMP_Add() Description Adds ICMP to the stack. Prototype void IP_ICMP_Add ( void ); Additional information IP_ICMP_Add() adds ICMP to the stack. The function should be called during the initialization of the stack. In the supplied sample configuration files IP_ICMP_Add() is called from IP_X_Config(). If you remove the call of IP_ICMP_Add(), the ICMP code will not be available in your application. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 71 4.2.24 IP_ICMP_DisableRxChecksum() Description Disables checksum verification of the checksum in the ICMP header for incoming packets. Prototype void IP_ICMP_DisableRxChecksum ( U8 IFace ); Parameter Parameter IFace Description [IN] Zero-based interface index. Table 4.21: IP_ICMP_DisableRxChecksum() parameter list Additional information In a typical network typically all data contained in a transferred frame has already been verified by the hardware checking the trasmitted frames checksum and it is unlikely that data within this frame is corrupted if the frame checksum was verified as being correct. Therefore for optimization reasons the checksum calculation might be disabled. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 72 CHAPTER 4 Core functions 4.2.25 IP_ICMP_EnableRxChecksum() Description Enables checksum verification of the checksum in the ICMP header for incoming packets. Prototype void IP_ICMP_EnableRxChecksum ( U8 IFace ); Parameter Parameter IFace Description [IN] Zero-based interface index. Table 4.22: IP_ICMP_EnableRxChecksum() parameter list Additional information In a typical network typically all data contained in a transferred frame has already been verified by the hardware checking the trasmitted frames checksum and it is unlikely that data within this frame is corrupted if the frame checksum was verified as being correct. Therefore for optimization reasons the checksum calculation might be disabled. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 73 4.2.26 IP_IGMP_Add() Description Adds IGMP to the stack. Prototype void IP_IGMP_Add ( void ); Additional information IP_IGMP_Add() adds IGMP (Internet Group Management Protocol) to the stack. The function should be either called during the initialization of the stack by adding it to your IP_X_Config() or should be called after IP_Init(). If you remove the call of IP_IGMP_Add(), the ICMP code will not be available in your application. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 74 CHAPTER 4 Core functions 4.2.27 IP_IGMP_JoinGroup() Description Joins an IGMP group. Prototype void IP_IGMP_JoinGroup ( unsigned IFace, IP_ADDR GroupIP ); Parameter Parameter IFace GroupIP Description [IN] Zero-based index of available interfaces. [IN] IGMP group IP addr. Table 4.23: IP_IGMP_JoinGroup() parameter list Additional information Calling this function should be only done after IP_init() as we relay on an already configured HW addr. Multicast is a technique to distribute a packet to multiple receivers in a network by sending only one packet. Handling of who will receive the packet is not done by the sender but instead is done by network hardware such as routers or switched hubs that will dupplicate the packet and send it to everyone that participates the chosen group. The target does not actively participate by sending a join request. The network hardware periodically broadcasts membership querys throughout the network that have to be answered with a membership report in case we want to participate in the queried group. Example /* Excerpt from IP.h */ #define IP_IGMP_MCAST_ALLHOSTS_GROUP #define IP_IGMP_MCAST_ALLRPTS_GROUP 0xE0000001uL 0xE0000016uL // 224.0.0.1 // 224.0.0.22, IGMPv3 /* Excerpt from the UPnP code */ #define SSDP_IP 0xEFFFFFFA // Simple service discovery protocol IP, 239.255.255.250 IP_IGMP_Add(); // IGMP is needed for UPnP // // Join IGMP ALLHOSTS group and IGMP group for SSDP // IP_IGMP_JoinGroup(0, IP_IGMP_MCAST_ALLHOSTS_GROUP); IP_IGMP_JoinGroup(0, SSDP_IP); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 75 4.2.28 IP_IGMP_LeaveGroup() Description Leaves an IGMP group. Prototype void IP_IGMP_LeaveGroup ( unsigned IFace, IP_ADDR GroupIP ); Parameter Parameter IFace GroupIP Description [IN] Zero-based index of available interfaces. [IN] IGMP group IP addr. Table 4.24: IP_IGMP_LeaveGroup() parameter list Additional information The target does not actively participate by sending a leave request. Instead the target will change its filters to no longer receiving IGMP membership querys and will then be removed from the list of participants of the network hardware after a timeout. Example /* Excerpt from IP.h */ #define IP_IGMP_MCAST_ALLHOSTS_GROUP #define IP_IGMP_MCAST_ALLRPTS_GROUP 0xE0000001uL 0xE0000016uL // 224.0.0.1 // 224.0.0.22, IGMPv3 /* Sample for leaving IGMP groups used for UPnP */ #define SSDP_IP 0xEFFFFFFA // Simple service discovery protocol IP, 239.255.255.250 // // Leave IGMP ALLHOSTS group and IGMP group for SSDP // IP_IGMP_LeaveGroup(0, IP_IGMP_MCAST_ALLHOSTS_GROUP); IP_IGMP_LeaveGroup(0, SSDP_IP); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 76 CHAPTER 4 Core functions 4.2.29 IP_PHY_DisableCheck() Description Disables PHY checks. Prototype void IP_PHY_DisableCheck ( U32 Mask ); Parameter Parameter Mask Description Bitmask of checks to disable. At this time only the following values are accepted: 0: All checks active. 1: Disable PHY ID check. Table 4.25: IP_PHY_DisableCheck() parameter list Additional information The generic PHY module is designed to work with fully IEEE 802.3u compliant Ethernet PHYs. Almost any PHY is compatible to this minimum standard. However there are PHYs that state in documentation that they are compliant but lack some of the standard registers that have to be present due to this standard. The PHY initialization may fail due to the lack of these registers if when they are part of the functional validation. Using this function some checks can be disabled if they do not work with the PHY you are using. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 77 4.2.30 IP_RAW_Add() Description Adds RAW socket support to the stack. Prototype void IP_RAW_Add ( void ); Additional information IP_RAW_Add() adds RAW socket support to the stack. The function should be called during the initialization of the stack. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 78 CHAPTER 4 Core functions 4.2.31 IP_SetAddrMask() Description Sets the IP address and subnet mask of the first interface of the stack (interface 0). Prototype void IP_SetAddrMask ( U32 Addr, U32 Mask ); Parameter Parameter Addr Mask Description [IN] 4-byte IPv4 address. [IN] Subnet mask. Table 4.26: IP_SetAddrMask() parameter list Additional information The address mask should only be set if no DHCP server is used to obtain IP address, subnet mask and default gateway. Refer to chapter DHCP client on page 223 for detailed information about the usage of the embOS/IP DHCP client. Example IP_SetAddrMask(0xC0A80505, 0xFFFF0000); UM07001 User & Reference Guide for embOS/IP // IP: 192.168.5.5 // Subnet mask: 255.255.0.0 (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 79 4.2.32 IP_SetAddrMaskEx() Description Sets the IP address and subnet mask of an interface. Prototype void IP_SetAddrMaskEx ( U8 IFace, U32 Addr, U32 Mask ); Parameter Parameter IFace Addr Mask Description [IN] Interface Id. [IN] 4-byte IPv4 address. [IN] Subnet mask. Table 4.27: IP_SetAddrMaskEx() parameter list Additional information The address mask should only be set if no DHCP server is used to obtain IP address, subnet mask and default gateway. Refer to chapter DHCP client on page 223 for detailed information about the usage of the embOS/IP DHCP client. Example IP_SetAddrMaskEx(0, 0xC0A80505, 0xFFFF0000); UM07001 User & Reference Guide for embOS/IP // Interface: 0 // IP: 192.168.5.5 // Subnet mask: 255.255.0.0 (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 80 CHAPTER 4 Core functions 4.2.33 IP_SetGWAddr() Description Sets the default gateway address of the selected interface. Prototype void IP_SetGWAddr ( U8 IFace, U32 Addr ); Parameter Parameter IFace Addr Description [IN] Interface Id. [IN] 4-byte gateway address. Table 4.28: IP_SetGWAddrEx() parameter list Additional information The address mask should only be set if no DHCP server is used to obtain IP address, subnet mask and default gateway. Refer to chapter DHCP client on page 223 for detailed information about the usage of the embOS/IP DHCP client. Example IP_SetGWAddr(0, 0xC0A80101); UM07001 User & Reference Guide for embOS/IP // Interface: 0 // IPv4 address of the GW: 192.168.1.1 (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 81 4.2.34 IP_SetHWAddr() Description Sets the Media Access Control address (MAC) of the first interface (interface 0). Prototype void IP_SetHWAddr( const U8 * pHWAddr ); Parameter Parameter pHWAddr Description [IN] 6-byte MAC address. Table 4.29: IP_SetHWAddr() parameter list Additional information The MAC address needs to be unique for production units. Example IP_SetHWAddr("\x00\x22\x33\x44\x55\x66"); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 82 CHAPTER 4 Core functions 4.2.35 IP_SetHWAddrEx() Description Sets the Media Access Control address (MAC) of the selected interface. Prototype void IP_SetHWAddr( const U8 * pHWAddr ); Parameter Parameter pHWAddr Description [IN] 6-byte MAC address. Table 4.30: IP_SetHWAddrEx() parameter list Additional information The MAC address needs to be unique for production units. Example IP_SetHWAddrEx(0, "\x00\x22\x33\x44\x55\x66"); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 83 4.2.36 IP_SetMTU() Description Allows to set the Maximum Transmission Unit (MTU) of the selected interface. Prototype void IP_SetMTU( U8 IFace, U32 Mtu ); Parameter Parameter IFace Mtu Description [IN] Zero-based index of available network interfaces. [IN] Size of maximum transmission unit in bytes. Table 4.31: IP_SetMTU() parameter list Additional information The Maximum Transmission Unit is the MTU from an IP standpoint, so the size of the IP-packet without local net header. A typical value for ethernet is 1500, since the maximum size of an Ethernet packet is 1518 bytes. Since Ethernet uses 12 bytes for MAC addresses, 2 bytes for type and 4 bytes for CRC, 1500 bytes "payload" remain. The minimum size of the MTU is 576 according to RFC 879. Refer to [RFC 879] - TCP - The TCP Maximum Segment Size and Related Topics for more information about the MTU. A smaller MTU size is effective for TCP connections only, it does not affect UDP connections. All TCP connections are guaranteed to work with any MTU in the permitted range of 576 - 1500 bytes. The advantage of a smaller MTU is that smaller packets are sent in TCP communication, resulting in reduced RAM requirements, especially if the window size is also reduced. The disadvantage is a loss of communication speed. Note: In the supplied embOS/IP example configurations, the MTU is used to configure the maximum packet size that the stack can handle. This means that if you lower the MTU (for example, set it to 576 bytes), the stack can only handle packets up to that size. If you plan to use larger UDP packets, change the configuration according to your requirements. For further information about the configuration of the stack, refer to Configuring embOS/IP on page 325. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 84 CHAPTER 4 Core functions 4.2.37 IP_SetPrimaryIFace() Description Allows to set the primary interface index of the system Prototype int IP_SetPrimaryIFace( int IFaceId ); Parameter Parameter IFaceId Description [IN] Zero-based interface index to use as primary interface of the system. Table 4.32: IP_SetPrimaryIFace() parameter list Return value 0: O.K. < 0: Error, interface index might not be valid. Additional information The primary interface will be be handled with priority in several situations e.g. finding a suitable DNS server to resolve a host name. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 85 4.2.38 IP_SetSupportedDuplexModes() Description Allows to set the allowed Duplex modes. Prototype int IP_SetSupportedDuplexModes( unsigned Unit, unsigned DuplexMode); Parameter Parameter Unit DuplexMode Description [IN] Zero-based index of available network interfaces. [IN] OR-combination of one or more of the following valid values. Table 4.33: IP_SetSupportedDuplexModes() parameter list Valid values for parameter DuplexMode Value IP_PHY_MODE_10_HALF IP_PHY_MODE_10_FULL IP_PHY_MODE_100_HALF IP_PHY_MODE_100_FULL UM07001 User & Reference Guide for embOS/IP Description Support Support Support Support 10 Mbit half-duplex 10 Mbit full-duplex 100 Mbit half-duplex 100 Mbit full-duplex (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 86 CHAPTER 4 Core functions 4.2.39 IP_SetTTL() Description Sets the default value for the Time-To-Live IP header field. Prototype void IP_SetTTL ( int v ); Parameter Parameter v Description [IN] Time-To-Live value. Table 4.34: IP_SetTTL() parameter list Additional information By default, the TTL (Time-To-Live) is 64. The TTL field length of the IP is 8 bits. The maximum value of the TTL field is therefore 255. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 87 4.2.40 IP_SOCKET_ConfigSelectMultiplicator() Description Allows to configure the multiplicator for the timeout parameter of select() on page 159. Prototype void IP_SOCKET_ConfigSelectMultiplicator( U32 v ); Parameter Parameter v Description [IN] Multiplicator to be used. Default 1. Table 4.35: IP_SOCKET_ConfigSelectMultiplicator() parameter list Additional information By default the select() timeout is given in ticks of 1 ms. The UNIX standard takes the timeout in a structue including seconds. The multiplicator can be configured but as it is more common for an embedded system we will stick to units of 1 tick (typically 1 ms) for the default. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 88 CHAPTER 4 Core functions 4.2.41 IP_SOCKET_SetDefaultOptions() Description Allows to set the maximum transmission unit (MTU) of an interface. Prototype void IP_SOCKET_SetDefaultOptions ( U16 v ); Parameter Parameter v Description [IN] Socket options which should be enabled. By default, keepalive (SO_KEEPALIVE) socket option is enabled. Refer to setsockopt() on page 164 for a list of supported socket options. Table 4.36: IP_SOCKET_SetDefaultOptions() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 89 4.2.42 IP_SOCKET_SetLimit() Description Sets the maximum number of available sockets. Prototype void IP_SOCKET_SetLimit ( unsigned Limit ); Parameter Parameter Limit Description [IN] Sets a limit on number of sockets which can be created. The embOS/IP default is 0 which means that no limit is set. Table 4.37: IP_SOCKET_SetLimit() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 90 CHAPTER 4 Core functions 4.2.43 IP_TCP_Add() Description Adds TCP to the stack. Prototype void IP_TCP_Add ( void ); Additional information IP_TCP_Add() adds TCP to the stack. The function should be called during the initialization of the stack. In the supplied sample configuration files IP_TCP_Add() is called from IP_X_Config(). If you remove the call of IP_TCP_Add(), the TCP code will not be available in your application. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 91 4.2.44 IP_TCP_DisableRxChecksum() Description Disables checksum verification of the checksum in the TCP header for incoming packets. Prototype void IP_TCP_DisableRxChecksum ( U8 IFace ); Parameter Parameter IFace Description [IN] Zero-based interface index. Table 4.38: IP_TCP_DisableRxChecksum() parameter list Additional information In a typical network typically all data contained in a transferred frame has already been verified by the hardware checking the trasmitted frames checksum and it is unlikely that data within this frame is corrupted if the frame checksum was verified as being correct. Therefore for optimization reasons the checksum calculation might be disabled. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 92 CHAPTER 4 Core functions 4.2.45 IP_TCP_EnableRxChecksum() Description Enables checksum verification of the checksum in the TCP header for incoming packets. Prototype void IP_TCP_EnableRxChecksum ( U8 IFace ); Parameter Parameter IFace Description [IN] Zero-based interface index. Table 4.39: IP_TCP_EnableRxChecksum() parameter list Additional information In a typical network typically all data contained in a transferred frame has already been verified by the hardware checking the trasmitted frames checksum and it is unlikely that data within this frame is corrupted if the frame checksum was verified as being correct. Therefore for optimization reasons the checksum calculation might be disabled. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 93 4.2.46 IP_TCP_Set2MSLDelay() Description Sets the maximum segment lifetime (MSL). Prototype void IP_TCP_Set2MSLDelay( unsigned v ); Parameter Parameter v Description [IN] Maximum segment lifetime. The embOS/IP default is 2 seconds. Table 4.40: IP_TCP_Set2MSLDelay() parameter list Additional information The maximum segment lifetime is the amount of time any segment can exist in the network before being discarded. This time limit is constricted. When TCP performs an active close the connection must stay in TIME_WAIT (2MSL) state for twice the MSL after sending the final ACK. Refer to [RFC 793] - TCP - Transmission Control Protocol for more information about TCP states. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 94 CHAPTER 4 Core functions 4.2.47 IP_TCP_SetConnKeepaliveOpt() Description Sets the keepalive options. Prototype void IP_TCP_SetConnKeepaliveOpt( U32 U32 U32 U32 Init, Idle, Period, MaxRep ); Parameter Parameter Init Idle Period MaxRep Description [IN] Maximum time after TCP-connection open (response to SYN) in ms in case no data transfer takes place. The embOS/IP default is 10 seconds. [IN] Time of TCP-inactivity before first keepalive probe is sent in ms. The embOS/IP default is 10 seconds. [IN] Time of TCP-inactivity between keepalive probes in ms. The embOS/IP default is 10 seconds. [IN] Number of keepalive probes before we give up and close the connection. The embOS/IP default is 8 repetitions. Table 4.41: IP_TCP_SetConnKeepaliveOpt() parameter list Additional information Keepalives are not part of the TCP specification, since they can cause good connections to be dropped during transient failures. For example, if the keepalive probes are sent during the time that an intermediate router has crashed and is rebooting, TCP will think that the client's host has crashed, which is not what has happened. Nevertheless, the keepalive feature is very useful for embedded server applications that might tie up resources on behalf of a client, and want to know if the client host crashes. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 95 4.2.48 IP_TCP_SetRetransDelayRange() Description Sets the retransmission delay range. Prototype void IP_TCP_SetRetransDelayRange( unsigned RetransDelayMin, unsigned RetransDelayMax ); Parameter Parameter RetransDelayMin RetransDelayMax Description [IN] Minimum time before first retransmission. The embOS/IP default is 200 ms. [IN] Maximum time to wait before a retransmission. The embOS/IP default is 5 seconds. Table 4.42: IP_TCP_SetRetransDelayRange() parameter list Additional information TCP is a reliable transport layer. One of the ways it provides reliability is for each end to acknowledge the data it receives from the communication partner. But data segments and acknowledgments can get lost. TCP handles this by setting a timeout when it sends data, and if the data is not acknowledged when the timeout expires, it retransmits the data. The timeout and retransmission is the measurement of the round-trip time (RTT) experienced on a given connection. The RTT can change over time, as routes might change and as network traffic changes, and TCP should track these changes and modify its timeout accordingly. IP_TCP_SetRetransDelayRange() should be called if the default limits are not sufficient for your application. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 96 CHAPTER 4 Core functions 4.2.49 IP_UDP_Add() Description Adds UDP to the stack. Prototype void IP_UDP_Add ( void ); Additional information IP_UDP_Add() adds UDP to the stack. The function should be called during the initialization of the stack. In the supplied sample configuration files IP_UDP_Add() is called from IP_X_Config(). If you remove the call of IP_UDP_Add(), the UDP code will not be available in your application. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 97 4.2.50 IP_UDP_DisableRxChecksum() Description Disables checksum verification of the checksum in the UDP header for incoming packets. Prototype void IP_UDP_DisableRxChecksum ( U8 IFace ); Parameter Parameter IFace Description [IN] Zero-based interface index. Table 4.43: IP_UDP_DisableRxChecksum() parameter list Additional information In a typical network typically all data contained in a transferred frame has already been verified by the hardware checking the trasmitted frames checksum and it is unlikely that data within this frame is corrupted if the frame checksum was verified as being correct. Therefore for optimization reasons the checksum calculation might be disabled. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 98 CHAPTER 4 Core functions 4.2.51 IP_UDP_EnableRxChecksum() Description Enables checksum verification of the checksum in the TCP header for incoming packets. Prototype void IP_TCP_EnableRxChecksum ( U8 IFace ); Parameter Parameter IFace Description [IN] Zero-based interface index. Table 4.44: IP_TCP_EnableRxChecksum() parameter list Additional information In a typical network typically all data contained in a transferred frame has already been verified by the hardware checking the trasmitted frames checksum and it is unlikely that data within this frame is corrupted if the frame checksum was verified as being correct. Therefore for optimization reasons the checksum calculation might be disabled. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 99 4.3 Management functions UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 100 CHAPTER 4 4.3.1 Core functions IP_DeInit() Description De-initializes the TCP/IP stack. Prototype void IP_DeInit ( void ); Additional information IP_DeInit() de-initializes the IP stack. This function should be the very last embOS/ IP function called and is typically not needed if you do not need to shutdown your whole application for a special reason. De-initialization should be done in the exact reversed order of intialization. This means terminating any created task that uses the IP API, terminating the IP_RxTask (if used), terminating the IP_Task and finally calling IP_DeInit() to close down the stack. The whole de-initialization should be done with Ethernet interrupts disabled and task switching disabled to prevent the de-initialization being interrupted by an Ethernet event. De-init has to be supported by the driver as well. If your driver does not yet support IP_DeInit() you will end up in IP_Panic() . Please contact our support address and ask for IP_DeInit() support to be added to your driver. Example #include "IP.h" void main(void) { IP_Init(); // // Create IP tasks and use the stack // ... // // Disable Ethernet interrupt // OS_EnterRegion(); // Prevent task switching // // Terminate all application tasks that make use of the IP API // // // Terminate IP_RxTask first (if used) and IP_Task // IP_DeInit(); OS_LeaveRegion(); // Allow task switching } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 101 4.3.2 IP_Init() Description Initializes the TCP/IP stack. Prototype void IP_Init ( void ); Additional information IP_Init() initializes the IP stack and creates resources required for an OS integration. This function must be called before any other embOS/IP function is called. Example #include "IP.h" void main(void) { IP_Init(); /* * Use the stack */ } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 102 CHAPTER 4 4.3.3 Core functions IP_Task() Description Main task for starting the stack. After startup, it settles into a loop handling received packets. This loop sleeps until a packet has been queued in the receive queue; then it should be awakened by the driver which queued the packet. Prototype void IP_Task ( void ); Additional information Implementing this task is the simplest way to include embOS/IP into your project. Typical stack usage is approximately 440 bytes. To be on the safe side set the size of the task stack to 1024 bytes. Note: The priority of task IP_Task should be higher then the priority of an application task which uses the stack. Example #include <stdio.h> #include #include #include #include static static static static "RTOS.h" "BSP.h" "IP.h" "IP_Int.h" OS_STACKPTR int _Stack0[512]; OS_TASK _TCB0; OS_STACKPTR int _IPStack[1024]; OS_TASK _IPTCB; // // // // Task stacks Task-control-blocks Task stacks Task-control-blocks /********************************************************************* * * MainTask */ void MainTask(void); void MainTask(void) { printf("****************************************\nProgram start\n"); IP_Init(); OS_SetPriority(OS_GetTaskID(), 255); // This task has highest prio! OS_CREATETASK(&_IPTCB, "IP_Task", IP_Task, 150, _IPStack); while (1) { BSP_ToggleLED(1); OS_Delay (200); } } /********************************************************** * * main */ void main(void) { BSP_Init(); BSP_SetLED(0); OS_IncDI(); /* Initially disable interrupts */ OS_InitKern(); /* initialize OS */ OS_InitHW(); /* initialize Hardware for OS */ OS_CREATETASK(&_TCB0, "MainTask", MainTask, 100, _Stack0); OS_Start(); } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 103 4.3.4 IP_RxTask() Description The task reads all available packets from the network interface and sleeps until a new packet is received. Prototype void IP_RxTask ( void ); Additional information This task is optional. Refer to Tasks and interrupt usage on page 21 for detailed information about the task and interrupt handling of embOS/IP. Typical stack usage is approximately 150 bytes. To be on the safe side set the size of the task stack to 1024 bytes. Note: The priority of task IP_RxTask() should be higher then the priority of an application task which uses the stack. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 104 CHAPTER 4 4.3.5 Core functions IP_Exec() Description Checks if the driver has received a packet and handles timers. Prototype void IP_Exec ( void ); Additional information This function is normally called from an endless loop in IP_Task(). If no particular IP task is implemented in your project, IP_Exec() should be called regularly. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 105 4.4 Network interface configuration and handling functions UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 106 CHAPTER 4 4.4.1 Core functions IP_NI_ConfigPHYAddr() Description Configures the PHY address. Prototype void IP_NI_ConfigPHYAddr ( unsigned Unit, U8 Addr ); Parameter Unit Addr Description [IN] Zero-based index of available network interfaces. [IN] 5-bit address. Table 4.45: IP_NI_ConfigPHYAddr() parameter list Additional information The PHY address is a 5-bit value. The available embOS/IP drivers try to detect the PHY address automatically, therefore this should not be called. If you use this function to set the address explicitly, the function must be called from within IP_X_Config(). Refer to IP_X_Configure() on page 326. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 107 4.4.2 IP_NI_ConfigPHYMode() Description Configures the PHY mode. Prototype void IP_NI_ConfigPHYMode ( unsigned Unit, U8 Mode ); Parameter Unit Mode Description [IN] Zero-based index of available network interfaces. [IN] The operating mode of the PHY. Table 4.46: IP_NI_ConfigPHYMode() parameter list Valid values for parameter Mode Value IP_PHY_MODE_MII IP_PHY_MODE_RMII Description Phy uses the Media Independent Interface (MII). Phy uses the Reduced Media Independent Interface (RMII). Additional information The PHY can be connected to the MAC via two different modes, MII or RMII. Refer to section MII / RMII: Interface between MAC and PHY on page 25 for detailed information about the differences of the MII and RMII modes. The selection which mode is used is normally done correctly by the hardware. The mode is typically sampled during power-on RESET. If you use this function to set the mode explicitly, the function must be called from within IP_X_Config(). Refer to IP_X_Configure() on page 326. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 108 CHAPTER 4 4.4.3 Core functions IP_NI_ConfigPoll() Description Select polled mode for the network interface. This should be used only if the network interface can not activate an ISR itself. Prototype void IP_NI_ConfigPoll( unsigned Unit ); Parameter Unit Description [IN] Zero-based index of available network interfaces. Table 4.47: IP_NI_ConfigPoll() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 109 4.4.4 IP_NI_ForceCaps() Description Allows to force capabilities to be set for an interface. Typically this is used to allow the checksum calculation capabilities to be set manually. Typically this is used to give the target a performance boost in high traffic applications on stable networks, where the occurence of wrong checksums is unlikely. Prototype void IP_NI_ForceCaps( U8 IFace, U8 CapsForcedMask, U8 CapsForcedValue ); Parameter IFace CapsForcedMask CapsForcedValue Description [IN] Zero-based index of available network interfaces. [IN] Capabilities mask. For a list of driver capabilities please refer to IP.h and look for the "Driver capabilities" section. [IN] Value mask for the capabilities to force. Table 4.48: IP_NI_ConfigPoll() parameter list Example Forcing the capability bits 0 to value '0' and bit 2 to value '1' for the first interface can be done as shown in the code example below: IP_NI_ForceCaps(0, 5, 4); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 110 CHAPTER 4 4.4.5 Core functions IP_NI_SetTxBufferSize() Description Sets the size of the Tx buffer of the network interface. Prototype int IP_NI_SetTxBufferSize ( unsigned Unit, U8 NumBytes ); Parameter Unit NumBytes Description [IN] Zero-based index of available network interfaces. [IN] Size of the Tx buffer (at least size of the MTU + 16 bytes for Ethernet.) Table 4.49: IP_NI_SetTxBufferSize() parameter list Return value -1: Not supported by the network interface driver. 0: OK 1: Error, called after driver initialization has been completed. Additional information The default Tx buffer size is 1536 bytes. It can be useful to reduce the buffer size on systems with less RAM and an application that uses a small MTU. According to RFC 576 bytes is the smallest possible MTU. The size of the Tx buffer should be at least MTU + 16 bytes for Ethernet header and footer. The function should be called in IP_X_Config(). Note: This function is not implemented in all network interface drivers, since not all Media Access Controllers (MAC) support variable buffer sizes. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 111 4.5 Other IP stack functions UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 112 CHAPTER 4 4.5.1 Core functions IP_AddAfterInitHook() Description Adds a hook to a callback that is executed at the end of IP_Init() to allow adding initializations to be executed right after the stack itself has been initialized and all API can be used. Prototype void IP_AddAfterInitHook ( IP_HOOK_AFTER_INIT *pHook, void (*pf)(void) ); Parameter Parameter pHook pf Description [IN] Pointer to static element of IP_HOOK_AFTER_INIT that can be internally used by the stack. [IN] Function pointer to the callback that will be executed. Table 4.50: IP_AddAfterInitHook() parameter list Additional information Adding a callback to be executed right after IP_Init() can be helpful for various things. For example this allows using a centralized initialization that is not located in the main routine that calls IP_Init() and has to make use of IP API that is only valid to be used after IP_Init(). Example // // Excerpt of content of IP_Config_*.c // static IP_HOOK_AFTER_INIT _Hook; static void _Connect(void) { ... } void IP_X_Config(void) { ... IP_AddAfterInitHook(&_Hook, _Connect); // Register _Connect() to be // executed at end of IP_Init() ... } // // Excerpt of content of main.c // void main(void) { ... IP_Init(); ... } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 113 4.5.2 IP_AddStateChangeHook() Description Adds a hook to a callback that is executed when the AdminState or HWState of an interface changes. Prototype void IP_AddStateChangeHook ( IP_HOOK_ON_STATE_CHANGE *pHook, void (*pf)( unsigned IFaceId, U8 AdminState, U8 HWState ) ); Parameter Parameter pHook pf Description [IN] Pointer to static element of IP_HOOK_ON_STATE_CHANGE that can be internally used by the stack. [IN] Function pointer to the callback that will be executed. Table 4.51: IP_AddStateChangeHook() parameter list Additional information A state change hook can be used to be notified about an interface has not been triggered by the application. Typical example would closes a dial-up connection and the application needs to get notified call a disconnect itself. Examples of this behavior can be found shipped with the stack. disconnect that be a peer that of this event to in the samples Example static IP_HOOK_ON_STATE_CHANGE _Hook; static void _OnChange(unsigned IFaceId, U8 AdminState, U8 HWState) { ... } void main(void) { ... IP_AddStateChangeHook(&_Hook, _OnChange); // Register _OnState() to be // executed when interface changes. // Connect dial-up interface. ... } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 114 CHAPTER 4 4.5.3 Core functions IP_Alloc() Description Thread safe memory allocation from IP stack memory pool. Prototype void * IP_Alloc ( U32 NumBytesReq ); Parameter Parameter NumBytesReq Description [IN] Number of bytes to allocate from IP stack memory. Table 4.52: IP_Alloc() parameter list Return value NULL: Error, unable to allocate memory. != NULL: Pointer to allocated memory block. Additional information Memory allocated with this function has to be freed with IP_Free() on page 118. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 115 4.5.4 IP_Connect() Description Calls a previously registered callback IP_SetIFaceConnectHook() on page 137. that has been registered with Prototype int IP_Connect ( unsigned IFaceId ); Parameter Parameter IFaceId Description [IN] Zero-based interface index. Table 4.53: IP_Connect() parameter list Return value 0 : O.K. or no callback set. Other: Error. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 116 CHAPTER 4 4.5.5 Core functions IP_Disconnect() Description Calls a previously registered callback IP_SetIFaceDisconnectHook() on page 138. that has been registered with Prototype int IP_Disconnect ( unsigned IFaceId ); Parameter Parameter IFaceId Description [IN] Zero-based interface index. Table 4.54: IP_Disconnect() parameter list Return value 0 : O.K. or no callback set. Other: Error. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 117 4.5.6 IP_Err2Str() Description Converts an error value to a printable string. Prototype const char * IP_Err2Str( int x ); Parameter Parameter x Description [IN] Error value other than 0. Table 4.55: IP_Err2Str() parameter list Return value String describing the value. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 118 CHAPTER 4 4.5.7 Core functions IP_Free() Description Thread safe memory free to IP stack memory pool. Prototype void IP_Free ( void *p ); Parameter Parameter p Description [IN] Pointer to memory block previously allocated with IP_Alloc() on page 114. Table 4.56: IP_Free() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 119 4.5.8 IP_GetAddrMask() Description Returns the IP address and the subnet mask of the device in network byte order (for example, 192.168.1.1 is returned as 0xc0a80101). Prototype void IP_GetAddrMask ( U8 IFace, U32 * pAddr, U32 * pMask ); Parameter Parameter IFace pAddr pMask Description [IN] Interface. [OUT] Address to store the IP address. [OUT] Address to store the subnet mask. Table 4.57: IP_GetAddrMask() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 120 CHAPTER 4 4.5.9 Core functions IP_GetCurrentLinkSpeed() Description Returns the current link speed of the first interface (interface ID '0'). Prototype int IP_GetCurrentLinkSpeed( void ); Return value 0: 1: 2: 3: link link link link speed speed speed speed unknown is 10 Mbit/s is 100 Mbit/s is 1000 Mbit/s Additional information The application should check if the link is up before a packet will be sent. It can take 2-3 seconds till the link is up if the PHY has been reset. Example // // Wait until link is up. // while (IP_GetCurrentLinkSpeed() == 0) { OS_IP_Delay(100); } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 121 4.5.10 IP_GetCurrentLinkSpeedEx() Description Returns the current link speed of the selected interface. Prototype int IP_GetCurrentLinkSpeedEx( unsigned IFaceId ); Parameter Parameter IFaceId Description [IN] Interface Id (zero-based). Table 4.58: IP_GetCurrentLinkSpeedEx() parameter list Return value 0: 1: 2: 3: link link link link speed speed speed speed unknown is 10 Mbit/s is 100 Mbit/s is 1000 Mbit/s Additional information The application should check if the link is up before a packet will be sent. It can take 2-3 seconds till the link is up if the PHY has been reset. Example // // Wait until link is up. // while (IP_GetCurrentLinkSpeedEx(0) == 0) { OS_IP_Delay(100); } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 122 CHAPTER 4 Core functions 4.5.11 IP_GetGWAddr() Description Returns the gateway address of the interface in network byte order (for example, 192.168.1.1 is returned as 0xc0a80101). Prototype U32 IP_GetGWAddr ( U8 IFace ); Parameter Parameter IFace Description [IN] Number of interface. Table 4.59: IP_GetGWAddr() parameter list Return value The gateway address of the interface. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 123 4.5.12 IP_GetHWAddr() Description Returns the hardware address (Media Access Control address) of the interface. Prototype void IP_GetHWAddr ( U8 IFace, U8 * pDest, unsigned Len ); Parameter Parameter IFace pDest Len Description [IN] Number of interface. [OUT] Address of the buffer to store the 48-bit MAC address. [IN] Size of the buffer. Should be at least 6-bytes. Table 4.60: IP_GetHWAddr() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 124 CHAPTER 4 Core functions 4.5.13 IP_GetIPAddr() Description Returns the IP address of the interface. Prototype U32 IP_GetIPAddr( U8 IFace ); Parameter Parameter IFace Description [IN] Zero-based interface index. Table 4.61: IP_GetIPAddr() parameter list Return value The IP address of the interface in host byte order (for example, 192.168.1.1 is returned as 0x0101a8c0 for a little endian target). Example void PrintIFaceIPAddr(void) { char ac[16]; U32 IPAddr; IPAddr = IP_GetIPAddr(0); IP_PrintIPAddr(ac, IPAddr, sizeof(ac)); printf("IP Addr: %s\n", ac); } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 125 4.5.14 IP_GetIPPacketInfo() Description Returns the start address of the data part of an IP packet. Prototype const char * IP_GetIPPacketInfo( IP_PACKET * pPacket ); Parameter Parameter pPacket Description [IN] Pointer to an IP_PACKET structure. Table 4.62: IP_GetIPPacketInfo() parameter list Return value 0 > Start address of the data part of the IP packet. 0 On failure. Example /********************************************************************* * * _pfOnRxICMP */ static int _pfOnRxICMP(IP_PACKET * pPacket) { const char * pData; pData = IP_GetIPPacketInfo(pPacket); if(*pData == 0x08) { printf("ICMP echo request received!\n"); } if(*pData == 0x00) { printf("ICMP echo reply received!\n"); } return 0; } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 126 CHAPTER 4 Core functions 4.5.15 IP_GetRawPacketInfo() Description Returns the start address of the raw data part of an IP packet. Prototype const char * IP_GetRawPacketInfo( IP_PACKET * pPacket, U16 * pNumBytes ); Parameter Parameter pPacket pNumBytes Description [IN] Pointer to an IP_PACKET structure. [OUT] Length of the packet. Table 4.63: IP_GetRawPacketInfo() parameter list Return value 0 > Start address of the raw data part of the IP packet. 0 On failure. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 127 4.5.16 IP_GetVersion() Description Returns the version number of the stack. Prototype int IP_GetVersion ( void ); Additional information The format of the version number: <Major><Minor><Minor><Revision><Revision>. For example, the return value 10201 means version 1.02a. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 128 CHAPTER 4 Core functions 4.5.17 IP_ICMP_SetRxHook() Description Sets a hook function which will be called if target receives a ping packet. Prototype void IP_ICMP_SetRxHook(IP_RX_HOOK * pf); Parameter Parameter pf Description Pointer to the callback function of type IP_RX_HOOK. Table 4.64: IP_ICMP_SetRxHook() parameter list Additional information The return value of the callback function is relevant for the further processing of the ICMP packet. A return value of 0 indicates that the stack has to process the packet after the callback has returned. A return value of 1 indicates that the packet will be freed directly after the callback has returned. The prototype for the callback function is defined as follows: typedef int (IP_RX_HOOK)(IP_PACKET * pPacket); Example /********************************************************************* * * Local defines, configurable * ********************************************************************** */ #define HOST_TO_PING 0xC0A80101 /********************************************************************* * * _pfOnRxICMP */ static int _pfOnRxICMP(IP_PACKET * pPacket) { const char * pData; pData = IP_GetIPPacketInfo(pPacket); if(*pData == 0x08) { printf("ICMP echo request received!\n"); } if(*pData == 0x00) { printf("ICMP echo reply received!\n"); } return 0; // Give packet back to the stack for further processing. } /********************************************************************* * * PingTask */ void PingTask(void) { int Seq; char * s = "This is a ICMP echo request!"; while (IP_IFaceIsReady() == 0) { OS_Delay(50); } IP_ICMP_SetRxHook(_pfOnRxICMP); Seq = 1111; while (1) { BSP_ToggleLED(1); OS_Delay (200); IP_SendPing(htonl(HOST_TO_PING), s, strlen(s), Seq++); } } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 129 4.5.18 IP_IFaceIsReady() Description Checks if the interface is ready for usage. Ready for usage means that the target has a physical link detected and a valid IP address. Prototype int IP_IFaceIsReady ( void ); Return value 1 network interface is ready. 0 network interface is not ready. Additional information The application has to check if the link is up before a packet will be sent and if the interface is configured. If a DHCP server is used for configuring your target, this function has to be called to assure that no application data will be sent before the target is ready. Example // // Wait until interface is ready. // while (IP_IFaceIsReady() == 0) { OS_Delay(100); } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 130 CHAPTER 4 Core functions 4.5.19 IP_IFaceIsReadyEx() Description Checks if the specified interface is ready for usage. Ready for usage means that the target has a physical link detected and a valid IP address. Prototype int IP_IFaceIsReadyEx ( unsigned IFaceId ); Parameter Parameter IFaceId Description [IN] Zero-based interface index. Table 4.65: IP_IFaceIsReadyEx() parameter list Return value 1 network interface is ready. 0 network interface is not ready. Additional information The application has to check if the link is up before a packet will be sent and if the interface is configured. If a DHCP server is used for configuring your target, this function has to be called to assure that no application data will be sent before the target is ready. Example // // Wait until second interface is ready. // while (IP_IFaceIsReadyEx(1) == 0) { OS_Delay(100); } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 131 4.5.20 IP_IsExpired() Description Checks if the given system timestamp has already expired. Prototype int IP_IsExpired ( I32 Time ); Parameter Parameter Time Description [IN] System timestamp as used by OS abstraction layer. Table 4.66: IP_IsExpired() parameter list Return value 1 Timestamp has expired. 0 Timestamp has not yet expired. Example U32 Timeout; // // Get current system time [ms] and timeout in one second. // Timeout = IP_OS_GET_TIME() + 1000; // // Wait until timeout expires. // do { OS_Delay(1); } while (IP_IsExpired(Timeout) == 0); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 132 CHAPTER 4 Core functions 4.5.21 IP_PrintIPAddr() Description Convert a 4-byte IP address to a dots-and-number string. Prototype int IP_PrintIPAddr( char * pDest, U32 IPAddr, int BufferSize ); Parameter Parameter pDest IPAddr Buffersize Description [OUT] Buffer to store the IP address string. [IN] IP address in host byte order. [IN] Size of buffer pDest. Should be 16 byte to store an IPv4 address. Table 4.67: IP_PrintIPAddr() parameter list Example void PrintIPAddr(void) { U32 IPAddr; char ac[16]; IPAddr = 0xC0A80801; // IP address: 192.168.8.1 IP_PrintIPAddr(ac, IPAddr, sizeof(ac)); printf("IP address: %s\n", ac); // Output: IP address: 192.168.8.1 } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 133 4.5.22 IP_ResolveHost() Description Resolve a host name string to its IP addr. by using a configured DNS server. Prototype int IP_ResolveHost( char *sHost, U32 *pIPAddr, U32 ms ); Parameter Parameter sHost pIPAddr ms Description [IN] Host name to resolve. [OUT] Pointer to where to store the resolved IP addr. [IN] Timeout in ms to wait for the DNS server to answer. Table 4.68: IP_ResolveHost() parameter list Return value 0 O.K., host name resolved. < 0 Error: Could not resolve host name. Additional information In contrast to the standard socket function gethostbyname(), this function allows resolving a host name in a thread safe way and should therefore be used whenever possible. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 134 CHAPTER 4 Core functions 4.5.23 IP_SendPacket() Description Sends a user defined packet on the interface. The packet will not be modified by the stack. IP_SendPacket() allocates a packet control block (IP_PACKET) and adds it to the out queue of the interface. Prototype int IP_SendPacket( unsigned IFace, void * pData, int NumBytes ); Parameter Parameter IFace pData Numbytes Description [IN] Zero-based interface index. [IN] Data packet that should be sent. [IN] Length of data which should be sent. Table 4.69: IP_SendPacket() parameter list Return value 0 -1 1 O.K., packet in out queue Error: Could not allocate a packet control block Error: Interface can not send UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 135 4.5.24 IP_SendPing() Description Sends a single "ping" (ICMP echo request) to the specified host. Prototype int IP_SendPing ( ip_addr host, char * data, unsigned datalen, U16 pingseq ); Parameter Parameter host data datalen pingseq Description [IN] [IN] [IN] [IN] 4-byte IPv4 address in network endian byte order. Ping data, NULL if do not care. Length of data to attach to ping request. Ping sequence number. Table 4.70: IP_SendPing() parameter list Return value Returns 0 if ICMP echo request was successfully sent, else negative error message. Additional information If you call this function with activated logging, the ICMP reply or (in case of an error) the error message will be sent to stdout. To enable the output of ICMP status messages, add the message type IP_MTYPE_ICMP to the log filter and the warn filter. Refer to Debugging on page 541 for detailed information about logging. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 136 CHAPTER 4 Core functions 4.5.25 IP_SendPingEx() Description Sends a single "ping" (ICMP echo request) to the specified host using the selected interface. Prototype int IP_SendPingEx ( U32 IFaceId, ip_addr host, char * data, unsigned datalen, U16 pingseq ); Parameter Parameter IFaceId host data datalen pingseq Description [IN] [IN] [IN] [IN] [IN] Interface index (zero-based). 4-byte IPv4 address in network endian byte order. Ping data, NULL if do not care. Length of data to attach to ping request. Ping sequence number. Table 4.71: IP_SendPingEx() parameter list Return value Returns 0 if ICMP echo request was successfully sent, else negative error message. Additional information If you call this function with activated logging, the ICMP reply or (in case of an error) the error message will be sent to stdout. To enable the output of ICMP status messages, add the message type IP_MTYPE_ICMP to the log filter and the warn filter. Refer to Debugging on page 541 for detailed information about logging. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 137 4.5.26 IP_SetIFaceConnectHook() Description Sets a callback for an interface that is executed when IP_Connect() on page 115 is called. Prototype void IP_SetIFaceConnectHook ( unsigned IFaceId, int (*pf) ( unsigned IFaceId ) ); Parameter Parameter IFaceId pf Description [IN] Zero-based interface index. [IN] Callback to set. Table 4.72: IP_SetIFaceConnectHook() parameter list Additional information Typically for a pure Ethernet interface this functionality is not needed. Typically it is used with dial-up interfaces or interfaces that need more configurations to be set by the application to work. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 138 CHAPTER 4 Core functions 4.5.27 IP_SetIFaceDisconnectHook() Description Sets a callback for an interface that is executed when IP_Disconnect() on page 116 is called. Prototype void IP_SetIFaceDisconnectHook ( unsigned IFaceId, int (*pf) ( unsigned IFaceId ) ); Parameter Parameter IFaceId pf Description [IN] Zero-based interface index. [IN] Callback to set. Table 4.73: IP_SetIFaceDisconnectHook() parameter list Additional information Typically for a pure Ethernet interface this functionality is not needed. Typically it is used with dial-up interfaces or interfaces that need more configurations to be set by the application to work. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 139 4.5.28 IP_SetRxHook() Description Sets a hook function which will be called if target receives a packet. Prototype void IP_SetRxHook(IP_RX_HOOK * pf); Parameter Parameter pf Description Pointer to the callback function of type IP_RX_HOOK. Table 4.74: IP_SetRxHook() parameter list Additional information The return value of the callback function is relevant for the further processing of the packet. A return value of 0 indicates that the stack has to process the packet after the callback has returned. A return value of >0 indicates that the packet will be freed directly after the callback has returned. The prototype for the callback function is defined as follows: typedef int (IP_RX_HOOK)(IP_PACKET * pPacket); Example Refer to IP_ICMP_SetRxHook() on page 128 for an example. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 140 CHAPTER 4 Core functions 4.6 Stack internal functions, variables and data-structures embOS/IP internal functions, variables and data-structures are not explained here as they are in no way required to use embOS/IP. Your application should not rely on any of the internal elements, as only the documented API functions are guaranteed to remain unchanged in future versions of embOS/IP. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 141 Chapter 5 Socket interface The embOS/IP socket API is almost compatible to the Berkeley socket interface. The Berkeley socket interface is the de facto standard for socket communication. All API functions are described in this chapter. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 142 5.1 CHAPTER 5 Socket interface API functions The table below lists the available socket API functions. Function accept() bind() closesocket() connect() gethostbyname() getpeername() getsockname() getsockopt() listen() recv() recvfrom() select() send() sendto() setsockopt() shutdown() socket() ntohl htonl htons ntohs Description Socket interface Accepts an incoming attempt on a socket. Assigns a name to an unnamed socket. Closes an existing socket. Establishes a connection to a socket. Resolves a host name into an IP address. Returns the IP addressing information of the connected host. Returns the current name for the specified socket. Returns the socket options. Marks a socket as accepting connections. Receives data from a connected socket. Receives a datagram and stores the source address. Checks if socket is ready. Sends data on a connected socket. Sends data to a specified address. Sets a socket option. Disables sends or receives on a socket. Creates an unbound socket. Helper macros Converts a unsigned long value from network to host byte order. Converts a unsigned long value from host byte order to network byte order. Converts a unsigned short value from host byte order to network byte order. Converts a unsigned short value from network to host byte order. Table 5.1: embOS/IP socket API function overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 143 5.1.1 accept() Description Accepts an incoming attempt on a socket. Prototype long accept ( long Socket, struct sockaddr * pAddr, int * pAddrLen ); Parameter Parameter Socket pAddr pAddrLen Description [IN] A descriptor identifying a socket. [OUT] An optional pointer to a buffer where the address of the connecting entity should be stored. The format of the address depends on the defined address family which was defined when the socket was created. [OUT] An optional pointer to an integer where the length of the received address should be stored. Just like the format of the address, the length of the address depends on the defined address family. Table 5.2: accept() parameter list Return value The returned value is a handle for the socket on which the actual connection will be made. -1 in case of an error. Additional information This call is used with connection-based socket types, currently with SOCK_STREAM. Refer to socket() on page 167 for more information about the different socket types. Before calling accept(), the used socket Socket has to be bound to an address with bind() and should be listening for connections after calling listen(). accept() extracts the first connection on the queue of pending connections, creates a new socket with the same properties of Socket and allocates a new file descriptor for the socket. If no pending connections are present on the queue, and the socket is not marked as non-blocking, accept() blocks the caller until a connection is present. If the socket is marked non-blocking and no pending connections are present on the queue, accept() returns and reports an error. The accepted socket is used to read and write data to and from the socket which is connected to this one; it is not used to accept more connections. The original socket Socket remains open for accepting further connections. The argument pAddr is a result parameter that is filled in with the address of the connecting entity as known to the communications layer. The exact format of the pAddr parameter is determined by the domain in which the communication is occurring. The pAddrLen is a value-result parameter. It should initially contain the amount of space pointed to by pAddr. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 144 CHAPTER 5 5.1.2 Socket interface bind() Description Assigns a name (port) to an unnamed socket. Prototype int bind ( long Socket, struct sockaddr * pAddr, int AddrLen ); Parameter Parameter Socket pAddr AddrLen Description [IN] A descriptor identifying a socket. [IN] A pointer to a buffer where the address of the connecting entity is stored. The format of the address depends on the defined address family which was defined when the socket was created. [IN] The length of the address. Table 5.3: bind() parameter list Return value 0 on success. -1 on failure. Additional information When a socket is created with socket() it exists in a name space (address family) but has no name assigned. bind() is used on an unconnected socket before subsequent calls to the connect() or listen() functions. bind() assigns the name pointed to by pAddr to the socket. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 145 5.1.3 closesocket() Description Closes an existing socket. Prototype int closesocket ( long Socket ); Parameter Parameter Socket Description [IN] Socket descriptor of the socket that should be closed. Table 5.4: closesocket() parameter list Return value 0 on success. -1 on failure. Additional information closesocket() closes a connection on the socket associated with Socket and the socket descriptor associated with Socket will be returned to the free socket descriptor pool. Once a socket is closed, no further socket calls should be made with it. If the socket promises reliable delivery of data and SO_LINGER is set, the system will block the caller on the closesocket() attempt until it is able to transmit the data or until it decides it is unable to deliver the information (a timeout period, termed the linger interval, is specified in the setsockopt() call when SO_LINGER is requested). If SO_LINGER is disabled and a closesocket() is issued, the system will process the close in a manner that allows the caller to continue as quickly as possible. If SO_LINGER is enabled with a timeout period of '0' and a closesocket() is issued, the system will perform a hard close. Example /********************************************************************* * * _CloseSocketGracefully() * * Function description * Wrapper for closesocket() with linger enabled to verify a gracefully * disconnect. */ static int _CloseSocketGracefully(long pConnectionInfo) { struct linger Linger; Linger.l_onoff = 1; // Enable linger for this socket. Linger.l_linger = 1; // Linger timeout in seconds setsockopt(hSocket, SOL_SOCKET, SO_LINGER, &Linger, sizeof(Linger)); return closesocket(hSocket); } /********************************************************************* * * _CloseSocketHard() * * Function description * Wrapper for closesocket() with linger option enabled to perform a hard close. */ static int _CloseSocketHard(long hSocket) { struct linger Linger; Linger.l_onoff = 1; // Enable linger for this socket. Linger.l_linger = 0; // Linger timeout in seconds setsockopt(hSocket, SOL_SOCKET, SO_LINGER, &Linger, sizeof(Linger)); return closesocket(hSocket); } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 146 CHAPTER 5 5.1.4 Socket interface connect() Description Establishes a connection to a socket. Prototype int connect ( long Socket, struct sockaddr * pAddr, int AddrLen ); Parameter Parameter Socket pAddr AddrLen Description [IN] A descriptor identifying an unconnected socket. [IN] A pointer to a buffer where the address of the connecting entity is stored. The format of the address depends on the defined address family which was defined when the socket was created. [IN] A pointer to an integer where the length of the received address is stored. Just like the format of the address, the length of the address depends on the defined address family. Table 5.5: connect() parameter list Return value 0 on success. -1 on failure. Additional information If Socket is of type SOCK_DGRAM or SOCK_RAW, then this call specifies the peer with which the socket is to be associated. pAddr defines the address to which datagrams are sent and the only address from which datagrams are received. To enable RAW socket support in the IP stack it is madatory to call IP_RAW_Add() on page 77 during initialization of the stack. If Socket is of type SOCK_STREAM, then this call attempts to make a connection to another socket. The other socket is specified by pAddr which is an address in the communications space of the socket. Each communications space interprets the pAddr parameter in its own way. Generally, stream sockets may successfully connect() only once; datagram sockets may use connect() multiple times to change their association. Datagram sockets may dissolve the association by connecting to an invalid address, such as a NULL address. If a connect is in progress and the socket is blocking, the connect call waits until connected or an error to happen. If the socket is non-blocking (refer to setsockopt() on page 164 for more information), 0 is returned. You can use the getsockopt() function (refer to getsockopt() on page 152) to determine the status of the connect attempt. Example #define SERVER_PORT #define SERVER_IP_ADDR 1234 0xC0A80101 // 192.168.1.1 /********************************************************************* * * _TCPClientTask * * Function description * Creates a connection to a given IP address, TCP port. */ static void _TCPClientTask(void) { UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 147 int TCPSockID; struct sockaddr_in ServerAddr; int ConnectStatus; // // Wait until link is up. This can take 2-3 seconds if PHY has been reset. // while (IP_GetCurrentLinkSpeed() == 0) { OS_Delay(100); } while(1) { TCPSockID = socket(AF_INET, SOCK_STREAM, 0); // Open socket if (TCPSockID < 0) { // Error, Could not get socket while (1) { OS_Delay(20); } } else { // // Connect to server // ServerAddr.sin_family = AF_INET; ServerAddr.sin_port = htons(SERVER_PORT); ServerAddr.sin_addr.s_addr = htonl(SERVER_IP_ADDR); ConnectStatus = connect(TCPSockID, (struct sockaddr *)&ServerAddr, sizeof(struct sockaddr_in)); if (ConnectStatus == 0) { // // Do something... // } } closesocket(TCPSockID); OS_Delay(50); } } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 148 CHAPTER 5 5.1.5 Socket interface gethostbyname() Description Resolve a host name into an IP address. Prototype struct hostent * gethostbyname (const char * name); Parameter Parameter Description [IN] Host name. name Table 5.6: gethostbyname() parameter list Return value On success, a pointer to a hostent structure is returned. Refer to Structure hostent on page 172 for detailed information about the hostent structure. On failure, it returns NULL. Additional information The function is called with a string containing the host name to be resolved as a fullyqualified domain name (for example, myhost.mydomain.com). Example static void _DNSClient() { struct hostent *pHostEnt; char **ps; char **ppAddr; // // Wait until link is up. // while (IP_IFaceIsReady() == 0) { OS_Delay(100); } while(1) { pHostEnt = gethostbyname("www.segger.com"); if (pHostEnt == NULL) { printf("Could not resolve host addr.\n"); break; } printf("h_name: %s\n", pHostEnt->h_name); // // Show aliases // ps = pHostEnt->h_aliases; for (;;) { char * s; s = *ps++; if (s == NULL) { break; } printf("h_aliases: %s\n", s); } // // Show IP addresses // ppAddr = pHostEnt->h_addr_list; for (;;) { U32 IPAddr; char * pAddr; char ac[16]; pAddr = *ppAddr++; if (pAddr == NULL) { break; } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 149 IPAddr = *(U32*)pAddr; IP_PrintIPAddr(ac, IPAddr, sizeof(ac)); printf("IP Addr: %s\n", ac); } } } Warning: gethostbyname() is not thread safe and should therefore only be used where absolutely necessary. If possible use the thread safe function IP_ResolveHost() instead. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 150 CHAPTER 5 5.1.6 Socket interface getpeername() Description Fills the passed structure sockaddr with the IP addressing information of the connected host. Prototype int getpeername ( long Socket, struct sockaddr * pAddr, struct int * pAddrLen ); Parameter Parameter Socket pAddr pAddrLen Description [IN] A descriptor identifying a socket. [OUT] A pointer to a structure of type sockaddr in which the IP address information of the connected host should be stored. [OUT] A pointer to an integer to store the length of socket address. Table 5.7: getpeername() parameter list Return value 0 on success. -1 on failure. Additional information Refer to Structure sockaddr on page 169 for detailed information about the structure sockaddr. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 151 5.1.7 getsockname() Description Returns the current name for the specified socket. Prototype int getsockname ( long Socket, struct sockaddr * pAddr ); Parameter Parameter Socket pAddr Description [IN] A descriptor identifying a socket. [OUT] A pointer to a structure of type sockaddr in which the IP address information of the connected host should be stored. Table 5.8: getsockname() parameter list Return value 0 on success. -1 on failure. Additional information Refer to Structure sockaddr on page 169 for detailed information about the structure sockaddr. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 152 CHAPTER 5 5.1.8 Socket interface getsockopt() Description Returns the options associated with a socket. Prototype int getsockopt ( long Socket, int Level, int Option, void * pData, int DataLen ); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 153 Parameter Parameter Socket Level Option pData DataLen Description [IN] A descriptor identifying a socket. [IN] Compatibility parameter for setsockopt() and getsockopt(). Use symbol SOL_SOCKET. [IN] The socket option which should be retrieved. [OUT] A pointer to the buffer in which the value of the requested option should be stored. [IN] The size of the data buffer. Table 5.9: getsockopt() parameter list Valid values for parameter Option Value Description Standard option flags. SO_ACCEPTCONN SO_DONTROUTE SO_KEEPALIVE SO_LINGER SO_NOSLOWSTART SO_TIMESTAMP Indicates that socket is in listen mode. Indicates that outgoing messages must bypass the standard routing facilities. Instead, messages are directed to the appropriate network interface according to the network portion of the destination address. Indicates that the periodic transmission of messages on a connected socket is enabled. If the connected party fails to respond to these messages, the connection is considered broken. Indicates that linger on close is enabled. Indicates that suppress slow start on this socket is enabled. Indicates that the TCP timestamp option is enabled. embOS/IP socket options. SO_ERROR SO_MYADDR SO_RCVTIMEO SO_NONBLOCK IP_HDRINCL Stores the latest socket error in pData and clears the error in socket structure. Stores the IP address of the used interface in pData. Returns the timeout for recv(). A return value of 0 indicates that no timeout is set. Gets sockets blocking status. Allows the caller to specify blocking or non-blocking IO that works the same as the other Boolean socket options. pData points to an integer value which will contain a non-zero value to set non-blocking IO or a 0 value to reset non-blocking IO. Checks if the IP header has to be included by the user for a RAW socket. Return value 0 on success. -1 on failure. Additional information getsockopt() retrieves the current value for a socket option associated with a socket of any type, in any state, and stores the result in pData. Options can exist at multiple protocol levels, but they are always present at the uppermost "socket" level. Options affect socket operations, such as the packet routing. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 154 CHAPTER 5 Socket interface The value associated with the selected option is returned in the buffer pData. The integer pointed to by DataLen should originally contain the size of this buffer; on return, it will be set to the size of the value returned. For SO_LINGER, this will be the size of a LINGER structure. For most other options, it will be the size of an integer. The application is responsible for allocating any memory space pointed to directly or indirectly by any of the parameters it specified. If the option was never set with setsockopt(), then getsockopt() returns the default value for the option. The option SO_ERROR returns 0 or the number of the socket error and clears the socket error. The following table lists the socket errors. Symbolic name Value IP_ERR_SEND_PENDING 1 IP_ERR_MISC -1 IP_ERR_TIMEDOUT IP_ERR_ISCONN -2 -3 IP_ERR_OP_NOT_SUPP -4 IP_ERR_CONN_ABORTED -5 IP_ERR_WOULD_BLOCK -6 IP_ERR_CONN_REFUSED IP_ERR_CONN_RESET IP_ERR_NOT_CONN IP_ERR_ALREADY -7 -8 -9 -10 IP_ERR_IN_VAL -11 IP_ERR_MSG_SIZE -12 IP_ERR_PIPE -13 IP_ERR_DEST_ADDR_REQ -14 IP_ERR_SHUTDOWN -15 IP_ERR_NO_PROTO_OPT -16 IP_ERR_NO_MEM -18 IP_ERR_ADDR_NOT_AVAIL -19 IP_ERR_ADDR_IN_USE -20 IP_ERR_IN_PROGRESS IP_ERR_NO_BUF -22 -23 IP_ERR_NOT_SOCK -24 IP_ERR_FAULT IP_ERR_NET_UNREACH IP_ERR_PARAM -25 -26 -27 IP_ERR_LOGIC -28 IP_ERR_NOMEM -29 Description Packet to send is not sent yet. Miscellaneous errors that do not have a specific error code. Operation timed out. Socket is already connected. Operation not supported for selected socket. Connection was aborted. Socket is in non-blocking state and the current operation would block the socket if not in non-blocking state. Connection refused by peer. Connection has been reset. Socket is not connected. Socket already is in the requested state. Passed value for configuration is not valid. Message is too big to send. Socket is not in the correct state for this operation. Destination addr. has not been specified. Connection has been closed as soon as all data has been received upon a FIN request. Unknown socket option for setsockopt() or getsockopt(). Not enough memory in the memory pool. No known path to send to the specified addr. Socket already has a connection to this addr. and port or is already bound to this addr. Operation is still in progress. No internal buffer was available. Socket has not been opened or has already been closed Generic error for a failed operation. No path to the desired network available. Invalid parameter to function. Logical error that should not have happened. System error: No memory for requested operation. Table 5.10: embOS/IP socket error types UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 155 Symbolic name Value IP_ERR_NOBUFFER -30 IP_ERR_RESOURCE -31 IP_ERR_BAD_STATE IP_ERR_TIMEOUT IP_ERR_NO_ROUTE -32 -33 -36 Description System error: No internal buffer available for the requested operation. System error: Not enough free resources available for the requested operation. Socket is in an unexpected state. Requested operation timed out. Net error: Destination is unreachable. Table 5.10: embOS/IP socket error types UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 156 CHAPTER 5 5.1.9 Socket interface listen() Description Prepares the socket to accept connections. Prototype int listen ( long Socket, int Backlog ); Parameter Parameter Socket Backlog Description [IN] Socket descriptor of an unconnected socket. [IN] Backlog for incoming connections. Defines the maximum length of the queue of pending connections. Table 5.11: listen() parameter list Return value On success 0. On failure, it returns -1. Additional information The listen() call applies only to sockets of type SOCK_STREAM. If a connection request arrives when the queue is full, the client will receive an error with an indication of ECONNREFUSED. Example /********************************************************************* * * _ListenAtTcpAddr * * Function description * Starts listening at the given TCP port. */ static int _ListenAtTcpAddr(U16 Port) { int Sock; struct sockaddr_in Addr; Sock = socket(AF_INET, SOCK_STREAM, 0); memset(&Addr, 0, sizeof(Addr)); Addr.sin_family = AF_INET; Addr.sin_port = htons(Port); Addr.sin_addr.s_addr = INADDR_ANY; bind(Sock, (struct sockaddr *)&Addr, sizeof(Addr)); listen(Sock, 1); return Sock; } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 157 5.1.10 recv() Description Receives data from a connected socket. Prototype int recv ( long Socket, char * pRecv, int Length, int Flags ); Parameter Parameter Socket pRecv Length Flags Description [IN] A descriptor identifying a socket. [OUT] A pointer to a buffer for incoming data. [IN] The length of buffer pRecv in bytes. [IN] OR-combination of one or more of the following valid values. Table 5.12: recv() parameter list Valid values for parameter Flag Value MSG_PEEK Description "Peek" at the data present on the socket; the data are returned, but not consumed, so that a subsequent receive operation will see the same data. Return value If no error occurs, recv() returns the number of bytes received. If the connection has been gracefully closed, the return value is zero. Otherwise, -1 is returned, and a specific error code can be retrieved by calling getsockopt(). Refer to getsockopt() on page 152 for detailed information. Additional information If a message is too long to fit in the supplied buffer, excess bytes may be discarded depending on the type of socket the message is received from. Refer to connect() on page 146 for more information about the different types of sockets. You can only use the recv() function on a connected socket. To receive data on a socket, whether it is in a connected state or not refer to recvfrom() on page 158. If no messages are available at the socket and the socket is blocking, the receive call waits for a message to arrive. If the socket is non-blocking (refer to setsockopt() on page 164 for more information), -1 is returned. You can use the select() function to determine when more data arrives. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 158 CHAPTER 5 Socket interface 5.1.11 recvfrom() Description Receives a datagram and stores the source address. Prototype int recvfrom ( long char * int int struct sockaddr * int * Socket, pRecv, Length, Flags, pAddr, pAddrLen ); Parameter Parameter Socket pRecv Length Flags pAddr pAddrLen Description [IN] A socket descriptor of a socket. [OUT] A pointer to a buffer for incoming data. [IN] Specifies the size of the buffer pRecv in bytes. [IN] OR-combination of one or more of the values listed in the table below. [OUT] An optional pointer to a buffer where the address of the connecting entity is stored. The format of the address depends on the defined address family which was defined when the socket was created. [IN/OUT] An optional pointer to an integer where the length of the received address is stored. Just like the format of the address, the length of the address depends on the defined address family. Table 5.13: recvfrom() parameter list Valid values for parameter Flags Value MSG_PEEK Description "Peek" at the data present on the socket; the data are returned, but not consumed, so that a subsequent receive operation will see the same data. Return value The number of bytes received or -1 if an error occurred. Additional information If pAddr is not a NULL pointer, the source address of the message is filled in. pAddrLen is a value-result parameter, initialized to the size of the buffer associated with pAddr, and modified on return to indicate the actual size of the address stored there. If a message is too long to fit in the supplied buffer, excess bytes may be discarded depending on the type of socket the message is received from. Refer to socket() on page 167 for more information about the different types of sockets. If no messages are available at the socket and the socket is blocking, the receive call waits for a message to arrive. If the socket is non-blocking (refer to setsockopt() on page 164 for more information), -1 is returned. You can use the select() function to determine when more data arrives. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 159 5.1.12 select() Description Examines the socket descriptor sets whose addresses are passed in readfds, writefds, and exceptfds to see if some of their descriptors are ready for reading, ready for writing or have an exception condition pending. Prototype int select ( IP_FD_set * readfds, IP_FD_set * writefds, IP_FD_set * exceptfds; long tv ); Parameter Parameter readfds writefds exceptfds tv Description See below. Table 5.14: select() parameter list Return value Returns a non-negative value on success. A positive value indicates the number of ready descriptors in the descriptor sets. 0 indicates that the time limit specified by tv expired. On failure, select() returns -1 and the descriptor sets are not changed. Additional information On return, select() replaces the given descriptor sets with subsets consisting of those descriptors that are ready for the requested operation. The total number of ready descriptors in all the sets is returned. Any of readfds, writefds, and exceptfds may be given as NULL pointers if no descriptors are of interest. Selecting true for reading on a socket descriptor upon which a listen() call has been performed indicates that a subsequent accept() call on that descriptor will not block. In the standard Berkeley UNIX Sockets API, the descriptor sets are stored as bit fields in arrays of integers. This works in the UNIX environment because under UNIX socket descriptors are file system descriptors which are guaranteed to be small integers that can be used as indexes into the bit fields. In embOS/IP, socket descriptors are pointers and thus a bit field representation of the descriptor sets is not feasible. Because of this, the embOS/IP API differs from the Berkeley standard in that the descriptor sets are represented as instances of the following structure: typedef struct IP_FD_SET { unsigned fd_count; long fd_array[FD_SETSIZE]; } IP_fd_set; // The select socket array manager // how many are SET? // an array of SOCKETs Instead of a socket descriptor being represented in a descriptor set via an indexed bit, an embOS/IP socket descriptor is represented in a descriptor set by its presence in the fd_array field of the associated IP_FD_SET structure. Despite this non-standard representation of the descriptor sets themselves, the following standard entry points are provided for manipulating such descriptor sets: IP_FD_ZERO (&fdset) initializes a descriptor set fdset to the null set. IP_FD_SET(fd, &fdset) includes a particular descriptor, fd, in fdset. IP_FD_CLR(fd, &fdset) removes fd from fdset. IP_FD_ISSET(fd, &fdset) is nonzero if fd is a member of fdset, zero otherwise. These entry points behave according to the standard Berkeley semantics. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 160 CHAPTER 5 Socket interface You should be aware that the value of FD_SETSIZE defines the maximum number of descriptors that can be represented in a single descriptor set. The default value of FD_SETSIZE is 12. This value can be increased in the source code version of embOS/ IP to accommodate a larger maximum number of descriptors at the cost of increased processor stack usage. Another difference between the Berkeley and embOS/IP select() calls is the representation of the timeout parameter. Under Berkeley Sockets, the timeout parameter is represented by a pointer to a structure. Under embOS/IP sockets, a timeout is specified by the tv parameter, which defines the maximum number of seconds that should elapse before the call to select() returns. A tv parameter equal to 0 implies that select() should return immediately (effectively a poll of the sockets in the descriptor sets). A tv parameter equal to -1 implies that select() blocks forever unless one of its descriptors becomes ready. The final difference between the Berkeley and embOS/IP versions of select() is the absence in the embOS/IP version of the Berkeley width parameter. The width parameter is of use only when descriptor sets are represented as bit arrays and was thus deleted in the embOS/IP implementation. Note: Under rare circumstances, select() may indicate that a descriptor is ready for writing when in fact an attempt to write would block. This can happen if system resources necessary for a write are exhausted or otherwise unavailable. If an application deems it critical that writes to a file descriptor not block, it should set the descriptor for non-blocking I/O. Refer to setsockopt() on page 164 for detailed information. Example static void _Client() { long Socket; struct sockaddr_in Addr; IP_fd_set readfds; char RecvBuffer[1472] int r; while (IP_IFaceIsReady() == 0) { OS_Delay(100); } Restart: Socket = socket(AF_INET, SOCK_DGRAM, 0); // Open socket Addr.sin_family = AF_INET; Addr.sin_port = htons(2222); Addr.sin_addr.s_addr = INADDR_ANY; r = bind(Socket, (struct sockaddr *)&Addr, sizeof(Addr)); if (r == -1){ socketclose(Socket); OS_Delay(1000); goto Restart; } while(1) { IP_FD_ZERO(&readfds); // Clear the set IP_FD_SET(Socket, &readfds); // Add descriptor to the set r = select(&readfds, NULL, NULL, 5000); // Check for activity. if (r <= 0) { continue; // No socket activity or error detected } if (IP_FD_ISSET(Socket, &readfds)) { IP_FD_CLR(Socket, &readfds); // Remove socket from set r = recvfrom(Socket, RecvBuffer, sizeof(RecvBuffer), 0, NULL, NULL); if (r == -1){ socketclose(Socket) goto Restart; } } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 161 OS_Delay(100); } } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 162 CHAPTER 5 Socket interface 5.1.13 send() Description Sends data to a connected socket. Prototype int send ( long Socket, char * pSend, int Length, int Flags ); Parameter Parameter Socket pSend Length Flags Description [IN] A descriptor identifying a socket. [IN] A pointer to a buffer of data which should be sent. [IN] The length of the message which should be sent. [IN] OR-combination of one or more of the valid values listed in the table below. Table 5.15: send() parameter list Valid values for parameter Flags Value MSG_DONTROUTE Description Specifies that the data should not be subject to routing. Return value The total number of bytes which were sent or -1 if an error occurred. Additional information send() may be used only when the socket is in a connected state. Refer to sendto() on page 163 for information about sending data to a non-connected socket. If no messages space is available at the socket to hold the message to be transmitted, then send() normally blocks, unless the socket has been placed in non-blocking I/O mode. MSG_DONTROUTE is usually used only by diagnostic or routing programs. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 163 5.1.14 sendto() Description Sends data to a specified address. Prototype int sendto ( long Socket, char * pSend, int Length, int Flags, struct sockaddr * pAddr, int ToLen ); Parameter Parameter Socket pSend Length Flags pAddr ToLen Description [IN] A descriptor identifying a socket. [IN] A pointer to a buffer of data which should be sent. [IN] The length of the message which should be sent. [IN] OR-combination of one or more of the valid values listed in the table below. [IN] An optional pointer to a buffer where the address of the connected entity is stored. The format of the address depends on the defined address family which was defined when the socket was created. [IN] The size of the address in pAddr. Table 5.16: sendto() parameter list Valid values for parameter Flags Value MSG_DONTROUTE Description Specifies that the data should not be subject to routing. Return value The total number of bytes which were sent or -1 if an error occurred. Additional information In contrast to send(), sendto() can be used at any time. The connection state is in which case the address of the target is given by the pAddr parameter. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 164 CHAPTER 5 Socket interface 5.1.15 setsockopt() Description Sets a socket option. Prototype int setsockopt ( long Socket, int Level, int Option, void * pData, int DataLen ); Parameter Parameter Socket Level Option pData DataLen Description [IN] A descriptor identifying a socket. [IN] Compatibility parameter for setsockopt() and getsockopt(). Use symbol SOL_SOCKET. [IN] The socket option for which the value is to be set. [IN] A pointer to the buffer in which the value for the requested option is supplied. [IN] The size of the pData buffer. Table 5.17: setsocketopt() parameter list Valid values for parameter Option Value Description Standard option flags. SO_DONTROUTE SO_KEEPALIVE SO_LINGER SO_TIMESTAMP Outgoing messages should bypass the standard routing facilities. Instead, messages are directed to the appropriate network interface according to the network portion of the destination address. By default, this socket option is disabled. Enable periodic transmission of messages on a connected socket. If the connected party fails to respond to these messages, the connection is considered broken. By default, this socket option is enabled. Controls the action taken when unsent messages are queued on a socket and a closesocket() is performed. Refer to closesocket() on page 145 for detailed information about the linger option. By default, this socket option is disabled. Enable the TCP timestamp option. By default, this socket option is disabled. embOS/IP socket options. SO_CALLBACK SO_RCVTIMEO UM07001 User & Reference Guide for embOS/IP Sets zero-copy callback routine. Refer to TCP zero-copy interface on page 175 for detailed information. Sets a timeout for recv(). This changes the behavior of recv(). recv() is by default a blocking function which only returns if data has been received. If a timeout is set recv() will return in case of data reception or timeout. By default, this socket option is disabled. (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 165 Value SO_NONBLOCK IP_HDRINCL Description Sets socket blocking status. Allows the caller to specify blocking or non-blocking IO that works the same as the other Boolean socket options. pData points to an integer value which will contain a non-zero value to set non-blocking IO or a 0 value to reset non-blocking IO. By default, this socket option is disabled. Configures if the IP header has to be included by the user or if the IP header is generated by the stack. Return value 0 on success Example void _EnableKeepAlive(long sock) { int v = 1; setsockopt(sock, SOL_SOCKET, SO_KEEPALIVE, &v, sizeof(v)); } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 166 CHAPTER 5 Socket interface 5.1.16 shutdown() Description Disables sends or receives on a socket. Prototype int shutdown( long Socket, int Mode ); Parameter Parameter Socket Mode Description [IN] A descriptor identifying a socket. [IN] Indicator which part of communication should be disabled. Refer to additional information below. Table 5.18: shutdown() parameter list Return value Returns 0 on success. On failure, it returns -1. Additional information A shutdown() call causes all or part of a full-duplex connection on the socket associated with Socket to be shut down. If Mode is 0, then further receives will be disallowed. If Mode is 1, then further sends will be disallowed. If Mode is 2, then further sends and receives will be disallowed. The shutdown function does not block regardless of the SO_LINGER setting on the socket. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 167 5.1.17 socket() Description Creates a socket. A socket is an endpoint for communication. Prototype long socket ( int Domain, int Type, int Proto ); Parameter Parameter Domain Type Proto Description [IN] Protocol family which should be used. [IN] Specifies the type of the socket. [IN] Specifies the protocol which should be used with the socket. Must be set to zero except when Type is SOCK_RAW. Table 5.19: socket() parameter list Valid values for parameter Domain Value AF_INET Description IPv4 - Internet protocol version 4 Valid values for parameter Type Value SOCK_STREAM SOCK_DGRAM SOCK_RAW Description Stream socket Datagram socket RAW socket Return value A non-negative descriptor on success. On failure, it returns -1. Additional information The Domain parameter specifies a communication domain within which communication will take place; the communication domain selects the protocol family which should be used. The protocol family generally is the same as the address family for the addresses supplied in later operations on the socket. A SOCK_STREAM socket provides sequenced, reliable, two-way connection based byte streams. A SOCK_DGRAM socket supports datagrams (connectionless, unreliable messages of a fixed - typically small - maximum length). Sockets of type SOCK_STREAM are full-duplex byte streams, similar to UNIX pipes. A stream socket must be in a connected state before it can send or receive data. A connection to another socket is created with a connect() call. Once connected, data can be transferred using send() and recv() calls. When a session has been completed, a closesocket() should be performed. The communications protocols used to implement a SOCK_STREAM ensure that data is not lost or duplicated. If a piece of data (for which the peer protocol has buffer space) cannot be successfully transmitted within a reasonable length of time, then the connection is considered broken and calls will return -1 which indicates an error. The protocols optionally keep sockets "warm" by forcing transmissions roughly every UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 168 CHAPTER 5 Socket interface minute in the absence of other activity. An error is then indicated if no response can be elicited on an otherwise idle connection for a extended period (such as five minutes). SOCK_DGRAM sockets allow sending of datagrams to correspondents named in sendto() calls. Datagrams are generally received with recvfrom(), which returns the next datagram with its return address. SOCK_RAW sockets allow receiving data including network and IP header and allow sending of data either with or without specifying the IP header yourself. RAW sockets are operated the same way as SOCK_DGRAM sockets but allow the ability to receive data including the IP and protocol header and to implement your own protocol. For using RAW sockets it is mandatory to call IP_RAW_Add() on page 77 during the initialization of the stack. More information about RAW sockets can be found below. The operation of sockets is controlled by socket-level options. The getsockopt() and setsockopt() functions are used to get and set options. Refer to getsockopt() on page 152 and setsockopt() on page 164 for detailed information. RAW sockets (receiving) For RAW sockets the Proto parameter specifies the IP protocol that will be received using this socket. Protocols registered to be used with IP_*_Add() will be handled the stack and can not be used with RAW sockets at the same time. Using IPPROTO_RAW will receive data for any protocol not handled by the IP stack. RAW sockets (sending) For RAW sockets the Proto parameter specifies the IP protocol that will be entered into the IP header when sending data using this socket. Using IPPROTO_RAW for Proto for a sending socket results in the same as setting the socket option IP_HDRINCL for this socket by using setsockopt() on page 164 and requires the user to include his own IP header in the data to send. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 169 5.2 Socket data structures 5.2.1 Structure sockaddr Description This structure holds socket address information for many types of sockets. Prototype struct sockaddr { U16 sa_family; char sa_data[14]; }; Member sa_family sa_data Description Address family. Normally AF_INET. The character array sa_data contains the destination address and port number for the socket. Table 5.20: Structure sockaddr member list Additional information The structure sockaddr is mostly used as function parameter. To deal with struct sockaddr, a parallel structure struct sockaddr_in is implemented. The structure sockaddr_in is the same size as structure sockaddr, so that a pointer can freely be casted from one type to the other. Refer to Structure sockaddr_in on page 170 for more information and an example. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 170 CHAPTER 5 5.2.2 Socket interface Structure sockaddr_in Description Structure for handling internet addresses. Prototype struct sockaddr_in { short sin_family; unsigned short sin_port; struct in_addr sin_addr; char sin_zero[8]; }; Member sin_family sin_port sin_addr sin_zero Description Address family. Normally AF_INET. Port number for the socket. Structure of type in_addr. The structure represents a 4-byte number that represents one digit in an IP address per byte. sin_zero member is unused. Table 5.21: Structure sockaddr_in member list Example Refer to connect() on page 146 for an example. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 171 5.2.3 Structure in_addr Description 4-byte number that represents one digit in an IP address per byte. Prototype struct in_addr { unsigned long s_addr; }; Member s_addr Description Number that represents one digit in an IP address per byte. Table 5.22: Structure in_addr member list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 172 CHAPTER 5 5.2.4 Socket interface Structure hostent Description The hostent structure is used by functions to store information about a given host, such as host name, IPv4 address, and so on. Prototype struct hostent { char * h_name; char ** h_aliases; int h_addrtype; int h_length; char ** h_addr_list; }; Member h_name h_aliases s_addrtype h_length s_addr_list Description Official name of the host. Alias list. Host address type. Length of the address. List of addresses from the name server. Table 5.23: Structure in_addr member list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 173 5.3 Error codes The following table contains a list of generic error codes, generally full success is 0. Definite errors are negative numbers, and indeterminate conditions are positive numbers. Symbolic name IP_ERR_PARAM IP_ERR_LOGIC IP_ERR_NOMEM IP_ERR_NOBUFFER IP_ERR_RESOURCE IP_ERR_BAD_STATE IP_ERR_TIMEOUT IP_ERR_BAD_HEADER IP_ERR_NO_ROUTE IP_ERR_SEND_PENDING IP_ERR_NOT_MINE Value Description Programming errors -10 Bad parameter. Sequence of events that shouldn't hap-11 pen. System errors -20 malloc() or calloc() failed. -21 Run out of free packets. -22 Run out of other queue-able resource. -23 TCP layer error. -24 Timeout error on TCP layer. Networking errors -32 Bad header at upper layer (for upcalls). -33 Can not find a reasonable next IP hop. Networking errors 1 Packet queued pending an ARP reply. 2 Packet was not of interest (upcall reply). Table 5.24: embOS/IP error types UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 174 UM07001 User & Reference Guide for embOS/IP CHAPTER 5 Socket interface (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 175 Chapter 6 TCP zero-copy interface The TCP protocol can be used via socket functions or the TCP zero-copy interface which is described in this chapter. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 176 CHAPTER 6 6.1 TCP zero-copy interface TCP zero-copy This section documents an optional extension to the Sockets layer, the TCP zero-copy API. The TCP zero-copy API is intended to assist the development of higher-performance embedded network applications by allowing the application direct access to the TCP/IP stack packet buffers. This feature can be used to avoid the overhead of having the stack copy data between application-owned buffers and stack-owned buffers in send() and recv(), but the application has to fit its data into, and accept its data from, the stack buffers. The TCP zero-copy API is small because it is simply an extension to the existing Sockets API that provides an alternate mechanism for sending and receiving data on a socket. The Sockets API is used for all other operations on the socket. 6.1.1 Allocating, freeing and sending packet buffers The two functions for allocating and freeing packet buffers are straightforward requests: IP_TCP_Alloc() allocates a packet buffer from the pool of packet buffers on the stack and IP_TCP_Free() frees a packet buffer. Applications using the TCP zero-copy API are responsible for allocating packet buffers for use in sending data, as well as for freeing buffers that have been used to receive data and those that the application has allocated but decided not to use for sending data. As these packet buffers are a limited resource, it is important that applications free them promptly when they are no longer of use. The functions for sending data, IP_TCP_Send() and IP_TCP_SendAndFree(), send a packet buffer of data using a socket. The TCP zero-copy interface supports two different approaches to send and free a packet. One approach is that the stack frees the packet independent from the success of sending the packet. Therefor, IP_TCP_SendAndFree() is called to send and free the packet. It frees the packet independent from the success of the send operation. The other approach is that IP_TCP_Send() is called. In this case it is the responsibility of the application to free the packet. Depending on the return value the application can decide if IP_TCP_Free() should be called to free the packet. 6.1.2 Callback function Applications that use the TCP Zero-copy API for receiving data must include a callback function for acceptance of received packets, and must register the callback function with the socket using the setsockopt() sockets function with the SO_CALLBACK option name. The callback function, once registered, receives not only received data packets, but also connection events that result in socket errors. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 177 6.2 Sending data with the TCP zero-copy API To send data with the TCP zero-copy API, you should proceed as follow: 1. 2. 3. Allocating a packet buffer Filling the allocated buffer Sending the packet The following section describes the procedure for allocating a packet buffer, sending data, and freeing the packet buffer step by step. 6.2.1 Allocating a packet buffer The first step in using the TCP zero-copy API to send data is to allocate a packet buffer from the stack using the IP_TCP_Alloc() function. This function takes the maximum length of the data you intend to send in the buffer as argument and returns a pointer to an IP_PACKET structure. IP_PACKET * pPacket; U32 DataLen; // Amount of data to send DataLen = 512; // Should indicate amount of data to send pPacket = IP_TCP_Alloc(DataLen); if (pPacket == NULL) { // Error, could not allocate packet buffer } This limits how much data you can send in one call using the TCP zero-copy API, as the data sent in one call to IP_TCP_Send() must fit in a single packet buffer. The actual limit is determined by the big packet buffer size, less 68 bytes for protocol headers. If you try to request a larger buffer than this, IP_TCP_Alloc() returns NULL to indicate that it cannot allocate a sufficiently large buffer. 6.2.2 Filling the allocated buffer with data Having allocated the packet buffer, you now fill it with the data to send. The function IP_TCP_Alloc() has initialized the returned IP_PACKET pPacket and so pPacket>pData points to where you can start depositing data. 6.2.3 Sending the packet Finally, you send the packet by giving it back to the stack using the function IP_TCP_Send(). e = IP_TCP_Send(socket, pPacket); if (e < 0) { IP_TCP_Free(pPacket); } This function sends the packet over TCP, or returns an error. If its return value is less than zero, it has not accepted the packet and the application has to decide either to free the packet or to retain it for sending later. Use IP_TCP_SendAndFree() if the packet should be freed automatically in any case. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 178 CHAPTER 6 6.3 TCP zero-copy interface Receiving data with the TCP zero-copy API To receive data with the TCP zero-copy API, you should proceed as follow: 1. 2. 6.3.1 Writing a callback function Registering the callback function Writing a callback function Using the TCP zero-copy API for receiving data requires the application developer to write a callback function that the stack can use to inform the application of received data packets and other socket events. This function is expected to conform to the following prototype: int rx_callback(long Socket, IP_PACKET * pPacket, int code); The stack calls this function when it has received a data packet or other event to report for a socket. The parameter Socket identifies the socket. The parameter pPacket passes a pointer to the packet buffer (if there is a packet buffer). If pPacket is not NULL, it is a pointer to a packet buffer containing received data for the socket. pPacket->pData points to the start of the received data, and pPacket->NumBytes indicates the number of bytes of received data in this buffer. The parameter code passes an error event (if there is an error to report). If code is not 0, it is a socket error indicating that an error or other event has occurred on the socket. Typical nonzero values are ESHUTDOWN and ECONNRESET. ESHUTDOWN defines that the connected peer has closed its end of the connection and sends no more data. ECONNRESET defines that the connected peer has abruptly closed its end of the connection and neither sends nor receives more data. Returned values The callback function may return one of the following values: Symbolic Nume rical IP_OK 0 IP_OK_KEEP_PACKET 1 Description Data handled, packet can be freed. Data will be handled by application later, the stack should NOT free the packet. This will be done by the application at a later time when the data has been handled and the packet is no longer needed. Table 6.1: embOS/IP TCP zero-copy - Valid return values for the receive callback function Note: The callback function is called from the stack and is expected to return promptly. Some of the places where the stack calls the callback function require that the data structures on the stack remain consistent through the callback, so the callback function must not call back into the stack except to call IP_TCP_Free(). 6.3.2 Registering the callback function The application must also inform the stack of the callback function. setsockopt() function provides an additional socket option, SO_CALLBACK, which should be used for this purpose once the socket has been created. The following code fragment illustrates the use of this option to register a callback function named RxUpcall() on the socket Socket: setsockopt(Socket, SOL_SOCKET, SO_CALLBACK, (void *)RxUpcall, 0); The function setsockopt() is described in setsockopt() on page 164. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 179 6.4 API functions Function IP_TCP_Alloc() IP_TCP_Free() IP_TCP_Send() IP_TCP_SendAndFree() Description Allocates a packet buffer. Frees a packet buffer. Sends a packet. Sends and frees a packet. Table 6.2: embOS/IP TCP zero-copy API function overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 180 CHAPTER 6 6.4.1 TCP zero-copy interface IP_TCP_Alloc() Description Allocates a packet buffer large enough to hold datasize bytes of TCP data, plus TCP, IP and MAC headers. Prototype IP_PACKET * IP_TCP_Alloc (int datasize); Parameter Parameter datasize Description [IN] Length of the data which should be sent. Table 6.3: IP_TCP_Alloc() parameter list Return value Success: Returns a pointer to the allocated buffer. Error: NULL Additional information This function must be called to allocate a buffer for sending data via IP_TCP_Send(). It returns the allocated packet buffer with its pPacket->pData field set to where the application must deposit the data to be sent. This datasize limits how much data that you can send in one call using the TCP zerocopy API, as the data sent in one call to IP_TCP_Send() must fit in a single packet buffer, with the TCP, IP, and lower-layer headers that the stack needs to add in order to send the packet. The actual limit is determined by the big packet buffer size (normally 1536 bytes). Refer to IP_AddBuffers() on page 48 for more information about defining buffer sizes. If you try to request a larger buffer than this, IP_TCP_Alloc() returns NULL to indicate that it cannot allocate a sufficiently-large buffer. Example IP_PACKET * pPacket; U32 DataLen; // Amount of data to send DataLen = 1024; // Should indicate amount of data to send pPacket = IP_TCP_Alloc(DataLen); if (pPacket == NULL) { // Error, could not allocate packet buffer } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 181 6.4.2 IP_TCP_Free() Description Frees a packet buffer allocated by IP_TCP_Alloc(). Prototype void IP_TCP_Free ( IP_PACKET * pPacket ); Parameter Parameter pPacket Description [IN] Pointer to the IP_Packet structure. Table 6.4: IP_TCP_Free() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 182 CHAPTER 6 6.4.3 TCP zero-copy interface IP_TCP_Send() Description Sends a packet buffer on a socket. Prototype int IP_TCP_Send ( U32 s, IP_PACKET * pPacket ); Parameter Parameter s pPacket Description [IN] Socket descriptor. [IN] Pointer to a packet buffer. Table 6.5: IP_TCP_Send() parameter list Return value 0 The packet was sent successfully. <0 The packet was not accepted by the stack. The application must re-send the packet using a call to IP_TCP_Send(), or free the packet using IP_TCP_Free(). >0 The packet has been accepted and queued on the socket but has not yet been transmitted. Additional information Applications using the TCP zero-copy API are responsible for allocating packet buffers for use in sending data, as well as for freeing buffers that have been used to receive data and those that the application has allocated but decided not to use for sending data. As these packet buffers are a limited resource, it is important that applications free them promptly when they are no longer of use. Packets have to be freed after processing. The TCP zero-copy interface supports two different approaches to free a packet. One approach is that the stack frees the packet independent from the success of sending the packet. Therefor, IP_TCP_SendAndFree() is called to send the packet and free the packet. It frees the packet independent from the success of the send operation. The other approach is that IP_TCP_Send() is called. In this case it is the responsibility application programmer to free the packet. Depending on the return value the application programmer can decide if IP_TCP_Free() should be called to free the packet. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 183 6.4.4 IP_TCP_SendAndFree() Description Sends a packet buffer on a socket. Prototype int IP_TCP_SendAndFree ( U32 s, IP_PACKET * pPacket ); Parameter Parameter s pPacket Description [IN] Socket descriptor. [IN] Pointer to the IP_Packet structure. Table 6.6: IP_TCP_Send() parameter list Return value 0 The packet was sent successfully. <0 The packet was not accepted by the stack. >0 The packet has been accepted and queued on the socket but has not yet been transmitted. Additional information Applications using the TCP zero-copy API are responsible for allocating packet buffers for use in sending data, as well as for freeing buffers that have been used to receive data and those that the application has allocated but decided not to use for sending data. As these packet buffers are a limited resource, it is important that applications free them promptly when they are no longer of use. IP_TCP_SendAndFree() frees packet pPacket after processing. It frees the packet independent from the success of the send operation. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 184 UM07001 User & Reference Guide for embOS/IP CHAPTER 6 TCP zero-copy interface (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 185 Chapter 7 UDP zero-copy interface The UDP transfer protocol can be used via socket functions or the zero-copy interface which is described in this chapter. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 186 CHAPTER 7 7.1 UDP zero-copy interface UDP zero-copy The UDP zero-copy API functions are provided for systems that do not need the overhead of sockets. These routines impose a lower demand on CPU and system memory requirements than sockets. However, they do not offer the portability of sockets. UDP zero-copy API functions are intended to assist the development of higher-performance embedded network applications by allowing the application direct access to the UDP/IP stack packet buffers. This feature can be used to avoid the overhead of having the stack copy data between application-owned buffers and stack-owned buffers in sendto() and recvfrom(), but the application has to fit its data into, and accept its data from the stack buffers. Refer to embOS/IP UDP discover (OS_IP_UDPDiscover.c / OS_IP_UDPDiscoverZeroCopy.c) on page 41 for detailed dinformation about the UDP zero-copy example application. 7.1.1 Allocating, freeing and sending packet buffers The two functions for allocating and freeing packet buffers are straightforward requests: IP_UDP_Alloc() allocates a packet buffer from the pool of packet buffers on the stack and IP_UDP_Free() frees a packet buffer. Applications using the UDP zero-copy API are responsible for allocating packet buffers for use in sending data, as well as for freeing buffers that have been used to receive data and those that the application has allocated but decided not to use for sending data. As these packet buffers are a limited resource, it is important that applications free them promptly when they are no longer of use. The functions for sending data, IP_UDP_Send() and IP_UDP_SendAndFree(), send a packet buffer of data using a port. The UDP zero-copy interface supports two different approaches to send and free a packet. One approach is that the stack frees the packet independent from the success of sending the packet. Therefor, IP_UDP_SendAndFree() is called to send and free the packet. It frees the packet independent from the success of the send operation. The other approach is that IP_UDP_Send() is called. In this case it is the responsibility of the application to free the packet. Depending on the return value the application can decide if IP_UDP_Free() should be called to free the packet. 7.1.2 Callback function Applications that use the UDP zero-copy API for receiving data must include a callback function for acceptance of received packets, and must register the callback function with a port using the IP_UDP_Open() function. The callback function, once registered, receives all matching data packets. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 187 7.2 Sending data with the UDP zero-copy API To send data with the UDP zero-copy API, you should proceed as follow: 1. 2. 3. Allocating a packet buffer Filling the allocated buffer Sending the packet The following section describes the procedure for allocating a packet buffer, sending data, and freeing the packet buffer step by step. 7.2.1 Allocating a packet buffer The first step in using the UDP zero-copy API to send data is to allocate a packet buffer from the stack using the IP_UDP_Alloc() function. This function takes the maximum length of the data you intend to send in the buffer as argument and returns a pointer to an IP_PACKET structure. IP_PACKET * pPacket; U32 DataLen; // Amount of data to send DataLen = 512; // Should indicate amount of data to send pPacket = IP_UDP_Alloc(DataLen); if (pPacket == NULL) { // Error, could not allocate packet buffer } This limits how much data you can send in one call using the UDP zero-copy API, as the data sent in one call to IP_UDP_Send() must fit in a single packet buffer. The actual limit is determined by the big packet buffer size, less typically 42 bytes for protocol headers (14 bytes for Ethernet header, 20 bytes IP header, 8 bytes UDP header). If you try to request a larger buffer than this, IP_UDP_Alloc() returns NULL to indicate that it cannot allocate a sufficiently large buffer. 7.2.2 Filling the allocated buffer with data Having allocated the packet buffer, you now fill it with the data to send. The function IP_UDP_Alloc() has initialized the returned IP_PACKET pPacket and so pPacket>pData points to where you can start depositing data. 7.2.3 Sending the packet Finally, you send the packet by giving it back to the stack using the function IP_UDP_Send(). #define SRC_PORT 50020 #define DEST_PORT 50020 #define DEST_ADDR 0xC0A80101 e = IP_UDP_Send(0, DEST_ADDR, SRC_PORT, DEST_PORT, pPacket); if (e < 0) { IP_UDP_Free(pPacket); } This function sends the packet over UDP, or returns an error. If its return value is less than zero, it has not accepted the packet and the application has to decide either to free the packet or to retain it for sending later. Use IP_UDP_SendAndFree() if the packet should be freed automatically in any case. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 188 CHAPTER 7 7.3 UDP zero-copy interface Receiving data with the UDP zero-copy API To receive data with the UDP zero-copy API, you should proceed as follow: 1. 2. 7.3.1 Writing a callback function Registering the callback function Writing a callback function Using the UDP zero-copy API for receiving data requires the application developer to write a callback function that the stack can use to inform the application of received data packets. This function is expected to conform to the following prototype: int rx_callback(IP_PACKET * pPacket, void * pContext) The stack calls this function when it has received a data packet for a port. The parameter pPacket points to the packet buffer. The packet buffer contains the received data for the socket. pPacket->pData points to the start of the received data, and pPacket->NumBytes indicates the number of bytes of received data in this buffer. Returned values The callback function may return one of the following values: Symbolic Nume rical IP_OK 0 IP_OK_KEEP_PACKET 1 Description Data handled. embOS/IP will free the packet. Data will be handled by application later, the stack should NOT free the packet. This will be done by the application at a later time when the data has been handled and the packet is no longer needed. Table 7.1: embOS/IP UDP zero-copy - Valid return values for the receive callback function Note: The callback function is called from the stack and is expected to return promptly. Some of the places where the stack calls the callback function require that the data structures on the stack remain consistent through the callback, so the callback function must not call back into the stack except to call IP_UDP_Free(). 7.3.2 Registering the callback function The application must also inform the stack of the callback function. This is done by calling the IP_UDP_Open() function. The following code fragment illustrates the use of this option to register a callback function named RxUpcall() on the port 50020: #define SRC_PORT 50020 #define DEST_PORT 50020 IP_UDP_Open(0L /* any foreign host */, SRC_PORT, DEST_PORT, RxUpCall, 0L /* any tag */); The function IP_UDP_Open() is described in IP_UDP_Open() on page 201. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 189 7.4 API functions Function IP_UDP_Alloc() IP_UDP_Close() IP_UDP_FindFreePort() IP_UDP_Free() IP_UDP_GetDataSize() IP_UDP_GetDataPtr() IP_UDP_GetDestAddr() IP_UDP_GetFPort() IP_UDP_GetIFIndex() IP_UDP_GetLPort() IP_UDP_GetSrcAddr() IP_UDP_Open() IP_UDP_OpenEx() IP_UDP_Send() IP_UDP_SendAndFree() Description Returns a pointer to a packet buffer big enough for the specified sizes. Closes a UDP connection handle. Returns a free local port number. Frees the buffer which was used for a packet. Returns size of data contained in the received UDP packet. Returns pointer to data contained in the received UDP packet. Retrieves the IP address of the destination of the given UDP packet. Extracts foreign port information from a UDP packet. Extract the interface on which the packet has been received. Extracts local port information from a UDP packet. Retrieves the IP address of the sender of the given UDP packet. Creates a UDP connection handle. Creates a UDP connection handle. Sends an UDP packet to a specified host. Sends an UDP packet to a specified host and frees the packet. Table 7.2: embOS/IP UDP zero-copy API function overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 190 CHAPTER 7 7.4.1 UDP zero-copy interface IP_UDP_Alloc() Description Returns a pointer to a packet buffer big enough for the specified sizes. Prototype IP_PACKET * IP_UDP_Alloc( int NumBytes ); Parameter Parameter NumBytes Description [IN] Length of the data which should be sent. Table 7.3: IP_UDP_Alloc() parameter list Return value Success: Returns a pointer to the allocated buffer. Error: NULL Additional information Applications using the UDP zero-copy API are responsible for allocating packet buffers for use in sending data, as well as for freeing buffers that have been used to receive data and those that the application has allocated but decided not to use for sending data. As these packet buffers are a limited resource, it is important that applications free them promptly when they are no longer of use. The UDP zero-copy interface supports two different approaches to free a packet. One approach is that the stack frees the packet independent from the success of sending the packet. Therefor, IP_UDP_SendAndFree() is called to send the packet and free the packet. It frees the packet independent from the success of the send operation. The other approach is that IP_UDP_Send() is called. In this case it is the responsibility application programmer to free the packet. Depending on the return value the application programmer can decide if IP_UDP_Free() should be called to free the packet. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 191 7.4.2 IP_UDP_Close() Description Closes a UDP connection handle and removes the connection from demux table list of connections and deallocates it. Prototype void IP_UDP_Close( IP_UDP_CONN Con ); Parameter Parameter Con Description [IN] UDP connection handle. Table 7.4: IP_UDP_Close() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 192 CHAPTER 7 7.4.3 UDP zero-copy interface IP_UDP_FindFreePort() Description Obtains a random port number. that is suitable for use as the lport parameter in a call to IP_UDP_Open(). Prototype U16 IP_UDP_FindFreePort( void ); Return value A usable port number in local endianess. Additional information The returned port number is suitable for use as the lport parameter in a call to IP_UDP_Open(). Refer to IP_UDP_Open() on page 201 for more information. IP_UDP_FindFreePort() avoids picking port numbers in the reserved range 0-1024, or in the range 1025-1199, which may be used for server applications. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 193 7.4.4 IP_UDP_Free() Description Frees the buffer which was used for a packet. Prototype void IP_UDP_Free( IP_PACKET * pPacket ); Parameter Parameter pPacket Description [IN] Pointer to a packet structure. Table 7.5: IP_UDP_Free() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 194 CHAPTER 7 7.4.5 UDP zero-copy interface IP_UDP_GetDataSize() Description Returns size of data contained in the received UDP packet. Prototype U16 IP_UDP_GetDataSize( const IP_PACKET *pPacket ); Parameter Parameter pPacket Description [IN] Pointer to a packet structure. Table 7.6: IP_UDP_GetDataSize() parameter list Return value Size of data contained in received UDP packet. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 195 7.4.6 IP_UDP_GetDataPtr() Description Returns pointer to data contained in the received UDP packet. Prototype void * IP_UDP_GetDataPtr( const IP_PACKET * pPacket ); Parameter Parameter pPacket Description [IN] Pointer to a packet structure. Table 7.7: IP_UDP_GetDataPtr() parameter list Return value Pointer to the data part of the UDP packet. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 196 CHAPTER 7 7.4.7 UDP zero-copy interface IP_UDP_GetDestAddr() Description Extracts destination address information from a UDP packet. Prototype void IP_UDP_GetDestAddr( const IP_PACKET * pPacket, void * pDestAddr, int AddrLen ); Parameter Parameter pPacket pDestAddr AddrLen Description [IN] Pointer to a packet structure. [IN] Pointer to a buffer to store the destination address. [IN] Size of the buffer used to store the destination address. Table 7.8: IP_UDP_GetDestAddr() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 197 7.4.8 IP_UDP_GetFPort() Description Extracts foreign port information from a UDP packet. Prototype U16 IP_UDP_GetFPort ( const IP_PACKET * pPacket ); Parameter Parameter pPacket Description [IN] Pointer to a packet structure. Table 7.9: IP_UDP_GetFPort() parameter list Return value Foreign port extracted from the packet. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 198 CHAPTER 7 7.4.9 UDP zero-copy interface IP_UDP_GetIFIndex() Description Extracts the interface information from a UDP packet. Prototype unsigned IP_UDP_GetIFIndex ( const IP_PACKET * pPacket ); Parameter Parameter pPacket Description [IN] Pointer to a packet structure. Table 7.10: IP_UDP_GetIFIndex() parameter list Return value Zero-based interface index on which the packet was received. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 199 7.4.10 IP_UDP_GetLPort() Description Extracts local port information from a UDP packet. Prototype U16 IP_UDP_GetLPort ( const IP_PACKET * pPacket ); Parameter Parameter pPacket Description [IN] Pointer to a packet structure. Table 7.11: IP_UDP_GetLPort() parameter list Return value Local port extracted from the packet. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 200 CHAPTER 7 UDP zero-copy interface 7.4.11 IP_UDP_GetSrcAddr() Description Extracts source address information from a UDP packet. Prototype void IP_UDP_GetSrcAddr( const IP_PACKET * pPacket, void * pSrcAddr, int AddrLen ); Parameter Parameter pPacket pSrcAddr AddrLen Description [IN] Pointer to a packet structure. [IN] Pointer to a buffer to store the source address. [IN] Size of the buffer used to store the source address. Table 7.12: IP_UDP_GetSrcAddr() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 201 7.4.12 IP_UDP_Open() Description Creates a UDP connection handle to receive, and pass upwards UDP packets that match the parameters passed. Prototype IP_UDP_CONN IP_UDP_Open( IP_ADDR U16 U16 int(*routine) void * FAddr, fport, lport, (IP_PACKET *, void * pContext), pContext ); Parameter Parameter FAddr fport lport (*routine) pContext Description [IN] Foreign IP address. [IN] Foreign port. [IN] Local port. [IN] Callback function which is called when a UDP packet is received. [IN/OUT] Application defined context pointer. Table 7.13: IP_UDP_Open() parameter list Return value Success: Returns a pointer to the UDP connection handle. Error: NULL Additional information The parameters FAddr, fport, and lport, can be set to 0 as a wild card, which enables the reception of broadcast datagrams. The callback handler function is called with a pointer to a received datagram and a copy of the data pointer which is passed to IP_UDP_Open(). This can be any data the programmer requires, such as a pointer to another function, or a control structure to aid in demultiplexing the received UDP packet. The returned handle is used as parameter for IP_UDP_Close() IP_UDP_Close() is not called, there is no need to safe the return value. UM07001 User & Reference Guide for embOS/IP only. If (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 202 CHAPTER 7 UDP zero-copy interface 7.4.13 IP_UDP_OpenEx() Description Creates a UDP connection handle to receive, and pass upwards UDP packets that match the parameters passed. Prototype IP_UDP_CONN IP_UDP_OpenEx( IP_ADDR U16 IP_ADDR U16 int(*routine) void * FAddr, fport, LAddr, lport, (IP_PACKET *, void * pContext), pContext ); Parameter Parameter FAddr fport LAddr lport (*routine) pContext Description [IN] Foreign IP address. [IN] Foreign port. [IN] Local IP address. [IN] Local port. [IN] Callback function which is called when a UDP packet is received. [IN/OUT] Application defined context pointer. Table 7.14: IP_UDP_OpenEx() parameter list Return value Success: Returns a pointer to the UDP connection handle. Error: NULL Additional information The parameters FAddr, fport, LAddr and lport, can be set to 0 as a wild card, which enables the reception of broadcast datagrams. The callback handler function is called with a pointer to a received datagram and a copy of the data pointer which is passed to IP_UDP_OpenEx(). This can be any data the programmer requires, such as a pointer to another function, or a control structure to aid in demultiplexing the received UDP packet. The returned handle is used as parameter for IP_UDP_Close() IP_UDP_Close() is not called, there is no need to safe the return value. UM07001 User & Reference Guide for embOS/IP only. If (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 203 7.4.14 IP_UDP_Send() Description Send an UDP packet to a specified host. Prototype int IP_UDP_Send( int IP_ADDR U16 U16 IP_PACKET * IFace, FHost, fport, lport, pPacket ); Parameter Parameter IFace IPAddr fport lport pPacket Description [IN] [IN] [IN] [IN] [IN] Zero-based index of available interfaces. IP address of the target host in network endianess. Foreign port. Local port. Data which should be sent to the target host. Table 7.15: IP_UDP_Send() parameter list Return value On success: 0 On error: Non-zero error code Additional information The packet pPacket has to be allocated by calling IP_UDP_Alloc(). Refer to IP_UDP_Alloc() on page 190 for detailed information. If you expect to get any response to this packet you should have opened a UDP connection prior to calling IP_UDP_Send(). Refer to IP_UDP_Open() on page 201 for more information about creating an UDP connection. IP_UDP_Send() does not free the packet after sending. It is the responsibility of the application programmer to free the packet. Depending on the return value the application programmer can decide if IP_UDP_Free() should be called to free the packet. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 204 CHAPTER 7 UDP zero-copy interface 7.4.15 IP_UDP_SendAndFree() Description Send an UDP packet to a specified host and frees the packet. Prototype int IP_UDP_SendAndFree( int IP_ADDR U16 U16 IP_PACKET * IFace, FHost, fport, lport, pPacket ); Parameter Parameter IFace IPAddr fport lport pPacket Description [IN] [IN] [IN] [IN] [IN] Zero-based index of available interfaces. IP address of the target host in network endianess. Foreign port. Local port. Data which should be sent to the target host. Table 7.16: IP_UDP_SendAndFree() parameter list Return value On success: 0 On error: Non-zero error code Additional information The packet pPacket has to be allocated by calling IP_UDP_Alloc(). Refer to IP_UDP_Alloc() on page 72 for detailed information. If you expect to get any response to this packet you should have opened a UDP connection prior to calling this. Refer to IP_UDP_Open() on page 201 for more information about creating an UDP connection. Packets are freed by calling IP_UDP_Free() is required. UM07001 User & Reference Guide for embOS/IP IP_UDP_SendAndFree(). Therefor, no call of (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 205 Chapter 8 RAW zero-copy interface Transferring RAW data can be used via socket functions or the zero-copy interface which is described in this chapter. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 206 CHAPTER 8 8.1 RAW zero-copy interface RAW zero-copy The RAW zero-copy API functions are provided for systems that do not need the overhead of sockets. These routines impose a lower demand on CPU and system memory requirements than sockets. However, they do not offer the portability of sockets. RAW zero-copy API functions are intended to assist the development of higher-performance embedded network applications by allowing the application direct access to the IP stack packet buffers. This feature can be used to avoid the overhead of having the stack copy data between application-owned buffers and stack-owned buffers in sendto() and recvfrom(), but the application has to fit its data into, and accept its data from the stack buffers. To enable RAW socket support in the IP stack it is madatory to call IP_RAW_Add() on page 77 during initialization of the stack. 8.1.1 Allocating, freeing and sending packet buffers The two functions for allocating and freeing packet buffers are straightforward requests: IP_RAW_Alloc() allocates a packet buffer from the pool of packet buffers on the stack and IP_RAW_Free() frees a packet buffer. Applications using the RAW zerocopy API are responsible for allocating packet buffers for use in sending data, as well as for freeing buffers that have been used to receive data and those that the application has allocated but decided not to use for sending data. As these packet buffers are a limited resource, it is important that applications free them promptly when they are no longer of use. The functions for sending data, IP_RAW_Send() and IP_RAW_SendAndFree(), send a packet buffer of data using a specific protocol or sending pure data which requires the user to include his own IP header. The RAW zero-copy interface supports two different approaches to send and free a packet. One approach is that the stack frees the packet independent from the success of sending the packet. Therefor, IP_RAW_SendAndFree() is called to send and free the packet. It frees the packet independent from the success of the send operation. The other approach is that IP_RAW_Send() is called. In this case it is the responsibility of the application to free the packet. Depending on the return value the application can decide if IP_RAW_Free() should be called to free the packet. 8.1.2 Callback function Applications that use the RAW zero-copy API for receiving data must include a callback function for acceptance of received packets, and must register the callback function with a protocol using the IP_RAW_Open() function. The callback function, once registered, receives all matching data packets. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 207 8.2 Sending data with the RAW zero-copy API To send data with the RAW zero-copy API, you should proceed as follow: 1. 2. 3. Allocating a packet buffer Filling the allocated buffer Sending the packet The following section describes the procedure for allocating a packet buffer, sending data, and freeing the packet buffer step by step. 8.2.1 Allocating a packet buffer The first step in using the RAW zero-copy API to send data is to allocate a packet buffer from the stack using the IP_RAW_Alloc() function. This function takes the maximum length of the data you intend to send in the buffer and if the IP header will be written by the stack or by yourself as arguments and returns a pointer to an IP_PACKET structure. IP_PACKET * pPacket; U32 DataLen; // Amount of data to send DataLen = 512; // Should indicate amount of data to send pPacket = IP_RAW_Alloc(0, DataLen, 0); // Stack will write IP header if (pPacket == NULL) { // Error, could not allocate packet buffer } This limits how much data you can send in one call using the RAW zero-copy API, as the data sent in one call to IP_RAW_Send() must fit in a single packet buffer. The actual limit is determined by the big packet buffer size, less typically 34 bytes for protocol headers (14 bytes for Ethernet header, 20 bytes IP header). If you try to request a larger buffer than this, IP_RAW_Alloc() returns NULL to indicate that it cannot allocate a sufficiently large buffer. If you decide to provide the IP header yourself you can allocate a packet buffer the following way: pPacket = IP_RAW_Alloc(0, DataLen, 1); In this case the packet size allocate limit is determined by the big packet buffer size, less typically 14 bytes for the Ethernet header. 8.2.2 Filling the allocated buffer with data Having allocated the packet buffer, you now fill it with the data to send. The function IP_RAW_Alloc() has initialized the returned IP_PACKET pPacket and so pPacket>pData points to where you can start depositing data. Depending on if you decided to provide your own IP header you will have to store this data starting at pPacket->pData as well. 8.2.3 Sending the packet Finally, you send the packet by giving it back to the stack using the function IP_RAW_Send(). #define PROTOCOL 1 // ICMP #define DEST_ADDR 0xC0A80101 e = IP_RAW_Send(0, DEST_ADDR, PROTOCOL, pPacket); if (e < 0) { IP_RAW_Free(pPacket); } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 208 CHAPTER 8 RAW zero-copy interface This function sends the packet specifying the ICMP protocol in the IP header, or returns an error. If its return value is less than zero, it has not accepted the packet and the application has to decide either to free the packet or to retain it for sending later. Use IP_RAW_SendAndFree() if the packet should be freed automatically in any case. In case you intend to provide your own IP header the protocol passed has to be IPPROTO_RAW . This prevents the stack to generate and include a header on its own. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 209 8.3 Receiving data with the RAW zero-copy API To receive data with the RAW zero-copy API, you should proceed as follow: 1. 2. 8.3.1 Writing a callback function Registering the callback function Writing a callback function Using the RAW zero-copy API for receiving data requires the application developer to write a callback function that the stack can use to inform the application of received data packets. This function is expected to conform to the following prototype: int rx_callback(IP_PACKET * pPacket, void * pContext) The stack calls this function when it has received a data packet for a protocol. The parameter pPacket points to the packet buffer. The packet buffer contains the received data for the socket. pPacket->pData points to the start of the received data (including network and IP header), and pPacket->NumBytes indicates the number of bytes of received data in this buffer. Returned values The callback function may return one of the following values: Nume rical Symbolic IP_OK 0 IP_OK_KEEP_PACKET 1 Description Data handled. embOS/IP will free the packet. Data will be handled by application later, the stack should NOT free the packet. This will be done by the application at a later time when the data has been handled and the packet is no longer needed. Table 8.1: embOS/IP RAW zero-copy - Valid return values for the receive callback function Note: The callback function is called from the stack and is expected to return promptly. Some of the places where the stack calls the callback function require that the data structures on the stack remain consistent through the callback, so the callback function must not call back into the stack except to call IP_RAW_Free(). 8.3.2 Registering the callback function The application must also inform the stack of the callback function. This is done by calling the IP_RAW_Open() function. The following code fragment illustrates the use of this option to register a callback function named RxUpcall() for the ICMP protocol: #define PROTOCOL 1 // ICMP IP_RAW_Open(0L /* any foreign host */, 0L /* any local host */, PROTOCOL, RxUpCall, 0L /* any tag */); The function IP_RAW_Open() is described in IP_RAW_Open() on page 219 . To receive ICMP packets the ICMP protocol has not to be added to the stack by calling IP_ICMP_Add(). Protocols known to the stack and added for handling through the stack can not be used with the RAW zero-copy API. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 210 8.4 CHAPTER 8 RAW zero-copy interface API functions Function IP_RAW_Alloc() IP_RAW_Close() IP_RAW_Free() IP_RAW_GetDataPtr() IP_RAW_GetDataSize() IP_RAW_GetDestAddr() IP_RAW_GetIFIndex() IP_RAW_GetSrcAddr() IP_RAW_Open() IP_RAW_Send() IP_RAW_SendAndFree() Description Returns a pointer to a packet buffer big enough for the specified sizes. Closes a RAW connection handle. Frees the buffer which was used for a packet. Returns pointer to data contained in the received RAW packet. Retrieves the payload size in the packet. Retrieves the IP address of the destination of the given RAW packet. Extract the interface on which the packet has been received. Retrieves the IP address of the sender of the given RAW packet. Creates a RAW connection handle. Sends a RAW packet to a specified host. Sends a RAW packet to a specified host and frees the packet. Table 8.2: embOS/IP RAW zero-copy API function overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 211 8.4.1 IP_RAW_Alloc() Description Returns a pointer to a packet buffer big enough for the specified sizes. Prototype IP_PACKET * IP_RAW_Alloc( unsigned IFaceId, int NumBytes, int IpHdrIncl ); Parameter Parameter IFaceId NumBytes IpHdrIncl Description [IN] Zero-based index of available interfaces. [IN] Length of the data which should be sent. [IN] Specifies if the IP header is generated or has to be provided by the user. 0: Header generated by the stack; 1: Header to be provided in the packet data by the user. Table 8.3: IP_RAW_Alloc() parameter list Return value Success: Returns a pointer to the allocated buffer. Error: NULL Additional information Applications using the RAW zero-copy API are responsible for allocating packet buffers for use in sending data, as well as for freeing buffers that have been used to receive data and those that the application has allocated but decided not to use for sending data. As these packet buffers are a limited resource, it is important that applications free them promptly when they are no longer of use. The RAW zero-copy interface supports two different approaches to free a packet. One approach is that the stack frees the packet independent from the success of sending the packet. Therefor, IP_RAW_SendAndFree() is called to send the packet and free the packet. It frees the packet independent from the success of the send operation. The other approach is that IP_RAW_Send() is called. In this case it is the responsibility application programmer to free the packet. Depending on the return value the application programmer can decide if IP_RAW_Free() should be called to free the packet. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 212 CHAPTER 8 8.4.2 RAW zero-copy interface IP_RAW_Close() Description Closes a RAW connection handle and removes the connection from demux table list of connections and deallocates it. Prototype void IP_RAW_Close( IP_RAW_CONN Con ); Parameter Parameter Con Description [IN] RAW connection handle. Table 8.4: IP_RAW_Close() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 213 8.4.3 IP_RAW_Free() Description Frees the buffer which was used for a packet. Prototype void IP_RAW_Free( IP_PACKET * pPacket ); Parameter Parameter pPacket Description [IN] Pointer to a packet structure. Table 8.5: IP_RAW_Free() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 214 CHAPTER 8 8.4.4 RAW zero-copy interface IP_RAW_GetDataPtr() Description Returns pointer to data contained in the received RAW packet. Prototype void * IP_RAW_GetDataPtr( const IP_PACKET * pPacket ); Parameter Parameter pPacket Description [IN] Pointer to a packet structure. Table 8.6: IP_RAW_GetDataPtr() parameter list Return value Pointer to the data part of the packet. Additional information The data pointer returned points to the start of the network header. Therefore typically 34 bytes header (14 bytes Ethernet header, 20 bytes IP header) are included. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 215 8.4.5 IP_RAW_GetDataSize() Description Returns size of the payload in the received RAW packet. Prototype U16 IP_RAW_GetDataSize( const IP_PACKET *pPacket ); Parameter Parameter pPacket Description [IN] Pointer to a packet structure. Table 8.7: IP_RAW_GetDataSize() parameter list Return value Number of data bytes received in the packet. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 216 CHAPTER 8 8.4.6 RAW zero-copy interface IP_RAW_GetDestAddr() Description Extracts destination address information from a RAW packet. Prototype void IP_RAW_GetDestAddr( const IP_PACKET * pPacket, void * pDestAddr, int AddrLen ); Parameter Parameter pPacket pDestAddr AddrLen Description [IN] Pointer to a packet structure. [IN] Pointer to a buffer to store the destination address. [IN] Size of the buffer used to store the destination address. Table 8.8: IP_RAW_GetDestAddr() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 217 8.4.7 IP_RAW_GetIFIndex() Description Extracts the interface information from a RAW packet. Prototype unsigned IP_RAW_GetIFIndex ( const IP_PACKET * pPacket ); Parameter Parameter pPacket Description [IN] Pointer to a packet structure. Table 8.9: IP_RAW_GetIFIndex() parameter list Return value Zero-based interface index on which the packet was received. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 218 CHAPTER 8 8.4.8 RAW zero-copy interface IP_RAW_GetSrcAddr() Description Extracts source address information from a RAW packet. Prototype void IP_RAW_GetSrcAddr( const IP_PACKET * pPacket, void * pSrcAddr, int AddrLen ); Parameter Parameter pPacket pSrcAddr AddrLen Description [IN] Pointer to a packet structure. [IN] Pointer to a buffer to store the source address. [IN] Size of the buffer used to store the source address. Table 8.10: IP_RAW_GetSrcAddr() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 219 8.4.9 IP_RAW_Open() Description Creates a RAW connection handle to receive, and pass upwards RAW packets that match the parameters passed. Prototype IP_RAW_CONN IP_RAW_Open( IP_ADDR IP_ADDR U8 int(*routine) void * FAddr, LAddr, Protocol, (IP_PACKET *, void * pContext), pContext ); Parameter Parameter FAddr LAddr Protocol (*routine) pContext Description [IN] Foreign IP address. [IN] Local IP address. [IN] IP protocol. [IN] Callback function which is called when a packet of protocol Protocol is received. [IN/OUT] Application defined context pointer. Table 8.11: IP_RAW_Open() parameter list Return value Success: Returns a pointer to the RAW connection handle. Error: NULL Additional information The parameters FAddr and LAddr can be set to 0 as a wild card, which enables the reception of broadcast packets. To enable reception of any protocol use IPPROTO_RAW for Protocol. The callback handler function is called with a pointer to a received protocol and a copy of the data pointer which is passed to IP_RAW_Open(). This can be any data the programmer requires, such as a pointer to another function, or a control structure to aid in demultiplexing the received packet. The returned handle is used as parameter for IP_RAW_Close() IP_RAW_Close() is not called, there is no need to safe the return value. UM07001 User & Reference Guide for embOS/IP only. If (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 220 CHAPTER 8 RAW zero-copy interface 8.4.10 IP_RAW_Send() Description Send a RAW packet to a specified host. Prototype int IP_RAW_Send( int IP_ADDR U8 IP_PACKET * IFace, FHost, Protocol, pPacket ); Parameter Parameter IFace FHost Protocol pPacket Description [IN] Zero-based index of available interfaces. [IN] IP address of the target host in network endianess. [IN] Protocol that will be used in the IP header generated by the stack. [IN] Packet that should be sent to the target host. Table 8.12: IP_RAW_Send() parameter list Return value On success: 0 On error: Non-zero error code Additional information The packet pPacket has to be allocated by calling IP_RAW_Alloc(). Refer to IP_RAW_Alloc() on page 211 for detailed information. If you expect to get any response to this packet you should have opened a RAW connection prior to calling IP_RAW_Send(). Refer to IP_RAW_Open() on page 219 for more information about creating a RAW connection. IP_RAW_Send() does not free the packet after sending. It is the responsibility of the application programmer to free the packet. Depending on the return value the application programmer can decide if IP_RAW_Free() should be called to free the packet. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 221 8.4.11 IP_RAW_SendAndFree() Description Send a RAW packet to a specified host and frees the packet. Prototype int IP_RAW_SendAndFree( int IP_ADDR U8 IP_PACKET * IFace, FHost, Protocol, pPacket ); Parameter Parameter IFace FHost Protocol pPacket Description [IN] Zero-based index of available interfaces. [IN] IP address of the target host in network endianess. [IN] Protocol that will be used in the IP header generated by the stack. [IN] Packet that should be sent to the target host. Table 8.13: IP_RAW_Send() parameter list Return value On success: 0 On error: Non-zero error code Additional information The packet pPacket has to be allocated by calling IP_RAW_Alloc(). Refer to IP_RAW_Alloc() on page 211 for detailed information. If you expect to get any response to this packet you should have opened a RAW connection prior to calling IP_RAW_Send(). Refer to IP_RAW_Open() on page 219 for more information about creating a RAW connection. Packets are freed by calling IP_RAW_Free() is required. UM07001 User & Reference Guide for embOS/IP IP_RAW_SendAndFree(). Therefor, no call of (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 222 UM07001 User & Reference Guide for embOS/IP CHAPTER 8 RAW zero-copy interface (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 223 Chapter 9 DHCP client This chapter explains the usage of the Dynamic Host Control Protocol (DHCP) with embOS/IP. All API functions are described in this chapter. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 224 9.1 CHAPTER 9 DHCP client DHCP backgrounds DHCP stands for Dynamic Host Configuration Protocol. It is designed to ease configuration management of large networks by allowing the network administrator to collect all the IP hosts "soft" configuration information into a single computer. This includes IP address, name, gateway, and default servers. Refer to [RFC 2131] - DHCP - Dynamic Host Configuration Protocol for detailed information about all settings which can be assigned with DHCP. DHCP is a "client/server" protocol, meaning that machine with the DHCP database "serves" requests from DHCP clients. The clients typically initiate the transaction by requesting an IP address and perhaps other information from the server. The server looks up the client in its database, usually by the client's media address, and assigns the requested fields. Clients do not always need to be in the server's database. If an unknown client submits a request, the server may optionally assign the client a free IP address from a "pool" of free addresses kept for this purpose. The server may also assign the client default information of the local network, such as the default gateway, the DNS server, and routing information. When the IP addresses is assigned, it is "leased" to the client for a finite amount of time. The DHCP client needs to keep track of this lease time, and obtain a lease extension from the server before the lease time runs out. Once the lease has elapsed, the client should not send any more IP packets (except DHCP requests) until he get another address. This approach allows computers (such as laptops or factory floor monitors) which will not be permanently attached to the network to share IP addresses and not hog them when they are not using the net. DHCP is just a superset of the Bootstrap Protocol (BOOTP). The main differences between the two are the lease concept, which was created for DHCP, and the ability to assigned addresses from a pool. Refer to [RFC 951] - Bootstrap Protocol for detailed information about the Bootstrap Protocol. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 225 9.2 API functions Function IP_DHCPC_Activate() IP_DHCPC_ConfigOnActivate() IP_DHCPC_ConfigOnFail() IP_DHCPC_ConfigOnLinkDown() IP_DHCPC_GetState() IP_DHCPC_Halt() IP_DHCPC_Renew() IP_DHCPC_SetCallback() Description Activates the DHCP client. Configure behavior on activate. Configure behavior on communication error. Configure behavior on interface link down. Returns the state of the DHCP client. Stops all DHCP client activity. Check configuration with server. Sets a callback for an interface. Table 9.1: embOS/IP DHCP client interface function overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 226 CHAPTER 9 9.2.1 DHCP client IP_DHCPC_Activate() Description Activates the DHCP client. Prototype void IP_DHCPC_Activate ( int IFIndex, const char * sHost, const char * sDomain, const char * sVendor ); Parameter Parameter IFIndex sHost sDomain sVendor Description [IN] Zero-based index number specifying the interface which should request configuration information from a DHCP server. [IN] Pointer to host name to use in negotiation. Can be NULL. [IN] Pointer to domain name to use in negotiation. Can be NULL. [IN] Pointer to vendor to use in negotiation. Can be NULL. Table 9.2: IP_DHCPC_Activate() parameter list Additional information This function is typically called from within IP_X_Config(). This function initializes the DHCP client. It attempts to open a UDP connection to listen for incoming replies and begins the process of configuring a network interface using DHCP. The process may take several seconds, and the DHCP client will keep retrying if the service does not respond. The parameters sHost, sDomain, sVendor are optional (can be NULL). If not NULL, must point to a memory area which remains valid after the call since the string is not copied. Example // Correct function call IP_DHCPC_Activate(0, "Target", NULL, NULL); // Illegal function call char ac; sprintf(ac, "Target%d, Index); IP_DHCPC_Activate(0, ac, NULL, NULL); // Correct function call static char ac; sprintf(ac, "Target%d, Index); IP_DHCPC_Activate(0, ac, NULL, NULL); If you start the DHCP client with activated logging the output on the terminal I/O should be similar to the listing below: DHCP: DHCP: DHCP: DHCP: DHCP: DHCP: DHCP: DHCP: DHCP: DHCP: DHCP: DHCP: DHCP: DHCP: DHCP: Sending discover! Received packet from 192.168.1.1 Packet type is OFFER. Renewal time: 2160 min. Rebinding time: 3780 min. Lease time: 4320 min. Host name received. Sending Request. Received packet from 192.168.1.1 Packet type is ACK. Renewal time: 2160 min. Rebinding time: 3780 min. Lease time: 4320 min. Host name received. IFace 0: IP: 192.168.199.20, Mask: 255.255.0.0, GW: 192.168.1.1. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 227 9.2.2 IP_DHCPC_ConfigOnActivate() Description Configures behavior regarding currently set parameters of an interface when the DHCP client is activated on this interface. Prototype void IP_DHCPC_ConfigOnActivate( int IFaceId, U8 Mode ); Parameter Parameter IFaceId Mode Description [IN] Zero-based interface index to configure. [IN] Mode to configure. The modes that can be setup are listed below. Table 9.3: IP_DHCPC_ConfigOnActivate() parameter list Modes Mode DHCPC_RESET_CONFIG DHCPC_USE_STATIC_CONFIG Description Reset interface when activating the DHCP client on this interface to avoid using old settings longer than necessary. Default. Keep previous static configuration, if any, as fallback configuration as long as no new configuration has been received from a server. Table 9.4: IP_DHCPC_ConfigOnActivate() mode list Additional information This function needs to be called before activating the DHCP client for an interface using IP_DHCPC_Activate() on page 226. Please be aware that activating the DHCP client with a static configured IP address instructs the DHCP client to tryto request this address from the server. In case IP_DHCPC_ConfigOnFail() on page 228 is configured to use DHCP_RESET_CONFIG (default) it might happen that the static IP will be reset if no server is reachable or the IP addr. is declined from a server. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 228 CHAPTER 9 9.2.3 DHCP client IP_DHCPC_ConfigOnFail() Description Configures behavior regarding currently set parameters of an interface when the DHCP client fails in communication to negotiate a configuration with a server. Prototype void IP_DHCPC_ConfigOnFail( int IFaceId, U8 Mode ); Parameter Parameter IFaceId Mode Description [IN] Zero-based interface index to configure. [IN] Mode to configure. The modes that can be setup are listed below. Table 9.5: IP_DHCPC_ConfigOnFail() parameter list Modes Mode DHCPC_RESET_CONFIG DHCPC_USE_STATIC_CONFIG DHCPC_USE_DHCP_CONFIG Description Reset interface to avoid using old settings longer than necessary as they might interfere with other DHCP clients in this network. Default. Setup previous static configuration, if any, as fallback configuration to remain accessible. Keep previously received DHCP configuration. Not recommended as it might interfere with other DHCP clients in this network. Table 9.6: IP_DHCPC_ConfigOnFail() mode list Additional information This function shall be called before activating the DHCP client for an interface using IP_DHCPC_Activate() on page 226. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 229 9.2.4 IP_DHCPC_ConfigOnLinkDown() Description Configures behavior regarding currently set parameters of an interface when the DHCP client is activated on this interface and the link goes down. Prototype void IP_DHCPC_ConfigOnLinkDown( int IFaceId, U32 Timeout, U8 Mode ); Parameter Parameter IFaceId Timeout Mode Description [IN] Zero-based interface index to configure. [IN] Timeout to wait before reacting on link down. [IN] Mode to configure. The modes that can be setup are listed below. Table 9.7: IP_DHCPC_ConfigOnLinkDown() parameter list Modes Mode DHCPC_RESET_CONFIG DHCPC_USE_STATIC_CONFIG DHCPC_USE_DHCP_CONFIG Description Reset interface when link goes down on this interface to avoid using old settings longer than necessary as the target might be connected to another network. Default. Setup previous static configuration, if any, as fallback configuration on link down to allow a quick start once the link goes up again. Keep previously received DHCP configuration on link down as long as the configuration is not declined or a new configuration is received once link on this interface is up again. Table 9.8: IP_DHCPC_ConfigOnLinkDown() mode list Additional information This function shall be called before activating the DHCP client for an interface using IP_DHCPC_Activate() on page 226. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 230 CHAPTER 9 9.2.5 DHCP client IP_DHCPC_GetState() Description Returns the state of the DHCP client. Prototype int IP_DHCPC_GetState( int IFIndex ); Parameter Parameter IFIndex Description [IN] Zero-based index number specifying the interface for which the state should be requested. Table 9.9: IP_DHCPC_GetState() parameter list Return value 0 DHCP client not used. >0 DHCP client in use. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 231 9.2.6 IP_DHCPC_Halt() Description Stops all DHCP activity on a network interface. Prototype void IP_DHCPC_Halt( int IFIndex ); Parameter Parameter IFIndex Description [IN] Zero-based index number specifying the interface which should be halted. Table 9.10: IP_DHCPC_Halt() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 232 CHAPTER 9 9.2.7 DHCP client IP_DHCPC_Renew() Description Sends a request with the currently in use DHCP configuration to the DHCP server to check if the configuration is still valid. Prototype void IP_DHCPC_Renew( int IFaceId ); Parameter Parameter IFaceId Description [IN] Zero-based interface index. Table 9.11: IP_DHCPC_Renew() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 233 9.2.8 IP_DHCPC_SetCallback() Description This function allows the caller to set a callback for an interface. Prototype void IP_DHCPC_SetCallback( int IFIndex, int (*routine)(int,int) ); Parameter Parameter IFIndex (*routine) Description [IN] Zero-based index number of available network interfaces. [IN] Callback functions which should be called with every status change. Table 9.12: IP_DHCPC_SetCallback() parameter list Additional information The callback is called with every status change. This mechanism is provided so that the caller can do some processing when the interface is up (like doing initialization or blinking LEDs, etc.). Refer to [RFC 2331] DHCP - Dynamic Host Configuration Protocol for detailed information about DHCP states. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 234 UM07001 User & Reference Guide for embOS/IP CHAPTER 9 DHCP client (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 235 Chapter 10 DHCP server (Add-on) The embOS/IPThis implementation of the DHCP server is an optional extension to embOS/IP. It allows setting up a Dynamic Host Control Protocol (DHCP) server that seamlessly integrates with embOS/IP. All API functions are described in this chapter. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 236 CHAPTER 10 DHCP server (Add-on) 10.1 DHCP backgrounds DHCP stands for Dynamic Host Configuration Protocol. It is designed to ease configuration management of large networks by allowing the network administrator to collect all the IP hosts "soft" configuration information into a single computer. This includes IP address, name, gateway, and default servers. Refer to [RFC 2131] - DHCP - Dynamic Host Configuration Protocol for detailed information about all settings which can be assigned with DHCP. Further information can be found in the chapter DHCP backgrounds on page 224 in the description of the DHCP client. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 237 10.2 API functions Function IP_DHCPS_ConfigDNSAddr() IP_DHCPS_ConfigGWAddr() IP_DHCPS_ConfigMaxLeaseTime() IP_DHCPS_ConfigPool() IP_DHCPS_Halt() IP_DHCPS_Init() IP_DHCPS_Start() Description Configure the DNS servers to distribute. Configure the gateway to distribute. Configure the max. lease time to grant. Configures the IP pool to use. Halts the DHCP server. Initializes the DHCP server. Starts the DHCP server. Table 10.1: embOS/IP DHCP server interface function overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 238 CHAPTER 10 DHCP server (Add-on) 10.2.1 IP_DHCPS_ConfigDNSAddr() Description Configures DNS servers to assign to clients. Prototype int IP_DHCPS_ConfigDNSAddr ( unsigned IFIndex, U32 *paDNSAddr, U8 NumServers ); Parameter Parameter IFIndex paDNSAddr NumServers Description [IN] Zero-based interface index on which the server will be running. [IN] Array of IPv4 addresses of DNS servers to use. [IN] Number of DNS servers in array. Table 10.2: IP_DHCPS_ConfigDNSAddr() parameter list Return value 0: O.K. Other: Error. Additional information Configuring DNS server settings is optional. If no DNS servers are configured no DNS servers will be assigned to clients. Needs to be called before activating the DHCP server for this interface with IP_DHCPS_Start() on page 244. Example U32 aDNSAddr[2]; // // Setup DNS addr. as needed. // aDNSAddr[0] = IP_BYTES2ADDR(192, 168, 12, 1); aDNSAddr[1] = IP_BYTES2ADDR(192, 168, 12, 2); IP_DHCPS_ConfigDNSAddr(0, &aDNSAddr[0], 2); IP_DHCPS_ConfigPool(0, IP_BYTES2ADDR(192, 168, 12, 11), 0xFFFF0000, 20); IP_DHCPS_Init(0); IP_DHCPS_Start(0); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 239 10.2.2 IP_DHCPS_ConfigGWAddr() Description Configures the gateway addr. that will be assign to clients. Prototype int IP_DHCPS_ConfigGWAddr ( unsigned IFIndex, U32 GWAddr ); Parameter Parameter IFIndex GWAddr Description [IN] Zero-based interface index on which the server will be running. [IN] IP addr. of gateway. Table 10.3: IP_DHCPS_ConfigGWAddr() parameter list Return value 0: O.K. Other: Error. Additional information Configuring a gateway setting is optional. If no gateway is configured no gateway will be assigned to clients. Needs to be called before activating the DHCP server for this interface with IP_DHCPS_Start() on page 244. Example IP_DHCPS_ConfigGWAddr(0, IP_BYTES2ADDR(192, 168, 12, 1)); IP_DHCPS_ConfigPool(0, IP_BYTES2ADDR(192, 168, 12, 11), 0xFFFF0000, 20); IP_DHCPS_Init(0); IP_DHCPS_Start(0); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 240 CHAPTER 10 DHCP server (Add-on) 10.2.3 IP_DHCPS_ConfigMaxLeaseTime() Description Configures the maximum lease time that a client will be granted to use the achieved configuration. Prototype int IP_DHCPS_ConfigMaxLeaseTime ( unsigned IFIndex, U32 Seconds ); Parameter Parameter IFIndex Seconds Description [IN] Zero-based interface index on which the server will be running. [IN] Maximum lease time in seconds. Default 7200s => 2h. Table 10.4: IP_DHCPS_ConfigMaxLeaseTime() parameter list Return value 0: O.K. Other: Error. Additional information Optional. Needs to be called before activating the DHCP server for this interface with IP_DHCPS_Start() on page 244. Example IP_DHCPS_ConfigMaxLeaseTime(0, 7200); IP_DHCPS_ConfigPool(0, IP_BYTES2ADDR(192, 168, 12, 11), 0xFFFF0000, 20); IP_DHCPS_Init(0); IP_DHCPS_Start(0); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 241 10.2.4 IP_DHCPS_ConfigPool() Description Configures the IP address pool that can be assigned to DHCP clients. Prototype int IP_DHCPS_ConfigPool ( unsigned U32 U32 U32 IFIndex, StartIPAddr, SNMask, PoolSize ); Parameter Parameter IFIndex StartIPAddr SNMask PoolSize Description [IN] [IN] [IN] [IN] Zero-based interface index on which the server will be running. First IP addr. of the pool. Subnet mask to assign to clients. Number of IP addresses in pool starting from StartIPAddr. Table 10.5: IP_DHCPS_ConfigPool() parameter list Return value 0: O.K. Other: Error. Additional information Needs to be called before activating the DHCP server for this interface with IP_DHCPS_Start() on page 244. Example IP_DHCPS_ConfigPool(0, IP_BYTES2ADDR(192, 168, 12, 11), 0xFFFF0000, 20); IP_DHCPS_Init(0); IP_DHCPS_Start(0); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 242 CHAPTER 10 DHCP server (Add-on) 10.2.5 IP_DHCPS_Halt() Description Halts the DHCP server on a specific interface. Prototype void IP_DHCPS_Halt ( unsigned IFIndex ); Parameter Parameter IFIndex Description [IN] Zero-based interface index on which the server is running. Table 10.6: IP_DHCPS_Halt() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 243 10.2.6 IP_DHCPS_Init() Description Initializes a DHCP server instance for an interface. Prototype int IP_DHCPS_Init ( unsigned IFIndex ); Parameter Parameter IFIndex Description [IN] Zero-based interface index on which the server will be running. Table 10.7: IP_DHCPS_Init() parameter list Return value 0: O.K. Other: Error. Additional information Needs to be called before activating the DHCP server for this interface with IP_DHCPS_Start() on page 244. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 244 CHAPTER 10 DHCP server (Add-on) 10.2.7 IP_DHCPS_Start() Description Starts a DHCP server instance on an interface. Prototype int IP_DHCPS_Start ( unsigned IFIndex ); Parameter Parameter IFIndex Description [IN] Zero-based interface index on which the server will be running. Table 10.8: IP_DHCPS_Start() parameter list Return value 0: O.K. Other: Error. Additional information IP_DHCPS_Init() on page 243 and IP_DHCPS_ConfigPool() on page 241 need to be called before activating the DHCP server for an interface in order to set at least the minimum configurations. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 245 10.3 DHCP server resource usage The ROM usage depends on the compiler options, the compiler version and the used CPU. The memory requirements of the DHCP server modules presented in the tables below have been measured on an ARM7 and a Cortex-M3 system. Details about the further configuration can be found in the sections of the specific example. 10.3.1 ROM usage on an ARM7 system The following resource usage has been measured on an ARM7 system using IAR Embedded Workbench V6.30.6, Thumb mode, no interwork, size optimization. Addon embOS/IP DHCP server ROM approximately 2.0Kbyte Table 10.9: DHCP server ROM usage ARM7 10.3.2 ROM usage on a Cortex-M3 system The following resource usage has been measured on a Cortex-M3 system using IAR Embedded Workbench V6.30.6, size optimization. Addon embOS/IP DHCP server ROM approximately 2.0Kbyte Table 10.10: DHCP server ROM usage Cortex-M3 10.3.3 RAM usage Addon embOS/IP DHCP server RAM approximately 200 bytes Table 10.11: DHCP server RAM usage UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 246 UM07001 User & Reference Guide for embOS/IP CHAPTER 10 DHCP server (Add-on) (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 247 Chapter 11 AutoIP All functions which are required to add AutoIP to your application are described in this chapter. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 248 CHAPTER 11 AutoIP 11.1 embOS/IP AutoIP backgrounds The embOS/IP AutoIP module adds the dynamic configuration of IPv4 Link-Local addresses to embOS/IP. This functionality is better known as AutoIP. Therefore, this term will be used in this document. The AutoIP implementation covers the relevant parts of the following RFCs: RFC# [RFC 3972] Description Dynamic Configuration of IPv4 Link-Local Addresses. Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc3972.txt In general AutoIP is a method to negotiate a IPv4 address in a network without the utilization of a server such as a DHCP server. AutoIP will try to use IPv4 addresses out of a reserved pool from the addresses 169.254.1.0 to 169.254.254.255 to find a free IP that is not used by any other network participant at this time. To achieve this goal AutoIP sends ARP probes into the network to ask if the addr. to be used is already in use. This is determined by an ARP reply for the requested address. Upon an address conflict AutoIP will generate a new address to use and will retry to use it by sending ARP probes again. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 249 11.2 API functions Function IP_AutoIP_Activate() IP_AutoIP_Halt() IP_AutoIP_SetUserCallback() IP_AutoIP_SetStartIP() Description Activates AutoIP. Stops all AutoIP activity. Sets a callback to get a notification about each status change. Sets the IP address which will be used for the first configuration try. Table 11.1: embOS/IP AutoIP interface function overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 250 CHAPTER 11 AutoIP 11.2.1 IP_AutoIP_Activate() Description Activates AutoIP for the specified interface. Prototype void IP_AutoIP_Activate ( unsigned IFaceId ); Parameter Parameter IFaceId Description [IN] Zero-based interface index. Table 11.2: IP_AutoIP_Activate() parameter list Additional information Activating the dynamic configuration of IPv4 Link-Local addresses means that an additional timer will be added to the stack. This timer will be called every second to check the status of the address configuration. With the AutoIP activation an IP address for the dynamic configuration will be created. The IPv4 prefix 169.254/16 is registered with the IANA for this purpose. This means that embOS/IP will generate an IP address similar to 169.254.xxx.xxx. The subnet mask of is always 255.255.0.0. In embOS/IP debug builds terminal I/O output can be enabled. AutoIP outputs status information in the terminal I/O window if the stack is configured to so (IP_MTYPE_AUTOIP added to the log filter mask). Please refer to IP_SetLogFilter() on page 547 and IP_AddLogFilter() on page 545 for further information about the enabling terminal I/O. If terminal I/O is enabled the output of a the program start should be similar to the following lines: 0:000 0:000 0:000 0:000 0:000 0:000 3:000 9:000 9:000 MainTask - INIT: Init started. Version 2.00.06 MainTask - DRIVER: Found PHY with Id 0x2000 at addr 0x1 MainTask - INIT: Link is down MainTask - INIT: Init completed IP_Task - INIT: IP_Task started IP_RxTask - INIT: IP_RxTask started IP_Task - LINK: Link state changed: Full duplex, 100 MHz IP_Task - AutoIP: 169.254.240.240 checked, no conflicts IP_Task - AutoIP: IFaceId 0: Using IP: 169.254.240.240. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 251 11.2.2 IP_AutoIP_Halt() Description Stops AutoIP activity for the passed interface. Prototype void IP_AutoIP_Halt ( unsigned IFaceId U8 KeepIP ); Parameter Parameter IFaceId KeepIP Description [IN] Zero-based interface index. [IN] Flag to indicate if the used IP address should be stored for the next start of AutoIP. 0 means do not keep the IP, 1 means keep the IP address for the next AutoIP start. Table 11.3: IP_AutoIP_Halt() parameter list Return value 0 : Ok. AutoIP stopped. IP address cleared. IP : Ok. AutoIP stopped. The IP address (for example, 0xA9FExxxx) has been kept. -1 : Error. Illegal interface number. Additional information The function stops the AutoIP module. The IP address which was used during AutoIP was activated, can be kept to speed up the configuration process after reactivating AutoIP. If the IP address will not be kept, AutoIP creates a new IP address after the reactivation. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 252 CHAPTER 11 AutoIP 11.2.3 IP_AutoIP_SetUserCallback() Description Sets a callback function. It will be called with every status change. Prototype void IP_AutoIP_SetUserCallback( unsigned IFaceId, IP_AUTOIP_INFORM_USER_FUNC * pfInformUser ); Parameter Parameter IFaceId pfInformUser Description [IN] Zero-based interface index. [IN] Pointer to a user function of type IP_AUTOIP_INFORM_USER_FUNC which is called when a status change occurs. Table 11.4: IP_AutoIP_SetCallback() parameter list Additional Information The possibility to set a callback function is provided so that the caller can do some processing when the interface is up (like doing initializations or blinking LEDs, etc.). IP_AUTOIP_INFORM_USER_FUNC is defined as follows: typedef void (IP_AUTOIP_INFORM_USER_FUNC)(U32 IFaceId, U32 Status); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 253 11.2.4 IP_AutoIP_SetStartIP() Description Sets the IP address which will be used for the first configuration try. Prototype void IP_AutoIP_SetStartIP( unsigned IFaceId, U32 IPAddr ); Parameter Parameter IFaceId IPAddr Description [IN] Zero-based interface index. [IN] 4-byte IPv4 address. Table 11.5: IP_AutoIP_SetCallback() parameter list Additional information A call of this function is normally not required, but in some cases it can be useful to set the IP address which should be used as starting point of the AutoIP functionality. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 254 CHAPTER 11 AutoIP 11.3 AutoIP resource usage The ROM usage depends on the compiler options, the compiler version and the used CPU. The memory requirements of the AutoIP module presented in the tables below have been measured on an ARM7 and a Cortex-M3 system. Details about the further configuration can be found in the sections of the specific example. 11.3.1 ROM usage on an ARM7 system The following resource usage has been measured on an ARM7 system using IAR Embedded Workbench V6.30.6, Thumb mode, no interwork, size optimization. Addon embOS/IP AutoIP module ROM approximately 1.1Kbyte Table 11.6: AutoIP ROM usage ARM7 11.3.2 ROM usage on a Cortex-M3 system The following resource usage has been measured on a Cortex-M3 system using IAR Embedded Workbench V6.30.6, size optimization. Addon embOS/IP AutoIP module ROM approximately 1.0Kbyte Table 11.7: AutoIP ROM usage Cortex-M3 11.3.3 RAM usage Addon embOS/IP AutoIP module RAM approximately 0.7Kbyte Table 11.8: AutoIP RAM usage UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 255 Chapter 12 Address Collision Detection All functions which are required to add Address Collision Detection (ACD) to your application are described in this chapter. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 256 CHAPTER 12 Address Collision Detection 12.1 embOS/IP ACD backgrounds The embOS/IP ACD module allows the user specific configuration of the behavior if an IPv4 address collision is detected. This means that more than one host in the network is using the same IPv4 address at the same time. This is discovered sending ARP discover packets to find hosts with the same addresses in the network. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 257 12.2 API functions Function IP_ACD_Activate() IP_ACD_Config() Description Activates ACD. Configures parameter for ACD. Table 12.1: embOS/IP ACD interface function overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 258 CHAPTER 12 Address Collision Detection 12.2.1 IP_ACD_Activate() Description Activates ACD for the specified interface. Prototype int IP_ACD_Activate ( unsigned IFace ); Parameter Parameter IFace Description [IN] Zero-based interface index. Table 12.2: IP_ACD_Activate() parameter list Return value 0 ACD activated and free IP found (does not mean the initial IP was good) 1 No IP address set when ACD was activated Additional information Activating the address conflict detection module means that a a hook into the ARP module of the stack will be activated that allows the user to take action if an IPv4 address conflict on the network has been discovered. When the ACD module is started it will check if the currently used IP address is in conflict with any other host on the network by sending ARP probes to find hosts with the same IPv4 address. To allow the user to take action on those conflicts it is necessary to use IP_ACD_Config() on page 259 before activating ACD. In embOS/IP debug builds terminal I/O output can be enabled. ACD outputs status information in the terminal I/O window if the stack is configured to so (IP_MTYPE_ACD added to the log filter mask). Please refer to IP_SetLogFilter() on page 547 and IP_AddLogFilter() on page 545 for further information about the enabling terminal I/ O. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 259 12.2.2 IP_ACD_Config() Description Configures ACD behavior for startup and in case of conflicts. Prototype void IP_ACD_Config ( unsigned unsigned unsigned const ADC_FUNC * IFace ProbeNum DefendInterval pACDContext ); Parameter Parameter IFace ProbeNum DefendInterval pACDContext Description [IN] Zero-based interface index. [IN] Number of ARP probes to send upon activating ACD before declaring the actual used IP address to be free to be used. [IN] Interval in which the currently active IP address is being known as defended after taking action. [IN] Pointer to a structure of type ACD_FUNC. Table 12.3: IP_ACD_Config() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 260 CHAPTER 12 Address Collision Detection 12.3 ACD data structures 12.3.1 Structure ACD_FUNC Description Used to store function pointers to the user defined callbacks to take several actions upon detecting an IP address conflict. Prototype typedef struct ACD_FUNC { U32 (*pfRenewIPAddr); int (*pfDefend); int (*pfRestart); } ACD_FUNC; Member Description Function pointer to a user defined routine that is used to generate a pfRenewIPAddr new IPv4 address if there is a collision detected during ACD activation. Function pointer to a user defined routine that is used to let the pfDefend user implement his own defend strategy. Can be NULL. Function pointer to a user defined routine that should reconfigure pfRestart the IP address used by the stack and optionally re-activates ACD. Table 12.4: Structure ACD_FUNC member list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 261 12.4 ACD resource usage The ROM usage depends on the compiler options, the compiler version and the used CPU. The memory requirements of the AutoIP module presented in the tables below have been measured on an ARM7 and a Cortex-M3 system. Details about the further configuration can be found in the sections of the specific example. 12.4.1 ROM usage on an ARM7 system The following resource usage has been measured on an ARM7 system using IAR Embedded Workbench V6.30.6, Thumb mode, no interwork, size optimization. Addon embOS/IP ACD module ROM approximately 0.4Kbyte Table 12.5: ACD ROM usage ARM7 12.4.2 ROM usage on a Cortex-M3 system The following resource usage has been measured on a Cortex-M3 system using IAR Embedded Workbench V6.30.6, size optimization. Addon embOS/IP ACD module ROM approximately 0.4Kbyte Table 12.6: ACD ROM usage Cortex-M3 12.4.3 RAM usage Addon embOS/IP ACD module RAM approximately 50Bytes Table 12.7: ACD RAM usage UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 262 UM07001 User & Reference Guide for embOS/IP CHAPTER 12 Address Collision Detection (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 263 Chapter 13 UPnP (Add-on) The embOS/IP implementation of UPnP which stand for Universal Plug and Play is an optional extension to embOS/IP. It allows making your target easily discoverable and advertising services available on your target throughout your network. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 264 CHAPTER 13 UPnP (Add-on) 13.1 embOS/IP UPnP The embOS/IP UPnP implementation is an optional extension which can be seamlessly integrated into your TCP/IP application. It combines the possibility to implemented UPnP services in a most flexible way by allowing to specify content to be sent upon UPnP requests completely generated by the application with a small memory footprint. The UPnP module implements the relevant parts of the UPnP documentation released by the UPnP Forum. Document UPnP Device Architecture 1.0 Download Direct download: http://upnp.org/specs/arch/UPnParch-DeviceArchitecture-v1.0.pdf The following table shows the contents of the embOS/IP root directory: Directory Content Application Contains the example application to run the UPnP implementation with embOS/IP and embOS/IP Web server add-on. IP Contains the UPnP source file, IP_UPnP.c . Supplied directory structure of embOS/IP UPnP package UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 265 13.2 Feature list * * * Low memory footprint. Advertising your services on the network Easy to implement UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 266 CHAPTER 13 UPnP (Add-on) 13.3 Requirements TCP/IP stack The embOS/IP UPnP implementation requires the embOS/IP TCP/IP stack and is designed to be used with the embOS/IP Web server add-on. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 267 13.4 UPnP backgrounds UPnP is designed to provide services throughout a network without interaction of the user. It is designed to use standardised protocols such as IP, TCP, UDP, Multicast, HTTP and XML for communication and to dirstribute services provided by a device. UPnP can be used to advertise services provided by a device across the network such as where to find the web interface for the device advertising. Newer operating systems support UPnP from scratch and will show UPnP devices available across a network and may provide easy access to a device by simply selecting the discovered UPnP device. A typical usage would be to advertise media accessible on a media storage on the network and opening a file browser window to the resource upon opening the UPnP entry discovered. 13.4.1 Using UPnP to advertise your service in the network The default UPnP XML file advertised is upnp.xml. A solution providing UPnP content has to serve a file called upnp.xml containing valid UPnP descriptors via a web server. The sample OS_IP_Webserver_UPnP.c provides a sample configuration for advertising a web server page that will open if the UPnP client clicks on the discovered UPnP device. A discovered UPnP device will typically be shown in the network neighborhood of your operating system. A discovered device found by a Windows OS is shown in the picture below: The example below shows the most important excerpts from the OS_IP_Webserver_UPnP.c sample that are necessary to setup a UPnP device in your network. Example The sample provides some easy to use defines to adopt the identification strings used by the UPnP device to advertise itself to be changed to your needs. /* Excerpt from OS_IP_Webserver_UPnP.c */ // // UPnP // #define UPNP_FRIENDLY_NAME "SEGGER UPnP Demo" #define UPNP_MANUFACTURER "SEGGER Microcontroller GmbH and Co. KG" // '&' is not allowed #define UPNP_MANUFACTURER_URL "http://www.segger.com" #define UPNP_MODEL_DESC "SEGGER Web server with UPnP" #define UPNP_MODEL_NAME "SEGGER UPnP Demo" #define UPNP_MODEL_URL "http://www.segger.com/embos-ip-webserver.html" The sample uses VFile hooks as described in IP_WEBS_AddVFileHook() on page 384 to provide dynamically serving the necessary XML files for UPnP without the need for a real file system or further processing through the web server. /* Excerpt from OS_IP_Webserver_UPnP.c */ /********************************************************************* * * Types * ********************************************************************** */ typedef struct { const char * sFileName; const char * pData; UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 268 CHAPTER 13 unsigned } VFILE_LIST; UPnP (Add-on) NumBytes; /* Excerpt from OS_IP_Webserver_UPnP.c */ /********************************************************************* * * Static const * ********************************************************************** */ // // UPnP, virtual files // static const char _acFile_dummy_xml[] = "<?xml version=\"1.0\" encoding=\"utf-8\"?>\r\n" "<scpd xmlns=\"urn:schemas-upnp-org:service-1-0\">\r\n" "<specVersion>\r\n" "<major>1</major>\r\n" "<minor>0</minor>\r\n" "</specVersion>\r\n" "<serviceStateTable>\r\n" "<stateVariable>\r\n" "<name>Dummy</name>\r\n" "<dataType>i1</dataType>\r\n" "</stateVariable>\r\n" "</serviceStateTable>\r\n" "</scpd>"; // // UPnP, virtual files list // static const VFILE_LIST _VFileList[] = { "/dummy.xml", _acFile_dummy_xml, sizeof(_acFile_dummy_xml) - 1, the null terminator of the string NULL , NULL , NULL }; // Do not count in /* Excerpt from OS_IP_Webserver_UPnP.c */ // // UPnP webserver VFile hook // static WEBS_VFILE_HOOK _UPnP_VFileHook; Several helper functions are provided in the sample to easily generate a valid XML file for advertising a service using UPnP. /* Excerpt from OS_IP_Webserver_UPnP.c */ // // UPnP // #define UPNP_FRIENDLY_NAME "SEGGER UPnP Demo" #define UPNP_MANUFACTURER "SEGGER Microcontroller GmbH and Co. KG" // '&' is not allowed #define UPNP_MANUFACTURER_URL "http://www.segger.com" #define UPNP_MODEL_DESC "SEGGER Web server with UPnP" #define UPNP_MODEL_NAME "SEGGER UPnP Demo" #define UPNP_MODEL_URL "http://www.segger.com/embos-ip-webserver.html" /* Excerpt from OS_IP_Webserver_UPnP.c */ /********************************************************************* * * Static code * ********************************************************************** */ /********************************************************************* UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 269 * * _UPnP_GetURLBase * * Function description * This function copies the information needed for the URLBase parameter * into the given buffer and returns a pointer to the start of the buffer * for easy readable code. * * Parameters * pBuffer - Pointer to the buffer that can be temporarily used to * store the requested data. * NumBytes - Size of the given buffer used for checks * * Return value * Pointer to the start of the buffer used for storage. */ static const char * _UPnP_GetURLBase(char * pBuffer, unsigned NumBytes) { #define URL_BASE_PREFIX "http://" char * p; p = pBuffer; *p = '\0'; // Just to be on the safe if the buffer is too small strncpy(pBuffer, URL_BASE_PREFIX, NumBytes); p += (sizeof(URL_BASE_PREFIX) - 1); NumBytes -= (sizeof(URL_BASE_PREFIX) - 1); IP_PrintIPAddr(p, IP_GetIPAddr(INTERFACE), NumBytes); return pBuffer; } /********************************************************************* * * _UPnP_GetModelNumber * * Function description * This function copies the information needed for the ModelNumber parameter * into the given buffer and returns a pointer to the start of the buffer * for easy readable code. * * Parameters * pBuffer - Pointer to the buffer that can be temporarily used to * store the requested data. * NumBytes - Size of the given buffer used for checks * * Return value * Pointer to the start of the buffer used for storage. */ static const char * _UPnP_GetModelNumber(char * pBuffer, unsigned NumBytes) { U8 aHWAddr[6]; if (NumBytes <= 12) { *pBuffer = '\0'; // Just to be on the safe if the buffer is too small } else { IP_GetHWAddr(INTERFACE, aHWAddr, sizeof(aHWAddr)); snprintf(pBuffer, NumBytes, "%02X%02X%02X%02X%02X%02X", aHWAddr[0], aHWAddr[1], aHWAddr[2], aHWAddr[3], aHWAddr[4], aHWAddr[5]); } return pBuffer; } /********************************************************************* * * _UPnP_GetSN * * Function description * This function copies the information needed for the SerialNumber parameter * into the given buffer and returns a pointer to the start of the buffer UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 270 CHAPTER 13 UPnP (Add-on) * for easy readable code. * * Parameters * pBuffer - Pointer to the buffer that can be temporarily used to * store the requested data. * NumBytes - Size of the given buffer used for checks * * Return value * Pointer to the start of the buffer used for storage. */ static const char * _UPnP_GetSN(char * pBuffer, unsigned NumBytes) { U8 aHWAddr[6]; if (NumBytes <= 12) { *pBuffer = '\0'; // Just to be on the safe if the buffer is too small } else { IP_GetHWAddr(INTERFACE, aHWAddr, sizeof(aHWAddr)); snprintf(pBuffer, NumBytes, "%02X%02X%02X%02X%02X%02X", aHWAddr[0], aHWAddr[1], aHWAddr[2], aHWAddr[3], aHWAddr[4], aHWAddr[5]); } return pBuffer; } /********************************************************************* * * _UPnP_GetUDN * * Function description * This function copies the information needed for the UDN parameter * into the given buffer and returns a pointer to the start of the buffer * for easy readable code. * * Parameters * pBuffer - Pointer to the buffer that can be temporarily used to * store the requested data. * NumBytes - Size of the given buffer used for checks * * Return value * Pointer to the start of the buffer used for storage. */ static const char * _UPnP_GetUDN(char * pBuffer, unsigned NumBytes) { #define UDN_PREFIX "uuid:95232DE0-3AF7-11E2-81C1-" char * p; U8 aHWAddr[6]; p = pBuffer; *pBuffer = '\0'; // Just to be on the safe if the buffer is too small strncpy(pBuffer, UDN_PREFIX, NumBytes); p += (sizeof(UDN_PREFIX) - 1); NumBytes -= (sizeof(UDN_PREFIX) - 1); if (NumBytes > 12) { IP_GetHWAddr(INTERFACE, aHWAddr, sizeof(aHWAddr)); snprintf(p, NumBytes, "%02X%02X%02X%02X%02X%02X", aHWAddr[0], aHWAddr[1], aHWAddr[2], aHWAddr[3], aHWAddr[4], aHWAddr[5]); } return pBuffer; } /********************************************************************* * * _UPnP_GetPresentationURL * * Function description * This function copies the information needed for the presentation URL parameter * into the given buffer and returns a pointer to the start of the buffer * for easy readable code. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 271 * * Parameters * pBuffer - Pointer to the buffer that can be temporarily used to * store the requested data. * NumBytes - Size of the given buffer used for checks * * Return value * Pointer to the start of the buffer used for storage. */ static const char * _UPnP_GetPresentationURL(char * pBuffer, unsigned NumBytes) { #define PRESENTATION_URL_PREFIX "http://" #define PRESENTATION_URL_POSTFIX "/index.htm" char * p; int i; p = pBuffer; *p = '\0'; // Just to be on the safe if the buffer is too small strncpy(pBuffer, PRESENTATION_URL_PREFIX, NumBytes); p += (sizeof(PRESENTATION_URL_PREFIX) - 1); NumBytes -= (sizeof(PRESENTATION_URL_PREFIX) - 1); i = IP_PrintIPAddr(p, IP_GetIPAddr(INTERFACE), NumBytes); p += i; NumBytes -= i; strncat(pBuffer, PRESENTATION_URL_POSTFIX, NumBytes); return pBuffer; } /********************************************************************* * * _UPnP_GenerateSend_upnp_xml * * Function description * Send the content for the requested file using the callback provided. * * Parameters * pContextIn - Send context of the connection processed for * forwarding it to the callback used for output. * pf - Function pointer to the callback that has to be * for sending the content of the VFile. * pContextOut - Out context of the connection processed. * pData - Pointer to the data that will be sent * NumBytes - Number of bytes to send from pData. If NumBytes * is passed as 0 the send function will run a strlen() * on pData expecting a string. * * Notes * (1) The data does not need to be sent in one call of the callback * routine. The data can be sent in blocks of data and will be * flushed out automatically at least once returning from this * routine. */ static void _UPnP_GenerateSend_upnp_xml(void * pContextIn, void (*pf) (void * pContextOut, const char * pData, unsigned NumBytes)) { char ac[128]; pf(pContextIn, "<?xml version=\"1.0\"?>\r\n" "<root xmlns=\"urn:schemas-upnp-org:device-1-0\">\r\n" "<specVersion>\r\n" "<major>1</major>\r\n" "<minor>0</minor>\r\n" "</specVersion>\r\n" , 0); pf(pContextIn, Base>" pf(pContextIn, UM07001 User & Reference Guide for embOS/IP _UPnP_GetURLBase(ac, "<URL, 0); sizeof(ac)) (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 272 CHAPTER 13 UPnP (Add-on) , 0); pf(pContextIn, "</URL- Base>\r\n" , 0); pf(pContextIn, "<device>\r\n" "<deviceType>urn:schemas-upnp-org:device:Basic:1</deviceType>\r\n" , 0); pf(pContextIn, "<friendlyName>" UPNP_FRIENDLY_NAME "</friendlyName>\r\n" , 0); pf(pContextIn, "<manufacturer>" UPNP_MANUFACTURER "</manufacturer>\r\n" , 0); pf(pContextIn, "<manufacturerURL>" UPNP_MANUFACTURER_URL "</manufacturerURL>\r\n" , 0); pf(pContextIn, "<modelDescription>" UPNP_MODEL_DESC "</modelDescription>\r\n" , 0); pf(pContextIn, "<modelName>" UPNP_MODEL_NAME "</modelName>\r\n" , 0); pf(pContextIn, ber>" "<modelNum, 0); _UPnP_GetModelNumber(ac, pf(pContextIn, sizeof(ac)) , 0); pf(pContextIn, "</modelNum- ber>\r\n" , 0); pf(pContextIn, lURL>\r\n" "<modelURL>" , 0); UPNP_MODEL_URL pf(pContextIn, ber>" "<serialNum, 0); _UPnP_GetSN(ac, pf(pContextIn, "</mode- sizeof(ac)) , 0); pf(pContextIn, ber>\r\n" "</serialNum, 0); pf(pContextIn, "<UDN>" , 0); pf(pContextIn, _UPnP_GetUDN(ac, sizeof(ac)) , 0); pf(pContextIn, "</UDN>\r\n" , 0); pf(pContextIn, "<serviceList>\r\n" "<service>\r\n" "<serviceType>urn:schemas-upnp-org:service:Dummy:1</service- Type>\r\n" "<serviceId>urn:upnp-org:serviceId:Dummy</serviceId>\r\n" "<SCPDURL>/dummy.xml</SCPDURL>\r\n" "<controlURL>/</controlURL>\r\n" "<eventSubURL></eventSubURL>\r\n" "</service>\r\n" "</service, 0); List>\r\n" pf(pContextIn, URL>" pf(pContextIn, "<presentation, 0); _UPnP_GetPresentationURL(ac, sizeof(ac)) , 0); pf(pContextIn, URL>\r\n" pf(pContextIn, "</presentation, 0); "</device>\r\n" "</root>" , 0); } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 273 The callbacks for providing a virtual file using a VFile hook allow providing dynamically created content for every file requested from the web server as soon as possible. A file served from a VFile hook will not be processed further by the web server code. /* Excerpt from OS_IP_Webserver_UPnP.c */ /********************************************************************* * * Static code * ********************************************************************** */ /********************************************************************* * * _UPnP_CheckVFile * * Function description * Check if we have content that we can deliver for the requested * file using the VFile hook system. * * Parameters * sFileName - Name of the file that is requested * pIndex - Pointer to a variable that has to be filled with * the index of the entry found in case of using a * filename<=>content list. * Alternative all comparisons can be done using the * filename. In this case the index is meaningless * and does not need to be returned by this routine. * * Return value * 0 - We do not have content to send for this filename, * fall back to the typical methods for retrieving * a file from the web server. * 1 - We have content that can be sent using the VFile * hook system. */ static int _UPnP_CheckVFile(const char * sFileName, unsigned * pIndex) { unsigned i; // // Generated VFiles // if (strcmp(sFileName, "/upnp.xml") == 0) { return 1; } // // Static VFiles // for (i = 0; i < SEGGER_COUNTOF(_VFileList); i++) { if (strcmp(sFileName, _VFileList[i].sFileName) == 0) { *pIndex = i; return 1; } } return 0; } /********************************************************************* * * _UPnP_SendVFile * * Function description * Send the content for the requested file using the callback provided. * * Parameters * pContextIn - Send context of the connection processed for UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 274 CHAPTER 13 UPnP (Add-on) * forwarding it to the callback used for output. * Index - Index of the entry of a filename<=>content list * if used. Alternative all comparisons can be done * using the filename. In this case the index is * meaningless. If using a filename<=>content list * this is faster than searching again. * sFileName - Name of the file that is requested. In case of * working with the Index this is meaningless. * pf - Function pointer to the callback that has to be * for sending the content of the VFile. * pContextOut - Out context of the connection processed. * pData - Pointer to the data that will be sent * NumBytes - Number of bytes to send from pData. If NumBytes * is passed as 0 the send function will run a strlen() * on pData expecting a string. */ static void _UPnP_SendVFile(void * pContextIn, unsigned Index, const char * sFileName, void (*pf) (void * pContextOut, const char * pData, unsigned NumBytes)) { (void)sFileName; // // Generated VFiles // if (strcmp(sFileName, "/upnp.xml") == 0) { _UPnP_GenerateSend_upnp_xml(pContextIn, pf); return; } // // Static VFiles // pf(pContextIn, _VFileList[Index].pData, _VFileList[Index].NumBytes); } static WEBS_VFILE_APPLICATION _UPnP_VFileAPI = { _UPnP_CheckVFile, _UPnP_SendVFile }; All that is needed to be added to your application in order to provide the necessary XML files through embOS/IP Web server and starting UPnP advertising are the following lines: /* Excerpt from OS_IP_Webserver_UPnP.c */ // // Activate UPnP with VFile hook for needed XML files // IP_WEBS_AddVFileHook(&_UPnP_VFileHook, &_UPnP_VFileAPI); IP_UPNP_Activate(INTERFACE, NULL); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 275 13.5 API functions Function IP_UPNP_Activate() Description Activates UPnP advertisement of the target in the network. Table 13.1: embOS/IP UPnP API function overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 276 CHAPTER 13 UPnP (Add-on) 13.5.1 IP_UPNP_Activate() Description Activates the UPnP server. Prototype void IP_UPNP_Activate( unsigned IFace, const char * acUDN ); Parameter Parameter IFace acUDN Description [IN] Zero-based index of available network interfaces. [IN] String containing a unique descriptor name. (Optional, can be NULL.) Table 13.2: IP_UPNP_Activate() parameter list Additional infromation If acUDN is NULL the unique descriptor name will be generated from the HW addr. of the interface. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 277 13.6 UPnP resource usage The ROM usage depends on the compiler options, the compiler version and the used CPU. The memory requirements of the UPnP modules presented in the tables below have been measured on an ARM7 and a Cortex-M3 system. Details about the further configuration can be found in the sections of the specific example. The pure size of the UPnP add-on has been measured as the size of the services provided may vary. 13.6.1 ROM usage on an ARM7 system The following resource usage has been measured on an ARM7 system using IAR Embedded Workbench V6.30.6, Thumb mode, no interwork, size optimization. Addon embOS/IP UPnP ROM approximately 2.2Kbyte Table 13.3: UPnP ROM usage ARM7 13.6.2 ROM usage on a Cortex-M3 system The following resource usage has been measured on a Cortex-M3 system using IAR Embedded Workbench V6.30.6, size optimization. Addon embOS/IP UPnP ROM approximately 2.0Kbyte Table 13.4: UPnP ROM usage Cortex-M3 13.6.3 RAM usage Addon embOS/IP UPnP RAM approximately 170 bytes Table 13.5: UPnP RAM usage UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 278 UM07001 User & Reference Guide for embOS/IP CHAPTER 13 UPnP (Add-on) (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 279 Chapter 14 VLAN The embOS/IP implementation of VLAN which stand for Virtual LAN allows seperating your network into multiple networks without the need to seperate it physically. This chapter will show you how easily VLAN access can be setup on your target. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 280 CHAPTER 14 VLAN 14.1 embOS/IP VLAN The embOS/IP VLAN implementation allows a fast and easy implement of VLAN on your target. embOS/IP VLAN support supports a basic VLAN tag specifying only a VLAN ID. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 281 14.2 Feature list * * * Low memory footprint. Easy to implement. Software based solution without the need for a driver to support VLAN tags. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 282 CHAPTER 14 VLAN 14.3 VLAN backgrounds VLAN technology can be used to seperate multiple devices operating on the same physical network into completely seperated networks without seeing each other. A typical usage would be to have 2 departments seperated from each other but using the same infrastructure such as a shared switch or router. Only devices using the same VLAN ID will be able to see each other. For this to happen 4 bytes are added in front of the packet type field in the Ethernet frame pushing the original packet type field back by 4 bytes. The Ethernet frame will still be of a maximum length 1518 bytes including CRC what means that instead of a maximum of 1500 bytes that can be transferred the amount of bytes that can be transferred per Ethernet frame will shrink to 1496 bytes per packet. VLAN tagged packets are typically forwarded by any switch as they are as the type field has been simply replaced and in most cases only the destination MAC, source MAC and packet type is checked. In this case the packet is simply of an unknown protocol and will be forwarded by the switch. The picture below shows the structure of an Ethernet frame once without using a VLAN tag and once with using a VLAN tag being assigned to VLAN ID #2. Ethernet frame of max. 1518 bytes Dest MAC Src MAC Packet Type Packet Data 00:23:C7:FF:FF:FF 00:23:C7:FF:EE:EE IP Packet 0x0800 Max. 1500 bytes data + 4 bytes CRC Dest MAC Src MAC VLAN TAG TPI 00:23:C7:FF:FF:FF 00:23:C7:FF:EE:EE 0x8100 Packet Type Packet Data IP Packet 0x0800 Max. 1496 bytes data + 4 bytes CRC 16 bit TCI (12 bit VLAN ID) VLAN ID #2 0x0002 Ethernet frame of max. 1518 bytes UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 283 14.4 API functions Function IP_VLAN_AddInterface() Description Activates UPnP advertisement of the target in the network. Table 14.1: embOS/IP VLAN API function overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 284 CHAPTER 14 VLAN 14.4.1 IP_VLAN_AddInterface() Description Adds a VLAN interface. Prototype int IP_VLAN_AddInterface( unsigned HWIFace, U16 VLANId ); Parameter Parameter HWIFace VLANId Description [IN] Zero-based index of available network interfaces to be used as physical interface for the VLAN pseudo interface. [IN] 12 bit VLAN ID. Table 14.2: IP_VLAN_AddInterface() parameter list Return value Zero-based index of the added VALN interface. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 285 14.5 VLAN resource usage The ROM usage depends on the compiler options, the compiler version and the used CPU. The memory requirements of the VLAN modules presented in the tables below have been measured on an ARM7 and a Cortex-M3 system. Details about the further configuration can be found in the sections of the specific example. 14.5.1 ROM usage on an ARM7 system The following resource usage has been measured on an ARM7 system using IAR Embedded Workbench V6.30.6, Thumb mode, no interwork, size optimization. Addon embOS/IP VLAN ROM approximately 1.2Kbyte Table 14.3: VLAN ROM usage ARM7 14.5.2 ROM usage on a Cortex-M3 system The following resource usage has been measured on a Cortex-M3 system using IAR Embedded Workbench V6.30.6, size optimization. Addon embOS/IP VLAN ROM approximately 1.0Kbyte Table 14.4: VLAN ROM usage Cortex-M3 14.5.3 RAM usage Addon embOS/IP VLAN RAM approximately 16 bytes Table 14.5: VLAN RAM usage UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 286 UM07001 User & Reference Guide for embOS/IP CHAPTER 14 VLAN (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 287 Chapter 15 Network interface drivers embOS/IP has been designed to cooperate with any kind of hardware. To use specific hardware with embOS/IP, a so-called network interface driver for that hardware is required. The network interface driver consists of basic functions for accessing the hardware and a global table that holds pointers to these functions. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 288 CHAPTER 15 Network interface drivers 15.1 General information To use embOS/IP, a network interface driver matching the target hardware is required. The code size of a network interface driver depends on the hardware and is typically between 1 and 3 Kbytes. The driver handles both the MAC (media access control) unit as well as the PHY (Physical interface). We recommend using drivers written and tested by SEGGER. However, it is possible to write your own driver. This is explained in section Writing your own driver on page 318. The driver interface has been designed to allow support of internal and external Ethernet controllers (EMACs). It also allows to take full advantage of hardware features such as MAC address filtering and checksum computation in hardware. 15.1.1 MAC address filtering The stack passes a list of MAC addresses to the driver. The driver is responsible for making sure that all packets from all MAC addresses specified are passed to the stack. It can do so with "precise filtering" if the hardware has sufficient filters for the given number of MAC addresses. If more MAC addresses are passed to the driver than hardware filters are available, the driver can use a hash filter if available in hardware or switch to promiscuous mode. This is a very flexible solution which allows making best use of the hardware filtering capabilities on all known Ethernet controllers. It also allows simple implementations to simply switch to promiscuous mode. 15.1.2 Checksum computation in hardware When the interface is initialized, the stack queries the capabilities of the driver. If the hardware can compute IP, TCP, UDP, ICMP checksums, it can indicates this to the stack. In this case, the stack does not compute these checksums, improving throughput and reducing CPU load. 15.1.3 Ethernet CRC computation Every Ethernet packet includes a 32-bit trailing CRC. In most cases, the Ethernet controller is capable of computing the CRC. The drivers take advantage of this. The CRC is computed in the driver only if the hardware does not support CRC computation. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 289 15.2 Available network interface drivers Network interface drivers are optional components to embOS/IP. The following network interface drivers are available: Driver (Device) ATMEL AT91CAP9 ATMEL AT91RM9200 ATMEL AT91SAM7X ATMEL AT91SAM9260 ATMEL AT91SAM9263 ATMEL AT91SAMG20 ATMEL AT91SAMG45 ATMEL AT91SAM9XE ATMEL AVR32UC DAVICOM DM9000 FREESCALE ColdFire MCF5223x FREESCALE ColdFire MCF5329 NIOSII IFI GMACII EMAC NIOSII MaCo-Engineering EMAC NIOSII More than IP A2A bridge NXP LPC17xx NXP LPC2378 / LPC2478 NXP LPC32xx RENESAS H8S2472 RENESAS RX62N RENESAS SH7670 RENESAS (NEC) V850JGH3 SMSC LAN9115 / LAN9215 SMSC LAN9118 SMSC LAN91C111 ST STM32F107 (Connectivity Line) ST STM32F207 ST STR912 TI (LUMINARY) LM3S6965 TI (LUMINARY) LM3S9B90 Identifier IP_Driver_CAP9 IP_Driver_AT91RM9200 IP_Driver_SAM7X IP_Driver_SAM9260 IP_Driver_SAM9263 IP_Driver_SAM9G20 IP_Driver_SAMG45 IP_Driver_SAM9XE IP_Driver_AVR32UC IP_Driver_DM9000 IP_Driver_MCF5223x IP_Driver_MCF5329 IP_Driver_GMACII IP_Driver_NIOSII_MaCo IP_Driver_NIOSII_More10IP_A2A IP_Driver_LPC17xx IP_Driver_LPC24xx IP_Driver_LPC32xx IP_Driver_H8S2472 IP_Driver_RX62N IP_Driver_SH7670 IP_Driver_V850JGH3 IP_Driver_LAN9115 IP_Driver_LAN9118 IP_Driver_LAN91C111 IP_Driver_STM32F107 IP_Driver_STM32F207 IP_Driver_STR912 IP_Driver_LM3S6965 IP_Driver_LM3S9B90 Table 15.1: List of default network interface driver labels To add a driver to embOS/IP, IP_AddEtherInterface() should be called with the proper identifier before the TCP/IP stack starts any transmission. Refer to IP_AddEtherInterface() on page 49 for detailed information. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 290 CHAPTER 15 Network interface drivers 15.2.1 ATMEL AT91CAP9 Atmel's CAPTM is a microcontroller-based system-on-chip platform with a Metal Programmable (MP) Block that allows the designer to add custom logic. 15.2.1.1 Supported hardware The network interface driver for the AT91CAP9 can be used with every ATMEL AT91CAP9 target board. The driver has been tested on the following eval boards: Tested evaluation boards ATMEL CAP-DK Table 15.2: List of tested eval boards 15.2.1.2 Configuring the driver Adding the driver to embOS/IP To add the driver, use IP_AddEtherInterface() with the driver identifier IP_Driver_CAP9. This function must be called from IP_X_Config(). Refer to IP_AddEtherInterface() on page 49 and IP_X_Configure() on page 326 for more information. Example void IP_X_Config(void) { int mtu; IP_AssignMemory(_aPool, sizeof(_aPool)); IP_AddEtherInterface(&IP_Driver_CAP9); IP_SetHWAddr("\x00\x22\xC7\xFF\xFF\xFF"); // // // // Assigning memory Add Ethernet driver MAC addr: Needs to be unique for production units // // Add protocols to the stack // IP_TCP_Add(); IP_UDP_Add(); IP_ICMP_Add(); // // Set supported duplex modes // 10Mbit half duplex, 10Mbit full duplex, 100Mbit half duplex // and 100Mbit full duplex are supported. // IP_SetSupportedDuplexModes(0, IP_PHY_MODE_10_HALF | IP_PHY_MODE_10_FULL | IP_PHY_MODE_100_HALF | IP_PHY_MODE_100_FULL ); IP_NI_ConfigPHYMode (0, 1); // Use RMII mode // // Run-time configure buffers. // The default setup will do for most cases. // mtu = 1500; // 576 is minimum acc. to RFC, // 1500 is max. for Ethernet IP_SetMTU(0, mtu); // Maximum Transmission Unit is // 1500 for ethernet by default IP_AddBuffers(12, 256); // Small buffers. IP_AddBuffers(8, mtu + 40 + 16); // Big buffers. Size should be // mtu + 16 byte for ethernet header // (2 bytes type, 2*6 bytes MAC, // 2 bytes padding) IP_ConfTCPSpace(8 * (mtu-40), 8 * (mtu-40)); // // Use DHCP client or define IP address, subnet mask, // gateway address and DNS server according to the // requirements of your application. // IP_DHCPC_Activate(0, "TARGET", NULL, NULL); IP_SetWarnFilter(0xFFFFFFFF); // 0xFFFFFFFF: Do not filter: // Output all warnings. IP_SetLogFilter(IP_MTYPE_INIT | IP_MTYPE_LINK_CHANGE | IP_MTYPE_DHCP); } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 291 UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 292 CHAPTER 15 Network interface drivers 15.2.1.3 Driver specific configuration functions Function Description Sets the number of Rx buffers. IP_NI_CAP9_ConfigNumRxBuffers() Table 15.3: embOS/IP CAP9 driver specific function overview 15.2.1.3.1 IP_NI_CAP9_ConfigNumRxBuffers Description Sets the number of Rx buffers of the driver. This function has to be called in the configuration phase. Prototype void IP_NI_CAP9_ConfigNumRxBuffers( U16 NumRxBuffers ); Parameter Parameter NumRxBuffers Description [IN] The number of Rx buffers. Table 15.4: IP_NI_CAP9_ConfigNumRxBuffers() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 293 15.2.1.4 Required BSP functions Function Description Initializes the network interface. BSP_ETH_Init() Table 15.5: embOS/IP driver specific function overview 15.2.1.4.1 BSP_ETH_Init() Description This function is called from the network interface driver. It initializes the network interface. This function should be used to enable the ports which are connected to the network hardware. It is called from the driver during the initialization process. Prototype void BSP_ETH_Init( unsigned Unit ); Parameter Parameter Unit Description [IN] Zero-based index of available network interfaces. Table 15.6: BSP_ETH_Init() parameter list Example /* Excerpt of BSP.c for the ATMEL AT91CAP9 CAP-DK */ /********************************************************************* * * BSP_ETH_Init() * * Function description * This function is called from the network interface driver. * It initializes the network interface. This function should be used * to enable the ports which are connected to the network hardware. * It is called from the driver during the initialization process. */ void BSP_ETH_Init(unsigned Unit) { unsigned PinsA; unsigned v; _PMC_PCER _EMAC_PORT_PPUDR = (1 << _ID_EMAC_PORT); = (1 << _EMAC_PORT_RXDV_BIT); // Enable clock for PIO // Disable RXDV pullup, // enter PHY normal mode // // Init PIO and perform a RESET of PHY since PHY // v = 0 | (1 << _EMAC_PORT_RXDV_BIT) ; _PIOB_PER = v; _PIOB_OER = v; _PIOB_CODR = 0 | (1 << _EMAC_PORT_RXDV_BIT) ; _PIOB_SODR = 0 | (1 << 0) // Isolate ; // // Perform hardware reset using RESET pin of MCU // AT91C_RSTC_RMR = 0xA5000000 | AT91C_RSTC_ERSTL & (1 << 8); AT91C_RSTC_RCR = 0xA5000000 | AT91C_RSTC_EXTRST; while ((AT91C_RSTC_RSR & AT91C_RSTC_NRSTL) == 0); // Wait until RESET timer has // expired (just a few ms) // // Init PIO Pins: EMAC is connected to specific lines of PIO // PinsA = (1uL << 11) // ETH_MDINTR | (1uL << 21) // ETXCK | (1uL << 22) // ERXDV | (1uL << 23) // ETX0 UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 294 CHAPTER 15 _EMAC_PORT_ASR _EMAC_PORT_PDR = = | (1uL | (1uL | (1uL | (1uL | (1uL | (1uL | (1uL ; PinsA; PinsA; << << << << << << << 24) 25) 26) 27) 28) 29) 30) // // // // // // // Network interface drivers ETX1 ERX0 ERX1 ERXER ETXEN EMDC EMDIO // Select peripheral A use // Disable GPIO mode, // select peripheral function } 15.2.1.5 Additional information None. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 295 15.2.2 ATMEL AT91RM9200 The ATMEL AT919200 is based on the ARM920T processor. Its peripheral set includes USB Full Speed Host and Device Ports, 10/100 Base T Ethernet MAC, Multimedia Card Interface (MCI), three Synchronous Serial Controllers (SSC), four USARTs, Master/ Slave Serial Peripheral Interface (SPI), Timer Counters (TC) and Two Wire Interface (TWI), four 32-bit Parallel I/O Controllers and peripheral DMA channels. 15.2.2.1 Supported hardware The network interface driver for the AT91RM9200 can be used with every ATMEL AT91RM9200 target board. The driver has been tested on the following eval board(s): Tested evaluation boards ATMEL AT91RM9200-EK Table 15.7: List of tested eval boards 15.2.2.2 Configuring the driver Adding the driver to embOS/IP To add the driver, use IP_AddEtherInterface() with the driver identifier IP_Driver_RM9200. This function must be called from IP_X_Config(). Refer to IP_AddEtherInterface() on page 49 and IP_X_Configure() on page 326 for more information. Example void IP_X_Config(void) { int mtu; IP_AssignMemory(_aPool, sizeof(_aPool)); // Assigning memory IP_AddEtherInterface(&IP_Driver_AT91RM9200); // Add Ethernet driver IP_SetHWAddr("\x00\x22\xC7\xFF\xFF\xFF"); // MAC addr: Needs to be unique // for production units // // Add protocols to the stack // IP_TCP_Add(); IP_UDP_Add(); IP_ICMP_Add(); // // Set supported duplex modes // 10Mbit half duplex, 10Mbit full duplex, 100Mbit half duplex // and 100Mbit full duplex are supported. // IP_SetSupportedDuplexModes(0, IP_PHY_MODE_10_HALF | IP_PHY_MODE_10_FULL | IP_PHY_MODE_100_HALF | IP_PHY_MODE_100_FULL ); IP_NI_ConfigPHYMode (0, 1); // Use RMII mode // // Run-time configure buffers. // The default setup will do for most cases. // mtu = 1500; // 576 is minimum acc. to RFC, // 1500 is max. for Ethernet IP_SetMTU(0, mtu); // Maximum Transmission Unit is // 1500 for ethernet by default IP_AddBuffers(12, 256); // Small buffers. IP_AddBuffers(8, mtu + 40 + 16); // Big buffers. Size should be // mtu + 16 byte for ethernet header // (2 bytes type, 2*6 bytes MAC, // 2 bytes padding) IP_ConfTCPSpace(8 * (mtu-40), 8 * (mtu-40)); // // Use DHCP client or define IP address, subnet mask, // gateway address and DNS server according to the // requirements of your application. // IP_DHCPC_Activate(0, "TARGET", NULL, NULL); IP_SetWarnFilter(0xFFFFFFFF); // 0xFFFFFFFF: Do not filter: // Output all warnings. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 296 CHAPTER 15 Network interface drivers IP_SetLogFilter(IP_MTYPE_INIT | IP_MTYPE_LINK_CHANGE | IP_MTYPE_DHCP); } 15.2.2.3 Driver specific configuration functions Function Description IP_NI_AT91RM9200_ConfigNumRxBuffers() Sets the number of Rx buffers. Table 15.8: embOS/IP RM9200 driver specific function overview 15.2.2.3.1 IP_NI_AT91RM9200_ConfigNumRxBuffers Description Sets the number of Rx buffers of the driver. This function has to be called in the configuration phase. Prototype void IP_NI_AT91RM9200_ConfigNumRxBuffers( U16 NumRxBuffers ); Parameter Parameter NumRxBuffers Description [IN] The number of Rx buffers. Table 15.9: IP_NI_RM9200_ConfigNumRxBuffers() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 297 15.2.2.4 Required BSP functions Function Description Initializes the network interface. BSP_ETH_Init() Table 15.10: embOS/IP driver specific function overview 15.2.2.4.1 BSP_ETH_Init() Description This function is called from the network interface driver. It initializes the network interface. This function should be used to enable the ports which are connected to the network hardware. It is called from the driver during the initialization process. Prototype void BSP_ETH_Init( unsigned Unit ); Parameter Parameter Description [IN] Zero-based index of available network interfaces. Unit Table 15.11: BSP_ETH_Init() parameter list Example /* Excerpt of BSP.c for the ATMEL AT91RM9200-EK */ #define #define #define #define #define #define #define #define #define #define #define #define #define #define #define #define _PIOA_BASE_ADDR _PMC_BASE_ADDR _PIO_PUDR_OFF _PIO_PUER_OFF _PIO_ASR_OFF _PIO_BSR_OFF _PMC _PMC_PCER _PMC_PCDR _PIOA_ASR _PIOA_BSR _PIOA_PUDR _PIOA_PUER _PIOA_ID _PIOB_ID _EMAC_ID (0xFFFFF400UL) (0xFFFFFC00UL) (0x60) (0x64) (0x70) (0x74) (*(volatile unsigned int*)(_PMC_BASE_ADDR)) (*(volatile unsigned int*)(_PMC_BASE_ADDR + 0x10)) (*(volatile unsigned int*)(_PMC_BASE_ADDR + 0x14)) (*(volatile unsigned int*)(_PIOA_BASE_ADDR + _PIO_ASR_OFF)) (*(volatile unsigned int*)(_PIOA_BASE_ADDR + _PIO_BSR_OFF)) (*(volatile unsigned int*)(_PIOA_BASE_ADDR + _PIO_PUDR_OFF)) (*(volatile unsigned int*)(_PIOA_BASE_ADDR + _PIO_PUER_OFF)) (2) // Parallel IO Controller A (3) // Parallel IO Controller B (24) // EMAC /********************************************************************* * * BSP_ETH_Init() */ void BSP_ETH_Init(unsigned Unit) { unsigned int Pins; // // Initialize peripheral clock // _PMC_PCER = (1 << _EMAC_ID); _PMC_PCER = (1 << _PIOA_ID); _PIOA_PUDR = (1 << 11); _PIOA_PUER = (1 << #ifdef RMII Pins = ((unsigned | ((unsigned | ((unsigned | ((unsigned | ((unsigned | ((unsigned | ((unsigned | ((unsigned | ((unsigned | ((unsigned ; #else 16); int) int) int) int) int) int) int) int) int) int) (1 (1 (1 (1 (1 (1 (1 (1 (1 (1 << << << << << << << << << << UM07001 User & Reference Guide for embOS/IP // // // // // Ensure the clock for EMAC is enabled Ensure the clock for PIOA is enabled Disable RXDV pullup, enter PHY normal mode Note: the PHY has an internal pull-down Enable Pull-Up on EMDIO pin 7)) 8)) 9)) 10)) 11)) 12)) 13)) 14)) 15)) 16)) (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 298 CHAPTER 15 #error "MII-mode #endif _PIOA_ASR = _PIOA_BSR = _PIOA_PDR = } Network interface drivers not supported by AT91RM9200-EK" Pins; 0; Pins; // Select peripheral A use of the associated pins // Select peripheral B, no peripheral B pins used // Set peripheral control of the associated pins 15.2.2.5 Additional information None. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 299 15.2.3 ATMEL AT91SAM7X The ATMEL AT91SAM7X's are flash microcontrollers with integrated Ethernet, USB and CAN interfaces, based on the 32-bit ARM7TDMI RISC processor. 15.2.3.1 Supported hardware The network interface driver for the AT91SAM7X can be used with every ATMEL AT91SAM7X target board. The driver has been tested on the following eval boards: Tested evaluation boards ATMEL AT91SAM7X-EK Olimex SAM7-EX256 Table 15.12: List of tested eval boards 15.2.3.2 Configuring the driver Adding the driver to embOS/IP To add the driver, use IP_AddEtherInterface() with the driver identifier IP_Driver_SAM7X. This function has to be called from IP_X_Config(). Refer to IP_AddEtherInterface() on page 49 and IP_X_Configure() on page 326 for more information. Example void IP_X_Config(void) { IP_AssignMemory(_aPool, sizeof(_aPool)); IP_AddEtherInterface(&IP_Driver_SAM7X); IP_SetHWAddr("\x00\x22\xC7\xFF\xFF\xFF"); // // // // Assigning memory Add Ethernet driver MAC addr: Needs to be unique for production units // // Add protocols to the stack // IP_TCP_Add(); IP_UDP_Add(); IP_ICMP_Add(); // // Set supported duplex modes // 10Mbit half duplex, 10Mbit full duplex, 100Mbit half duplex // and 100Mbit full duplex are supported. // IP_SetSupportedDuplexModes(0, IP_PHY_MODE_10_HALF | IP_PHY_MODE_10_FULL | IP_PHY_MODE_100_HALF | IP_PHY_MODE_100_FULL ); // // Run-time configure buffers. // The default setup will do for most cases. // mtu = 1500; // 576 is minimum acc. to RFC, // 1500 is max. for Ethernet IP_SetMTU(0, mtu); // Maximum Transmission Unit is // 1500 for ethernet by default IP_AddBuffers(12, 256); // Small buffers. IP_AddBuffers(6, mtu + 40 + 16); // Big buffers. Size should be // mtu + 16 byte for ethernet header // (2 bytes type, 2*6 bytes MAC, // 2 bytes padding) IP_ConfTCPSpace(3 * (mtu-40), 3 * (mtu-40)); IP_DHCPC_Activate(0, "TARGET", NULL, NULL); IP_SetWarnFilter(0xFFFFFFFF); // 0xFFFFFFFF: Do not filter: // Output all warnings. IP_SetLogFilter(IP_MTYPE_INIT | IP_MTYPE_LINK_CHANGE | IP_MTYPE_DHCP); } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 300 CHAPTER 15 Network interface drivers 15.2.3.3 Driver specific configuration functions Function Description Sets the number of Rx buffers. IP_NI_SAM7X_ConfigNumRxBuffers() Table 15.13: embOS/IP SAM7X driver specific function overview 15.2.3.3.1 IP_NI_SAM7X_ConfigNumRxBuffers() Description Sets the number of Rx buffers of the driver. This function has to be called in the configuration phase. Prototype void IP_NI_SAM7X_ConfigNumRxBuffers( U16 NumRxBuffers ); Parameter Parameter NumRxBuffers Description [IN] The number of Rx buffers. Table 15.14: IP_NI_SAM7X_ConfigNumRxBuffers() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 301 15.2.3.4 Required BSP functions Function Description Initializes the network interface. BSP_ETH_Init() Table 15.15: embOS/IP driver specific function overview 15.2.3.4.1 BSP_ETH_Init() Description This function is called from the network interface driver. It initializes the network interface. This function should be used to enable the ports which are connected to the network hardware. It is called from the driver during the initialization process. Prototype void BSP_ETH_Init( unsigned Unit ); Parameter Parameter Description [IN] Zero-based index of available network interfaces. Unit Table 15.16: BSP_ETH_Init() parameter list Example /* Excerpt from implementation for ATMEL AT91SAM7X-EK */ #define #define #define #define #define #define #define #define #define #define #define #define #define #define AT91C_PMC_PCER (*(volatile AT91C_PIOB_PPUDR (*(volatile AT91C_PIOB_PER (*(volatile AT91C_PIOB_OER (*(volatile AT91C_PIOB_CODR (*(volatile AT91C_PIOB_SODR (*(volatile AT91C_PIOB_ODR (*(volatile AT91C_PIOB_PDR (*(volatile AT91C_RSTC_RMR (*(volatile AT91C_PIOB_ASR (*(volatile AT91C_RSTC_RCR (*(volatile AT91C_RSTC_ERSTL AT91C_RSTC_EXTRST AT91C_RSTC_NRSTL unsigned*) unsigned*) unsigned*) unsigned*) unsigned*) unsigned*) unsigned*) unsigned*) unsigned*) unsigned*) unsigned*) 0xFFFFFC10) 0xFFFFF660) 0xFFFFF600) 0xFFFFF610) 0xFFFFF634) 0xFFFFF630) 0xFFFFF614) 0xFFFFF604) 0xFFFFFD08) 0xFFFFF670) 0xFFFFFD00) (0xF << 8) (0x1 << 3) (1UL << 16) void BSP_ETH_Init(unsigned Unit) { unsigned v; AT91C_PMC_PCER AT91C_PIOB_PPUDR = (1 << _PIOB_ID); // Enable clock for PIOB = 1UL << 15; // Disable RXDV pullup, // enter PHY normal mode = 1UL << 16; AT91C_PIOB_PPUDR // // Init PIO and perform a RESET of PHY // v = 0 | (1 << | (1 << | (1 << | (1 << ; AT91C_PIOB_PER AT91C_PIOB_OER AT91C_PIOB_CODR UM07001 User & Reference Guide for embOS/IP = = = | | since PHY 0) 15) 16) 18) v; // Entire lower 19 bits enabled v; 0 (1 << 7) // 0: node mode, 1: repeater mode (1 << 15) // 0: Normal mode, 1: test mode (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 302 CHAPTER 15 | (1 << 16) | (1 << 18) ; AT91C_PIOB_SODR = 0 | (1 << 0) ; Network interface drivers // 0: MII // 0: Power down // Isolate // // Perform hardware reset using RESET pin of MCU // AT91C_RSTC_RMR = 0xA5000000 | AT91C_RSTC_ERSTL & (1 << 8); AT91C_RSTC_RCR = 0xA5000000 | AT91C_RSTC_EXTRST; while ((AT91C_RSTC_RSR & AT91C_RSTC_NRSTL) == 0); // Wait until RESET timer has // expired // // Switch to peripheral functions // v = 0x3FFFF; // Lower 18 bits are used for the peripheral AT91C_PIOB_ODR = v; // Entire lower 18 bits disabled AT91C_PIOB_ASR = v; // Select peripheral A use AT91C_PIOB_PDR = v; // Disable GPIO mode, select peripheral } 15.2.3.5 Additional information None. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 303 15.2.4 ATMEL AT91SAM9260 The ATMEL AT91SAM9260 is based on the ARM926EJ-STM processor. Its peripheral set includes USB Full Speed Host and Device interfaces, a 10/100 Base T Ethernet MAC, Image Sensor Interface, Multimedia Card Interface (MCI), Synchronous Serial Controllers (SSC), USARTs, Master/Slave Serial Peripheral Interfaces (SPI), a threechannel 16-bit Timer Counter (TC), a Two Wire Interface (TWI) and four-channel 10bit ADC. 15.2.4.1 Supported hardware The network interface driver for the AT91SAM9260 can be used with every ATMEL AT91SAM9260 target board. The driver has been tested on the following eval boards: Tested evaluation boards ATMEL AT91SAM9260 Table 15.17: List of tested eval boards 15.2.4.2 Configuring the driver Adding the driver to embOS/IP To add the driver, use IP_AddEtherInterface() with the driver identifier IP_Driver_SAM9260. This function must be called from IP_X_Config(). Refer to IP_AddEtherInterface() on page 49 and IP_X_Configure() on page 326 for more information. Example void IP_X_Config(void) { IP_AssignMemory(_aPool, sizeof(_aPool)); IP_AddEtherInterface(&IP_Driver_SAM9260); IP_SetHWAddr("\x00\x22\xC7\xFF\xFF\xFF"); // // // // Assigning memory Add Ethernet driver MAC addr: Needs to be unique for production units IP_DHCPC_Activate(0, "TARGET", NULL, NULL); // // Add protocols to the stack // IP_TCP_Add(); IP_UDP_Add(); IP_ICMP_Add(); // // Run-time configure buffers. // The default setup will do for most cases. // IP_AddBuffers(50, 256); // IP_AddBuffers(50, 1536); // // IP_ConfTCPSpace(16 * 1024, 16 * 1024); IP_SetWarnFilter(0xFFFFFFFF); // // IP_SetLogFilter(IP_MTYPE_INIT | IP_MTYPE_LINK_CHANGE | IP_MTYPE_DHCP); Small buffers. Big buffers. Size should be 1536 to allow a full ether packet to fit. 0xFFFFFFFF: Do not filter: Output all warnings. } 15.2.4.3 Driver specific configuration functions Function Description Sets the number of Rx buffers. IP_NI_SAM9260_ConfigNumRxBuffers() Table 15.18: embOS/IP SAM9260 driver specific function overview 15.2.4.3.1 IP_NI_SAM9260_ConfigNumRxBuffers Description Sets the number of Rx buffers of the driver. This function has to be called in the configuration phase. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 304 CHAPTER 15 Network interface drivers Prototype void IP_NI_SAM9260_ConfigNumRxBuffers( U16 NumRxBuffers ); Parameter Parameter NumRxBuffers Description [IN] The number of Rx buffers. Table 15.19: IP_NI_SAM9260_ConfigNumRxBuffers() parameter list 15.2.4.4 Required BSP functions Function Description Initializes the network interface. BSP_ETH_Init() Table 15.20: embOS/IP driver specific function overview 15.2.4.4.1 BSP_ETH_Init() Description This function is called from the network interface driver. It initializes the network interface. This function should be used to enable the ports which are connected to the network hardware. It is called from the driver during the initialization process. Prototype void BSP_ETH_Init( unsigned Unit ); Parameter Parameter Unit Description [IN] Zero-based index of available network interfaces. Table 15.21: BSP_ETH_Init() parameter list Example /********************************************************************* * * BSP_ETH_Init() * * Function description * This function is called from the network interface driver. * It initializes the network interface. This function should be used * to enable the ports which are connected to the network hardware. * It is called from the driver during the initialization process. * * Note: * (1) If your MAC is connected to the PHY via Media Independent * Interface (MII) change the macro _USE_RMII and call * IP_NI_ConfigPHYMode() from within IP_X_Config() * to change the default of driver. * */ void BSP_ETH_Init(unsigned Unit) { unsigned PinsA; unsigned PinsB; PMC_PCER = (1 << ID_EMAC_PORT); // Enable clock for PIO EMAC_PORT_PPUDR = (1 << EMAC_PORT_RXDV_BIT); // Disable RXDV pullup, // enter PHY normal mode #if _USE_RMII EMAC_PORT_PPUER = (1 << EMAC_PORT_RMII_BIT); // Enable Pullup => Switch to RMII. #else EMAC_PORT_PPUDR = (1 << EMAC_PORT_RMII_BIT); // Disable Pullup => Switch to MII. #endif // // Power up PHY, may not be required, if set as hardwired option on target // #ifdef EMAC_PORT_PWR_PHY_BIT EMAC_PORT_PER = (1 << EMAC_PORT_PWR_PHY_BIT); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 305 EMAC_PORT_OER = (1 << EMAC_PORT_PWR_PHY_BIT); EMAC_PORT_CODR = (1 << EMAC_PORT_PWR_PHY_BIT); #endif // // Init PIO Pins: EMAC is connected to specific lines of PIO // PinsA = (1uL << 12) | (1uL << 13) | (1uL << 14) | (1uL << 15) | (1uL << 16) | (1uL << 17) | (1uL << 18) | (1uL << 19) | (1uL << 20) | (1uL << 21) ; PinsB = (1uL << 10) | (1uL << 11) | (1uL << 22) | (1uL << 25) | (1uL << 26) | (1uL << 27) | (1uL << 28) | (1uL << 29) ; EMAC_PORT_ASR = PinsA; // Select peripheral A use EMAC_PORT_BSR = PinsB; // Select peripheral B use EMAC_PORT_PDR = PinsA | PinsB; // Disable GPIO mode, select peripheral function // // Initialize priority of BUS MATRIX. EMAC needs highest priority for SDRAM access // MATRIX_SCFG3 = 0x01160030; // Assign EMAC as default master, activate priority arbitration, increase cycles MATRIX_PRAS3 = 0x00320000; // Set Priority of EMAC to 3 (highest value) } 15.2.4.5 Additional information None. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 306 CHAPTER 15 Network interface drivers 15.2.5 DAVICOM DM9000/DM9000A The Davicom DM9000 is a fully integrated single chip Fast Ethernet MAC controller with a generic processor interface, a 10/100M PHY and SRAM. 15.2.5.1 Supported hardware The network interface driver for the Davicom DM9000 can be used with every target board which complies with the following: * * * Davicom DM9000 is presented DM 9000 is connected to the data/address bus; data bus is 16-bits wide INT pin connected to CPU in a way which allows generating interrupts The driver has been tested on the following eval boards: Tested evaluation boards ATMEL AT91SAM9261-EK Table 15.22: List of tested eval boards 15.2.5.2 Configuring the driver Adding the driver to embOS/IP To add the driver, use IP_AddEtherInterface() with the driver identifier IP_Driver_DM9000. This function must be called from within IP_X_Config(). Refer to IP_AddEtherInterface() on page 49 and IP_X_Configure() on page 326 for more information. Example void IP_X_Config(void) { IP_AssignMemory(_aPool, sizeof(_aPool)); // Assigning memory IP_AddEtherInterface(&IP_Driver_DM9000); // Add Ethernet driver IP_NI_DM9000_ConfigAddr(0, (void*) (0x30000000), (void*) (0x30000000 + 0x04)); IP_NI_ConfigPoll(0); // No ISR routine IP_SetHWAddr("\x00\x22\x33\x44\x55\x66"); // MAC addr: Needs to be unique IP_DHCPC_Activate(0, "TARGET", NULL, NULL); // // Add protocols to the stack // IP_TCP_Add(); IP_UDP_Add(); IP_ICMP_Add(); // // Run-time configure buffers. The default setup will do for most cases. // IP_AddBuffers(12, 256); // Small buffers. IP_AddBuffers(12, 1536); // Big buffers. Size should be 1536 to // allow a full ether packet to fit. IP_ConfTCPSpace(6 * 1024, 4 * 1024); IP_SetWarnFilter(0xFFFFFFFF); // 0xFFFFFFFF: Do not filter: // Output all warnings. IP_SetLogFilter(IP_MTYPE_INIT | IP_MTYPE_LINK_CHANGE | IP_MTYPE_DHCP ); } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 307 15.2.5.3 Driver-specific configuration functions Function Description Sets the base address for commands and data register. Interrupt service routine for the network interface. IP_NI_DM9000_ConfigAddr() IP_NI_DM9000_ISR_Handler() Table 15.23: embOS/IP DM9000 driver-specific function overview 15.2.5.3.1 IP_NI_DM9000_ConfigAddr() Description Sets the base address (for command) and data address. Prototype void IP_NI_DM9000_ConfigAddr( unsigned Unit, void * pBase, void * pValue ); Parameter Parameter Unit pBase pValue Description [IN] Zero-based index of available network interfaces. [IN] Pointer to the control register of the MAC. [IN] Pointer to the data register of the MAC. Table 15.24: IP_NI_DM9000_ConfigAddr() parameter list Additional information This function must be called from within IP_X_Config. Refer to IP_X_Configure() on page 326 for detailed information. 15.2.5.3.2 IP_NI_DM9000_ISR_Handler() Description This is the interrupt service routine for the network interface (EMAC). It handles all interrupts (Rx, Tx, Error). Prototype void IP_NI_DM9000_ISR_Handler( unsigned Unit ); Parameter Parameter Unit Description [IN] Zero-based index of available network interfaces. Table 15.25: IP_NI_DM9000_ISR_Handler() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 308 CHAPTER 15 Network interface drivers 15.2.5.4 Required BSP functions Function Description Initializes the network interface. BSP_ETH_Init() Table 15.26: embOS/IP driver specific function overview 15.2.5.4.1 BSP_ETH_Init() Description This function is called from the network interface driver. It initializes the network interface. This function should be used to enable the ports which are connected to the network hardware. It is called from the driver during the initialization process. Prototype void BSP_ETH_Init( unsigned Unit ); 15.2.5.5 Additinal information None. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 309 15.2.6 FREESCALE ColdFire MCF5329 15.2.6.1 Supported hardware The network interface driver for the ColdFire MCF5329 MCU can be used with every target board. The driver has been tested on the following eval boards: Tested evaluation boards LOGICPD ZOOM COLDFIRE SDK with MCF5329 Fire Engine Table 15.27: List of tested eval boards 15.2.6.2 Configuring the driver Adding the driver to embOS/IP To add the driver, use IP_AddEtherInterface() with the driver identifier IP_Driver_MCF5329. This function must be called from IP_X_Config(). Refer to IP_AddEtherInterface() on page 49 and IP_X_Configure() on page 326 for more information. Example /* Sample implementation taken from the configuration for the ColdFire MCF5329 */ #define ALLOC_SIZE U32 _aPool[ALLOC_SIZE / 4]; 0xA000 // Size of memory dedicated // to the stack in bytes // This is the memory area used // by the stack. /********************************************************************* * * IP_X_Config */ void IP_X_Config(void) { IP_AssignMemory(_aPool, sizeof(_aPool)); // Assigning memory IP_AddEtherInterface(&IP_Driver_MCF5329); // Add ethernet driver IP_SetHWAddr((const unsigned char *)"\x00\x22\xC7\xFF\xFF\xFF"); // // Use DHCP client or define IP address, subnet mask, // gateway address and DNS server according to the // requirements of your application. // IP_DHCPC_Activate(0, "TARGET", NULL, NULL); // IP_SetAddrMask(0xC0A805E6, 0xFFFF0000); // Assign IP addr. and subnet mask // IP_SetGWAddr(0, 0xC0A80201); // Set gateway address // IP_DNS_SetServer(0xCC98B84C); // Set DNS server address, // for example 204.152.184.76 // // Add protocols to the stack // IP_TCP_Add(); IP_UDP_Add(); IP_ICMP_Add(); // // Run-time configure buffers. // The default setup will do for most cases. // IP_AddBuffers(12, 256); // Small buffers. IP_AddBuffers(10, 1536); // Big buffers. IP_ConfTCPSpace(4 * 1024, 4 * 1024); // Define the TCP Tx and Rx window size // // Define log and warn filter // IP_SetWarnFilter(0xFFFFFFFF); IP_SetLogFilter(IP_MTYPE_INIT UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 310 CHAPTER 15 Network interface drivers | IP_MTYPE_LINK_CHANGE | IP_MTYPE_DHCP ); } 15.2.6.3 Driver-specific configuration functions None. 15.2.6.4 Required BSP functions None. 15.2.6.5 Additional information None. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 311 Parameter Parameter Description [IN] Zero-based index of available network interfaces. Unit Table 15.28: BSP_ETH_Init() parameter list Example /* Excerpt from implementation for the ATMEL AT91SAM9261-EK */ #define #define #define #define #define #define #define _PIOC_ID _PMC_PCER _PIOC_PER _PIOC_ODR _PIOC_OER _PIOC_SODR _PIOC_CODR (4) (*(volatile (*(volatile (*(volatile (*(volatile (*(volatile (*(volatile unsigned unsigned unsigned unsigned unsigned unsigned int*) int*) int*) int*) int*) int*) 0xFFFFF810) 0xFFFFFC00) 0xFFFFFC14) 0xFFFFFC10) 0xFFFFFC30) 0xFFFFFC34) /********************************************************************* * * BSP_ETH_Init() */ void BSP_ETH_Init(unsigned Unit) { int i; _PMC_PCER |= (1 << _PIOC_ID); // Enable peripheral clock _PIOC_PER = (1 << 10) | (1 << 11); // Enable Ports for RESET and Interrupt _PIOC_OER = (1 << 10); // Switch RESET to output mode _PIOC_ODR = (1 << 11); // Switch Interrupt to output mode // // Activate & deactivate RESET of Ethernet controller. // We do this in a loop to allow sufficient time for Controller to get out of RESET // for (i = 0; i < 1000; i++) { _PIOC_SODR = (1 << 10); // Activate RESET } for (i = 0; i < 1000; i++) { _PIOC_CODR = (1 << 10); // Deactivate RESET } } 15.2.6.6 Additional information None. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 312 CHAPTER 15 Network interface drivers 15.2.7 NXP LPC17xx The NXP LPC17xx MCUs are flash microcontrollers with integrated Ethernet, USB and CAN interfaces, based on the 32-bit Cortex-M3 processor. 15.2.7.1 Supported hardware The network interface driver for the NXP 17xx can be used with every NXP LPC17xx target board. The driver has been tested on the following eval boards: Tested evaluation boards KEIL MCB1760 IAR LPC1768-SK EmbeddedArtists LPC1788 Table 15.29: List of tested eval boards 15.2.7.2 Configuring the driver Adding the driver to embOS/IP To add the driver, use IP_AddEtherInterface() with the driver identifier IP_Driver_LPC24xx. This function must be called from IP_X_Config(). Refer to IP_AddEtherInterface() on page 49 and IP_X_Configure() on page 326 for more information. Example /* Sample implementation taken from the configuration for the NXP LPC2468 */ /********************************************************************* * * IP_X_Config * * Function description * This function is called by the IP stack during IP_Init(). */ void IP_X_Config(void) { IP_AssignMemory(_aPool, sizeof(_aPool)); // Assigning memory IP_AddEtherInterface(&IP_Driver_LPC17xx); // Add ethernet driver IP_SetHWAddr("\x00\x22\x33\x44\x55\x66"); // MAC addr: Needs to be unique // for production units IP_DHCPC_Activate(0, "TARGET", NULL, NULL); // // Add protocols to the stack // IP_TCP_Add(); IP_UDP_Add(); IP_ICMP_Add(); // // Run-time configure buffers. // The default setup will do for most cases. // IP_AddBuffers(6, 256); // Small buffers. IP_AddBuffers(8, 1536); // Big buffers. Size should be 1536 // to allow a full ether packet to fit. IP_ConfTCPSpace(6 * 1024, 6 * 1024); IP_SetWarnFilter(0xFFFFFFFF); // Do not filter: Output all warnings. IP_SetLogFilter(IP_MTYPE_INIT | IP_MTYPE_LINK_CHANGE ); } 15.2.7.3 Driver-specific configuration functions None. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 313 15.2.7.4 Required BSP functions Function Description Initializes the network interface. BSP_ETH_Init() Table 15.30: embOS/IP driver specific function overview 15.2.7.4.1 BSP_ETH_Init() Description This function is called from the network interface driver. It initializes the network interface. This function should be used to enable the ports which are connected to the network hardware. It is called from the driver during the initialization process. Prototype void BSP_ETH_Init( unsigned Unit ); Parameter Parameter Unit Description [IN] Zero-based index of available network interfaces. Table 15.31: BSP_ETH_Init() parameter list Example /* Sample implementation for NXP LPC2468 */ #define PINSEL2 #define PINSEL3 *(volatile unsigned long *)(0xE002C008) *(volatile unsigned long *)(0xE002C00C) /********************************************************************* * * ETH_Init */ void BSP_ETH_Init(unsigned Unit) { /*-----------------------------------------------------------------------------* write to PINSEL2/3 to select the PHY functions on P1[17:0] *-----------------------------------------------------------------------------*/ /* P1.6, ENET-TX_CLK, has to be set for EMAC to address a BUG in the rev"xx-X" or "xx-Y" silicon(see errata). On the new rev.(xxAY, released on 06/22/2007), P1.6 should NOT be set. */ if (MAC_MODULEID == 0x39022000) { // Older chip ? PINSEL2 = 0x50151105; /* Selects P1[0,1,4,6,8,9,10,14,15] */ } else { PINSEL2 = 0x50150105; /* Selects P1[0,1,4,8,9,10,14,15] */ } PINSEL3 = (PINSEL3 & ~0x0000000f) | 0x5; } 15.2.7.5 Additional information None. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 314 CHAPTER 15 Network interface drivers 15.2.8 NXP LPC23xx / 24xx The NXP LPC23xx and LPC24xx MCU families are flash microcontrollers with integrated Ethernet, USB and CAN interfaces, based on the 32-bit ARM7TDMI-S RISC processor. 15.2.8.1 Supported hardware The network interface driver for the NXP LPC23xx and LPC24xx MCUs can be used with every NXP LPC23xx/LPC24xx target board. The driver has been tested on the following eval boards: Tested evaluation boards KEIL MCB2300 IAR LPC2468 V1.0 EmbeddedArtists LPC2468 Table 15.32: List of tested eval boards 15.2.8.2 Configuring the driver Adding the driver to embOS/IP To add the driver, use IP_AddEtherInterface() with the driver identifier IP_Driver_LPC24xx. This function must be called from IP_X_Config(). Refer to IP_AddEtherInterface() on page 49 and IP_X_Configure() on page 326 for more information. Example /* Sample implementation taken from the configuration for the NXP LPC2468 */ /********************************************************************* * * IP_X_Config * * Function description * This function is called by the IP stack during IP_Init(). */ void IP_X_Config(void) { IP_AssignMemory(_aPool, sizeof(_aPool)); // Assigning memory IP_AddEtherInterface(&IP_Driver_LPC24xx); // Add ethernet driver IP_SetHWAddr("\x00\x22\x33\x44\x55\x66"); // MAC addr: Needs to be unique // for production units IP_DHCPC_Activate(0, "TARGET", NULL, NULL); // // Add protocols to the stack // IP_TCP_Add(); IP_UDP_Add(); IP_ICMP_Add(); // // Run-time configure buffers. // The default setup will do for most cases. // IP_AddBuffers(6, 256); // Small buffers. IP_AddBuffers(8, 1536); // Big buffers. Size should be 1536 // to allow a full ether packet to fit. IP_ConfTCPSpace(6 * 1024, 6 * 1024); IP_SetWarnFilter(0xFFFFFFFF); // Do not filter: Output all warnings. IP_SetLogFilter(IP_MTYPE_INIT | IP_MTYPE_LINK_CHANGE ); } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 315 15.2.8.3 Driver-specific configuration functions None. 15.2.8.4 Required BSP functions Function Description Initializes the network interface. BSP_ETH_Init() Table 15.33: embOS/IP driver specific function overview 15.2.8.4.1 BSP_ETH_Init() Description This function is called from the network interface driver. It initializes the network interface. This function should be used to enable the ports which are connected to the network hardware. It is called from the driver during the initialization process. Prototype void BSP_ETH_Init( unsigned Unit ); Parameter Parameter Unit Description [IN] Zero-based index of available network interfaces. Table 15.34: BSP_ETH_Init() parameter list Example /* Sample implementation for NXP LPC2468 */ #define PINSEL2 #define PINSEL3 *(volatile unsigned long *)(0xE002C008) *(volatile unsigned long *)(0xE002C00C) /********************************************************************* * * ETH_Init */ void BSP_ETH_Init(unsigned Unit) { /*-----------------------------------------------------------------------------* write to PINSEL2/3 to select the PHY functions on P1[17:0] *-----------------------------------------------------------------------------*/ /* P1.6, ENET-TX_CLK, has to be set for EMAC to address a BUG in the rev"xx-X" or "xx-Y" silicon(see errata). On the new rev.(xxAY, released on 06/22/2007), P1.6 should NOT be set. */ if (MAC_MODULEID == 0x39022000) { // Older chip ? PINSEL2 = 0x50151105; /* Selects P1[0,1,4,6,8,9,10,14,15] */ } else { PINSEL2 = 0x50150105; /* Selects P1[0,1,4,8,9,10,14,15] */ } PINSEL3 = (PINSEL3 & ~0x0000000f) | 0x5; } 15.2.8.5 Additional information None. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 316 CHAPTER 15 Network interface drivers 15.2.9 ST STR912 The ST STR912 is based on the ARM966E-STM processor. It is a flash microcontroller with integrated Ethernet, USB and CAN interfaces, AC Motor Control, 4 Timers, ADC, RTC, and DMA. 15.2.9.1 Supported hardware The network interface driver for the STR912 can be used with every target ST STR912 target board. The driver has been tested on the following eval boards: Tested evaluation boards IAR STR912FA development board Table 15.35: List of tested eval boards 15.2.9.2 Configuring the driver Adding the driver to embOS/IP To add the driver, use IP_AddEtherInterface() with the driver identifier IP_Driver_STR912. This function must be called from IP_X_Config(). Refer to IP_AddEtherInterface() on page 49 and IP_X_Configure() on page 326 for more information. Example /* Sample implementation taken from the configuration for the ST STR912 */ void IP_X_Config(void) { IP_AssignMemory(_aPool, sizeof(_aPool)); IP_AddEtherInterface(&IP_Driver_STR912); IP_SetHWAddr("\x00\x22\x33\x44\x55\x66"); // // // // IP_DHCPC_Activate(0, "TARGET", NULL, NULL); // // Add protocols to the stack // IP_TCP_Add(); IP_UDP_Add(); IP_ICMP_Add(); // // Run-time configure buffers. // The default setup will do for most cases. // IP_AddBuffers(20, 256); // IP_AddBuffers(12, 1536); // // IP_ConfTCPSpace(8 * 1024, 8 * 1024); IP_SetWarnFilter(0xFFFFFFFF); // // IP_SetLogFilter(IP_MTYPE_INIT | IP_MTYPE_LINK_CHANGE | IP_MTYPE_DHCP); Assigning memory Add Ethernet driver MAC addr: Needs to be unique for production units Small buffers. Big buffers. Size should be 1536 to allow a full ether packet to fit. 0xFFFFFFFF: Do not filter: Output all warnings. } 15.2.9.3 Driver-specific configuration functions None. 15.2.9.4 Required BSP functions None. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 317 15.2.9.5 Additional information None. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 318 CHAPTER 15 Network interface drivers 15.3 Writing your own driver If you are going to use embOS/IP with your own hardware, you may have to write your own network interface driver. This section describes which functions are required and how to integrate your own network interface driver into embOS/IP. Note: We strongly recommend contacting SEGGER if you need to have a driver for a particular piece of hardware which is not yet supported. Writing a driver is a difficult task which requires a thorough understanding of Ethernet, MAC, and PHY. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 319 15.3.1 Network interface driver structure embOS/IP uses a simple structure with function pointers to call the appropriate driver function for a device. Use the supplied template IP_NI_Template.c for the implementation. Device Driver Structure pfInit() pfTimer() pfSendPackedIfTxIdle() pfGetPacketSize() pfReadPacket() pfControl() Data structure typedef struct IP_HW_DRIVER { int (*pfInit) ( unsigned int (*pfSendPacket) ( unsigned int (*pfGetPacketSize) ( unsigned int (*pfReadPacket) ( unsigned void (*pfTimer) ( unsigned int (*pfControl) ( unsigned } IP_HW_DRIVER; Unit ); Unit ); Unit ); Unit, U8 * pDest, unsigned NumBytes ); Unit ); Unit, int Cmd, void * p ); Elements of IP_HW_DRIVER Element pfInit pfSendPacket pfGetPacketSize pfReadPacket pfTimer pfControl Meaning Pointer to the initialization function. Pointer to the send packet function. Pointer to the get packet size function. Pointer to the read packet function. Optional: Pointer to the timer function. The routine is called from the stack periodically. Pointer to the control function. Table 15.36: IP_HW_DRIVER - List of structure member variables Example /* Sample implementation taken from the driver for the ATMEL AT91SAM7X */ /********************************************************************* * * Driver API Table * ********************************************************************** */ const IP_HW_DRIVER IP_Driver_SAM7X = { _Init, _SendPacketIfTxIdle, _GetPacketSize, _ReadPacket, _Timer, _Control }; UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 320 CHAPTER 15 Network interface drivers 15.3.2 Device driver functions This section provides descriptions of the network interface driver functions required by embOS/IP. Note that the names used for these functions are not really relevant for embOS/IP because the stack accesses them through a structure of function pointers. Function pfControl() pfInit() pfGetPacketSize() pfReadPacket() pfSendPacketIfTxIdle() pfTimer() Description This function is used to implement additional driver specific control functions. It can be empty. General initialization function of the driver. Reads buffer descriptors to find out if a packet has been received. Reads the first packet in the buffer. Send the next packet in the send queue if transmitter is idle. Timer function called by the networking task, IP_Task(), once per second. Table 15.37: embOS/IP network interface driver functions UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 321 15.3.3 Driver template The driver template IP_NI_Template.c is supplied in the folder Sample\Driver\Template\. Example /********************************************************************* * SEGGER MICROCONTROLLER SYSTEME GmbH * * Solutions for real time microcontroller applications * ********************************************************************** * * * (C) 2007 - 2008 SEGGER Microcontroller Systeme GmbH * * * * www.segger.com Support: support@segger.com * * * ********************************************************************** * * * TCP/IP stack for embedded applications * * * ********************************************************************** ---------------------------------------------------------------------File : IP_NI_Template.c Purpose : Network interface driver template -------- END-OF-HEADER --------------------------------------------*/ #include "IP_Int.h" /********************************************************************* * * _SetFilter * * Function description * Sets the MAC filter(s) * The stack tells the driver which addresses should go thru the filter. * The number of addresses can generally be unlimited. * In most cases, only one address is set. * However, if the NI is in multiple nets at the same time or if multicast is used, * multiple addresses can be set. * * Notes * (1) Procedure * In general, precise filtering is used as far as supported by the hardware. * If the more addresses need to be filtered than precise address filters are * available, then the hash filter is used. * Alternativly, the MAC can be switched to promiscuous mode for simple * implementations. */ static int _SetFilter(IP_NI_CMD_SET_FILTER_DATA * pFilter) { U32 v; U32 w; unsigned i; unsigned NumAddr; const U8 * pAddrData; NumAddr = pFilter->NumAddr; for (i = 0; i < NumAddr; i++) { pAddrData = *(&pFilter->pHWAddr + i); } return 0; // O.K. } /********************************************************************* * * _SendPacket * * Function description * Send the next packet in the send queue. * Function is called from 2 places: * - from a task via pfSendPacketIfTxIdle() in Driver structure * - from ISR when Tx is completed (TxInterrupt) */ static int _SendPacket(void) { U32 v; void * pPacket; unsigned NumBytes; UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 322 CHAPTER 15 IP_GetNextOutPacket(&pPacket, &NumBytes); Network interface drivers // Get information about next // packet in the Queue. 0 // means no packet in queue if (NumBytes == 0) { return 0; } IP_LOG((IP_MTYPE_DRIVER, "DRIVER: Sending packet: %d bytes", NumBytes)); // // Start send // return 0; } /********************************************************************* * * _ISR_Handler * * Function description * This is the interrupt service routine for the NI (EMAC). * It handles all interrupts (Rx, Tx, Error). * */ static void _ISR_Handler(void) { } /********************************************************************* * * _Init * * Function description * General init function of the driver. * Called by the stack in the init phase before any other driver function. */ static int _Init(unsigned Unit) { int r; r = _PHY_Init(Unit); if (r) { return 1; } // // TBD // return 0; // Configure the PHY } /********************************************************************* * * _SendPacketIfTxIdle * * Function description * Send the next packet in the send queue if transmitter is idle. * If transmitter is busy, nothing is done since the next packet is sent * automatically with Tx-interrupt. * Function is called from a task via function pointer in in driver structure. */ static int _SendPacketIfTxIdle(unsigned Unit) { // // TBD // return 0; } /********************************************************************* * * _GetPacketSize() * * Function description * Reads buffer descriptors in order to find out if a packet has been received. * Different error conditions are checked and handled. * Function is called from a task via function pointer in driver structure. * * Return value * Number of buffers used for the next packet. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 323 * 0 if no complete packet is available. */ static int _GetPacketSize(unsigned Unit) { // // TBD // return 0; } /********************************************************************* * * _ReadPacket * * Function description * Reads the first packet into the buffer. * NumBytes must be the correct number of bytes as retrieved by _GetPacketSize(); * Function is called from a task via function pointer in driver structure. * */ static int _ReadPacket(unsigned Unit, U8 *pDest, unsigned NumBytes) { // // TBD // return 0; } /********************************************************************* * * _Timer * * Function description * Timer function called by the Net task once per second. * Function is called from a task via function pointer in driver structure. */ static void _Timer(unsigned Unit) { // _UpdateLinkState(); } /********************************************************************* * * _Control * * Function description * Control function for various purposes. * Function is called from a task via function pointer in driver structure. * * Return value * -1: Command is not supported * !=-1: Command supported. Typically 0 means success, * but can also be a return value. */ static int _Control(unsigned Unit, int Cmd, void * p) { switch (Cmd) { case IP_NI_CMD_SET_FILTER: return _SetFilter((IP_NI_CMD_SET_FILTER_DATA*)p); case IP_NI_CMD_SET_BPRESSURE: // // TBD: Enable back pressure (if supported) and change return value to 0 // break; case IP_NI_CMD_CLR_BPRESSURE: // // TBD: Disable back pressure (if supported) and change return value to 0 // break; case IP_NI_CMD_GET_MAC_ADDR: break; case IP_NI_CMD_GET_CAPS: // // TBD: Retrieves the capabilites, which are a logical-or combination of // the IP_NI_CAPS (if any) // // { // int v; // // v = 0 // | IP_NI_CAPS_WRITE_IP_CHKSUM // Driver capable of inserting the // IP-checksum into an outgoing packet? UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 324 CHAPTER 15 // | IP_NI_CAPS_WRITE_UDP_CHKSUM // | IP_NI_CAPS_WRITE_TCP_CHKSUM // | IP_NI_CAPS_WRITE_ICMP_CHKSUM // | IP_NI_CAPS_CHECK_IP_CHKSUM // | IP_NI_CAPS_CHECK_UDP_CHKSUM // | IP_NI_CAPS_CHECK_TCP_CHKSUM // | IP_NI_CAPS_CHECK_ICMP_CHKSUM // // // // // // // // // // // // // // // // // // Network interface drivers Driver capable of inserting the UDP-checksum into an outgoing packet? Driver capable of inserting the TCP-checksum into an outgoing packet? Driver capable of inserting the ICMP-checksum into an outgoing packet? Driver capable of computing and comparing the IP-checksum of incoming packets? Driver capable of computing and comparing the UDP-checksum of an incoming packet? Driver capable of computing and comparing the TCP-checksum of an incoming packet? Driver capable of computing and comparing the ICMP-checksum of an incoming packet? // } // return v; break; case IP_NI_CMD_POLL: // // Poll MAC (typically once per ms) in cases where MAC does not // trigger an interrupt. // break; default: ; } return -1; } /********************************************************************* * * Public API struct * * This is the only public part of the driver. * All driver functions are called indirectly via this structure * */ const IP_HW_DRIVER IP_Driver_Template = { _Init, _SendPacketIfTxIdle, _GetPacketSize, _ReadPacket, _Timer, _Control }; /*************************** End of file ****************************/ UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 325 Chapter 16 Configuring embOS/IP embOS/IP can be used without changing any of the compile-time flags. All compiletime configuration flags are preconfigured with valid values, which match the requirements of most applications. Network interface drivers can be added at runtime. The default configuration of embOS/IP can be changed via compile-time flags which can be added to IP_Conf.h. IP_Conf.h is the main configuration file for the TCP/IP stack. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 326 CHAPTER 16 Configuring embOS/IP 16.1 Runtime configuration Every driver folder includes a configuration file with implementations of runtime configuration functions explained in this chapter. These functions can be customized. 16.1.1 IP_X_Configure() Description Helper function to prepare and configure the TCP/IP stack. Prototype void IP_X_Config (void); Additional information This function is called by the startup code of the TCP/IP stack from IP_Init(). Refer to IP_Init() on page 101 for more information. Example /********************************************************************* * * IP_X_Config * * Function description * This function is called by the IP stack during IP_Init(). * * Typical memory/buffer configurations: * Microcontroller system, minimum size optimized * #define ALLOC_SIZE 0x1000 // 4 kBytes RAM * mtu = 576; // 576 is minimum acc. to * // RFC, 1500 is max. for * // Ethernet. * IP_SetMTU(0, mtu); // Maximum Transmission * // Unit is 1500 for * // Ethernet by default. * IP_AddBuffers(4, 256); // Small buffers. * IP_AddBuffers(2, mtu + 16); // Big buffers. Size should * // be mtu + 16 bytes for * // Ethernet header (2 bytes * // type, 2 * 6 bytes MAC, * // 2 bytes padding). * IP_ConfTCPSpace(2 * (mtu - 40), 1 * (mtu - 40)); // Define TCP Tx and Rx * // window size. * * Microcontroller system, size optimized * #define ALLOC_SIZE 0x3000 // 12 kBytes RAM * mtu = 576; // 576 is minimum acc. to * // RFC, 1500 is max. for * // Ethernet. * IP_SetMTU(0, mtu); // Maximum Transmission * // Unit is 1500 for * // Ethernet by default. * IP_AddBuffers(8, 256); // Small buffers. * IP_AddBuffers(4, mtu + 16); // Big buffers. Size should * // be mtu + 16 bytes for * // Ethernet header (2 bytes * // type, 2 * 6 bytes MAC, * // 2 bytes padding). * IP_ConfTCPSpace(2 * (mtu - 40), 2 * (mtu - 40)); // Define TCP Tx and Rx * // window size. * * Microcontroller system, speed optimized or multiple connections * #define ALLOC_SIZE 0x6000 // 24 kBytes RAM * mtu = 1500; // 576 is minimum acc. to * // RFC, 1500 is max. for * // Ethernet. * IP_SetMTU(0, mtu); // Maximum Transmission * // Unit is 1500 for * // Ethernet by default. * IP_AddBuffers(12, 256); // Small buffers. * IP_AddBuffers(6, mtu + 16); // Big buffers. Size should * // be mtu + 16 bytes for * // Ethernet header (2 bytes * // type, 2 * 6 bytes MAC, UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 327 * * IP_ConfTCPSpace(3 * (mtu - 40), 3 * (mtu - 40)); * * * System with lots of RAM * #define ALLOC_SIZE 0x20000 * mtu = 1500; * * * IP_SetMTU(0, mtu); * * * IP_AddBuffers(50, 256); * IP_AddBuffers(50, mtu + 16); * * * * * IP_ConfTCPSpace(8 * (mtu - 40), 8 * (mtu - 40)); * */ void IP_X_Config(void) { int mtu; IP_AssignMemory(_aPool, sizeof(_aPool)); IP_AddEtherInterface(&IP_Driver_STR912); IP_SetHWAddr("\x00\x22\x33\x44\x55\x66"); // // // // // 2 bytes padding). // Define TCP Tx and Rx // window size. // // // // // // // // // // // // // // // 128 kBytes RAM 576 is minimum acc. to RFC, 1500 is max. for Ethernet. Maximum Transmission Unit is 1500 for Ethernet by default. Small buffers. Big buffers. Size should be mtu + 16 bytes for Ethernet header (2 bytes type, 2 * 6 bytes MAC, 2 bytes padding). Define TCP Tx and Rx window size. Assigning memory Add ethernet driver MAC addr: Needs to be unique for production units // // Use DHCP client or define IP address, subnet mask, // gateway address and DNS server according to the // requirements of your application. // IP_DHCPC_Activate(0, "TARGET", NULL, NULL); // IP_SetAddrMask(0xC0A805E6, 0xFFFF0000); // Assign IP addr. and subnet mask // IP_SetGWAddr(0, 0xC0A80201); // Set gateway address // IP_DNS_SetServer(0xCC98B84C); // Set DNS server address, // for example 204.152.184.76 // // Add protocols to the stack // IP_TCP_Add(); IP_UDP_Add(); IP_ICMP_Add(); // // Run-time configure buffers. // The default setup will do for most cases. // IP_AddBuffers(12, 256); // Small buffers. IP_AddBuffers(6, mtu + 16); // Big buffers. Size should be // mtu + 16 bytes for Ethernet // header (2 bytes type, 2 * 6 // bytes MAC, 2 bytes padding). IP_ConfTCPSpace(3 * (mtu - 40), 3 * (mtu - 40)); // Define the TCP Tx and Rx // window size. // // Define log and warn filter // Note: The terminal I/O emulation affects the timing // of your communication, since the debugger stops the target // for every terminal I/O output unless you use DCC! // IP_SetWarnFilter(0xFFFFFFFF); // 0xFFFFFFFF: Output all warnings. IP_SetLogFilter(IP_MTYPE_INIT // Output all messages from init | IP_MTYPE_LINK_CHANGE // Output a msg if link status changes | IP_MTYPE_DHCP // Output general DHCP status messages ); } 16.1.2 Driver handling IP_X_Config() is called at initialization of the TCP/IP stack. It is called by the IP stack during IP_Init(). IP_X_Config() should help to bundle the process of adding and configuring the driver. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 328 CHAPTER 16 Configuring embOS/IP 16.1.3 Memory and buffer assignment The total memory requirements of the TCP/IP stack can basically be computed as the sum of the following components: Description IP-Stack core Sockets UDP connection TCP/ connection ROM app. 200 bytes n * app. 200 bytes n * app. 100 bytes n * app. 200 bytes + RAM for TCP Window 16.1.3.1 RAM for TCP window The data for the TCP window is typically stored in large buffers. The number of large buffers required is typically: RxWindowSize / BigBufferSize This amount of buffers (and RAM for these buffers) is needed for every simultaneously active TCP connection, where "active" means sending & receiving data. 16.1.3.2 Required buffers Most of the RAM used by the stack is used for packet buffers. Packet buffers are used to hold incoming and outgoing packets and data in receive and transmit windows of TCP connections. Example configuration - Extremly small (4 kBytes) This configuration is the smallest available or at least very close. It is intended to be used on MCUs with very little RAM and can be used for applications which are designed for a very low amount of traffic. #define ALLOC_SIZE 0x1000 mtu = 576; IP_SetMTU(0, mtu); IP_AddBuffers(4, 256); IP_AddBuffers(2, mtu + 16); IP_ConfTCPSpace(2 * (mtu-40), 1 * (mtu-40)); // // // // // // // // // // // 4 kBytes RAM 576 is minimum acc. to RFC, 1500 is max. for Ethernet Maximum Transmission Unit is 1500 for ethernet by default Small buffers. Big buffers. Size should be mtu + 16 byte for ethernet header (2 bytes type, 2*6 bytes MAC, 2 bytes padding) Define TCP Tx and Rx window size Example configuration - Small (12 kBytes) This configuration is a small configuration intended to be used on MCUs with little RAM and can be used for applications which are designed for a medium amount of traffic. #define ALLOC_SIZE 0x3000 mtu = 576; IP_SetMTU(0, mtu); IP_AddBuffers(8, 256); IP_AddBuffers(4, mtu + 16); IP_ConfTCPSpace(2 * (mtu-40), 2 * (mtu-40)); UM07001 User & Reference Guide for embOS/IP // // // // // // // // // // // 12 kBytes RAM 576 is minimum acc. to RFC, 1500 is max. for Ethernet Maximum Transmission Unit is 1500 for ethernet by default Small buffers. Big buffers. Size should be mtu + 16 byte for ethernet header (2 bytes type, 2*6 bytes MAC, 2 bytes padding) Define TCP Tx and Rx window size (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 329 Example configuration - Normal (24 kBytes) This configuration is a typical configuration for many MCUs that have a fair amount of internal RAM. It can be used for applications which are designed for a higher amount of traffic and/or multiple client connections. #define ALLOC_SIZE 0x6000 mtu = 1500; IP_SetMTU(0, mtu); IP_AddBuffers(12, 256); IP_AddBuffers(6, mtu + 16); IP_ConfTCPSpace(3 * (mtu-40), 3 * (mtu-40)); // // // // // // // // // // // 24 kBytes RAM 576 is minimum acc. to RFC, 500 is max. for Ethernet Maximum Transmission Unit is 1500 for ethernet by default Small buffers. Big buffers. Size should be mtu + 16 byte for ethernet header (2 bytes type, 2*6 bytes MAC, 2 bytes padding) Define TCP Tx and Rx window size Example configuration - Large (128 kBytes) This configuration is a large configuration intended to be used on MCUs with many external RAM. It can be used for applications which are designed for a high amount of traffic and multiple client/server connections at the same time. #define ALLOC_SIZE 0x20000 mtu = 1500; IP_SetMTU(0, mtu); IP_AddBuffers(50, 256); IP_AddBuffers(50, mtu + 16); IP_ConfTCPSpace(8 * (mtu-40), 8 * (mtu-40)); UM07001 User & Reference Guide for embOS/IP // // // // // // // // // // // 128 Kbytes RAM 576 is minimum acc. to RFC, 1500 is max. for Ethernet Maximum Transmission Unit is 1500 for ethernet by default Small buffers. Big buffers. Size should be mtu + 16 byte for ethernet header (2 bytes type, 2*6 bytes MAC, 2 bytes padding) Define TCP Tx and Rx window size (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 330 CHAPTER 16 Configuring embOS/IP 16.2 Compile-time configuration The following types of configuration macros exist: Binary switches "B" Switches can have a value of either 0 or 1, for deactivated and activated respectively. Actually, anything other than 0 works, but 1 makes it easier to read a configuration file. These switches can enable or disable a certain functionality or behavior. Switches are the simplest form of configuration macros. Numerical values "N" Numerical values are used somewhere in the code in place of a numerical constant. A typical example is the configuration of the sector size of a storage medium. Function replacements "F" Macros can basically be treated like regular functions although certain limitations apply, as a macro is still put into the code as simple text replacement. Function replacements are mainly used to add specific functionality to a module which is highly hardware-dependent. This type of macro is always declared using brackets (and optional parameters). 16.2.1 Compile-time configuration switches Type Symbolic name N IP_IS_BIGENDIAN N IP_DEBUG F IP_CKSUM F IP_MEMCPY F IP_MEMSET Default Description System configuration macros Macro to define if a big endian tar-get is used. Debug macros Macro to define the debug level of the embOS/IP build. Refer to 0 Debug level on page 331 for a description of the different debug level. Optimization macros Macro to define an optimized checksum routine to speed up the stack. An optimized checksum rouIP_cksum tine is typically implemented in (C- routine in IP assembly language. stack) Optimized versions for the GNU, IAR and ADS compilers are supplied. Macro to define an optimized memcpy routine to speed up the memcpy stack. An optimized memcpy rou(C-routine in tine is typically implemented in standard Cassembly language. library) Optimized version for the IAR compiler is supplied. Macro to define an optimized memset memset routine to speed up the (C-routine in stack. An optimized memset roustandard Ctine is typically implemented in library) assembly language. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 331 Type F F Symbolic name Default IP_MEMMOVE memmove (C-routine in standard Clibrary) IP_MEMCMP memcmp (C-routine in standard Clibrary) Description Macro to define an optimized memmove routine to speed up the stack. An optimized memmove routine is typically implemented in assembly language. Macro to define an optimized memcmp routine to speed up the stack. An optimized memcmp routine is typically implemented in assembly language. 16.2.2 Debug level embOS/IP can be configured to display debug information at higher debug levels to locate a problem (Error) or potential problem. To display information, embOS/IP uses the logging routines (see chapter Debugging on page 541). These routines can be blank, they are not required for the functionality of embOS/IP. In a target system, they are typically not required in a release (production) build, since a production build typically uses a lower debug level. If (IP_DEBUG == 0): used for release builds. Includes no debug options. If (IP_DEBUG == 1): IP_PANIC() is mapped to IP_Panic(). If (IP_DEBUG >= 2): IP_PANIC() is mapped to IP_Panic() and logging support is activated. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 332 UM07001 User & Reference Guide for embOS/IP CHAPTER 16 Configuring embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 333 Chapter 17 Web server (Add-on) The embOS/IP web server is an optional extension to embOS/IP. The web server can be used with embOS/IP or with a different TCP/IP stack. All functions that are required to add a web server task to your application are described in this chapter. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 334 CHAPTER 17 Web server (Add-on) 17.1 embOS/IP web server The embOS/IP web server is an optional extension which adds the HTTP protocol to the stack. It combines a maximum of performance with a small memory footprint. The web server allows an embedded system to present web pages with dynamically generated content. It comes with all features typically required by embedded systems: multiple connections, authentication, forms and low RAM usage. RAM usage has been kept to a minimum by smart buffer handling. The web server implements the relevant parts of the following Request For Comments (RFC). RFC# Description HTTP - Hypertext Direct download: HTTP - Hypertext Direct download: [RFC 1945] [RFC 2616] Transfer Protocol -- HTTP/1.0 ftp://ftp.rfc-editor.org/in-notes/rfc1945.txt Transfer Protocol -- HTTP/1.1 ftp://ftp.rfc-editor.org/in-notes/rfc2616.txt The following table shows the contents of the embOS/IP web server root directory: Directory Content Application\ Contains the example application to run the web server with embOS/IP. Config Contains the web server configuration file. Refer to Configuration on page 355 for detailed information. Inc Contains the required include files. IP Contains the web server sources, IP_Webserver.c, IP_Webserver.h and IP_UTIL_BASE64.c, IP_UTIL.h. IP\FS\ Contains the sources for the file system abstraction layer and the read-only file system. Refer to File system abstraction layer on page 564 for detailed information. Windows\Webserver\ Contains the source, the project files and an executable to run embOS/IP web server on a Microsoft Windows host. Refer to Using the web server sample on page 339 for detailed information. Supplied directory structure of embOS/IP web server package UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 335 17.2 Feature list * * * * * * * * * * * Low memory footprint. Dynamic web pages (Server Side Includes). Authentication supported. Forms: POST and GET support. Multiple connections supported. r/o file system included. HTML to C converter included. Independent of the file system: any file system can be used. Independent of the TCP/IP stack: any stack with sockets can be used. Demo with authentication, various forms, dynamic pages included. Project for executable on PC for Microsoft Visual Studio included. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 336 CHAPTER 17 Web server (Add-on) 17.3 Requirements TCP/IP stack The embOS/IP web server requires a TCP/IP stack. It is optimized for embOS/IP, but any RFC-compliant TCP/IP stack can be used. The shipment includes a Win32 simulation, which uses the standard Winsock API and an implementation which uses the socket API of embOS/IP. Multi tasking The web server needs to run as a separate thread. Therefore, a multi tasking system is required to use the embOS/IP web server. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 337 17.4 HTTP backgrounds It is a communication protocol originally designed to transfer information via hypertext pages. The development of HTTP is coordinated by the IETF (Internet Engineering Task Force) and the W3C (World Wide Web Consortium). The current protocol version is 1.1. Application layer HTTP Transport layer TCP Network layer IP Link layer Ethernet (IEEE 802.3), ... 17.4.1 HTTP communication basics HTTP is a challenge and response protocol. A client initiates a TCP connection to the web server and sends a HTTP request. A HTTP request starts with a method token. [RFC 2616] defines 8 method tokens. The method token indicates the method to be performed on the requested resource. embOS/IP web server supports all methods which are typically required by an embedded web server. HTTP method GET HEAD POST Description The GET method means that it retrieves whatever information is identified by the Request-URI. The HEAD method means that it retrieves the header of the content which is identified by the Request-URI. The POST method submits data to be processed to the identified resource. The data is included in the body of the request. Table 17.1: Supported HTTP methods The following example shows parts of a HTTP session, where a client (for example, 192.168.1.75) asks the embOS/IP web server for the hypertext page example.html. The request is followed by a blank line, so that the request ends with a double newline, each in the form of a carriage return followed by a line feed. GET /example.html HTTP/1.1 Host: 192.168.1.75 The first line of every response message is the Status-Line, consisting of the protocol version followed by a numeric status code. The Status-Line is followed by the content-type, the server, expiration and the transfer-encoding. The server response ends with an empty line, followed by length of content that should be transferred. The length indicates the length of the web page in bytes. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 338 CHAPTER 17 Web server (Add-on) HTTP/1.1 200 OK Content-Type: text/html Server: embOS/IP Expires: THU, 26 OCT 1995 00:00:00 GMT Transfer-Encoding: chunked A3 Thereafter, the web server sends the requested hypertext page to the client. The zero at the end of the web page followed by an empty line signalizes that the transmission of the requested web page is complete. <HTML> <HEAD> <TITLE>embOS/IP examples</TITLE> </HEAD> <BODY> <CENTER> <H1>Website: example.htm</H1> </CENTER> </BODY> </HTML> 0 17.4.2 HTTP status codes The first line of a HTTP response is the Status-Line. It consists of the used protocol version, a status code and a short textual description of the Status-Code. The StatusCode element is a 3-digit integer result code of the attempt to understand and satisfy the request. The first digit of the Status-Code defines the class of response. The last two digits do not have any categorization role. There are 5 values for the first digit: * * * * * 1xx: 2xx: 3xx: 4xx: 5xx: Informational - Request received, continuing process. Success - The action was successfully received, understood, and accepted. Redirection - Further action must be taken in order to complete the request. Client Error - The request contains bad syntax or cannot be fulfilled. Server Error - The server failed to fulfill an apparently valid request. Refer to [RFC 2616] for a complete list of defined status-codes. embOS/IP web server supports a subset of the defined HTTP status codes. The following status codes are implemented: Status code 200 401 404 501 503 Description OK. The request has succeeded. Unauthorized. The request requires user authentication. Not found. The server has not found anything matching the Request-URI. Not implemented. The server does not support the HTTP method. Service unavailable. The server is currently unable to handle the request due to a temporary overloading of the server. Table 17.2: embOS/IP status codes UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 339 17.5 Using the web server sample Ready to use examples for Microsoft Windows and embOS/IP are supplied. If you use another TCP/IP stack, the sample OS_IP_Webserver.c has to be adapted. The web server itself does not handle multiple connections. This is part of the application and is included in the OS_IP_Webserver.c sample. The sample application opens a port which listens on port 80 until an incoming connection is detected in a parent task that accepts new connections (or rejects them if no more connections can be accepted). For each accepted client connection, the parent task creates a child task running IP_WEBS_Process() in a seperated context that will then process the request of the connected client (for example a browser). This way the parent task is ready to handle further incoming connections on port 80. Therefore the sample uses n client connections + one for the parent task. Some browsers may open multiple connections and do not even intend to close the connection. They rather keep the connections open for further data that might be requested. To give other clients a chance, a special handling is implemented in the web server. The embOS/IP web server has two functions for processing a connection in a child task: * * IP_WEBS_Process(), that allows a connection to stay open even after all data has been sent from the target. The connection will stay open as long as the client does not close it. IP_WEBS_ProcessLast(), that will close the connection once the target has sent all data requested. This is used by the web server sample for the last free connection available. This ensures that at least one connection will be available after it has been served to accept further clients. In addition to available connections that can be served directly, a feature called "backlogging" can be used. This means additional connections will be accepted (SYN/ACK is sent from target) but not yet processed. They will be processed as soon as a free connection becomes available once a child task has served the clients request and has been closed. Connections in backlog will be kept active until the client side sends a reset due to a possible timeout in the client. The example application uses a read-only file system to make web pages available. Refer to File system abstraction layer on page 564 and File system abstraction layer on page 564 for detailed information about the read-only file system. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 340 CHAPTER 17 Web server (Add-on) 17.5.1 Using the Windows sample If you have MS Visual C++ 6.00 or any later version available, you will be able to work with a Windows sample project using embOS/IP web server. If you do not have the Microsoft compiler, an precompiled executable of the web server is also supplied. Building the sample program Open the workspace Start_Webserver.dsw with MS Visual Studio (for example, double-clicking it). There is no further configuration necessary. You should be able to build the application without any error or warning message. The server uses the IP address of the host PC on which it runs. Open a web browser and connect by entering the IP address of the host (127.0.0.1) to connect to the web server. 17.5.2 Running the web server example on target hardware The embOS/IP web server sample application should always be the first step to check the proper function of the web server with your target hardware. Add all source files located in the following directories (and their subdirectories) to your project and update the include path: * * * * * * Application Config Inc IP IP\IP_FS\FS_RO\ IP\IP_FS\FS_RO\Generated\ It is recommended that you keep the provided folder structure. The sample application can be used on the most targets without the need for changing any of the configuration flags. The server processes up to three connections using the default configuration. Note: Three connections mean that the target can handle up to three targets in parallel, if every target uses only one connection. Because a single web browser often attempts to open more then one connection to a web server to request the files (.gif, .jpeg, etc.) which are included in the requested web page, the number of possible parallel connected targets is less than the number of possible connections. Every connection is handled in an separate task. Therefore, the web server uses up to four tasks in the default configuration, one task which listens on port 80 and accepts connections and three tasks to process the accepted connections. To modify the number of connections, only the macro MAX_CONNECTIONS has to be modified. The supplied sample web pages index.htm, embos.htm and stats.htm include dynamic content, refer to Common Gateway Interface (CGI) on page 342 for detailed information about the implementation of dynamic content. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 341 17.5.3 Changing the file system type By default, the web server uses the supplied read-only file system. If a real file system like emFile should be used to store the web pages, you have to modify the function _WebServerChildTask() of the example OS_IP_Webserver.c. /********************************************************************* * * _WebServerChildTask * */ static void _WebServerChildTask(void * Context) { long Sock; int Opt; _pFS_API = &IP_FS_ReadOnly; Sock = (long)Context; Opt = 1; setsockopt(Sock, SOL_SOCKET, SO_KEEPALIVE, &Opt, sizeof(Opt)); if (_ConnectCnt < MAX_CONNECTIONS) { IP_WEBS_Process(_Send, _Recv, Context, _pFS_API, &_Application); } else { IP_WEBS_ProcessLast(_Send, _Recv, Context, _pFS_API, &_Application); } _closesocket(Sock); _AddToConnectCnt(-1); OS_Terminate(0); } The usage of the read-only file system is configured with the following line: _pFS_API = &IP_FS_ReadOnly; To use emFile as file system for your web server application, add the emFile abstraction layer IP_FS_FS.c to your project and change the line to: _pFS_API = &IP_FS_FS; Refer to File system abstraction layer on page 564 and File system abstraction layer on page 564 for detailed information about the emFile and read-only file system abstraction layer. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 342 CHAPTER 17 Web server (Add-on) 17.6 Dynamic content embos/IP supports two different approaches to implement dynamic content in your web server application. A Common Gateway Interface (CGI) like interface for static HTML pages with dynamic elements and virtual files which are completely generated from the application. 17.6.1 Common Gateway Interface (CGI) A Common Gateway Interface (CGI) like interface is used to implement dynamic content in web pages. Every web page will be parsed by the server each time a request is received. The server searches the web page for a special tag. In the default configuration, the searched tag starts <!--#exec cgi=" and ends with "-->. The tag will be analyzed and the parameter will be extracted. This parameter specifies a serverside command and will be given to the user application, which can handle the command. The following screenshot shows the example page index.htm. The HTML source for the page includes the following line: <!--#exec cgi="Counter"--> When the web page is requested, the server parses the tag and the parameter Counter is searched for in an array of structures of type WEBS_CGI. The structure includes a string to identify the command and a pointer to the function which should be called if the parameter is found. typedef struct { const char * sName; // e.g. "Counter" void (*pf)(WEBS_OUTPUT * pOutput, const char * sParameters, const char * sValue); } WEBS_CGI; In the example, Counter is a valid parameter and the function _callback_ExecCounter will be called. You need to implement the WEBS_CGI array and the callback functions in your application. static const WEBS_CGI _aCGI[] = { {"Counter" , _callback_ExecCounter }, {"GetOSInfo" , _callback_ExecGetOSInfo}, {"GetIPAddr" , _callback_ExecGetIPAddr}, {NULL} }; UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 343 ExecCounter() is a simple example of how to use the CGI feature. It returns a string that includes the value of a variable which is incremented with every call to ExecCounter(). void ExecCounter( WEBS_OUTPUT * pOutput, const char * sParameters, const char * sValue ) { char ac[40]; static char Cnt = 1; sprintf(ac, "You are visitor no.: %d", Cnt); IP_WEBS_SendString(pOutput, ac); Cnt++; } If the web page includes the CGI tag followed by an unknown command (for example, a typo like COounter instead of Counter in the source code of the web page) an error message will be sent to the client. 17.6.1.1 Add new CGI functions to your web server application To define new CGI functions, three things have to be done. 1. Add a new command name which should be used as tag to the WEBS_CGI structure. For example: UserCGI static const WEBS_CGI _aCGI[] = { {"Counter" , _callback_ExecCounter }, {"GetOSInfo" , _callback_ExecGetOSInfo}, {"GetIPAddr" , _callback_ExecGetIPAddr}, {"UserCGI" , _callback_ExecUserCGI }, {NULL} }; 2. Implement the new function in your application source code. void _callback_ExecUserCGI( WEBS_OUTPUT * pOutput, const char * sParameters const char * sValue ) { /* Add application code here */ } 3. Add the new tag to the source code of your web page: <!--#exec cgi="UserCGI"--> UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 344 CHAPTER 17 Web server (Add-on) 17.6.2 Virtual files embOS/IP supports virtual files. A virtual file is not a real file which is stored in the used file system. It is a function which is called instead. The function generates the content of a file and sends it to the client. The web server checks the extension of all requested files, the extension .cgi is by default used for virtual files. To change the extension that is used to detect a virtual file, refer to IP_WEBS_SetFileInfoCallback() on page 365 for detailed information. The embOS/IP web server comes with an example (CallVirtualFile.htm) that requests a virtual file. The sample web page contains a form with two input test fields, named FirstName and LastName, and a button to transmit the data to the server. When the button on the web page is pressed, the file Send.cgi is requested. The embOS/IP Web server recognizes the extension .cgi, checks if a virtual file with the name Send.cgi is defined and calls the defined function. The function in the example is _callback_SendCGI and gets the string FirstName=Foo&LastName=Bar as parameter. typedef struct { const char * sName; void (*pf)(WEBS_OUTPUT * pOutput, const char * sParameters); } WEBS_VFILES; In the example, Send.cgi is a valid URI and the function _callback_SendCGI will be called. static const WEBS_VFILES _aVFiles[] = { {"Send.cgi", _callback_SendCGI }, NULL }; The virtual file Send.cgi gets two parameters. The strings entered in the input fields Firstname and LastName are transmitted with the URI. For example, you enter Foo in the first name field and Bar for last name and push the button. The browser will transmit the following string to our web server: Send.cgi?FirstName=Foo&LastName=Bar You can parse the string and use it in the way you want to. In the example we parse the string and output the values on a web page which is build from the function _callback_SendCGI(). static void _callback_SendCGI(WEBS_OUTPUT * pOutput, const char * sParameters) { char aPara0[32]; char aValue0[32]; char aPara1[32]; char aValue1[32]; int r; UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 345 IP_WEBS_SendString(pOutput, "<HTML><HEAD><TITLE>CGI Sample</TITLE></HEAD>"); IP_WEBS_SendString(pOutput, "<style type=\"text/css\"> H1, H2, H3, H4 { color: blue } H1, H2, H3, H4, H5 {font-family: Helvetica;} PRE {color: black; margin-left: 2%; font-size=150%} BODY {color: black; margin-left: 2%; } </style>"); IP_WEBS_SendString(pOutput, "<HR><H2>CGI Sample</H2><HR><BODY>First name: "); r = IP_WEBS_GetParaValue(sParameters, 0, aPara0, sizeof(aPara0), aValue0, sizeof(aValue0)); if (r == 0) { IP_WEBS_SendString(pOutput, aValue0); } IP_WEBS_SendString(pOutput, "<BR>Last name: "); r = IP_WEBS_GetParaValue(sParameters, 1, aPara1, sizeof(aPara1), aValue1, sizeof(aValue1)); if (r == 0) { IP_WEBS_SendString(pOutput, aValue1); } IP_WEBS_SendString(pOutput, "<BR>"); IP_WEBS_SendString(pOutput, "<HR><CENTER> <A HREF=\"CallVirtualFile.htm\">Back</A> </CENTER><IMG SRC=\"segger.gif\">&nbsp;&nbsp; <A HREF=\"http://www.segger.com\">www.segger.com</A> </BODY></HTML>"); } The output of _callback_SendCGI() should be similar to: UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 346 CHAPTER 17 Web server (Add-on) 17.7 Authentication "HTTP/1.0", includes the specification for a Basic Access Authentication scheme. The basic authentication scheme is a non-secure method of filtering unauthorized access to resources on an HTTP server, because the user name and password are passed over the network as clear text. It is based on the assumption that the connection between the client and the server can be regarded as a trusted carrier. As this is not generally true on an open network, the basic authentication scheme should be used accordingly. The basic access authentication scheme is described in: RFC# [RFC 2617] Description HTTP Authentication: Basic and Digest Access Authentication Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc2617.txt The "basic" authentication scheme is based on the model that the client must authenticate itself with a user-ID and a password for each realm. The realm value should be considered an opaque string which can only be compared for equality with other realms on that server. The server will service the request only if it can validate the user-ID and password for the protection space of the Request-URI. There are no optional authentication parameters. Upon receipt of an unauthorized request for a URI within the protection space, the server should respond with a challenge like the following: WWW-Authenticate: Basic realm="Embedded web server" where "embOS/IP embedded web server" is the string assigned by the server to identify the protection space of the Request-URI. To receive authorization, the client sends the user-ID and password, separated by a single colon (":") character, within a base64 encoded string in the credentials. If the user agent wishes to send the user-ID "user" and password "pass", it would use the following header field: Authorization: Basic dXNlcjpwYXNz UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 347 17.7.1 Authentication example The client requests a resource for which authentication is required: GET /conf/Authen.htm HTTP/1.1 Host: 192.168.1.75 The server answers the request with a "401 Unauthorized" status page. The header of the 401 error page includes an additional line WWW-Authenticate. It includes the realm for which the proper user name and password should be transmitted from the client (for example, a web browser). HTTP/1.1 401 Unauthorized Date: Mon, 04 Feb 2008 17:00:44 GMT Server: embOS/IP Accept-Ranges: bytes Content-Length: 695 Connection: close Content-Type: text/html X-Pad: avoid browser bug WWW-Authenticate: Basic realm="embOS/IP embedded web server" <HTML> <HEAD><TITLE>401 Unauthorized</TITLE></HEAD> <BODY> <H1>401 Unauthorized</H1> Browser not authentication-capable or authentication failed.<P> </BODY> </HTML> The client interprets the header and opens a dialog box to enter the user name and password combination for the realm of the resource. Note: The embOS/IP web server example always uses the following user name and the password combination: User Name: user - Password: pass Enter the proper user name/password combination for the requested realm and confirm with the OK button. The client encodes the user name/password combination to a base64 encoded string and requests the resource again. The request header is enhanced by the following line: Authorization: Basic dXNlcjpwYXNz GET /conf/Authen.htm HTTP/1.1 Host: 192.168.1.75 Authorization: Basic dXNlcjpwYXNz The server decodes the user name/password combination and checks if the decoded string matches to the defined user name/password combination of the realm. If the strings are identical, the server delivers the page. If the strings are not identical, the server answers again with a "401 Unauthorized" status page. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 348 CHAPTER 17 Web server (Add-on) HTTP/1.1 200 OK Content-Type: text/html Server: embOS/IP Expires: THU, 26 OCT 1995 00:00:00 GMT Transfer-Encoding: chunked 200 <HTML> <HEAD> <TITLE>web server configuration</TITLE> </HEAD> <BODY> <!-- Content of the page --> </BODY> </HTML> 0 17.7.2 Configuration of the authentication The embOS/IP web server checks the access rights of every resource before returning it. The user can define different realms to separate different parts of the web server resources. An array of WEBS_ACCESS_CONTROL structures has to be implemented in the user application. Refer to Structure WEBS_ACCESS_CONTROL on page 394 for detailed information about the elements of the WEBS_ACCESS_CONTROL structure. If no authentication should be used, the array includes only one entry for the root path. WEBS_ACCESS_CONTROL _aAccessControl[] = { { "/", NULL, NULL }, 0 }; To define a realm "conf", an additional WEBS_ACCESS CONTROL entry has to be implemented. WEBS_ACCESS_CONTROL _aAccessControl[] = { { "/conf/", "Login for configuration", "user:pass" }, { "/", NULL, NULL }, 0 }; The string "Login for configuration" defines the realm. "user:pass" is the user name/password combination stored in one string. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 349 17.8 Form handling The embOS/IP web server supports both POST and GET actions to receive form data from a client. POST submits data to be processed to the identified resource. The data is included in the body of the request. GET is normally only used to requests a resource, but it is also possible to use GET for actions in web applications. Data processing on server side might create a new resource or update existing resources or both. Every HTML form consists of input items like textfields, buttons, checkboxes, etc. Each of these input items has a name tag. When the user places data in these items in the form, that information is encoded into the form data. Form data is a stream of <name>=<value> pairs separated by the "&" character. The value each of the input item is given by the user is called the value. The <name>=<value> pairs are URL encoded, which means that spaces are changed into "+" and special characters are encoded into hexadecimal values. Refer to [RFC 1738] for detailed information about URL encoding. The parsing and decoding of form data is handled by the embOS/IP web server. Thereafter, the server calls a callback function with the decoded and parsed strings as parameters. The responsibility to implement the callback function is on the user side. Valid characters for CGI function names: * * * * A-Z a-z 0-9 . _ - Valid characters for CGI parameter values: * * * * * A-Z a-z 0-9 All URL encoded characters . _ - *()!$\ UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 350 CHAPTER 17 Web server (Add-on) 17.8.1 Simple form processing sample The following example shows the handling of the output of HTML forms with your web server application. The example web page ExampleGET.htm implements a form with three inputs, two text fields and one button. The HTML code of the web page as it is added to the server is listed below: <html> <head><title>embOS/IP web server form example</title></head> <body> <form action="" method="GET"> <p> First name: <input name="FirstName" type="text" size="30" maxlength="30" value="<!--#exec cgi="FirstName"-->" > <br> Last name: <input name="LastName" type="text" size="30" maxlength="30" value="<!--#exec cgi="LastName"-->" > <br> <input type="submit" value="Send"> </p> </form> </body> </html> The action field of the form can specify a resource that the browser should reference when it sends back filled-in form data. If the action field defines no resource, the current resource will be requested again. If you request the web page from the embOS/IP web server and check the source of the page in your web browser, the CGI parts "<!--#exec cgi="FirstName"-->" and "<!--#exec cgi="LastName"-->" will be executed before the page will be transmitted to the server, so that in the example the values of the value= fields will be empty strings. The HTML code of the web page as seen by the web browser is listed below: <html> <head><title>embOS/IP web server form example</title></head> <body> <form action="" method="GET"> <p> First name: <input name="FirstName" type="text" size="30" maxlength="30" value="" > <br> Last name: <input name="LastName" type="text" size="30" maxlength="30" value="" > <br> <input type="submit" value="Send"> </p> </form> </body> </html> UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 351 To start form processing, you have to fill in the FirstName and the LastName field and click the Send button. In the example, the browser sends a GET request for the resource referenced in the form and appends the form data to the resource name as an URL encoded string. The form data is separated from the resource name by "?". Every <name>=<value> pair is separated by "&". For example, if you type in the FirstName field John and Doe in the LastName field and confirm the input by clicking the Send button, the following string will be transmitted to the server and shown in the address bar of the browser. http://192.168.1.230/ExampleGET.htm?FirstName=John&LastName=Doe Note: If you use POST as HTTP method, the name>=<value> pairs are not shown in the address bar of the browser. The <name>=<value> pairs are in this case included in the entity body. The embOS/IP web server parses the form data. The <name> field specifies the name of a CGI function which should be called to process the <value> field. The server checks therefore if an entry is available in the WEBS_CGI array. static const WEBS_CGI _aCGI[] = { {"FirstName", _callback_ExecFirstName}, {"LastName", _callback_ExecLastName }, {NULL} }; If an entry can be found, the specified callback function will be called. The callback function for the parameter FirstName is defined as follow: /********************************************************************* * * Static data * ********************************************************************** */ static char _acFirstName[12]; /********************************************************************* * * _callback_FirstName */ static void _callback_ExecFirstName( WEBS_OUTPUT * pOutput, const char * sParameters, const char * sValue ) { if (sValue == NULL) { IP_WEBS_SendString(pOutput, _acFirstName); } else { _CopyString(_acFirstName, sValue, sizeof(_acFirstName)); } } The function returns a string if sValue is NULL. If sValue is defined, it will be written into a character array. Because HTTP transmission methods GET and POST only transmit the value of filled input fields, the same function can be used to output a stored value of an input field or to set a new value. The example web page shows after entering and transmitting the input the new values of FirstName and LastName as value in the input fields. The source of the web page as seen by the web browser is listed below: UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 352 CHAPTER 17 Web server (Add-on) <html> <head><title>embOS/IP web server form example</title></head> <body> <form action="" method="GET"> <p> First name: <input name="FirstName" type="text" size="30" maxlength="30" value="John" > <br> Last name: <input name="LastName" type="text" size="30" maxlength="30" value="Doe" > <br> <input type="submit" value="Send"> </p> </form> </body> </html> UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 353 17.9 File upload The embOS/IP web server supports file uploads from the client. For this to be possible a real file system has to be used and the define WEBS_SUPPORT_UPLOAD has to be defined to "1". From the application side uploading a file in general is the same as for other form data as described in Form handling on page 349. For file uploading a <form> field with encoding of type multipart/form-data is needed. An upload form field may contain additional input fields that will be parsed just as if using a non upload formular and can be parsed in your callback using IP_WEBS_GetParaValue() on page 377 or by using IP_WEBS_GetParaValuePtr() on page 378. 17.9.1 Simple form upload sample The following example shows the handling of file uploads with your web server application. The example web page Upload.htm implements a form with a file upload field. The HTML code of the web page as it is added to the server is listed below: <HTML> <BODY> <CENTER> <P> <form action="Upload.cgi" method="post" enctype="multipart/form-data"> <p>Select a file: <input name="Data" type="file"> </p> <input type="submit"><input type="reset"> </form> </P> </CENTER> </BODY> </HTML> The action field of the form can specify a resource that the browser should reference when it has finished handling the file upload. If the action field defines no resource, the current resource will be requested again. To upload a file, you have to select a file by using the browse button and select a file to upload and click the Send button. In the example, the browser sends a POST request for the resource referenced in the form and appends the form and file data in an encoded string. The embOS/IP web server parses additional form data passed besides the file to be uploaded. This works the same as handling form data described in Form handling on page 349. The action parameter of the <form> field specifies the name of a virtual file that should be processed. A callback can then be used to provide an answer page referring the state of the upload. The example below shows how to check the success of an upload using a virtual file prvided by the WEBS_VFILES array: static const WEBS_VFILES _aVFiles[] = { {"Upload.cgi", _callback_CGI_UploadFile { NULL, NULL } }; }, If an entry can be found, the specified callback function will be called. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 354 CHAPTER 17 Web server (Add-on) The callback function for the file Upload.cgi is defined as follow: /********************************************************************* * * Static data * ********************************************************************** */ /********************************************************************* * * _callback_CGI_UploadFile */ static void _callback_CGI_UploadFile(WEBS_OUTPUT * pOutput, const char * sParameters) { int r; const char * pFileName; int FileNameLen; const char * pState; // Can be 0: Upload failed; 1: Upload succeeded; Therefore we do not need to know the length, it will always be 1. IP_WEBS_SendString(pOutput, "<HTML><BODY>"); r = IP_WEBS_GetParaValuePtr(sParameters, 0, NULL, 0, &pFileName, &FileNameLen); r |= IP_WEBS_GetParaValuePtr(sParameters, 1, NULL, 0, &pState , NULL); if (r == 0) { IP_WEBS_SendString(pOutput, "Upload of \""); IP_WEBS_SendMem(pOutput, pFileName, FileNameLen); if (*pState == '1') { IP_WEBS_SendString(pOutput, "\" successful!<br>"); IP_WEBS_SendString(pOutput, "<a href=\""); IP_WEBS_SendMem(pOutput, pFileName, FileNameLen); IP_WEBS_SendString(pOutput, "\">Go to "); IP_WEBS_SendMem(pOutput, pFileName, FileNameLen); IP_WEBS_SendString(pOutput, "</a><br>"); } else { IP_WEBS_SendString(pOutput, "\" not successful!<br>"); } } else { IP_WEBS_SendString(pOutput, "Upload not successful!"); } IP_WEBS_SendString(pOutput, "</BODY></HTML>"); } In addition to the provided form fields from the upload form used two additional entries will be added to the end of the parameter list available for parsing: * * The original filename of the file uploaded The status of the upload process. This can be 0: Upload failed or 1: Upload succeeded. The example web page shows after the upload has been finished. The source of the web page as seen by the web browser is listed below: <HTML><BODY> Upload of "1.gif" successful!<br> <a href="1.gif">Go to 1.gif</a><br> </BODY></HTML> UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 355 17.10 Configuration The embOS/IP web server can be used without changing any of the compile time flags. All compile time configuration flags are preconfigured with valid values, which match the requirements of most applications. The following types of configuration macros exist: Binary switches "B" Switches can have a value of either 0 or 1, for deactivated and activated respectively. Actually, anything other than 0 works, but 1 makes it easier to read a configuration file. These switches can enable or disable a certain functionality or behavior. Switches are the simplest form of configuration macros. Numerical values "N" Numerical values are used somewhere in the source code in place of a numerical constant. A typical example is the configuration of the sector size of a storage medium. Alias "A" A macro which operates like a simple text substitute. An example would be the define U8, which the preprocessor would replace with unsigned char. Function replacements "F" Macros can basically be treated like regular functions although certain limitations apply, as a macro is still put into the source code as simple text replacement. Function replacements are mainly used to add specific functionality to a module which is highly hardware-dependent. This type of macro is always declared using brackets (and optional parameters). 17.10.1 Compile time configuration switches Type Symbolic name Default F WEBS_WARN -- F WEBS_LOG -- N WEBS_IN_BUFFER_SIZE 512 N WEBS_OUT_BUFFER_SIZE 512 N WEBS_PARA_BUFFER_SIZE 256 N WEBS_TEMP_BUFFER_SIZE 256 N WEBS_AUTH_BUFFER_SIZE 32 UM07001 User & Reference Guide for embOS/IP Description Defines a function to output warnings. In debug configurations (DEBUG == 1) WEBS_WARN maps to IP_Warnf_Application(). Defines a function to output logging messages. In debug configurations (DEBUG == 1) WEBS_LOG maps to IP_Logf_Application(). Defines the size of the input buffer. The input buffer is used to store the HTTP client requests. Defines the size of the output buffer. The output buffer is used to store the HTTP response. Defines the size of the buffer used to store the parameter/value string that is given to a virtual file. If virtual files are not used in your application, remove the definition from WEBS_Conf.h to save RAM. Defines the size of the TEMP buffer used internally by the web server. Defines the size of the buffer used to store the authentication string. Refer to Authentication on page 346 for detailed information about authentication. (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 356 CHAPTER 17 Type Symbolic name Web server (Add-on) Default N WEBS_FILENAME_BUFFER_SIZE 32 B WEBS_SUPPORT_UPLOAD 0/1 N WEBS_URI_BUFFER_SIZE 0 Description Defines the size of the buffer used to store the filename strings. Defines if file upload is enabled. Defaults to 0: Not enabled, for source code shipments and 1: Enabled, for object shipments. Defines the size of the buffer used to store the "full URI" of the accessed resource. By default this feature is disabled. Status message web pages The status message web pages are visualizations of the information transmitted to the client in the header of the web server response. Because these visualizations are not required for the functionality of the web server, the macros can be empty. Type Symbolic name A WEBS_401_PAGE A WEBS_404_PAGE A WEBS_501_PAGE A WEBS_503_PAGE Default "<HTML>\n" \ "<HEAD>\n" \ "<TITLE>401 Unauthorized</TITLE>\n" \ </HEAD>\n" \ "<BODY>\n" \ "<H1>401 Unauthorized</H1>\n" \ "Browser not authentication-capable" \ "or authentication failed.\n" \ "</BODY>\n" \ "</HTML>\n" "<HTML>\n" \ "<HEAD>\n" \ "<TITLE>404 Not Found</TITLE>\n" \ </HEAD>\n" \ "<BODY>\n" \ "<H1>404 Not Found</H1>\n" \ "The requested document was not " \ "found on this server.\n" \ "</BODY>\n" \ "</HTML>\n" "<HTML>\n" \ "<HEAD>\n" \ "<TITLE>501 Not implemented</TITLE>\n" \ </HEAD>\n" \ "<BODY>\n" \ "<H1>Command is not implemented</H1>\n" \ "</BODY>\n" \ "</HTML>\n" "<HTML>\n" \ "<HEAD>\n" \ "<TITLE>503 Connection limit reached</TITLE>\n" \ </HEAD>\n" \ "<BODY>\n" \ "<H1>503 Connection limit reached</H1>\n" \ "The max. number of simultaneous connections to " \ "this server reached.<P>\n" \ "Please try again later.\n" \ "</BODY>\n" \ "</HTML>\n" UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 357 17.11 API functions Function Description Processes a HTTP request of a client. Processes a HTTP request of a client and IP_WEBS_ProcessLast() closes the connection thereafter. Outputs an error message to the conIP_WEBS_OnConnectionLimit() nected client. IP_WEBS_SendMem() Sends data to a connected target. IP_WEBS_SendString() Sends a string to a connected target. Encodes and sends a string to a conIP_WEBS_SendStringEnc() nected target. Sends an unsigned value to a connected IP_WEBS_SendUnsigned() target. Sets a callback function to handle file IP_WEBS_SetFileInfoCallback() information used by the web server. Retrieves a previously stored user conIP_WEBS_RetrieveUserContext() text from the current connection context. Saves an user context into the current IP_WEBS_StoreUserContext() connection context. Adds a new file name extension to MIME IP_WEBS_AddFileTypeHook() type correlation. Configures automatic sending of a header IP_WEBS_ConfigSendVFileHeader() based on the file name for virtual files. Configures automatic sending of a header IP_WEBS_ConfigSendVFileHookHeader() based on the file name for VFile hooks. Redirect to a file on filesystem by sendIP_WEBS_Redirect() ing its content. IP_WEBS_Reset() Resets internal structures. IP_WEBS_SendHeader() Sends a header with data provided. CGI/virtual file related functions IP_WEBS_CompareFileNameExt() Checks the file name extension. Returns the number of parameter/value IP_WEBS_GetNumParas() pairs. IP_WEBS_GetParaValue() Gets a parameter value pair. Gets a parameter value pairs pointers for IP_WEBS_GetParaValuePtr() further processing. Returns the length of a HTML encoded IP_WEBS_GetDecodedStrLen() string after decoding. Returns the URI of the accessed IP_WEBS_GetURI() resource. Decodes an HTML encoded string and IP_WEBS_DecodeAndCopyStr() copy it into a buffer. IP_WEBS_DecodeString() Decodes an HTML encoded string. IP_WEBS_AddVFileHook() Adds a hook to serve a simple virtual file. METHOD extension related functions IP_WEBS_METHOD_AddHook() Adds a new METHOD hook. Retrieves data sent from within a IP_WEBS_METHOD_CopyData() METHOD hook callback. Utility functions IP_UTIL_BASE64_Decode() Decodes a Base64 encoded string. IP_UTIL_BASE64_Encode() Encodes a string as a Base64 string. IP_WEBS_Process() Table 17.3: embOS/IP web server interface function overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 358 CHAPTER 17 Web server (Add-on) 17.11.1 IP_WEBS_Process() Description Processes a HTTP request of a client. Prototype int IP_WEBS_Process ( IP_WEBS_tSend pfSend, IP_WEBS_tReceive pfReceive, void * pConnectInfo, const IP_WEBS_FS_API * pFS_API const WEBS_APPLICATION * pApplication); Parameter Parameter pfSend pfReceive pConnectInfo pFS_API pApplication Description [IN] Pointer to the function to be used by the server to send data to the client. [IN] Pointer to the function to be used by the server to receive data from the client. [IN] Pointer to the connection information. [IN] Pointer to the used file system API. [IN] Pointer to a structure of type WEBS_APPLICATION. Table 17.4: IP_WEBS_Process() parameter list Return value 0 OK. Additional Information This function is part of the thread functionality of the web server. The following types are used as function pointers to the routines used to send and receive bytes from/to the client: typedef int (*IP_WEBS_tSend) (const unsigned char * pData, int len, void * pConnectInfo); typedef int (*IP_WEBS_tReceive) (const unsigned char * pData, int len, void * pConnectInfo); The send and receive functions should return the number of bytes successfully sent/ received to/from the client. The pointer pConnectInfo is passed to the send and receive routines. It can be used to pass a pointer to a structure containing connection information or to pass a socket number. For details about the parameter pFS_API and the IP_WEBS_FS_API structure, refer to File system abstraction layer on page 564. For details about the parameter pApplication and the WEBS_APPLICATION structure, refer to Structure WEBS_APPLICATION on page 395. Refer to IP_WEBS_ProcessLast() on page 359 and IP_WEBS_OnConnectionLimit() on page 360 for further information. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 359 17.11.2 IP_WEBS_ProcessLast() Description Processes a HTTP request of a client and closes the connection thereafter. Prototype int IP_WEBS_Process ( IP_WEBS_tSend pfSend, IP_WEBS_tReceive pfReceive, void * pConnectInfo, const IP_WEBS_FS_API * pFS_API const WEBS_APPLICATION * pApplication); Parameter Parameter pfSend pfReceive pConnectInfo pFS_API pApplication Description [IN] Pointer to the function to be used by the server to send data to the client. [IN] Pointer to the function to be used by the server to receive data from the client. [IN] Pointer to the connection information. [IN] Pointer to the used file system API. [IN] Pointer to a structure of type WEBS_APPLICATION. Table 17.5: IP_WEBS_Process() parameter list Return value 0 OK. Additional Information This function is part of the thread functionality of the web server. This is typically called for the last available connection. In contrast to IP_WEBS_Process(), this function closes the connection as soon as the command is completed in order to not block the last connection longer than necessary and avoid connection-limit errors. The following types are used as function pointers to the routines used to send and receive bytes from/to the client: typedef int (*IP_WEBS_tSend) (const unsigned char * pData, int len, void * pConnectInfo); typedef int (*IP_WEBS_tReceive) (const unsigned char * pData, int len, void * pConnectInfo); The send and receive functions should return the number of bytes successfully sent/ received to/from the client. The pointer pConnectInfo is passed to the send and receive routines. It can be used to pass a pointer to a structure containing connection information or to pass a socket number. For details about the parameter pFS_API and the IP_WEBS_FS_API structure, refer to File system abstraction layer on page 564. For details about the parameter pApplication and the WEBS_APPLICATION structure, refer to Structure WEBS_APPLICATION on page 395. Refer to IP_WEBS_Process() on page 358 and IP_WEBS_OnConnectionLimit() on page 360 for further information. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 360 CHAPTER 17 Web server (Add-on) 17.11.3 IP_WEBS_OnConnectionLimit() Description Outputs an error message to the connected client. Prototype void IP_WEBS_OnConnectionLimit( const IP_WEBS_API * pIP_API, void * CtrlSock ); Parameter Parameter pIP_API CtrlSock Description [IN] Pointer to a structure of type IP_FTPS_API. [IN] Pointer to the socket which is related to the command connection. Table 17.6: IP_WEBS_OnConnectionLimit() parameter list Additional information This function is typically called by the application if the connection limit is reached. The structure type IP_WEBS_API contains mappings of the required socket functions to the actual IP stack. This is required because the socket functions are slightly different on different systems. Refer to IP_WEBS_Process() on page 358 and IP_WEBS_ProcessLast() on page 359 for further information. Example Pseudo code: // // Call IP_WEBS_Process() or IP_WEBS_ProcessLast() if multiple or just // one more connection is available // do { if (NumAvailableConnections > 1) { IP_WEBS_Process(); return; } else if (NumAvailableConnections == 1) { IP_WEBS_ProcessLast(); return; } Delay(); } while (!Timeout) // // No connection available even after waiting => Output error message // IP_WEBS_OnConnectionLimit(); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 361 17.11.4 IP_WEBS_SendMem() Description Sends data to a connected target. Prototype int IP_WEBS_SendMem ( WEBS_OUTPUT * pOutput, const char * s, unsigned NumBytes); Parameter Parameter pOutput s NumBytes Description [IN] Pointer to the WEBS_OUTPUT structure. [IN] Pointer to a memory location that should be transmitted. [IN] Number of bytes that should be sent. Table 17.7: IP_WEBS_SendMem() parameter list Return value 0 OK. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 362 CHAPTER 17 Web server (Add-on) 17.11.5 IP_WEBS_SendString() Description Sends a zero-terminated string to a connected target. Prototype int IP_WEBS_SendString( WEBS_OUTPUT * pOutput, const char * s); Parameter Parameter pOutput s Description [IN] Pointer to the WEBS_OUTPUT structure. [IN] Pointer to a string that should be transmitted. Table 17.8: IP_WEBS_SendString() parameter list Return value 0 OK. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 363 17.11.6 IP_WEBS_SendStringEnc() Description Encodes and sends a zero-terminated string to a connected target. Prototype int IP_WEBS_SendString( WEBS_OUTPUT * pOutput, const char * s); Parameter Parameter pOutput s Description [IN] Pointer to the WEBS_OUTPUT structure. [IN] Pointer to a string that should be transmitted. Table 17.9: IP_WEBS_SendStringEnc() parameter list Return value 0 OK. Additional information This function encodes the string s with URL encoding, which means that spaces are changed into "+" and special characters are encoded to hexadecimal values. Refer to [RFC 1738] for detailed information about URL encoding. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 364 CHAPTER 17 Web server (Add-on) 17.11.7 IP_WEBS_SendUnsigned() Description Sends an unsigned value to the client. Prototype int IP_WEBS_SendUnsigned ( WEBS_OUTPUT * pOutput, unsigned v, unsigned Base, int NumDigits ); Parameter Parameter pOutput s Base NumDigits Description [IN] Pointer to the WEBS_OUTPUT structure. [IN] Value that should be sent. [IN] Numerical base. [IN] Number of digits that should be sent. 0 can be used as a wildcard. Table 17.10: IP_WEBS_SendUnsigned() parameter list Return value 0 OK. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 365 17.11.8 IP_WEBS_SetFileInfoCallback() Description Sets a callback function to receive the file information which are used by the stack. Prototype void IP_WEBS_SetFileInfoCallback ( IP_WEBS_pfGetFileInfo pf ); Parameter Parameter pf Description [IN] Pointer to a callback function. Table 17.11: IP_WEBS_SetFileInfoCallback() parameter list Additional information The function can be used to change the default behavior of the web server. If the file info callback function is set, the web server calls it to retrieve the file information. The file information are used to decide how to handle the file and to build the HTML header. By default (no file info callback function is set), the web server parses every file with the extension.htm to check if dynamic content is included; all requested files with the extension .cgi are recognized as virtual files. Beside of that, the web server sends by default the expiration date of a web site in the HTML header. The default expiration date (THU, 01 JAN 1995 00:00:00 GMT) is in the past, so that the requested website will never be cached. This is a reasonable default for web pages with dynamic content. If the callback function returns 0 for DateExp, the expiration date will not be included in the header. For static websites, it is possible to add the optional "Last-Modified" header field. The "Last-Modified" header field is not part of the header by default. Refer to Structure IP_WEBS_FILE_INFO on page 396 for detailed information about the structure IP_WEBS_FILE_INFO. Example static void _GetFileInfo(const char * sFilename, IP_WEBS_FILE_INFO * pFileInfo){ int v; // // .cgi files are virtual, everything else is not // v = IP_WEBS_CompareFilenameExt(sFilename, ".cgi"); pFileInfo->IsVirtual = v ? 0 : 1; // // .htm files contain dynamic content, everything else is not // v = IP_WEBS_CompareFilenameExt(sFilename, ".htm"); pFileInfo->AllowDynContent = v ? 0 : 1; // // If file is a virtual file or includes dynamic content, // get current time and date stamp as file time // pFileInfo->DateLastMod = _GetTimeDate(); if (pFileInfo->IsVirtual || pFileInfo->AllowDynContent) { // // Set last-modified and expiration time and date // pFileInfo->DateExp = _GetTimeDate(); // If "Expires" HTTP header field should // be transmitted, set expiration date. } else { pFileInfo->DateExp = 0xEE210000; // Expiration far away (01 Jan 2099) // if content is static } } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 366 CHAPTER 17 Web server (Add-on) 17.11.9 IP_WEBS_RetrieveUserContext() Description Retrieves a previously stored user context from connection context. Prototype void * IP_WEBS_RetrieveUserContext ( WEBS_OUTPUT *pOutput ); Parameter Parameter pOutput Description [IN] Connection context passed to callback. Table 17.12: IP_WEBS_RetrieveUserContext() parameter list Return value Previously stored data. Additional information A user context retrieved will not reset the stored context. The user stored context remains valid until either set to NULL by the user or the connection being closed. In case a browser reuses an already opened connection the user context is not reset. This can be used to identify a connection reuse or to exchange data within the same connection. It is user responsibility to make sure that the user context is set back to NULL by the last callback if this behavior is not desired. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 367 17.11.10IP_WEBS_StoreUserContext() Description Stores a user context into the connection context for using it across several callbacks. Prototype void IP_WEBS_StoreUserContext ( WEBS_OUTPUT *pOutput, void *pContext ); Parameter Parameter pOutput pContext Description [IN] Connection context passed to callback. [IN] Pointer to store. Table 17.13: IP_WEBS_StoreUserContext() parameter list Additional information Sometimes it might be necessary to exchange information between several callbacks that will be called one after another when a website is processed or form data is submitted. The user can use this mechanism to store data into the current connection context in one callback and retrieve the data from another callback of the same connection. Callbacks such as CGIs will be called in the order they are referenced by the web page. Therefore the order of their accesses is known and can be used in dynamic memory allocation. A sample using pseudo code is shown below. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 368 CHAPTER 17 Web server (Add-on) Examples /********************************************************************* * * _CGI_1 * * Notes * This is the first callback accessed for the operation requested * by the browser. This is a perfect place to allocate some memory. */ static void _CGI_1(WEBS_OUTPUT *pOutput, const char *sParameters, const char *sValue) { char *s; s = (char*)OS_malloc(13); strcpy(s, "Hello world!"); IP_WEBS_StoreUserContext(pOutput, (void*)s); // // // // // // Allocate memory for data as data has to remain valid outside of this routine. Fill with data Store pointer to text for other callback to access. } /********************************************************************* * * _CGI_2 * * Notes * This is the last callback accessed for the operation requested * by the browser. This is a perfect place to free the previously * allocated memory. */ static void _CGI_2(WEBS_OUTPUT *pOutput, const char *sParameters, const char *sValue) { char *s; s = (char*)IP_WEBS_RetrieveUserContext(pOutput); printf("%s", s); IP_WEBS_StoreUserContext(pOutput, NULL); OS_free((void*)s); // // // // // Retrieve previously stored data. Output data. Invalidate user context. Free allocated memory. } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 369 17.11.11IP_WEBS_AddFileTypeHook() Description Registers an element of type WEBS_FILE_TYPE_HOOK to extend or override the list of file extension to MIME type correlation. Prototype void IP_WEBS_AddFileTypeHook ( WEBS_FILE_TYPE_HOOK * pHook, const char * sExt, const char * sContent ); Parameter Parameter pHook sExt sContent Description [IN] Pointer to an element of type WEBS_FILE_TYPE_HOOK. [IN] String containing the extension without leading dot. [IN] String containing the MIME type associated to the extension. Table 17.14: IP_WEBS_AddFileTypeHook() parameter list Additional information The function can be used to extend or override the basic list of file extension to MIME type correlations included in the Web server. It might be necessary to extend the this list in case you want to serve a yet unkown file format. The header sent for this file in case a client reuqests it will be generated based on this information. Refer to Structure WEBS_FILE_TYPE_HOOK on page 400 for detailed information about the structure WEBS_FILE_TYPE_HOOK. Example static WEBS_FILE_TYPE_HOOK _FileTypeHook; int main(void){ // // Register *.new files to be treated as binary that will // be offered to be downloaded by the browser. // IP_WEBS_AddFileTypeHook(&_FileTypeHook, "new", "application/octet-stream"); } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 370 CHAPTER 17 Web server (Add-on) 17.11.12IP_WEBS_ConfigSendVFileHeader() Description Configures behavior of automatically sending a header containing a MIME type associated to the requested files extension based on an internal list for a requested virtual file. Prototype void IP_WEBS_ConfigSendVFileHeader ( U8 OnOff ); Parameter Parameter OnOff Description [IN] 0: Off, header will not be automatically generated and sent. 1: On, header will be automatically generated. Default: On. Table 17.15: IP_WEBS_ConfigSendVFileHeader() parameter list Additional information In case you decide not to let the Web server generate a header with the best content believed to be known you will either have to completely send a header on your own or sending a header using the function IP_WEBS_SendHeader() on page 374. Sending a header has to be done before sending any other content. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 371 17.11.13IP_WEBS_ConfigSendVFileHookHeader() Description Configures behavior of automatically sending a header containing a MIME type associated to the requested files extension based on an internal list for a requested file being served by a registered VFile hook. Prototype void IP_WEBS_ConfigSendVFileHookHeader ( U8 OnOff ); Parameter Parameter OnOff Description [IN] 0: Off, header will not be automatically generated and sent. 1: On, header will be automatically generated. Default: On. Table 17.16: IP_WEBS_ConfigSendVFileHookHeader() parameter list Additional information In case you decide not to let the Web server generate a header with the best content believed to be known you will either have to completely send a header on your own or sending a header using the function IP_WEBS_SendHeader() on page 374. Sending a header has to be done before sending any other content. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 372 CHAPTER 17 Web server (Add-on) 17.11.14IP_WEBS_Redirect() Description This routine can send the content of a file from a filesystem instead of having to send a redirect page first. Prototype int IP_WEBS_Redirect ( WEBS_OUTPUT *pOutput, const char *sFileName, const char *sMIMEType ); Parameter Parameter pOutput sFileName sMIMEType Description [IN] Connection context passed to callback. [IN] Path of file to send. [IN] MIME type to use instead of automatically detected MIME type based on file name. Can be NULL. Table 17.17: IP_WEBS_Redirect() parameter list Return value < 0: Error 0: O.K. Additional information The function shall only be called if no other data has been sent out before. The page that will be sent is parsed for CGIs the same way as it would be parsed when being directly being accessed by the browser. However the URL accessed by the browser will remain the same and the browser will show the same URL as address. Example /********************************************************************* * * _CGI_Redirect */ static void _CGI_Redirect(WEBS_OUTPUT *pOutput, const char *sParameters) { IP_WEBS_Redirect(pOutput, "/index.htm", NULL); // Redirect back to index } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 373 17.11.15IP_WEBS_Reset() Description This routine resets internal structures of the Web Server. Prototype void IP_WEBS_Reset ( void ); Additional information As the Web Server is not directly connected to the IP stack itself it can not register to the IP stacks de-initialize process. Once the stack has been de-initialized this routine shall be called before re-initializing the IP stack and using the Web Server again. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 374 CHAPTER 17 Web server (Add-on) 17.11.16IP_WEBS_SendHeader() Description Generates and sends a header based on the information passed to this function. Prototype void IP_WEBS_SendHeader ( WEBS_OUTPUT * pContext, const char * sFileName, const char * sMimeType ); Parameter Parameter pContext sFileName sMimeType Description [IN] Pointer to the context used for sending data from your callback to the client. [IN] String containing the file name including extension to be written to the header. [IN] String containing the MIME type that is sent back in the header. Table 17.18: IP_WEBS_SendHeader() parameter list Additional information This function can be used in case automatically generating and sending a header has been switched off using IP_WEBS_ConfigSendVFileHeader() on page 370 or IP_WEBS_ConfigSendVFileHookHeader() on page 371. Typically this is the first function you call from your callback generating content for a virtual file or a VFile hook registered callback providing content before you send any other data. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 375 17.11.17IP_WEBS_CompareFileNameExt() Description Checks if the given filename has the given extension. Prototype char IP_WEBS_CompareFilenameExt( const char * sFilename, const char * sExt ); Parameter Parameter sFilename sExt Description [IN] Name of the file. [IN] Extension which should be checked. Table 17.19: IP_WEBS_CompareFilenameExt() parameter list Return value 0 Match != 0 Mismatch Additional information The test is case-sensitive, meaning: IP_WEBS_CompareFilenameExt("Index.html", IP_WEBS_CompareFilenameExt("Index.htm", IP_WEBS_CompareFilenameExt("Index.HTML", IP_WEBS_CompareFilenameExt("Index.html", UM07001 User & Reference Guide for embOS/IP ".html") ".html") ".html") ".HTML") ---> ---> ---> ---> Match Mismatch Mismatch Mismatch (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 376 CHAPTER 17 Web server (Add-on) 17.11.18IP_WEBS_GetNumParas() Description Returns the number of parameter/value pairs. Prototype int IP_WEBS_GetNumParas ( const char * sParameters ); Parameter Parameter sParameters Description [IN] Zero-terminated string with parameter/value pairs. Table 17.20: IP_WEBS_GetNumParas() parameter list Return value Number of parameters/value pairs. -1 if the string does not include parameter value pairs. Additional information Parameters are separated from values by a '='. If a string includes more as one parameter/value pair, the parameter/value pairs are separated by a '&'. For example, if the virtual file Send.cgi gets two parameters, the string should be similar to the following: Send.cgi?FirstName=Foo&LastName=Bar sParameter is in this case FirstName=Foo&LastName=Bar. IP_WEBS_GetNumParas() with this string, the return value will be 2. UM07001 User & Reference Guide for embOS/IP If you call (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 377 17.11.19IP_WEBS_GetParaValue() Description Parses a string for valid parameter/value pairs and writes the results in the respective buffers. Prototype int IP_WEBS_GetParaValue( const char * sBuffer, int ParaNum, char * sPara, int ParaLen, char * sValue, int ValueLen ); Parameter Parameter sBuffer ParaNum sPara ParaLen sValue ValueLen Description [IN] Zero-terminated parameter/value string that should be parsed. [IN] Zero-based index of the parameter/value pairs. [Out] Buffer to store the the parameter name. (Optional, can be NULL.) [IN] Size of the buffer to store the parameter. (0 if sPara is NULL.) [Out] Buffer to store the the value. (Optional, can be NULL.) [IN] Size of the buffer to store the value. (0 if sValue is NULL.) Table 17.21: IP_WEBS_GetParaValue() parameter list Return value 0: O.K. >0: Error Additional information A valid string is in the following format: <Param0>=<Value0>&<Param1>=<Value1>& ... <Paramn>=<Valuen> If the parameter value string is FirstName=John&LastName=Doo and parameter 0 should be copied, sPara will be FirstName and sValue John. If parameter 1 should be copied, sPara will be LastName and sValue Doo. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 378 CHAPTER 17 Web server (Add-on) 17.11.20IP_WEBS_GetParaValuePtr() Description Parses a string for valid parameter/value pairs and returns a pointer to the requested paramater and the length of the paramater string without termination. Prototype int IP_WEBS_GetParaValuePtr( const char int const char int const char int * sBuffer, ParaNum, ** ppPara, * pParaLen, ** ppValue, * pValueLen ); Parameter Parameter sBuffer ParaNum ppPara pParaLen ppValue pValueLen Description [IN] Zero-terminated parameter/value string that should be parsed. [IN] Zero-based index of the parameter/value pairs. [Out] Pointer to the pointer locating the start of the requested paramater name. (Optional, can be NULL.) [OUT] Pointer to a buffer to store the length of the parameter name without termination. (Optional, can be NULL.) [Out] Pointer to the pointer locating the start of the requested parameter value. (Optional, can be NULL.) [OUT] Pointer to a buffer to store the length of the parameter value without termination. (Optional, can be NULL.) Table 17.22: IP_WEBS_GetParaValuePtr() parameter list Return value 0: O.K. >0: Error Additional information A valid string is in the following format: <Param0>=<Value0>&<Param1>=<Value1>& ... <Paramn>=<Valuen> This function can be used in case you simply want to check or use the paramaters passed by the client without modyfing them. Depending on your application this might save you a lot of stack that otherwise would have to be wasted for copying the same data that is already perfectly present to another location. This saves execution time as of course the data will not have to be copied. Example /* Excerpt from OS_IP_Webserver.c */ /********************************************************************* * * _callback_CGI_Send */ static void _callback_CGI_Send(WEBS_OUTPUT * pOutput, const char * sParameters) { int r; const char * pFirstName; int FirstNameLen; const char * pLastName; int LastNameLen; IP_WEBS_SendString(pOutput, "<HTML><HEAD><TITLE>Virtual file HEAD>"); IP_WEBS_SendString(pOutput, "<style type=\"text/css\"> \ H1, H2, H3, H4 { color: white; font-family: Helvetica; } \ UM07001 User & Reference Guide for embOS/IP example</TITLE></ (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 379 PRE { color: white; margin-left: 2%; ; font-size=150%} \ BODY{padding:0px; margin:0px; text-align:center; font-family:Verdana, Helvetica, sans-serif; background:#6699CC url(bg.png) repeat-x; font-size:11px; color:white } \ A:link { font-weight:bold; color:white; text-decoration:none; } \ A:visited { font-weight:bold; color:silver; text-decoration:none; } \ A:focus { font-weight:bold; color:white; text-decoration:underline; } \ A:hover { font-weight:bold; color:silver; text-decoration:none; } \ A:active { font-weight:bold; color:white; text-decoration:underline; }\ </style>"); IP_WEBS_SendString(pOutput, "<BODY><CENTER><HR><H2>Virtual file example</H2><HR></ CENTER><BR><BR><BR>"); r = IP_WEBS_GetParaValuePtr(sParameters, 0, NULL, 0, &pFirstName, &FirstNameLen); r |= IP_WEBS_GetParaValuePtr(sParameters, 1, NULL, 0, &pLastName, &LastNameLen); if (r == 0) { IP_WEBS_SendString(pOutput, "First name: "); IP_WEBS_SendMem(pOutput, pFirstName, FirstNameLen); IP_WEBS_SendString(pOutput, "<BR>Last name: "); IP_WEBS_SendMem(pOutput, pLastName, LastNameLen); } else { IP_WEBS_SendString(pOutput, "<BR>Error!"); } IP_WEBS_SendString(pOutput, "<BR><BR><BR>"); IP_WEBS_SendString(pOutput, "<HR><CENTER><A HREF=\"index.htm\">Back to main</A></ CENTER><IMG SRC=\"logo.gif\" ALT=\"Segger logo\">&nbsp;&nbsp; SEGGER Microcontroller GmbH &amp; Co. KG &nbsp;&nbsp;<A HREF=\"http://www.segger.com\">www.segger.com</A></ BODY></HTML>"); } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 380 CHAPTER 17 Web server (Add-on) 17.11.21IP_WEBS_GetDecodedStrLen() Description Returns the length of a HTML encoded string when decoded excluding null character. Prototype int IP_WEBS_GetDecodedStrLen( const char *s, int Len ); Parameter Parameter s Len Description [IN] String. [IN] Length of input string excluding terminating null character. Table 17.23: IP_WEBS_GetDecodedStrLen() parameter list Return value <0: Error >0: Length of decoded string excluding terminating null character. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 381 17.11.22IP_WEBS_GetURI() Description Returns the URI of the accessed resource. Prototype const char* IP_WEBS_GetURI( WEBS_OUTPUT *pOutput, char GetFullURI ); Parameter Parameter pOutput GetFullURI Description [IN] Connection output context. [IN] Switch to select between URI and "full URI". URI contains the resource address up to any delimiter such as '?'. The "full URI" contains the complete resource address accessed up to the next whitespace after the resource address including '?' and following characters. 0: URI 1: "full URI" Table 17.24: IP_WEBS_GetURI() parameter list Return value NULL: In case "full URI" has been selected but is not available. Other: Pointer to URI or "full URI" string. Additional information To support storing the "full URI" the define WEBS_URI_BUFFER_SIZE needs to be set. If it is not set or its size is too small, requesting the "full URI" will always return NULL. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 382 CHAPTER 17 Web server (Add-on) 17.11.23IP_WEBS_DecodeAndCopyStr() Description Checks if a string includes url encoded characters, decodes the characters and copies them into destination buffer. Prototype void IP_WEBS_DecodeAndCopyStr ( char * pDest, int DestLen, const char * pSrc, int SrcLen ); Parameter Parameter pDest DestLen pSrc SrcLen Description [OUT] Buffer to store the decoded string. [IN] Size of the destination buffer. [IN] Source string that should be decoded. [IN] Size of the source string. Table 17.25: IP_WEBS_DecodeAndCopyStr() parameter list Additional information Destination string is 0-terminated. Source and destination buffer can be identical. pSrc "FirstName=J%F6rg" "FirstName=John" SrcLen 16 14 pDest "FirstName=Jorg\0" "FirstName=John\0" DestLen 15 15 Table 17.26: Example UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 383 17.11.24IP_WEBS_DecodeString() Description Checks if a string includes url encoded characters, decodes the characters. Prototype int IP_WEBS_DecodeString( const char * s ); Parameter Parameter s Description [IN/OUT] Zero-terminated string that should be decoded. Table 17.27: IP_WEBS_DecodeString() parameter list Return value 0 String does not include url encoded characters. No change. >0 Length of the decoded string excluding the terminating null character. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 384 CHAPTER 17 Web server (Add-on) 17.11.25IP_WEBS_AddVFileHook() Description Registers a function table containing callbacks to check and serve simple virtual file content that is not further processed by the Web server. Prototype void IP_WEBS_AddVFileHook ( WEBS_VFILE_HOOK *pHook, WEBS_VFILE_APPLICATION *pVFileApp, U8 ForceEncoding ); Parameter Parameter Description [IN] Pointer to an element of type WEBS_VFILE_HOOK. [IN] Pointer to an element of type WEBS_VFILE_APPLICATION. [IN] When set to HTTP_ENCODING_RAW chunked encoding will not ForceEncoding be used. Necessary for some implementations such as UPnP. pHook pVFileApp Table 17.28: IP_WEBS_AddVFileHook() parameter list Additional information The function can be used to serve simple dynamically generated content for a requested file name that is simply sent back as generated by the application and is not further processed by the Web server. Refer to Structure WEBS_VFILE_HOOK on page 398 for detailed information about the structure WEBS_VFILE_HOOK. Refer to Structure WEBS_VFILE_APPLICATION on page 397 for detailed information about the structure WEBS_VFILE_APPLICATION. Example /* Excerpt from OS_IP_Webserver_UPnP.c */ /********************************************************************* * * _UPnP_GenerateSend_upnp_xml * * Function description * Send the content for the requested file using the callback provided. * * Parameters * pContextIn - Send context of the connection processed for * forwarding it to the callback used for output. * pf - Function pointer to the callback that has to be * for sending the content of the VFile. * pContextOut - Out context of the connection processed. * pData - Pointer to the data that will be sent * NumBytes - Number of bytes to send from pData. If NumBytes * is passed as 0 the send function will run a strlen() * on pData expecting a string. * * Notes * (1) The data does not need to be sent in one call of the callback * routine. The data can be sent in blocks of data and will be * flushed out automatically at least once returning from this * routine. */ static void _UPnP_GenerateSend_upnp_xml(void * pContextIn, void (*pf) (void * pContextOut, const char * pData, unsigned NumBytes)) { char ac[128]; pf(pContextIn, "<?xml version=\"1.0\"?>\r\n" "<root xmlns=\"urn:schemas-upnp-org:device-1-0\">\r\n" "<specVersion>\r\n" "<major>1</major>\r\n" UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 385 "<minor>0</minor>\r\n" "</specVersion>\r\n", 0); } /* Excerpt from OS_IP_Webserver_UPnP.c */ // // UPnP webserver VFile hook // static WEBS_VFILE_HOOK _UPnP_VFileHook; /* Excerpt from OS_IP_Webserver_UPnP.c */ /********************************************************************* * * _UPnP_CheckVFile * * Function description * Check if we have content that we can deliver for the requested * file using the VFile hook system. * * Parameters * sFileName - Name of the file that is requested * pIndex - Pointer to a variable that has to be filled with * the index of the entry found in case of using a * filename<=>content list. * Alternative all comparisons can be done using the * filename. In this case the index is meaningless * and does not need to be returned by this routine. * * Return value * 0 - We do not have content to send for this filename, * fall back to the typical methods for retrieving * a file from the web server. * 1 - We have content that can be sent using the VFile * hook system. */ static int _UPnP_CheckVFile(const char * sFileName, unsigned * pIndex) { unsigned i; // // Generated VFiles // if (strcmp(sFileName, "/upnp.xml") == 0) { return 1; } // // Static VFiles // for (i = 0; i < SEGGER_COUNTOF(_VFileList); i++) { if (strcmp(sFileName, _VFileList[i].sFileName) == 0) { *pIndex = i; return 1; } } return 0; } /********************************************************************* * * _UPnP_SendVFile * * Function description * Send the content for the requested file using the callback provided. * * Parameters * pContextIn - Send context of the connection processed for * forwarding it to the callback used for output. * Index - Index of the entry of a filename<=>content list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 386 CHAPTER 17 Web server (Add-on) * if used. Alternative all comparisons can be done * using the filename. In this case the index is * meaningless. If using a filename<=>content list * this is faster than searching again. * sFileName - Name of the file that is requested. In case of * working with the Index this is meaningless. * pf - Function pointer to the callback that has to be * for sending the content of the VFile. * pContextOut - Out context of the connection processed. * pData - Pointer to the data that will be sent * NumBytes - Number of bytes to send from pData. If NumBytes * is passed as 0 the send function will run a strlen() * on pData expecting a string. */ static void _UPnP_SendVFile(void * pContextIn, unsigned Index, const char * sFileName, void (*pf) (void * pContextOut, const char * pData, unsigned NumBytes)) { (void)sFileName; // // Generated VFiles // if (strcmp(sFileName, "/upnp.xml") == 0) { _UPnP_GenerateSend_upnp_xml(pContextIn, pf); return; } // // Static VFiles // pf(pContextIn, _VFileList[Index].pData, _VFileList[Index].NumBytes); } static WEBS_VFILE_APPLICATION _UPnP_VFileAPI = { _UPnP_CheckVFile, _UPnP_SendVFile }; /* Excerpt from OS_IP_Webserver_UPnP.c */ /********************************************************************* * * MainTask */ void MainTask(void); void MainTask(void) { // // Activate UPnP with VFile hook for needed XML files // IP_WEBS_AddVFileHook(&_UPnP_VFileHook, &_UPnP_VFileAPI, HTTP_ENCODING_RAW); } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 387 17.11.26IP_WEBS_METHOD_AddHook() Description Registers a callback to serve special content upon call of a METHOD. Prototype void IP_WEBS_METHOD_AddHook ( WEBS_METHOD_HOOK *pHook, IP_WEBS_pfMethod *pf, const char *sURI ); Parameter Parameter pHook pf sURI Description [IN] Pointer to an element of type WEBS_METHOD_HOOK. [IN] Pointer to a function of type IP_WEBS_pfMethod. [IN] URI to listen for requested method. Table 17.29: IP_WEBS_METHOD_AddHook() parameter list Additional information The function can be used to implement web applications that need to make use of METHODs in a special way such as REST (REpresentational State Transfer) that uses GET and POST in a different way they are typically used by a web server. Refer to Structure WEBS_METHOD_HOOK on page 401 for detailed information about the structure WEBS_METHOD_HOOK. Refer to Callback IP_WEBS_pfMethod on page 402 for detailed information about the callback parameters of IP_WEBS_pfMethod. Typically one URI on the server is used to serve such a special need and this function allows redefining METHODs for a specific URI for such cases. Locations within this URI such as /URI/1 in case /URI has been defined for the hook are served by the hook as well. In case further hooks are placed inside paths of other hooks the hook with the deepest path matching the requested URI will be used. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 388 CHAPTER 17 Web server (Add-on) Example /* Excerpt from OS_IP_Webserver.c */ /********************************************************************* * * _REST_cb * * Function descrition * Callback for demonstrational REST implementation using a METHOD * hook. As there is no clearly defined standard for REST this * implementation shall act as sample and starting point on how * REST support could be implemented by you. * * Parameters * pContext - Context for incoming data * pOutput - Context for outgoing data * sMethod - String containing used METHOD * sAccept - NULL or string containing value of "Accept" field of HTTP header * sContentType - NULL or string containing value of "Content-Type" field of * HTTP header * sResource - String containing URI that was accessed * ContentLen - 0 or length of data submitted by client * * Return value * 0 - O.K. * Other - Error */ static int _REST_cb( void *pContext, WEBS_OUTPUT *pOutput, const char *sMethod, const char *sAccept, const char *sContentType, const char *sResource, U32 ContentLen ) { int Len; char acAccept[128]; char acContentType[32]; // // // // // if Strings located at sAccept and sContentType need to be copied to another location before calling any other Web Server API as they will be overwritten. (sAccept) { _CopyString(acAccept, sAccept, sizeof(acAccept)); } if (sContentType) { _CopyString(acContentType, sContentType, sizeof(acContentType)); } // // Send implementation specific header to client // IP_WEBS_SendHeader(pOutput, NULL, "application/REST"); // // Output information about the METHOD used by the client // IP_WEBS_SendString(pOutput, "METHOD: "); IP_WEBS_SendString(pOutput, sMethod); IP_WEBS_SendString(pOutput, "\n"); // // Output information about which URI has been accessed by the client // IP_WEBS_SendString(pOutput, "URI: "); IP_WEBS_SendString(pOutput, sResource); IP_WEBS_SendString(pOutput, "\n"); // UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 389 // Output information about "Accept" field given in header sent by client, if any // if (sAccept) { IP_WEBS_SendString(pOutput, "Accept: "); IP_WEBS_SendString(pOutput, acAccept); IP_WEBS_SendString(pOutput, "\n"); } // // Output information about "Content-Type" field given in header sent by // client, if any // if (sContentType) { IP_WEBS_SendString(pOutput, "Content-Type: "); IP_WEBS_SendString(pOutput, acContentType); } // // Output content sent by client, or content previously sent by client that has // been saved // if ((_acRestContent[0] || ContentLen) && sContentType) { IP_WEBS_SendString(pOutput, "\n"); } if (_acRestContent[0] || ContentLen) { IP_WEBS_SendString(pOutput, "Content:\n"); } if (ContentLen) { // // Update saved content // Len = SEGGER_MIN(sizeof(_acRestContent) - 1, ContentLen); IP_WEBS_METHOD_CopyData(pContext, _acRestContent, Len); _acRestContent[ContentLen] = 0; } if (_acRestContent[0]) { IP_WEBS_SendString(pOutput, _acRestContent); } return 0; } /********************************************************************* * * MainTask */ void MainTask(void); void MainTask(void) { // // Register URI "http://<ip>/REST" for demonstrational REST implementation // IP_WEBS_METHOD_AddHook(&_MethodHook, _REST_cb, "/REST"); } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 390 CHAPTER 17 Web server (Add-on) 17.11.27IP_WEBS_METHOD_CopyData() Description Requests incoming data for use in a METHOD callback. Prototype int IP_WEBS_METHOD_CopyData ( void *pContext, void *pBuffer, unsigned NumBytes ); Parameter Parameter pContext pBuffer NumBytes Description [IN] METHOD context for incoming data. [OUT] Pointer to buffer where incoming data is stored. [IN] Number of bytes to read. Table 17.30: IP_WEBS_METHOD_CopyData() parameter list Return value <0: Error 0: Connection closed >0: Number of bytes read Additional information The function can be used to implement web applications that need to make use of METHODs in a special way such as REST (REpresentational State Transfer) that uses GET and POST in a different way they are typically used by a web server. Refer to Structure WEBS_METHOD_HOOK on page 401 for detailed information about the structure WEBS_METHOD_HOOK. Refer to Callback IP_WEBS_pfMethod on page 402 for detailed information about the callback parameters of IP_WEBS_pfMethod. Typically one URI on the server is used to serve such a special need and this function allows redefining METHODs for a specific URI for such cases. Locations within this URI such as /URI/1 in case /URI has been defined for the hook are served by the hook as well. In case further hooks are placed inside paths of other hooks the hook with the deepest path matching the requested URI will be used. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 391 17.11.28IP_UTIL_BASE64_Decode() Description Performs BASE-64 decoding according to RFC3548. Prototype int IP_UTIL_BASE64_Decode( const U8 * pSrc, int SrcLen, U8 * pDest, int * pDestLen ); Parameter Parameter pSrc SrcLen pDest pDestLen Description [IN] Pointer to data to encode. Number of bytes to encode. [IN] Pointer to the destination buffer. [IN] Pointer to the destination buffer size. [OUT] Pointer to the number of bytes used in the destination buffer. Table 17.31: IP_UTIL_BASE64_Decode() parameter list Return value < 0 > 0 0 Error Number of source bytes encoded, further call required All bytes encoded Additional information For more information, refer to http://tools.ietf.org/html/rfc3548. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 392 CHAPTER 17 Web server (Add-on) 17.11.29IP_UTIL_BASE64_Encode() Description Performs BASE-64 encoding according to RFC3548. Prototype int IP_UTIL_BASE64_Encode( const U8 * pSrc, int SrcLen, U8 * pDest, int * pDestLen ); Parameter Parameter pSrc SrcLen pDest pDestLen Description [IN] Pointer to data to encode. Number of bytes to encode. [IN] Pointer to the destination buffer. [IN] Pointer to the destination buffer size. [OUT] Pointer to the number of bytes used in the destination buffer. Table 17.32: IP_UTIL_BASE64_Encode() parameter list Return value < 0 > 0 0 Error Number of source bytes encoded, further call required All bytes encoded Additional information For more information, refer to http://tools.ietf.org/html/rfc3548. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 393 17.12 Web server data structures 17.12.1 Structure WEBS_CGI Description Used to store the CGI command names and the pointer to the proper callback functions. Prototype typedef struct { const char * sName; void (*pf)(WEBS_OUTPUT * pOutput, const char * sParameters); } WEBS_CGI; Member sName pf Description Name of the CGI command. Pointer to a callback function. Table 17.33: Structure WEBS_CGI member list Additional information Refer to Common Gateway Interface (CGI) on page 342 for detailed information about the use of this structure. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 394 CHAPTER 17 Web server (Add-on) 17.12.2 Structure WEBS_ACCESS_CONTROL Description Used to store information for the HTTP Basic Authentication scheme. Prototype typedef struct { const char * sPath; const char * sRealm; const char * sUserPass; } WEBS_ACCESS_CONTROL; Member sPath sRealm sUserPass Description A string which defines the path of the resources. A string which defines the realm which requires authentication. Optional, can be NULL. A string containing the user name/password combination. Optional, can be NULL. Table 17.34: Structure WEBS_ACCESS_CONTROL member list Additional information If sRealm is initialized with NULL, sUserPass is not interpreted by the web server. Refer to Authentication on page 346 for detailed information about the HTTP Basic Authentication scheme. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 395 17.12.3 Structure WEBS_APPLICATION Description Used to store application-specific parameters. Prototype typedef struct { const WEBS_CGI * paCGI; WEBS_ACCESS_CONTROL * paAccess; void (*pfHandleParameter)( WEBS_OUTPUT * pOutput, const char sPara, const char * sValue ); } WEBS_APPLICATION; Member paCGI paAccess pfHandleParameter Description Pointer to an array of structures of type WEBS_CGI. Pointer to an array of structures of type WEBS_ACCESS_CONTROL. Pointer to an array of structures of type WEBS_CGI. Table 17.35: Structure WEBS_APPLICATION member list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 396 CHAPTER 17 Web server (Add-on) 17.12.4 Structure IP_WEBS_FILE_INFO Description Used to store application-specific parameters. Prototype typedef struct { U32 DateLastMod; U32 DateExp; U8 IsVirtual; U8 AllowDynContent; } IP_WEBS_FILE_INFO; // Used for "Last modified" header field // Used for "Expires" header field Member DateLastModified DateExp IsVirtual AllowDynContent Description The date when the file has been last modified. The date of the expiration of the valiity. Flag to indicate if a file is virtual or not. Valid values are 0 for non-virtual, 1 for virtual files. Flag to indicate if a file should be parsed for dynamic content or not. 0 means that the file should not be parsed for dynamic content, 1 means that the file should be parsed for dynamic content. Table 17.36: Structure IP_WEBS_FILE_INFO member list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 397 17.12.5 Structure WEBS_VFILE_APPLICATION Description Used to check if the application can provide content for a simple VFile. Prototype typedef struct WEBS_VFILE_APPLICATION { int (*pfCheckVFile)(const char * sFileName, unsigned * pIndex); void (*pfSendVFile) (void * pContextIn, unsigned Index, const char * sFileName, void (*pf) (void * pContextOut, const char * pData, unsigned NumBytes)); } WEBS_VFILE_APPLICATION; Member pfCheckVFile pfSendVFile Description Pointer to a callback for checking if content for a requested file name can be served. Pointer to a callback for actually sending the content for the requested file name using the provided callback pf. In case NumBytes is passed with '0' the callback expects to find a string and will automatically run strlen() to find out the length of the string internally. In case NumBytes is not passed '>0' only NumBytes from the start of pData will be sent. Table 17.37: Structure WEBS_VFILE_APPLICATION member list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 398 CHAPTER 17 Web server (Add-on) 17.12.6 Structure WEBS_VFILE_HOOK Description Used to send application generated content from the application upon request of a specific file name. Prototype typedef struct WEBS_VFILE_HOOK { struct WEBS_VFILE_HOOK * pNext; WEBS_VFILE_APPLICATION * pVFileApp; } WEBS_VFILE_HOOK; Member pNext pVFileApp Description Pointer to the previously registered element of WEBS_VFILE_HOOK. Pointer to an element of type WEBS_VFILE_APPLICATION. Table 17.38: Structure WEBS_VFILE_HOOK member list Additional information Refer to Structure WEBS_VFILE_HOOK on page 398 for detailed information about the structure WEBS_VFILE_HOOK. Refer to Structure WEBS_VFILE_APPLICATION on page 397 for detailed information about the structure WEBS_VFILE_APPLICATION. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 399 17.12.7 Structure WEBS_FILE_TYPE Description Used to extend or overwrite the file extension to MIME type correlation. Prototype typedef struct WEBS_FILE_TYPE { const char *sExt; const char *sContent; } WEBS_FILE_TYPE; Member sExt sContent Description String containing the extension without leading dot. String containing the MIME type associated to the extension. Table 17.39: Structure WEBS_FILE_TYPE member list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 400 CHAPTER 17 Web server (Add-on) 17.12.8 Structure WEBS_FILE_TYPE_HOOK Description Used to extend or overwrite the file extension to MIME type correlation. Prototype typedef struct WEBS_FILE_TYPE_HOOK { struct WEBS_FILE_TYPE_HOOK * pNext; WEBS_FILE_TYPE FileType; } WEBS_FILE_TYPE_HOOK; Member pNext FileType Description Pointer to the previously registered element of WEBS_FILE_TYPE_HOOK. Element of Structure WEBS_FILE_TYPE. Table 17.40: Structure WEBS_VFILE_HOOK member list Additional information Refer to Structure WEBS_FILE_TYPE_HOOK on page 400 for detailed information about the structure WEBS_FILE_TYPE_HOOK. Refer to Structure WEBS_FILE_TYPE on page 399 for detailed information about the structure WEBS_FILE_TYPE. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 401 17.12.9 Structure WEBS_METHOD_HOOK Description Used to extend the usage of METHODs in the web server for a given URI. Prototype typedef struct WEBS_METHOD_HOOK { struct WEBS_METHOD_HOOK *pNext; IP_WEBS_pfMethod pf; const char *sURI; } WEBS_FILE_TYPE_HOOK; Member pNext pf sURI Description Pointer to the previously registered element of WEBS_METHOD_HOOK. Pointer to callback handling the requested method of type Callback IP_WEBS_pfMethod. URI registered for METHODs callback. Table 17.41: Structure WEBS_METHOD_HOOK member list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 402 CHAPTER 17 Web server (Add-on) 17.12.10Callback IP_WEBS_pfMethod Description Used to extend the usage of METHODs in the web server for a given URI. Prototype typedef int (*IP_WEBS_pfMethod) ( const const const const Member pContext pOutput sMethod sAccept sContentType sResource ContentLen void WEBS_OUTPUT char char char char U32 *pContext, *pOutput, *sMethod, *sAccept, *sContentType, *sResource, ContentLen ); Description [IN] METHOD context for incoming data used with IP_WEBS_METHOD_* routines. [IN] Output context for IP_WEBS_* routines. [IN] String containing METHOD requested by client. [IN] String containing value of "Accept" field of header sent by client. May be NULL in case there was no such field. [IN] String containing value of "Content-Type" field of header sent by client. May be NULL in case there was no such field. String contanining URI that was accessed. Length of data submitted by client that can be read. 0 in case no data was sent by client. Table 17.42: Callback IP_WEBS_pfMethod parameter list Warning: Strings located at sAccept and sContentType need to be copied to another location before calling any other Web Server API as they will be overwritten. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 403 17.13 Resource usage The ROM usage depends on the compiler options, the compiler version and the used CPU. The memory requirements of the web server presented in the tables below have been measured on an ARM7 and a Cortex-M3 system. Details about the further configuration can be found in the sections of the specific example. Configuration used #define #define #define #define #define #define #define #define WEBS_IN_BUFFER_SIZE WEBS_OUT_BUFFER_SIZE WEBS_TEMP_BUFFER_SIZE WEBS_PARA_BUFFER_SIZE WEBS_ERR_BUFFER_SIZE WEBS_AUTH_BUFFER_SIZE WEBS_FILENAME_BUFFER_SIZE WEBS_UPLOAD_FILENAME_BUFFER_SIZE 256 512 512 256 128 32 32 64 17.13.1 ROM usage on an ARM7 system The following resource usage has been measured on an ARM7 system using IAR Embedded Workbench V6.30.6, Thumb mode, no interwork, size optimization. Addon ROM embOS/IP Web server approximately 7.0Kbyte Table 17.43: Web server ROM usage ARM7 17.13.2 ROM usage on a Cortex-M3 system The following resource usage has been measured on a Cortex-M3 system using IAR Embedded Workbench V6.30.6, size optimization. Addon ROM embOS/IP Web server approximately 6.5Kbyte Table 17.44: Web server ROM usage Cortex-M3 17.13.3 RAM usage: Almost all of the RAM used by the web server is taken from task stacks. The amount of RAM required for every child task depends on the configuration of your server. The table below shows typical RAM requirements for your task stacks. Task Description ParentTask ChildTask RAM Listens for incoming connections. Handles a request. approximately 1000 bytes approximately 3000 bytes Table 17.45: Web server RAM usage Note: The web server requires at least 1 child task. The approximately RAM usage for the web server can be calculated as follows: RAM usage = 0.1 Kbytes + ParentTask + (NumberOfChildTasks * 3 kBytes) Example: Web server accepting only 1 connection RAM usage = 0.1 kBytes + 1000 +(1 * 3 kBytes) RAM usage = 4.1 kBytes Example: Web server accepting up to 3 connections in parallel RAM usage = 0.1 kBytes + 1000 + (3 * 3 kBytes) RAM usage = 10.1 kBytes UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 404 UM07001 User & Reference Guide for embOS/IP CHAPTER 17 Web server (Add-on) (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 405 Chapter 18 SMTP client (Add-on) The embOS/IP SMTP client is an optional extension to embOS/IP. The SMTP client can be used with embOS/IP or with a different TCP/IP stack. All functions that are required to add the SMTP client task to your application are described in this chapter. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 406 CHAPTER 18 SMTP client (Add-on) 18.1 embOS/IP SMTP client The embOS/IP SMTP client is an optional extension which can be seamlessly integrated into your TCP/IP application. It combines a maximum of performance with a small memory footprint. The SMTP client allows an embedded system to send emails with dynamically generated content. The RAM usage of the SMTP client module has been kept to a minimum by smart buffer handling. The SMTP client implements the relevant parts of the following Request For Comments (RFC). RFC# Description Simple Mail Transfer Protocol Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc821.txt Mail routing and the domain system Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc974.txt SMTP Service Extension for Authentication Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc2554.txt Simple Mail Transfer Protocol Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc5321.txt [RFC 821] [RFC 974] [RFC 2554] [RFC 5321] The following table shows the contents of the embOS/IP SMTP client root directory: Directory Content Application\ Contains the example application to run the SMTP client with embOS/IP. Config Contains the SMTP client configuration file. Refer to Configuration on page 411 for detailed information. Inc Contains the required include files. IP Contains the SMTP client sources, IP_SMTPC.c and IP_SMTPC.h. Windows\SMTPC\ Contains the source, the project files and an executable to run embOS/IP SMTP client on a Microsoft Windows host. Supplied directory structure of embOS/IPSMTP client package UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 407 18.2 Feature list * * * * Low memory footprint. Independent of the TCP/IP stack: any stack with sockets can be used. Example applications included. Project for executable on PC for Microsoft Visual Studio included. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 408 CHAPTER 18 SMTP client (Add-on) 18.3 Requirements TCP/IP stack The embOS/IP SMTP client requires a TCP/IP stack. It is optimized for embOS/IP, but any RFC-compliant TCP/IP stack can be used. The shipment includes a Win32 simulation, which uses the standard Winsock API and an implementation which uses the socket API of embOS/IP. Multi tasking The SMTP client needs to run as a separate thread. Therefore, a multi tasking system is required to use the embOS/IP SMTP client. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 409 18.4 SMTP backgrounds The Simple Mail Transfer Protocol is a text based communication protocol for electronic mail transmission across IP networks. Application layer SMTP Transport layer TCP Network layer IP Link layer Ethernet (IEEE 802.3), ... Using SMTP, an embOS/IP application can transfer mail to an SMTP servers on the same network or to SMTP servers in other networks via a relay or gateway server accessible to both networks. When the embOS/IP SMTP client has a message to transmit, it establishes a TCP connection to an SMTP server and transmits after the handshaking the message content. The handshaking mechanism includes normally an authentication process. The RFC's define the following four different authentication schemes: * * * * PLAIN LOGIN CRAM-MD5 NTLM In the current version, the embOS/IP SMTP client supports only PLAIN authentication. The following listing shows a typical SMTP session: S: C: S: C: S: C: S: C: S: C: S: C: S: C: S: C: S: C: S: C: C: C: C: 220 srv.sample.com ESMTP HELO 250 srv.sample.com AUTH LOGIN 334 VXNlcm5hbWU6 c3BzZXk29IulbkY29tZcZXIbtZ 334 UGFzc3dvcmQ6 UlblhFz7ZlblsZlZQ== 235 go ahead Mail from:<user0@sample.com> 250 ok Rcpt to:<user1@sample.com> 250 ok Rcpt to:<user2@sample.com> 250 ok Rcpt to:<user3@sample.com> 250 ok DATA 354 go ahead Message-ID: <1000.2234@sample.com> From: "User0" <User0@sample.com> TO: "User1" <User1@sample.com> CC: "User2" <User2@sample.com>, "User3" <User3@sample.com> UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 410 CHAPTER 18 C: C: C: C: C: C: S: C: S: SMTP client (Add-on) Subject: Testmail Date: 1 Jan 2008 00:00 +0100 This is a test! . 250 ok 1231221612 qp 3364 quit 221 srv.sample.com UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 411 18.5 Configuration The embOS/IP SMTP client can be used without changing any of the compile time flags. All compile time configuration flags are preconfigured with valid values, which match the requirements of most applications. The following types of configuration macros exist: Binary switches "B" Switches can have a value of either 0 or 1, for deactivated and activated respectively. Actually, anything other than 0 works, but 1 makes it easier to read a configuration file. These switches can enable or disable a certain functionality or behavior. Switches are the simplest form of configuration macros. Numerical values "N" Numerical values are used somewhere in the source code in place of a numerical constant. A typical example is the configuration of the sector size of a storage medium. Alias "A" A macro which operates like a simple text substitute. An example would be the define U8, which the preprocessor would replace with unsigned char. Function replacements "F" Macros can basically be treated like regular functions although certain limitations apply, as a macro is still put into the source code as simple text replacement. Function replacements are mainly used to add specific functionality to a module which is highly hardware-dependent. This type of macro is always declared using brackets (and optional parameters). 18.5.1 Compile time configuration switches Type Symbolic name Default F SMTPC_WARN -- F SMTPC_LOG -- N SMTPC_SERVER_PORT 25 N SMTPC_IN_BUFFER_SIZE 256 N SMTPC_AUTH_USER_BUFFER_SIZE 48 N SMTPC_AUTH_PASS_BUFFER_SIZE 48 UM07001 User & Reference Guide for embOS/IP Description Defines a function to output warnings. In debug configurations (DEBUG == 1) SMTPC_WARN maps to IP_Warnf_Application(). Defines a function to output logging messages. In debug configurations (DEBUG == 1) SMTPC_LOG maps to IP_Logf_Application(). Defines the port where the SMTP server is listening. Defines the size of the input buffer. The input buffer is used to store the SMTP replies of the SMTP server. Defines the size of the buffer used for the Base-64 encoded user name. Defines the size of the buffer used for the Base-64 encoded password. (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 412 CHAPTER 18 SMTP client (Add-on) 18.6 API functions Function IP_SMTPC_Send() Description SMTP client functions Sends an email to a mail transfer agent. Table 18.1: embOS/IP SMTP client interface function overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 413 18.6.1 IP_SMTPC_Send() Description Sends an email to one or multiple recipients. Prototype int IP_SMTPC_Send( const IP_SMTPC_API IP_SMTPC_MAIL_ADDR int IP_SMTPC_MESSAGE const IP_SMTPC_MTA const IP_SMTPC_APPLICATION * pIP_API, * paMailAddr, NumMailAddr, * pMessage, * pMTA, * pApplication ); Parameter Parameter pIP_API paMailAddr NumMailAddr pMessage pMTA pApplication Description [IN] Pointer to an IP_STMPC_API structure. Refer to Structure IP_SMTPC_API on page 415 for detailed information about the elements of the IP_SMTPC_API structure. [IN] Pointer to an array of IP_SMTPC_MAIL_ADDR structures. Refer to Structure IP_SMTPC_MAIL_ADDR on page 418 for detailed information about the elements of the IP_SMTPC_MAIL_ADDR structure. The first element of the array has to be filled with the data of the sender (FROM). The order of the following data sets for recipients (TO), carbon copies (CC) and blind carbon copies (BCC) is not relevant. [IN] Number of email addresses. [IN] Pointer to an array of IP_SMTPC_MESSAGE structures. Refer to Structure IP_SMTPC_MESSAGE on page 420 for detailed information about the elements of the IP_SMTPC_MESSAGE structure. [IN] Pointer to an array of IP_SMTPC_MTA structures. Refer to Structure IP_SMTPC_MTA on page 421 for detailed information about the elements of the IP_SMTPC_MTA structure. [IN] Pointer to an array of IP_SMTPC_APPLICATION structures. Refer to Structure IP_SMTPC_APPLICATION on page 417 for detailed information about the elements of the IP_SMTPC_APPLICATION structure. Table 18.2: IP_SMTPC_Send() parameter list Return value 0 OK. 1 Error. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 414 CHAPTER 18 SMTP client (Add-on) 18.7 SMTP client data structures Function IP_SMTPC_API IP_SMTPC_APPLICATION IP_SMTPC_MAIL_ADDR IP_SMTPC_MESSAGE IP_SMTPC_MTA Description Structure with pointers to the required socket interface functions. Structure with application related elements. Structure to store the mail addresses. Structure defining the message format. Structure to store the login information for the mail transfer agent. Table 18.3: embOS/IP SMTP client interface function overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 415 18.7.1 Structure IP_SMTPC_API Description Structure with pointers to the required socket interface functions. Prototype typedef struct SMTPC_SOCKET void int { (*pfConnect) (char * SrvAddr); (*pfDisconnect) (SMTPC_SOCKET Socket); (*pfSend) (const char * pData, int Len, SMTPC_SOCKET Socket); int (*pfReceive) (char * pData, int Len, SMTPC_SOCKET Socket); } IP_SMTPC_API; Member pfConnect pfDisconnect pfSend pfDisconnect Description Pointer Pointer Pointer Pointer to to to to the function (for example, connect()). the disconnect function (for example, closesocket()). a callback function (for example, send()). a callback function (for example, recv()). Table 18.4: Structure IP_SMTPC_API member list Example /********************************************************************* * * _Connect * * Function description * Creates a socket and opens a TCP connection to the mail host. */ static SMTPC_SOCKET _Connect(char * SrvAddr) { long IP; long Sock; struct hostent * pHostEntry; struct sockaddr_in sin; int r; // // Convert host into mail host // pHostEntry = gethostbyname(SrvAddr); if (pHostEntry == NULL) { SMTPC_LOG(("gethostbyname failed: %s\r\n", SrvAddr)); return NULL; } IP = *(unsigned*)(*pHostEntry->h_addr_list); // // Create socket and connect to mail server // Sock = socket(AF_INET, SOCK_STREAM, 0); if(Sock == -1) { SMTPC_LOG(("Could not create socket!")); return NULL; } IP_MEMSET(&sin, 0, sizeof(sin)); sin.sin_family = AF_INET; sin.sin_port = htons(SERVER_PORT); sin.sin_addr.s_addr = IP; r = connect(Sock, (struct sockaddr*)&sin, sizeof(sin)); if(r == SOCKET_ERROR) { UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 416 CHAPTER 18 SMTP client (Add-on) SMTPC_LOG(("\nSocket error :")); return NULL; } SMTPC_LOG(("APP: Connected.\r\n")); return (SMTPC_SOCKET)Sock; } /********************************************************************* * * _Disconnect * * Function description * Closes a socket. */ static void _Disconnect(SMTPC_SOCKET Socket) { closesocket((long)Socket); } /********************************************************************* * * _Send * * Function description * Sends data via socket interface. */ static int _Send(const char * buf, int len, void * pConnectionInfo) { return send((long)pConnectionInfo, buf, len, 0); } /********************************************************************* * * _Recv * * Function description * Receives data via socket interface. */ static int _Recv(char * buf, int len, void * pConnectionInfo) { return recv((long)pConnectionInfo, buf, len, 0); } static const IP_SMTPC_API _IP_Api = { _Connect, _Disconnect, _Send, _Recv }; UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 417 18.7.2 Structure IP_SMTPC_APPLICATION Description Structure with pointers to application related functions. Prototype typedef struct { U32 (*pfGetTimeDate) (void); int (*pfCallback)(int Stat, void *p); const char * sDomain; // email domain const char * sTimezone; // Time zone. } IP_SMTPC_APPLICATION; Member pfGetTimeDate pfCallback sDomain sTimezone Description Pointer to the function which returns the current system time. Used to set the correct date and time of the email. Pointer to status callback function. Can be NULL. Domain name. For example, sample.com. According to RFC 821 the maximum total length of a domain name or number is 64 characters. Time zone. The zone specifies the offset from Coordinated Universal Time (UTC). Offset from UTC is passed as string: "+0100". Can be NULL. Table 18.5: Structure IP_SMTPC_APPLICATION member list Example ********************************************************************* * * _GetTimeDate */ static U32 _GetTimeDate(void) { U32 r; U16 Sec, Min, Hour; U16 Day, Month, Year; Sec Min Hour Day = = = = 0; 0; 0; 1; // 0 based. Valid range: 0..59 // 0 based. Valid range: 0..59 // 0 based. Valid range: 0..23 // 1 based. Means that 1 is 1. // Valid range is 1..31 (depending on month) Month = 1; // 1 based. Means that January is 1. Valid range is 1..12. Year = 28; // 1980 based. Means that 2008 would be 28. r = Sec / 2 + (Min << 5) + (Hour << 11); r |= (U32)(Day + (Month << 5) + (Year << 9)) << 16; return r; } ********************************************************************* * * _Application */ static const SMTPC_APPLICATION _Application = { _GetTimeDate, NULL, "sample.com" // Your domain. }; UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 418 CHAPTER 18 SMTP client (Add-on) 18.7.3 Structure IP_SMTPC_MAIL_ADDR Description Structure to store an email address. Prototype typedef struct { const char * sName; const char * sAddr; int Type; } IP_SMTPC_MAIL_ADDR; Member sName sAddr Type Description Name of the recipient (for example, "Foo Bar"). Can be NULL. email address of the recipient (for example, "foo@bar.com"). Type of the email address. Table 18.6: Structure IP_SMTPC_MAIL_ADDR member list Valid values for parameter Type Value Description SMTPC_REC_TYPE_FROM email address of the sender (FROM). SMTPC_REC_TYPE_TO email address of the recipient (TO). email address of a recipient which should SMTPC_REC_TYPE_CC get a carbon copy (CC) of the email. email address of a recipient which should SMTPC_REC_TYPE_BC get a blind carbon copy (BCC) of the email. Additional information The structure is used to store the data sets of the sender and all recipients. IP_SMTPC_Send() gets a pointer to an array of IP_SMTPC_MAIL_ADDR structures as parameter. The first element of these array has to be filled with the data of the sender (FROM). The order of the following data sets for Recipients (TO), Carbon Copies (CC) and Blind Carbon Copies (BCC) is not relevant. For detailed information about IP_SMTPC_Send() refer to IP_SMTPC_Send() on page 413. Example /********************************************************************* * * Mailer */ static void _Mailer(void) { SMTPC_MAIL_ADDR MailAddr[4]; SMTPC_MTA Mta; SMTPC_MESSAGE Message; IP_MEMSET(&MailAddr, 0, sizeof(MailAddr)); // // Sender // MailAddr[0].sName = 0; // for example, "Your name"; MailAddr[0].sAddr = 0; // for example, "user@foobar.com"; MailAddr[0].Type = SMTPC_REC_TYPE_FROM; // // Recipient(s) // MailAddr[1].sName = 0; // "Recipient"; MailAddr[1].sAddr = 0; // "recipient@foobar.com"; MailAddr[1].Type = SMTPC_REC_TYPE_TO; UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 419 MailAddr[2].sName = 0; // "CC Recp 1"; MailAddr[2].sAddr = 0; // "cc1@foobar.com"; MailAddr[2].Type = SMTPC_REC_TYPE_CC; MailAddr[3].sName = 0; // "BCC Recp 1" MailAddr[3].sAddr = 0; // "bcc1@foobar.com";; MailAddr[3].Type = SMTPC_REC_TYPE_BCC; // // Message // Message.sSubject = "SMTP message sent via embOS/IP SMTP client"; Message.sBody = "embOS/IP SMTP client - www.segger.com"; // // Fill mail transfer agent structure // Mta.sServer = 0; // for example, "mail.foobar.com"; Mta.sUser = 0; // for example, "user@foobar.com"; Mta.sPass = 0; // for example, "password"; // // Check if sample is configured! // if(Mta.sServer == 0) { SMTPC_WARN(("You have to enter valid SMTP server, sender and recipient(s).\r\n")); while(1); } // // Wait until link is up. This can take 2-3 seconds if PHY has been reset. // while (IP_IFaceIsReady() == 0) { OS_Delay(100); } SMTPC_Send(&_IP_Api, &MailAddr[0], 4, &Message, &Mta, &_Application); while(1); } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 420 CHAPTER 18 SMTP client (Add-on) 18.7.4 Structure IP_SMTPC_MESSAGE Description Structure to store the subject and the text of the email. Prototype typedef struct { const char * sSubject; const char * sBody; int MessageSize; } IP_SMTPC_MESSAGE; Member sSubject sBody MessageSize Description Pointer to the string used as subject of the email. Pointer to the string used as message of the email. Size of the message. Table 18.7: Structure IP_SMTPC_MESSAGE member list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 421 18.7.5 Structure IP_SMTPC_MTA Description Structure to store the server address and the login information. Prototype typedef struct { const char * sServer; const char * sUser; const char * sPass; } IP_SMTPC_MTA; Member sServer sUser sPass Description Server address (for example, "mail.foobar.com"). Account user name (for example, "foo@bar.com"). Can be NULL. Account password (for example, "password"). Can be NULL. Table 18.8: Structure IP_SMTPC_MTA member list Additional information The parameters sUser and sPass have to be NULL if no authentication is used by the server. If sUser is set in the application code, the client tries to use authentication. This means that the client sends the AUTH LOGIN command to the server. If the server does not support authentication, he will return an error code and the client closes the session. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 422 CHAPTER 18 SMTP client (Add-on) 18.8 Resource usage The ROM usage depends on the compiler options, the compiler version and the used CPU. The memory requirements of the SMTP client presented in the tables below have been measured on an ARM7 and a Cortex-M3 system. Details about the further configuration can be found in the sections of the specific example. Configuration used #define SMTPC_OUT_BUFFER_SIZE 256 18.8.1 Resource usage on an ARM7 system The following resource usage has been measured on an ARM7 system using IAR Embedded Workbench V6.30.6, Thumb mode, no interwork, size optimization. 18.8.1.1 ROM usage Addon embOS/IP SMTP client ROM approximately 7.1Kbyte Table 18.9: SMTPC client ROM usage ARM7 18.8.1.2 RAM usage Addon embOS/IP SMTP client (w/o task stack) RAM approximately 4.7Kbyte Table 18.10: SMTPC client RAM usage ARM7 18.8.2 Resource usage on a Cortex-M3 system The following resource usage has been measured on a Cortex-M3 system using IAR Embedded Workbench V6.30.6, size optimization. 18.8.2.1 ROM usage Addon embOS/IP SMTP client ROM approximately 6.5Kbyte Table 18.11: SMTPC client ROM usage Cortex-M3 18.8.2.2 RAM usage Addon embOS/IP SMTP client w/o task stack RAM approximately 4.7Kbyte Table 18.12: SMTPC client RAM usage Cortex-M3 UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 423 Chapter 19 FTP server (Add-on) The embOS/IP FTP server is an optional extension to the TCP/IP stack. The FTP server can be used with embOS/IP or with a different TCP/IP stack. All functions which are required to add a FTP server task to your application are described in this chapter. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 424 CHAPTER 19 FTP server (Add-on) 19.1 embOS/IP FTP server The embOS/IP FTP server is an optional extension which adds the FTP protocol to the stack. FTP stands for File Transfer Protocol. It is the basic mechanism for moving files between machines over TCP/IP based networks such as the Internet. FTP is a client/ server protocol, meaning that one machine, the client, initiates a file transfer by contacting another machine, the server and making requests. The server must be operating before the client initiates his requests. Generally a client communicates with one server at a time, while most servers are designed to work with multiple simultaneous clients. The FTP server implements the relevant parts of the following RFCs. RFC# Description FTP - File Transfer Protocol Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc959.txt [RFC 959] The following table shows the contents of the embOS/IP FTP server root directory: Directory Contents Application\ Contains the example application to run the FTP server with embOS/IP. Config Contains the FTP server configuration file. Inc Contains the required include files. IP Contains the FTP server sources. IP\FS\ Contains the sources for the file system abstraction layer and the read-only file system. Refer to File system abstraction layer function table on page 565 for detailed information. Windows\FTPserver\ Contains the source, the project files and an executable to run embOS/IP FTP server on a Microsoft Windows host. Supplied directory structure of embOS/IP FTP server package UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 425 19.2 Feature list * * * * * * Low memory footprint. Multiple connections supported. Independent of the file system: Any file system can be used. Independent of the TCP/IP stack: Any stack with sockets can be used. Demo application included. Project for executable on PC for Microsoft Visual Studio included. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 426 CHAPTER 19 FTP server (Add-on) 19.3 Requirements TCP/IP stack The embOS/IP FTP server requires a TCP/IP stack. It is optimized for embOS/IP, but any RFC-compliant TCP/IP stack can be used. The shipment includes a Win32 simulation, which uses the standard Winsock API and an implementation which uses the socket API of embOS/IP. Multi tasking The FTP server needs to run as a separate thread. Therefore, a multi tasking system is required to use the embOS/IP FTP server. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 427 19.4 FTP basics The File Transfer Protocol (FTP) is an application layer protocol. FTP is an unusual service in that it utilizes two ports, a 'Data' port and a 'CMD' (command) port. Traditionally these are port 21 for the command port and port 20 for the data port. FTP can be used in two modes, active and passive. Depending on the mode, the data port is not always on port 20. Application layer FTP Transport layer TCP Network layer IP Link layer Ethernet (IEEE 802.3), ... When an FTP client contacts a server, a TCP connection is established between the two machines. The server does a passive open (a socket is listen) when it begins operation; thereafter clients can connect with the server via active opens. This TCP connection persists for as long as the client maintains a session with the server, (usually determined by a human user) and is used to convey commands from the client to the server, and the server replies back to the client. This connection is referred to as the FTP command connection. The FTP commands from the client to the server consist of short sets of ASCII characters, followed by optional command parameters. For example, the FTP command to display the current working directory is PWD (Print Working Directory). All commands are terminated by a carriage return-linefeed sequence (CRLF) (ASCII 10,13; or CtrlJ, Ctrl-M). The servers replies consist of a 3 digit code (in ASCII) followed by some explanatory text. Generally codes in the 200s are success and 500s are failures. See the RFC for a complete guide to reply codes. Most FTP clients support a verbose mode which will allow the user to see these codes as commands progress. If the FTP command requires the server to move a large piece of data (like a file), a second TCP connection is required to do this. This is referred to as the FTP data connection (as opposed to the aforementioned command connection). In active mode the data connection is opened by the server back to a listening client. In passive mode the client opens also the data connection. The data connection persists only for transporting the required data. It is closed as soon as all the data has been sent. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 428 CHAPTER 19 FTP server (Add-on) 19.4.1 Active mode FTP In active mode FTP the client connects from a random unprivileged port P (P > 1023) to the FTP server's command port, port 21. Then, the client starts listening to port P+1 and sends the FTP command PORT P+1 to the FTP server. The server will then connect back to the client's specified data port from its local data port, which is port 20. Server 20 Data Client 21 Cmd 1026 Cmd 1027 Data 1 2 3 4 UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 429 19.4.2 Passive mode FTP In passive mode FTP the client connects from a random unprivileged port P (P > 1023) to the FTP server's command port, port 21. In opposite to an active mode FTP connection where the client opens a passive port for data transmission and waits for the connection from server-side, the client sends in passive mode the "PASV" command to the server and expects an answer with the information on which port the server is listening for the data connection. After receiving this information, the client connects to the specified data port of the server from its local data port. Server 20 Data 1655 Data Client 21 Cmd 1026 Cmd 1027 Data 1 2 3 4 UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 430 CHAPTER 19 FTP server (Add-on) 19.4.3 FTP reply codes Every FTP command is answered by one or more reply codes defined in [RFC 959]. A reply is an acknowledgment (positive or negative) sent from server to user via the control connection in response to FTP commands. The general form of a reply is a 3digit completion code (including error codes) followed by Space <SP>, followed by one line of text and terminated by carriage return line feed <CRLF>. The codes are for use by programs and the text is usually intended for human users. The first digit of the reply code defines the class of response. There are 5 values for the first digit: * * * * * 1yz: 2yz: 3yz: 4yz: 5yz: Positive preliminary reply Positive completion reply Positive intermediate reply Transient negative Completion reply Permanent negative Completion reply The second digit of the reply code defines the group of the response. * * * * * * x0z: Syntax - Syntax errors, syntactically correct commands that don't fit any functional category, unimplemented or superfluous commands. x1z: Information - These are replies to requests for information, such as status or help. x2z: Connections - Replies referring to the control and data connections. x3z: Authentication and accounting - Replies for the login process and accounting procedures. x4z: Unspecified as yet. x5z: File system - These replies indicate the status of the Server file system visa-vis the requested transfer or other file system action. The third digit gives a finer gradation of meaning in each of the function categories, specified by the second digit. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 431 19.4.4 Supported FTP commands embOS/IP FTP server supports a subset of the defined FTP commands. Refer to [RFC 959] for a complete detailed description of the FTP commands. The following FTP commands are implemented: FTP commands CDUP CWD DELE LIST MKD NLST NOOP PASS PASV PORT PWD QUIT RETR RMD RNFR RNTO SIZE STOR SYST TYPE USER XCUP XMKD XPWD XRMD Description Change to parent directory Change working directory Delete List Make directory Name list No operation Password Passive Data port Print the current working directory Logout Retrieve Remove directory Renamr from Rename to Size of file Store System Transfer type User name Change to parent directory Make directory Print the current working directory Remove directory Table 19.1: embOS/IP FTP commands UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 432 CHAPTER 19 FTP server (Add-on) 19.5 Using the FTP server sample Ready to use examples for Microsoft Windows and embOS/IP are supplied. If you use another TCP/IP stack the sample OS_IP_FTPServer.c has to be adapted. The sample application opens a port which listens on port 21 until an incoming connection is detected. If a connection has been established IP_FTPS_Process() handles the client request in an extra task, so that the server is further listening on port 21. The example application requires a file system to make data files available. Refer to File system abstraction layer on page 564 for detailed information. 19.5.1 Using the Windows sample If you have MS Visual C++ 6.00 or any later version available, you will be able to work with a Windows sample project using embOS/IP FTP server. If you do not have the Microsoft compiler, an precompiled executable of the FTP server is also supplied. The base directory of the Windows sample application is C:\FTP\. Building the sample program Open the workspace Start_FTPServer.dsw with MS Visual Studio (for example, double-clicking it). There is no further configuration necessary. You should be able to build the application without any error or warning message. The server uses the IP address of the host PC on which it runs. Open a FTP client and connect by entering the IP address of the host (127.0.0.1) to connect to the FTP server. The server accepts anonymous logins. You can also login with the user name "Admin" and the password "Secret". 19.5.2 Running the FTP server example on target hardware The embOS/IP FTP server sample application should always be the first step to check the proper function of the FTP server with your target hardware. Add all source files located in the following directories (and their subdirectories) to your project and update the include path: * * * * * Application Config Inc IP IP\IP_FS\[NameOfUsedFileSystem] It is recommended that you keep the provided folder structure. The sample application can be used on the most targets without the need for changing any of the configuration flags. The server processes two connections using the default configuration. Note: Two connections mean that the target can handle up one target. A target requires always two connection, one for the command transfer and one for the data transfers. Every connection is handled in an separate task. Therefore, the FTP server uses up to three tasks in the default configuration. One task which listens on port 21 and accepts connections and two tasks to process the accepted connection. To modify the number of connections only the macro MAX_CONNECTIONS has to be modified. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 433 19.6 Access control The embOS/IP FTP server supports a fine-grained access permission scheme. Access permissions can be defined on user-basis for every directory and every file. The access permission of a directory or a file is a combination of the following attributes: visible, readable and writable. To control the access permission four callback functions have be implemented in the user application. The callback functions are defined in the structure FTPS_ACCESS_CONTROL. For detailed information about these structure, refer to Structure FTPS_ACCESS_CONTROL on page 446. 19.6.1 pfFindUser() Description Callback function which checks if the user is valid. Prototype int (*pfFindUser) ( const char * sUser ); Return value 0 - UserID invalid or unknown 0 < - UserID, no password required 0 > - UserID, password required Parameter Parameter sUser Description [IN] User name. Table 19.2: pfFindUser() parameter list Example enum { USER_ID_ANONYMOUS = 1, USER_ID_ADMIN }; /********************************************************************* * * _FindUser * * Function description * Callback function for user management. * Checks if user name is valid. * * Return value * 0 UserID invalid or unknown * > 0 UserID, no password required * < 0 - UserID, password required */ static int _FindUser (const char * sUser) { if (strcmp(sUser, "Admin") == 0) { return - USER_ID_ADMIN; } if (strcmp(sUser, "anonymous") == 0) { return USER_ID_ANONYMOUS; } return 0; } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 434 CHAPTER 19 FTP server (Add-on) 19.6.2 pfCheckPass() Description Callback function which checks if the password is valid. Prototype int (*pfCheckPass) ( int UserId, const char * sPass ); Parameter Parameter UserId Pass Description [IN] Id number [IN] Password string. Table 19.3: pfCheckPass() parameter list Example enum { USER_ID_ANONYMOUS = 1, USER_ID_ADMIN }; /********************************************************************* * * _CheckPass * * Function description * Callback function for user management. * Checks user password. * * Return value * 0 UserID know, password valid * 1 UserID unknown or password invalid */ static int _CheckPass (int UserId, const char * sPass) { if ((UserId == USER_ID_ADMIN) && (strcmp(sPass, "Secret") == 0)) { return 0; } else { return 1; } } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 435 19.6.3 pfGetDirInfo() Description Callback function which checks the permissions of the connected user for every directory. Prototype int (*pfGetDirInfo) ( int UserId, const char * sDirIn, char * pDirOut, int SizeOfDirOut ); Parameter Parameter UserId sDirIn pDirOut SizeOfDirOut Description [IN] Id number [IN] Directory to check permission for [OUT] Directory that can be accessed [IN] Size of buffer addressed by pDirOut Table 19.4: pfGetDirInfo() parameter list Example /* Excerpt from IP_FTPServer.h */ #define IP_FTPS_PERM_VISIBLE (1 << 0) #define IP_FTPS_PERM_READ (1 << 1) #define IP_FTPS_PERM_WRITE (1 << 2) /* Excerpt from OS_IP_FTPServer.c */ /********************************************************************* * * _GetDirInfo * * Function description * Callback function for permission management. * Checks directory permissions. * * Return value * Returns a combination of the following: * IP_FTPS_PERM_VISIBLE - Directory is visible as a directory entry * IP_FTPS_PERM_READ - Directory can be read/entered * IP_FTPS_PERM_WRITE - Directory can be written to * * Parameters * UserId - User ID returned by _FindUser() * sDirIn - Full directory path and with trailing slash * sDirOut - Reserved for future use * DirOutSize - Reserved for future use * * Notes * In this sample configuration anonymous user is allowed to do anything. * Samples for folder permissions show how to set permissions for different * folders and users. The sample configures permissions for the following * directories: * - /READONLY/: This directory is read only and can not be written to. * - /VISIBLE/ : This directory is visible from the folder it is located * in but can not be accessed. * - /ADMIN/ : This directory can only be accessed by the user "Admin". */ static int _GetDirInfo(int UserId, const char * sDirIn, char * sDirOut, int DirOutSize) { int Perm; (void)sDirOut; UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 436 CHAPTER 19 FTP server (Add-on) (void)DirOutSize; Perm = IP_FTPS_PERM_VISIBLE | IP_FTPS_PERM_READ | IP_FTPS_PERM_WRITE; if (strcmp(sDirIn, "/READONLY/") == 0) { Perm = IP_FTPS_PERM_VISIBLE | IP_FTPS_PERM_READ; } if (strcmp(sDirIn, "/VISIBLE/") == 0) { Perm = IP_FTPS_PERM_VISIBLE; } if (strcmp(sDirIn, "/ADMIN/") == 0) { if (UserId != USER_ID_ADMIN) { return 0; // Only Admin is allowed for this directory } } return Perm; } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 437 19.6.4 pfGetFileInfo() Description Callback function which checks the permissions of the connected user for every directory. Prototype int (*pfGetFileInfo) ( int UserId, const char * sFileIn, char * pFileOut, int SizeOfFileOut ); Parameter Parameter UserId sFileIn pFileOut SizeOfFileOut Description [IN] Id number [IN] File to check permission for [OUT] File that can be accessed [IN] Size of buffer addressed by pFileOut Table 19.5: pfGetFileInfo() parameter list Additional information Providing a function for file permissions is optional. If using permisisons on directory level is sufficient for your needs pfGetFileInfo may be declared NULL in the FTPS_ACCESS_CONTROL function table. Example /* Excerpt from IP_FTPServer.h */ #define IP_FTPS_PERM_VISIBLE (1 << 0) #define IP_FTPS_PERM_READ (1 << 1) #define IP_FTPS_PERM_WRITE (1 << 2) /* Excerpt from OS_IP_FTPServer.c */ /********************************************************************* * * _GetFileInfo * * Function description * Callback function for permission management. * Checks file permissions. * * Return value * Returns a combination of the following: * IP_FTPS_PERM_VISIBLE - File is visible as a file entry * IP_FTPS_PERM_READ - File can be read * IP_FTPS_PERM_WRITE - File can be written to * * Parameters * UserId - User ID returned by _FindUser() * sFileIn - Full path to the file * sFileOut - Reserved for future use * FileOutSize - Reserved for future use * * Notes * In this sample configuration all file accesses are allowed. File * permissions are checked against directory permissions. Therefore it * is not necessary to limit permissions on files that reside in a * directory that already limits access. * Setting permissions works the same as for _GetDirInfo() . */ static int _GetFileInfo(int UserId, const char * sFileIn, char * sFileOut, int FileOutSize) { UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 438 CHAPTER 19 FTP server (Add-on) int Perm; (void)UserId; (void)sFileIn; (void)sFileOut; (void)FileOutSize; Perm = IP_FTPS_PERM_VISIBLE | IP_FTPS_PERM_READ | IP_FTPS_PERM_WRITE; return Perm; } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 439 19.7 Configuration The embOS/IP FTP server can be used without changing any of the compile time flags. All compile time configuration flags are preconfigured with valid values, which match the requirements of most applications. The following types of configuration macros exist: Binary switches "B" Switches can have a value of either 0 or 1, for deactivated and activated respectively. Actually, anything other than 0 works, but 1 makes it easier to read a configuration file. These switches can enable or disable a certain functionality or behavior. Switches are the simplest form of configuration macros. Numerical values "N" Numerical values are used somewhere in the source code in place of a numerical constant. A typical example is the configuration of the sector size of a storage medium. Alias "A" A macro which operates like a simple text substitute. An example would be the define U8, which the preprocessor would replace with unsigned char. Function replacements "F" Macros can basically be treated like regular functions although certain limitations apply, as a macro is still put into the source code as simple text replacement. Function replacements are mainly used to add specific functionality to a module which is highly hardware-dependent. This type of macro is always declared using brackets (and optional parameters). 19.7.1 Compile time configuration switches Type Symbolic name Default F FTPS_WARN -- F FTPS_LOG -- N FTPS_AUTH_BUFFER_SIZE 32 N FTPS_BUFFER_SIZE 512 N FTPS_MAX_PATH 128 N FTPS_MAX_PATH_DIR 64 N FTPS_ERR_BUFFER_SIZE 256 UM07001 User & Reference Guide for embOS/IP Description Defines a function to output warnings. In debug configurations (DEBUG == 1) FTPS_WARN maps to IP_Warnf_Application() Defines a function to output logging messages. In debug configurations (DEBUG == 1) FTPS_LOG maps to IP_Logf_Application(). Defines the size of the buffer used for the authentication string. Defines the size of the send and receive buffer of the FTP server. Defines the maximum length of the buffer used for the path string. Defines the maximum length of the buffer used for the directory string. Defines the size of the buffer used for the authentication string. (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 440 CHAPTER 19 FTP server (Add-on) 19.7.2 FTP server system time The FTP server requires a system time for the transmission of a complete file timestamp. FTP servers send only a piece of the timestamp of a file, either month, day and year or month, day and time. For the decision which pieces of the timestamp has to be transmitted, it compares the year of the current system time with the year which is stored in the timestamp of the file. Depending on the result of this comparison either the year or the time will be send. The following two examples show the output for both cases. Example 1. If the value for year in the timestamp of the file is smaller then the value for year in the current system time, year will be sent: -rw-r--r-1 root 2000 Jan 1 2007 PAKET00.TXT In this case, the FTP client leaves this column empty or fills the missing time with 00:00. The following screenshot shows the output of the Microsoft Windows command line FTP client: 2. If the value for year in the timestamp of the file is identical to the value for year in the current system time, the time (HH:MM) will be sent: -rw-r--r-1 root 1000 Jul 29 11:04 PAKET01.TXT In this case, the FTP client leaves this column empty or fills the missing year with the current year. The following screenshot shows the output of the Microsoft Windows command line FTP client: In the example, the value for the current time and date is defined to 1980-01-01 00:00. Therefore, the output will be similar to example 1., since no real time clock (RTC) has been implemented. Refer to pfGetTimeDate() on page 441 for detailed information. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 441 19.7.2.1 pfGetTimeDate() Description Returns the current system time. Prototype int (*pfGetTimeDate) ( void ); Return value Current system time. If no real time clock is implemented, it should return 0x00210000 (1980-01-01 00:00) Additional information The format of the time is arranged as follows: Bit 0-4: 2-second count (0-29) Bit 5-10: Minutes (0-59) Bit 11-15: Hours (0-23) Bit 16-20: Day of month (1-31) Bit 21-24: Month of year (1-12) Bit 25-31: Number of years since1980 (0-127) This function pointer is used in the FTPS_APPLICATION structure. Refer to Structure FTPS_APPLICATION on page 447 for further information. Example static U32 _GetTimeDate(void) { U32 r; U16 Sec, Min, Hour; U16 Day, Month, Year; Sec Min Hour Day = = = = 0; 0; 0; 1; // 0 based. Valid range: 0..59 // 0 based. Valid range: 0..59 // 0 based. Valid range: 0..23 // 1 based. Means that 1 is 1. // Valid range is 1..31 (depending on month) Month = 1; // 1 based. Means that January is 1. Valid range is 1..12. Year = 28; // 1980 based. Means that 2008 would be 28. r = Sec / 2 + (Min << 5) + (Hour << 11); r |= (U32)(Day + (Month << 5) + (Year << 9)) << 16; return r; } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 442 CHAPTER 19 FTP server (Add-on) 19.8 API functions Function IP_FTPS_Process() IP_FTPS_OnConnectionLimit() Description Initializes and starts the embOS/IP FTP server. Returns when the connection is closed or a fatal error occurs. Table 19.6: embOS/IP FTP server interface function overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 443 19.8.1 IP_FTPS_Process() Description Initializes and starts the FTP server. Prototype int IP_FTPS_Process ( const IP_FTPS_API void const IP_FS_API const FTPS_APPLICATION * * * * pIP_API, pConnectInfo, pFS_API, pApplication ); Parameter Parameter pIP_API pConnectInfo pFS_API pApplication Description [IN] [IN] [IN] [IN] Pointer Pointer Pointer Pointer to to to to a structure of type IP_FTPS_API. the connection info. the used file system API. a structure of type FTPS_APPLICATION. Table 19.7: IP_FTPS_Process() parameter list Additional information The structure type IP_FTPS_API contains mappings of the required socket functions to the actual IP stack. This is required because the socket functions are slightly different on different systems. The connection info is the socket which was created when the client has been connected to the command port (usually port 21). For detailed information about the structure type IP_FS_API refer to Appendix A - File system abstraction layer on page 563. For detailed information about the structure type FTPS_APPLICATION refer to Structure FTPS_APPLICATION on page 447. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 444 CHAPTER 19 FTP server (Add-on) 19.8.2 IP_FTPS_OnConnectionLimit() Description Returns when the connection is closed or a fatal error occurs. Prototype void IP_FTPS_OnConnectionLimit( const IP_FTPS_API * pIP_API, void * CtrlSock ); Parameter Parameter pIP_API CtrlSock Description [IN] Pointer to a structure of type IP_FTPS_API. [IN] Pointer to the socket which is related to the command connection. Table 19.8: IP_FTPS_OnConnectionLimit() parameter list Additional information The structure type IP_FTPS_API contains mappings of the required socket functions to the actual IP stack. This is required because the socket functions are slightly different on different systems. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 445 19.9 FTP server data structures 19.9.1 Structure IP_FTPS_API Description This structure contains the pointer to the socket functions which are required to use the FTP server. Prototype typedef struct { int (*pfSend) (const unsigned char * pData, int len, FTPS_SOCKET Socket); int (*pfReceive) (unsigned char * pData, int len, FTPS_SOCKET Socket); FTPS_SOCKET (*pfConnect) (FTPS_SOCKET CtrlSocket, U16 Port); void (*pfDisconnect) (FTPS_SOCKET DataSocket); FTPS_SOCKET (*pfListen) (FTPS_SOCKET CtrlSocket,U16 * pPort,U8 * pIPAddr); int (*pfAccept) (FTPS_SOCKET CtrlSocket, FTPS_SOCKET * pDataSocket); } IP_FTPS_API; Member pfSend pfReceive pfConnect pfDisconnect pfListen pfAccept Description Callback function that sends data to the client on socket level. Callback function that receives data from the client on socket level. Callback function that handles the connect back to a FTP client on socket level if not using passive mode. Callback function that disconnects a connection to the FTP client on socket level if not using passive mode. Callback function that binds the server to a port and addr. Callback function that accepts incoming connections. Table 19.9: Structure IP_FTPS_API member list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 446 CHAPTER 19 FTP server (Add-on) 19.9.2 Structure FTPS_ACCESS_CONTROL Description This structure contains the pointer to the access control callback functions. Prototype typedef struct { int (*pfFindUser) int (*pfCheckPass) ( const char ( int const char int (*pfGetDirInfo) ( int const char char int } FTPS_ACCESS_CONTROL; Member * sUser ); UserId, * sPass ); UserId, * sDirIn, * sDirOut, SizeOfDirOut ); Description Callback function that checks if the user is valid. Callback function that checks if the password is valid. Callback function that checks the permissions of the connected user pfGetDirInfo for every directory. Callback function that checks the permisisons of the connected user pfGetFileInfo for every file. May be NULL if directory permisisons are sufficient for your needs. pfFindUser pfCheckPass Table 19.10: Structure FTPS_ACCESS_CONTROL member list Example Refer to Access control on page 433 for an example. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 447 19.9.3 Structure FTPS_APPLICATION Description Used to store application specific parameters. Prototype typedef struct { FTPS_ACCESS_CONTROL * pAccess; U32 (*pfGetTimeDate) (void); } FTPS_APPLICATION; Member Description pAccess Pointer to the FTPS_ACCESS_APPLCIATION structure. pfGetTimeDate Pointer to the function which returns the current system time. Table 19.11: Structure FTPS_APPLICATION member list Example For additional information to structure FTPS_ACCESS_APPLICATION refer to Structure FTPS_ACCESS_CONTROL on page 446. For additional information to function pointer pfGetTimeDate() refer to FTP server system time on page 440. Example /* Excerpt from OS_IP_FTPServer.c */ /********************************************************************* * * FTPS_ACCESS_CONTROL * * Description * User/pass data table */ static FTPS_ACCESS_CONTROL _Access_Control = { _FindUser, _CheckPass, _GetDirInfo }; ********************************************************************* * * _GetTimeDate */ static U32 _GetTimeDate(void) { U32 r; U16 Sec, Min, Hour; U16 Day, Month, Year; Sec Min Hour Day = = = = 0; 0; 0; 1; // 0 based. Valid range: 0..59 // 0 based. Valid range: 0..59 // 0 based. Valid range: 0..23 // 1 based. Means that 1 is 1. // Valid range is 1..31 (depending on month) Month = 1; // 1 based. Means that January is 1. Valid range is 1..12. Year = 28; // 1980 based. Means that 2008 would be 28. r = Sec / 2 + (Min << 5) + (Hour << 11); r |= (U32)(Day + (Month << 5) + (Year << 9)) << 16; return r; } ********************************************************************* * * FTPS_APPLICATION * * Description * Application data table, defines all application specifics * used by the FTP server */ static const FTPS_APPLICATION _Application = { &_Access_Control, _GetTimeDate }; UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 448 CHAPTER 19 FTP server (Add-on) 19.10 Resource usage The ROM usage depends on the compiler options, the compiler version and the used CPU. The memory requirements of the FTP server presented in the tables below have been measured on an ARM7 and a Cortrex-M3 system. Details about the further configuration can be found in the sections of the specific example. Configuration used #define #define #define #define #define FTPS_AUTH_BUFFER_SIZE 32 FTPS_BUFFER_SIZE 512 FTPS_MAX_PATH 128 FTPS_MAX_PATH_DIR 64 FTPS_ERR_BUFFER_SIZE (FTPS_BUFFER_SIZE / 2) 19.10.1 ROM usage on an ARM7 system The following resource usage has been measured on an ARM7 system using IAR Embedded Workbench V6.30.6, Thumb mode, no interwork, size optimization. Addon ROM embOS/IP FTP server approximately 6.6Kbyte Table 19.12: FTP server ROM usage ARM7 19.10.2 ROM usage on a Cortex-M3 system The following resource usage has been measured on a Cortex-M3 system using IAR Embedded Workbench V6.30.6, size optimization. Addon ROM embOS/IP FTP server approximately 5.6Kbyte Table 19.13: FTP server ROM usage Cortex-M3 19.10.3 RAM usage: Almost all of the RAM used by the FTP server is taken from task stacks. The amount of RAM required for every child task depends on the configuration of your server. The table below shows typical RAM requirements for your task stacks. Task Description ParentTask ChildTask RAM Listens for incoming connections. Handles a request. approximately 500 bytes approximately 1800 bytes Table 19.14: FTP server RAM usage Note: The FTP server requires at least 1 child task. The approximately RAM usage for the FTP server can be calculated as follows: RAM usage = 0.2 Kbytes + ParentTask + (NumberOfChildTasks * 1.8 Kbytes) Example: FTP server accepting up only 1 connection RAM usage = 0.2 Kbytes + 0.5 Kbytes + (1 * 1.8 Kbytes) RAM usage = 2.5 Kbytes UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 449 Chapter 20 FTP client (Add-on) The embOS/IP FTP client is an optional extension to the TCP/IP stack. The FTP client can be used with embOS/IP or with a different TCP/IP stack. All functions which are required to add a FTP client to your application are described in this chapter. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 450 CHAPTER 20 FTP client (Add-on) 20.1 embOS/IP FTP client The embOS/IP FTP client is an optional extension which adds the client part of FTP protocol to the stack. FTP stands for File Transfer Protocol. It is the basic mechanism for moving files between machines over TCP/IP based networks such as the Internet. FTP is a client/server protocol, meaning that one machine, the client, initiates a file transfer by contacting another machine, the server and making requests. The FTP client implements the relevant parts of the following RFCs. RFC# Description FTP - File Transfer Protocol Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc959.txt [RFC 959] The following table shows the contents of the embOS/IP FTP client root directory: Directory Contents Application\ Contains the example application to run the FTP client with embOS/IP. Config Contains the FTP client configuration file. Inc Contains the required include files. IP Contains the FTP client sources. IP\FS\ Contains the sources for the file system abstraction layer and the read-only file system. Refer to File system abstraction layer function table on page 565 for detailed information. Windows\FTPclient\ Contains the source, the project files and an executable to run embOS/IP FTP client on a Microsoft Windows host. Supplied directory structure of embOS/IP FTP client package UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 451 20.2 Feature list * * * * * * Low memory footprint. Multiple connections supported. Independent of the file system: Any file system can be used. Independent of the TCP/IP stack: Any stack with sockets can be used. Demo application included. Project for executable on PC for Microsoft Visual Studio included. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 452 CHAPTER 20 FTP client (Add-on) 20.3 Requirements TCP/IP stack The embOS/IP FTP client requires a TCP/IP stack. It is optimized for embOS/IP, but any RFC-compliant TCP/IP stack can be used. The shipment includes a Win32 simulation, which uses the standard Winsock API and an implementation which uses the socket API of embOS/IP. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 453 20.4 FTP basics The File Transfer Protocol (FTP) is an application layer protocol. FTP is an unusual service in that it utilizes two ports, a 'Data' port and a 'CMD' (command) port. Traditionally these are port 21 for the command port and port 20 for the data port. FTP can be used in two modes, active and passive. Depending on the mode, the data port is not always on port 20. Application layer FTP Transport layer TCP Network layer IP Link layer Ethernet (IEEE 802.3), ... When an FTP client contacts a server, a TCP connection is established between the two machines. The server does a passive open (a socket is listen) when it begins operation; thereafter clients can connect with the server via active opens. This TCP connection persists for as long as the client maintains a session with the server, (usually determined by a human user) and is used to convey commands from the client to the server, and the server replies back to the client. This connection is referred to as the FTP command connection. The FTP commands from the client to the server consist of short sets of ASCII characters, followed by optional command parameters. For example, the FTP command to display the current working directory is PWD (Print Working Directory). All commands are terminated by a carriage return-linefeed sequence (CRLF) (ASCII 10,13; or CtrlJ, Ctrl-M). The servers replies consist of a 3 digit code (in ASCII) followed by some explanatory text. Generally codes in the 200s are success and 500s are failures. See the RFC for a complete guide to reply codes. Most FTP clients support a verbose mode which will allow the user to see these codes as commands progress. If the FTP command requires the server to move a large piece of data (like a file), a second TCP connection is required to do this. This is referred to as the FTP data connection (as opposed to the aforementioned command connection). In active mode the data connection is opened by the server back to a listening client. In passive mode the client opens also the data connection. The data connection persists only for transporting the required data. It is closed as soon as all the data has been sent. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 454 CHAPTER 20 FTP client (Add-on) 20.4.1 Passive mode FTP In passive mode FTP the client connects from a random unprivileged port P (P > 1023) to the FTP server's command port, port 21. In opposite to an active mode FTP connection where the client opens a passive port for data transmission and waits for the connection from server-side, the client sends in passive mode the "PASV" command to the server and expects an answer with the information on which port the server is listening for the data connection. After receiving this information, the client connects to the specified data port of the server from its local data port. Server 20 Data 1655 Data Client 21 Cmd 1026 Cmd 1027 Data 1 2 3 4 Note: In the current version of embOS/IP, the FTP client supports only passive mode FTP. Active mode FTP will be added in one of the coming versions. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 455 20.4.2 Supported FTP client commands embOS/IP FTP client supports a subset of the defined FTP commands. Refer to [RFC 959] for a complete detailed description of the FTP commands. The following FTP commands are implemented: FTP commands CDUP CWD LIST MKD PASS PWD RETR RMD STOR TYPE USER Description Change to parent directory Change working directory List directory Make driectory Password Print the current working directory Retrieve Remove directory Store Transfer type User name Table 20.1: embOS/IP FTP client commands UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 456 CHAPTER 20 FTP client (Add-on) 20.5 Configuration The embOS/IP FTP client can be used without changing any of the compile time flags. All compile time configuration flags are preconfigured with valid values, which match the requirements of most applications. The following types of configuration macros exist: Binary switches "B" Switches can have a value of either 0 or 1, for deactivated and activated respectively. Actually, anything other than 0 works, but 1 makes it easier to read a configuration file. These switches can enable or disable a certain functionality or behavior. Switches are the simplest form of configuration macros. Numerical values "N" Numerical values are used somewhere in the source code in place of a numerical constant. A typical example is the configuration of the sector size of a storage medium. Alias "A" A macro which operates like a simple text substitute. An example would be the define U8, which the preprocessor would replace with unsigned char. Function replacements "F" Macros can basically be treated like regular functions although certain limitations apply, as a macro is still put into the source code as simple text replacement. Function replacements are mainly used to add specific functionality to a module which is highly hardware-dependent. This type of macro is always declared using brackets (and optional parameters). 20.5.1 Compile time configuration switches Type Symbolic name Default F FTPC_WARN -- F FTPC_LOG -- N FTPC_BUFFER_SIZE 512 N FTPC_CTRL_BUFFER_SIZE 256 N FTPC_SERVER_REPLY_BUFFER_ 128 SIZE UM07001 User & Reference Guide for embOS/IP Description Defines a function to output warnings. In debug configurations (DEBUG == 1) FTPC_WARN should be mapped to IP_Warnf_Application() Defines a function to output logging messages. In debug configurations (DEBUG == 1) FTPC_LOG should be mapped to IP_Logf_Application(). Defines the size of the in and the out buffer of the FTP client. This means that the client requires the defined number of bytes for each buffer. For example, FTPC_BUFFER_SIZE == 512 means 1024 bytes RAM requirement. Defines the maximum length of the buffer used for the control channel. Defines the maximum length of the buffer used for the server reply strings. This buffer is only required and used in debug builds. In release builds the memory will not be allocated. (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 457 20.6 API functions Function IP_FTPC_Connect() IP_FTPC_Disconnect() IP_FTPC_ExecCmd() IP_FTPC_Init() Description Establishes a connection to a FTP server. Closes an established connection to a FTP server. Sends a command to a FTP server. Initializes the embOS/IP FTP client. Table 20.2: embOS/IP FTP client interface function overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 458 CHAPTER 20 FTP client (Add-on) 20.6.1 IP_FTPC_Connect() Description Establishes a connection to a FTP server. Prototype int IP_FTPC_Connect ( IP_FTPC_CONTEXT * pContext, const char * sServer, const char * sUser, const char * sPass, unsigned PortCmd, unsigned Mode ); Parameter Parameter pContext sServer sUser sPass PortCmd Mode Description [IN] Pointer to a structure of type IP_FTPC_CONTEXT. [IN] Dot-decimal IP address of a FTP server, for example "192.168.1.55". [IN] User name if required for the authentication. Can be NULL. [IN] Password if required for the authentication. Can be NULL. [IN] Port number of the port which is in listening mode on the FTP server. The well-known port for an FTP server that is waiting for connections is 21. [IN] FTP transfer mode. Table 20.3: IP_FTPC_Connect() parameter list Valid values for parameter Mode FTPC_MODE_PASSIVE Description Use passive mode FTP. Return value 0 on success. 1 on error. Illegal parameter (pContext == NULL). -1 on error during the process of establishing a connection. Additional information The function IP_FTPC_Init() must be called before a call IP_FTPC_Connect(). For detailed information about IP_FTPC_Init() refer to IP_FTPC_Init() on page 464. Note: In the current version of embOS/IP, the FTP client supports only passive mode FTP. Example Refer to IP_FTPC_ExecCmd() on page 460 for an example application which uses IP_FTPC_Connect(). UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 459 20.6.2 IP_FTPC_Disconnect() Description Closes an established connection to a FTP server. Prototype int IP_FTPC_Disconnect ( IP_FTPC_CONTEXT * pContext ); Parameter Parameter pContext Description [IN] Pointer to a structure of type IP_FTPC_CONTEXT. Table 20.4: IP_FTPC_Disconnect() parameter list Return value 0 on success. 1 on error. Illegal parameter (pContext == NULL). Example Refer to IP_FTPC_ExecCmd() on page 460 for an example application which uses IP_FTPC_Disconnect(). UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 460 CHAPTER 20 FTP client (Add-on) 20.6.3 IP_FTPC_ExecCmd() Description Executes a command on the FTP server. Prototype int IP_FTPC_ExecCmd ( IP_FTPC_CONTEXT * pContext, unsigned Cmd, const char * sPara ); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 461 Parameter Parameter pContext Cmd sPara Description [IN] Pointer to a structure of type IP_FTPC_CONTEXT. [IN] See table below. [IN] String with the required parameters for the command. Depending on the command, the parameter can be NULL. Table 20.5: IP_FTPC_ExecCmd() parameter list Valid values for parameter Cmd Description The command CDUP (Change to Parent Directory). sPara is NULL. The command CWD (Change Working Directory). sPara is the path to the directory that should be accessed. The command LIST (List current directory content). sPara is NULL. The command MKD (Make directory). sPara is the name of the directory that should be created. The command PASS (Set password). sPara is the password. The command PWD (Print Working Directory). sPara is NULL. The command RETR (Retrieve). sPara is the name of the file that should be received from the server. The FTP client creates a file on the used storage medium and stores the retrieved file. The command RMD (Remove directory). sPara is the name of the directory that should be removed. The command STOR (Store). sPara is the name of the file that should be stored on the server. The FTP client opens the file and transmits it to the FTP server. The command TYPE (Transfer type). sPara is the transfer type. The command USER (Set username). sPara is the username. The command DELE (delete file). sPara is the name of the file to delete. FTPC_CMD_CDUP FTPC_CMD_CWD FTPC_CMD_LIST FTPC_CMD_MKD FTPC_CMD_PASS FTPC_CMD_PWD FTPC_CMD_RETR FTPC_CMD_RMD FTPC_CMD_STOR FTPC_CMD_TYPE FTPC_CMD_USER FTPC_CMD_DELE Return value 0 on success. 1 on error. Illegal parameter (pContext == NULL). -1 on error during command execution. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 462 CHAPTER 20 FTP client (Add-on) Additional information IP_FTPC_Init() and IP_FTPC_Connect() have to be called before IP_FTPC_ExecCmd(). Refer to IP_FTPC_Init() on page 464 for detailed information about how to initialize the FTP client and refer to IP_FTPC_Connect() on page 458 for detailed information about how to establish a connection to a FTP server. IP_FTPC_ExecCmd() sends a command to the server and handles everything what is required on FTP client side. The commands which are listed in section Supported FTP client commands on page 455, but not explained here, are normally not directly called from the user application. There is no need to call IP_ExecCmd() with these commands. The FTP client uses these commands internally and sends them to the server if required. For example, the call of IP_FTPC_Connect() sends the the commands USER, PASS and SYST to the server and process the server replies for each of the commands, an explicit call of IP_FTPC_Exec() with one of these commands is not requried. Example /* Excerpt from the example application OS_IP_FTPClient.c */ /********************************************************************* * * MainTask * * Note: * The size of the stack of this task should be at least * 1200 bytes + FTPC_CTRL_BUFFER_SIZE + 2 * FTPC_BUFFER_SIZE. */ void MainTask(void); void MainTask(void) { IP_FTPC_CONTEXT FTPConnection; U8 acCtrlIn[FTPC_CTRL_BUFFER_SIZE]; U8 acDataIn[FTPC_BUFFER_SIZE]; U8 acDataOut[FTPC_BUFFER_SIZE]; int r; // // Initialize the IP stack // IP_Init(); OS_CREATETASK(&_TCB, "IP_Task", IP_Task , 150, _IPStack); // Start the IP_Task // // Check if target is configured // while (IP_IFaceIsReady() == 0) { BSP_ToggleLED(1); OS_Delay(50); } // // FTP client task // while (1) { BSP_SetLED(0); // // Initialize FTP client context // memset(&FTPConnection, 0, sizeof(FTPConnection)); // // Initialize the FTP client // IP_FTPC_Init(&FTPConnection, &_IP_Api, &IP_FS_FS, acCtrlIn, sizeof(acCtrlIn), acDataIn, sizeof(acDataIn), acDataOut, sizeof(acDataOut)); // // Connect to the FTP server // r = IP_FTPC_Connect(&FTPConnection, "192.168.199.164", "Admin", "Secret", UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 463 21, FTPC_MODE_PASSIVE); if (r == FTPC_ERROR) { FTPC_LOG(("APP: Could not connect to FTP server.\r\n")); goto Disconnect; } // // Change from root directory into directory "Test" // r = IP_FTPC_ExecCmd(&FTPConnection, FTPC_CMD_CWD, "/Test/"); if (r == FTPC_ERROR) { FTPC_LOG(("APP: Could not change working directory.\r\n")); goto Disconnect; } // // Upload the file "Readme.txt // r = IP_FTPC_ExecCmd(&FTPConnection, FTPC_CMD_STOR, "Readme.txt"); if (r == FTPC_ERROR) { FTPC_LOG(("APP: Could not upload data file.\r\n")); goto Disconnect; } // // Change back to root directory. // r = IP_FTPC_ExecCmd(&FTPConnection, FTPC_CMD_CDUP, NULL); if (r == FTPC_ERROR) { FTPC_LOG(("APP: Change to parent directory failed.\r\n")); goto Disconnect; } // // Disconnect. // Disconnect: IP_FTPC_Disconnect(&FTPConnection); FTPC_LOG(("APP: Done.\r\n")); BSP_ClrLED(0); OS_Delay (10000); } } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 464 CHAPTER 20 FTP client (Add-on) 20.6.4 IP_FTPC_Init() Description Initializes the FTP client context. Prototype int IP_FTPC_Init ( IP_FTPC_CONTEXT * pContext, const IP_FTPC_API * pIP_API, const IP_FS_API * pFS_API, U8 * pCtrlBuffer, unsigned NumBytesCtrl, U8 * pDataInBuffer, unsigned NumBytesDataIn, U8 * pDataOutBuffer, unsigned NumBytesDataOut ); Parameter Parameter Description [IN] Pointer to a structure of type IP_FTPC_CONTEXT. [IN] Pointer to a structure of type IP_FTPC_API. [IN] Pointer to the file system API. [IN] Pointer to the buffer used for the control channel informapControlBuffer tion. NumBytesCtrl [IN] Size of the control buffer in bytes. pDataInBuffer [IN] Pointer to the buffer used to receive data from the server. NumBytesDataIn [IN] Size of the receive buffer in bytes. pDataOutBuffer [IN] Pointer to the buffer used to transmit data to the server. NumBytesDataOut [IN] Size of the transmit buffer in bytes. pContext pIP_API pFS_API Table 20.6: IP_FTPC_Init() parameter list Return value 0 on success. 1 on error. Invalid parameters. Additional information IP_FTPC_Init() must be called before any other FTP client function will be called. For detailed information about the structure type IP_FS_API refer to Appendix A - File system abstraction layer on page 563. For detailed information about the structure type IP_FTPC_API refer to Appendix A - File system abstraction layer on page 563. Example Refer to IP_FTPC_ExecCmd() on page 460 for an example application which uses IP_FTPC_Init(). UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 465 20.7 FTP client data structures 20.7.1 Structure IP_FTPC_API Description This structure contains the pointer to the socket functions which are required to use the FTP client. Prototype typedef struct FTPC_SOCKET void int int } IP_FTPC_API; { (*pfConnect) (const char * SrvAddr, unsigned SrvPort); (*pfDisconnect) (FTPC_SOCKET Socket); (*pfSend) (const char * pData, int Len, FTPC_SOCKET Socket); (*pfReceive) (char * pData, int Len, FTPC_SOCKET Socket); Member pfConnect pfDisconnect pfSend pfReceive Description Callback function that handles the connect to a FTP server on socket level. Callback function that disconnects a connection to the FTP server on socket level. Callback function that sends data to the FTP server on socket level. Callback function that receives data from the FTP server on socket level. Table 20.7: Structure IP_FTPC_API member list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 466 CHAPTER 20 FTP client (Add-on) 20.8 Resource usage The ROM usage depends on the compiler options, the compiler version and the used CPU. The memory requirements of the FTP client presented in the tables below have been measured on an ARM7 and a Cortex-M3 system. Details about the further configuration can be found in the sections of the specific example. Configuration used #define FTPC_BUFFER_SIZE #define FTPC_CTRL_BUFFER_SIZE #define FTPC_SERVER_REPLY_BUFFER_SIZE 512 256 128 // Only required in debug builds // with enabled logging. 20.8.1 ROM usage on an ARM7 system The following resource usage has been measured on an ARM7 system using IAR Embedded Workbench V6.30.6, Thumb mode, no interwork, size optimization. Addon ROM embOS/IP FTP client approximately 2Kbyte Table 20.8: FTP client ROM usage ARM7 20.8.2 ROM usage on a Cortex-M3 system The following resource usage has been measured on a Cortex-M3 system using IAR Embedded Workbench V6.30.6, size optimization. Addon ROM embOS/IP FTP client approximately 1.7Kbyte Table 20.9: FTP client ROM usage Cortex-M3 20.8.3 RAM usage: Almost all of the RAM used by the web server is taken from task stacks. The amount of RAM required for every child task depends on the configuration of your client. The table below shows typical RAM requirements for your task stacks. Build Release Description A task used for the FTP client without debugging features and disabled debug outputs. RAM app. 1400 bytes Table 20.10: FTP client RAM usage release build The approximately task stack size required for the FTP client can be calculated as follows: TaskStackSize = 2 * FTPC_BUFFER_SIZE + FTPC_CTRL_BUFFER_SIZE Build Debug Description RAM A task used for the FTP client with debugging features app. 1550 bytes and enabled debug outputs. Table 20.11: FTP client RAM usage debug build The approximately task stack size required for the FTP client can be calculated as follows: TaskStackSize = 2 * FTPC_BUFFER_SIZE + FTPC_CTRL_BUFFER_SIZE + FTPC_SERVER_REPLY_BUFFER_SIZE UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 467 Chapter 21 TFTP client/server The TFTP (Trivial File Transfer Protocol) is an extension to the TCP/IP stack. All functions which are required to add a TFTP client or a TFPT server to your application are described in this chapter. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 468 CHAPTER 21 TFTP client/server 21.1 embOS/IP TFTP The embOS/IP TFTP is an extension which adds the TFTP protocol to the stack. TFTP stands for Trivial File Transfer Protocol. It is the basic mechanism for moving files via UDP between machines over IP based networks. TFTP is a client/server protocol, meaning that one machine, the client, initiates a file transfer by contacting another machine, the server and making requests. The server must be operating before the client initiates his requests. The TFTP server implements the relevant parts of the following RFCs. RFC# [RFC 1350] Description TFTP - THE TFTP PROTOCOL (REVISION 2) Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc1350.txt UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 469 21.2 Feature list * * * * Low memory footprint. Independent of the file system: Any file system can be used. Independent of the TCP/IP stack: Any stack with sockets can be used. Demo application included. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 470 CHAPTER 21 TFTP client/server 21.3 TFTP basics The Trivial File Transfer Protocol (TFTP) is an application layer protocol. Application layer TFTP Transport layer UDP Network layer IPv4 Link layer Ethernet When a TFTP client contacts a server, a UDP command is sent to the servers port. The traditional port is 69. The command sent is either a read or a write request. The client will send data always to the servers port wheras the server will repsond with data to the port on that the client is sending. The TFTP requests are sent in a RFC conform format. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 471 21.4 Using the TFTP samples Ready to use examples for embOS/IP are supplied. The sample applications are configured to work with each other but can be used with any TFTP client/server with minimal modification. The example applications requires a file system to make data files available. Refer to File system abstraction layer on page 564 for detailed information. 21.4.1 Running the TFTP server example on target hardware The embOS/IP TFTP sample applications should always be the first step to check the proper function of the TFTP client/server with your target hardware. Add all source files located in the following directories (and their subdirectories) to your project and update the include path: * * * * * Application Config Inc IP IP\IP_FS\[NameOfUsedFileSystem] It is recommended that you keep the provided folder structure. The sample applications can be used on the most targets without the need for changing any of the configuration flags. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 472 CHAPTER 21 TFTP client/server 21.5 API functions Function Description Table 21.1: embOS/IP TFTP client/server function overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 473 21.5.1 IP_TFTP_InitContext() Description Initializes the context for storing connection parameters of a TFTP client/server. Prototype int IP_TFTP_InitContext ( TFTP_CONTEXT *pContext, unsigned IFace, const IP_FS_API *pFS_API, char *pBuffer, int BufferSize, U16 ServerPort ); Parameter Parameter pContext IFace pFS_API pBuffer BufferSize ServerPort Description [IN] Pointer to a structure of type TFTP_CONTEXT. [IN] Zero-based interface index to use for UDP transfer. [IN] Pointer to the used file system API. [IN] Pointer to buffer for storing transfer data. Needs to be big enough to hold the biggest TFTP message (512 bytes payload + 4 bytes TFTP header). [IN] Size of buffer assigned with pBuffer. Server port to open if server. Table 21.2: IP_TFTP_InitContext() parameter list Return value 0: O.K. < 0: Error, typically buffer too small or no buffer set. Additional information A static structure of TFTP_CONTEXT needs to be supplied by the application to supply space to store connection parameters. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 474 CHAPTER 21 TFTP client/server 21.5.2 IP_TFTP_RecvFile() Description Requests a file from a TFTP server. Prototype int IP_TFTP_RecvFile ( TFTP_CONTEXT *pContext, unsigned IFace, U32 IPAddr, U16 Port, const char *sFileName, int Mode ); Parameter Parameter pContext IFace IPAddr Port sFileName Mode Description [IN] [IN] [IN] [IN] [IN] [IN] Pointer to a structure of type TFTP_CONTEXT. Zero-based interface index to use for UDP transfer. IP addr. of TFTP server. Port of TFTP server listening. Name of file to retrieve from server. TFTP_MODE_OCTET. Table 21.3: IP_TFTP_RecvFile() parameter list Return value SOCKET_ERROR (-1): Error. Other: O.K. Additional information A static structure of TFTP_CONTEXT needs to initialized with IP_TFTP_InitContext() on page 473 before using it with this function. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 475 21.5.3 IP_TFTP_SendFile() Description Sends a file to a TFTP server. Prototype int IP_TFTP_SendFile ( TFTP_CONTEXT *pContext, unsigned IFace, U32 IPAddr, U16 Port, const char *sFileName, int Mode ); Parameter Parameter pContext IFace IPAddr Port sFileName Mode Description [IN] [IN] [IN] [IN] [IN] [IN] Pointer to a structure of type TFTP_CONTEXT. Zero-based interface index to use for UDP transfer. IP addr. of TFTP server. Port of TFTP server listening. Name of file to send to server. TFTP_MODE_OCTET. Table 21.4: IP_TFTP_SendFile() parameter list Return value SOCKET_ERROR (-1): Error. Other: O.K. Additional information A static structure of TFTP_CONTEXT needs to initialized with IP_TFTP_InitContext() on page 473 before using it with this function. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 476 CHAPTER 21 TFTP client/server 21.5.4 IP_TFTP_ServerTask() Description TFTP server task that can be be started in a separate task. Prototype void IP_TFTP_ServerTask ( void *pPara ); Parameter Parameter pPara Description [IN] Casted pointer to a structure of type TFTP_CONTEXT. Table 21.5: IP_TFTP_RecvFile() parameter list Additional information A static structure of TFTP_CONTEXT needs to initialized with IP_TFTP_InitContext() on page 473 before using it with this function. The task does never return. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 477 21.6 Resource usage The ROM usage depends on the compiler options, the compiler version and the used CPU. The memory requirements of the TFTP client/server presented in the tables below have been measured on an ARM7 and a Cortrex-M3 system. Details about the further configuration can be found in the sections of the specific example. 21.6.1 ROM usage on an ARM7 system The following resource usage has been measured on an ARM7 system using IAR Embedded Workbench V6.30.6, Thumb mode, no interwork, size optimization. Addon ROM embOS/IP TFTP client embOS/IP TFTP server approximately 1.2Kbyte approximately 1.2Kbyte Table 21.6: TFTP client/server ROM usage ARM7 21.6.2 ROM usage on a Cortex-M3 system The following resource usage has been measured on a Cortex-M3 system using IAR Embedded Workbench V6.30.6, size optimization. Addon ROM embOS/IP FTP client embOS/IP FTP server approximately 1.2Kbyte approximately 1.2Kbyte Table 21.7: TFTP client/server ROM usage Cortex-M3 21.6.3 RAM usage: Each connection requires approximately 550 bytes of RAM that split into space for the required transfer buffer (app. 516 bytes) and the space for TFTP_CONTEXT. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 478 UM07001 User & Reference Guide for embOS/IP CHAPTER 21 TFTP client/server (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 479 Chapter 22 PPP / PPPoE (Add-on) The embOS/IP implementation of the Point to Point Protocol (PPP) is an optional extension to embOS/IP. It can be used to establish a PPP connection over Ethernet (PPPoE) or using modem to connect via telephone carrier. All functions that are required to add PPP/PPPoE to your application are described in this chapter. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 480 CHAPTER 22 PPP / PPPoE (Add-on) 22.1 embOS/IP PPP/PPPoE The embOS/IP PPP implementation is an optional extension which can be seamlessly integrated into your TCP/IP application. It combines a maximum of performance with a small memory footprint. The PPP implementation allows an embedded system to connect via Point to Point Protocol to a network. The PPP module implements the relevant parts of the following Request For Comments (RFC). RFC# [RFC 1334] [RFC 1661] [RFC 1994] [RFC 2516] Description PPP Authentication Protocols Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc1334.txt The Point-to-Point Protocol (PPP) Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc1661.txt PPP Challenge Handshake Authentication Protocol (CHAP) Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc1994.txt A Method for Transmitting PPP Over Ethernet (PPPoE) Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc2516.txt The following table shows the contents of the embOS/IP root directory: Directory Content Application Contains the example application to run the PPP implementation with embOS/IP. Inc Contains the required include files. IP Contains the PPP sources, IP_PPP.c, IP_PPP_CCP.c, IP_PPP_Int.h, IP_PPP_IPCP.c, IP_PPP_LCP.c, IP_PPP_Line.c, IP_PPP_PAP.c and IP_PPPoE.c. Additionally to the main source code files of the PPP add-on an example implementation for the connection of a modem via USART (IP_Modem_UART.c) is supplied. Supplied directory structure of embOS/IP PPP package UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 481 22.2 Feature list * * * Low memory footprint. Support PAP authentication protocol Support for PPP over Ethernet. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 482 CHAPTER 22 PPP / PPPoE (Add-on) 22.3 Requirements TCP/IP stack The embOS/IP PPP implementation requires the embOS/IP TCP/IP stack. Your modem has to be able to be configured to respond in the format "<CR><LF><Response>". UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 483 22.4 PPP backgrounds The Point to Point Protocol is a link layer protocol for establishing a direct connection between two network nodes. Application layer SMTP Transport layer TCP Network layer IP Link layer PPP, PPPoE Using PPP, an embOS/IP application can establish a PPP connection to a PPP server. The handshaking mechanism includes normally an authentication process. The current version of embOS/IP supports the the following authentication schemes: * PAP - Password Authentication Protocol UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 484 CHAPTER 22 PPP / PPPoE (Add-on) 22.5 API functions Function Description PPPoE functions IP_PPPOE_AddInterface() Adds a PPPoE interface. Configures the number of times to resend a IP_PPPOE_ConfigRetries() lost message before breaking the connection. IP_PPPOE_Reset() Resets the PPPoE connection. Sets the authentication information for the IP_PPPOE_SetAuthInfo() PPPoE connection. Sets a callback function to inform the user IP_PPPOE_SetUserCallback() about a status change of the connection. PPP functions IP_PPP_AddInterface() Adds a PPP driver. Receives one or more characters from the IP_PPP_OnRx() hardware. IP_PPP_OnRxChar() Receives a character from the hardware. IP_PPP_OnTxChar() Sends a character via PPP. Sets a callback function to inform the user IP_PPP_SetUserCallback() about a status change of the connection. Modem functions IP_MODEM_Connect() Connects using the modem line. IP_MODEM_Disconnect() Disconnects the modem line. Retrieves the last received responses from IP_MODEM_GetResponse() the modem. IP_MODEM_SendString() Sends a command to the modem. Sends a command to the modem and IP_MODEM_SendStringEx() checks for the correct response. Sets authentication information required by IP_MODEM_SetAuthInfo() your ISP. Sets the timeout how long to wait until the IP_MODEM_SetConnectTimeout() modem is fully connected. Sets a callback proving modem initializaIP_MODEM_SetInitCallback() tions. Sets a single command needed for modem IP_MODEM_SetInitString() initialization. Sets a delay when sending "+++ATH" is IP_MODEM_SetSwitchToCmdDelay() problematic. Table 22.1: embOS/IP PPP/PPPoE/Modem API function overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 485 22.6 PPPoE functions UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 486 CHAPTER 22 PPP / PPPoE (Add-on) 22.6.1 IP_PPPOE_AddInterface() Description Adds a PPPoE interface. Prototype int IP_PPPOE_AddInterface( unsigned HWIFace ); Parameter Parameter HWIFace Description [IN] Zero-based index of available network interfaces. Table 22.2: IP_PPPOE_AddInterface() parameter list Return value >= 0 Index of the interface. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 487 22.6.2 IP_PPPOE_ConfigRetries() Description Configures the number of times to resend a lost message before breaking the connection. Prototype void IP_PPPOE_ConfigRetries( unsigned HWIFace, U32 NumTries, U32 Timeout ); Parameter Parameter HWIFace NumTries Timeout Description [IN] Zero-based index of available network interfaces. [IN] Number of times the stack will resend the message. [IN] Timout in ms before a resend is triggered. Table 22.3: IP_PPPOE_ConfigRetries() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 488 CHAPTER 22 PPP / PPPoE (Add-on) 22.6.3 IP_PPPOE_Reset() Description Resets the PPPoE connection. The PPPoE layer is closed by sending a PADT if connected. Also resets the PPP connection state, but does not send any more PPP packets. Prototype void IP_PPPOE_Reset( unsigned HWIFace ); Parameter Parameter HWIFace Description [IN] Zero-based index of available network interfaces. Table 22.4: IP_PPPOE_Reset() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 489 22.6.4 IP_PPPOE_SetAuthInfo() Description Sets the authentication information for the PPPoE connection. Prototype void IP_PPPOE_SetAuthInfo(unsigned IFaceId, const char * sUser, const char * sPass ); Parameter Parameter IFaceId sUser sPass Description [IN] Zero-based index of available network interfaces. [IN] PPPoE user name. [IN] PPPoE user password. Table 22.5: IP_PPPOE_SetAuthInfo() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 490 CHAPTER 22 PPP / PPPoE (Add-on) 22.6.5 IP_PPPOE_SetUserCallback() Description Sets a callback function to inform the user about a status change. Prototype void IP_PPPOE_SetUserCallback( U32 IFaceId, IP_PPPOE_INFORM_USER_FUNC * pfInformUser ); Parameter Parameter IFaceId pfInformUser Description [IN] Zero-based index of available network interfaces. [IN] Pointer to a user function of type IP_PPPOE_INFORM_USER_FUNC which is called when a status change occurs. Table 22.6: IP_PPP_SetUserCallback() parameter list Additional Information Callback function will only be added if IP_PPPOE_AddInterface() has been called before. IP_PPPOE_INFORM_USER_FUNC is defined as follows: typedef void (IP_PPPOE_INFORM_USER_FUNC)(U32 IFaceId, U32 Status); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 491 22.7 PPP functions UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 492 CHAPTER 22 PPP / PPPoE (Add-on) 22.7.1 IP_PPP_AddInterface() Description Adds a PPP driver. Prototype int IP_PPP_AddInterface( const IP_PPP_LINE_DRIVER * pLineDriver, int ModemIndex); Parameter Parameter pLineDriver ModemIndex Description [IN] Pointer to a Structure IP_PPP_LINE_DRIVER. [IN] Modem index; Fixed to 0. Table 22.7: IP_PPP_AddInterface() parameter list Return value >= 0 Index of the interface. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 493 22.7.2 IP_PPP_OnRx() Description Receives one or more characters from the hardware. Uses IP_PPP_OnRxChar() to receive the characters one by one. Prototype void IP_PPP_OnRx( struct IP_PPP_CONTEXT * pContext, U8 * pData, int NumBytes ); Parameter Parameter pContext pData NumBytes Description [IN] Pointer to a Structure IP_PPP_CONTEXT. [IN] Pointer to a buffer which is storing the received data. [IN] Number of received bytes. Table 22.8: IP_PPP_OnRx() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 494 CHAPTER 22 PPP / PPPoE (Add-on) 22.7.3 IP_PPP_OnRxChar() Description Receives a character from the hardware. Checks if the received character is an escape character, removes the escape character if equired and stores the character into packet buffer. When a complete packet is received, it is given to the stack. Prototype void IP_PPP_OnRxChar( struct IP_PPP_CONTEXT * pContext, U8 Data ); Parameter Parameter pContext Data Description [IN] Pointer to a Structure IP_PPP_CONTEXT. [IN] 1 character. Table 22.9: IP_PPP_OnRxChar() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 495 22.7.4 IP_PPP_OnTxChar() Description Sends a character via PPP. The function checks if the character needs an escape character for the HDLC framing and sends the the escape character if required. Prototype int IP_PPP_OnTxChar( unsigned Unit ); Parameter Parameter Unit Description Typically 0. Table 22.10: IP_PPP_OnTxChar() parameter list Return value 0: More data has been sent. Keep Tx interrupt enabled. 1: No more data to send. Disable Tx interrupt if necessary. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 496 CHAPTER 22 PPP / PPPoE (Add-on) 22.7.5 IP_PPP_SetUserCallback() Description Sets a callback function to inform the user about a status change. Prototype void IP_PPP_SetUserCallback( U32 IFaceId, IP_PPP_INFORM_USER_FUNC * pfInformUser ); Parameter Parameter IFaceId pfInformUser Description [IN] Zero-based index of available network interfaces. [IN] Pointer to a user function of type IP_PPP_INFORM_USER_FUNC which is called when a status change occurs. Table 22.11: IP_PPP_SetUserCallback() parameter list Additional Information Callback function will only be added if IP_PPP_AddInterface() has been called before. IP_PPP_INFORM_USER_FUNC is defined as follows: typedef void (IP_PPP_INFORM_USER_FUNC)(U32 IFaceId, U32 Status); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 497 22.8 Modem functions UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 498 CHAPTER 22 PPP / PPPoE (Add-on) 22.8.1 IP_MODEM_Connect() Description Initializes a PPP connect on a modem using the passed AT command. Prototype int IP_MODEM_Connect( const char * sATCommand ); Parameter Parameter sATCommand Description [IN] AT command string to dial up a connection. Must not use <CR> at the end of the dial string. Typically this is the command "ATD" followed by a number to dial. Table 22.12: IP_MODEM_Connect() parameter list Return value 0: Connected != 0: Error Example IP_MODEM_Connect("ATD*99***1#"); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 499 22.8.2 IP_MODEM_Disconnect() Description Disconnects the connection established with a modem on a specific interface. Prototype void IP_MODEM_Disconnect( unsigned IFaceId ); Parameter Parameter IFaceId Description [IN] Zero-based interface index. Table 22.13: IP_MODEM_Disconnect() parameter list Example IP_MODEM_Disconnect(0); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 500 CHAPTER 22 PPP / PPPoE (Add-on) 22.8.3 IP_MODEM_GetResponse() Description Retrieves a pointer to the responses received since the last AT command sent. Prototype const char * IP_MODEM_GetResponse( unsigned IFaceId, char * pBuffer unsigned NumBytes unsigned * pNumBytesInBuffer ); Parameter Parameter IFaceId pBuffer NumBytes pNumBytesInBuffer Description [IN] Zero-based interface index. [OUT] Pointer to the receive buffer where the response will be copied to. May be NULL. [IN] Size of the buffer pointed to by pBuffer. [OUT] Number of bytes in receive buffer. May be NULL. Table 22.14: IP_MODEM_GetResponse() parameter list Return value Pointer to the last responses received in the original buffer. Example U8 aBuffer[256]; unsigned NumBytesReceived; IP_MODEM_SendString(0, "AT"); IP_MODEM_GetResponse(0, &aBuffer[0], sizeof(aBuffer), &NumBytesReceived); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 501 22.8.4 IP_MODEM_SendString() Description Sends an AT command to the modem without waiting for an answer. Prototype void IP_MODEM_SendString( unsigned IFaceId, const char * sCmd ); Parameter Parameter IFaceId sCmd Description [IN] Zero-based interface index. [IN] AT command to be sent. Table 22.15: IP_MODEM_SendString() parameter list Example IP_MODEM_SendString(0, "AT"); Additional information This routine is meant for sending simple AT commands to the modem that do not need to be checked for their response. It is not designed to be used with IP_MODEM_GetResponse() on page 500. If you intend to process the modem response please use IP_MODEM_SendStringEx() on page 502 instead. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 502 CHAPTER 22 PPP / PPPoE (Add-on) 22.8.5 IP_MODEM_SendStringEx() Description Sends an AT command to the modem and waits for the expected response with a timeout or checks for responses received in multpiple parts. Prototype int IP_MODEM_SendStringEx( unsigned IFaceId, const char * sCmd, const char * sResponse, unsigned Timeout, unsigned RecvBufOffs ); Parameter Parameter IFaceId sCmd sResponse Timeout RecvBufOffs Description [IN] Zero-based interface index. [IN] AT command to be sent. May be NULL. [IN] Expected response without <CR><LF> in front. May be NULL. [IN] Timeout to wait for any response in ms. [IN] Can be used to check for a response that is sent in multiple parts. See below for additional information. May be NULL. Table 22.16: IP_MODEM_SendStringEx() parameter list Return value 0: O.K., corect response received 1: Timeout 2: Wrong response received, check with IP_MODEM_GetResponse() Additional information Sending a new command with IP_MODEM_SendString() clears the buffer of previous received responses. RecvBufOffs can be used to check for responses that are sent by the modem in multiple responses. If not passed '0' the receive buffer will not be cleared to not clear out already received following responses from the previously sent command. RecvBufOffs id the offset in bytes from the beginning of the first received response. Being able to receive responses that are sent in multiple parts is necessary as some command may be responded with a confirm for the command sent itself and respond with a second message after an undefined time. Example sending a command and checking for its response with a timeout IP_MODEM_SendStringEx(0, "AT", "OK", 100, 0); Example for checking the SIM status of a GSM modem int r; // // Check if the modem is waiting for a SIM PIN to be entered // r = IP_MODEM_SendStringEx(0, "AT+CPIN?\r", "+CPIN: SIM PIN", 1000, 0); if (r == 0) { // // The modem is waiting for the PIN to be entered // IP_MODEM_SendString(0, "AT^SSET=1\r"); // Enable "^SSIM READY" response once // the SIM data has been read IP_OS_Delay(100); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 503 // // Enter SIM PIN. The OK response will arrive quickly. The modem then // reads data from the SIM. // IP_MODEM_SendStringEx(0, "AT+CPIN="1234"\r", "OK", 15000, 0); // // After receiving the "OK" response for the command the modem will need an // undefined time to read data from the SIM. The modem sends the response // "^SSIM READY" once it has finished. We will receive the response at an // 6 byte offset (OK<CR><LF><CR><LF>^SSIM READY). // IP_MODEM_SendStringEx(0, NULL, "^SSIM READY", 15000, 6); } else { // // The modem does not seem to wait for a PIN, check if the modem // reports "READY". This means no PIN is set for the SIM card. In this case // the modem responds with "+CPIN: READY" that will be located at offset 0 // in the recive buffer. // if (IP_MEMCMP(IP_MODEM_GetResponse(0, NULL, 0, NULL), "+CPIN: READY", 12) != 0) { IP_Panic("Unrecognized response from modem."); } } UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 504 CHAPTER 22 PPP / PPPoE (Add-on) 22.8.6 IP_MODEM_SetAuthInfo() Description Sets authentication information if needed for the connection to establish. Prototype void IP_MODEM_SetAuthInfo( unsigned IFaceId, const char * sUser, const char * sPass ); Parameter Parameter IFaceId sUser sPass Description [IN] Zero-based interface index. [IN] String containing the user name to be used. [IN] String containing the password to be used. Table 22.17: IP_MODEM_SetAuthInfo() parameter list Example IP_MODEM_SetAuthInfo(0, "User", "Pass"); Additional information Setting a user name and a password is only necessary when required by your ISP. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 505 22.8.7 IP_MODEM_SetConnectTimeout() Description Sets the connect timeout to wait IP_MODEM_Connect() to be established. for a requested connection with Prototype void IP_MODEM_SetConnectTimeout( unsigned IFaceId, unsigned ms ); Parameter Parameter IFaceId ms Description [IN] Zero-based interface index. [IN] Timeout in ms. Default: 15s. Table 22.18: IP_MODEM_SetConnectTimeout() parameter list Example IP_MODEM_SetConnectTimeout(0, 30000); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 506 CHAPTER 22 PPP / PPPoE (Add-on) 22.8.8 IP_MODEM_SetInitCallback() Description Sets a callback that is used to initialize the modem before actually starting the connection attempt. The callback is called from IP_MODEM_Connect(). Prototype void IP_MODEM_SetInitCallback( void (*pfInit)(void) ); Parameter Parameter pfInit Description [IN] Void callback routine for intialization of the modem before connecting. Table 22.19: IP_MODEM_SetInitCallback() parameter list Example static void _InitModem(void) { IP_MODEM_SendString(0, "AT"); } IP_MODEM_SetInitCallback(_InitModem); IP_MODEM_Connect("ATD*99***1#"); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 507 22.8.9 IP_MODEM_SetInitString() Description Sets an initialization string that is sent to the modem before actually starting the connection attempt. In case IP_MODEM_SetInitCallback() is used the init string is not sent. Prototype void IP_MODEM_SetInitString( const char * sInit ); Parameter Parameter sInit Description [IN] Command to be sent to the modem before connecting. Table 22.20: IP_MODEM_SetInitString() parameter list Example IP_MODEM_SetInitString("ATE0V1"); IP_MODEM_Connect("ATD*99***1#"); UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 508 CHAPTER 22 PPP / PPPoE (Add-on) 22.8.10 IP_MODEM_SetSwitchToCmdDelay() Description Sets a delay that will IP_MODEM_Disconnect(). be executed with "+++ATH" command when using Prototype void IP_MODEM_SetSwitchToCmdDelay( unsigned IFaceId, unsigned ms ); Parameter Parameter IFaceId ms Description [IN] Zero-based interface index. [IN] Timeout in ms between sending "+++" and "ATH". Table 22.21: IP_MODEM_SetSwitchToCmdDelay() parameter list Additional information Sending "+++ATH" to switch back to command mode and then hanging up the connection is fine to be sent in one in one message. For some modem this does not apply. They need some time to switch back to command mode before accepting "ATH" for hanging up. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 509 22.9 PPP data structures Function IP_PPP_CONTEXT RESEND_INFO IP_PPP_LINE_DRIVER Description Structure which stores the information about the PPP connection. A structure which stores the resend condition for different stages of the PPP connection. Structure with pointers to application related functions. Table 22.22: embOS/IP PPP data structure overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 510 CHAPTER 22 PPP / PPPoE (Add-on) 22.9.1 Structure IP_PPP_CONTEXT Description A structure which stores the information about the PPP connection. Prototype typedef struct IP_PPP_CONTEXT { PPP_SEND_FUNC * pfSend; PPP_TERM_FUNC * pfTerm; PPP_INFORM_USER_FUNC * pfInformUser; void * pSendContext; int NumBytesPrepend; U8 IFaceId; struct { U32 NumTries; I32 Timeout; } Config; struct { U8 Id; U8 aOptCnt[MAX_OPT]; PPP_LCP_STATE AState; PPP_LCP_STATE PState; RESEND_INFO Resend; U16 MRU; U32 ACCM; U32 OptMask; } LCP; struct { U8 Id; U8 aOptCnt[MAX_OPT]; PPP_CCP_STATE AState; PPP_CCP_STATE PState; RESEND_INFO Resend; U32 OptMask; } CCP; struct { U8 Id; U8 aOptCnt[MAX_OPT]; PPP_IPCP_STATE AState; PPP_IPCP_STATE PState; RESEND_INFO Resend; IP_ADDR IpAddr; IP_ADDR aDNSServer[IP_MAX_DNS_SERVERS]; U32 OptMask; } IPCP; struct { U8 UserLen; U8 abUser[64]; U8 PassLen; U8 abPass[64]; U16 Prot; U32 Data; PPP_AUTH_STATE State; RESEND_INFO Resend; U32 OptMask; } Auth; IP_PPP_LINE_DRIVER * pLineDriver; } IP_PPP_CONTEXT; UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 511 Member pfSend pfTerm pfInformUser pSendContext NumBytesPrepend IFaceId Config.NumTries Config.Timeout LCP.Id LCP.aOptCnt LCP.AState LCP.PState LCP.Resend LCP.MRU LCP.ACCM LCP.OptMask CCP.Id CCP.aOptCnt CCP.AState CCP.PState CCP.Resend CCP.OptMask IPCP.Id IPCP.aOptCnt IPCP.AState IPCP.PState IPCP.Resend IPCP.IpAddr IPCP.aDNSServer IPCP.OptMask Auth.UserLen Auth.abUser Auth.PassLen Auth.abPass Auth.Prot Description Pointer to a function which sends a packet. Pointer to a function which terminates the connection. Pointer to a callback function which informs the user about a status change of the connection. Pointer to a user callback function which is triggered when a status change of the PPP connection occurs. The size of the PPP header to be prepended when sending packets. Internal index number of the interface. Defines the number of times the stack tries to initialise a connection via PADI before giving up. Can be set via IP_PPPOE_ConfigRetries(), the default is 5. Sets the timeout between PADI configuration retries in ms, the default is 2000. Sequential ID number of the LCP packet. An array of supported LPC options. An enum of type PPP_LCP_STATE. Indicates the active status of the LPC connection. An enum of type PPP_LCP_STATE. Indicates the passive status (modem side) of the LPC connection. A structure of type RESEND_INFO. Maximum-Receive-Unit. Async-Control-Character-Map. Mask to identify the options which should be added to the LCP packet. Sequential ID number of the CCP packet. An array of supported CCP options. An enum of type PPP_CCP_STATE. Indicates the active status of the CCP connection. An enum of type PPP_CCP_STATE. Indicates the passive status (modem side) of the LPC connection. A structure of type RESEND_INFO. Mask to identify the options which should be added to the CCP packet. Sequential ID number of the IPCP packet. An array of supported IPCP options. An enum of type PPP_IPCP_STATE. Indicates the active status of the LPC connection. An enum of type PPP_IPCP_STATE. Indicates the passive status (modem side) of the LPC connection. A structure of type RESEND_INFO. An IP_ADDR to store the IP adress of the PPP interface. An IP_ADDR to store the IP adress of the PPP interface. Mask to identify the options which should be added to the IPCP packet. Length of the user name, is being set internally. User name for the PPPoE connection. Length of the user password, is being set internally. User password for the PPPoE connection. Defines the PPP authentication protocol, is set typically to PPP_PROT_PAP. Table 22.23: Structure IP_PPP_CONTEXT member list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 512 CHAPTER 22 Member Auth.State Auth.Resend pLineDriver PPP / PPPoE (Add-on) Description An enum of type PPP_AUTH_STATE. A structure of type RESEND_INFO. Pointer to a structure of type IP_PPP_LINE_DRIVER Table 22.23: Structure IP_PPP_CONTEXT member list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 513 22.9.2 Structure RESEND_INFO Description A structure which stores the resend condition for different stages of the PPP connection. Prototype typedef struct { IP_PACKET * pPacket; I32 Timeout; I32 InitialTimeout; U32 RemTries; #if IP_DEBUG const char * sPacketName; #endif } RESEND_INFO; Member pPacket Timeout InitialTimeout RemTries sPacketName Description Pointer to an IP_PACKET structure. Timeout in ms before a resend is triggered. Initial timeout in ms before a resend is triggered. Saved to be able to reset Timeout to it's original state. Counter for the remaining number of retries. (Only with IP_DEBUG >= 1.) Custom name assigned to the packet. Table 22.24: Structure RESEND_INFO member list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 514 CHAPTER 22 PPP / PPPoE (Add-on) 22.9.3 Structure IP_PPP_LINE_DRIVER Description Structure with pointers to application related functions. Prototype typedef struct { void (*pfInit) (struct IP_PPP_CONTEXT * pPPPContext); void (*pfSend) (U8 Data); void (*pfSendNext) (U8 Data); void (*pfTerminate) (U8 IFaceId); void (*pfOnPacketCompletion) (void); } IP_PPP_LINE_DRIVER; Member Description Pointer to a function which initialises the PPP connection. Pointer to a function which sends the first byte. Pointer to a function which sends the next byte. Typically pfSendNext called from an interrupt that confirms that the last byte has been sent. pfTerminate Pointer to a function which terminates the connection. Optional. Called when packet is complete. Normally used for pfOnPacketCompletion packet oriented PPP interfaces GPRS or USB modems. pfInit pfSend Table 22.25: Structure IP_PPP_LINE_DRIVER member list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 515 22.10 PPPoE resource usage The ROM usage depends on the compiler options, the compiler version and the used CPU. The memory requirements of the PPP/PPPoE modules presented in the tables below have been measured on an ARM7 and a Cortex-M3 system. Details about the further configuration can be found in the sections of the specific example. The resource usage of a typical PPPoE scenario with 1 WAN interface has been measured. 22.10.1 ROM usage on an ARM7 system The following resource usage has been measured on an ARM7 system using IAR Embedded Workbench V6.30.6, Thumb mode, no interwork, size optimization. Addon embOS/IP PPP used for PPPoE ROM approximately 7.0Kbyte Table 22.26: PPPoE ROM usage ARM7 22.10.2 ROM usage on a Cortex-M3 system The following resource usage has been measured on a Cortex-M3 system using IAR Embedded Workbench V6.30.6, size optimization. Addon embOS/IP PPP used for PPPoE ROM approximately 6.5Kbyte Table 22.27: PPPoE ROM usage Cortex-M3 22.10.3 RAM usage Addon embOS/IP PPP used for PPPoE RAM approximately 100 bytes Table 22.28: PPPoE RAM usage UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 516 CHAPTER 22 PPP / PPPoE (Add-on) 22.11 PPP resource usage The ROM usage depends on the compiler options, the compiler version and the used CPU. The memory requirements of the PPP modules presented in the tables below have been measured on an ARM7 system. Details about the further configuration can be found in the sections of the specific example. The resource usage of a typical PPP scenario without network interface and one modem connected via RS232 has been measured. 22.11.1 ROM usage on an ARM7 system The following resource usage has been measured on an ARM7 system using IAR Embedded Workbench V6.30.6, Thumb mode, no interwork, size optimization. Addon embOS/IP PPP ROM approximately 7.0 kBytes Table 22.29: PPP ROM usage ARM7 22.11.2 RAM usage Addon embOS/IP PPP RAM approximately 0.5 kBytes Table 22.30: PPP RAM usage UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 517 Chapter 23 NetBIOS (Add-on) The embOS/IP implementation of the Network Basic Input/Output System Protocol (NetBIOS) is an optional extension to embOS/IP. It can be used to resolve NetBIOS names in a local area network. All functions that are required to add NetBIOS to your application are described in this chapter. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 518 CHAPTER 23 NetBIOS (Add-on) 23.1 embOS/IP NetBIOS The embOS/IP NetBIOS implementation is an optional extension which can be seamlessly integrated into your application. It combines a maximum of performance with a small memory footprint. The NetBIOS implementation allows an embedded system to resolve NetBIOS names in the local area network. The NetBIOS module implements the relevant parts of the following Request For Comments (RFC). RFC# [RFC 1001] [RFC 1002] Description NetBIOS Concenpts and methods Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc1001.txt NetBIOS Detailed Specifications Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc1002.txt The following table shows the contents of the embOS/IP root directory: Directory Content Application Contains the example application to run the NetBIOS implementation with embOS/ IP. Inc Contains the required include files. IP Contains the NetBIOS sources, IP_Netbios.c. Supplied directory structure of embOS/IP NetBIOS package UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 519 23.2 Feature list * * * Low memory footprint. Seamless integration with the embOS/IP stack. Client based NetBIOS name resolution. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 520 CHAPTER 23 NetBIOS (Add-on) 23.3 Requirements TCP/IP stack The embOS/IP NetBIOS implementation requires the embOS/IP TCP/IP stack. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 521 23.4 NetBIOS backgrounds The Network Basic Input/Output System protocol is an API on top of the TCP/IP protocol, it provides a way of communication between separate computers within a local arena network via the session layer. NetBIOS Application layer NetBIOS API NetBIOS over TCP/IP NetBIOS name service UDP port 137 UDP IPv4 Using NetBIOS, an embOS/IP application can resolve a NetBIOS name to an IP adress in the local area network. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 522 CHAPTER 23 NetBIOS (Add-on) 23.5 API functions Function IP_NETBIOS_Init() IP_NETBIOS_Start() IP_NETBIOS_Stop() Description NetBIOS Initializes the NetBIOS Name Service client. Starts the NetBIOS client. Stops the NetBIOS client. Table 23.1: embOS/IP NetBIOS API function overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 523 23.5.1 IP_NETBIOS_Init() Description Initializes the NetBIOS Name Service client. Prototype int IP_NETBIOS_Init( U32 IFaceId, const IP_NETBIOS_NAME * paHostnames, U16 LPort ); Parameter Parameter IFaceId paHostnames LPort Description [IN] Zero-based index of available network interfaces. [IN] Pointer to an array of Structure IP_NETBIOS_NAME. Expects last index to be zero filled. [IN] Local port used for listening. Typically 137. If parameter LPort is 0, 137 will be used. Table 23.2: IP_NETBIOS_Init() parameter list Return value < 0: Error, invalid NetBIOS name in paHostnames list. > 0: Ok, Number of valid NetBIOS names assigned to the target. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 524 CHAPTER 23 NetBIOS (Add-on) 23.5.2 IP_NETBIOS_Start() Description Starts the NetBIOS client. Creates an UDP socket to receive Netbios Name Service requests. Prototype int IP_NETBIOS_Start ( U32 IFaceId ); Parameter Parameter IFaceId Description [IN] Zero-based index of available network interfaces. Table 23.3: IP_NETBIOS_Start() parameter list Return value 0: Error, could not create an UDP socket for NetBIOS. > 0: OK, number of the socket which is used for the NetBIOS Name Service. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 525 23.5.3 IP_NETBIOS_Stop() Description Stops the NetBIOS client. Closes the UDP socket. Prototype void IP_NETBIOS_Stop ( U32 IFaceId ); Parameter Parameter IFaceId Description [IN] Zero-based index of available network interfaces. Table 23.4: IP_NETBIOS_Stop() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 526 CHAPTER 23 NetBIOS (Add-on) 23.5.4 Structure IP_NETBIOS_NAME Description A structure which stores the information about the NetBIOS name. Prototype typedef struct IP_NETBIOS_NAME { char * sName; U8 NumBytes; } IP_NETBIOS_NAME; Member sName NumBytes Description [IN] Pointer to a string which stores the NetBIOS name. [IN] Length of the NetBIOS name without termination. Table 23.5: Structure IP_NETBIOS_NAME member list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 527 23.6 Resource usage The ROM usage depends on the compiler options, the compiler version and the used CPU. The memory requirements of the NetBIOS module presented in the tables below have been measured on an ARM7 and a Cortex-M3 system. Details about the further configuration can be found in the sections of the specific example. 23.6.1 ROM usage on an ARM7 system The following resource usage has been measured on an ARM7 system using IAR Embedded Workbench V6.30.6, Thumb mode, no interwork, size optimization. Addon embOS/IP NetBIOS module ROM approximately 0.8Kbyte Table 23.6: NetBIOS ROM usage ARM7 23.6.2 ROM usage on a Cortex-M3 system The following resource usage has been measured on a Cortex-M3 system using IAR Embedded Workbench V6.30.6, size optimization. Addon embOS/IP NetBIOS module ROM approximately 0.7Kbyte Table 23.7: NetBIOS ROM usage Cortex-M3 23.6.3 RAM usage Addon embOS/IP NetBIOS module RAM approximately 2.4Kbyte Table 23.8: NetBIOS RAM usage UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 528 UM07001 User & Reference Guide for embOS/IP CHAPTER 23 NetBIOS (Add-on) (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 529 Chapter 24 SNTP client (Add-on) The embOS/IP implementation of the Simple Network Time Protocol (SNTP) client is an optional extension to embOS/IP. It can be used to request a timestamp with the current time from a NTP server. All functions that are required to add SNTP client functionality to your application are described in this chapter. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 530 CHAPTER 24 SNTP client (Add-on) 24.1 embOS/IP SNTP client The embOS/IP SNTP client implementation is an optional extension which can be seamlessly integrated into your application. It combines a maximum of performance with a small memory footprint. The SNTP client implementation allows an embedded system to use real timestamps from a remote NTP server without using a RTC or to initialize a RTC. The SNTP protocol is based on SNTP v4. The SNTP client module implements the relevant parts of the following Request For Comments (RFC). RFC# [RFC 4330] [RFC 1305] Description Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc4330.txt Network Time Protocol (Version 3) - Specification, Implementation and Analysis Direct download: ftp://ftp.rfc-editor.org/in-notes/rfc1305.txt The following table shows the contents of the embOS/IP root directory: Directory IP Content Contains the SNTPc sources, IP_SNTPC.c. Supplied directory structure of embOS/IP SNTPc package UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 531 24.2 Feature list * * * Low memory footprint. Seamless integration with the embOS/IP stack. Time synchronization with a remote NTP server. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 532 CHAPTER 24 SNTP client (Add-on) 24.3 Requirements TCP/IP stack The embOS/IP SNTPc implementation requires the embOS/IP TCP/IP stack. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 533 24.4 SNTP backgrounds The SNTP protocol is an API on top of the TCP/IP protocol, it provides a way of synchronizing the target time with a local or remote NTP server over the network. SNTPc Application layer SNTPc API SNTPc over UDP/IP SNTPc service UDP port 123 UDP IPv4 Using SNTP, an embOS/IP application can synchronize its time with a NTP server either in the local network or in a remote network to use a timestamp with the current date and time or to initialize its own RTC with a good start value. 24.4.1 The NTP timestamp The NTP timestamp used is represented by a 64-bit value consisting of two 32-bit fields. The first 32-bit field contains the complete seconds passed since January 1st 1900. The second 32-bit field contains fractions of a second in 232 picoseconds. More information about the NTP timestamp can be found in RFC 1305. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 534 CHAPTER 24 SNTP client (Add-on) 24.4.2 The epoch problem (year 2036 problem) The NTP timestamp reserves only 32-bit for full seconds passed which equals a little bit more than 136 years. As the NTP time is based on January 1st 1900 this means that the timestamp will overlap back to 0 some time in 2036. A timestamp older than a reference timestamp can be interpretet as valid time as well as long as it does not count up to the reference timestamp. Based on this solution there are several possible ways of extending this period even more: * * * The simplest solution to extend the timestamp to be used for around 136 years is for the target to remember the date it was built or has its firmware changed and can then use this timestamp as reference extending the NTP timestamp for further 136 years. Storing the current year in non volatile memory using it as reference in which epoch the target runs. Using other sources as reference for the epoch such as timestamps from other sources. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 535 24.5 API functions Function Description SNTP client IP_SNTPC_ConfigTimeout() Configures request timeout. IP_SNTPC_GetTimeStampFromServer() Request timestamp from server. Table 24.1: embOS/IP SNTPc API function overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 536 CHAPTER 24 SNTP client (Add-on) 24.5.1 IP_SNTPC_ConfigTimeout() Description Configures the maximum time to wait for a response from a NTP server for a sent request. Prototype void IP_SNTPC_ConfigTimeout ( unsigned ms ); Parameter Parameter ms Description [IN] Timeout in ms to wait for a server response when requesting a timestamp. Table 24.2: IP_SNTPC_ConfigTimeout() parameter list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 537 24.5.2 IP_SNTPC_GetTimeStampFromServer() Description Request the current timestamp from a NTP server using the SNTP protocol. Prototype int IP_SNTPC_GetTimeStampFromServer( unsigned IFaceId, const char * sServer, IP_SNTP_TIMESTAMP * pTimestamp ); Parameter Parameter IFaceId sServer pTimestamp Description [IN] Zero-based index of available network interfaces. [IN] String containing either dotted decimal IP addr. (192.168.1.1) or DNS name (us.pool.ntp.org) of NTP server. [OUT] Pointer to an element of Structure IP_NTP_TIMESTAMP. Table 24.3: IP_SNTPC_GetTimeStampFromServer() parameter list Return value Label Numeric IP_SNTPC_STATE_NO_ANSWER 0 IP_SNTPC_STATE_UPDATED 1 IP_SNTPC_STATE_KOD 2 Other < 0 Description Request sent but no answer from server received within timeout. Timestamp updated from server response. Server sent Kiss-Of-Death and wants us to use another server. Error. Table 24.4: IP_SNTPC_GetTimeStampFromServer() return value list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 538 CHAPTER 24 SNTP client (Add-on) 24.5.3 Structure IP_NTP_TIMESTAMP Description A structure which stores the timestamp from a NTP request. Prototype typedef struct IP_NTP_TIMESTAMP { U32 Seconds; U32 Fractions; } IP_NTP_TIMESTAMP; Member Seconds Fractions Description Seconds passed since start of epoch, typically January 1st 1900. Fractions of a second in 232 picoseconds. Table 24.5: Structure IP_NTP_TIMESTAMP member list UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 539 24.6 Resource usage The ROM usage depends on the compiler options, the compiler version and the used CPU. The memory requirements of the NetBIOS module presented in the tables below have been measured on an ARM7 and a Cortex-M3 system. Details about the further configuration can be found in the sections of the specific example. 24.6.1 ROM usage on an ARM7 system The following resource usage has been measured on an ARM7 system using IAR Embedded Workbench V6.30.6, Thumb mode, no interwork, size optimization. Addon embOS/IP SNTP client module ROM approximately 0.5Kbyte Table 24.6: SNTP client ROM usage ARM7 24.6.2 ROM usage on a Cortex-M3 system The following resource usage has been measured on a Cortex-M3 system using IAR Embedded Workbench V6.30.6, size optimization. Addon embOS/IP SNTP client module ROM approximately 0.5Kbyte Table 24.7: SNTP client ROM usage Cortex-M3 24.6.3 RAM usage Addon embOS/IP NetBIOS module RAM approximately 24 bytes Table 24.8: SNTP client RAM usage UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 540 UM07001 User & Reference Guide for embOS/IP CHAPTER 24 SNTP client (Add-on) (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 541 Chapter 25 Debugging embOS/IP comes with various debugging options. These includes optional warning and log outputs, as well as other run-time options which perform checks at run time as well as options to drop incoming or outgoing packets to test stability of the implementation on the target system. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 542 CHAPTER 25 Debugging 25.1 Message output The debug builds of embOS/IP include a fine grained debug system which helps to analyze the correct implementation of the stack in your application. All modules of the TCP/IP stack can output logging and warning messages via terminal I/O, if the specific message type identifier is added to the log and/or warn filter mask. This approach provides the opportunity to get and interpret only the logging and warning messages which are relevant for the part of the stack that you want to debug. By default, all warning messages are activated in all embOS/IP sample configuration files. All logging messages are disabled except for the messages from the initialization and the DHCP setup phase. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 543 25.2 Testing stability embOS/IP allows to define drop-rates for both receiver an transmitter. This feature can be used to simulate packet loss. Packet loss means that one or more packets fail to reach their destination. Packet loss can be caused by a number of factors (for example, signal degradation over the network medium, faulty networking hardware, error in network applications, etc.). Two variables, IP_TxDropRate and IP_RxDropRate, are implemented to define the drop-rate while the target is running. There is no need to recompile the stack. The default value of these variables is 0, which means that no packets should be dropped from the stack. Any other value of n (for example, n = 2,3, ...) will drop every n-th packet. This allows testing the reliability of communication and performance drop. A good value to test the stability is typically around 50. To change the value of IP_TxDropRate and/or IP_RxDropRate the following steps are required: 1. 2. 3. 4. Download your embOS/IP application into the target. Start your debugger. Open the Watch window and add one or both drop-rate variables. Assign the transmit and/or receive drop-rate and start your application. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 544 CHAPTER 25 Debugging 25.3 API functions Function IP_Log() IP_Warn() IP_AddLogFilter() IP_AddWarnFilter() IP_SetLogFilter() IP_SetWarnFilter() IP_PANIC() Description Filter functions This function is called by the stack in debug builds with log & warn output (debug level > 1). In a release build, this function may not be linked in. This function is called by the stack in debug builds with log & warn output (debug level > 1). In a release build, this function may not be linked in. Adds an additional filter condition to the mask which specifies the logging messages that should be displayed. Adds an additional filter condition to the mask which specifies the warning messages that should be displayed. Sets the mask that defines which logging message should be displayed. Sets the mask that defines which warning message should be displayed. General debug functions/macros Called if the stack encounters a critical situation. Table 25.1: embOS/IP debugging API function overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 545 25.3.1 IP_AddLogFilter() Description Adds an additional filter condition to the mask which specifies the logging messages that should be displayed. Prototype void IP_AddLogFilter(U32 FilterMask); Parameter Parameter FilterMask Description Specifies which logging messages should be added to the filter mask. Refer to Message types on page 550 for a list of valid values for parameter FilterMask. Table 25.2: IP_AddLogFilter() parameter list Additional information IP_AddLogFilter() can also be used to remove a filter condition which was set before. It adds/removes the specified filter to/from the filter mask via a disjunction. Example IP_AddLogFilter(IP_MTYPE_DRIVER); // Activate driver logging messages /* * Do something */ IP_AddLogFilter(IP_MTYPE_DRIVER); // Deactivate all driver logging messages UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 546 CHAPTER 25 Debugging 25.3.2 IP_AddWarnFilter() Description Adds an additional filter condition to the mask which specifies the warning messages that should be displayed. Prototype void IP_AddWarnFilter(U32 FilterMask); Parameter Parameter FilterMask Description Specifies which warning messages should be added to the filter mask. Refer to Message types on page 550 for a list of valid values for parameter FilterMask. Table 25.3: IP_AddWarnFilter() parameter list Additional information IP_AddWarnFilter() can also be used to remove a filter condition which was set before. It adds/removes the specified filter to/from the filter mask via a disjunction. Example IP_AddWarnFilter(IP_MTYPE_DRIVER); // Activate driver warning messages /* * Do something */ IP_AddWarnFilter(IP_MTYPE_DRIVER); // Deactivate all driver warning messages UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 547 25.3.3 IP_SetLogFilter() Description Sets a mask that defines which logging message that should be logged. Logging messages are only available in debug builds of embOS/IP. Prototype void IP_SetLogFilter( U32 FilterMask ); Parameter Parameter FilterMask Description Specifies which logging messages should be displayed. Refer to Message types on page 550 for a list of valid values for parameter FilterMask. Table 25.4: IP_SetLogFilter() parameter list Additional information This function should be called from IP_X_Config(). By default, the filter condition IP_MTYPE_INIT is set. Refer to IP_X_Configure() on page 326 for more information. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 548 CHAPTER 25 Debugging 25.3.4 IP_SetWarnFilter() Description Sets a mask that defines which warning messages that should be logged. Warning messages are only available in debug builds of embOS/IP. Prototype void IP_SetWarnFilter( U32 FilterMask ); Parameter Parameter FilterMask Description Specifies which warning messages should be displayed. Refer to Message types on page 550 for a list of valid values for parameter FilterMask. Table 25.5: IP_SetWarnFilter() parameter list Additional information This function should be called from IP_X_Config(). By default, all filter conditions are set. Refer to IP_X_Configure() on page 326 for more information. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 549 25.3.5 IP_PANIC() Description This macro is called by the stack code when it detects a situation that should not be occurring and the stack can not continue. The intention for the IP_PANIC() macro is to invoke whatever debugger may be in use by the programmer. In this way, it acts like an embedded breakpoint. Prototype IP_PANIC ( const char * sError ); Additional information This macro maps to a function in debug builds only. If IP_DEBUG > 0, the macro maps to the stack internal function void IP_Panic ( const char * sError ). IP_Panic() disables all interrupts to avoid further task switches, outputs sError via terminal I/O and loops forever. When using an emulator, you should set a breakpoint at the beginning of this routine or simply stop the program after a failure. The error code is passed to the function as parameter. In a release build, this macro is defined empty, so that no additional code will be included by the linker. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 550 CHAPTER 25 Debugging 25.4 Message types The same message types are used for log and warning messages. Separate filters can be used for both log and warnings. For details, refer to IP_SetLogFilter() on page 547 and IP_SetWarnFilter() on page 548 as wells as IP_AddLogFilter() on page 545 and IP_AddLogFilter() on page 545 for more information about using the message types. Symbolic name IP_MTYPE_INIT IP_MTYPE_CORE IP_MTYPE_ALLOC IP_MTYPE_DRIVER IP_MTYPE_ARP IP_MTYPE_IP IP_MTYPE_TCP_CLOSE IP_MTYPE_TCP_OPEN IP_MTYPE_TCP_IN IP_MTYPE_TCP_OUT IP_MTYPE_TCP_RTT IP_MTYPE_TCP_RXWIN IP_MTYPE_TCP IP_MTYPE_UDP_IN IP_MTYPE_UDP_OUT IP_MTYPE_UDP IP_MTYPE_LINK_CHANGE IP_MTYPE_AUTOIP IP_MTYPE_DHCP IP_MTYPE_DHCP_EXT Description Activates output of messages from the initialization of the stack that should be logged. Activates output of messages from the core of the stack that should be logged. Activates output of messages from the memory allocating module of the stack that should be logged. Activates output of messages from the driver that should be logged. Activates output of messages from ARP module that should be logged. Activates output of messages from IP module that should be logged. Activates output of messages from TCP module that should be logged when a TCP connection gets closed. Activates output of messages from TCP module that should be logged when a TCP connection gets opened. Activates output of messages from TCP module that should be logged if a TCP packet is received. Activates output of messages from TCP module that should be logged if a TCP packet is sent. Activates output of messages from TCP module regarding TCP roundtrip time. Activates output of messages from TCP module regarding peer TCP Rx window size. Activates output of messages from TCP that module should be logged. Activates output of messages from UDP module that should be logged when a UDP packet is received. Activates output of messages from UDP module that should be logged if a UDP packet is sent. Activates output of messages from UDP module that should be logged if a UDP packet is sent or received. Activates output of messages regarding to the link change process. Activates output of from the AutoIP module that should be logged. Activates output of messages from DHCP client module that should be logged. Activates output of optional messages from DHCP client module that should be logged. Table 25.6: embOS/IP message types UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 551 Symbolic name IP_MTYPE_APPLICATION IP_MTYPE_ICMP IP_MTYPE_NET_IN IP_MTYPE_NET_OUT IP_MTYPE_PPP IP_MTYPE_SOCKET_STATE IP_MTYPE_SOCKET_READ IP_MTYPE_SOCKET_WRITE IP_MTYPE_SOCKET IP_MTYPE_DNSC IP_MTYPE_ACD Description Activates output of messages from user application related modules that should be logged. Activates output of messages from the ICMP module that should be logged. Activates output of messages from NET_IN module that should be logged. Activates output of messages from NET_OUT module that should be logged. Activates output of messages from PPP modules that should be logged. Activates output of messages from socket module that should be logged when state has been changed. Activates output of messages from socket module that should be logged if a socket is used to read data. Activates output of messages from socket module that should be logged if a socket is used to write data Activates all socket related output messages. Activates output of messages from DNS client module that should be logged. Activates output of messages from address conflict module that should be logged. Table 25.6: embOS/IP message types UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 552 CHAPTER 25 Debugging 25.5 Using a network sniffer to analyse communication problems Using a network sniffer to analyze your local network traffic may give you a deeper understanding of the data that is being sent in your network. For this purpose you can use several network sniffers. Some of them are available for free such as Wireshark. An example of a network sniff using Wireshark is shown in the screenshot below: UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 553 Chapter 26 OS integration embOS/IP is designed to be used in a multitasking environment. The interface to the operating system is encapsulated in a single file, the IP/OS interface. For embOS, all functions required for this IP/OS interface are implemented in a single file which comes with embOS/IP. This chapter provides descriptions of the functions required to fully support embOS/ IP in multitasking environments. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 554 CHAPTER 26 OS integration 26.1 General information The complexity of the IP/OS Interface depends on the task model selected. Refer to Tasks and interrupt usage on page 21 for detailed informations about the different task models. All OS interface functions for embOS are implemented in IP_OS_embOS.c which is located in the root folder of the IP stack. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 555 26.2 OS layer API functions Function Description General macros IP_OS_Delay() Blocks the calling task for a given time. IP_OS_DisableInterrupt() Disables interrupts. IP_OS_EnableInterrupt() Enables interrupts. Returns the current system time in ticks. Return the current system time in ms. On 32-bit systems, the IP_OS_GetTime32() value will wrap around after approximately 49.7 days. This is taken into account by the stack. Creates and initializes all objects required for task synchronization. These are 2 events (for IP_Task and IP_OS_Init() IP_RxTask) and one semaphore for protection of critical code which may not be executed from multiple task at the same time. The stack requires a single lock, typically a resource semaphore or mutex. This function locks this object, guarding sections of the stack code against other IP_OS_Lock() tasks. If the entire stack executes from a single task, no functionality is required here. Unlocks the single lock used locked by a previous call IP_OS_Unlock() to IP_OS_Lock(). IP_Task synchronization Wakes the IP_Task if it is waiting for a NET-event or IP_OS_SignalNetEvent() timeout in the function IP_OS_WaitNetEvent(). Called from IP_Task only. Blocks until the timeout expires or a NET-event occurs, meaning IP_OS_WaitNetEvent() IP_OS_SignalNetEvent() is called from an other task or ISR. IP_RxTask synchronization Wakes the IP_RxTask if it is waiting for a NET-event or IP_OS_SignalRxEvent() timeout in the function IP_OS_WaitRxEvent(). Optional. Called from IP_RxTask, if it is used to receive data. Blocks until the timeout expires or a IP_OS_WaitRxEvent() NET-event occurs, meaning IP_OS_SignalRxEvent() is called from the ISR. Application task synchronization Suspend a task which needs to wait for a object. This IP_OS_WaitItem() object is identified by a pointer to it and can be of any type, for example a socket. Suspend a task which needs to wait for a object. This object is identified by a pointer to it and can be of any IP_OS_WaitItemTimed() type, for example a socket. The second parameter defines the maximum time in timer ticks until the event have to be signaled. Sets an event object to signaled state, or resumes IP_OS_SignalItem() tasks which are waiting at the event object. Function is called from a task, not an ISR. Table 26.1: Target OS interface function list 26.2.1 Examples OS interface routine for embOS All OS interface routines are implemented in IP_OS_embOS.c which is located in the root folder of the IP stack. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 556 UM07001 User & Reference Guide for embOS/IP CHAPTER 26 OS integration (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 557 Chapter 27 Performance & resource usage This chapter covers the performance and resource usage of embOS/IP. It contains information about the memory requirements in typical systems which can be used to obtain sufficient estimates for most target systems. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 558 CHAPTER 27 Performance & resource usage 27.1 Memory footprint embOS/IP is designed to fit many kinds of embedded design requirements. Several features can be excluded from a build to get a minimal system. Note that the values are only valid for the given configurations. 27.1.1 ARM7 system The following table shows the hardware and the toolchain details of the project: Detail CPU Tool chain Model Compiler options Description ARM7 IAR Embedded Workbench for ARM V6.30.6 ARM7, Thumb instructions; no interwork; Highest size optimization; Table 27.1: ARM7 sample configuration 27.1.1.1 ROM usage The following table shows the ROM requirement of embOS/IP: Description embOS/IP - complete stack ROM approximately 19.0Kbytes The memory requirements of a interface driver is about 1.5 - 2.0Kbytes. 27.1.1.2 RAM usage The following table shows the RAM requirement of embOS/IP: Description embOS/IP - complete stack w/o buffers UM07001 User & Reference Guide for embOS/IP RAM approximately 1.5Kbytes (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 559 27.1.2 Cortex-M3 system The following table shows the hardware and the toolchain details of the project: Detail CPU Tool chain Model Compiler options Description Cortex-M3 IAR Embedded Workbench for ARM V6.30.6 Cortex-M3 Highest size optimization; Table 27.2: ARM7 sample configuration 27.1.2.1 ROM usage The following table shows the ROM requirement of embOS/IP: Description embOS/IP - complete stack ROM approximately 19Kbytes The memory requirements of a interface driver is about 1.5 - 2.0Kbytes. 27.1.2.2 RAM usage The following table shows the RAM requirement of embOS/IP: Description embOS/IP - complete stack w/o buffers UM07001 User & Reference Guide for embOS/IP RAM approximately 4.5Kbytes (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 560 CHAPTER 27 Performance & resource usage 27.2 Performance 27.2.1 ARM7 system Detail CPU Tool chain Model Compiler options Description ARM7 with integrated MAC running with 48Mhz IAR Embedded Workbench for ARM V6.30.6 ARM7, Thumb instructions; no interwork; Highest speed optimization; Table 27.3: ARM7 sample configuration Memory configuration #define ALLOC_SIZE 0xD000 IP_AddBuffers(12, 256); IP_AddBuffers(18, mtu + 16); IP_ConfTCPSpace(8 * (mtu-40), 8 * (mtu-40)); Driver configuration #define NUM_RX_BUFFERS (2 * 12 + 1) Measurements The following table shows the send and receive speed of embOS/IP: Speed [Mbytes per second] Description TCP - socket interface Send speed Receive speed approximately 9.0 approximately 7.5 TCP - zero-copy interface Send speed Receive speed approximately 9.0 approximately 11.7 The performance of any network will depend on several considerations, including the length of the cabling, the size of packets, and the amount of traffic. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 561 27.2.2 Cortex-M3 system Detail CPU Tool chain Model Compiler options Description Cortex-M3 with integrated MAC running with 96Mhz IAR Embedded Workbench for ARM V6.30.6 Cortex-M3 Highest speed optimization; Table 27.4: ARM7 sample configuration Memory configuration #define ALLOC_SIZE 0x10000 IP_AddBuffers(12, 256); IP_AddBuffers(12, mtu + 16); IP_ConfTCPSpace(9 * (mtu-40), 9 * (mtu-40)); Driver configuration #define NUM_RX_BUFFERS #define BUFFER_SIZE (36) (256) Measurements The following table shows the send and receive speed of embOS/IP: Speed [Mbytes per second] Description TCP - socket interface Send speed Receive speed approximately 9.4 approximately 11.7 TCP - zero-copy interface Send speed Receive speed approximately 9.4 approximately 11.8 The performance of any network will depend on several considerations, including the length of the cabling, the size of packets, and the amount of traffic. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 562 UM07001 User & Reference Guide for embOS/IP CHAPTER 27 Performance & resource usage (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 563 Chapter 28 Appendix A - File system abstraction layer UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 564 CHAPTER 28 Appendix A - File system abstraction layer 28.1 File system abstraction layer This section provides a description of the file system abstraction layer used by embOS/IP applications which require access to a data storage medium. The file system abstraction layer is supplied with the embOS/IP web server and the embOS/IP FTP server. Three file system abstraction layer implementations are available: File name Description IP_FS_FS.c Mapping of the embOS/IP file system abstraction layer functions to the emFile functions. IP_FS_RO.c Implementation of a read-only file system. Typically used in a web server application. IP_FS_WIN32.c Mapping of the embOS/IP file system abstraction layer functions to the Windows file I/O functions. Supplied implementations of the file system abstraction layer UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 565 28.2 File system abstraction layer function table embOS/IP uses a function table to call the appropriate file system function. Data structure typedef struct { // // Read only file operations. These have to be present on ANY file system, // even the simplest one. // void * (*pfOpenFile) ( const char * sFilename, const char * sOpenFlags ); int (*pfCloseFile) ( void * hFile ); int (*pfReadAt) ( void * hFile, void * pBuffer, U32 Pos, U32 NumBytes ); long (*pfGetLen) ( void * hFile ); // // Directory query operations. // void (*pfForEachDirEntry) ( void * pContext, const char * sDir, void (*pf) (void * pContext, void * pFileEntry)); void (*pfGetDirEntryFileName) ( void * pFileEntry, char * sFileName, U32 SizeOfBuffer ); U32 (*pfGetDirEntryFileSize) ( void * pFileEntry, U32 * pFileSizeHigh ); int (*pfGetDirEntryFileTime) ( void * pFileEntry ); U32 (*pfGetDirEntryAttributes) ( void * pFileEntry ); // // Write file operations. // void * (*pfCreate) ( const char * sFileName ); void * (*pfDeleteFile) ( const char * sFilename ); int (*pfRenameFile) ( const char * sOldFilename, const char * sNewFilename ); int (*pfWriteAt) ( void * hFile, void * pBuffer, U32 Pos, U32 NumBytes ); // // Additional directory operations // int (*pfMKDir) (const char * sDirName); int (*pfRMDir) (const char * sDirName); // // Additional operations // int (*pfIsFolder) (const char * sPath); int (*pfMove) (const char * sOldFilename, const char * sNewFilename); } IP_FS_API; UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 566 CHAPTER 28 Appendix A - File system abstraction layer Elements of IP_FS_API Function Description Read only file system functions (required) Pointer to a function that creates/opens a pfOpenFile file and returns the handle of these file. pfCloseFile Pointer to a function that closes a file. pfReadAt Pointer to a function that reads a file. Pointer to a function that returns the length pfGetLen of a file. Directory query operations Pointer to a function which is called for each pfForEachDirEntry directory entry. Pointer to a function that returns the name pfGetDirEntryFileName of a file entry. Pointer to a function that returns the size of pfGetDirEntryFileSize a file. Pointer to a function that returns the timepfGetDirEntryFileTime stamp of a file. Pointer to a function that returns the pfGetDirEntryAttributes attributes of a directory entry. Write file operations pfCreate Pointer to a function that creates a file. pfDeleteFile Pointer to a function that deletes a file. pfRenameFile Pointer to a function that renames a file. pfWriteAt Pointer to a function that writes a file. Additional directory operations (optional) Pointer to a function that creates a direcpfMKDir tory. Pointer to a function that deletes a direcpfRMDir tory. Additional operations (optional) Pointer to a function that checks if a path is pfIsFolder a folder. Pointer to a function that moves a file or pfMove directory. Table 28.1: embOS/IP file system API function overview UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 567 28.2.1 emFile interface The embOS/IP web server and FTP server are shipped with an interface to emFile, SEGGER's file system for embedded applications. It is a good example how to use a real file system with the embOS/IP web server / FTP server. /* Excerpt from IP_FS_FS.c */ const IP_FS_API IP_FS_FS = { // // Read only file operations. // _FS_Open, _Close, _ReadAt, _GetLen, // // Simple directory operations. // _ForEachDirEntry, _GetDirEntryFileName, _GetDirEntryFileSize, _GetDirEntryFileTime, _GetDirEntryAttributes, // // Simple write type file operations. // _Create, _DeleteFile, _RenameFile, _WriteAt, // // Additional directory operations // _MKDir, _RMDir, // // Additional operations // _IsFolder, _Move }; The emFile interface is used in all SEGGER Eval Packages. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 568 CHAPTER 28 Appendix A - File system abstraction layer 28.2.2 Read-only file system The embOS/IP web server and FTP server are shipped with a very basic implementation of a read-only file system. It is a good solution if you use embOS/IP without a real file system like emFile. /* Excerpt from FS_RO.c */ const IP_WEBS_FS_API IP_FS_ReadOnly = { // // Read only file operations. // _FS_RO_FS_Open, _FS_RO_Close, _FS_RO_ReadAt, _FS_RO_GetLen, // // Simple directory operations. // NULL, NULL, NULL, NULL, NULL, // // Simple write type file operations. // NULL, NULL, NULL, NULL, // // Additional directory operations // NULL, NULL, // // Additional operations // NULL, NULL }; The read-only file system can be used in the example applications. It is sufficient, if the server should only deliver predefined files which are hardcoded in the sources of your application. It is used by default with the embOS/IP Web server example application. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 569 28.2.3 Using the read-only file system The read-only file system relies on an array of directory entries. A directory entry consists of a file name, a pointer to the data and an entry for the file size in bytes. This array of directory entries will be searched if a client requests a page. /* Excerpt from FS_RO.c */ typedef struct { const char * sFilename; const unsigned char * pData; unsigned int FileSize; } DIR_ENTRY; #include #include #include #include "webdata\generated\embos.h" "webdata\generated\index.h" "webdata\generated\segger.h" "webdata\generated\stats.h" /* /* /* /* DIR_ENTRY _aFile[] = { /* file name file array current size /* ----------------------------{ "/embos.htm", embos_file, EMBOS_SIZE { "/index.htm", index_file, INDEX_SIZE { "/segger.gif", segger_file, SEGGER_SIZE { "/stats.htm", stats_file, STATS_SIZE { 0 } }; HTML page */ HTML page */ segger.gif */ HTML page */ */ */ }, }, }, }, The example source files can easily be replaced. To build new contents for the readonly file system the following steps are required: 1. 2. 3. 4. Copy the file which should be included in the read-only file system into the folder: IP\IP_FS\FS_RO\webdata\html\ Use an text editor (for example, Notepad) to edit the batch file m.bat. The batch file is located under: IP\IP_FS\FS_RO\webdata\. Add the file which should be built. For example: If your file is called example.htm, you have to add the following line to m.bat: call cc example htm m.bat calls cc.bat. cc.bat uses bin2C.exe an utility which converts any file to a standard C array. The new files are created in the folder: IP\IP_FS\FS_RO\webdata\generated\ Add the new source code file (for example, example.c) into your project. To add the new file to your read-only file system, you have to add the new file to the DIR_ENTRY array _aFile[] and include the generated header file (for example, example.h) in FS_RO.c. The expanded definition of _aFile[] should look like: #include #include #include #include #include "webdata\generated\embos.h" "webdata\generated\index.h" "webdata\generated\segger.h" "webdata\generated\stats.h" "webdata\generated\example.h" /* /* /* /* /* HTML page */ HTML page */ segger.gif */ HTML page */ NEW HTML page */ DIR_ENTRY _aFile[] = { /* file name file array current size /* ----------------------------{ "/embos.htm", embos_file, EMBOS_SIZE { "/index.htm", index_file, INDEX_SIZE { "/segger.gif", segger_file, SEGGER_SIZE { "/stats.htm", stats_file, STATS_SIZE { "/example.htm", example_file, EXAMPLE_SIZE { 0 } }; 5. */ */ }, }, }, }, }, Recompile your application. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 570 CHAPTER 28 Appendix A - File system abstraction layer 28.2.4 Windows file system interface The embOS/IP web server and FTP server is shipped with an implementation. const IP_FS_API IP_FS_Win32 = { // // Read only file operations. // _IP_FS_WIN32_Open, _IP_FS_WIN32_Close, _IP_FS_WIN32_ReadAt, _IP_FS_WIN32_GetLen, // // Simple directory operations. // _IP_FS_WIN32_ForEachDirEntry, _IP_FS_WIN32_GetDirEntryFileName, _IP_FS_WIN32_GetDirEntryFileSize, _IP_FS_WIN32_GetDirEntryFileTime, _IP_FS_WIN32_GetDirEntryAttributes, // // Simple write type file operations. // _IP_FS_WIN32_Create, _IP_FS_WIN32_DeleteFile, _IP_FS_WIN32_RenameFile, _IP_FS_WIN32_WriteAt, // // Additional directory operations // _IP_FS_WIN32_MakeDir, _IP_FS_WIN32_RemoveDir // // Additional operations // _IP_FS_WIN32_IsFolder, _IP_FS_WIN32_Move }; The Windows file system interface is supplied with the FTP and the Web server addon packages. It is used by default with the embOS/IP FTP server application. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 571 Chapter 29 Glossary UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 572 CHAPTER 29 Glossary ARP Address Resolution Protocol. CPU Central Processing Unit. The "brain" of a microcontroller; the part of a processor that carries out instructions. DHCP Dynamic Host Configuration Protocol. DNS Domain Name System. EOT End Of Transmission. FIFO First-In, First-Out. FTP File Transfer Protocol. HTML Hypertext Markup Language. HTTP Hypertext Transfer Protocol. ICMP Internet Control Message Protocol. IP Internet Protocol. ISR Interrupt Service Routine. The routine is called automatically by the processor when an interrupt is acknowledged. ISRs must preserve the entire context of a task (all registers). LAN Local Area Network. MAC Media Access Control. NIC Network Interface Card. PPP Point-to-Point Protocol. RFC Request For Comments. RIP Routing Information Protocol. RTOS Real-time Operating System. Scheduler The program section of an RTOS that selects the active task, based on which tasks are ready to run, their relative priorities, and the scheduling system being used. SLIP Serial Line Internet Protocol. SMTP Simple Mail Transfer Protocol. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 573 Stack Superloop Task An area of memory with LIFO storage of parameters, automatic variables, return addresses, and other information that needs to be maintained across function calls. In multitasking systems, each task normally has its own stack. A program that runs in an infinite loop and uses no real-time kernel. ISRs are used for real-time parts of the software. A program running on a processor. A multitasking system allows multiple tasks to execute independently from one another. TCP Transmission Control Protocol. TFTP Trivial File Transfer Protocol. Tick The OS timer interrupt. Usually equals 1 ms. UDP User Datagram Protocol. UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 574 UM07001 User & Reference Guide for embOS/IP CHAPTER 29 Glossary (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 575 Index C Compile-time configuration ................. 330 D Debugging IP_Panic() ...................................... 549 DHCP client IP_DHCPC_Activate() ....................... 226 IP_DHCPC_ConfigOnActivate() .......... 227 IP_DHCPC_ConfigOnFail() ................. 228 IP_DHCPC_ConfigOnLinkDown() ........ 229 IP_DHCPC_Halt() .....................231, 233 IP_DHCPC_Renew() ......................... 232 E embOS/IP Features ...........................................18 Integrating into your system ...............32 layers ..............................................19 F FS abstraction layer emFile interface .............................. 567 I IP stack ACD functions IP_ACD_Activate() ........................... 258 IP_ACD_Config() ............................. 259 IP stack AutoIP functions IP_AutoIP_Activate() ....................... 250 IP_AutoIP_Halt() ............................. 251 IP_AutoIP_SetStartIP() .................... 253 IP_AutoIP_SetUserCallback ............... 252 IP stack configuration functions IP_AddBuffers() ................................48 IP_AddEtherInterface() ......................49 IP_AddLoopbackInterface() .................50 IP_AllowBackpressure() ......................51 IP_ARP_ConfigAgeout() ......................53 IP_ARP_ConfigAgeoutNoReply() ..........54 IP_ARP_ConfigAgeoutSniff() ...............55 UM07001 User & Reference Guide for embOS/IP IP_ARP_ConfigAllowGratuitousARP() .... 56 IP_ARP_ConfigMaxPending() .............. 57 IP_ARP_ConfigMaxRetries() ................ 58 IP_ARP_ConfigNumEntries() ............... 59 IP_AssignMemory() ........................... 52 IP_ConfigOffCached2Uncached() ......... 61 IP_ConfigTCPSpace() ........................ 60 IP_DisableIPRxChecksum() ................ 62 IP_DNS_GetServer() ......................... 63 IP_DNS_GetServerEx() ...................... 64 IP_DNS_SetMaxTTL() ........................ 65 IP_DNS_SetServer() ......................... 66 IP_DNS_SetServerEx() ...................... 67 IP_EnableIPRxChecksum() ................. 68 IP_GetPrimaryIFace() ........................ 69 IP_ICMP_Add() ................................. 70 IP_ICMP_DisableRxChecksum() .......... 71 IP_ICMP_EnableRxChecksum() ........... 72 IP_IGMP_Add() ................................ 73 IP_IGMP_JoinGroup() ........................ 74 IP_IGMP_LeaveGroup() ..................... 75 IP_NI_ConfigPHYAddr() ....................106 IP_NI_ConfigPHYMode() ...................107 IP_NI_ConfigPoll() ...........................108 IP_NI_ForceCaps() ...........................109 IP_NI_SetTxBufferSize() ...................110 IP_PHY_DisableCheck() ..................... 76 IP_RAW_Add() ................................. 77 IP_SetAddrMask() ............................. 78 IP_SetAddrMaskEx() ......................... 79 IP_SetGWAddr() ............................... 80 IP_SetHWAddr() ............................... 81 IP_SetHWAddrEx() ............................ 82 IP_SetMTU() .................................... 83 IP_SetPrimaryIFace() ........................ 84 IP_SetSupportedDuplexModes() ......... 85 IP_SetTTL() ..................................... 86 IP_SOCKET_ConfigSelectMultiplicator() 87 IP_SOCKET_SetDefaultOptions() ......... 88 IP_SOCKET_SetLimit() ...................... 89 IP_TCP_Add() .................................. 90 IP_TCP_DisableRxChecksum() ............ 91 IP_TCP_EnableRxChecksum() ............. 92 (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG 576 IP_TCP_Set2MSLDelay() .................... 93 IP_TCP_SetConnKeepaliveOpt() .......... 94 IP_TCP_SetRetransDelayRange() ......... 95 IP_UDP_Add() .................................. 96 IP_UDP_DisableRxChecksum() ............ 97 IP_UDP_EnableRxChecksum() ............ 98 IP stack DHCP server functions IP_DHCPS_ConfigDNSAddr() ............ 238 IP_DHCPS_ConfigGWAddr() .............. 239 IP_DHCPS_ConfigMaxLeaseTime() ..... 240 IP_DHCPS_ConfigPool() ................... 241 IP_DHCPS_Halt() ............................ 242 IP_DHCPS_Init() ............................. 243 IP_DHCPS_Start() ........................... 244 IP stack functions IP_AddAfterInitHook() ..................... 112 IP_AddStateChangeHook() ............... 113 IP_Alloc() ...................................... 114 IP_Connect() .................................. 115 IP_Disconnect() .............................. 116 IP_Err2Str() ................................... 117 IP_Free() ....................................... 118 IP_GetAddrMask() ........................... 119 IP_GetCurrentLinkSpeed() ............... 120 IP_GetCurrentLinkSpeedEx() ............ 121 IP_GetIPAddr() ........................ 122-124 IP_GetIPPacketInfo() ....................... 125 IP_GetRawPacketInfo() .................... 126 IP_GetVersion() .............................. 127 IP_ICMP_SetRxHook() ..................... 128 IP_IFaceIsReady() ........................... 129 IP_IFaceIsReadyEx() ....................... 130 IP_IsExpired() ................................ 131 IP_PrintIPAddr() ............................. 132 IP_ResolveHost() ............................ 133 IP_SendPacket() ............................. 134 IP_SendPing() ................................ 135 IP_SendPingEx() ............................. 136 IP_SetIFaceConnectHook() ............... 137 IP_SetIFaceDisconnectHook() ........... 138 IP_SetRxHook() .............................. 139 IP stack management functions IP_DeInit() .................................... 100 IP_Exec() ....................................... 104 IP_Init() ........................................ 101 IP_RxTask() ................................... 103 IP_Task() ....................................... 102 IP stack Modem functions IP_MODEM_Connect() ..................... 498 IP_MODEM_Disconnect() .................. 499 IP_MODEM_GetResponse() ............... 500 IP_MODEM_SendString() ................. 501 IP_MODEM_SendStringEx() .............. 502 IP_MODEM_SetAuthInfo() ................ 504 IP_MODEM_SetConnectTimeout() ..... 505 IP_MODEM_SetInitCallback() ............ 506 IP_MODEM_SetInitString() ............... 507 IP_MODEM_SetSwitchToCmdDelay() .. 508 IP stack NetBIOS functions IP_NETBIOS_Init() .......................... 523 IP_NETBIOS_Start() ........................ 524 IP_NETBIOS_Stop() ........................ 525 IP stack PPP functions IP_PPP_AddInterface() .................... 492 IP stack PPPoE functions IP_PPPOE_AddInterface() ................. 486 IP_PPPOE_ConfigRetries() ................ 487 UM07001 User & Reference Guide for embOS/IP Index IP_PPPOE_Reset() ........................... 488 IP_PPPOE_SetAuthInfo() .................. 489 IP_PPPOE_SetUserCallback() ............ 490 IP stack SNTP client functions IP_SNTPC_ConfigTimeout ................. 536 IP_SNTPC_GetTimeStampFromServer 537 IP stack UPnP functions IP_UPNP_Activate() ......................... 276 IP stack VLAN functions IP_VLAN_AddInterface() .................. 284 IP stack Web server functions Callback IP_WEBS_pfMethod ............ 402 IP_UTIL_BASE64_Decode() .............. 391 IP_UTIL_BASE64_Encode() ............... 392 IP_WEBS_AddFileTypeHook() ............ 369 IP_WEBS_AddVFileHook() ................ 384 IP_WEBS_CompareFileNameExt() ...... 375 IP_WEBS_ConfigSendVFileHeader() ... 370 IP_WEBS_ConfigSendVFileHookHeader() . 371 IP_WEBS_DecodeAndCopyStr() ......... 382 IP_WEBS_DecodeString() ................. 383 IP_WEBS_GetDecodedStrLen() ......... 380 IP_WEBS_GetNumParas() ................. 376 IP_WEBS_GetParaValue() ................. 377 IP_WEBS_GetParaValuePtr() ............. 378 IP_WEBS_GetURI() ......................... 381 IP_WEBS_METHOD_AddHook() ......... 387 IP_WEBS_METHOD_CopyData() ........ 390 IP_WEBS_OnConnectionLimit() ......... 360 IP_WEBS_Process() ......................... 358 IP_WEBS_ProcessLast() ................... 359 IP_WEBS_Redirect() ........................ 372 IP_WEBS_Reset() ............................ 373 IP_WEBS_RetrieveUserContext() ....... 366 IP_WEBS_SendHeader() .................. 374 IP_WEBS_SendMem() ...................... 361 IP_WEBS_SendString() .................... 362 IP_WEBS_SendStringEnc() ............... 363 IP_WEBS_SendUnsigned() ................ 364 IP_WEBS_SetFileInfoCallback() ......... 365 IP_WEBS_StoreUserContext() ........... 367 Structure IP_WEBS_FILE_INFO ......... 396 Structure WEBS_ACCESS_CONTROL .. 394 Structure WEBS_APPLICATION .......... 395 Structure WEBS_CGI ....................... 393 Structure WEBS_FILE_TYPE .............. 399 Structure WEBS_FILE_TYPE_HOOK .... 400 Structure WEBS_METHOD_HOOK ...... 401 Structure WEBS_VFILE_APPLICATION 397 Structure WEBS_VFILE_HOOK ........... 398 Web server data structures ............... 393 L Logging functions IP_AddLogFilter() ............................ 545 IP_AddWarnFilter() .......................... 546 IP_SetLogFilter() ............................. 547 IP_SetWarnFilter() ........................... 548 N Network interface drivers ATMEL AT91SAM7X .......................... 299 ATMEL AT91SAM9260 ...................... 303 DAVICOM DM9000 ........................... 306 FREESCALE ColdFire MCF5329 .......... 309 (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG Index NXP LPC23xx/24xx .......................... 314 ST STR912 ..................................... 316 O OS integration ................................... 553 API functions .................................. 555 R RAW zero-copy IP_RAW_Alloc() ............................... 211 IP_RAW_Close() .............................. 212 IP_RAW_Free() ............................... 213 IP_RAW_GetDataPtr() ...................... 214 IP_RAW_GetDataSize() .................... 215 IP_RAW_GetDestAddr() .................... 216 IP_RAW_GetIFIndex() ...................... 217 IP_RAW_GetSrcAddr() ..................... 218 IP_RAW_Open() .............................. 219 IP_RAW_Send() .............................. 220 IP_RAW_SendAndFree() ................... 221 577 IP_UDP_GetDestAddr() .....................196 IP_UDP_GetFPort() ..........................197 IP_UDP_GetIFIndex() .......................198 IP_UDP_GetLPort() ..........................199 IP_UDP_Open() ...............................201 IP_UDP_OpenEx() ............................202 IP_UDP_Send() ...............................203 IP_UDP_SendAndFree() ....................204 Utility functions IP_UTIL_BASE64_Decode() ...............391 IP_UTIL_BASE64_Encode() ...............392 S Socket functions accept() ......................................... 143 bind() ............................................ 144 closesocket() .................................. 145 connect() ....................................... 146 gethostbyname() ............................. 148 getpeername() ................................ 150 getsockname() ................................ 151 listen() ........................................... 156 recv() ............................................ 157 recvfrom() ...................................... 158 select() .......................................... 159 send() ........................................... 162 sendto() ......................................... 163 setsockopt() ................................... 164 socket() ......................................... 167 Structure hostent ............................ 172 Structure in_addr ............................ 171 Structure sockaddr .......................... 169 Structure sockaddr_in ...................... 170 Syntax, conventions used ...................... 9 T TCP zero-copy IP_TCP_Alloc() ................................ 180 IP_TCP_Free() ................................ 181 IP_TCP_Send() ............................... 182 IP_TCP_SendAndFree() .................... 183 TFTP IP_TFTP_InitContext() ..................... 473 IP_TFTP_RecvFile() .......................... 474 IP_TFTP_SendFile() ......................... 475 IP_TFTP_ServerTask() ...................... 476 U UDP zero-copy IP_UDP_Alloc() ............................... 190 IP_UDP_Close() .............................. 191 IP_UDP_FindFreePort() ..................... 192 IP_UDP_Free() ................................ 193 IP_UDP_GetDataPtr() ....................... 195 IP_UDP_GetDataSize() ..................... 194 UM07001 User & Reference Guide for embOS/IP (c) 2007 - 2014 SEGGER Microcontroller GmbH & Co. KG