Redpine Signals RS9110-N-11-22, RS9110-N-11-24, RS9110-N-11-28, RS9110-N-11-26 User Manual

RS9110-N-11-22/24/26/28 – Self-Contained

WLAN Modules with Networking Stack

UART Evaluation Board User Guide

VVeerrssiioonn 11..1133

April ’10

Redpine Signals, Inc.

Redpine Signals, Inc.

2107 N. First Street, #680

2107 N. First Street, #680

San Jose, CA 95131.

San Jose, CA 95131.
Tel: [phone]

Tel: [phone]

Fax: [phone]

Fax: [phone]

Email: [e-mail]

Email: [e-mail]

Website: www.redpinesignals.com

Website: www.redpinesignals.com

Redpine Signals, Inc

. Proprietary and Confidential

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

Overview

The RS9110-N-11-22/24/26/28
modules are complete IEEE 802.11bgn
and 802.11abgn based wireless device
servers that directly provide a wireless
interface to any equipment with a serial
or SPI interface for data transfer. They
integrate a MAC, baseband processor,
single/dual band RF transceiver with
power amplifier in hardware; and all
WLAN protocol and configuration
functionality, networking stack, and
HTTP server in embedded firmware to
make a fully self-contained 802.11n
WLAN solution for a variety of
applications. The RS9110-N-11-22/26
modules integrate an antenna and a
frequency reference also to further
reduce the complexity of integrating the
solution.

Applications:

 Seamless Wi-Fi connectivity for

Application Processors

 Industrial M2M communications
 Point of Sale Terminals
 Metering (Parking Meters, Utility

Meters, Power Meters, etc.)

 Security Cameras and Surveillance

Equipment

 Logistics and Freight Management

 Warehousing
 Digital Picture Frames
 Several medical applications

including Patient Monitoring, Remote
Diagnostics

Device Features:

 Compliant to 802.11b/g, 802.11a

and single stream draft 802.11n

 Fully self-contained serial-to-

wireless functionality

 Includes all the protocol and

configuration functions for WLAN
connectivity in Open, WPA/WPA2­PSK and WPA/WPA2-Enterprise
modes of operation

1

 Payload data through Serial

Interface and SPI

 Terminates TCP and UDP

connections, and offers transparent
serial modem functionality

 Configuration through UART or

Wireless means

 Bluetooth coexistence support
 Integrated antenna, frequency

reference and low-frequency clock in
the RS9110-N-11-2X/26 modules

 Ultra-low-power operation with

power-save modes

 Ad-hoc and infrastructure modes for

maximum deployment flexibility

 Single supply – 3.1 to 3.6V

operation

1

Refer to the datasheets of the individual modules to know which features are

supported by which modules.

Redpine Signals, Inc. Proprietary and confidential Page 2

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

RS9110-N-11-22 System Block Diagram

GPIO

BT Coexistence I/f

Host Proce ss or

Applications

Serial I/f

UART Port

SPI Host

I/f

3.3V
Supply

Res e t

RS9110

TCP/UDP

WLAN Stack

Reset

RS9110-N-11-24 System Block Diagram

Reference Frequency

SPI/UART
Selection

RF

Transceiver

Flash

RS9110 WLAN Subsystem

XO

LED

Flash

RS9110-N-11-22

UART/SPI Select

RF
FE

Test Port

Reset

T/R

Switch

Balun

RS9110-N-11-24

3.3V

RF Transceiver

+

PA

RS9110

(TCP/UDP,

WLAN Stack)

Flash

Peripheral I/O,

GPIO

BT Coexistence i/f

UART

SPI

Hos t Proces so r

Ap plic ations

Redpine Signals, Inc. Proprietary and confidential Page 3

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

RS9110-N-11-26 System Block Diagram

3.3V

UART/SPI Select

BT Coexistence i/f

5

G

z

T/R

Switch

Diplexer

Diplexer

2

Balun
Balun

H

z

H

G

.

4

G

5

.

2

4

G

RF

Transceiver

+

PA

WLAN Subsystem

Reset

RESET XO LED Flash

RS9110-N-11-26

RS9110-N-11-28 System Block Diagram

Reference

RF

PA

+

Frequency

Diversity
Antennas

T/R

Switch

Reset

Diplexer

Diplexer

2

Balun
Balun

3.3V

5

G

z

H

z

H

G

4

.

G

5

.

2

4

Transceiver

G

RS9110

(TCP, UDP,

WLAN Stack)

Flash

RS9110

(TCP, UDP,

WLAN Stack)

UART

SPI

Peripheral I/O,

GPIO

UART/SPI Select

BT Coex istence i/f

UART

SPI

Host Pro ce ss or

Applications

Host Processor

Applications

Document Conventions

This document is for the following modules:
RS9110-N-11-22, RS9110-N-11-24, RS9110-N-11-26, RS9110-N-11-28
All references to RS9110-N-11-2X denote the above modules only.
These four modules are classified based on the hardware as depicted in the figure
below.

Redpine Signals, Inc. Proprietary and confidential Page 4

RS9110-N-11-28

Flash

Peripheral I/O,

GPIO

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

RS9110-N-11-2X

Single Band

(2.4 GHz)

With XO &

Antenna*

RS 9110-N-11-22 RS 9110-N-11-24 RS 9110-N-11-26 RS9110-N-11-28

