MotoHawk Network Stack Definition

Declares the kind of software TCP/IP network stack to use for each of the ethernet adapters that reference this definition.

Block ID

Network Stack Definition





Block Parameters

Setup Tab

Parameter Field Values Comments/Description
Stack Name Single quote enclosed alphanumeric A unique name that identifies this stack instance. Must be C-legal.
Resource Drop-down list Module resource.

Stack Setup Tab

The Stack Setup tab contains stack specific configuration and will change based on the kind of stack selected

Specific Parameters
Values Comments/Description
Use Referenced Worker Task Check Box (enable) Allow the block to reference a private (worker) task specified via Task Definition when checked.
Worker Task name Single quote enclosed alpha-numeric. The name of the task that will be used for TCP/IP thread processing in the lwIP stack.

When Use Referenced Worker Task is checked this task name is a reference to a Task Definition that is configured as a private (worker) task. Using a referenced task definition will allow this behavior to employ a task that has the complete gambit of task configuration options available to it.

When not checked this string will be used as the name of the task created by this block. If left empty then a name will be created automatically.
Worker Task Stack Size Single quote enclosed alpha-numeric. The stack size in bytes that the task will use.
Worker Task Stack Margin Single quote enclosed alpha-numeric. The stack margin in bytes that the task will be use.
Processing Task Priority Drop-Down List The priority of the task that will be used for TCP/IP thread processing in the lwIP stack.
Only visible and applicable when Use Worker Task Reference is not checked.
Build Configuration Drop-Down List The desired build configuration of the stack. When "Default" is selected, the recommended configuration for the currently selected target is used, otherwise the configuration used is overridden by this selection.

Options include Standard and Tiny. Standard reserves more resources and is very capable. Standard can be thought of as sufficient to support a small embedded Ethernet router. The Tiny setting will be more conservative on the reservations of resources. Tiny should be sufficient to sustain command/response style communication between a low number of endpoints. With the Tiny setting, a busy network with lots of traffic may cause packet loss due to the lower reservation of RAM.