VIAVI SPB209A WiFi Bluetooth NFC Module

Overview

SPB209A is a complete WLAN/BT/NFC module with EMC shield, and dual-band antenna (WiFi and BT), prepared for application-specific NFC antenna and ready for quick validation in a hosted environment. SPB209A-RNM provides an ultra-low power, high performance and feature-rich client solution. It provides up to 433 Mbit/s data rate when operating in the OFDM mode and up to 11 Mbit/s data rate when operating in the DSSS/CCK mode.
SPB209A integrates RF, baseband/MAC, Bluetooth Package Engine, NFC, memory, RF filters, oscillator, antenna or SMA connector and EMC shield into a highly integrated and optimized module solution with high quality and reliability to a complete standalone solution with no need for external components.
This highly integrated solution is optimized for customer applications running on a Linux host platform. The host interface supports SDIO 3.0, High Speed UART and I2C. Internal RAM comprises both code and data memory eliminating the need for external RAM, Flash or ROM memory interfaces. MAC address, trimming values etc. are stored in the on-board memory.

Key Features

• Support for 802.11a/b/g/n/ac
• Data Rates: 20MHz CH 1-86Mbps; 40MHz CH 13-200Mbps; 80MHz CH 29-433Mbps
• Modulation: BPSK, CCK, QPSK, 16QAM, 64QAM 256 QAM for WLAN and GFSK/π/4DQPSK/8DPSK/LE
• Open WEP, WPA/WPA2 encryption
• No external components except for the antenna options
• Low power consumption due to efficient PA design and power off mode
• An on-board 32 kHz oscillator maintains real time in power save mode, allows the high-frequency clock to be turned off.
• Supporting STA and AP operation mode
• Supports BT-WLAN coexistence and ISM-LTE coexistence
• Extensive DMA hardware support for data flow to reduce CPU load.
• Advanced power management for optimum power consumption at varying load.
• External interfaces 4 bit SDIO 3.0 for WLAN and UART/PCM for BT interface
• On-board High Frequency High Precision Oscillator 37.4 MHz
• Small footprint 14 x 14 mm (196 mm2) 41-pin
• RoHS Compliant

APPLICATION INFORMATION

Power Supply
SPB209A should be powered by a single supply voltage on VDD of 3.3V. It generates all required digital and analog supply voltages with the built in DC-DC converter.

1. Main supply
   The main power is connected to VDD. The ripple on VDD should be less than 10mV p-p.
2. Clock Signals
   The SPB209A requires no external clock signals. It has an internal high-frequency oscillator with a high precision 37.4 MHz crystal and a low power oscillator to generate the required clock signals.
3. Standby
   The Power Down pin (PDn) shall be set high during normal operation of either connectivity type. Pulling PDn pin low, sets SPB209A in Standby mode. This turns OFF most parts of the circuit and minimizes the current consumption. All I/O interface pins are set to predefined states (high, low or high-z) when in Standby mode.
   To end Standby mode set PDn high and reload firmware.
4. Power save
   Power save is an energy-saving mode where SPB209A is only listening at regular intervals for the beacons transmitted from an access point and is set in sleep mode in between. During this sleep mode, firmware is kept in RAM but all not needed functions are turned off. Since the receive time is very short compared to the listening interval the average current consumption is reduced significantly. The timing of the listening interval is based on the low power oscillator clock generated internally.
5. Interfaces
   The SPB209A is equipped with a number of interfaces that can be set up in various ways by the value on GPIO2 and GPIO3 during boot, see section 2.5.1.
6. Host Interface SDIO and UART
   The SDIO interface is in SDIO 4-bit mode, supporting up to 208MHz clock speed.
   The High-Speed UART interface default supporting Baud Rates from 1200 up to 2764800 bps, 8 bits, no parity, 1 stop bit.
   Booth GPIO2 and GPIO3 have internal pull-up and only needs to be connected via a 100kOhm resistor to GND to be set low (0). For high level (1) the pin can be left unconnected. Table 2-1 shows the different options. The default is to leave GPIO2 and GPIO3 unconnected (11) and SDIO as host interface for all services.

Table 2-1: Host Interface Selection

GPIO2	GPIO3	WLAN Host Interface	BT/BLE/NFC Host Interface	FW Download interface	FW Download mode
0	0	SDIO	UART	SDIO	Serial
0	1	SDIO	SDIO	SDIO	Parallel
1	0	SDIO	UART	SDIO+UART	Parallel
1	1	SDIO	SDIO	SDIO	Serial

