This section describes all the steps required to build a DNSc-based application. The instructions provided in this section are not intended for any particular toolchain, but instead are described in a generic way that can be adapted to any toolchain.
The best way to start building a DNSc-based project is to start from an existing µC/TCP-IP project.
Working project with µC/TCP-IP
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 µ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 µC/DNSc. Then you can follow the following steps to build and run your first µC/DNSc sample application.
Including Additional Modules to the Project
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 modules:.
Optional module
Including µC/DNSc Source Code
Include the following files in your project tree from the µC/DNSc source code distribution, as indicated in Figure - µC/DNSc Source Code.
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
Copying and Modifying Template Files
Copy the files from the uC-HTTPs configuration folder into your application as illustrated in Figure - Copying Template Files.
http-s_cfg.h is a configuration file used to setup µC/HTTPs module static parameters and features such as CGI form configuration, dynamic token replacement configuration, header field feature, proxy configuration and so on. Refer to section Module Configuration for more details on all the configurations inside http-s_cfg.h
The http-s_instance_cfg.c/.h pair of files, defines the configuration structure for an HTTP server’s instance (see µC/HTTPs Instance Configuration for more details). If your application requires a secured HTTP server instance, the http-s_instance_secure_cfg.c/.h pair of files should be used as template instead.
Modifying the HEAP memory configuration
The µC/HTTPs Module uses additional heap memory space. Therefore, it is possible that your sample application will require more allocation of heap memory. If ti is the case, you can increase the HEAP memory size of your sample project, refer to section µC/LIB Memory Management Configuration for more details on the heap usage.
Adding µC/HTTPs application function
Before running the sample application, you will need to add the new function call, in your application file to initialize and setup the µC/HTTPs module. Section Sample Application gives an example of how to initialize µC/HTTPs and start a web server instance.
This code example will need to be modified in accordance with your project.
Adding Additional includes
#include <Source/http-s.h>
#include <FS/uC-FS-V4/net_fs_v4.h> (optional if uC/FS is used)
#include <FS/Static/http-s_fs_static.h> (optional if no File system is available in the project)