Skip to main content
Matti Sillanpaa
Matti Sillanpaa
Associate III
June 14, 2017
Question

Yet another SPI SPWF04S problem

  • June 14, 2017
  • 4 replies
  • 3511 views
Posted on June 14, 2017 at 12:07

Hi all.

I'm having trouble connecting to AP with SPI mode. I tried to same network with putty and USB-to-UART cable and it connected fine (I only did ping over the connection, so not much). However with SPI it connects and drops it right away and repeats it forever.

Initializing SPWF04SA Interface..

>> Configuration Failure no 2 <-----i

nteresting, 'RAM cannot be mounted'

<<WIND 7, status 0

10

<<WIND 1, status 0

170216-fd39c59-SPWF04S

<<WIND 13, status 0

SPWF04SA

<<WIND 65, status 0

1

<<WIND 0, status 0

<<WIND 3, status 0

20

<<WIND 32, status 3

>>AT

<<OK

>>AT

<<OK

>>AT

<<WIND 49, status 2

0

<<OK

>>AT

<<OK

>>AT

<<OK

<<WIND 32, status 3

wifi started and ready...

>>AT

<<corrupted OK packet!!

<<OK

End of Initialization..

>>connecting to AP... TPNY, xxxxxxxxxx, 2

>>AT

<<corrupted OK packet!!

<<OK

>>AT

<<OK

>>AT

<<OK

>>AT

<<OK

>>AT

<<OK

>>AT

<<OK

<<WIND 32, status 3

<<WIND 21, status 4

<<WIND 35, status 4

00

<<WIND 19, status 7

98:DE:D0:EA:4C:62

<<WIND 25, status 7

TPNY

<<WIND 41, status 7

2

<<WIND 21, status 4

<<WIND 35, status 4

00

<<WIND 21, status 4

<<WIND 35, status 4

00

<<WIND 19, status 7

98:DE:D0:EA:4C:62 (after this it loops back line <<WIND 25 status 7)

The RAM mount thing is a littlebit worrying.

Othervise it seems to connect-disconnect-connect forever.

My setup is STM32F469NI, 1Mhz (currently) SPI and X-Nucleo-IDW04A1 board.

#spwf04sa

Note: this post was migrated and contained many threaded conversations, some content may be missing.
    This topic has been closed for replies.

    4 replies

    Gerardo GALLUCCI
    Gerardo GALLUCCI
    ST Employee
    June 14, 2017
    Posted on June 14, 2017 at 17:42

    Ciao Matti,

    there is something strage.

    Configuration failures (WIND:7) with reason code < 10 are rare and 'blocking'. It means that if you get that error, module will not boot. I see here that module goes on...

    What's the reason code for disconnection?

    Try to clean module's variables. AT&F (or GPIO0 high at boot), and start from scratch

    j

    Matti Sillanpaa
    Matti SillanpaaAuthor
    Associate III
    June 15, 2017
    Posted on June 15, 2017 at 08:41

    Hi Gerardo.

    Ok, booted the module with jumper in the JP2 and then rebooted it without it. No effect on the module. I'll see what happens if i put the firmware again to module altough it's the same version as the one currently in it.

    Don't know about the reason, but first time it seems that there's :

    <<WIND 49, status 2 <---WPA terminated

    After that it's just:

    <<WIND 41, status 7 <----Wifi disassosiation, don't know about the status code.

    2

    -----------------

    Regarding the driver package (

    http://www.st.com/content/st_com/en/products/embedded-software/mcus-embedded-software/stm32-embedded-software/stm32cube-expansion-software/x-cube-wifi1.html

    ). When I download it the version is still 3.0.1 in both name and in version history document.
    Gerardo GALLUCCI
    Gerardo GALLUCCI
    ST Employee
    June 15, 2017
    Posted on June 15, 2017 at 10:50

    Ciao Matti,

    - JP2 is boot pin. Use GPIO0 instead.

    - just downloaded v3.0.2 from link above. It's ok in links, project name, release note, file content, etc.

    Mridupawan Das
    Mridupawan Das
    Visitor II
    June 16, 2017
    Posted on June 16, 2017 at 08:37

    websocket, mqtt and tftp implementation are not complete, so please don't try that. we hope to support it in the next release cycle. Usage logic for sockets are same. you seem to be using secure socket.

    Beware that only mutual and one-way auth are supported in SPWF04. Anonymous mode won't work. So you must supply certificates.

    Matti Sillanpaa
    Matti SillanpaaAuthor
    Associate III
    June 16, 2017
    Posted on June 16, 2017 at 09:10

    Ok. So has this changed vs SPWF01? It worked just fine in this area.

    If I need to do something with certificates, are there any instructions how to work with those.

    Mridupawan Das
    Mridupawan Das
    Visitor II
    June 16, 2017
    Posted on June 16, 2017 at 10:14

    Hi Matti,

    yes, SPWF01 supports anonymous, one-way and mutual auth. SPWF04 only supports one-way and mutual auth. So yes that has changed.

    regarding usage of certificates, there is no immediate instructions but I will check if we can direct you to some docs.

    regards,

    Mridu

    Mridupawan Das
    Mridupawan Das
    Visitor II
    June 16, 2017
    Posted on June 16, 2017 at 10:58

    you can check the doc: AN4963

    : Security on SPWF04S module

    at 

    http://www.st.com/en/wireless-connectivity/spwf04sc.html

    Matti Sillanpaa
    Matti SillanpaaAuthor
    Associate III
    June 16, 2017
    Posted on June 16, 2017 at 11:02

    Ok, I'll check that. Thanks a lot for support.

    Any plans on adding that anynomous mode to SPWF04?

    Gerardo GALLUCCI
    Gerardo GALLUCCI
    ST Employee
    June 16, 2017
    Posted on June 16, 2017 at 14:00

    Hi,

    no plans for anonymous on 04.

    Using a cipher with anonymous authentication means that no authentication of the server will be done inside the TLS handshake and thus the connection is open for 'man in the middle' attacks.

    Terms & ConditionsAccessibility statement