PCM Interface

PCM
PCM interface is used for BT audio and can operate in master or slave mode. The interface supports the following:

• 8, 13, 14, 15 or 16-bit samples
• 4 slots per frame with up to 16-bits per slot
• Long or short frame sync

Host Wake up
Wake up command via the SDIO interface. This is the normal wake up and is implemented in the FW.
There is options to use defined GPIO:s for Host Wake-up or opposite for SPB209A Wake-Up involving both WLAN, BT and NFC. Below table outline the options.

GPIO No.	Function
GPIO1	WLAN to Host Wake-up
GPIO13	BT/NFC to Host Wake-up
GPIO14	Host to WLAN Wake-up
GPIO15	Host to BT/NFC Wake-up

NFC Wake up
The NFC support contactless wake up functionality giving a trigger on a GPIO pin depending on the activities on the RF interface, when an antenna is connected to the NFC_ANT P and _N pins.

NFC Interface
The NFC Interface provides RFID and NFC functionality.

Supported features:

• Protocol support fir ISO 14443A/B, ISO 15693, NFCIP-2, NFC-Forum, EMV contactless targets with a data rate up to 848 Kbps.
• Reader/Writer, Card Emulation and Peer-to-Peer (P2P) modes
• Low Power and sleep modes
• Programmable Carrier detection level for Card Emulation mode
• Programmable field detection level for RF anti-collision when operating as Reader or Active Target.

The NFC chip can also be accessed via the I2C interface pin SDA and SCL provided that the SPB209A device is powered. Support standard 100kHz and Fast 400kHz mode.

RF interface
The SPB209A EVK is prepared with a chip dual band antenna optimal for quick evaluation of the SPB209A RF module.
Designing custom application board with the SPB209A RF module the following RF parametrical requirements shall be considered:

• The RF output pin impedance is 50 ohm and shall be connected to an antenna with VSWR better than 2:1.
• The RF antenna gain must be maximum 1.8 dBi for the 2.4 GHz band and equal or less than 4.9 dBi for the 5GHz band.

A custom NFC antenna will need to be selected with a maximum size of 45 x 45 mm. NFC antenna is soldered down with two pin interface to the side of the SPB209A-RNM.
For further information, please refer to the document “Hardware Design Guide SPB209A Application Note”.

Operational Mode

General
The SPB209A can be operated as STA or AP using a Linux Host platform. The STA operation uses the Linux WPA supplicant and the AP operation us Linux HostAPD. RF testing and FCC/ETSI certification shall use equivalent software tools provided by Viavi Solutions up on request.

STA operation using WPA Supplicant
The wpa_supplicant is the IEEE 802.1X/WPA component used in the client stations. The WPA supplicant can be configured to control the roaming and IEEE 802.11 authentication/association of the SPB209A device.
The configuration is usually performed in a configuration file, e.g. /etc/wpa_supplicant.conf. It is also possible to directly issue commands to the WPA Supplicant, using a dedicated shell command, wpa_cli. The usage of wpa_cli is out of the scope of this document, but is described in detail in the WPA supplicant documentation http://hostap.epitest.fi/wpa_supplicant/.
Below list show supported WPA Supplicant network options

• Key management (key_mgmt): WPA-PSK, NONE
• Group key encryption (group): CCMP, TKIP
• Pairwise key encryption (pairwise): CCMP, TKIP
• Protocol (proto): WPA, WPA2

Below list show examples of instructions on how to perform the following operations using WPA Supplicant

Connect to an unencrypted network

To simply instruct the WPA Supplicant to connect to any unencrypted network with ssid viavisolutions, the following configuration file should be enough:

• ctrl_interface=/var/run/wpa_supplicant
• network={ssid=”viavisolutions” key_mgmt=NONE}
• The path to the configuration file and the interface name (owl0) should then be passed as parameters when starting the WPA Supplicant:
• $ wpa_supplicant -Dwext -iowl0 -c /etc/wpa_supplicant.conf -B
• The paramater -Dwext informs the WPA Supplicant that the standard Wireless Extensions interface should be used to control the network interface. For detailed information on how to configure and run the WPA supplicant, see the WPA supplicant
• documentationhttp://hostap.epitest.fi/wpa_supplicant/.
• The WPA Supplicant will now periodically scan for networks until one that matches the configuration is found. Once found, a connection will be established. The WPA Supplicant will also handle reconnect if the connection is lost. Therefore, opposed to Wirieless Tools, when using the
• WPA Supplicant, it is not necessary to perform manual scanning and network selection.
• Note that the WPA Supplicant configuration can hold several networks and the WPA Supplicant will choose and roam amongst them. However, most importantly, the WPA supplicant implements the key negotiation with a WPA Authenticators.
• 2.8.2.2 Connect to a WPA protected network that uses TKIP encryption
• To connect to a network using WPA key management and TKIP encryption, the following network configuration can be specified in the configuration file:
• ctrl_interface=/var/run/wpa_supplicant
• network={ssid=”viavisolutions” key_mgmt=WPA-PSK group=TKIP pairwise=TKIP proto=WPA
• psk=”viavisolutionskey”}
• The key configured on the access point should be “viavisolutionskey”.
• To force the WPA Supplicant to re-read its configuration file wpa_cli can be used
• $ wpa_cli reconfigure

