...
The first step before including the µC/DNSc is to have a working project with the µC/TCP-IP. As previously mentioned, Micriµm may offer starting example with µC/OS-III kernels and µC/TCP-IP and even with µC/DNSc for many evalboards.
If no project that include includes µC/TCP-IP is available, you should follow the µC/TCP-IP - Getting Started Guide to start with a working TCP/IP project before starting integrating to integrate µC/DNSc. Then you can follow the following steps to build and run your first µC/DNSc sample application.
...
Once you have a working project with your RTOS and µC/TCP-IP additional modules are needed by the Micriµm DNC client that are not necessarily already included in your project. Therefore, be sure to add µC/CPU, µC/LIB and µC/Common to your project.
Refer to the following manuals for further information about MIcrium Micrium modules:.
...
Include the following files in your project tree from the µC/DNSc source code distribution, as indicated in Figure - µC/DNSc Source Code.
| Panel | ||
|---|---|---|
| ||
|
As indicated in the Figure - µC/DNSc Source Code, all the files in the Source folder must be added to your project tree. File under the folder Cmd can be added if µC/Shell is already included in your project.
Compiler settings
Finally, add the following include paths to your project’s C compiler settings:
\Micrium\Software\uC-DNSc
\Micrium\Software\uC-TCPIP
\Micrium\Software\uC-Shell (optional if uC/Shell is used)
...
Copy the files from the uC-DNSc configuration folder into your application as illustrated in Figure - Copying Template Files.
| Panel | ||
|---|---|---|
| ||
|
dns-c_cfg.c/.h pair of files, define µC/DNSc module static parameters and run-time configuration structure. Refer to section Module Configuration for more details on all the configurations inside templates files.
...