DA16200/DA16600 WiFi provisioning app 'connection to socket' problem

Question

I'm testing the functionality of a DA16600 PMOD board and have encountered a problem with the WiFi provisioning demo using the Android app (v2.4.11) which gets stuck at stage 6 (UM-WI-042 manual) with the message 'connection to socket...' (see screen shot below). I don't know whether the app is failing to receive the list of APs from the DA16600 or if the DA16600 isn't able to see them, although when I configure it as a STA the APs are visible. Any suggestions what's wrong? 
 I'm using the firmware supplied with the PMOD board, SDK version = V3.2.7.1 GEN-ATCMD, F/W Version = FRTOS-GEN01-01-98e58a5d3-006374

ksw · Accepted Answer

The problem seems to be with the Wi-Fi provisioning app running on my phone (Android 8) as I've just discovered it does work on a phone running Android 13, although the documentation for the app suggests it should work with Android 5.0 and later.

OV_Renesas · Answer

Hi There, Thank you for posting your question online. 
 ksw said: Any suggestions what's wrong? 
 I'm using the firmware supplied with the PMOD board, SDK version = V3.2.7.1 GEN-ATCMD 
 I am not really sure if your FreeRTOS Image has the Wi-Fi Provisioning feature enabled. Please refer on the US159-DA16600EVZ Evaluation Board Manual (renesas.com) on page:5 Please use a FTDI Cable (or USB to Serial converter) on J3 header in order to get access on the UART0 (Debug Console Interface). From the logs shown there you will understand if the Wi-Fi Provisioning is supported or not. Otherwise you can use the UART0 to load another firmware image that can support Wi-Fi Provisioning from the pre-compiled binaries. Best Regards, OV_Renesas

OV_Renesas · Answer

Hi There, Thank you for the reply. From the 1st log you shared, it is clear that the DA14531 image (BLE image) was not loaded correctly. [combo] BLE_BOOT_MODE_0
invalid Product Header, program multi-part image again !
Error Initialization of DA14531, freeRTOS, err_code = -5

This is the reason why you could not use the Wi-Fi Provisioning Mobile app. 
 ksw said: I installed the latest AT command firmware image for the DA16600 (see below) and the android app will now provision it via Bluetooth, but I still get the same problem when the DA16600 is configured in SoftAP mode. 
 Could you please share the full UART0 logs of the same problem here as well? Before trying to do Wi-Fi Provisioning, it is suggested you do a factory reset. This can be done, by typing 'factory' on the UART0 console interface. Best Regards, OV_Renesas

OV_Renesas · Answer

Hi There, Thank you for the reply. Please check for any multiple definitions of the same macro inside your project. 
 ksw said: is there an simple SDK configuration macro that would disable the BLE functionality and make the DA16600 behave as a DA16200? 
 You can just download the DA16200 image that you want on your DA16600, and make sure you have erased the DA14531 (BLE) image. The DA16600 will then behave like the DA16200. Best Regards, OV_Renesas

OV_Renesas · Answer

Hi KSW, Thank you for the reply. On the Google PlayStore I checked the Renesas WiFiProvisioning mobile application: As you can see, it is available for Android 8.1 and up. Best Regards, OV_Renesas

DA16200/DA16600 WiFi provisioning app 'connection to socket' problem

Top Replies