One should remember that all wireless operations performed by both the WPA supplicant and Wireless Tools are done through the same Wireless Extensions API. This means that it will still be possible to e.g. check the connection status with iwconfig:
$ iwconfig

owl0

• IEEE 802.11bg ESSID:”angr”
• Mode:Managed Frequency:2.422 GHz Access Point:68:7F:74:10:5B:4C Bit Rate=54 Mb/s
• Encryption key:472A-7E38-C465-D4EB-6DA7-BAE6-4700-0960-EDB1-40DE- 18CC-5A02-4AE1-EA96-F3EE-142A Security mode:open
• Power Management timeout:10
• Link Quality=24/30 Signal level=-20 dBm Noise level=-44 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
• Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Once connected, it is possible to obtain an ip address and perform the ping test:

• $ udhcpc -i owl0 Sending
• discover…
• Sending select for 192.168.2.102…
• Lease of 192.168.2.102 obtained, lease time 172800 adding dns 192.168.2.1
• $ ping -c 3 192.168.2.1

Connect to a WPA2-enabled network that uses CCMP encryption
To connect to a network using the WPA2 protocol and CCMP encryption, the following network configuration can be specified in the configuration file:
ctrl_interface=/var/run/wpa_supplicant
network={

ssid=”viavisolutions” key_mgmt=WPA-PSK group=CCMP pairwise=CCMP proto=WPA2 psk=”viavisolutionskey”}

Connect to a network that uses any WPA/WPA2 protocol and TKIP/CCMP encryption 

Note that several encryption parameters can be specified on a single line, allowing connections to a specific ssid using a range of encryption methods. The configuration file below should allow connections to the hdwireless access point regardless of whether the WPA or WPA2 protocol is used or whether CCMP or TKIP is used for pairwise and group key encryption. The actual encryption method used will be the most secure one that is supported by the access point.
ctrl_interface=/var/run/wpa_supplicant
network={ssid=”viavisolutions” key_mgmt=WPA-PSK group=TKIP CCMP pairwise=TKIP CCMP
proto=WPA WPA2 psk=”viavisolutionskey”}

Connect to a network with hidden SSID
To allow the wpa_supplicant to connect to hidden networks, the scan_ssid parameter must be added to the network configuration.
ctrl_interface=/var/run/wpa_supplicant
network={ssid=”viavisolutions” scan_ssid=1 key_mgmt=WPA-PSK group=TKIP CCMP
pairwise=TKIP CCMP proto=WPA WPA2 psk=”hdwirelesskey”}

List of supported WPA Supplicant network options

• Key management (key_mgmt): WPA-PSK, NONE
• Group key encryption (group): CCMP, TKIP Pairwise
• key encryption (pairwise): CCMP, TKIP Protocol (proto):
• WPA, WPA2

 AP operation using HostAPD

• Currently there is only hw support for the Linux driver with SDIO interface for SPB209A.
  Linux kernel version 4.0 or higher is required supporting DFS operation in 5GHz band required for AP mode operation.
• The Linux driver consist of four kernel objects: mwifiex.ko, mwifiex_sdio.ko, btmrvl.ko and btmrvl_sdio.ko.
• mwifiex.ko and mwifiex_sdio.ko handles the wifi protocols, while btmrvl.ko and btmrvl_sdio.ko handles Bluetooth, BLE and NFC.
• Along with the driver goes a fw binary that is downloaded to the chip by the driver. It must be named sd8887_uapsta.bin and located at /lib/firmware/mrvl/
• HOWTO run Linux softAP with hostapd

1. Make sure the network manager is disabled with regards to wifi:
   
2. Make sure the radio interface is unblocked:
   rfkill unblock all
