firstset.cgi psk not crunched

Posted on December 18, 2014 at 10:13

We are currently developing a product that uses the SPWF01S module running firmware:

140623-cd34ea1-SPWF01S.

Our product relies on the firstset.cgi to connect to a network, the situation is as follows:

1. A microcontroller controls the SPWF01S
2. The SPWF01S is started in MiniAP
3. The microcontroller creates a custom pages with available networks. This custom page contains a html form that pushes its data into firstset.cgi
4. A user can select a network and the firstset.cgi will then tell the SPWF01S to connect to that network

The problem:

We had this working correctly, but made changes to the code of the microcontroller, that should not affect the described situation, but somehow it does.

When using the same webpage, the SPWF01S can no longer connect to WPA2 networks, because is no longer crunches the key:

When working correcty:

+WIND:28:Station 00:22:43:96:6A:68 Associated

 

 

 

+WIND:29:DHCP reply for 172.31.178.2/00:22:43:96:6A:68

 

 

 

+WIND:29:DHCP reply for 172.31.178.2/00:22:43:96:6A:68

 

 

 

+WIND:57:Received SSID is Network

 

 

 

+WIND:57:Received PWD is Password

 

 

 

+WIND:57:Received Auth mode is 2

 

 

 

+WIND:57:Received Mode is 1

 

 

 

+WIND:2:Reset

 

 

 

+WIND:1:Poweron (140623-cd34ea1-SPWF01S)

 

 

 

+WIND:13:ST SPWF01SA IWM: Copyright (c) 2012-2014 STMicroelectronics, Inc.  All rights Reserved.

 

 

 

+WIND:3:Watchdog Running

 

 

 

+WIND:0:Console active

 

 

 

+WIND:46:WPA: Crunching PSK...

 

 

 

+WIND:32:WiFi Hardware Started

 

 

 

+WIND:21:WiFi Scanning

 

 

 

+WIND:35:WiFi Scan Complete (0x0)

 

 

 

+WIND:19:WiFi Join:00:02:6F:AD:AD:18

 

 

 

+WIND:25:WiFi Association with 'Network' successful

 

 

 

+WIND:51:WPA Handshake Complete

 

 

 

+WIND:24:WiFi Up:192.168.10.177

 

When working incorrectly:

+WIND:28:Station 00:22:43:96:6A:68 Associated

+WIND:29:DHCP reply for 172.31.178.2/00:22:43:96:6A:68

+WIND:29:DHCP reply for 172.31.178.2/00:22:43:96:6A:68

+WIND:57:Received SSID is Network

+WIND:57:Received PWD is Password

+WIND:57:Received Auth mode is 2

+WIND:57:Received Mode is 1

+WIND:2:Reset

+WIND:1:Poweron (140623-cd34ea1-SPWF01S)

+WIND:13:ST SPWF01SA IWM: Copyright (c) 2012-2014 STMicroelectronics, Inc.  All rights Reserved.

+WIND:3:Watchdog Running

+WIND:0:Console active

+WIND:32:WiFi Hardware Started

+WIND:21:WiFi Scanning

+WIND:35:WiFi Scan Complete (0x0)

+WIND:19:WiFi Join:00:02:6F:AD:AD:18

+WIND:25:WiFi Association with 'Network' successful

+WIND:40:WiFi Deauthentication

I've checked status and configuration in both cases afterwards and in both causes they seem ok:

wifi_mode = 1

 

wifi_auth_type = 0

 

wifi_priv_mode = 2

wifi_ssid and wifi_wpa_psk_text are correct.

The only difference I see is the wifi_wpa_psk_raw being different (due to not being crunched I suspect).

What can cause the SPWF01SA to skip this essential step?

#spwf01sa-wpa-psk