ESP8266 Community Forum

- Wed Apr 06, 2022 2:54 pm #94200

the RTOS just rides on top of the same guts used in the NoOS version.

I don't think so
It's a different SDK

https://github.com/quackmore

- Wed Apr 06, 2022 4:13 pm #94201

the RTOS just rides on top of the same guts used in the NoOS version.

I don't think so
It's a different SDK

I understand it is a different HIGH-LEVEL SDK.

However, they both use lwIP for handling TCP and the levels below... down to the ESP8266 hardware. And that is the memory we are talking about that is dynamically allocated without our knowledge, but we must leave available.

IMO I believe leaving somewhere between 6kB and 10kB as reported by system_get_free_heap_size() is necessary. It does not matter what is riding above the TCP - be it... SSL, HTTP, MQTT, NonOS, RTOS or even Python... they are already taking up the space they need when calling system_get_free_heap_size.

3 lines of code = Complete IoT, App, Web Server
w/ GUI Admin Client, Drag & Drop File Manager, OTA Built-In, Access Point Manager,
Performance Metrics, Web Socket Comms, App API, All running on ESP8266...
Even usable on ESP-01S --- Please check it out!
https://inqonthat.com/inqportal-the-three-line-promise/
https://InqOnThat.com/inqportal

- Wed Apr 06, 2022 5:51 pm #94203 when I say nonos and rtos sdk are different I mean that none of the system calls you've mentioned will work with the rtos sdk

system_get_free_heap_size doesn't even provide the same information of esp_get_minimum_free_heap_size we were talking about

don't take it personal but it's like you're describing pistons to the owner of a Tesla... you're not helping

https://github.com/quackmore