firstset.cgi psk not crunched

jimmicola · ‎2014-12-18

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:

A microcontroller controls the SPWF01S
The SPWF01S is started in MiniAP
The microcontroller creates a custom pages with available networks. This custom page contains a html form that pushes its data into firstset.cgi
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: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: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: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: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

Gerardo GALLUCCI · ‎2014-12-18

Posted on December 18, 2014 at 13:52

Hi,

you are using a not official FW Release. Where did you get it?

I think you are facing an already fixed bug. Please update.

Thanks

jerry

jimmicola · ‎2014-12-18

Posted on December 18, 2014 at 16:11

Thank you Jerry,

The firmware was suplied to us by silica, who by now have supplied us with a new version: 141106-0950875-SPWF01S

Could you tell me if this is the latest/most stable firmware?

Because running my current code I already encountered a major bug,

the file append command (at+s.fsa=/<filename>,<size>) no longer appends, but overwrites previous data in the file.

Again thank you for your time.

Jim

Gerardo GALLUCCI · ‎2014-12-18

Posted on December 18, 2014 at 16:21

The 141106-0950875-SPWF01S is the latest

official

Release.

There is another more recent version, which fix the FSA command issue you found.

Please consider this issue as fixed.

We'll inform Silica and other distributors when new FW can be delivered.

jerry

jimmicola · ‎2014-12-19

Posted on December 19, 2014 at 09:07

Jerry,

Can you give us an estimation on when the new firmware will be available.

Considering deadlines we have for this new product, we need to decide to wait for the new firmware, or adept our code to work around the bugs.

Thank you,

Jim Micola

From: gallucci.gerardo

Posted: Thursday, December 18, 2014 4:21 PM

Subject: firstset.cgi psk not crunched

The 141106-0950875-SPWF01S is the latest

official

Release.

There is another more recent version, which fix the FSA command issue you found.

Please consider this issue as fixed.

We'll inform Silica and other distributors when new FW can be delivered.

jerry

Gerardo GALLUCCI · ‎2014-12-19

Posted on December 19, 2014 at 11:33

Hi Jim,

I got your point.

A newer version of the FW will be available for customers within Q1 2015.

Please consider this issue as already fixed. Could you implement a workaround to avoid the issue? When new FW will be available, this workaround can be removed. Is it ok for you?

Thanks

j

jimmicola · ‎2015-01-05

Posted on January 05, 2015 at 12:46

We will indeed try to work around it for now.