Q: What is the difference between RTOS and the non-OS SDK?

ESP_Luna
Posts: 32
Joined: Wed Jun 17, 2015 4:10 pm

Q: What is the difference between RTOS and the non-OS SDK?

Postby ESP_Luna » Tue Jul 28, 2015 12:59 pm

Q: What is the difference between RTOS and the non-OS SDK?
The main differences are listed below:
【Non-OS SDK】
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.
【RTOS SDK】
    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.

kenn2
Posts: 2
Joined: Sun Aug 02, 2015 3:46 am

Re: Q: What is the difference between RTOS and the non-OS SDK?

Postby kenn2 » Sun Aug 02, 2015 4:19 am

(for the rest of us ;-) )

The main points of difference are as follows:

[Non-OS SDK]

The Non-OS SDK uses timers and callbacks as the main way to perform the various functions - nested events, functions triggered by certain conditions. The Non-OS SDK uses the espconn network interface; the user needs to develop their software according to the usage rules of the espconn interface.

[RTOS SDK]

1. RTOS version SDK uses the freeRTOS system, a multi-tasking OS. You can use standard interfaces to freeRTOS resource management, recycling operations, execution delay, inter-task messaging and synchronization, task-oriented process design. For the specifics of interface methods, refer to freeRTOS official website instructions or USING THE FREERTOS REAL TIME KERNEL - A Practical Guide introduction.

2. RTOS SDK version of the network operating interface is a standard lwIP API, while providing a package which enables BSD Socket APIsocket interface. Users can directly use the socket API to develop software applications; your code can also be directly compiled to run standard applications on other platforms Socket , effectively reducing the cost of learning platform switching. (possibly flawed translation)

3. RTOS version of the SDK introduces cJSON library, use the library functions to more easily parse JSON packets.

4. RTOS version is compatible with non-OS SDK in the Wi-Fi interface, smart config interfaces, Sniffer related interfaces, system interface, timer interface, FOTA interfaces and peripheral driver interface, but does not support the AT implementation.

(espressif - please make corrections)

Who is online

Users browsing this forum: No registered users and 1 guest