I am developing firmware with an ESP-32 EVM board. I updated MOS from version 2.5.1 to 2.6 on Wednesday 10/10. Now, all firmware compiled with 2.6 (new firmware and also previous versions that were successful under 2.5.1) will not connect to a Windows 10 HP computer with BCM43142. The EVM is configured as AP, and the EVM's SSID always appears in the Windows 10 computer's list of available APs. When ever a connection is attempted , the EVM delivers connection messages over USB COM3.
A successful connection (with all firmware compiled with 2.5.1) delivers connection messages as follows:
[Oct 12 12:43:47.049] I (89093) wifi: n:6 0, o:6 0, ap:6 1, sta:255 255, prof:6 [Oct 12 12:43:47.423] I (89103) wifi: station: d8:5d:e2:e6:b5:21 join, AID=1, bgn, 20 [Oct 12 12:43:47.424] [0;32mI (89193) tcpip_adapter: softAP assign IP to station,IP is: 192.168.4.2[0m [Oct 12 12:43:47.426] event_handler event: 17
A failed connection (with all firmware compiled with 2.6) delivers connection messages as follows:
[Oct 12 12:54:40.981] I (45780) wifi: n:6 0, o:6 0, ap:6 1, sta:255 255, prof:6 [Oct 12 12:54:40.987] I (45790) wifi: station: d8:5d:e2:e6:b5:21 join, AID=1, bgn, 20 [Oct 12 12:54:41.000] mgos_wifi_on_change_ d8:5d:e2:e6:b5:21 connected
Any thoughts on why this is happening, and how to fix?
WiFi configuration and settings may alleviate this problem. Can anyone provide a recommended WiFi configuration (for Windows and confx.json and any other relevant file) that works with Windows 10 and version 2.6?