cancel
Showing results for 
Search instead for 
Did you mean: 

Getting started with the “wifi 4 click� board

mmeerian
Associate
Posted on December 22, 2015 at 16:33

I’m trying to get up and running with the “Wifi 4 click�? module.

 

This board has a SPWF01SA wifi module.

 

My power supply is set to 3.30V with a current limit of 2A.

 

I’m using a 3.3V, USB to serial breakout board (FT232R breakout board) between the windows desktop and the module.

 

I’m using bray’s terminal on the windows side of things.

 

When I power up the module, this is what I get:

+WIND:1:Poweron (141106-0950875-SPWF01S) 

+WIND:13:ST SPWF01SA1 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:21:WiFi Scanning

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

 But, when I send in any “AT�? or and other command, the module does not respond and seems to lockup.

 

When I received the module yesterday, I would occasionally get an “OK�? to an “AT�? command and other commands would occasionally work.

 

Using an o-scope now, the serial comm seems to be getting to and from the module. (Is it normal for the serial out from module to peak at only 2.5V?) 

Are there any ideas on how I can resurrect the module?

-matt
2 REPLIES 2
Posted on December 27, 2015 at 16:15

Hi Matt,

I have no ''wifi 4 click'' board to perform any test.

SPWF01Sx modules have I/Os @ 2V

5

. If you want to be compliant to datasheet, you should use a level translator between module and serial converter.

In the meanwhile, you can try to reduce power supply to 3V0 (3V1 to be compliant...). Let me know if helps.

Ciao

jerry

mmeerian
Associate
Posted on December 28, 2015 at 17:18

Well, that was embarrassing.  I had two issues:

-inadequate power cables

-There was no <CR><LF> when sending commands using the ''macro'' buttons in brays terminal.  (I have not used brays terminal much)  A ''$0d$0a'' was added to end of all of the commands in the macros and then it worked great.