...
In order for the network device driver to remain hardware independent, µC/TCPIP requires a BSP abstraction layer to implement such things as configuring clocks, interrupt controllers, general-purpose input/ouput (GPIO) pins. Inside your project folder tree, under the board name, you should already have a BSP folder. Boards for which TCPIP application have been develop should have a TCPIP folder inside the BSP directory. You can add this directory to your project tree. If your board does not have such a folder, you would have to write your own BSP for the network device driver. Refer to section Network Board Support Package for more details on how to write a BSP for µC/TCP-IP. Micrium offers template files inside the BSP folder in the µC/TCP-IP source code distribution to get you started with your own BSP. However, we recommend starting with a working configuration from an example project for your network device. Micrium might have some projects available only for internal usage, so if no working project are found online, please ask at support@micrium.com for a BSP file example specific for your network device.
AfterwordsAfterwards, add a path leading to the following include paths to your project’s C compiler settings:
\Micrium\Software\EvalBoards\<manufactuer>\<boardname>\BSP\TCPIP
...
Copy the files from the uC-TCPIP configuration folder into your application as illustrated in Figure - Copying Template Files .
| Anchor | ||||
|---|---|---|---|---|
|
| Panel | ||||
|---|---|---|---|---|
| ||||
|
net_cfg.c is a configuration file including the NET_TASK_CFG objects used to configured the µC/TCP-IP internal tasks. The µC/TCP-IP stack has three internal tasks : the Receive task, the Transmit De-allocation task and the Timer task. Each task as its own NET_TASK_CFG object defining the task priority, the task's stack size and the pointer to start of task stack. Refer to section Network Tasks Configuration for more details on the µC/TCP-IP tasks configuration.
...