*Option for u. FL connector for External Antenna

Wi thout XO &

Antenna

With XO &

Antenna*

Dual Band

(2.4 and 5 GHz)

Wi thout XO &

Antenna

Hardware
Diffe r entiation

Redpine Signals, Inc. Proprietary and confidential Page 5

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

Table of Contents

1: System Overview ................................................................. 8

1.1: Scope....................................................................................... 9

1.2: Limitations............................................................................... 9

2: Getting Started................................................................... 10

2.1: Connecting the RS9110-N-11-2X EVB .................................... 10

2.2: Configuring the RS9110-N-11-2X Module .............................. 11

2.2.1: Initialize the COM port of the PC................................................. 13

2.2.2: Scan............................................................................................ 15

2.2.3: Connect to a Scanned Access Point in Infrastructure Mode ........ 16

2.2.4: Connect to an IBSS Network....................................................... 17

2.2.5: Connect to a Hidden Access Point............................................... 18

2.2.6: Creating a IBSS Network ............................................................ 18

2.3: IP Address Configuration....................................................... 19

2.3.1: Manual Configuration ................................................................. 19

2.3.2: DHCP Configuration .................................................................... 20

2.4: Disconnect from Access Point ................................................ 21

2.5: TCP (UDP)/IP Evaluation....................................................... 22

2.5.1: DUT Application.......................................................................... 22

2.5.2: Peer Application ......................................................................... 23

2.5.3: Test setup and Evaluation........................................................... 23

2.5.3.1: Create Sockets...................................................................... 26

2.5.3.2: Send And Receive Data (UDP, TCP Client, LUDP) .................. 29

2.5.3.3: Send And Receive Data (TCP Server) .................................... 31

2.5.3.4: List Sockets .......................................................................... 31

2.5.3.5: Close Sockets........................................................................ 32

2.5.3.6: Power modes........................................................................ 33

3: Firmware Upgrade.............................................................. 38

4: Components on the EVB and their Usage............................ 42

4.1: DIP Switches ......................................................................... 43

4.2: Header J4............................................................................... 43

4.3: Header J7............................................................................... 44

4.4: Header J6............................................................................... 44

4.5: Switches SW4 and SW5 ......................................................... 44

Redpine Signals, Inc. Proprietary and confidential Page 6

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

Table of Figures

Figure 1: RS9110-N-11-2X Software Architecture Block Diagram ................ 8

Figure 2: EVB of the RS9110-N-11-22/24 Modules .................................... 10

Figure 3: EVB for RS9110-N-11-26/28 Modules......................................... 11

Figure 4: Wi-Fi Config Utility Startup Screenshot....................................... 12

Figure 5: System Properties Window ......................................................... 13

Figure 6: COM Port Name ........................................................................... 14

Figure 7: Opened the COM Port successfully .............................................. 15

Figure 8: Wi-Fi Config Utility showing the list of Scanned Access

Points/IBSS Stations ................................................................................. 16

Figure 9: Wi-Fi Config Utility displaying the "Connected" Status................ 17

Figure 10: Connected to a IBSS Network.................................................... 18

Figure 11: Creating a IBSS Network........................................................... 19

Figure 12: IP Address Configured............................................................... 20

Figure 13: IP Address Configured through DHCP........................................ 21

Figure 14: Screenshot showing the Disconnected message........................ 22

Figure 15: Test setup for TCP (UDP)/IP Evaluation.................................... 23

Figure 16: Startup window for UDP Server Application .............................. 24

Figure 17: Startup window of UDP Client Application................................. 25

Figure 18: COM Port opened successfully by the Clie nt application............ 25

Figure 19: Enter Socket type...................................................................... 26

Figure 20: Socket type – TCP...................................................................... 27

Figure 21: Socket type – UDP..................................................................... 27

Figure 22: Socket type – LTCP.................................................................... 28

Figure 23: Socket Type- LUDP.................................................................... 29

Figure 24: Parameters and Result for Send and Receive Data on UDP Socket

................................................................................................................... 29

Figure 25: Parameters and Result for Send and Receive Data on TCP Socket

................................................................................................................... 30

Figure 26: Server Application Starts Receiving Packets ............................. 31

Figure 27: Query Connection status and transmit/receive the data ........... 31

Figure 28: List Sockets............................................................................... 32

Figure 29: Close Sockets ............................................................................ 32

Figure 30: Sleep Timer Configuration......................................................... 33

Figure 31: Power Mode 1 - Before WLAN Connection ................................. 34

Figure 32: Power Mode 2 - Before WLAN Connection ................................. 35

Figure 33: Power Mode 1 - After WLAN Connection.................................... 36

Figure 34: Power Mode 2 - After WLAN Connection.................................... 36

Figure 35: Prompt to upgrade firmware..................................................... 39

Figure 36: Transferring "taim1"................................................................. 40

Figure 37: Firmware upgrade successful.................................................... 41

Figure 38: Components on the EVB of RS9110-N-11-22/24 Modules ......... 42

Figure 39: Components on the EVB of RS9110-N-11-26/28 Modules ......... 43

Figure 40: Pin Configuration of Header J7.................................................. 44

Figure 41: Pin Configuration of Header J6.................................................. 44

Redpine Signals, Inc. Proprietary and confidential Page 7

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

1: System Overview

