- Wed Jan 07, 2015 2:25 am
#6515
As far as I can tell, when my code calls wifi_softap_set_config(), the Espressif code saves those parameters in flash, and attempts to set up the AP configuration automatically whenever the chip boots before even calling any of my code.
I'd rather it didn't do that; I want no state to exist in Flash, or to manage the state myself.
One example of a problem this causes is that there's apparently a bug in the libmain.a contained in https://github.com/espressif/esp_iot_rtos_sdk_lib; the stack size isn't large enough, so having the AP configuration saved and automatically restored causes a crash very early during boot, which is extremely non-obvious to debug. I'd rather any failures always occur under control of my own code, so I know exactly what's happening and when, and so something in my code can always boot and start printing debug messages before any crash.
For the record (e.g. Google), the fix for that particular bug appears to be:
http://bbs.espressif.com/viewtopic.php? ... p=433#p433
(and I notice there's a commit on github very recently which presumably updates libmain.a to include that fix)
I'd rather it didn't do that; I want no state to exist in Flash, or to manage the state myself.
One example of a problem this causes is that there's apparently a bug in the libmain.a contained in https://github.com/espressif/esp_iot_rtos_sdk_lib; the stack size isn't large enough, so having the AP configuration saved and automatically restored causes a crash very early during boot, which is extremely non-obvious to debug. I'd rather any failures always occur under control of my own code, so I know exactly what's happening and when, and so something in my code can always boot and start printing debug messages before any crash.
For the record (e.g. Google), the fix for that particular bug appears to be:
http://bbs.espressif.com/viewtopic.php? ... p=433#p433
(and I notice there's a commit on github very recently which presumably updates libmain.a to include that fix)
