cancel
Showing results for 
Search instead for 
Did you mean: 

SPWF04SA Console active not correctly formated

Pascal Zosso
Associate II
Posted on November 14, 2017 at 18:30

Hello,

I am using the SPWF04 to provide Wifi acces to my system, interfacing by SPI. SPI works fine but I receive the following 'Console active' WIND message:

02 10 00 02 00 0d 

sync

KOE : WIND

Indication Nb : WIND ID 0 -> 'console active'

length : 0x0002

payload : '<cr>'

In UM2114 there is no payload for this WIND message, then my question is :

Why the payload lenght is 2 but the payload is only one Carriage Return char? Is it normal?

Thank you for your help

In attachement, the SPI dialog without MOSI to receive the WIND message

#console #spi #spwf04 #wind-message
1 ACCEPTED SOLUTION

Accepted Solutions
Posted on November 15, 2017 at 07:08

Ciao Pascal,

<Cr> should not be part of SPI protocol. This bug has been fixed into FW1.1.0 (on st.com in a few days)

View solution in original post

3 REPLIES 3
Posted on November 15, 2017 at 07:08

Ciao Pascal,

<Cr> should not be part of SPI protocol. This bug has been fixed into FW1.1.0 (on st.com in a few days)

Pascal Zosso
Associate II
Posted on November 15, 2017 at 17:03

Hello,

Thank you for your reply. As I expected, a <LF> char was not read by my code because the nIRQ line was put high, now my code can read it. It explains why the length was 2. It looks like the nIRQ is put high before the <LF> was sent.


_legacyfs_online_stmicro_images_0690X0000060N01QAE.png

So, in the version FW1.1.0, the ''Console active'' message will be : 0x02 0x10 0x00 0x00 0x00 , right?

Posted on November 15, 2017 at 19:05

<Cr> and <Lf> are not needed over SPI, since the master knows how many bytes are going to be received (by length into the header packet).

New FW for SPWF04 will be released at the same time with new FW for XCube WiFi. So, protocol will be updated also on referenced SPI master.