[WICED-SDK-3.5.2]:[wifi_config_dct.h]:Personal SSID

Solved
miltondsantos's picture
miltondsantos
Junior(2)

Hi Dear,

I'm trying to enable my board to connect drectly in my personal SSID without use the SoftAP config. Then I edited the file "wifi_config_dct.h" as following:

37 /* This is the default AP the device will connect to (as a client)*/
38 #define CLIENT_AP_SSID       "MIMO"
39 #define CLIENT_AP_PASSPHRASE "mypassword"
40 #define CLIENT_AP_BSS_TYPE   WICED_BSS_TYPE_INFRASTRUCTURE
41 #define CLIENT_AP_SECURITY   WICED_SECURITY_WPA2_MIXED_PSK
42 #define CLIENT_AP_CHANNEL    1
43 #define CLIENT_AP_BAND       WICED_802_11_BAND_2_4GHZ

 And I try to run it but following the error:

---------------------------------------------------------------------------------------------
21:48:53 **** Incremental Build of configuration Default for project WICED-SDK ****
"C:\\Users\\milton\\Documents\\WICED\\WICED-SDK-3.5.2\\WICED-SDK\\make.exe" Default 
MAKEFILE MAKECMDGOALS=Default OTA2_SUPPORT is disabled
Making config file for first time
tools/makefiles/wiced_config.mk:224: *** Unknown component: Default.  Stop.
make: *** No rule to make target 'build/Default/config.mk', needed by 'main_app'.  Stop.

21:48:54 Build Finished (took 1s.214ms)
---------------------------------------------------------------------------------------------

And I double clicked on line tools/makefiles/wiced_config.mk:224: *** Unknown component: Default.  Stop. and was showed the line below of file "wiced_config.mk":

$(foreach comp, $(COMPONENTS), $(if $(wildcard $(foreach dir, $(addprefix $(SOURCE_ROOT),$(COMPONENT_DIRECTORIES)), $(dir)/$(subst .,/,$(comp)) ) ),,$(error Unknown component: $(comp))))

My question is how to fix it to make the board connect alone in my personal SSID?

Thank you
MDS

 

PeterF's picture
PeterF
Moderator(15)

Please refer to the Installation Tutorials for assistance on this! 
http://cloudconnectkits.org/forum/topic/installation-tutorials

 

Part 2 of these tutorials guides you through the key steps required before building projects in WICED SDK.

 

The section titled "Bake-in the WLAN and AWS Settings" is what you need to hard-code the network settings of the Wireless A/P that you want the kit to connect to.  

miltondsantos's picture
miltondsantos
Junior(2)

Hi Peter,

Look my comments on this post.

Thanks.

miltondsantos's picture
miltondsantos
Junior(2)

Hi Peter,

I followed your tips but I created the certificates using the "connect a device" and the certificates and policy were created, but after I used the softap page the border is restarting with this info of my wifi connection but I can not see it on aws page:

Starting WICED v3.5.2
Platform BCM94343W_AVN initialised
Started ThreadX v5.6
Initialising NetX_Duo v5.7_sp2
Creating Packet pools
WWD SDIO interface initialised
WLAN MAC Address : B0:38:29:3D:39:EB
WLAN Firmware    : wl0: Nov 25 2015 12:57:14 version 7.45.45.1 (r602358) FWID 01-1920c040
 Please wait, connecting to network...
(To return to SSID console screen, hold USER switch for 5 seconds during RESET to clear DCT configuration)
Joining : MIMO
Successfully joined : MIMO
Obtaining IPv4 address via DHCP
DHCP CLIENT hostname WICED IP
IPv4 network ready IP: 192.168.20.21
Setting IPv6 link-local address
IPv6 network ready IP: FE80:0000:0000:0000:B238:29FF:FE3D:39EB
[MQTT] Connecting to broker 54.236.181.116 ...

Thing Name: startkit_0040
Shadow State Topic: $aws/things/startkit_0040/shadow/update
Shadow Delta Topic: $aws/things/startkit_0040/shadow/update/delta
Reading the certificate and private key from DCT...
[MQTT] Connecting to MQTT Broker...
Reading the certificate and private key from DCT...
[MQTT] Connecting to MQTT Broker...
Reading the certificate and private key from DCT...
[MQTT] Connecting to MQTT Broker...

 And I can not see anything from the board on aws:

 

Name

startkit_0040

REST API endpoint

https://A125VMFPNNGISW.iot.us-east-1.amazonaws.com/things/startkit_0040/...

MQTT topic

$aws/things/startkit_0040/shadow/update

Last update

No state

Attributes

miltondsantos's picture
miltondsantos
Junior(2)

Peter, I did it one time ago but now the device is not recognized by AWS cloud. Do you have any idea what is the problem? Thank you.