...
If the static file system is being used with µC/HTTPs, the following configuration values also have to be added to your app_cfg.h file.
#define APPS_FS_CFG_NBR_FILES 5
This value defines the maximum number of files the static file system could manage.
#define APPS_FS_CFG_NBR_DIRS 5
This value defines the maximum number of directory the static file system could manage.
...
#define APPS_FS_CFG_MAX_FILE_NAME_LEN 25
This value defines the maximum file name length.
Operating System Configuration
...
The priority of µC/HTTPs task is dependent on the requirements of the application.For µC/OS-II and µC/OS-III, the following macros must be configured within app_cfg.h :
#define HTTPs_OS_CFG_TASK_PRIO 13
Value of the priority for the µC/HTTPs tasks. The value assigned depend of the software architecture of your system, and of the importance of this module response time relative to the other tasks
...
#define HTTPs_OS_CFG_TASK_STK_SIZE 2048
Value of the priority for the µC/HTTPs tasks. This default value should be enough for most environments, but you should check this on your system for reliability or performance purpose.
Interface with RTOS
µC/HTTPs requires the presence of a Real Time Operating System (RTOS). As mentioned in See Directories and Files., the sample application uses µC/OS-II or µC/OS-III. It is possible to port µC/HTTPs so it is used with other OS by providing an appropriate implementation of http-s_os.c .
...