You can chat about native SDK questions and issues here.

User avatar
By shiv patil
#83267 Hello Community,

I am very new to ESP8266 WIFI module.
I have started studying the Datasheet, User Guide & Application Notes for ESP8266EX module.

I am able to know that there are 2 types of SDK available for ESP8266 module.
I am little bit confuse about, which one I must chose for the developing my application code.

1. Can any one help me to understand what are advantages & disadvantages of those SDK's?..
2. Which one is suitable for using module with minimal functionality & Low power consumption mode?..

Regards,
Shiv Patil
User avatar
By quackmore
#83272 NONOS_SDK is bare-metal, check out the "code structure" section in the "2c-esp8266_non_os_sdk_api" manual. Quick and dirty said:
+ think about non-os-sdk like something similar to node.js (an asynchronous event driven engine) not an operating system
+ let your application be driven by events (wifi events, communications events, interrupts ...)
+ in case you need to do polling or periodic tasks use timers
+ the only thing you have to care about is that your code execution does not take that long to trigger the watchdog

RTOS_SDK is an OS layer API based on FreeRTOS thus featuring:
+ multitasking operation
+ networking using lwIP API (standard interface)

RTOS will require you more expertise but will result in more portable code.

Don't have data for comparing power consumption.