...
...
...
...
...
...
...
...
...
...
Tasks priorities configuration
The following configuration constants relate to the µC/FTPs OS port. For many OSs, the µC/FTPs task priority will need to be explicitly configured for the particular OS (consult the specific OS’s documentation for more information).
| Panel | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| |||||||||
|
We recommend to configure the Network Protocol Stack task priorities & FTP server tasks priorities as follows:
NET_OS_CFG_IF_TX_DEALLOC_TASK_PRIO (Highest)
FTPs_OS_CFG_SERVER_TASK_PRIOFTPs_OS_CFG_CTRL_TASK_PRIO ( ... )NET_OS_CFG_TMR_TASK_PRIO ( ... )
NET_OS_CFG_IF_RX_TASK_PRIO (Lowest )
We recommend that the uC/TCP-IP Timer task and network interface Receive task be lowe priority lower priority than almost all other application tasks; but we recommend that the network interface Transmit De-allocation task be higher priority than all application tasks that use uC/TCP-IP network services.
However better performance can be observed when the web server instance is set with the lowest priority. So some experimentation could be required to identify the better task priority configuration.
Task Stack Size Configuration
In general, the size of µC/FTPs task stacks is dependent on the CPU architecture and compiler used.
...
On ARM processors, experience has shown that configuring the task stacks to 1024 OS_STK entries (4,096 bytes) is sufficient for most applications. Certainly, the stack sizes may be examined and reduced accordingly once the run-time behavior of the device has been analyzed and additional stack space deemed to be unnecessary.
| Panel | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| |||||||||
|