The main differences are listed below:
Non-OS SDK enables features or events to be embedded via timers and call-back functions. In this regard, specific functions will be triggered in specific conditions. In the Non-OS SDK, espconn is utilized to operate the network. The users need to develop softwares based on the usage rules for espconn.
- 1. FreeRTOS is utilized in the RTOS SDK that features multitasking operation. Designed in this way, this system enables users to utilize the standard interface for resource management, cyclic operation, time delay within a task, and inter-task information delivery and synchronization. For specific usage methods for interfaces, please refer to the official website of freeRTOS or USING THE FREERTOS REAL TIME KERNEL--A Practical Guide.
- 2. lwIP API, a standard interface, is utilized in the RTOS SDK to operate the network. In the RTOS SDK, SD Socket API is encapsulated. Users may develop software applications in the same way that they apply socket API, or compile the standard Socket applications that run on other platforms. This helps reduce costs incurred in switching from one platform to another.
- 3. cJSON library is added into the RTOS SDK. This library facilitates its functions to parse the contents of JSON data packet.
- 4. RTOS is compatible with Wi-fi interfaces, smart config interfaces, Sniffer related interfaces, system interfaces, timer interface, FOTA interfaces and peripheral driver interfaces in the non-OS SDK, but does not support the AT commands.