2016-08-10 01:25 AM
I am using my SPWFS01 together with a host controller. The host will, at startup, configure the SPWFS01 after which it will try to connect to a certain WiFi. This has worked for a long period of time but now suddently it does not work. My host sends this to the module:
AT+S.SCFG=wifi_mode,0AT+S.SCFG=wifi_wpa_psk_text,wifipassAT+S.SSIDTXT=wifissidAT+S.SCFG=wifi_priv_mode,2AT+S.SCFG=wifi_mode,1AT&WAT+CFUN=0after which it performs a HW reset.Usually, the module responds OK to everything and then boots. Now however, the response isOKOKOKOKOKOKand then nothing. It appears that it responds OK to everything up until saving configuration in flash. What could be the cause of this?Regards2016-08-11 03:46 AM
Check boot and reset pins
[DEAD LINK /public/STe2ecommunities/interface/Lists/WiFi%20Modules/Flat.aspx?RootFolder=/public/STe2ecommunities/interface/Lists/WiFi%20Modules/Module%20soft%20reset&FolderCTID=0x01200200770978C69A1141439FE559EB459D75800086789498A6852D4897EA192EB1DEE909&TopicsView=https://my.st.com/public/STe2ecommunities/interface/Lists/WiFi%2520Modules/AllItems.aspx¤tviews=90]https://my.st.com/public/STe2ecommunities/interface/Lists/WiFi%20Modules/Flat.aspx?RootFolder=%2fpublic%2fSTe2ecommunities%2finterface%2fLists%2fWiFi%20Modules%2fModule%20soft%20reset&FolderCTID=0x01200200770978C69A1141439FE559EB459D75800086789498A6852D4897EA192EB1DEE909&TopicsView=https%3A%2F%2Fmy%2Est%2Ecom%2Fpublic%2FSTe2ecommunities%2Finterface%2FLists%2FWiFi%2520Modules%2FAllItems%2Easpx¤tviews=902016-08-11 11:09 PM
This problem has been fixed and identified. When we deploy SW on the chip hosting the module it gives a lot of wierd output on UART while performing the deployment. What had happened was that I accidentally deployed new SW right while the host was configuring the module (using AT+S.SCFG..). Therefor some of this nonsense that the host spits out on UART was accidentally put in the module configuration, which made it very unresponsive, not sending any winds (since the wind-conf variables where all set to FFF..) and some variables hade real bogus values (as though they were maxed out), for example
# wifi_beacon_wakeup = 65535# standby_time = 4294967295# ip_hostname = ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ[01]ÿÿÿÿÿÿÿÿÿÿÿWe connected the module directly to computer, however it was very unresponsive. Once every ~50th command was actually received and OK'd by the module. We tried the HW factory reset without success so finally we just spammed AT&F until it finally received that CMD and made factory reset and was restored.2016-08-23 12:15 PM
Thanks for info.
Configuration variables corruption as been improved by CRC check in future releases. If CRC fails @ startup, AT&F is automatically issued by module itself.