The following diagram depicts the software architecture of the RS9110-N-11-2X
module.

HOST PROCESSOR (H OST)

Application

Station

Managment Entity

WPA/WPA-2

UART Driv erSPI Driver

SPI

Host Abstraction Layer

SLIP

Wireless Control Block

802.11 b/g/n MAC

UART

UARTSPI

TCP/IP

Figure 1: RS9110-N-11-2X Software Architecture Block Diagram

Redpine Signals, Inc. Proprietary and confidential Page 8

RS9110-N-11-2X

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

As shown in the figure above, the RS9110-N-11-2X module is integrated with the
Host using either UART or SPI interfaces. The transmission and reception of the
data to/from the Host depends on the interface used to connect the module as
briefed below.

UART mode:
The Host transmits/receives raw data using UART interface when RS9110-N-11-

2X is configured for UART mode. The access to the TCP/IP stack in the Wi-Fi
module through UART is provided through AT commands.

SPI mode:

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

Host trans
mode. A thin driver on the Host takes care of interacting with the Wi-Fi module
through the SPI Host interface.

mits/receives raw data when RS9110-N-11-2X is configured for SPI

1.1: Scope

The scope of this document is to guide the user in setting up the Evaluation
Board (EVB) of the RS9110-N-11-2X module to be used as a Wireless Device
Server and interact with Applications on the Host using the UART interface. The
following topics are discussed:

 Procedure to use the “Wi-Fi Config Utility” GUI, wh ich configures the

RS9110-N-11-2X module.

 Procedure to evaluate the TCP/IP, UDP/IP protocols using RS9110-N-11-

2X module

 Procedure to perform firmware upgrade on the RS9110-N-11-2X module.

The “Wi-Fi Config Utility” GUI and the command s explained in this document
configure the RS9110-N-11-2X module only when it is configured to use UART.

This document does not explain the design details/command formats of the
RS9110-N-11-2X module.

1.2: Limitations

My name is Rohan Joginpalli.

1. The “Wi-Fi Config Utility” explained in this document is only for the
Windows Operating System.

2. The maximum size of the raw data to be transmitted/received is 1000.

3. The maximum numbers of sockets supported in the current release of the
firmware are 8.

4. Security, DHCP and Power Save modes are not supported in IBSS.

Redpine Signals, Inc. Proprietary and confidential Page 9

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

2: Getting Started

The following steps are to be performed to establish a Wi-Fi network and open a
network connection using the RS9110-N-11-2X module.

1. Connect power supply to the RS9110-N-11-2X EVB and switch it on.

2. Configure the RS9110-N-11-2X module using “Wi-Fi Config Utility”.

2.1: Connecting the RS9110-N-11-2X EVB

1. Connect the Male end of the supplied serial cable to the RS9110-N-11-2X
EVB’s serial port.

2. Connect the Female end of the DB9 serial cable to a PC’s serial COM port.

3. Connect the USB power cable to the RS9110-N-11-2X EVB and to a power
outlet and switch on the power to the EVB by toggling the Power Switch
(refer to the figures below).

DB9 Connector

RS9110-N-11-22

RS9110-N-11-24

Module

LED

Module

Figure

USB Power Supply

Power Switch

2: EVB of the RS9110-N-11-22/24 Modules2

2

The image shown here for the EVB may be different from the one delivered to the
user because of updates in design. Please follow the instructions in this document
irrespective of the image displayed here or contact Redpine Signals in case any help
is required.

Redpine Signals, Inc. Proprietary and confidential Page 10

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

DB9 Connector

RS9110-N-1 1- 26

RS9110-N-1 1- 28

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

Module

Module

LED

USB Power Sup ply

Power Switc h

Figure

3: EVB for RS9110-N-11-26/28 Modules3

4. Wait till the LED glows on the RS9110-N-11-2X module. This indicates the
completion of bootloading and initialization of the baseband and RF
components.

You are now ready to configure the module using the “Wi-Fi Config Utilit y”.

NOTE: Please make sure that the EVB is powered on, the LED is
glowing and the serial cable is connected before proceeding with the
steps in the following sections.

2.2: Configuring the RS9110-N-11-2X Module

The Wi-Fi Config Utility is a GUI based application used to configure the RS9110­N-11-2X module. To execute this utility, double-click on the executable RS9110­N-11-2X.exe found in the CD in the GUI folder.

NOTE: If a Wi-Fi connection has been configured previously and if you
wish to re-configure the RS9110-N-11-2X, please restart the procedure
explained below

The following is a screenshot of the GUI.

3

The image shown here for the EVB may be different from the one delivered to the
user because of updates in design. Please follow the instructions in this document
irrespective of the image displayed here.

Redpine Signals, Inc. Proprietary and confidential Page 11

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

Figu

4: Wi-Fi Config Utility Startup Screenshot

re

The following are the actions that are to be performed to configure the Wi-Fi
module using the GUI above.

1. Initialize the COM port of the PC to which the RS9110-N-11-2X EVB is
connected.

2. Select the baud rate with which the COM port is configured from the drop
down menu beside the “Baud Rate” label.

NOTE: PCs and Laptops with Windows XP usually support a maximum
baud rate of 115200 bps. If a higher baud rate is selected (e.g., in a
Hyperterminal), the observation has been that the baud rate that is
actually used is 115200 bps. This will be true for the Wi-Fi Config
Utility as well. This is a limitation of the PC rather than of the RS9110­N-11-2X EVB.

