1) Clients have an extremely hard time connecting to ESP AP. Our PC with WiFi can't connect, and our Raspbery Pi has to retry for almost a minute if it connects at all. True for both unencrypted / WPA2.
2) When clients do connect, we can CURL GET / POST correct WiFi STA info. But if we POST deliberately incorrect STA SSID, the ESP gets a fatal exception.
It then runs in an endless loop where it starts AP+STA, starts DHCPS, etc then gets the exception. We have to flash the chip to stop the problem, indicating that User Param (0x3C-3F000) is corrupted.
We get the same result with ESP Flash Tool 2.3 and esptool.py.python2. Pls see screenshot. Only setting changed on InitConfig to create esp_init_data_setting.bin is CrystalFreq = 26MHz. We also tried writing "blank.bin" to User Param 0x3C000-0x3E000. Didn't help.
We've wasted a week on this. When it actually works, we do NTP, REST, JSON, etc with no issues. But we keep getting these two problems.
Statistics: Posted by azapps — Sat Feb 06, 2016 2:46 am
]]>