3. Download the attachment:hostapd.conf file to the local disk.
4. Install Linux Wifi host AP package:
   sudo apt-get install hostapd
5. Plugin the sdio module.
   Make sure mwifiex driver was successfully started by typing:
   iwconfig mlan0
   This command should display information about the mlan0 interface
6. mwifiex driver does not support ap mode on native interface, so an additional ap- dedicated interface must be created. In order to do so we need to find out the phy<n> enum for the mlan0 interface by typing:
   iw list | grep Wiphy
   Normally phy0 corresponds to builtin wlan0, and the next higher enum will correspond to mlan0
7. Now create the ap specific interface (uap0) by typing
   sudo iw phy phy<n> interface add uap0 type ap
   Where <n> is the enum found out from iw list command
8. Now configure the AP by editing the hostapd.conf file.
   Example: For 11n, 5GHz band, channel 36, DFS enabled: Search for and edit the following parameters in hostapd.conf file:
   
   
9. Start the AP by typing:
   sudo hostapd <hostapd config file name>
   AP should now be up and running
10.  To run traffic, assign a fixed ip address to the interface:
    sudo ifconfig uapC) <dersired *e.g. 192.168. 10.1
11. Associate a station and assign a static ip at the same subnet
12. To remove the uap0 interface, kill the hostapd process and run:
    sudo iw dev uapC) del

Regulatory

Country	Approval authority	Regulatory	Frequency band
USA	FCC	FCC ID: WUW-SPB209A	2.412 GHz -2.462 GHz 5.250 GHz – 5.725 GHz
Canada	IC	IC: 9613A-SPB209A	2.412 GHz -2.462 GHz 5.250 GHz – 5.725 GHz

Table 3-1: Regulatory standards

FCC (United States of America)
This equipment complies with Part 15 of the FCC rules and regulations.
To fulfill FCC Certification requirements, an OEM manufacturer must comply with the following regulations:

1. The modular transmitter must be labeled with its own FCC ID number, and, if the FCC ID is not visible when the module is installed inside another device, then the outside of the device into which the module is installed must also display a label referring to the enclosed module. This exterior label can use wording such as Contains FCC ID: WUW-SPB209A.
2. Only antennas approved may be used with the SPB209A module. The SPB209A module may be integrated with custom design antennas which OEM installer must authorize following the FCC 15.21 requirements.

The internal/external antenna(s) used for this mobile transmitter must provide a separation distance of at least 20 cm from all persons and must not be co-located or operating in conjunction with any other antenna or transmitter.
This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

• Reorient or relocate the receiving antenna.
• Increase the separation between the equipment and receiver.
• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
• Consult the dealer or an experienced radio/TV technician for help.

Changes or modifications made to the device not expressly approved by Viavi Solutions could void the user’s authority to operate the equipment.
This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions:

1. This device may not cause harmful interference, and
2.  this device must accept any interference received, including interference that may cause undesired operation.

ISED (Canada)
The device complies with Industry Canada’s licence-exempt RSSs. Operation is subject to the following two conditions:

The radio elements shall have the radio frequency circuitry shielded. Physical/discrete and tuning capacitors may be located external to the shield, but shall be on the module assembly.
If the module has modulation/data input(s), they shall be buffered in order to ensure that the module will comply with the requirements set out in the applicable Radio Standards Specification (ARSS) under conditions of excessive data rates or over-modulation.
The module shall have its own power supply regulation on the module itself. This is to ensure that the module will comply with the requirements set out in the applicable standard regardless of the design of the power supply circuitry in the host product that houses the module.
The module shall comply with the provisions for external power amplifiers and antennas detailed in the applicable RSS. The equipment certification application shall contain:

1. detailed description of the configuration of highest antenna gain for each type of transmitteing antenna for license-exempt module;
2. the maximum transmitting antenna gain for licence modules; and ii. a detailed description of the configuration of lowest anenna gain for each type of receiving antenna for Dynamic Frequency Slection (DFS) modules with removable antenna(s).

The module shall be tested for compliance with the applicable standard ina stand-alone configuration (i.e. the module shall not be instide another product during testing).
The module complies or will comply with the applicable RSS-102 exposure requirements in its intended configuration/integration in a host.

Documents / Resources

VIAVI SPB209A WiFi Bluetooth NFC Module [pdf] User Manual SPB209A, SPB209A WiFi Bluetooth NFC Module, WiFi Bluetooth NFC Module, Bluetooth NFC Module, NFC Module

References

• User Manual