GS2011M Low Power Wi-Fi Module Hardware Guide Rev 5.0
GS2011M Low Power Wi-Fi Module Hardware Guide Rev 5.0
GS2011M Low Power Wi-Fi Module Hardware Guide Rev 5.0
NOTICE
While reasonable efforts have been made to assure the accuracy of this document, Telit assumes
no liability resulting from any inaccuracies or omissions in this document, or from use of the
information obtained herein. The information in this document has been carefully checked and is
believed to be reliable. However, no responsibility is assumed for inaccuracies or omissions. Telit
reserves the right to make changes to any products described herein and reserves the right to
revise this document and to make changes from time to time in content hereof with no obligation
to notify any person of revisions or changes. Telit does not assume any liability arising out of the
application or use of any product, software, or circuit described herein; neither does it convey
license under its patent rights or the rights of others.
It is possible that this publication may contain references to, or information about Telit products
(machines and programs), programming, or services that are not announced in your country.
Such references or information must not be construed to mean that Telit intends to announce
such Telit products, programming, or services in your country.
COPYRIGHTS
This instruction manual and the Telit products described in this instruction manual may be,
include or describe copyrighted Telit material, such as computer programs stored in
semiconductor memories or other media. Laws in the Italy and other countries preserve for Telit
and its licensors certain exclusive rights for copyrighted material, including the exclusive right to
copy, reproduce in any form, distribute and make derivative works of the copyrighted material.
Accordingly, any copyrighted material of Telit and its licensors contained herein or in the Telit
products described in this instruction manual may not be copied, reproduced, distributed, merged
or modified in any manner without the express written permission of Telit. Furthermore, the
purchase of Telit products shall not be deemed to grant either directly or by implication, estoppel,
or otherwise, any license under the copyrights, patents or patent applications of Telit, as arises by
operation of law in the sale of a product.
APPLICABILITY TABLE
PRODUCT
Software Release
5.5.0
Note: The features described in the present document are provided by the products equipped with
the software versions equal or higher than the versions shown in the table. See also the
Revision History chapter.
Table of Contents
This manual describes the GS2011M Low Power module hardware specification.
Refer to the following sections:
• Revision History, page 8
• Audience, page 8
• Standards, page 8
• Certifications, page 8
• Documentation Conventions, page 9
• Documentation, page 12
• Contact Information, Support, page 14
• Returning Products to GainSpan, page 15
• Accessing the GainSpan Portal, page 16
• Ordering Information, page 16
Revision History
This version of the GainSpan GS2011M Low Power Wi-Fi Data Sheet contains the
following new information listed in Table 1, page 8.
Table 1 Revision History
Version Date Remarks
Removed reference to external PA, LNA, and control of external RF Switch
(GS2011MIE only). See 2.2.1.2 802.11 PHY, page 26.
Added Errata notification to the Pin Signal and Pin MUX tables regarding
SPI0_OUT and SPI1_OUT signals. See Table 7, page 42 and Table 8,
1.0 June 2015 page 47.
Updated Power Consumption information in Table 15, page 55.
Updated 802.11 Radio Parameters Transmit/Receive Specifications for
1Mbps and 54Mbps in Table 16, page 56.
Updated 802.11 Radio Parameters Output power (average) and Receive
Sensitivity at antenna port in Table 16, page 56.
2.0 February 2016
Updated the Note under 5.1 GS2011Mxx Recommended PCB Footprint and
Dimensions
3.0 July 2016 Updated 802.11 Radio Parameters RF Frequency Range in Table 16, page 56
Corrected the System State - WLAN Continuous Transmit from 16dbm to
4.0 November 2017
15dbm see Table 15, page 55
Updated Output power (average) for GS2011MIE and GS2011MIZ in Table
5.0 January 2018
16, page 56
Audience
This manual is designed to help system designers build low power, cost effective, flexible
platforms to add Wi-Fi connectivity for embedded device applications using the GainSpan
GS2011M based module.
Standards
The standards that are supported by the GainSpan modules are IEEE 802.11 b/g/n.
Certifications
GainSpan GS2011M Low Power Wi-Fi Module has Certification Compliance for the
following:
Hereby, GainSpan Corporation declares that the radio equipment type GS2011MIZ &
GS2011MIE is in compliance with Radio Equipment Directive (RED) 2014/53/EU. The
Declaration of Conformity (DoC) for the same is available at URL:
https://www.telit.com/red/
Documentation Conventions
This manual uses the following text and syntax conventions:
– Special text fonts represent particular commands, keywords, variables, or window
sessions
– Color text indicates cross-reference hyper links to supplemental information
– Command notation indicates commands, subcommands, or command elements
Table 3, page 9, describes the text conventions used in this manual for software procedures
that are explained using the AT command line interface.
UPPERCASE Indicates user input. Enter a value according to the descriptions that
follow. Each uppercased token expands into one or more other token.
Variable parameter
Table 4, page 11, describes the symbol conventions used in this manual for notification and
important instructions.
Documentation
The GainSpan documentation suite listed in Table 5, page 12 includes the part number,
documentation name, and a description of the document. The documents are available from
the GainSpan Portal. Refer to , page 15 for details.
Table 5 Documentation List
Part Number Document Title Description
Provides an easy to follow guide on
GS2011M Evaluation Board Quick how to unpack and setup GainSpan
1VV0301415
Start Guide GS2000 based module kit for the
GS2011M module.
Provides users steps to program the
on-board Flash on the GainSpan
GS2000 based modules using DOS or
GS2K Module Programming User
1VV0301437 Graphical User Interface utility
Guide
provided by GainSpan. The user guide
uses the evaluation boards as a
reference example board.
Provides a complete listing of AT serial
commands, including configuration
GS2011M Serial-to-Wi-Fi Adapter
1VV0301463 examples for initiating, maintaining,
Command Reference Guide
and evaluating GainSpan Wi-Fi
GS2011M series modules.
Provides a complete listing of AT serial
commands, including configuration
GS2100M Serial-to-Wi-Fi Adapter
1VV0301463 examples for initiating, maintaining,
Command Reference Guide
and evaluating GainSpan Wi-Fi
GS2100M series modules.
Provides instructions on how to setup
and use the GS2000 based module
GS2K Module Evaluation Board
1VV0301435 evaluation board along with component
Hardware User Guide
description, jumper settings, board
specifications, and pinouts.
Provides information to help Wi-Fi
GS2011M Low Power Wi-Fi Module system designers to build systems using
1VV0301482
Hardware User Guide GainSpan GS2011M module and
develop wireless applications.
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can improve
the documentation. You can send your comments by logging into Telit Support Portal. If
you are using e-mail, be sure to include the following information with your comments:
– Document name
– URL or page number
– Hardware release version (if applicable)
– Software release version (if applicable)
NOTE: Do not return any components to GainSpan Corporation unless you have
first obtained an RMA number. GainSpan reserves the right to refuse shipments
that do not have an RMA. Refused shipments will be returned to the customer by
collect freight.
NOTE: You must first contact GainSpan to set up an account, and obtain a
customer user name and password before you can access the GainSpan Portal.
Ordering Information
To order GainSpan’s GS2011Mxx low power module contact a GainSpan Sales/Distributor
Representative. Table 6, page 16 lists the GainSpan device information.
NOTE: Modules ship with test code ONLY. Designers must first program the
modules with a released firmware version. Designers should bring out GPIO27
pin (option to pull this pin to VDDIO during reset or power-on) and UART0 or SPI0
pins to enable programming of firmware into the module. For details refer to the
Programming the GainSpan Modules document.
This chapter describes the GainSpan® GS2011M low power module hardware specification
overview.
• Product Overview, page 19
• GS2011M Module Product Features, page 19
• Wi-Fi Solution:
• Wi-Fi security (802.11i)
– WPA™ - Enterprise, Personal
– WPA2™ - Enterprise, Personal
– Vendor EAP Type(s):
– EAP-TTLS/MSCHAPv2, PEAPv0/EAP-MSCHAPv2,
PEAPv1/EAP-GTC, EAP-FAST, EAP-TLS
• Hardware-accelerated high-throughput AES and RC4 encryption/decryption
engines for WEP, WPA/WPA2 (AES-CCMP and TKIP).
• Additional dedicated encryption HW engine to support higher layer encryption
such as IPSEC (IPv4 and IPv6), SSL/TLS, HTTPs, PKI, digital certificates, RNG,
etc.
• Dual ARM Cortex M3 Processor Platform:
• 1st Cortex M3 processor (WLAN CPU) for WLAN software
– Implements 802.11b/g/n WLAN protocol services
– 320 KB dedicated SRAM
– 512 KB dedicated ROM
• 2nd Cortex M3 processor (APP CPU) for networking software
– Implements networking protocol stacks and user application software
– 384 KB dedicated SRAM
– 512 KB dedicated ROM
• 64KB shared dual ported SRAM for inter-processor communications
• 320KB assignable (under SW control) SRAM
• Support processor clock frequencies for both CPU of up to 120MHz
• Based on Advanced Microprocessor Bus Architecture (AMBA) system
– AMBA Multilayer High-Speed Bus (AHB)
– AMBA Peripheral Bus (APB)
• On-module controller
– Manages read/write/program/erase operations to the 4 MB flash memory
device on the module
– Supports higher performance QUAD SPI protocol operations
– Active power management
• Interfaces:
• SDIO:
– Compliant to SDIO v2.0 specification
– Interface clock frequency up to 40 MHz
This chapter describes the GainSpan® GS2011M Low Power module architecture.
• Architecture Description, page 23
• Wireless LAN and System Control Subsystem, page 25
Key Features
Key Features
2.2.1.3 RF/Analog
The RF/Analog is a single RF transceiver for IEEE 802.11b/g/n (WLAN). The RF Interface
block provides the access to the RF and analog control and status to the CPU. This block is
accessible only from the WLAN CPU. It implements registers to write static control words.
It provides read only register interface to read static status. It generates the dynamic control
signals required for TX and RX based on the PHY signals. The AGC look up table to map
the gain to RF gain control word is implemented in this block.
2.2.3.1 SRAM
The system memory is built with single port and dual port memories. Most of the memory
consists of single port memory. A 64KB dual port memory is used for exchange of data
between the two CPU domains. All the memories are connected to the system bus matrix
in each CPU subsystem. All masters can access any of the memory within the subsystem.
The APP subsystem has 384KB of dedicated SRAM for program and data use.
The WLAN subsystem has 320KB of dedicated SRAM for program and data use.
These memories are divided into banks of 64KB each. The bank structure allows different
masters to access different banks simultaneously through the bus matrix without incurring
any stall. Code from the external Flash is loaded into the SRAM for execution by each
CPU.
In addition, a static shared SRAM is provided. This consists of five 64KB memory blocks.
At any time, any of these memory blocks can be assigned to one of the CPU subsystem.
These should be set up by the APP CPU SW at initialization time. The assignment is not
intended to change during operation and there is no HW interlock to avoid switching in the
middle of a memory transaction. The assignment to the WLAN CPU should be done
starting from the highest block number going down to lowest block number. This result in
the shared memory appearing as a single bank for each CPU subsystem, independent of the
number of blocks assigned. The shared memory is mapped such that the SRAM space is
continuous from the dedicated SRAM to shared SRAM.
A 64KB dual port memory is used for exchange of data between the two CPU domains.
Each CPU subsystem can read or write to this memory using an independent memory port.
SW must manage the memory access to avoid simultaneous write to the same memory
location. The dual port memory appears as a single bank to each CPU subsystem.
2.2.3.2 ROM
ROM is provided in each CPU subsystem to provide the boot code and other functional
code that are not expected to change regularly. Each CPU has 512KB of ROM.
The GS2000 device includes a 64Kbit OTP ROM used for storing MAC ID and other
information such as security keys etc. The APP and WLAN subsystem each contain
32Kbits (4Kbytes) of OTP memory.
2.2.4 Clocks
The GS2011M includes four basic clock sources:
– Low power 32KHz clock (see 2.2.5 Real Time Clock (RTC) Overview, page 29)
– 40MHz Xtal Oscillator
– PLL to generate the internal 120MHz (CPU) and 80MHz (PHY) clocks from the
40MHz Xtal.
– High speed RC oscillator 80MHz
Intermediate modes of operation, in which high speed clocks are active but some modules
are inactive, are obtained by gating the clock signal to different subsystems. The clock
control blocks within the device are responsible for generation, selection and gating of the
clocked used in the module to reduce power consumption in various power states.
substituted for the RC oscillator under software control. In normal operation the RTC is
always powered up, even in the Power up state.
The dc_dc_cntl programmable counter is 48-bits and provides up to 272 years worth of
standby duration.
For the other RTC_IO pins, the programmable embedded counters (32-bit) are provided to
enable periodic wake-up of the remainder of the external system, and provide a 1.5 days
max period. The RTC_IO pins can be configured as inputs (ALARMS) or output (WAKE
UP) pins.
The RTC includes a Power-On Reset (POR) circuit, to eliminate the need for an external
component. The RTC contains low-leakage non-volatile (battery-powered) RAM, to enable
storage of data that needs to be preserved. It also includes a brown-out detector that can be
disabled by SW.
Total current consumption of the RTC is typically less than 5 μA with 1Kbyte of data
storage, using the 32.768 kHz oscillator.
2.2.5.4 DC_DC_CNTL
During RTC Power-on-Reset (e.g. when the battery is first connected), the dc_dc_cntl pin
is held low; it goes high to indicate completion of RTC power-on-reset. This pin can be
used as an enable into an external device such as voltage regulator. The dc_dc_cntl also is
held low when module is in standby and goes high to indicate wake up from standby.
2.2.6.5 GPIO
The GPIO block provides programmable inputs and outputs that can be controlled from the
CPU SW through an APB interface. Any number of inputs can be configured as an interrupt
source. The interrupts can be generated based on the level or the transition of a pin. At reset,
all GPIO lines defaults to inputs. Each pin can be configured as input or output from SW
control.
2.2.6.6 ADC
2.2.6.7 PWM
The PWM consists of three identical PWM function blocks. The PWM function blocks can
be used in two modes of operations:
• Independent PWM function blocks providing output signal with programmable
frequency and duty cycle
• Synchronized PWM function blocks with programmable phase delay between
each PWM output
The PWM has the following features:
• 32-bit AMBA APB interface to access control, and status information
• Three identical PWM function blocks
• Each PWM block can be enabled independently
• All three PWM blocks can be started synchronously or chained with
programmable delay
• Programmable 6-bit prescaler for the input clock (see 2.2.4 Clocks, page 28)
• Programmable frequency and duty cycle using 16 bit resolution in terms of clock
cycles for ON and OFF interval time
• Combined interrupt line with independent masking of interrupts
In standby state, the 32.768KHz oscillator keeps running and only the RTC RAM
retains the state (how many banks retain their state is SW configurable). SRAM, CPUs
and I/Os are all in OFF state, as there is no 1.8V and no VDDIO being supplied to the
GS2011M device.
This is the lowest-power-consumption state. In a typical application, the system returns
to the Standby state between periods of activity, to keep the average power very low
and enable years of operation using conventional batteries. During standby, the RTC
isolates itself from the rest of the chip, since the signals from the rest of the chip are
invalid. This prevents corruption of the RTC registers.
Exit from standby occurs when a pre-specified wakeup time occurs, or when one of the
RTC_IO’s configured as alarm inputs sees the programmed polarity of signal edge.
When one of the wakeup conditions occurs, the RTC asserts reset to the chip and sets
the DC_DC_CNTL pin high to enable power to the rest of the module. After power to
the rest of the module is assumed to be good, the isolation between the RTC and the
rest of the chip is released, and the EXT_RESETn pin is released. The system now
starts booting.
NOTE: During first battery plug, i.e., when power is applied the first time to the
RTC power rail (VRTC), the power detection circuit in the RTC also causes a
wakeup request.
System Configuration: When a power-up is requested, the system transitions from the
Standby state to the System Configuration state. In this state, the APP CPU is released
from reset by the RTC. The WLAN CPU remains in the reset state during System
Configuration. The APP CPU then executes the required system configurations,
releases the WLAN CPU from reset, and transitions to the Power-ON state.
The System Configuration state is also entered on transition from the Power-ON state
to the Standby state, to complete necessary preparations before shutting off the power
to the core system.
Power-ON: This is the active state where all system components can be running. The
Power-ON state has various sub-states, in which unused parts of the system can be in
sleep mode, reducing power consumption. Sleep states are implemented by gating the
clock signal off for a specific system component. Additionally, unneeded clock sources
can be turned off. For example, receiving data over a slave SPI interface could be done
with only the 80MHz RC oscillator active, and the 40MHz crystal and PLL turned off.
Sleep: In the Sleep state, the 40MHz crystal and the 80MHz RC oscillator remains
running, but it is gated off to one or both CPUs. Each CPU can independently control
its own entry into Sleep state. Any enabled interrupt will cause the interrupted CPU to
exit from Sleep state, and this will occur within a few clock cycles.
Deep Sleep: Deep sleep is entered only when both CPUs agree that the wakeup latency
is OK. In Deep Sleep mode, the 40MHz crystal oscillator and 80MHz RC oscillator are
turned off to save power, but all power supplies remain turned on. Thus all registers,
memory, and I/O pins retain their state. Any enabled interrupt will cause an exit from
Deep Sleep state.
NOTE: For the above power states, software controls which clocks stay turned
on in each of the three states.
The following are not system states, but are related design notes:
Power Control: The GS2011M was designed with the intent that power to the
non-RTC portions of the chip be controlled from the DC_DC_CNTL signal. In
applications where it is preferred that an external host control the power, this is OK if
ALL power, including VRTC power, is turned on and off by the external host. In this
case, all state is lost when power goes off, and the latencies from first battery plug
apply.
If these latencies are not acceptable, then the GS2011M MUST control power. The
external host would use an alarm to wake it up, and a serial command to put it into
standby. The DC_DC_CNTL pin would control the power supplies. It is NOT reliable
for the external host to directly control the power supplies if VRTC is to be left turned
on. This is because the RTC would not know when to isolate itself from the rest of the
chip, and might get corrupted during power up or power down.
EXT_RESET_n pin: If the external host is driving the EXT_RESET_n pin, it MUST
do so with an open drain driver. This is because this pin is driven low during power up
by the RTC. In addition, if an external host is connected to the EXT_RESET_n pin,
there must be an external 10K ohm pull-up resistor on the board, pulling up to VDDIO.
This is needed to overcome a possible pull-down in the host at first power application.
It is also recommended that the host not actively assert EXT_RESET_n until all the
startup latencies have expired.
Notes:
1. Always ON is obtained by tying EN_1V8 to 1 which is the enable for the 1.8V voltage
regulator.
2. With this connection method, standby current will not be optimized.
Notes:
1. This connection applies for designs (typically battery operated) using GS2011M module and
want to optimized standby (lowest current consumption) state of the module. In this
connection it is important to note the following:
2. Input voltage to VRTC must always be ON to keep the RTC powered so that the 32KHz
crystal is running.
3. VDDIO and VIN_3V3 power should be OFF during this state. Recommendation is to use
DC_DC_CNTL to also control the unit supplying the voltage to VDDIO and VIN_3V3
4. DC_DC_CNTL must be connected to EN_1V8 to so that the internal 1.8V regulator gets
turned OFF when system goes to standby state (i.e., DC_DC_CNTL is de-asserted).
This chapter describes the GainSpan® GS2011M Low Power module architecture.
• GS2011Mxx Device Pin-out, page 41
Notes:
1. Pins with drive strength 4, 12, and 16 have one pull resistor (either up or down, not both),
which is enabled at reset. RTC_IO pins have both pull_up and pull_down resisters. The
RTC_IO pull down resisters are enabled at reset for non DC_DC_CNTL pins.
2. Can be left as no connect.
3. This pin enables programming of the module. If UART1_RTS (GPIO27) is high during
reset or power on then the GS2011M will wait for Flash download via UART0 or SPI0
interface. Route this pin on the base board so it can be pulled up to VDDIO for programming
the module.
4. GPIO29 is the primary function; if using GPIO8/9 as I2C function, then this pin cannot be
used for I2C function.
5. If I2C interface is used, provide 2K Ohm pull-ups, to VIN_3V3, for I2C_CLK and
I2C_DATA.
6. EXT_RESET_n is an active low signal. It is an output during power up, indicating to the
system when GS2011 device is out of power-on-reset. After power-on-reset, this pin is an
input. It is not necessary to assert reset to the GS2011M after power on, since the GS2011
has a built-in power on reset. Also, the EXT_RESET_n signal does not clear the RTC, RTC
RAM, or the SRAM. If the external host is driving the EXT_RESET_n pin, it MUST do so
with an open drain driver. This is because this pin also must be able to be driven by the RTC.
In addition, if an external host is connected to the EXT_RESET_n pin, there must be an
external 10K Ohm pull-up resistor on the board, pulling up to VDDIO.
7. CTS and RTS signals indicate it is clear to send or ready to send when they are LOW. If
signals are high indicates device is not ready.
8. These pins have higher drive strength so they can drive LEDs directly.
9. This pin is generally reserved for GainSpan use, but if a design requires writing to OTP
during production, then design must take into account connection to this pin. Otherwise, it
should be left as a No Connect.
10. In the Serial-to-Wi-Fi firmware when using SPI interface this pin is the host wake-up
signal or the Ready to Send signal.
a. GPIO37 - when using SPI interface this pin is the host wake-up signal or the Ready to
Send signal.
Errata
E1. The SPI0_DOUT and SPI1_OUT signals do not disable their drive and become Hi-Z
when the associated chip select pin is high. This applies to all pin MUX locations for the
SPI_DOUT signals. If there are multiple write only devices on the same SPI bus, then this
is not an issue. This only becomes an issue when there are other read/write devices on the
same SPI bus. The workaround is to add an external buffer chip, such as 74LVC1G125
between the SPI_DOUT pin and the SPI bus, with the enable connected to the chip select
signal.
Note 1. The SPI0_DOUT and SPI1_OUT signals do not disable their drive and become Hi-Z
when the associated chip select pin is high. This applies to all pin MUX locations for the
SPI_DOUT signals. If there are multiple write only devices on the same SPI bus, then this is
not an issue. This only becomes an issue when there are other read/write devices on the same
SPI bus. The workaround is to add an external buffer chip, such as 74LVC1G125 between the
SPI_DOUT pin and the SPI bus, with the enable connected to the chip select signal.
Note:
1. In Run Mode, boot ROM leaves all GPIO pins as input with pull resistor enabled until flash
code sets them otherwise. In Program Mode, only the pins required for the Program Mode
specified interfaces are set to non-GPIO mode.
Note:
1. Reference domain voltage is the Voltage Domain. Refer to the section on GS2011Mxx
Module Pins Description. For limitations on state voltage ranges, refer to the section
GS2011Mxx Module Pins Description.
Notes:
1. Reference domain voltage is the Voltage Domain. Refer to section GS2011Mxx Module
Pins Description.
2. The VPP pin should be left floating when not doing OTP programming operations.
4.4.1 I/O Digital Specifications (Tri-State) Pin Types 4mA, 12mA, and 16mA
The specifications for these I/O’s are given for voltage ranges: 2.7V to 3.6V.
*RTC I/O’s are software selectable as 1mA (default) or 4mA drive strength.
Notes:
1. Depends on firmware version.
2. One Sigma (+140μA).
3. This is average current draw measurements.
NOTE: TX output power and RX sensitivity are firmware dependent. All the
values provided for these parameters are measured at the antenna port based on
5.2.1 GA firmware.
Notes:
1. No missing codes.
2. This is the gain of the ADC core measured in External reference mode.
This chapter describes the GainSpan® GS2011M package and layout guidelines.
• GS2011Mxx Recommended PCB Footprint and Dimensions, page 61
Notes:
1. All Dimensions are in inches. Tolerances shall be + 0.010 for .xxx and + 0.02 for .xx inches.
2. For Boards using PCB or Ceramic Antenna, we recommend:
– Have Only Air on BOTH sides of antenna.
– Hang Antenna over edge of base board (best)
– Or Cut notch in base board under antenna area
– No metal or FR4 encircling antenna area
– Antenna at edge of base board, not interior of base board
– Nothing conductive near antenna (e.g. battery, display, wire)
3. The 3 RF shield mounting holes and 2 test fixture alignment holes (circled in red in Figure
7, page 61 and Figure 8, page 62) have exposed metal. These areas must not have metal
on the customer board.
4. For best RF performance, we recommend:
– Using power(PWR) or the GND planes from module back to power supply.
– Isolating PWR/GND from high frequency or high current components. For example, a
notch in GND plane to isolate from host uC
– Using at least 3 vias when either power or GND changes layers. This applies particularly
at the module GND pins and at the VIN_3V3 pins.
– Providing a 10 uF capacitor at the VIN_3V3 pin and using 3 vias both sides of the
capacitor.
Notes:
1. Perform adequate test in advance as the reflow temperature profile will vary according to the
conditions of the parts and boards, and the specifications of the reflow furnace.
2. Max number of reflow supported are two.
3. Temperature uniformity inside the IR reflow oven must be tightly controlled and multiple
thermocouples should be used. An example of possible thermocouple locations is given in
Figure 10, page 66. The locations should also include multiple points INSIDE the module
RF shield (e.g., TC1, TC5, and TC7 in Figure 10, page 66). The temperature profile of
ALL thermocouples must meet the requirements of Table 18, page 64.
4. Pay close attention to “Melting Time over 220oC”. Sufficient time is necessary to
completely melt all solder.
5. Be careful about rapid temperature rise in preheat zone as it may cause excessive slumping
of the solder paste.
6. If the preheat is insufficient, rather large solder balls tend to be generated. Conversely, if
performed excessively, fine balls and large balls will generate in clusters at a time.
7. If the temperature is too low, non-melting tends to be caused in the area with large heat
capacity after reflow.
8. Be careful about sudden rise in temperature as it may worsen the slump of solder paste.
9. Be careful about slow cooling as it may cause the positional shift of parts and decline in
joining at times.
10. A no clean flux should be used during SMT process.
Note: The modules are shipped in sealed trays with the following conditions (see Figure 11,
page 67).