Proposal to SDK changes

[DarkSide]

Well, I guess right name for this topic should be “write SDK for Developers, not for Dummies”, but let’s begin.
As we all know SDK is a Software Development Kit. Software is developed by Developers. Developers is a people who writing application. This can be done fully from scratch writing code piece by piece or by using code/libraries provided by other Developers. Talking in scope of embedded systems, it’s probably unreal to write an “application” for embedded system from scratch (because of…  many things). Here is a moment where SDK for embedded system comes. SDK should provide full control of MCU/board/embedded system. It should be clean, straightforward and all functions, provided by SDK, should do exactly what they are supposed to do. SDK interface methods should be thought of, not “written on knee” for a couple of hours and do exactly what they should do.
For which purpose I’m writing all of this. Let’s looks at the “wifi_station_connect” method. From it signature it should connect chip to remote AP. He SHOULD just connect to AP (synchronous) or start connection routine (asynchronous). It should not write connection information into EEPROM and after next power on try to automatically connect to it. When ESP8266 is just booted I expect that I will receive full control on what chip will do, but… The chip is doing what it want to do. The same is for “wifi_set_opmode”, “wifi_station_ap_number_set”, “wifi_station_set_auto_connect” and so on. No need to do things that developer can do itself (and of course if he needs to do this). It would be much better if instead of auto saving data into EEPROM we have function like “persist_wifi_settings” which will save current wifi settings into EEPROM. BUT, this is really unnecessary. That was just an example. What I'd like as a developer, is that if I just have an API to write to EEPROM and read from EEPROM at special offset predefined by Espressif for user data (in other, simplified, words where currently wifi settings is saved).
I agree that this functionality is not redundant at all, especially for AT firmware, but SDK is not a place for this.

[tve]

Yup. I would say that the SDk has too many functions that are solutions and too few that are building blocks.

[NASATEC]

We are under new project based on ESP8266.
We need serial comm for another porpuse different than StartUp.
Is it possible we save config info into the firmware, in order to automatic starts of the module every power up (without AT commands)?