This is actually a problem with Windows WPS implementations, which use the WPS external registrar handshake to do WPS discovery. Wiced does not support being configured by an external registrar so the configuration methods attribute in probe responses is set to zero, as per the WPS 2.0 specification.
Attached patch that adds a flag to the WPS device details which allows the SoftAP registrar to advertise in the configuration methods attribute in probe responses. This change works for Windows 7 and has been tested with a ThreadX NetX Duo build. Attached patch is not tested with a Windows 8.
A fix for a ThreadX priority problem is also included and is required with the WPS fix or the WPS handshake won't complete after being restarted, ThreadX Patch for WICED SDK-3.1.x
For wiced_dct_read_lock(...) in ...\apps\snip\wps_enrollee application update following:
wiced_dct_read_lock( (void**) &softap_info, WICED_FALSE, DCT_WIFI_CONFIG_SECTION, OFFSETOF(platform_dct_wifi_config_t, soft_ap_settings), sizeof(wiced_config_soft_ap_t) );
The effect of the change is that Windows should now automatically proceed with WPS push button mode.
Dear Mr. Sehan,
thank you for the response. As far as i understood and tested the above approach, there exists no real solution how to handle WPS with Win8.1 and Win7.
There is quite a different behavior between both of them. Win7 is the more difficult theme as already mentioned above; but until now the more interesting one until the market penetration does not change.
To sum it up, there exists no solution to this topic ==> so far not successfully answered.