3. In case the user wants to connect to an Access Point or an IBSS Station
that is broadcasting its SSID, he/she will have to first scan for the list of
available Access Points/IBSS Stations and select the appropriate Access
Point/Station by clicking on it.

4. Alternatively, in case the user wants to connect to a hidden Access Point
whose SSID is known, he/she may enter the SSID in the GUI directly.

Redpine Signals, Inc. Proprietary and confidential Page 12

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

5. The user can then connect to an Access Point in Infrastructure mode or to
a second Station in IBSS mode.

6. The user then needs to configure the IP address, Subnet Mask and
Gateway Address for the TCP/UDP layer inbuilt in the RS9110-N-11-2X
module.

The procedure to perform the above mentioned actions are discussed in the
following sections.

2.2.1: Initialize the COM port of the PC

The following steps are to be followed to initiali ze the COM port of the PC to
which the RS9110-N-11-2X module is connected.

1. In order to initialize the COM port, the correct COM port name has to be
entered in the GUI.

2. To know the COM port name, open the System Properties window by
right-clicking on "My Computer" and clicking "Properties".

Redpine Signals, Inc. Proprietary and confidential Page 13

Figure

5: System Properties Window

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

3. In

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

the window that opens, click on the "Hardware" tab followed by the

"Device Manager" button.

4. In the new window that opens, double-click on "Ports (COM & LPT)".

5. The COM port name is the data in the brackets as shown in the screenshot
below.

COM Port Name

Figure

6: COM Port Name

6. IBSS In the Wi-Fi Config Utility, enter the COM port name and click on
“Open”.

7. The display on the bottom-left corner shows that the COM port connection
has been initialized successfully.

Redpine Signals, Inc. Proprietary and confidential Page 14

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

Figu

7: Opened the COM Port successfully

re

NOTE: In case the ABRD process fails, the GUI displays a message and
opens the COM port with the default settings. If the ABRD process
fails, it will mostly because of the connection betw een the PC and the
EVB not being proper. It’s recommended that the serial cable be used
directly without adapters like a USB-to-Serial adapter.

2.2.2: Scan

To scan for the available Access Points and IBSS Stations in all channels, click the
“SCAN” button. The list of scanned Access Points and IBSS Stations is displayed
on the GUI as shown below. The SSID corresponds to the SSID of the AP/IBSS
Station and mode is the security type. The RSSI value is also displayed as an
absolute value

4

RSSI is a negative value. The RSSI displayed on the GUI is an absolute value.

Hence, the lower the value displayed, the better is the Received Signal Strength.

4

.

Redpine Signals, Inc. Proprietary and confidential Page 15

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

Figu

8: Wi-Fi Config Utility showing the list of Scanned Access

re

Points/IBSS

Stations

2.2.3: Connect to a Scanned Access Point in Infrastructure Mode

The following actions are to be performed to connect to an Access Point.

1. Select a specific SSID in the list by clicking on it.

2. Enter the Pre Shared Key if the Access Point is configured to be in either
WEP, WPA or WPA2 mode5.

3. Select the transmission rate and
dBm), MEDIUM (10dBm) and HIGH (>=15dBm).

4. Click the “CONNECT” button to connect to the selected Access Point.

5. The status of the connection is displayed in the GUI as below. An error
status is displayed accordingly if the connection has failed.

5

Security is not supported in IBSS mode in the present firmware release

