Redpine Signals, Inc.
Page 58
R
R
S
S
-
-
W
W
C
C
-
-
3
3
0
0
1
1
E
E
v
v
a
a
l
l
u
u
a
a
t
t
i
i
o
o
n
n
B
B
o
o
a
a
r
r
d
d
U
U
s
s
e
e
r
r
G
G
u
u
i
i
d
d
e
e
V
V
e
e
r
r
s
s
i
i
o
o
n
n
2
2
.
.
5
5
1
1
2.
The DIP switches should be configured to put the EVB in SPI mode
according to table
Interface Selection
.
3.
The source code of a sample driver, API set and application is
provided with the Software Package. The developer should port the
source code into the target platform. Appropriate HAL changes may
be required for porting.
a.
The Driver source code is present in the software package
inside RS.WSC.x.x.GENR.x.x.x.x.x.x\Resources\SPI\Driver\
b.
The porting guidelines to port the driver are present in the
document RS-WC-301_Software_PRM.pdf in the section
“
Driver Porting Guide for SPI
”
c.
The section “
RS-WC-301 in SPI mode
” in RS-WC-
301_Software_PRM.pdf should be carefully read to understand
all the commands to configure and operate the module.
4.
The following settings should be observed to use the SPI interface
a.
SPI CPOL=0
b.
SPI CPHASE=0
c.
Max SPI Clock = 12.5 Mhz (For detailed timing information on
the SPI signals, please refer to the Datasheet).
d.
The Interrupt output from the module is active high, level
triggered.
10.1
Sample flow for evaluating SPI mode
The set-ups described in the previous sections describing the UART
interface (Client Mode with Personal Security, Client Mode with Enterprise
Security, Wi-Fi Direct Mode and Access Point mode can be used to
evaluate the module in SPI mode. A sample flow for evaluating the
module in different modes is given below. The Application running in the
Host should execute this flow by calling the different APIs provided.
