Specifications

1–16 Chapter 1: Using the NicheStack TCP/IP Stack
Nios II Simple Socket Server Overview
Using the NicheStack TCP/IP Stack - Nios II Edition Tutorial June 2011 Altera Corporation
Nios II Simple Socket Server Overview
The following sections describe the Nios II Simple Socket Server:
■ “Software Naming Conventions” on page 1–16—Identifies the naming convention
used in the tutorial files.
■ “Software Architecture” on page 1–17—Describes the architectural model of a
Nios II software application and how it fits with the rest of the Nios II system
software components.
■ “MicroC-OS/II Resources” on page 1–19—Describes the tasks, queue, event flag,
and semaphores that implement the Nios II Simple Socket Server software
application.
■ “NicheStack TCP/IP Stack Initialization” on page 1–20—Describes the required
tasks and functions of the tutorial to establish and maintain the Ethernet TCP/IP
socket connection.
■ “Nios II Simple Socket Server Implementation Details” on page 1–21—Describes
the structure that maintains the socket connection and the functions for each
software component, including
main() , MicroC/OS-II initialization, and the
details of the SSS and LED software modules.
Software Naming Conventions
The Nios II Simple Socket Server uses capitalized acronym prefixes to identify public
resources for each software module, and lowercase letters with underscores to
indicate a private resource or function used internally to a software module. Table 1–2
shows the software module acronym identifiers.
Table 1–2. Software Module Acronyms and Names
Acronym Name
SSS Nios II Simple Socket Server software module
LED LED management software module
OS MicroC/OS-II RTOS software component