power. The modes of power are LOW (7

Redpine Signals, Inc. Proprietary and confidential Page 16

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

Figu

9: Wi-Fi Config Utility displaying the "Connected" Status

re

You are now connected to the WLAN network!

2.2.4: Connect to an IBSS Network

To connect to an IBSS Network the following steps are to be followed:

1. Select a specific IBSS SSID in the list by clicking on it.

2. Select the transmission rate and power. The modes of power are LOW (7
dBm), MEDIUM (10dBm) and HIGH (>=15dBm).

3. Select the Network type as IBSS.

4. Click the “CONNECT” button to connect to the selected IBSS Network.

5. The status of the connection is displayed in the GUI as below. An error
status is displayed accordingly if the connection has failed.

Redpine Signals, Inc. Proprietary and confidential Page 17

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

Figu

re 10: Connected to a IBSS Network

2.2.5: Connect to a Hidden Access Point

To connect to a hidden Access Point whose SSID is known, the following steps
are to be followed:

1. Click the “SSID” button.

2. Enter the SSID in the adjacent text field.

3. If security is enabled, enter the Pre Shared Key.

4. Click the “CONNECT” button to connect to the Access Point.

2.2.6: Creating a IBSS Network

To create an IBSS Network, the following steps are to be followed:

1. Enter the network name (SSID) in the “IBSS Creation” section of the GUI.

2. Select the Channel in which you the IBSS Network is to be created.

3. Click on the CREATE button to start the network.

4. The status of creation is displayed in the GUI as shown in the figure
below.

Redpine Signals, Inc. Proprietary and confidential Page 18

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

Figure

NOTE: The present firmware requires that the module be powered off
and on if a connection to a different BSS is required. After powering on
the module, the same steps are to be followed as before.

11: Creating a IBSS Network

2.3: IP Address Configuration

The RS9110-N-11-2X has an inbuilt TCP(UDP)/IP stack and thus provides an
option for the Host to transmit only application data, which is transmitted over
WLAN after TCP/UDP packetization.
The TCP/IP stack has to be configured with the IP Address, Subnet Mask and
Gateway Address.

The Configuration can be done in two ways:

1. Manual

2. DHCP

2.3.1: Manual Configuration

The user has to perform the steps below to configure the IP parameters.

1. Select the Manual Mode from the configuration utility.

2. Enter the IP Address in the dotted decimal format.

Redpine Signals, Inc. Proprietary and confidential Page 19

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

3. Enter

the Subnet Mask in the dotted decimal format.

4. Enter the Gateway Address in the dotted decimal format.

5. Click “OK” to complete the configuration.

2.3.2: DHCP Configuration

The user has to perform the steps below to obtain the IP address.

1. Select the DHCP Radio button from IP Configuration section of the
configuration utility.

2. Select the mode of reception of the data from the TCP/IP stack to the
application.

3. The IP parameters obtained from the Access Point are then displayed in
the corresponding fields.

Redpine Signals, Inc. Proprietary and confidential Page 20

Figure

12: IP Address Configured

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

Figu

re 13: IP Address Configured through DHCP

NOTE: For getting the IP parameters over DHCP, the Access Point
should be configured accordingly.

NOTE: DHCP is not supported in IBSS mode.
NOTE: The parameters that are loaded using the Wi-Fi C onfig Utility

are not stored in non-volatile memory. So when the module is powered
off and then powered on, it has to be configured with the values again.
In future firmware releases this will not be required.

NOTE: The IP address, Subnet Mask and Default Gateway have to be
configured through the GUI in case of manual mode by clicking the
“OK” button prior to executing the applications used to validate the
TCP/IP stack.

2.4: Disconnect from Access Point

The “DISCONNECT” button can be used to disconnect from an Access Point to
which the EVB is associated (connected) over WLAN. This feature can be used if
the user wants to Scan and connect to another Access Point or to the same
Access Point again with different parameters. It’s expected that the Access Point
is also configured accordingly before attempting the connection again with the
changed parameters.

Redpine Signals, Inc. Proprietary and confidential Page 21

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

Figure

14: Screenshot showing the Disconnected message

2.5: TCP (UDP)/IP Evaluation

The Evaluation kit is supplied with DUT (Device Under Test) application and peer
applications for Windows OS to evaluate the (TCP) UDP/IP stack in the RS9110­N-11-2X module. The source code for these applications is also supplied.

2.5.1: DUT Application

The DUT Application (RS9110-N-11-2X_DUT_App.exe) is to be executed in the PC
to which the RS9110-N-11-2X EVB is connected using the RS232 cable. It
communicates with the TCP/IP stack in the RS9110-N-11-2X module over the
UART interface through AT commands. Please refer to the programmer’s
reference manual for the description of the AT commands.

The application RS9110-N-11-2X_DUT_APP.exe in the path
Applications\DUT_Application has to be executed to interact with the DUT.
Alternatively, the DUT Application can be launched from the Configuration GUI
also by copying it to the same folder as the Configuration GUI application and
clicking on the “Launch DUT Application” button after the IP address is configured
successfully.

Redpine Signals, Inc. Proprietary and confidential Page 22

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

2.5.2: Peer Application

The Peer application consists of a UDP server, TCP server and a UDP client that
are run when the corresponding sockets are to be evaluated on the DUT. The
UDP Server Application (RS9110-N-11-2X_UDP_Server_App.exe), TCP server
application (RS9110-N-11-2X_TCP_Server_App.exe), and TCP client application
(RS9110-N-11-2X_TCP_Client_App.exe) are to be executed on a PC, which is
connected to the Access Point through Ethernet or Wi-Fi.

All the peer applications receive the data from the corresponding socket on the
DUT and transmit the obtained data back to the socket (application).

2.5.3: Test setup and Evaluation

The figure below illustrates the test setup.

1

TCP/UDP

Client/Ser ver PC

(Windows XP)

RS232

RS9110-N-11-22

EVB

Figure

15: Test setup for TCP (UDP)/IP Evaluation6

To run the test, please follow the steps below.

1. Make sure that the Access Point and the Server/Client PC’s are
connected properly and are on the same network. If they are on
different networks, ensure proper routing between them.

2. Make sure that the RS9110-N-11-2X module has been configured
properly and connected to the Access Point as described in the
Sections 2.1

, 2.2, and 2.3.

3. Check the wireless connection via a ‘ping’ command that can be
executed on the peer PC.

4. On PC 2, double-click the RS9110-N-11-2X_UDP_Server_App.exe,
RS9110-N-11-2X_TCP_Server_App.exe and RS9110-N-11­2X_TCP_Client_App.exe files to communicate with the
corresponding application (socket) on PC 1.

Access Point

10/100

TCP/UDP

2

Server /Client

(Windows XP/Linux)

PC

5. If PC 2 has a Linux OS, then execute the applications RS9110-N­11-2X_UDP_Server_App, RS9110-N-11-2X_TCP_Server_App,
RS9110-N-11-2X_TCP_Client_App.

6

The test setup for the IBSS Network will not include the Access Point and the
RS9110-N-11-22 EVB will be connected to another IBSS client over WLAN through
the IBSS network.

Redpine Signals, Inc. Proprietary and confidential Page 23

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

re

Figu

16: Startup window for UDP Server Application

NOTE 1: The Port number (1024 in the above screenshot) or the IP
address can be configured for an application to a different value by
giving the following command in a console:

On Windows
“RS9110-N-11-2X_TCP_App_Client.exe yyy.yyy.yyy.yyy xxxx”
On Linux

RS9110-N-11-2X_TCP_App_Client yyy.yyy.yyy.yyy xxxx
Where “xxxx” is the port number and yyy.yyy.yyy.yyy is the IP

address in the dotted decimal format.
NOTE 2: The TCP server and the UDP server take only the port number

as the input whereas the TCP client takes the IP address and the port
number as inputs. These parameters correspond to the IP address and
the port number of the application (socket) on the DUT.

NOTE 3: The TCP server socket on the DUT has to be created prior to
the execution of the TCP client on the peer.

6. On the PC connected to the RS9110-N-11-2X EVB, double-click the
RS9110-N-11-2X_DUT_App.exe file. A console window opens as
shown below.

Redpine Signals, Inc. Proprietary and confidential Page 24

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

re

Figu

17: Startup window of UDP Client Application

7. Enter the name of the COM Port. To know the COM Port to which
the RS9110-N-11-2X EVB is connected, follow the steps given in

Section 2.2.1

. The following screen appears, asking the user to

enter a choice.

Figure

18: COM Port opened successfully by the Client application

Redpine Signals, Inc. Proprietary and confidential Page 25

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

The following sections explain the description of each choice with
shots.

2.5.3.1: Create Sockets

1. Enter

“1” (Create Sockets) as the choice.

2. The application asks to enter the type of socket as shown below.

the screen

Figure

19: Enter Socket type

3. If the choice entered is 0, a TCP client socket is created. The
application asks for the local port number of the socket, destin ation
IP address and the destination port number of the application on
the peer (TCP server).

Redpine Signals, Inc. Proprietary and confidential Page 26

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

re

Figu

20: Socket type – TCP

4. If the choice entered is 1, a UDP socket is created. The application
asks for the local port number of the socket, destination IP address
and the destination port number of the application on the peer.

5. If the choice entered is 2, an LTCP (Listening TCP) socket is
created. This will create a TCP server socket, which will be

Redpine Signals, Inc. Proprietary and confidential Page 27

Figure

21: Socket type – UDP

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

“listening” on a given port number for the connection to be
est

ablished by a TCP client. The application asks for the local port

number on which the socket should listen.

Figure

22: Socket type – LTCP

6. If the choice entered is 3, an LUDP (Listening UDP) socket is
created. This will create a listening UDP server socket, which will
be “listening” on a given port number for the data from any peer.
The application asks for the local port number on which the socket
should listen.

Redpine Signals, Inc. Proprietary and confidential Page 28

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

Figure 23: Socket Type- LUDP

7. On successful creation of the socke

t, a valid socket descriptor
returned by the TCP/IP stack is displayed, as shown in the figure
above.

2.5.3.2: Send And Receive Data (UDP, TCP Client, LUDP)

Enter

“3” (Send Data) as a choice. The application now asks for the number of
sockets, the socket numbers, the length of the data, the destination IP address,
the destination port and the number of packets to be sent and received on each
socket.

The number of sockets specifies the total number of sockets on which the data
has to be sent and received.

The socket numbers signify the sockets on which the data has to be sent and
received. The sockets have to be created for the data transmission and reception
to happen. If a wrong socket number is entered then the user is prompted to
enter a valid socket descriptor.

Figure

24: Parameters and Result for Send and Receive Data on UDP Socket

NOTE: In case of TCP Client socket Destination IP address and
Destination port number should be zero as shown in the figure below

Redpine Signals, Inc. Proprietary and confidential Page 29

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

re

Figu

25: Parameters and Result for Send and Receive Data on TCP Socket

The application starts transmitting and receiving the data packets through the
RS9110-N-11-2X module over Wi-Fi. The application displays the statistics as
shown in the figure above.

The application compares the received data with the sent data. Any failure in the
comparison results in a packet loss and is displayed accordingly.

The application sends and receives the number of packets specified.
The server receives and transmits these packets and also displays the number of

packets received/sent.

Redpine Signals, Inc. Proprietary and confidential Page 30

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

Figure

26: Server Application Starts Receiving Packets

2.5.3.3: Send And Receive Data (TCP Server)

If

a TCP server (LTCP) socket is created, the connection is est a blished only when
the TCP peer connects with the server. The DUT application queries for the
connection status on a particular TCP server socket till the connection is
established. Once the connection is established, the transmission and recept ion
of the data happens as shown in the figure below.

NOTE: In case of TCP Server Socket (LTCP) Destination IP address and
Destination port number should be zero.

Figure

27: Query Connection status and transmit/receive the data

2.5.3.4: List Sockets

st Sockets option lists the active sockets at a particular instance. The

The Li
socket descriptor and the socket type are displayed as below.

Redpine Signals, Inc. Proprietary and confidential Page 31

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

re

Figu

28: List Sockets

2.5.3.5: Close Sockets

The Close Sockets option closes an active socket. The socket descriptor of the
socket to be closed is the parameter for this option as shown below.

Redpine Signals, Inc. Proprietary and confidential Page 32

Figure

29: Close Sockets

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

2.5.3.6: Power modes

The RS9110-N-11-2X module supports the following 3 power modes. Please refer
to the Software PRM for the details of these power modes.

1. Power Mode 0 (Power save disabled – Default mode).

2. Power

Mode 1 (Power save with Host handshake).

3. Power Mode 2 (Power save without Host handshake).

2.5.3.6.1 Sleep Timer
The RS9110-N-11-2X module, when placed in Power Mode 1 while being in the

WLAN unconnected state, sleeps for the amount of time configured with the
“Sleep Timer” option in the “Power Save” submenu.

The unit for the sleep timer is milliseconds. The default value of the Sleep Timer
is 100 ms. The maximum value that can be configured is 10000 ms.

2.5.3.6.2 Power Mode 1 (unconnected state)
T

o trigger the power modes, enter choice 5 in the main menu. The following

screen shot shows the menu on selecting Power Mode 1 (Mode 1).
On entering the choice for Power Mode 1 the user is prompted to enter the Wi-Fi

connection status.
The user should enter ‘y’ or ‘Y’ if the module is connected to the Access point,

and ’n’ or ‘N’ if not connected.
After querying the Wi-Fi status with the user, the prompt for querying the

number of ACK messages to be issued for the SLEEP messages will be displayed.

Redpine Signals, Inc. Proprietary and confidential Page 33

Figure

30: Sleep Timer Configuration

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

The DUT application issues “ACK” messages for the received “SL
this power mode for the configured number of times.

NOTE: The user should configure the sleep timer before configuring the
module for Power Mode 1.

EEP” messages in

Figure

31: Power Mode 1 - Before WLAN Connection

2.5.3.6.3 Power Mode 2 (unconnected state)
To trigger the power m

odes, enter the choice 5 in the main menu. The following

screen shot shows the menu for the Power Mode 2 (Mode 2).
There is no negotiation with the host in this power mode. Thus, th e module is in

this mode till the user switches to Power Mode 0 (Mode 0).

NOTE: The direct switching between the Power Mode 1 and Power
Mode 2 is not possible. The user has to switch back to power mode 0
before switching between the two power modes.

Redpine Signals, Inc. Proprietary and confidential Page 34

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

re

Figu

32: Power Mode 2 - Before WLAN Connection

2.5.3.6.4 Power mode 1 (connected state)
To test

the Power Mode 1 in connected state, the module has to be connected to

an Access Point and configured with an IP address using the Configuration GUI.
After selecting the Power Mode 1 in the console, the user is prompted to “Enter

the number of ACKs to be issued for the Sleep”. The DUT application sends the
configured number of ACK messages for the obtained SLEEP messages before
sending/receiving each data packet.

The module continuously issues the SLEEP message after every DTIM period to
query the Host’s acceptance to go to sleep till the next DTIM interval expiry. The
DUT application issues the ACK message for the configured number of times
before sending or receiving data.

To send or receive data, please refer to Section 2.4.3.2

.

Redpine Signals, Inc. Proprietary and confidential Page 35

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

re

Figu

33: Power Mode 1 - After WLAN Connection

2.5.3.6.5 Power mode 2 (connected state)
To test Power Mode 2 in connected

state, the module has to be connected to an

Access Point and configured with an IP address using the Configuration GUI.
The following screen shot shows the selection of the Power Mode 2.

Figure

34: Power Mode 2 - After WLAN Connection

Redpine Signals, Inc. Proprietary and confidential Page 36

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

NOTE: The GUI can be used at any stage to Disconnect from the
Access Point and attempt a new connection. For this, the user need to
close the Test Applications and restart the GUI, since the COM port can
be used only by one application at any time. When the GUI is opened,
it will try to perform the ABRD process again and fail. Only after the
failure, the DISCONNECT button will be enabled.

Of course, in an embedded environment, the user can directly issue
the disconnect command (AT+RSI_DISASSOC) without attempting the
ABRD process.

Redpine Signals, Inc. Proprietary and confidential Page 37

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

3: Firmware Upgrade

The following steps explain the procedure for upgrading the firmware of the
RS9110-N-11-2X module.

1. Connect the power to the RS9110-N-11-2X EVB.

2. Connect one end of the supplied DB9F – DB9M null modem serial cable
to the RS9110-N-11-2X EVB’s serial port.

onnect the other end of the DB9 serial cable to a terminal or a PC’s

3. C
serial COM port.

4. Open a terminal emulation program, e.g., HyperTerminal, on Windows
XP. Configure the terminal with the following settings.

 Baud Rate = 115200
 Stop Bits = 1
 Pari
 Flow Control = No

5. Switch on the power to the EVB by toggling the Power Switch on the
EVB.

6. The module is configured for Auto Baud Rate Detection (ABRD) and
hence the module waits for approximately 40 to 50 seconds for ABRD
message exchange to be initiated by the Host as described in the
Software PRM. However, in the case of firmware upgrade through the
Hyperterminal, it’s not possible to perform the ABRD bytes’ exchange.
The user has to wait for the ABRD to fail and for the module to start
working at 115200 bps which is the baud rate that the module is
configured for if ABRD fails.

7. The user is now prompted to enter ‘y’ for a firmware upgrade or ‘n’ for
no firmware upgrade, as shown in the figure below.

ty = No

Redpine Signals, Inc. Proprietary and confidential Page 38

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

Figure

35: Prompt to upgrade firmware

8. The user should enter ‘y’ to stop the boot process with the default
firmware. The RS9110-N-11-2X module waits for a few seconds for the
prompt from the user and hence the user has to enter ‘y’ as soon as
the prompt appears.

8. The user has to now transfer the firmware files. The files, viz., taim1,
taim2, tadm1 and tadm2 (present in the Firmware folder of the CD),
have to be transferred in the same order from the HyperTerminal. The
following is the procedure to send a file through the HyperTerminal.

9. Click on “Transfer” on the toolbar of the HyperTerminal window.

10. Select “Send File” on the “Transfer” menu.

11. Click the “Browse” button to point to the path of taim1/taim2/tadm in
the Host system.

12. Select the protocol as “Kermit”.

13. Click the “Send” button to start the transfer.

Redpine Signals, Inc. Proprietary and confidential Page 39

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

Figure

36: Transferring "taim1"

14. For each file being transferred, wait for a display on the Hyperterminal
which says “Send <nextfile>”. Please note that after a file is
transmitted, there is some delay is writing the data to the non-volatile
memory. This might take a few seconds and the user has to wait for
the prompt on the Hyperterminal for the next file.

15. Once all three files are t ransferred, the following message is displayed
on the HyperTerminal.

Redpine Signals, Inc. Proprietary and confidential Page 40

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

37: Firmware upgrade successful

re

Figu

You are now ready to work with the new firmware!

Redpine Signals, Inc. Proprietary and confidential Page 41

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

4: Components on the EVB and their Usage

The RS9110-N-11-2X EVB has various switches and headers to enable the user to
configure it for different scenarios
components.

DB9 Connector

7

. The figure below shows the various

USB Power Supp l y

Switch SW4

RS9110-N-11-22

Header J4 (Debug)

HeaderJ7 (SPI)

Figure

Module

LED

DIP Switches

38: Components on the EVB of RS9110-N-11-22/24 Modules

Switch SW5

Power Switch

HeaderJ6 (UART)

Push Button (Reset)

7

Some of the older revisions of the EVB may not contain all the components
described in this section. Please contact Redpine Signals (with a picture of the EVB)
in case help is required to realize the functionality described in this section.

Redpine Signals, Inc. Proprietary and confidential Page 42

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

DB9 Connector

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

USB Power Supply

RS9110-N-11-26

RS9110-N-11-28

Header J4 ( Debug)

Module

Module

LED

DIP Switches

Figure

39: Components on the EVB of RS9110-N-11-26/28 Modules

The following sections explain these components and their configuration for the
different usage scenarios.

4.1: DIP Switches

The 4 DIP Switches on the EVB are used for the following purposes:

1. Use of Power-On Reset or Push-Button Reset

2. Select between SPI and UART modes

Power Switch

Switch SW4

Switch SW5
Header J6 (UART)

Header J7 (SPI)

Push Button (Reset)

3. Debug

DIP Switches 1 and 2 are used to configure the source of the Reset for the
module. Placing DIP Switch 1 towards the ‘ON’ label and DIP Switch 2 towards
the opposite side selects the Power-On Reset. Flipping the switches (Switch 2
towards ‘ON’ and Switch 1 in the opposite side) selects the Push-Button Reset.

DIP Switch 3 is used to select between the UART and SPI interfaces. Placin g this
switch towards the ‘ON’ label selects SPI and flipping it to the opposite side
selects UART.

NOTE: The firmware for UART and SPI interfaces (RS9110-N-11-2X
and RS9110-N-11-2X-01, respectively) are different and the user is
advised to contact Redpine Signals in order to switch between the two
interfaces.

DIP Switch 4 is used for debug purposes only and has to be placed on the side
opposite to the ‘ON’ label.

4.2: Header J4

The Header labeled J4 is used for debug purposes.

Redpine Signals, Inc. Proprietary and confidential Page 43

RRSS99111100--NN--1111--2222//2244//2266//2288 –– SSeellff--CCoonnttaaiinneedd WWLLAANN

MMoodduulleess wwiitthh NNeettwwoorrkkiinngg SSttaacckk

4.3: Header J7

The Header labeled J7 is used for the SPI interface. The pin configur ation of this
header is as follows:

Figure 40: Pin Configuration of Header J7

4.4: Header J6

The Header labeled J6 is used for interfacing the EVB over UART to a second PCB
which has the Host microcontroller mounted. This header bypasses the DB9
connector and the 3.3V-5V level shifter ICs and a simple ribbon-cable can be
used for this interface. This header can be enabled/disabled by flipping the
switches SW4 and SW5. The pin configuration of this header is as follows:

Figure

41: Pin Configuration of Header J6

4.5: Switches SW4 and SW5

The Switches SW4 and SW5 are used to select between the DB9 connector and
the Header J6 for the UART interface. In the images of the EVBs shown above,
the switches are placed (to the right on the RS9110-N-11-22/24 EVB and to the
left on the RS9110-N-11-26/28 EVB) to enable the DB9 connector. If they are
flipped, the Header J6 is enabled.

Redpine Signals, Inc. Proprietary and confidential Page 44