This document describes how to use the RS-WC-301 EVB. It describes the
sequence of commands and set-up requirements to quickly evaluate the
major functions of the modules. The document should be used in
conjunction with the Programming Reference Manual (PRM) where all
commands to configure and operate the modules are described in detail.
Even if the user does not plan to use the UART interface, it is
recommended to go through the UART sections because all the set-ups to
evaluate different functionalities of the module in UART mode are directly
reusable in the SPI and USB modes also.
The RS-WC-301 EVB has various switches and headers to enable the user to
configure it for different scenarios.
Figure 1: RS-WC-301-EVB
USB Connector for Power
The power for the board can be supplied through this connector. Note that this
connector is used only for supplying power. For actual communication using
USB, the USB interface described below is used.
Power Selection Switch
The power selection switch should be put in the position shown in the figures
above so that the board receives power from the USB connector.
Reset
Push button reset for the board. Note that there is a power-on reset circuit on
the board that generates the necessary reset. This additional push-button is to
reset the module during normal operation.
UART Connector
A DB9 connector is provided to interface the UART port.
Not used in current
firmware. Should be left
unconnected
7
UART-RTS
-
Not used in current
firmware. Should be left
unconnected
8
GND
-
Ground
9
GND
-
Ground
10
GND
-
Ground
Switch #
UART Mode
SPI Mode
USB
1
ON
ON
ON
2
ON
OFF
ON
3
ON
ON
OFF
4
ON
ON
ON
If the EVB needs to be connected to the serial interface of an MCU platform, this
header can be used. The voltage level of the UART Tx and Rx pins of this header
is 3.3V. The Ground pin should be connected to a corresponding ground signal of
the MCU board. For RS-WC-301 the header assignment is shown below
Table 1:UART Header (RS-WC-301)
Mode Selection Switches
To select the interface in the EVB, configure the individual switches of Mode
Selection Switch bank as shown in the below table.
Table 2: Interface Selection
Card Ready
The Card Ready LED glows after the module has booted up successfully. It is an
indication that the EVB is ready to accept commands from the Host.
Handshake signal used in SPI
mode and connected to a GPIO
pin of the Host MCU. In other
modes, this signal can be left
open
2
NC - No connect
3
RESET_N
Input
Active low reset input. This can
be connected to the Host MCU to
reset the module from the Host.
If not used, should be left open
4
NC - No connect
5
WAKEUP
Input
The module wakes up from sleep
if a logic high is driven into this
pin. Used only in SPI mode,
should be left open in UART
mode
6
PT_GPIO2
Output
Pass through output pin
controllable by Host software.
Not used in current firmware,
should be left open
7
ADC2
Input
Analog input to internal ADC. Not
used in current firmware, should
be left open
8
PT_GPIO1
Output
Pass through output pin
controllable by Host software.
Not used in current firmware,
should be left open
9
GND
-
Ground
10
VCC
Power
3.3V power supply. If the USB
port for power supply is not
used, this pin can be used to
drive power to the EVB from the
Host MCU platform. The direction
of the “Power Selection” switch is
ignored in this case. The
maximum current sourcing
capacity of the Host should be
500mA. If not used, this pin
should be left open
11
ADC1
Input
Analog input to internal ADC. Not
used in current firmware, should
The LED indicates that wireless data transfer activity is in progress. This LED is
not used in the current firmware.
Used to indicate through logic
high that BT is transmitting high
priority traffic. When BT
coexistence is not used, this pin
should be grounded
14
NC - No connect
15
WLAN_ACTIVE
Output
Used for BT Coexistence. It
indicates with logic high that
WLAN activity is in progress.
When low, BT device has the
opportunity to transmit. Not used
in current firmware, should be
left open
16
NC - No connect
17
NC - No connect
18
NC - No connect
19
NC - No connect
20
GND
-
Ground
Pin
number
Pin name
Direction
Description
1
SPI_READY
Output
Handshake signal used in SPI
mode and connected to a GPIO
pin of the Host MCU. In other
modes, this signal can be left
open
2
NC - No connect
3
RESET_N
Input
Active low reset input. This can be
connected to the Host MCU to
reset the module from the Host. If
not used, should be left open
4
NC - No connect
5
WAKEUP
Input
The module wakes up from sleep
if a logic high is driven into this
pin. Used only in SPI mode,
should be left open in UART mode
6
PT_GPIO2
Output
Pass through output pin
controllable by Host software. Not
used in current firmware, should
be left open
7
NC - No connect
8
PT_GPIO1
Output
Pass through output pin
controllable by Host software. Not
used in current firmware, should
3.3V power supply. If the USB
port for power supply is not used,
this pin can be used to drive
power to the EVB from the Host
MCU platform. The direction of the
“Power Selection” switch is
ignored in this case. The
maximum current sourcing
capacity of the Host should be
500mA. If not used, this pin
should be left open
11
NC - No connect
12
NC - No connect
13
BT_PRIORITY
Input
Used to indicate through logic
high that BT is transmitting high
priority traffic. When BT
coexistence is not used, this pin
should be grounded
14
NC - No connect
15
WLAN_ACTIVE
Output
Used for BT Coexistence. It
indicates with logic high that
WLAN activity is in progress.
When low, BT device has the
opportunity to transmit. Not used
in current firmware, should be left
open
16
NC - No connect
17
NC - No connect
18
NC - No connect
19
NC - No connect
20
GND
-
Ground
Pin
Number
Pin Name
Direction
Description
1
NC
-
No connect
2
SPI_CS
Input
SPI slave select. Active low.
3
GND
-
Ground
4
NC
-
This pin must be left unconnected
5
SPI_CLK
Input
SPI clock. Max frequency of 12.5
Table 4: General Purpose Header(RS-WC-301-EVB)
SPI Header
The SPI header is used to connect the SPI interface of the module to a Host
MCU.
Active high, level triggered
interrupt, used in SPI mode. The
interrupt is raised by the module
to indicate there is data to be
read by the Host, or to indicate
the module has woken up from
sleep. In UART mode, it can be
left open
10
NC
-
No connect
Pin
Number
Pin Name
Direction
Description
1
NC
-
No connect
2
NC
-
No connect
3
GND
-
Ground
4
NC
-
This pin must be left unconnected
5
ADC2
Input
Analog input to internal ADC. Not
used in current firmware, should
be left open
6
GND
-
Ground
7
ADC1
Input
Analog input to internal ADC. Not
used in current firmware, should
be left open
8
WF_HNDSHKE1
Input
Handshake signal for wireless
firmware upgrade. Should be
connected to a GPIO pin of the
Host MCU
9
NC
-
No connect
10
WF_HNDSHKE2
Ouput
Handshake signal for wireless
firmware upgrade. Should be
connected to a GPIO pin of the
Host MCU
UART Interface Selection
Table 5: SPI Header Pins
These switches are present in RS-WC-301-EVB. If both the switches are
put in the direction shown by the green arrow, the DB9 connector for
UART is selected. If the switches are put in the direction shown by the
red arrow, the “UART Header for MCU” is selected.
This is a USB 2.0 interface and is supported in firmware version
2.0.0.1.2.4 and above.
Jumper
The jumper shown in some versions of the EVBs can be used for
measurement of current consumed by the module.
NOTE: EVB Versions below 3.1 do not support Power Save Mode 3 (Refer to
Programming Reference Manual version 1.9 or higher for definition of this mode).
2.1 Test Setup
The following additional components (not included with the EVB) are
required to complete the procedures described here.
1. PC with an available serial port, and running Windows XP. The PC
would be interfaced to the UART port of the EVB.
2. An 802.11a, 11b, 11g, or 11n Access Point with administrative
access to change its settings
3. A RADIUS server for operation in enterprise security mode (see
section Evaluation of Client Mode with Enterprise Security for
details)
4. A Wi-Fi Direct™ compatible mobile phone or laptop (see section
Evaluation of Wi-Fi Direct Mode )
5. A third party client device, such as a laptop or Wi-Fi phone, for
The following sections describe how to use the Evaluation Board in UART
mode. The sections should be used in conjunction with the Programming
Reference Manual to understand the commands better.
3.1 Configure Serial port in PC
To know the COM port name, check the computer‟s Device Manager settings.
The COM port name is displayed in the window. Hyperterminal or Teraterm
should be opened and configured accordingly with this COM port name.
The steps for configuring Hyperterminal are shown below.
Complete the settings as shown below and click OK.
3.2 Configure Serial Port Monitor in the PC
The actual bytes exchanged between the module and the Host PC may
not all be readable on Hyperterminal or Teraterm because of ASCII
conversion. A serial port monitor1 can be used to see the actual bytes. A
free package is available at http://www.serial-port-monitor.com/ , while
other similar software such as Hterm, Docklight etc. also provide good
interfaces to simultaneously view ASCII and actual bytes exchanged in
the UART interface. The following sections assume that HHD Free Serial
Port Monitor has been installed from the above link.
Open the “HHD Free Serial Port Monitor” BEFORE opening the
Hyperterminal or Teraterm. Click on File -> New Session. Select “Serial
Port Monitor”. Select the appropriate COM port and “Request view” for
the display format.
Redpine Signals Inc. assumes no liability for damages of any kind resulting from