u blox TOBYL280 GSM/UMTS/LTE Data Module User Manual TOBY L2 series

u-blox AG GSM/UMTS/LTE Data Module TOBY L2 series

System Integrators Manual

TOBY-L2 and MPCI-L2 series LTE/DC-HSPA+/EGPRS modules System Integration Manual Abstract This document describes the features and the system integration of TOBY-L2 and MPCI-L2 series multi-mode cellular modules. These modules are a complete and cost efficient LTE/3G/2G solution offering up to 150 Mb/s download and 50 Mb/s upload data rates, covering up to six LTE bands, up to five WCDMA/DC-HSPA+ bands and four GSM/EGPRS bands in the compact TOBY LGA form factor of TOBY-L2 modules or in the industry standard PCI Express Mini Card form factor of MPCI-L2 modules. TOBY-L2 series www.u-blox.com UBX-13004618 - R08 MPCI-L2 series

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Page 2 of 158 Document Information Title TOBY-L2 and MPCI-L2 series Subtitle LTE/DC-HSPA+/EGPRS modules Document type System Integration Manual Document number UBX-13004618 Revision and date R08 29-Jun-2015 Document status Early Production Information Document status explanation Objective Specification Document contains target values. Revised and supplementary data will be published later. Advance Information Document contains data based on early testing. Revised and supplementary data will be published later. Early Production Information Document contains data from product verification. Revised and supplementary data may be published later. Production Information Document contains the final product specification. This document applies to the following products: Name Type number Modem version Application version PCN / IN TOBY-L200 TOBY-L200-00S-00 09.71 A01.15 UBX-14044437 TOBY-L200-50S-00 09.71 A01.57 UBX-15004131 TOBY-L201 TOBY-L201-01S-00 09.87 A01.01 UBX-15016217 TOBY-L210 TOBY-L210-00S-00 09.71 A01.15 UBX-14044437 TOBY-L210-50S-00 09.71 A01.57 UBX-15004131 TOBY-L280 TOBY-L280-00S-00 09.90 A01.02 UBX-15016802 MPCI-L200 MPCI-L200-00S-00 09.71 A01.15 UBX-14044437 MPCI-L210 MPCI-L210-00S-00 09.71 A01.15 UBX-14044437 u-blox reserves all rights to this document and the information contained herein. Products, names, logos and designs described herein may in whole or in part be subject to intellectual property rights. Reproduction, use, modification or disclosure to third parties of this document or any part thereof without the express permission of u-blox is strictly prohibited. The information contained herein is provided “as is” and u-blox assumes no liability for the use of the information. No warranty, either express or implied, is given, including but not limited, with respect to the accuracy, correctness, reliability and fitness for a particular purpose of the information. This document may be revised by u-blox at any time. For most recent documents, please visit www.u-blox.com. Copyright © 2015, u-blox AG u-blox® is a registered trademark of u-blox Holding AG in the EU and other countries. PCI, PCI Express, PCIe, and PCI-SIG are trademarks or registered trademarks of PCI-SIG. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. ARM® is a registered trademark of ARM Limited in the EU and other countries. All other registered trademarks or trademarks mentioned in this document are property of their respective owners.

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information Preface Page 3 of 158 Preface u-blox Technical Documentation As part of our commitment to customer support, u-blox maintains an extensive volume of technical documentation for our products. In addition to our product-specific technical data sheets, the following manuals are available to assist u-blox customers in product design and development.  AT Commands Manual: This document provides the description of the AT commands supported by the u-blox cellular modules.  System Integration Manual: This document provides the description of u-blox cellular modules’ system from the hardware and the software point of view, it provides hardware design guidelines for the optimal integration of the cellular modules in the application device and it provides information on how to set up production and final product tests on application devices integrating the cellular modules.  Application Note: These documents provide guidelines and information on specific hardware and/or software topics on u-blox cellular modules. See Related documents for a list of Application Notes related to your Cellular Module. How to use this Manual The TOBY-L2 and MPCI-L2 series System Integration Manual provides the necessary information to successfully design and configure the u-blox cellular modules. This manual has a modular structure. It is not necessary to read it from the beginning to the end. The following symbols are used to highlight important information within the manual: An index finger points out key information pertaining to module integration and performance. A warning symbol indicates actions that could negatively impact or damage the module. Questions If you have any questions about u-blox Cellular Integration:  Read this manual carefully.  Contact our information service on the homepage http://www.u-blox.com/ Technical Support Worldwide Web Our website (http://www.u-blox.com/) is a rich pool of information. Product information, technical documents can be accessed 24h a day. By E-mail Contact the closest Technical Support office by email. Use our service pool email addresses rather than any personal email address of our staff. This makes sure that your request is processed as soon as possible. You will find the contact details at the end of the document. Helpful Information when Contacting Technical Support When contacting Technical Support, have the following information ready:  Module type (TOBY-L200) and firmware version  Module configuration  Clear description of your question or the problem  A short description of the application  Your complete contact details

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information Contents Page 4 of 158 Contents Preface ................................................................................................................................ 3 Contents .............................................................................................................................. 4 1 System description ....................................................................................................... 8 1.1 Overview .............................................................................................................................................. 8 1.2 Architecture ........................................................................................................................................ 10 1.2.1 Internal blocks ............................................................................................................................. 11 1.3 Pin-out ............................................................................................................................................... 12 1.3.1 TOBY-L2 series pin assignment .................................................................................................... 12 1.3.2 MPCI-L2 series pin assignment .................................................................................................... 17 1.4 Operating modes ................................................................................................................................ 19 1.5 Supply interfaces ................................................................................................................................ 21 1.5.1 Module supply input (VCC or 3.3Vaux) ....................................................................................... 21 1.5.2 RTC supply input/output (V_BCKP) .............................................................................................. 28 1.5.3 Generic digital interfaces supply output (V_INT) ........................................................................... 29 1.6 System function interfaces .................................................................................................................. 30 1.6.1 Module power-on ....................................................................................................................... 30 1.6.2 Module power-off ....................................................................................................................... 32 1.6.3 Module reset ............................................................................................................................... 34 1.6.4 Module configuration selection by host processor ....................................................................... 34 1.7 Antenna interface ............................................................................................................................... 35 1.7.1 Antenna RF interfaces (ANT1 / ANT2) .......................................................................................... 35 1.7.2 Antenna detection interface (ANT_DET) ...................................................................................... 38 1.8 SIM interface ...................................................................................................................................... 38 1.8.1 SIM interface ............................................................................................................................... 38 1.8.2 SIM detection interface ............................................................................................................... 38 1.9 Data communication interfaces .......................................................................................................... 39 1.9.1 Universal Serial Bus (USB) ............................................................................................................ 39 1.9.2 Asynchronous serial interface (UART)........................................................................................... 43 1.9.3 DDC (I2C) interface ...................................................................................................................... 54 1.9.4 Secure Digital Input Output interface (SDIO) ................................................................................ 55 1.10 Audio .............................................................................................................................................. 55 1.10.1 Digital audio over I2S interface ..................................................................................................... 55 1.11 General Purpose Input/Output ........................................................................................................ 56 1.12 Mini PCIe specific signals (W_DISABLE#, LED_WWAN#) .................................................................. 57 1.13 Reserved pins (RSVD) ...................................................................................................................... 57 1.14 Not connected pins (NC) ................................................................................................................. 57 1.15 System features............................................................................................................................... 58 1.15.1 Network indication ...................................................................................................................... 58 1.15.2 Antenna supervisor ..................................................................................................................... 58

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information Contents Page 6 of 158 2.12 TOBY-L2 series module footprint and paste mask ......................................................................... 123 2.13 MPCI-L2 series module installation ................................................................................................ 124 2.14 Thermal guidelines ........................................................................................................................ 126 2.15 ESD guidelines .............................................................................................................................. 127 2.15.1 ESD immunity test overview ...................................................................................................... 127 2.15.2 ESD immunity test of TOBY-L2 and MPCI-L2 series reference designs ........................................ 128 2.15.3 ESD application circuits .............................................................................................................. 128 2.16 Schematic for TOBY-L2 and MPCI-L2 series module integration .................................................... 130 2.16.1 Schematic for TOBY-L200-00S / TOBY-L210-00S ....................................................................... 130 2.16.2 Schematic for TOBY-L201-01S / TOBY-L280-00S ....................................................................... 131 2.16.3 Schematic for TOBY-L200-50S / TOBY-L210-50S ....................................................................... 132 2.16.4 Schematic for MPCI-L2 series ..................................................................................................... 133 2.17 Design-in checklist ........................................................................................................................ 134 2.17.1 Schematic checklist ................................................................................................................... 134 2.17.2 Layout checklist ......................................................................................................................... 135 2.17.3 Antenna checklist ...................................................................................................................... 135 3 Handling and soldering ........................................................................................... 136 3.1 Packaging, shipping, storage and moisture preconditioning ............................................................. 136 3.2 Handling ........................................................................................................................................... 136 3.3 Soldering .......................................................................................................................................... 137 3.3.1 Soldering paste.......................................................................................................................... 137 3.3.2 Reflow soldering ....................................................................................................................... 137 3.3.3 Optical inspection ...................................................................................................................... 138 3.3.4 Cleaning .................................................................................................................................... 138 3.3.5 Repeated reflow soldering ......................................................................................................... 139 3.3.6 Wave soldering.......................................................................................................................... 139 3.3.7 Hand soldering .......................................................................................................................... 139 3.3.8 Rework ...................................................................................................................................... 139 3.3.9 Conformal coating .................................................................................................................... 139 3.3.10 Casting ...................................................................................................................................... 139 3.3.11 Grounding metal covers ............................................................................................................ 139 3.3.12 Use of ultrasonic processes ........................................................................................................ 139 4 Approvals .................................................................................................................. 140 4.1 Product certification approval overview ............................................................................................. 140 4.2 Federal Communications Commission notice .................................................................................... 141 4.2.1 Safety warnings review the structure ......................................................................................... 141 4.2.2 Declaration of Conformity ......................................................................................................... 141 4.2.3 Modifications ............................................................................................................................ 142 4.3 Industry Canada notice ..................................................................................................................... 142 4.3.1 Declaration of Conformity ......................................................................................................... 143 4.3.2 Modifications ............................................................................................................................ 143 4.4 Anatel certification ........................................................................................................................... 144 4.5 R&TTED and European Conformance CE mark ................................................................................. 145

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information Contents Page 7 of 158 5 Product testing ......................................................................................................... 146 5.1 u-blox in-series production test ......................................................................................................... 146 5.2 Test parameters for OEM manufacturer ............................................................................................ 147 5.2.1 “Go/No go” tests for integrated devices .................................................................................... 147 5.2.2 RF functional tests ..................................................................................................................... 147 Appendix ........................................................................................................................ 149 A Glossary .................................................................................................................... 149 B Migration between TOBY-L1 and TOBY-L2 ............................................................ 151 B.1 Overview .......................................................................................................................................... 151 B.2 Pin-out comparison between TOBY-L1 and TOBY-L2 ........................................................................ 153 B.3 Schematic for TOBY-L1 and TOBY-L2 integration .............................................................................. 155 Related documents......................................................................................................... 156 Revision history .............................................................................................................. 157 Contact ............................................................................................................................ 158

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 8 of 158 1 System description 1.1 Overview TOBY-L2 and MPCI-L2 series comprises LTE/3G/2G multi-mode modules supporting up to six LTE bands, up to five UMTS/DC-HSPA+ bands and up to four GSM/(E)GPRS bands for voice and/or data transmission as following:  TOBY-L200, TOBY-L201 and MPCI-L200 are designed primarily for operation in America  TOBY-L210 and MPCI-L210 are designed primarily for operation in Europe, Asia and other countries  TOBY-L280 is mainly designed for operation in Asia and Oceania TOBY-L2 and MPCI-L2 series are designed in two different form-factors suitable for applications as following:  TOBY-L2 modules are designed in the small TOBY 152-pin Land Grid Array form-factor (35.6 x 24.8 mm), easy to integrate in compact designs and form-factor compatible with the u-blox cellular module families: this allows customers to take the maximum advantage of their hardware and software investments, and provides very short time-to-market.  MPCI-L2 modules are designed in the industry standard PCI Express Full-Mini Card form-factor (51 x 30 mm) easy to integrate into industrial and consumer applications and also ideal for manufacturing of small series. With LTE Category 4 data rates at up to 150 Mb/s (down-link) and 50 Mb/s (up-link), the TOBY-L2 and MPCI-L2 series modules are ideal for applications requiring the highest data-rates and high-speed internet access. Table 1 summarizes the TOBY-L2 and MPCI-L2 series main features and interfaces. Module LTE UMTS GSM Positioning Interfaces Audio Features Grade LTE FDD category Bands HSDPA category HSUPA category Bands GPRS/EDGE multi-slot class Bands GNSS receiver GNSS via modem Assist Now Software CellLocate® UART USB 2.0 SDIO (Master) DCC (I2C) GPIOs Analog audio Digital audio Network indication Antenna supervisor MIMO 2x2 / Rx Diversity Jamming detection Embedded TCP/UDP stack Embedded HTTP,FTP FOTA eCall / ERA GLONASS Dual stack IPv4/IPv6 Standard Professional Automotive TOBY-L200 4 2,4,5 7,17 24 6 850/900 AWS 1900/2100 12 Quad F F F ○ ● ○ F F F □ F ● F F F F F ● TOBY-L201 4 2,4,5 13,17 24 6 850/1900 F F F ● ● F F F F ● F ● F ● ● ● F ● TOBY-L210 4 1,3,5 7,8,20 24 6 850/900 1900/2100 12 Quad F F F ○ ● ○ F F F □ F ● F F F F F ● TOBY-L280 4 1,3,5, 7,8,28 24 6 850/900 1900/2100 12 Quad F F F ● ● F F F F ● F ● F F F F F ● MPCI-L200 4 2,4,5 7,17 24 6 850/900 AWS 1900/2100 12 Quad ● ● ● F F F F ● MPCI-L210 4 1,3,5 7,8,20 24 6 850/900 1900/2100 12 Quad ● ● ● F F F F ● ● = supported by all product versions ○ = supported by product version “50” and future product versions □ = supported by all product versions except product version “50” F = supported by future product versions Table 1: TOBY-L2 and MPCI-L2 series main features summary

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 9 of 158 Table 2 reports a summary of cellular radio access technologies characteristics and features of the modules. 4G LTE 3G UMTS/HSDPA/HSUPA 2G GSM/GPRS/EDGE 3GPP Release 9 Long Term Evolution (LTE) Evolved Uni.Terrestrial Radio Access (E-UTRA) Frequency Division Duplex (FDD) DL Multi-Input Multi-Output (MIMO) 2 x 2 3GPP Release 8 Dual-Cell HS Packet Access (DC-HSPA+) UMTS Terrestrial Radio Access (UTRA) Frequency Division Duplex (FDD) DL Rx diversity 3GPP Release 8 Enhanced Data rate GSM Evolution (EDGE) GSM EGPRS Radio Access (GERA) Time Division Multiple Access (TDMA) DL Advanced Rx Performance (DARP) Phase 1 Band support:  TOBY-L200:  Band 17 (700 MHz)  Band 5 (850 MHz)  Band 4 (AWS, i.e. 1700 MHz)  Band 2 (1900 MHz)  Band 7 (2600 MHz)  TOBY-L201:  Band 17 (700 MHz)  Band 13 (750 MHz)  Band 5 (850 MHz)  Band 4 (AWS, i.e. 1700 MHz)  Band 2 (1900 MHz)  TOBY-L210:  Band 20 (800 MHz)  Band 5 (850 MHz)  Band 8 (900 MHz)  Band 3 (1800 MHz)  Band 1 (2100 MHz)  Band 7 (2600 MHz)  TOBY-L280:  Band 28 (750 MHz)  Band 5 (850 MHz)  Band 8 (900 MHz)  Band 3 (1800 MHz)  Band 1 (2100 MHz)  Band 7 (2600 MHz) Band support:  TOBY-L200:  Band 5 (850 MHz)  Band 8 (900 MHz)  Band 4 (AWS, i.e. 1700 MHz)  Band 2 (1900 MHz)  Band 1 (2100 MHz)  TOBY-L201:  Band 5 (850 MHz)  Band 2 (1900 MHz)  TOBY-L210:  Band 5 (850 MHz)  Band 8 (900 MHz)  Band 2 (1900 MHz)  Band 1 (2100 MHz)  TOBY-L280:  Band 5 (850 MHz)  Band 8 (900 MHz)  Band 2 (1900 MHz)  Band 1 (2100 MHz) Band support  TOBY-L200:  GSM 850 MHz  E-GSM 900 MHz  DCS 1800 MHz  PCS 1900 MHz  TOBY-L210:  GSM 850 MHz  E-GSM 900 MHz  DCS 1800 MHz  PCS 1900 MHz  TOBY-L280:  GSM 850 MHz  E-GSM 900 MHz  DCS 1800 MHz  PCS 1900 MHz LTE Power Class  Power Class 3 (23 dBm) for LTE mode WCDMA/HSDPA/HSUPA Power Class  Power Class 3 (24 dBm) for UMTS/HSDPA/HSUPA mode GSM/GPRS (GMSK) Power Class  Power Class 4 (33 dBm) for GSM/E-GSM bands  Power Class 1 (30 dBm) for DCS/PCS bands EDGE (8-PSK) Power Class  Power Class E2 (27 dBm) for GSM/E-GSM bands  Power Class E2 (26 dBm) for DCS/PCS bands Data rate  LTE category 4: up to 150 Mb/s DL, 50 Mb/s UL Data rate  TOBY-L200 / MPCI-L200:  HSDPA cat.14, up to 21 Mb/s DL1  HSUPA cat.6, up to 5.6 Mb/s UL  TOBY-L210 / MPCI-L210:  HSDPA cat.24, up to 42 Mb/s DL  HSUPA cat.6, up to 5.6 Mb/s UL Data rate2  GPRS multi-slot class 123, CS1-CS4, up to 85.6 kb/s DL/UL  EDGE multi-slot class 123, MCS1-MCS9 up to 236.8 kb/s DL/UL Table 2: TOBY-L2 and MPCI-L2 series LTE, 3G and 2G characteristics summary 1 HSDPA category 24 capable 2 GPRS/EDGE multi-slot class determines the number of timeslots available for upload and download and thus the speed at which data can be transmitted and received, with higher classes typically allowing faster data transfer rates. 3 GPRS/EDGE multi-slot class 12 implies a maximum of 4 slots in DL (reception) and 4 slots in UL (transmission) with 5 slots in total.

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 10 of 158 1.2 Architecture Figure 1 summarizes the internal architecture of TOBY-L2 series modules. CellularBase-bandProcessorMemoryPower Management Unit26 MHz32.768 kHzANT1RF TransceiverANT2V_INT (I/O)V_BCKP (RTC)VCC (Supply)SIMUSBGPIOPower OnExternal ResetPAsLNAs FiltersFiltersDuplexerFiltersPAsLNAs FiltersFiltersDuplexerFiltersLNAs FiltersFiltersLNAs FiltersFiltersSwitchSwitchDDC(I2C)SDIOUARTDigital audio (I2S)ANT_DETHost Select Figure 1: TOBY-L2 series block diagram As described in the Figure 2, each MPCI-L2 series module integrates one TOBY-L2 series module:  The MPCI-L200 integrates a TOBY-L200 module  The MPCI-L210 integrates a TOBY-L210 module The TOBY-L2 module represents the core of the device, providing the related LTE/3G/2G modem and processing functionalities. Additional signal conditioning circuitry is implemented for PCI Express Mini Card compliance, and two UF.L connectors are available for easy antenna integration. ANT1SIMUSBW_DISABLE#TOBY-L2seriesSignal ConditioningANT2PERST#LED_WWAN#U.FLU.FL3.3Vaux (Supply)Boost ConverterVCC Figure 2: MPCI-L2 series block diagram

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 11 of 158 1.2.1 Internal blocks As described in Figure 2, each MPCI-L2 series module integrates one TOBY-L2 series module, which consists of the following internal sections: RF, baseband and power management. RF section The RF section is composed of RF transceiver, PAs, LNAs, crystal oscillator, filters, duplexers and RF switches. Tx signal is pre-amplified by RF transceiver, then output to the primary antenna input/output port (ANT1) of the module via power amplifier (PA), SAW band pass filters band, specific duplexer and antenna switch. Dual receiving paths are implemented according to LTE Down-Link MIMO 2 x 2 and 3G Receiver Diversity radio technologies supported by the modules as LTE category 4 and HSDPA category 24 User Equipments: incoming signals are received through the primary (ANT1) and the secondary (ANT2) antenna input ports which are connected to the RF transceiver via specific antenna switch, diplexer, duplexer, LNA, SAW band pass filters.  RF transceiver performs modulation, up-conversion of the baseband I/Q signals for Tx, down-conversion and demodulation of the dual RF signals for Rx. The RF transceiver contains: Automatically gain controlled direct conversion Zero-IF receiver, Highly linear RF demodulator / modulator capable GMSK, 8-PSK, QPSK, 16-QAM, 64-QAM, Fractional-N Sigma-Delta RF synthesizer, VCO.  Power Amplifiers (PA) amplify the Tx signal modulated by the RF transceiver  RF switches connect primary (ANT1) and secondary (ANT2) antenna ports to the suitable Tx / Rx path  Low Noise Amplifiers (LNA) enhance the received sensitivity  SAW duplexers separate the Tx and Rx signal paths and provide RF filtering  SAW band pass filters enhance the rejection of out-of-band signals  26 MHz crystal oscillator generates the clock reference in active-mode or connected-mode. Baseband and power management section The Baseband and Power Management section is composed of the following main elements:  A mixed signal ASIC, which integrates Microprocessor for control functions DSP core for LTE/3G/2G Layer 1 and digital processing of Rx and Tx signal paths Memory interface controller Dedicated peripheral blocks for control of the USB, SIM and GPIO digital interfaces Analog front end interfaces to RF transceiver ASIC  Memory system, which includes NAND flash and LPDDR  Voltage regulators to derive all the subsystem supply voltages from the module supply input VCC  Voltage sources for external use: V_BCKP and V_INT (not available on MPCI-L2 series modules)  Hardware power on  Hardware reset  Low power idle-mode support  32.768 kHz crystal oscillator to provide the clock reference in the low power idle-mode, which can be set by enable power saving configuration using the AT+UPSV command.

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 12 of 158 1.3 Pin-out 1.3.1 TOBY-L2 series pin assignment Table 3 lists the pin-out of the TOBY-L2 series modules, with pins grouped by function. Function Pin Name Pin No I/O Description Remarks Power VCC 70,71,72 I Module supply input VCC pins are internally connected each other. VCC supply circuit affects the RF performance and compliance of the device integrating the module with applicable required certification schemes. See section 1.5.1 for functional description and requirements for the VCC module supply. See section 2.2.1 for external circuit design-in. GND 2, 30, 32, 44, 46, 69, 73, 74, 76, 78, 79, 80, 82, 83, 85, 86, 88-90, 92-152 N/A Ground GND pins are internally connected each other. External ground connection affects the RF and thermal performance of the device. See section 1.5.1 for functional description. See section 2.2.1 for external circuit design-in. V_BCKP 3 I/O RTC supply input/output V_BCKP = 3.0 V (typical) generated by internal regulator when valid VCC supply is present. See section 1.5.2 for functional description. See section 2.2.2 for external circuit design-in. V_INT 5 O Generic digital interfaces supply output V_INT = 1.8 V (typical) generated by internal regulator when the module is switched on. See section 1.5.3 for functional description. See section 2.2.3 for external circuit design-in. System PWR_ON 20 I Power-on input Internal active pull-up to the VCC enabled. See section 1.6.1 for functional description. See section 2.3.1 for external circuit design-in. RESET_N 23 I External reset input Internal active pull-up to the VCC enabled. See section 1.6.3 for functional description. See section 2.3.2 for external circuit design-in. HOST_SELECT0 26 I Selection of module configuration by the host processor Note: Not supported by “00”, “01”, “50” product versions. See section 1.6.4 for functional description. See section 2.3.3 for external circuit design-in. HOST_SELECT1 62 I Selection of module configuration by the host processor Note: Not supported by “00”, “01”, “50” product versions. See section 1.6.4 for functional description. See section 2.3.3 for external circuit design-in. Antennas ANT1 81 I/O Primary antenna Main Tx / Rx antenna interface. 50  nominal characteristic impedance. Antenna circuit affects the RF performance and application device compliance with required certification schemes. See section 1.7 for functional description / requirements. See section 2.4 for external circuit design-in. ANT2 87 I Secondary antenna Rx only for MIMO 2x2 and Rx diversity. 50  nominal characteristic impedance. Antenna circuit affects the RF performance and application device compliance with required certification schemes. See section 1.7 for functional description / requirements See section 2.4 for external circuit design-in. ANT_DET 75 I Antenna detection Note: not supported by “00”, “01”, “50” product versions. See section 1.7.2 for functional description. See section 2.4.2 for external circuit design-in.

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 13 of 158 Function Pin Name Pin No I/O Description Remarks SIM VSIM 59 O SIM supply output VSIM = 1.8 V / 3 V output as per the connected SIM type. See section 1.8 for functional description. See section 2.5 for external circuit design-in. SIM_IO 57 I/O SIM data Data input/output for 1.8 V / 3 V SIM Internal 4.7 k pull-up to VSIM. See section 1.8 for functional description. See section 2.5 for external circuit design-in. SIM_CLK 56 O SIM clock 3.25 MHz clock output for 1.8 V / 3 V SIM See section 1.8 for functional description. See section 2.5 for external circuit design-in. SIM_RST 58 O SIM reset Reset output for 1.8 V / 3 V SIM See section 1.8 for functional description. See section 2.5 for external circuit design-in. USB VUSB_DET 4 I USB detect input Note: leave unconnected, as VBUS detect is not supported. Input for VBUS (5 V typical) USB supply sense. See section 1.9.1 for functional description. See section 2.6.1 for external circuit design-in. USB_D- 27 I/O USB Data Line D- USB interface for AT commands, data communication, FOAT, FW update by u-blox EasyFlash tool and diagnostic. 90  nominal differential impedance (Z0) 30  nominal common mode impedance (ZCM) Pull-up or pull-down resistors and external series resistors as required by the USB 2.0 specifications [4] are part of the USB pad driver and need not be provided externally. See section 1.9.1 for functional description. See section 2.6.1 for external circuit design-in. USB_D+ 28 I/O USB Data Line D+ USB interface for AT commands, data communication, FOAT, FW update by u-blox EasyFlash tool and diagnostic. 90  nominal differential impedance (Z0) 30  nominal common mode impedance (ZCM) Pull-up or pull-down resistors and external series resistors as required by the USB 2.0 specifications [4] are part of the USB pad driver and need not be provided externally. See section 1.9.1 for functional description. See section 2.6.1 for external circuit design-in.

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 14 of 158 Function Pin Name Pin No I/O Description Remarks UART RXD 17 O UART data output Note: not supported by TOBY-L200-00S, TOBY-L210-00S. 1.8 V output, Circuit 104 (RXD) in ITU-T V.24, for AT command, data communication, FOAT. Add Test-Point and series 0  to access for diagnostic. See section 1.9.2 for functional description. See section 2.6.2 for external circuit design-in. TXD 16 I UART data input Note: not supported by TOBY-L200-00S, TOBY-L210-00S. 1.8 V input, Circuit 103 (TXD) in ITU-T V.24, for AT command, data communication, FOAT. Internal active pull-up to V_INT. Add Test-Point and series 0  to access for diagnostic. See section 1.9.2 for functional description. See section 2.6.2 for external circuit design-in. CTS 15 O UART clear to send output Note: not supported by TOBY-L200-00S, TOBY-L210-00S. 1.8 V output, Circuit 106 (CTS) in ITU-T V.24. Add Test-Point and series 0  to access for diagnostic. See section 1.9.2 for functional description. See section 2.6.2 for external circuit design-in. RTS 14 I UART ready to send input Note: not supported by TOBY-L200-00S, TOBY-L210-00S. 1.8 V input, Circuit 105 (RTS) in ITU-T V.24. Internal active pull-up to V_INT. Add Test-Point and series 0  to access for diagnostic. See section 1.9.2 for functional description. See section 2.6.2 for external circuit design-in. DSR 10 O / I/O UART data set ready output / GPIO Note: UART DSR not supported by TOBY-L200-00S, TOBY-L210-00S, TOBY-L200-50S, TOBY-L210-50S; GPIO not supported by “00”, “01”, “50” product versions. 1.8 V, Circuit 107 in ITU-T V.24, configurable as GPIO. Add Test-Point and series 0  to access for diagnostic. See section 1.9.2 and 1.11 for functional description. See section 2.6.2 and 2.8 for external circuit design-in. RI 11 O / I/O UART ring indicator output / GPIO Note: RI not supported by TOBY-L200-00S, TOBY-L210-00S; GPIO not supported by “00”, “01”, “50” product versions. 1.8 V, Circuit 125 in ITU-T V.24, configurable as GPIO. Add Test-Point and series 0  to access for diagnostic. See section 1.9.2 and 1.11 for functional description. See section 2.6.2 and 2.8 for external circuit design-in. DTR 13 I / I/O UART data terminal ready input / GPIO Note: UART DTR not supported by TOBY-L200-00S, TOBY-L210-00S, TOBY-L200-50S, TOBY-L210-50S; GPIO not supported by “00”, “01”, “50” product versions. 1.8 V, Circuit 108/2 in ITU-T V.24, configurable as GPIO. Internal active pull-up to V_INT when configured as DTR. Add Test-Point and series 0  to access for diagnostic. See section 1.9.2 and 1.11 for functional description. See section 2.6.2 and 2.8 for external circuit design-in. DCD 12 O / I/O UART data carrier detect output / GPIO Note: UART DCD not supported by TOBY-L200-00S, TOBY-L210-00S, TOBY-L200-50S, TOBY-L210-50S; GPIO not supported by “00”, “01”, “50” product versions. 1.8 V, Circuit 109 in ITU-T V.24, configurable as GPIO. Add Test-Point and series 0  to access for diagnostic. See section 1.9.2 and 1.11 for functional description. See section 2.6.2 and 2.8 for external circuit design-in.

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 15 of 158 Function Pin Name Pin No I/O Description Remarks DDC SCL 54 O I2C bus clock line Note: not supported by “00”, “01”, “50” product versions. 1.8 V open drain, for communication with u-blox GNSS receivers and other I2C-slave devices as an audio codec. External pull-up required. See section 1.9.3 for functional description. See section 2.6.3 for external circuit design-in. SDA 55 I/O I2C bus data line Note: not supported by “00”, “01”, “50” product versions. 1.8 V open drain, for communication with u-blox GNSS receivers and other I2C-slave devices as an audio codec. External pull-up required. See section 1.9.3 for functional description. See section 2.6.3 for external circuit design-in. SDIO SDIO_D0 66 I/O SDIO serial data [0] Note: not supported by “00”, “01” product versions. SDIO interface for communication with external Wi-Fi chip See section 1.9.4 for functional description. See section 2.6.4 for external circuit design-in. SDIO_D1 68 I/O SDIO serial data [1] Note: not supported by “00”, “01” product versions. SDIO interface for communication with external Wi-Fi chip See section 1.9.4 for functional description. See section 2.6.4 for external circuit design-in. SDIO_D2 63 I/O SDIO serial data [2] Note: not supported by “00”, “01” product versions. SDIO interface for communication with external Wi-Fi chip See section 1.9.4 for functional description. See section 2.6.4 for external circuit design-in. SDIO_D3 67 I/O SDIO serial data [3] Note: not supported by “00”, “01” product versions. SDIO interface for communication with external Wi-Fi chip See section 1.9.4 for functional description. See section 2.6.4 for external circuit design-in. SDIO_CLK 64 O SDIO serial clock Note: not supported by “00”, “01” product versions. SDIO interface for communication with external Wi-Fi chip See section 1.9.4 for functional description. See section 2.6.4 for external circuit design-in. SDIO_CMD 65 I/O SDIO command Note: not supported by “00”, “01” product versions. SDIO interface for communication with external Wi-Fi chip See section 1.9.4 for functional description. See section 2.6.4 for external circuit design-in. Audio I2S_TXD 51 O / I/O I2S transmit data / GPIO Note: not supported by “00”, “01”, “50” product versions. I2S transmit data output, alternatively configurable as GPIO. See sections 1.10 and 1.11 for functional description. See sections 2.7 and 2.8 for external circuit design-in. I2S_RXD 53 I / I/O I2S receive data / GPIO Note: not supported by “00”, “01”, “50” product versions. I2S receive data input, alternatively configurable as GPIO. See sections 1.10 and 1.11 for functional description. See sections 2.7 and 2.8 for external circuit design-in. I2S_CLK 52 I/O / I/O I2S clock / GPIO Note: not supported by “00”, “01”, “50” product versions. I2S serial clock, alternatively configurable as GPIO. See sections 1.10 and 1.11 for functional description. See sections 2.7 and 2.8 for external circuit design-in. I2S_WA 50 I/O / I/O I2S word alignment / GPIO Note: not supported by “00”, “01”, “50” product versions. I2S word alignment, alternatively configurable as GPIO. See sections 1.10 and 1.11 for functional description. See sections 2.7 and 2.8 for external circuit design-in.

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 16 of 158 Function Pin Name Pin No I/O Description Remarks GPIO GPIO1 21 I/O GPIO Note: not supported by “00”, “01”, “50” product versions. WWAN status indication set on “00”, “01” product versions. Wi-Fi enable function set on “50” product version. 1.8 V GPIO with alternatively configurable functions See section 1.11 for functional description. See section 2.8 for external circuit design-in. GPIO2 22 I/O GPIO Note: not supported by “00”, “01”, “50” product versions. 1.8 V GPIO with alternatively configurable functions See section 1.11 for functional description. See section 2.8 for external circuit design-in. GPIO3 24 I/O GPIO Note: not supported by “00”, “01”, “50” product versions. 1.8 V GPIO with alternatively configurable functions See section 1.11 for functional description. See section 2.8 for external circuit design-in. GPIO4 25 I/O GPIO Note: not supported by “00”, “01”, “50” product versions. 1.8 V GPIO with alternatively configurable functions See section 1.11 for functional description. See section 2.8 for external circuit design-in. GPIO5 60 I/O GPIO Note: not supported by “00”, “01”, “50” product versions. 1.8 V GPIO with alternatively configurable functions See section 1.11 for functional description. See section 2.8 for external circuit design-in. GPIO6 61 I/O GPIO Note: not supported by “00”, “01”, “50” product versions. 1.8 V GPIO with alternatively configurable functions See section 1.11 for functional description. See section 2.8 for external circuit design-in. Reserved RSVD 6 N/A Reserved pin This pin must be connected to ground. See section 2.10 RSVD 1, 7-9, 18, 19, 29, 31, 33-43, 45, 47-49, 77, 84, 91 N/A Reserved pin Leave unconnected. See section 2.10 Table 3: TOBY-L2 series module pin definition, grouped by function

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 17 of 158 1.3.2 MPCI-L2 series pin assignment Table 4 lists the pin-out of the MPCI-L2 series modules, with pins grouped by function. Function Pin Name Pin No I/O Description Remarks Power 3.3Vaux 2, 24, 39, 41, 52 I Module supply input 3.3Vaux pins are internally connected each other. 3.3Vaux supply circuit affects the RF performance and compliance of the device integrating the module with applicable required certification schemes. See section 1.5.1 for functional description and requirements for the 3.3Vaux module supply. See section 2.2.1 for external circuit design-in. GND 4, 9, 15, 18, 21, 26, 27, 29, 34, 35, 37, 40, 43, 50 N/A Ground GND pins are internally connected each other. External ground connection affects the RF and thermal performance of the device. See section 1.5.1 for functional description. See section 2.2.1 for external circuit design-in. Auxiliary Signals PERST# 22 I External reset input Internal 45 k pull-up to 3.3 V supply. See section 1.6.3 for functional description. See section 2.3.2 for external circuit design-in. Antennas ANT1 U.FL I/O Primary antenna Main Tx / Rx antenna interface. 50  nominal characteristic impedance. Antenna circuit affects the RF performance and compliance of the device integrating the module with applicable required certification schemes. See section 1.7 for functional description / requirements. See section 2.4 for external circuit design-in. ANT2 U.FL I Secondary antenna Rx only for MIMO 2x2 and Rx diversity. 50  nominal characteristic impedance. Antenna circuit affects the RF performance and compliance of the device integrating the module with applicable required certification schemes. See section 1.7 for functional description / requirements See section 2.4 for external circuit design-in. SIM UIM_PWR 8 O SIM supply output UIM_PWR = 1.8 V / 3 V automatically generated according to the connected SIM type. See section 1.8 for functional description. See section 2.5 for external circuit design-in. UIM_DATA 10 I/O SIM data Data input/output for 1.8 V / 3 V SIM Internal 4.7 k pull-up to UIM_PWR. See section 1.8 for functional description. See section 2.5 for external circuit design-in. UIM_CLK 12 O SIM clock 3.25 MHz clock output for 1.8 V / 3 V SIM See section 1.8 for functional description. See section 2.5 for external circuit design-in. UIM_RESET 14 O SIM reset Reset output for 1.8 V / 3 V SIM See section 1.8 for functional description. See section 2.5 for external circuit design-in.

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 18 of 158 Function Pin Name Pin No I/O Description Remarks USB USB_D- 36 I/O USB Data Line D- USB interface for AT commands, data communication, FOAT, FW update by u-blox EasyFlash tool and diagnostic. 90  nominal differential impedance (Z0) 30  nominal common mode impedance (ZCM) Pull-up or pull-down resistors and external series resistors as required by the USB 2.0 specifications [4] are part of the USB pad driver and need not be provided externally. See section 1.9.1 for functional description. See section 2.6.1 for external circuit design-in. USB_D+ 38 I/O USB Data Line D+ USB interface for AT commands, data communication, FOAT, FW update by u-blox EasyFlash tool and diagnostic. 90  nominal differential impedance (Z0) 30  nominal common mode impedance (ZCM) Pull-up or pull-down resistors and external series resistors as required by the USB 2.0 specifications [4] are part of the USB pad driver and need not be provided externally. See section 1.9.1 for functional description. See section 2.6.1 for external circuit design-in. Specific Signals LED_WWAN# 42 O LED indicator output Open drain active low output. See section 1.12 for functional description. See section 2.9 for external circuit design-in. W_DISABLE# 20 I Wireless radio disable input Internal 22 k pull-up to 3.3Vaux. See section 1.12 for functional description. See section 2.9 for external circuit design-in. Not Connected NC 1, 3, 5-7, 11, 13, 16, 17, 19, 23, 25, 28, 30-33, 44-46, 47-49, 51 N/A Not connected Internally not connected. See section 1.14 for the description. Table 4: MPCI-L2 series module pin definition, grouped by function

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 19 of 158 1.4 Operating modes TOBY-L2 and MPCI-L2 series modules have several operating modes. The operating modes are defined in Table 5 and described in detail in Table 6, providing general guidelines for operation. General Status Operating Mode Definition Power-down Not-Powered Mode VCC or 3.3Vaux supply not present or below operating range: module is switched off. Power-Off Mode VCC or 3.3Vaux supply within operating range and module is switched off. Normal Operation Idle-Mode Module processor core runs with 32 kHz reference generated by the internal oscillator. Active-Mode Module processor core runs with 26 MHz reference generated by the internal oscillator. Connected-Mode RF Tx/Rx data connection enabled and processor core runs with 26 MHz reference. Table 5: TOBY-L2 and MPCI-L2 series modules operating modes definition Operating Mode Description Transition between operating modes Not-Powered Mode Module is switched off. Application interfaces are not accessible. When VCC or 3.3Vaux supply is removed, the modules enter not-powered mode. When in not-powered mode, TOBY-L2 modules cannot be switched on by PWR_ON, RESET_N or RTC alarm and enter active-mode after applying VCC supply (see 1.6.1). When in not-powered mode, MPCI-L2 modules cannot be switched on by RTC alarm and enter active-mode after applying 3.3Vaux supply (see 1.6.1). Power-Off Mode Module is switched off: normal shutdown by an appropriate power-off event (see 1.6.2). Application interfaces are not accessible. MPCI-L2 modules do not support Power-Off Mode but halt mode (see 1.6.2 and u-blox AT Commands Manual [3], AT+CFUN=127 command). When the modules are switched off by an appropriate power-off event (see 1.6.2), the modules enter power-off mode from active-mode. When in power-off mode, TOBY-L2 modules can be switched on by PWR_ON, RESET_N or an RTC alarm. When in power-off mode, TOBY-L2 modules enter the not-powered mode after removing VCC supply. Idle-Mode Module is switched on with application interfaces disabled or suspended: the module is temporarily not ready to communicate with an external device by means of the application interfaces as configured to reduce the current consumption. The module enters the low power idle-mode whenever possible if power saving is enabled by AT+UPSV (see u-blox AT Commands Manual [3]) reducing current consumption (see 1.5.1.5). With HW flow control enabled and AT+UPSV=1 or AT+UPSV=3, the UART CTS line indicates when the UART is enabled (see 1.9.2.3, 1.9.2.4). With HW flow control disabled, the UART CTS line is fixed to ON state (see 1.9.2.3). Power saving configuration is not enabled by default: it can be enabled by the AT+UPSV command (see the u-blox AT Commands Manual [3]). The modules automatically switch from active-mode to low power idle-mode whenever possible if power saving is enabled (see sections 1.5.1.5, 1.9.1.4, 1.9.2.4 and u-blox AT Commands Manual [3], AT+UPSV). The modules wake up from idle-mode to active-mode in the following events:  Automatic periodic monitoring of the paging channel for the paging block reception according to network conditions (see 1.5.1.5)  The connected USB host forces a remote wakeup of the module as USB device (see 1.9.1.4)  Automatic periodic enable of the UART interface to receive / send data, with AT+UPSV=1 (see 1.9.2.4)  Data received on UART interface, with HW flow control disabled and AT+UPSV=1 (see 1.9.2.4)  RTS input set ON by the host DTE, with HW flow control disabled and AT+UPSV=2 (see 1.9.2.4)  DTR input set ON by the host DTE, with AT+UPSV=3 (see 1.9.2.4)  The connected SDIO device forces a wakeup of the module as SDIO host (see 1.9.4)  A preset RTC alarm occurs (see u-blox AT Commands Manual [3], AT+CALA)

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 20 of 158 Operating Mode Description Transition between operating modes Active-Mode Module is switched on with application interfaces enabled or not suspended: the module is ready to communicate with an external device by means of the application interfaces unless power saving configuration is enabled by AT+UPSV (see 1.9.1.4, 1.9.2.4 and u-blox AT Commands Manual [3]). When the modules are switched on by an appropriate power-on event (see 1.6.1), the module enter active-mode from power-off mode. If power saving configuration is enabled by the AT+UPSV command, the module automatically switches from active to idle-mode whenever possible and the module wakes up from idle to active-mode in the events listed above (see idle-mode to active-mode transition description above). When a RF Tx/Rx data connection is initiated or when RF Tx/Rx is required due to a connection previously initiated, the module switches from active to connected-mode. Connected-Mode RF Tx/Rx data connection is in progress. The module is prepared to accept data signals from an external device unless power saving configuration is enabled by AT+UPSV (see sections 1.9.1.4, 1.9.2.4 and u-blox AT Commands Manual [3]). When a data connection is initiated, the module enters connected-mode from idle-mode. If power saving configuration is enabled by the AT+UPSV command, the module automatically switches from connected to active and then idle-mode whenever possible and the module wakes up from idle to active and then connected mode if RF Transmission/Reception is necessary. When a data connection is terminated, the module returns to the active-mode. Table 6: TOBY-L2 and MPCI-L2 series modules operating modes description Figure 3 describes the transition between the different operating modes. TOBY-L2 Switch ON:•Apply VCCMPCI-L2 Switch ON:•Apply 3.3VauxIf power saving is enabled and there is no activity for a defined time intervalAny wake up event described in the module operating modes summary table aboveIncoming/outgoing call or other dedicated device network communicationNo RF Tx/Rx in progress, Call terminated, Communication droppedTOBY-L2 Switch ON:•PWR_ON•RESET_N•RTC alarmNot poweredPower offActiveConnected IdleTOBY-L2 Switch OFF:•AT+CPWROFF•RESET_NMPCI-L2:•AT+CFUN=127 and then remove 3.3VauxTOBY-L2:•Remove VCC Figure 3: TOBY-L2 and MPCI-L2 series modules operating modes transition

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 21 of 158 1.5 Supply interfaces 1.5.1 Module supply input (VCC or 3.3Vaux) TOBY-L2 modules are supplied via the three VCC pins, and MPCI-L2 modules are supplied via the five 3.3Vaux pins. All supply voltages used inside the modules are generated from the VCC or the 3.3Vaux supply input by integrated voltage regulators, including the V_BCKP RTC supply, the V_INT generic digital interface supply, and the VSIM or UIM_PWR SIM interface supply. The current drawn by the TOBY-L2 and MPCI-L2 series modules through the VCC or 3.3Vaux pins can vary by several orders of magnitude depending on radio access technology, operation mode and state. It is important that the supply source is able to support both the high peak of current consumption during 2G transmission at maximum RF power level (as described in the section 1.5.1.2) and the high average current consumption during 3G and LTE transmission at maximum RF power level (as described in the sections 1.5.1.3 and 1.5.1.4). 1.5.1.1 VCC or 3.3Vaux supply requirements Table 7 summarizes the requirements for the VCC or 3.3Vaux modules supply. See section 2.2.1 for suggestions to properly design a VCC or 3.3Vaux supply circuit compliant with the requirements listed in Table 7. The supply circuit affects the RF compliance of the device integrating TOBY-L2 and MPCI-L2 series modules with applicable required certification schemes as well as antenna circuit design. Compliance is guaranteed if the requirements summarized in the Table 7 are fulfilled. Item Requirement Remark VCC or 3.3Vaux nominal voltage Within VCC or 3.3Vaux normal operating range: See “Supply/Power pins” section in the TOBY-L2 Data Sheet [1] or in the MPCI-L2 Data Sheet [2]. The modules cannot be switched on if the supply voltage is below the normal operating range minimum limit. VCC or 3.3Vaux voltage during normal operation Within VCC or 3.3Vaux extended operating range: See “Supply/Power pins” section in the TOBY-L2 Data Sheet [1] or in the MPCI-L2 Data Sheet [2]. The modules may switch off if the supply voltage drops below the extended operating range minimum limit. VCC or 3.3Vaux average current Support with adequate margin the highest averaged current consumption value in connected-mode conditions specified for VCC in TOBY-L2 Data Sheet [1] or specified for 3.3Vaux in MPCI-L2 Data Sheet [2]. The maximum average current consumption can be greater than the specified value according to the actual antenna mismatching, temperature and supply voltage. Sections 1.5.1.2, 1.5.1.3 and 1.5.1.4 describe current consumption profiles in 2G, 3G and LTE connected-mode. VCC or 3.3Vaux peak current Support with margin the highest peak current consumption value in 2G connected-mode conditions specified for VCC in TOBY-L2 Data Sheet [1] or specified for 3.3Vaux in MPCI-L2 Data Sheet [2]. The specified maximum peak of current consumption occurs during GSM single transmit slot in 850/900 MHz connected-mode, in case of mismatched antenna. Section 1.5.1.2 describes 2G Tx peak/pulse current. VCC or 3.3Vaux voltage drop during 2G Tx slots Lower than 400 mV Supply voltage drop values greater than recommended during 2G TDMA transmission slots directly affect the RF compliance with applicable certification schemes. Figure 5 describes supply voltage drop during 2G Tx slots. VCC or 3.3Vaux voltage ripple during RF transmission Noise in the supply has to be minimized High supply voltage ripple values during LTE/3G/2G RF transmissions in connected-mode directly affect the RF compliance with applicable certification schemes. Figure 5 describes supply voltage ripple during RF Tx. VCC or 3.3Vaux under/over-shoot at start/end of Tx slots Absent or at least minimized Supply voltage under-shoot or over-shoot at the start or the end of 2G TDMA transmission slots directly affect the RF compliance with applicable certification schemes. Figure 5 describes supply voltage under/over-shoot Table 7: Summary of VCC or 3.3Vaux modules supply requirements

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 28 of 158 1.5.2 RTC supply input/output (V_BCKP) The RTC supply V_BCKP pin is not available on MPCI-L2 series modules. The V_BCKP pin of TOBY-L2 series modules connects the supply for the Real Time Clock (RTC). A linear LDO regulator integrated in the Power Management Unit internally generates this supply, as shown in Figure 11, with low current capability (see the TOBY-L2 series Data Sheet [1]). The output of this regulator is always enabled when the main module voltage supply applied to the VCC pins is within the valid operating range. Baseband Processor70VCC71VCC72VCC3V_BCKPLinear LDOPower ManagementTOBY-L2 series32 kHzRTC Figure 11: TOBY-L2 series RTC supply (V_BCKP) simplified block diagram The RTC provides the module time reference (date and time) that is used to set the wake-up interval during the low power idle-mode periods, and is able to make available the programmable alarm functions. The RTC functions are available also in power-down mode when the V_BCKP voltage is within its valid range (specified in the “Input characteristics of Supply/Power pins” table in TOBY-L2 series Data Sheet [1]). The RTC can be supplied from an external back-up battery through the V_BCKP, when the main module voltage supply is not applied to the VCC pins. This lets the time reference (date and time) run until the V_BCKP voltage is within its valid range, even when the main supply is not provided to the module. Consider that the module cannot switch on if a valid voltage is not present on VCC even when the RTC is supplied through V_BCKP (meaning that VCC is mandatory to switch on the module). The RTC has very low current consumption, but is highly temperature dependent. For example, V_BCKP current consumption at the maximum operating temperature can be higher than the typical value at 25 °C specified in the “Input characteristics of Supply/Power pins” table in the TOBY-L2 series Data Sheet [1]. If V_BCKP is left unconnected and the module main supply is not applied to the VCC pins, the RTC is supplied from the bypass capacitor mounted inside the module. However, this capacitor is not able to provide a long buffering time: within few milliseconds the voltage on V_BCKP will go below the valid range (1.4 V min). This has no impact on cellular connectivity, as all the module functionalities do not rely on date and time setting.

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 29 of 158 1.5.3 Generic digital interfaces supply output (V_INT) The generic digital interfaces supply V_INT pin is not available on MPCI-L2 series modules. The V_INT output pin of the TOBY-L2 series modules is connected to an internal 1.8 V supply with current capability specified in the TOBY-L2 series Data Sheet [1]. This supply is internally generated by a switching step-down regulator integrated in the Power Management Unit and it is internally used to source the generic digital I/O interfaces of the TOBY-L2 module, as described in Figure 12. The output of this regulator is enabled when the module is switched on and it is disabled when the module is switched off. Baseband Processor70VCC71VCC72VCC5V_INTSwitchingStep-DownPower ManagementTOBY-L2 seriesDigital I/O Figure 12: TOBY-L2 series generic digital interfaces supply output (V_INT) simplified block diagram The switching regulator operates in Pulse Width Modulation (PWM) mode for greater efficiency at high output loads and it automatically switches to Pulse Frequency Modulation (PFM) power save mode for greater efficiency at low output loads. The V_INT output voltage ripple is specified in the TOBY-L2 series Data Sheet [1].

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 30 of 158 1.6 System function interfaces 1.6.1 Module power-on The PWR_ON input pin is not available on MPCI-L2 series modules. When the TOBY-L2 and MPCI-L2 series modules are in the not-powered mode (switched off, i.e. the VCC or 3.3Vaux module supply is not applied), they can be switched on as following:  Rising edge on the VCC or 3.3Vaux supply input to a valid voltage for module supply, so that the module switches on applying a proper VCC or 3.3Vaux supply within the normal operating range.  Alternately, the RESET_N or PERST# pin can be held to the low level during the VCC or 3.3Vaux rising edge, so that the module switches on releasing the RESET_N or PERST# pin when the VCC or 3.3Vaux module supply voltage stabilizes at its proper nominal value within the normal operating range. The status of the PWR_ON input pin of TOBY-L2 modules while applying the VCC module supply is not relevant: during this phase the PWR_ON pin can be set high or low by the external circuit. When the TOBY-L2 modules are in the power-off mode (i.e. switched off with valid VCC module supply applied), they can be switched on as following:  Low level on the PWR_ON pin, which is normally set high by an internal pull-up, for a valid time period.  Low level on the RESET_N pin, which is normally set high by an internal pull-up, for a valid time period.  RTC alarm, i.e. pre-programmed alarm by AT+CALA command (see u-blox AT Commands Manual [3]). As described in Figure 13, the TOBY-L2 series PWR_ON input is equipped with an internal active pull-up resistor to the VCC module supply: the PWR_ON input voltage thresholds are different from the other generic digital interfaces. Detailed electrical characteristics are described in TOBY-L2 series Data Sheet [1]. Baseband Processor20PWR_ONTOBY-L2 seriesVCCPower-onPower ManagementPower-on50k Figure 13: TOBY-L2 series PWR_ON input description

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 31 of 158 Figure 14 shows the module power-on sequence from the not-powered mode, describing the following phases:  The external supply is applied to the VCC or 3.3Vaux module supply inputs, representing the start-up event.  The PWR_ON and the RESET_N or PERST# pins suddenly rise to high logic level due to internal pull-ups.  The V_BCKP RTC supply output is suddenly enabled by the module as VCC reaches a valid voltage value.  All the generic digital pins of the module are tri-stated until the switch-on of their supply source (V_INT).  The internal reset signal is held low: the baseband core and all the digital pins are held in the reset state. The reset state of all the digital pins is reported in the pin description table of TOBY-L2 Series Data Sheet [1].  When the internal reset signal is released, any digital pin is set in a proper sequence from the reset state to the default operational configured state. The duration of this pins’ configuration phase differs within generic digital interfaces and the USB interface due to host / device enumeration timings (see section 1.9.1).  The module is fully ready to operate after all interfaces are configured. VCC or 3.3VauxV_BCKPPWR_ONRESET_N or PERST#V_INTInternal ResetSystem StateBB Pads StateInternal Reset → Operational OperationalTristate / Floating Internal ResetOFFON0 ms~10 ms~20 sStart of interface configurationModule interfaces are configuredStart-up event~5 ms Figure 14: TOBY-L2 and MPCI-L2 series power-on sequence description The Internal Reset signal is not available on a module pin, but the host application can monitor:  The V_INT pin to sense the start of the TOBY-L2 module power-on sequence.  The USB interface to sense the start of the MPCI-L2 module power-on sequence: the module, as USB device, informs the host of the attach event via a reply on its status change pipe for proper bus enumeration process according to Universal Serial Bus Revision 2.0 specification [6]. Before the switch-on of the generic digital interface supply source (V_INT) of the module, no voltage driven by an external application should be applied to any generic digital interface of TOBY-L2 module. Before the TOBY-L2 and MPCI-L2 series module is fully ready to operate, the host application processor should not send any AT command over the AT communication interfaces (USB, UART) of the module.

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 32 of 158 1.6.2 Module power-off TOBY-L2 series can be properly switched off by:  AT+CPWROFF command (see u-blox AT Commands Manual [3]). The current parameter settings are saved in the module’s non-volatile memory and a proper network detach is performed. The MPCI-L2 series modules do not switch off by the AT+CPWROFF command as the TOBY-L2 modules, but the AT+CPWROFF command causes a reset (reboot) of the module due to the MPCI-L2 module’s internal configuration: the command stores the actual parameter settings in the non-volatile memory of MPCI-L2 modules and performs a network detach, with a subsequent reset (reboot) of the module. An abrupt under-voltage shutdown occurs on TOBY-L2 and MPCI-L2 series modules when the VCC or 3.3Vaux module supply is removed. If this occurs, it is not possible to perform the storing of the current parameter settings in the module’s non-volatile memory or to perform the proper network detach. It is highly recommended to avoid an abrupt removal of the VCC supply during TOBY-L2 modules normal operations: the power off procedure must be started by the AT+CPWROFF command, waiting the command response for a proper time period (see u-blox AT Commands Manual [3]), and then a proper VCC supply has to be held at least until the end of the modules’ internal power off sequence, which occurs when the generic digital interfaces supply output (V_INT) is switched off by the module. It is highly recommended to avoid an abrupt removal of the 3.3Vaux supply during MPCI-L2 modules normal operations: the power off procedure must be started by setting the MPCI-L2 module in the halt mode by the AT+CFUN=127 command (which stores the actual parameter settings in the non-volatile memory of the module and performs a network detach), waiting the command response for a proper time period (see the u-blox AT Commands Manual [3]), and then the 3.3Vaux supply can be removed. An abrupt hardware shutdown occurs on TOBY-L2 series modules when a low level is applied on the RESET_N pin for a specific time period. In this case, the current parameter settings are not saved in the module’s non-volatile memory and a proper network detach is not performed. It is highly recommended to avoid an abrupt hardware shutdown of the module by forcing a low level on the RESET_N input pin during module normal operation: the RESET_N line should be set low only if reset or shutdown via AT commands fails or if the module does not reply to a specific AT command after a time period longer than the one defined in the u-blox AT Commands Manual [3]. An over-temperature or an under-temperature shutdown occurs on TOBY-L2 and MPCI-L2 series modules when the temperature measured within the cellular module reaches the dangerous area, if the optional Smart Temperature Supervisor feature is enabled and configured by the dedicated AT command. For more details see u-blox AT Commands Manual [3], +USTS AT command. The Smart Temperature Supervisor feature is not supported by the “00”, “01”, and “50” product versions.

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 33 of 158 Figure 15 describes the TOBY-L2 power-off sequence by means of AT+CPWROFF with the following phases:  When the +CPWROFF AT command is sent, the module starts the switch-off routine.  The module replies OK on the AT interface: the switch-off routine is in progress.  At the end of the switch-off routine, all the digital pins are tri-stated and all the internal voltage regulators are turned off, including the generic digital interfaces supply (V_INT), except the RTC supply (V_BCKP).  Then, the module remains in power-off mode as long as a switch on event does not occur (e.g. applying a proper low level to the PWR_ON input, or applying a proper low level to the RESET_N input), and enters not-powered mode if the supply is removed from the VCC pins. VCC V_BCKPPWR_ONRESET_N V_INTInternal ResetSystem StateBB Pads State OperationalOFFTristate / FloatingONOperational → TristateAT+CPWROFFsent to the module0 s~2.5 s~5 sOKreplied by the moduleVCC can be removed Figure 15: TOBY-L2 series power-off sequence description The Internal Reset signal is not available on a module pin, but the application can monitor the V_INT pin to sense the end of the power-off sequence. Figure 16 describes the MPCI-L2 power-off procedure with the following phases:  When the AT+CFUN=127 command is issued, the module starts the halt mode setting routine.  The module replies OK on the AT interface: after this, the module is set in the halt mode.  Then, the module remains in the Halt mode and enters not-powered mode if the supply is removed from the 3.3Vaux pins. 3.3VauxPERST#Internal ResetSystem StateBB Pads StateOFFONTristate / FloatingOperationalAT+CFUN=127sent to the module0 s~2.5 s~5 sOKreplied by the module3.3Vaux can be removed Figure 16: MPCI-L2 series power-off procedure description The duration of each phase in the TOBY-L2 and MPCI-L2 series modules’ switch-off routines can largely vary depending on the application / network settings and the concurrent module activities.

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 34 of 158 1.6.3 Module reset TOBY-L2 and MPCI-L2 series modules can be properly reset (rebooted) by:  AT+CFUN command (see u-blox AT Commands Manual [3]). MPCI-L2 series modules can be additionally properly reset (rebooted) by:  AT+CPWROFF command (see u-blox AT Commands Manual [3]): the behavior differs than TOBY-L2 series, as MPCI-L2 modules will reboot rather than remain switched off due to modules’ internal configuration. In the cases listed above an “internal” or “software” reset of the module is executed: the current parameter settings are saved in the module’s non-volatile memory and a proper network detach is performed. An abrupt hardware reset occurs on TOBY-L2 and MPCI-L2 series modules when a low level is applied on the RESET_N or PERST# input pin for a specific time period. In this case, the current parameter settings are not saved in the module’s non-volatile memory and a proper network detach is not performed. It is highly recommended to avoid an abrupt hardware reset of the module by forcing a low level on the RESET_N or PERST# input during modules normal operation: the RESET_N or PERST# line should be set low only if reset or shutdown via AT commands fails or if the module does not provide a reply to a specific AT command after a time period longer than the one defined in the u-blox AT Commands Manual [3]. As described in Figure 17, the RESET_N and PERST# input pins are equipped with an internal pull-up to the VCC supply in the TOBY-L2 series and to the 3.3 V in the MPCI-L2 series. Baseband Processor23RESET_NTOBY-L2 seriesVCCResetPower ManagementReset50kBaseband Processor22PERST#MPCI-L2 seriesResetPower ManagementReset45k3.3 V Figure 17: TOBY-L2 and MPCI-L2 series RESET_N and PERST# input equivalent circuit description For more electrical characteristics details see TOBY-L2 Data Sheet [1] and MPCI-L2 Data Sheet [2]. 1.6.4 Module configuration selection by host processor The HOST_SELECT0 and HOST_SELECT1 pins are not available on MPCI-L2 series modules. The selection of the module configuration by the host application processor over the HOST_SELECT0 and HOST_SELECT1 pins is not supported by TOBY-L2 “00”, “01”, and “50” product versions. TOBY-L2 series modules include two input pins (HOST_SELECT0 and HOST_SELECT1) for the selection of the module configuration by the host application processor.

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 35 of 158 1.7 Antenna interface 1.7.1 Antenna RF interfaces (ANT1 / ANT2) TOBY-L2 and MPCI-L2 series modules provide two RF interfaces for connecting the external antennas:  The ANT1 represents the primary RF input/output for transmission and reception of LTE/3G/2G RF signals. The ANT1 pin of TOBY-L2 series modules has a nominal characteristic impedance of 50  and must be connected to the primary Tx / Rx antenna through a 50  transmission line to allow proper RF transmission and reception. The ANT1 Hirose U.FL-R-SMT coaxial connector receptacle of MPCI-L2 series modules has a nominal characteristic impedance of 50  and must be connected to the primary Tx / Rx antenna through a mated RF plug with a 50  coaxial cable assembly to allow proper RF transmission and reception.  The ANT2 represents the secondary RF input for the reception of the LTE RF signals for the Down-Link MIMO 2 x 2 radio technology supported by TOBY-L2 and MPCI-L2 series modules as required feature for LTE category 4 UEs, and for the reception of the 3G RF signals for the Down-Link Rx diversity radio technology supported by TOBY-L2 and MPCI-L2 series modules as additional feature for 3G DC-HSDPA category 24 UEs. The ANT2 pin of TOBY-L2 series modules has a nominal characteristic impedance of 50  and must be connected to the secondary Rx antenna through a 50  transmission line to allow proper RF reception. The ANT2 Hirose U.FL-R-SMT coaxial connector receptacle of MPCI-L2 series modules has a nominal characteristic impedance of 50  and must be connected to the secondary Rx antenna through a mated RF plug with a 50  coaxial cable assembly to allow proper RF reception. The Multiple Input Multiple Output (MIMO) radio technology is an essential component of LTE radio systems based on the use of multiple antennas at both the transmitter and receiver sides to improve communication performance and achieve highest possible bit rate. A MIMO m x n system consists of m transmit and n receive antennas, where the data to be transmitted is divided into m independent data streams. Note that the terms Input and Output refer to the radio channel carrying the signal, not to the devices having antennas, so that in the Down-Link MIMO 2 x 2 system supported by TOBY-L2 and MPCI-L2 series modules:  The LTE data stream is divided into 2 independent streams by the Tx-antennas of the base station  The cellular modules, at the receiver side, receives both LTE data streams by 2 Rx-antennas (ANT1 / ANT2) Base StationTx-1 AntennaTx-2 AntennaTOBY-L2 seriesMPCI-L2 seriesANT1Rx-1 AntennaANT2Rx-2 AntennaData Stream 1Data Stream 2 Figure 18: Description of the LTE Down-Link MIMO 2 x 2 radio technology supported by TOBY-L2 and MPCI-L2 series modules TOBY-L2 and MPCI-L2 series modules support the LTE MIMO 2 x 2 radio technology in the Down-Link path only (from the base station to the module): the ANT1 port is the only one RF interface that is used by the module to transmit the RF signal in the Up-Link path (from the module to the base station).

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 36 of 158 1.7.1.1 Antenna RF interfaces requirements Table 8, Table 9 and Table 10 summarize the requirements for the antennas RF interfaces (ANT1 / ANT2). See section 2.4.1 for suggestions to properly design antennas circuits compliant with these requirements. The antenna circuits affect the RF compliance of the device integrating TOBY-L2 and MPCI-L2 series modules with applicable required certification schemes (for more details see section 4). Compliance is guaranteed if the antenna RF interfaces (ANT1 / ANT2) requirements summarized in Table 8, Table 9 and Table 10 are fulfilled. Item Requirements Remarks Impedance 50  nominal characteristic impedance The impedance of the antenna RF connection must match the 50  impedance of the ANT1 port. Frequency Range See the TOBY-L2 series Data Sheet [1] and the MPCI-L2 series Data Sheet [2] The required frequency range of the antenna connected to ANT1 port depends on the operating bands of the used cellular module and the used mobile network. Return Loss S11 < -10 dB (VSWR < 2:1) recommended S11 < -6 dB (VSWR < 3:1) acceptable The Return loss or the S11, as the VSWR, refers to the amount of reflected power, measuring how well the primary antenna RF connection matches the 50  characteristic impedance of the ANT1 port. The impedance of the antenna termination must match as much as possible the 50  nominal impedance of the ANT1 port over the operating frequency range, reducing as much as possible the amount of reflected power. Efficiency > -1.5 dB ( > 70% ) recommended > -3.0 dB ( > 50% ) acceptable The radiation efficiency is the ratio of the radiated power to the power delivered to antenna input: the efficiency is a measure of how well an antenna receives or transmits. The radiation efficiency of the antenna connected to the ANT1 port needs to be enough high over the operating frequency range to comply with the Over-The-Air (OTA) radiated performance requirements, as Total Radiated Power (TRP) and the Total Isotropic Sensitivity (TIS), specified by applicable related certification schemes. Maximum Gain According to radiation exposure limits The power gain of an antenna is the radiation efficiency multiplied by the directivity: the gain describes how much power is transmitted in the direction of peak radiation to that of an isotropic source. The maximum gain of the antenna connected to ANT1 port must not exceed the herein stated value to comply with regulatory agencies radiation exposure limits. For additional info see the section 4.2.2. Input Power > 33 dBm ( > 2 W ) The antenna connected to the ANT1 port must support with adequate margin the maximum power transmitted by the modules. Table 8: Summary of primary Tx/Rx antenna RF interface (ANT1) requirements

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 37 of 158 Item Requirements Remarks Impedance 50  nominal characteristic impedance The impedance of the antenna RF connection must match the 50  impedance of the ANT2 port. Frequency Range See the TOBY-L2 series Data Sheet [1] and the MPCI-L2 series Data Sheet [2] The required frequency range of the antennas connected to ANT2 port depends on the operating bands of the used cellular module and the used Mobile Network. Return Loss S11 < -10 dB (VSWR < 2:1) recommended S11 < -6 dB (VSWR < 3:1) acceptable The Return loss or the S11, as the VSWR, refers to the amount of reflected power, measuring how well the secondary antenna RF connection matches the 50  characteristic impedance of the ANT2 port. The impedance of the antenna termination must match as much as possible the 50  nominal impedance of the ANT2 port over the operating frequency range, reducing as much as possible the amount of reflected power. Efficiency > -1.5 dB ( > 70% ) recommended > -3.0 dB ( > 50% ) acceptable The radiation efficiency is the ratio of the radiated power to the power delivered to antenna input: the efficiency is a measure of how well an antenna receives or transmits. The radiation efficiency of the antenna connected to the ANT2 port needs to be enough high over the operating frequency range to comply with the Over-The-Air (OTA) radiated performance requirements, as the TIS, specified by applicable related certification schemes. Table 9: Summary of secondary Rx antenna RF interface (ANT2) requirements Item Requirements Remarks Efficiency imbalance < 0.5 dB recommended < 1.0 dB acceptable The radiation efficiency imbalance is the ratio of the primary (ANT1) antenna efficiency to the secondary (ANT2) antenna efficiency: the efficiency imbalance is a measure of how much better an antenna receives or transmits compared to the other antenna. The radiation efficiency of the secondary antenna needs to be roughly the same of the radiation efficiency of the primary antenna for good RF performance. Envelope Correlation Coefficient < 0.4 recommended < 0.5 acceptable The Envelope Correlation Coefficient (ECC) between the primary (ANT1) and the secondary (ANT2) antenna is an indicator of 3D radiation pattern similarity between the two antennas: low ECC results from antenna patterns with radiation lobes in different directions. The ECC between primary and secondary antenna needs to be enough low to comply with radiated performance requirements specified by related certification schemes. Isolation > 15 dB recommended > 10 dB acceptable The antenna to antenna isolation is the loss between the primary (ANT1) and the secondary (ANT2) antenna: high isolation results from low coupled antennas. The isolation between primary and secondary antenna needs to be high for good RF performance. Table 10: Summary of primary (ANT1) and secondary (ANT2) antennas relationship requirements

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 38 of 158 1.7.2 Antenna detection interface (ANT_DET) Antenna detection (ANT_DET) is not available on MPCI-L2 series modules. Antenna detection (ANT_DET) is not supported by TOBY-L2 “00”, “01”, and “50” product versions. The antenna detection is based on ADC measurement. The ANT_DET pin is an Analog to Digital Converter (ADC) provided to sense the antenna presence. The antenna detection function provided by ANT_DET pin is an optional feature that can be implemented if the application requires it. The antenna detection is forced by the +UANTR AT command. See the u-blox AT Commands Manual [3] for more details on this feature. The ANT_DET pin generates a DC current (for detailed characteristics see the TOBY-L2 series Data Sheet [1]) and measures the resulting DC voltage, thus determining the resistance from the antenna connector provided on the application board to GND. So, the requirements to achieve antenna detection functionality are the following:  an RF antenna assembly with a built-in resistor (diagnostic circuit) must be used  an antenna detection circuit must be implemented on the application board See section 2.4.2 for antenna detection circuit on application board and diagnostic circuit on antenna assembly design-in guidelines. 1.8 SIM interface 1.8.1 SIM interface TOBY-L2 and MPCI-L2 series modules provide high-speed SIM/ME interface including automatic detection and configuration of the voltage required by the connected SIM card or chip. Both 1.8 V and 3 V SIM types are supported. Activation and deactivation with automatic voltage switch from 1.8 V to 3 V are implemented, according to ISO-IEC 7816-3 specifications. The VSIM or UIM_PWR supply output provides internal short circuit protection to limit start-up current and protect the SIM to short circuits. The SIM driver supports the PPS (Protocol and Parameter Selection) procedure for baud-rate selection, according to the values determined by the SIM card or chip. 1.8.2 SIM detection interface SIM detection (GPIO5) is not available on MPCI-L2 series modules. SIM detection (GPIO5) is not supported by TOBY-L2 “00”, “01”, and “50” product versions. The GPIO5 pin is by default configured to detect the SIM card mechanical / physical presence. The pin is configured as input with an internal active pull-down enabled, and it can sense SIM card presence only if properly connected to the mechanical switch of a SIM card holder as described in section 2.5:  Low logic level at GPIO5 input pin is recognized as SIM card not present  High logic level at GPIO5 input pin is recognized as SIM card present The SIM card detection function provided by GPIO5 pin is an optional feature that can be implemented / used or not according to the application requirements: an Unsolicited Result Code (URC) is generated each time that there is a change of status (for more details see the u-blox AT Commands Manual [3]). The optional function “SIM card hot insertion/removal” can be additionally enabled on the GPIO5 pin by specific AT command (see the u-blox AT Commands Manual [3]).

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 39 of 158 1.9 Data communication interfaces TOBY-L2 and MPCI-L2 series modules provide the following serial communication interface:  USB interface: High-Speed USB 2.0 compliant interface available for the communication with an external host application processor, for AT commands, data communication, FW upgrade by means of the FOAT feature, FW upgrade by means of the u-blox EasyFlash tool and for diagnostic purpose (see section 1.9.1 for functional description) TOBY-L2 series modules additionally provide the following serial communication interfaces:  UART interface: asynchronous serial interface available for the communication with an external host application processor, for AT commands, data communication, FW upgrade by means of the FOAT feature (see section 1.9.2 for functional description)  DDC interface: I2C bus compatible interface available for the communication with u-blox GNSS positioning chips/modules and with external I2C devices as an audio codec (see section 1.9.3 for functional description)  SDIO interface: Secure Digital Input Output interface available for the communication with an external Wi-Fi chip or module (see section 1.9.4 for functional description) 1.9.1 Universal Serial Bus (USB) 1.9.1.1 USB features TOBY-L2 and MPCI-L2 series modules include a High-Speed USB 2.0 compliant interface with maximum data rate of 480 Mb/s, representing the main interface for transferring high speed data with a host application processor: the USB interface is available for AT commands, data communication, FW upgrade by means of the FOAT feature, FW upgrade by means of the u-blox EasyFlash tool and for diagnostic purpose. The module itself acts as a USB device and can be connected to a USB host such as a Personal Computer or an embedded application microprocessor equipped with compatible drivers. The USB_D+ / USB_D- lines carry the USB serial bus data and signaling, providing all the functionalities for the bus attachment, configuration, enumeration, suspension or remote wakeup according to the Universal Serial Bus Revision 2.0 specification [6] The additional VUSB_DET input is available as an optional feature to sense the host VBUS voltage (5.0 V typical). The VUSB_DET functionality is not supported by TOBY-L2 “00”, “01”, and “50” product versions: the pin should be left unconnected or it should not be driven high by any external device, because a high logic level applied to the pin will represent a module switch-on event (additional to the ones listed in section 1.6.1) and will prevent reaching the minimum possible consumption with power saving enabled. The VUSB_DET pin is not available on MPCI-L2 series modules. The USB interface is controlled and operated with:  AT commands according to 3GPP TS 27.007 [8], 3GPP TS 27.005 [9], 3GPP TS 27.010 [10]  u-blox AT commands For the complete list of supported AT commands and their syntax see u-blox AT Commands Manual [3].

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 42 of 158 1.9.1.2 USB in Windows The USB drivers (INF files) are provided for Windows systems and should be installed properly by following the step-by-step instruction in EVK-L20 / EVK-L21 User Guide [4]. USB drivers are available for the following operating system platforms:  Windows Vista  Windows 7  Windows 8  Windows 8.1  Windows Embedded Compact 7 The module firmware can be upgraded over the USB interface by means of the FOAT feature, or using the u-blox EasyFlash tool (for more details see Firmware Update Application Note [4]). 1.9.1.3 USB in Linux/Android It is not required to install a specific driver for each Linux-based or Android-based operating system (OS) to use the module USB interface, which is compatible with standard Linux/Android USB kernel drivers. The full capability and configuration of the module USB interface can be reported by running “lsusb –v” or an equivalent command available in the host operating system when the module is connected. 1.9.1.4 USB and power saving The modules automatically enter the USB suspended state when the device has observed no bus traffic for a specific time period according to the USB 2.0 specification [6]. In suspended state, the module maintains any USB internal status as device. In addition, the module enters the suspended state when the hub port it is attached to is disabled. This is referred to as USB selective suspend. If the USB is suspended and a power saving configuration is enabled by the AT+UPSV command, the module automatically enters the low power idle-mode whenever possible but it wakes up to active-mode according to any required activity related to the network (e.g. the periodic paging reception described in section 1.5.1.5) or any other required activity related to the functions / interfaces of the module. The USB exits suspend mode when there is bus activity. If the USB is connected and not suspended, the module is forced to stay in active-mode, therefore the AT+UPSV settings are overruled but they have effect on the power saving configuration of the other interfaces. The modules are capable of USB remote wake-up signaling: i.e. it may request the host to exit suspend mode or selective suspend by using electrical signaling to indicate remote wake-up, for example due to incoming call, URCs, data reception on a socket. The remote wake-up signaling notifies the host that it should resume from its suspended mode, if necessary, and service the external event. Remote wake-up is accomplished using electrical signaling described in the USB 2.0 specifications [6]. For the module current consumption description with power saving enabled and USB suspended, or with power saving disabled and USB not suspended, see the sections 1.5.1.5, 1.5.1.6 and the TOBY-L2 Data Sheet [1] or the MPCI-L2 Data Sheet [2].

$TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 43 of 158 1.9.2 Asynchronous serial interface (UART) The UART interface is not available on MPCI-L2 series modules. The UART interface is not supported by TOBY-L200-00S and TOBY-L210-00S modules versions. The DTR, DSR and DCD signals are not supported by TOBY-L200-50S, TOBY-L210-50S modules versions. 1.9.2.1 UART features The UART interface is a 9-wire 1.8 V unbalanced asynchronous serial interface (UART) that can be connected to an application host processor for AT commands and data communication. The module firmware can be upgraded over the UART interface by means of the Firmware upgrade over AT (FOAT) feature only: for more details see section 1.15 and Firmware update application note [4]. UART interface provides RS-232 functionality conforming to the ITU-T V.24 Recommendation [7], with CMOS compatible signal levels: 0 V for low data bit or ON state, and 1.8 V for high data bit or OFF state (for detailed electrical characteristics see TOBY-L2 Data Sheet [1]), providing:  data lines (RXD as output, TXD as input),  hardware flow control lines (CTS as output, RTS as input),  modem status and control lines (DTR as input, DSR as output, DCD as output, RI as output). TOBY-L2 modules are designed to operate as LTE/3G/2G cellular modems, i.e. as the data circuit-terminating equipment (DCE) according to the ITU-T V.24 Recommendation [7]. A host application processor connected to the module through the UART interface represents the data terminal equipment (DTE). UART signal names of TOBY-L2 modules conform to the ITU-T V.24 Recommendation [7]: e.g. TXD line represents data transmitted by the DTE (host processor output) and received by the DCE (module input). The UART interface is controlled and operated with:  AT commands according to 3GPP TS 27.007 [8], 3GPP TS 27.005 [9], 3GPP TS 27.010 [10]  u-blox AT commands For the complete list of supported AT commands and their syntax see u-blox AT Commands Manual [3], and in particular for the UART configuration see the +IPR, +ICF, +IFC, &K, \Q, +UPSV AT commands. Flow control handshakes are supported by the UART interface and can be set by appropriate AT commands (see u-blox AT Commands Manual [3], &K, +IFC, \Q AT commands): hardware flow control (over the RTS / CTS lines), software flow control (XON/XOFF), or none flow control. Hardware flow control is enabled by default. Software flow control is not supported by “00”, “01” and “50” module product versions. The one-shot autobauding is supported: the automatic baud rate detection is performed only once, at module start up. After the detection, the module works at the detected baud rate and the baud rate can only be changed by AT command (see u-blox AT Commands Manual [3], +IPR). One-shot automatic baud rate recognition (autobauding) is enabled by default. The automatic baud rate recognition (autobauding) is not supported by “50” product version.$

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 44 of 158 The following baud rates can be configured by AT command (see u-blox AT Commands Manual [3], +IPR):  9600 b/s  19200 b/s  38400 b/s  57600 b/s  115200 b/s, default value for “50” modules product version or when one-shot autobauding is disabled  230400 b/s  460800 b/s  921600 b/s The following frame formats can be configured by AT command (see u-blox AT Commands Manual [3], +ICF):  8N2 (8 data bits, no parity, 2 stop bits)  8N1 (8 data bits, no parity, 1 stop bit), default frame format  8E1 (8 data bits, even parity, 1 stop bit)  8O1 (8 data bits, odd parity, 1 stop bit)  7N2 (7 data bits, no parity, 2 stop bits)  7N1 (7 data bits, no parity, 1 stop bit)  7E1 (7 data bits, even parity, 1 stop bit)  7O1 (7 data bits, odd parity, 1 stop bit) Automatic frame format recognition is not supported by “00”, “01” and “50” module product versions. Figure 20 describes the 8N1 frame format, which is the default frame format configuration. D0 D1 D2 D3 D4 D5 D6 D7Start of 1-BytetransferStart Bit(Always 0)Possible Start ofnext transferStop Bit(Always 1)tbit = 1/(Baudrate)Normal Transfer, 8N1 Figure 20: Description of UART default frame format (8N1, i.e. 8 data bits, no parity, 1 stop bit)

$TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 46 of 158 CTS signal behavior The module hardware flow control output (CTS line) is set to the ON state (low level) at UART initialization. If the hardware flow control is enabled, as it is by default, the CTS line indicates when the UART interface is enabled (data can be sent and received). The module drives the CTS line to the ON state or to the OFF state when it is either able or not able to accept data from the DTE over the UART interface (for more details see section 1.9.2.4 and in particular Figure 22). If hardware flow control is enabled, then when the CTS line is OFF it does not necessarily mean that the module is in low power idle-mode, but only that the UART is not enabled, as the module could be forced to stay in active-mode for other activities, e.g. related to the network or related to other interfaces. If hardware flow control is enabled and the multiplexer protocol is active, then the CTS line state is mapped to FCon / FCoff MUX command for flow control matters outside the power saving configuration while the physical CTS line is still used as a UART power state indicator. For more details, see the Mux Implementation Application Note [11]. The CTS hardware flow control setting can be changed by AT commands (for more details, see the u-blox AT Commands Manual [3], AT&K, AT\Q, AT+IFC AT commands). If the hardware flow control is not enabled, the CTS line still indicates when the UART interface is enabled, as it does when hardware flow control is enabled. The module drives the CTS line to the ON state or to the OFF state when it is either able or not able to accept data from the DTE over the UART interface, as described in Figure 22. When the power saving configuration is enabled by AT+UPSV command and the hardware flow-control is not implemented in the DTE/DCE connection, data sent by the DTE can be lost: the first character sent when the module is in low power idle-mode will not be a valid communication character (see section 1.9.2.4 and in particular the sub-section “Wake up via data reception” for further details). RTS signal behavior The hardware flow control input (RTS line) is set by default to the OFF state (high level) at UART initialization. The module then holds the RTS line in the OFF state if the line is not activated by the DTE: an active pull-up is enabled inside the module on the RTS input. If the HW flow control is enabled, as it is by default, the module monitors the RTS line to detect permission from the DTE to send data to the DTE itself. If the RTS line is set to the OFF state, any on-going data transmission from the module is interrupted until the RTS line changes to the ON state. The DTE must still be able to accept a certain number of characters after the RTS line is set to the OFF state: the module guarantees the transmission interruption within two characters from RTS state change. The module behavior according to the RTS hardware flow control status can be configured by AT commands (for more details, see the u-blox AT Commands Manual [3], AT&K, AT\Q, AT+IFC AT commands). If AT+UPSV=2 is set and HW flow control is disabled, the module monitors the RTS line to manage the power saving configuration (for more details, see section 1.9.2.4 and u-blox AT Commands Manual [3], AT+UPSV):  When an OFF-to-ON transition occurs on the RTS input, the UART is enabled and the module is forced to active-mode; after ~5 ms from the transition the switch is completed and data can be received without loss. The module cannot enter low power idle-mode and the UART is keep enabled as long as the RTS input line is held in the ON state  If the RTS input line is set to the OFF state by the DTE, the UART is disabled (held in low power mode) and the module automatically enters low power idle-mode whenever possible$

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 47 of 158 DSR signal behavior If AT&S1 is set, as it is by default, the DSR module output line is set by default to the OFF state (high level) at UART initialization. The DSR line is then set to the OFF state when the module is in command mode6 or in online command mode6 and is set to the ON state when the module is in data mode6. If AT&S0 is set, the DSR module output line is set by default to the ON state (low level) at UART initialization and is then always held in the ON state. DTR signal behavior The DTR module input line is set by default to the OFF state (high level) at UART initialization. The module then holds the DTR line in the OFF state if the line is not activated by the DTE: an active pull-up is enabled inside the module on the DTR input. Module behavior according to DTR status can be changed by AT command configuration (for more details see the u-blox AT Commands Manual [3], &D AT command description). If AT+UPSV=3 is set, the DTR line is monitored by the module to manage the power saving configuration (for more details, see section 1.9.2.4 and u-blox AT Commands Manual [3], AT+UPSV):  When an OFF-to-ON transition occurs on the DTR input, the UART is enabled and the module is forced to active-mode; after ~5 ms from the transition, the switch is completed and data can be received without loss. The module cannot enter low power idle-mode and the UART is keep enabled as long as the DTR input line is held in the ON state  If the DTR input line is set to the OFF state by the DTE, the UART is disabled (held in low power mode) and the module automatically enters low power idle-mode whenever possible DCD signal behavior If AT&C1 is set, as it is by default, the DCD module output line is set by default to the OFF state (high level) at UART initialization. The module then sets the DCD line according to the carrier detect status: ON if the carrier is detected, OFF otherwise. If a Packet Switched Data call occurs before activating the PPP protocol (data mode), a dial-up application must provide the ATD*99***<context_number># to the module: with this command the module switches from command mode6 to data mode6 and can accept PPP packets. The module sets the DCD line to the ON state, then answers with a CONNECT to confirm the ATD*99 command. The DCD ON is not related to the context activation but with the data mode. The DCD is set to ON during the execution of the +CMGS, +CMGW, +USOWR, +USODL AT commands requiring input data from the DTE: the DCD line is set to the ON state as soon as the switch to binary/text input mode is completed and the prompt is issued; DCD line is set to OFF as soon as the input mode is interrupted or completed (for more details see the u-blox AT Commands Manual [3]). The DCD line is kept in the ON state, even during the online command mode6, to indicate that the data call is still established even if suspended, while if the module enters command mode6, the DSR line is set to the OFF state. For more details see DSR signal behavior description. For scenarios when the DCD line setting is requested for different reasons (e.g. SMS texting during online command mode6), the DCD line changes to guarantee the correct behavior for all the scenarios. For example, in case of SMS texting in online command mode6, if the data call is released, DCD is kept ON till the SMS command execution is completed (even if the data call release would request DCD set OFF). If AT&C0 is set, the DCD module output line is set by default to the ON state (low level) at UART initialization and is then always held in the ON state. 6 For the definition of the interface data mode, command mode and online command mode see the u-blox AT Commands Manual [3]

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 48 of 158 RI signal behavior The RI module output line is set by default to the OFF state (high level) at UART initialization. The RI output line can notify an SMS arrival. When the SMS arrives, the RI line switches from OFF to ON for 1 s (see Figure 21), if the feature is enabled by the proper AT command (see the u-blox AT Commands Manual [3], AT+CNMI command). Figure 21: RI behavior at SMS arrival This behavior allows the DTE to stay in power saving mode until the DCE related event requests service. For SMS arrival, if several events coincidently occur or in quick succession each event independently triggers the RI line, although the line will not be deactivated between each event. As a result, the RI line may stay to ON for more than 1 s, so that: RI line monitoring cannot be used by the DTE to determine the number of received SMSes. For multiple events, the RI line cannot be used to discriminate the two events, but the DTE must rely on the subsequent URCs and interrogate the DCE with the proper commands. 1.9.2.4 UART and power-saving The power saving configuration is controlled by the AT+UPSV command (for the complete description, see the u-blox AT Commands Manual [3]). When power saving is enabled, the module automatically enters low power idle-mode whenever possible, and otherwise the active-mode is maintained by the module (see section 1.4 for definition and description of module operating modes referred to in this section). The AT+UPSV command configures both the module power saving and also the UART behavior in relation to the power saving. The conditions for the module entering low power idle-mode also depend on the UART power saving configuration, as the module does not enter the low power idle-mode according to any required activity related to the network (within or outside an active call) or any other required concurrent activity related to the functions and interfaces of the module, including the UART interface. The AT+UPSV command can set these different power saving configurations:  AT+UPSV=0, power saving disabled (default configuration)  AT+UPSV=1, power saving enabled cyclically  AT+UPSV=2, power saving enabled and controlled by the UART RTS input line  AT+UPSV=3, power saving enabled and controlled by the UART DTR input line The different power saving configurations that can be set by the +UPSV AT command are described in details in the following subsections. Table 12 summarizes the UART interface communication process in the different power saving configurations, in relation with the hardware flow control settings and the RTS input line status. For more details on the +UPSV AT command description, see u-blox AT commands Manual [3]. SMS arrives time [s] 0 RI ON RI OFF 1s time [s] 0 RI ON RI OFF 1s

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 49 of 158 AT+UPSV HW flow control RTS line DTR line Communication during idle-mode and wake up 0 Enabled (AT&K3) ON ON or OFF Data sent by the DTE is correctly received by the module. Data sent by the module is correctly received by the DTE. 0 Enabled (AT&K3) OFF ON or OFF Data sent by the DTE is correctly received by the module. Data sent by the module is buffered by the module and will be correctly received by the DTE when it is ready to receive data (i.e. RTS line will be ON). 0 Disabled (AT&K0) ON or OFF ON or OFF Data sent by the DTE is correctly received by the module. Data sent by the module is correctly received by the DTE if it is ready to receive data, otherwise the data is lost. 1 Enabled (AT&K3) ON ON or OFF Data sent by the DTE is buffered by the DTE and will be correctly received by the module when it is ready to receive data (when the UART is enabled). Data sent by the module is correctly received by the DTE. 1 Enabled (AT&K3) OFF ON or OFF Data sent by the DTE is buffered by the DTE and will be correctly received by the module when it is ready to receive data (when the UART is enabled). Data sent by the module is buffered by the module and will be correctly received by the DTE when it is ready to receive data (i.e. RTS line will be ON). 1 Disabled (AT&K0) ON or OFF ON or OFF The first character sent by the DTE is lost by the module, but after ~5 ms the UART and the module are woken up: recognition of subsequent characters is guaranteed only after the UART / module complete wake-up (i.e. after ~5 ms). Data sent by the module is correctly received by the DTE if it is ready to receive data, otherwise the data is lost. 2 Enabled (AT&K3) ON or OFF ON or OFF Not Applicable: HW flow control cannot be enabled with AT+UPSV=2. 2 Disabled (AT&K0) ON ON or OFF Data sent by the DTE is correctly received by the module. Data sent by the module is correctly received by the DTE if it is ready to receive data, otherwise data is lost. 2 Disabled (AT&K0) OFF ON or OFF The first character sent by the DTE is lost by the module, but after ~5 ms the UART and the module are woken up. Recognition of subsequent characters is guaranteed only after the UART / module complete wake-up (i.e. after ~5 ms). Data sent by the module is correctly received by the DTE if it is ready to receive data, otherwise data is lost. 3 Enabled (AT&K3) ON ON Data sent by the DTE is correctly received by the module. Data sent by the module is correctly received by the DTE. 3 Enabled (AT&K3) ON OFF Data sent by the DTE is buffered by the DTE and will be correctly received by the module when it is ready to receive data (when the UART is enabled). Data sent by the module is correctly received by the DTE. 3 Enabled (AT&K3) OFF ON Data sent by the DTE is correctly received by the module. Data sent by the module is buffered by the module and will be correctly received by the DTE when it is ready to receive data (i.e. RTS line will be ON). 3 Enabled (AT&K3) OFF OFF Data sent by the DTE is buffered by the DTE and will be correctly received by the module when it is ready to receive data (when the UART is enabled). Data sent by the module is buffered by the module and will be correctly received by the DTE when it is ready to receive data (i.e. RTS line will be ON). 3 Disabled (AT&K0) ON or OFF ON Data sent by the DTE is correctly received by the module. Data sent by the module is correctly received by the DTE if it is ready to receive data, otherwise data is lost. 3 Disabled (AT&K0) ON or OFF OFF The first character sent by the DTE is lost by the module, but after ~5 ms the UART and the module are woken up. Recognition of subsequent characters is guaranteed only after the UART / module complete wake-up (i.e. after ~5 ms). Data sent by the module is correctly received by the DTE if it is ready to receive data, otherwise data is lost. Table 12: UART and power-saving summary

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 50 of 158 AT+UPSV=0: power saving disabled, fixed active-mode The module does not enter low power idle-mode and the UART interface is enabled (data can be sent and received): the CTS line is always held in the ON state after UART initialization. This is the default configuration. AT+UPSV=1: power saving enabled, cyclic idle/active-mode When the AT+UPSV=1 command is issued by the DTE, then the UART is immediately disabled by the module. Afterwards, the UART is enabled again, and the module does not enter low power idle-mode, as following:  Periodically, during each paging reception (see section 1.5.1.5), to temporarily receive or send data over the UART, e.g. data buffered by the DTE with HW flow control enabled will be correctly received by the module  If the module needs to transmit some data over the UART (e.g. URC), the UART is temporarily enabled  If a data call with external context is activated, the UART is kept enabled  If the DTE send data with HW flow control disabled, the first character sent causes the UART and module wake-up after ~5 ms: recognition of subsequent characters is guaranteed only after the complete wake-up (see the following subsection “wake up via data reception”) The module automatically enters the low power idle-mode whenever possible but it wakes up to active-mode according to the UART periodic wake up so that the module cyclically enters the low power idle-mode and the active-mode. Additionally, the module wakes up to active-mode according to any required activity related to the network (e.g. for the periodic paging reception described in section 1.5.1.5, or for any other required RF Tx / Rx) or any other required activity related to module functions / interfaces (including the UART itself). When the UART interface is enabled, data can be received. When a character is received, it forces the UART interface to stay enabled for a longer time and it forces the module to stay in the active-mode for a longer time, according to the timeout configured by the second parameter of the +UPSV AT command. The timeout can be set from 40 2G-frames (i.e. 40 x 4.615 ms = 184 ms) up to 65000 2G-frames (i.e. 65000 x 4.615 ms = 300 s). Default value is 2000 2G-frames (i.e. 2000 x 4.615 ms = 9.2 s). Every subsequent character received during the active-mode, resets and restarts the timer; hence the active-mode duration can be extended indefinitely. The hardware flow-control output (CTS line) indicates when the UART interface is enabled (data can be sent and received), as illustrated in Figure 22. time [s]UART disabled~ 20 msUART enabled~9.2 s (default)UART enabledData inputCTS ONCTS OFF2G: 0.45-2.10 s 3G: 0.62-5.10 s LTE: 0.30-2.52 s Figure 22: CTS output pin indicates when module’s UART is enabled (CTS = ON = low level) or disabled (CTS = OFF = high level)

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 51 of 158 AT+UPSV=2: power saving enabled and controlled by the RTS line This configuration can only be enabled with the module hardware flow control disabled (i.e. AT&K0 setting). The UART interface is immediately disabled after the DTE sets the RTS line to OFF. Afterwards, the UART is enabled again, and the module does not enter low power idle-mode, as following:  If an OFF-to-ON transition occurs on the RTS input line, this causes the UART / module wake-up after ~5 ms: recognition of subsequent characters is guaranteed only after the complete wake-up, and the UART is kept enabled as long as the RTS input line is set to ON.  If the module needs to transmit some data over the UART (e.g. URC)  If a data call with external context is activated  If the DTE sends data, the first character sent causes the UART and module wake-up after ~5 ms: the recognition of subsequent characters is guaranteed only after the complete wake-up, and the UART will be then kept enabled after the last data received according to the timeout previously set with the AT+UPSV=1 configuration (see the following subsection “wake up via data reception”) The module automatically enters the low power idle-mode whenever possible but it wakes up to active-mode according to any required activity related to the network (e.g. for the periodic paging reception described in section 1.5.1.5, or for any other required RF transmission / reception) or any other required activity related to the module functions / interfaces (including the UART itself). The hardware flow-control output (CTS line) indicates when the UART interface is enabled (data can be sent and received) as illustrated in Figure 22, even if hardware flow control is disabled with AT+UPSV=2 configuration. AT+UPSV=3: power saving enabled and controlled by the DTR line The UART interface is immediately disabled after the DTE sets the DTR line to OFF. Afterwards, the UART is enabled again, and the module does not enter low power idle-mode, as following:  If an OFF-to-ON transition occurs on the DTR input line, this causes the UART / module wake-up after ~5 ms: recognition of subsequent characters is guaranteed only after the complete wake-up, and the UART is kept enabled as long as the DTR input line is set to ON  If the module needs to transmit some data over the UART (e.g. URC)  If a data call with external context is activated  If the DTE sends data, the first character sent causes the UART and module wake-up after ~5 ms: recognition of subsequent characters is guaranteed only after the complete wake-up, and the UART will be then kept enabled after the last data received according to the timeout previously set with the AT+UPSV=1 configuration (see the following subsection “wake up via data reception”) The module automatically enters the low power idle-mode whenever possible but it wakes up to active-mode according to any required activity related to the network (e.g. for the periodic paging reception described in section 1.5.1.5, or for any other required RF signal transmission or reception) or any other required activity related to the functions / interfaces of the module. The AT+UPSV=3 configuration can be enabled regardless the flow control setting on UART. In particular, the HW flow control can be enabled (AT&K3) or disabled (AT&K0) on UART during this configuration. In both cases, the CTS line indicates the UART power saving state as illustrated in Figure 22. When the AT+UPSV=3 configuration is enabled, the DTR input line can still be used by the DTE to control the module behavior according to AT&D command configuration (see u-blox AT commands Manual [3]).

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 52 of 158 Wake up via data reception The UART wake up via data reception consists of a special configuration of the module TXD input line that causes the system wake-up when a low-to-high transition occurs on the TXD input line. In particular, the UART is enabled and the module switches from the low power idle-mode to active-mode within ~5 ms from the first character received: this is the system “wake up time”. As a consequence, the first character sent by the DTE when the UART is disabled (i.e. the wake up character) is not a valid communication character even if the wake up via data reception configuration is active, because it cannot be recognized, and the recognition of the subsequent characters is guaranteed only after the complete system wake-up (i.e. after ~5 ms). The TXD input line is configured to wake up the system via data reception in the following cases:  AT+UPSV=1 is set with HW flow control disabled  AT+UPSV=2 is set with HW flow control disabled, and the RTS line is set OFF  AT+UPSV=3 is set with HW flow control disabled, and the DTR line is set OFF Figure 23 and Figure 24 show examples of common scenarios and timing constraints:  AT+UPSV=1 power saving configuration is active and the timeout from last data received to idle-mode start is set to 2000 frames (AT+UPSV=1,2000)  Hardware flow control is disabled Figure 23 shows the case where the module UART is disabled and only a wake-up is forced. In this scenario the only character sent by the DTE is the wake-up character; as a consequence, the DCE module UART is disabled when the timeout from last data received expires (2000 frames without data reception, as the default case). Wake up character Not recognized by DCEOFFONDCE UART is enabled for 2000 GSM frames (~9.2 s)time Wake up time: ~5 mstime TXD inputUARTOFFON Figure 23: Wake-up via data reception without further communication Figure 24 shows the case where in addition to the wake-up character further (valid) characters are sent. The wake up character wakes-up the module UART. The other characters must be sent after the “wake up time” of ~5 ms. If this condition is satisfied, the module (DCE) recognizes characters. The module will disable the UART after 2000 GSM frames from the latest data reception. Wake up character Not recognized by DCEValid characters Recognized by DCEDCE UART is enabled for 2000 GSM frames (~9.2s) after the last data receivedtime Wake up time: ~5 mstime OFFONTXD inputUARTOFFON Figure 24: Wake-up via data reception with further communication

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 54 of 158 1.9.3 DDC (I2C) interface The I2C bus compatible Display Data Channel interface is not available on the MPCI-L2 series modules, as AssistNow embedded GNSS positioning aiding, CellLocate® positioning through cellular information and custom functions over GPIOs for the integration with u-blox positioning chips / modules. The I2C bus compatible Display Data Channel interface is not supported by the TOBY-L2 series modules “00”, “01” and “50” product versions, as the AssistNow embedded GNSS positioning aiding, CellLocate® positioning through cellular information and custom functions over GPIOs for the integration with u-blox positioning chips / modules. The SDA and SCL pins of TOBY-L2 series modules represent an I2C bus compatible Display Data Channel (DDC) interface for the communication with u-blox GNSS receivers and with other external I2C devices as audio codecs: an I2C master can communicate with more I2C slaves in accordance to the I2C bus specifications [12]. The DDC (I2C) interface is the only one interface dedicated for communication between u-blox cellular module and u-blox positioning receivers. The AT commands interface is not available on the DDC (I2C) interface. The DDC (I2C) interface pads of the module, serial data (SDA) and serial clock (SCL), are open drain output and external pull up resistors must be used conforming to the I2C bus specifications [12]. u-blox has implemented special features in the cellular modules to ease the design effort for the integration of a u-blox cellular module with a u-blox GNSS receiver (details in GNSS Implementation Application Note [13]). Combining a u-blox cellular module with a u-blox GNSS receiver allows designers to full access the GNSS receiver directly via the cellular module: it relays control messages to the GNSS receiver via a dedicated DDC (I2C) interface. A 2nd interface connected to the GNSS receiver is not necessary: AT commands via the AT interfaces of the cellular module (UART, USB) allows a full control of the GNSS receiver from any host processor. u-blox cellular modules feature embedded GNSS aiding that is a set of specific features developed by u-blox to enhance GNSS performance, decreasing Time To First Fix (TTFF), thus allowing to calculate the position in a shorter time with higher accuracy. Additional custom functions over GPIO pins are designed to improve the integration with u-blox GNSS receivers:  GNSS receiver power-on/off: “GNSS supply enable” function over the GPIO2 pin improves the positioning receiver power consumption. When the GNSS functionality is not required, the positioning receiver can be completely switched off by the cellular module controlled by the application processor over AT commands  The wake up from idle-mode when the GNSS receiver is ready to send data: “GNSS data ready” function over the GPIO3 pin improves the cellular module power consumption. When power saving is enabled in the cellular module by the AT+UPSV command and the GNSS receiver does not send data by the DDC (I2C) interface, the module automatically enters idle-mode whenever possible. With the “GNSS data ready” function the GNSS receiver can indicate to the cellular module that it is ready to send data: the positioning receiver can wake up the cellular module to avoid data loss even if power saving is enabled.  The RTC synchronization signal to the GNSS receiver: “GNSS RTC sharing” function over the GPIO4 pin improves GNSS receiver performance, decreasing the Time To First Fix (TTFF), and thus allowing to calculate the position in a shorter time with higher accuracy. When GNSS local aiding is enabled, the cellular module automatically uploads data such as position, time, ephemeris, almanac, health and ionospheric parameter from the positioning receiver into its local memory, and restores this to the GNSS receiver at the next power up of the positioning receiver

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 55 of 158 1.9.4 Secure Digital Input Output interface (SDIO) Secure Digital Input Output interface is not available on MPCI-L2 series modules. Secure Digital Input Output interface is not supported by TOBY-L2 “00” and “01” product versions. TOBY-L2 series modules include a 4-bit Secure Digital Input Output interface (SDIO_D0, SDIO_D1, SDIO_D2, SDIO_D3, SDIO_CLK, SDIO_CMD) designed to communicate with an external u-blox short range Wi-Fi module: the TOBY-L2 cellular module acts as an SDIO host controller which can communicate over the SDIO bus with a compatible u-blox short range Wi-Fi module acting as SDIO device. The SDIO interface is the only one interface of TOBY-L2 series modules dedicated for communication between the u-blox cellular module and the u-blox short range Wi-Fi module. The AT commands interface is not available on the SDIO interface of TOBY-L2 series modules. The SDIO interface supports 50 MHz bus clock frequency, which allows a data throughput of 200 Mb/s. Combining a u-blox cellular module with a u-blox short range communication module gives designers full access to the Wi-Fi module directly via the cellular module, so that a second interface connected to the Wi-Fi module is not necessary. AT commands via the AT interfaces of the cellular module (UART, USB) allows a full control of the Wi-Fi module from any host processor, because Wi-Fi control messages are relayed to the Wi-Fi module via the dedicated SDIO interface (for more details, see the Wi-Fi AT commands in the u-blox AT Commands Manual [3]). u-blox has implemented special features in the cellular modules to ease the design effort for the integration of a u-blox cellular module with a u-blox short range Wi-Fi module to provide both Bridge and Router functionality (for more details, see the Wi-Fi / Cellular Integration Application Note [14]). Additional custom functions over GPIO pins are designed to improve the integration with u-blox Wi-Fi modules:  Wi-Fi enable Switch-on / switch-off the Wi-Fi  Wi-Fi reset Reset the Wi-Fi  Wi-Fi data ready Cellular module wake-up when the Wi-Fi is ready for sending data over SDIO  Wi-Fi power saving Enable/disable the low power mode of the Wi-Fi  32 kHz output Clock for the Wi-Fi  26 MHz output Clock for the Wi-Fi GPIOs are not supported by TOBY-L2 “00”, “01”, and “50” product versions, except for:  Wireless Wide Area Network status indication configured on GPIO1 of “00”, “01” product versions  Wi-Fi enable function configured on the GPIO1 of “50“ product version GPIOs are not available on MPCI-L2 series modules. 1.10 Audio 1.10.1 Digital audio over I2S interface Digital audio over I2S interface is not available on MPCI-L2 series modules. Digital audio over I2S interface is not supported by TOBY-L2 modules ”00”, “01”, “50” product versions. TOBY-L2 series modules include a 4-wire I2S digital audio interface (I2S_TXD, I2S_RXD, I2S_CLK, I2S_WA) that can be configured by AT command to transfer digital audio data with an external device as an audio codec (for more details see u-blox AT Commands Manual [3]).

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 56 of 158 1.11 General Purpose Input/Output GPIOs are not supported by TOBY-L2 series modules “00”, “01” and “50” product versions, except for:  Wireless Wide Area Network status indication configured on GPIO1 of “00”, “01” product versions  Wi-Fi enable function configured on the GPIO1 of “50” product version GPIOs are not available on MPCI-L2 series modules. TOBY-L2 series modules include 14 pins (GPIO1-GPIO6, I2S_TXD, I2S_RXD, I2S_CLK, I2S_WA, DTR, DSR, DCD, RI) that can be configured as General Purpose Input/Output or to provide custom functions via u-blox AT commands (see the u-blox AT Commands Manual [3]), as summarized in Table 13. Function Description Default GPIO Configurable GPIOs Network status indication Network status: registered home network, registered roaming, data transmission, no service GPIO1 GPIO1 GNSS supply enable Enable/disable the supply of u-blox GNSS receiver connected to cellular module GPIO2 GPIO2 GNSS data ready Sense when u-blox GNSS receiver connected to the module is ready for sending data by the DDC (I2C) GPIO3 GPIO3 GNSS RTC sharing Real Time Clock synchronization signal to u-blox GNSS receiver connected to cellular module GPIO4 GPIO4 SIM card detection SIM card physical presence detection GPIO5 GPIO5 SIM card hot insertion/removal SIM card hot insertion/removal -- GPIO5 I2S digital audio interface I2S digital audio interface I2S_RXD, I2S_TXD, I2S_CLK, I2S_WA I2S_RXD, I2S_TXD, I2S_CLK, I2S_WA 26 MHz clock output 26 MHz clock output for an external audio codec or an external Wi-Fi chip/module GPIO6 GPIO6 Wi-Fi enable Enable/disable the supply of the external Wi-Fi chip or module connected to the cellular module -- GPIO1, GPIO4, DSR Wi-Fi data ready Sense when the external Wi-Fi chip/module connected to the cellular module is ready for sending data by the SDIO, waking up the cellular module from low power idle mode -- GPIO3, DTR Wi-Fi reset Reset the external Wi-Fi chip or module connected to the cellular module -- GPIO3, DCD Wi-Fi power saving Enable/disable the low power mode of the external Wi-Fi chip/module connected to the cellular module -- GPIO2, RI 32 kHz clock output 32 kHz clock output for an external Wi-Fi chip or module -- GPIO6 Antenna tuning 4-bit tunable antenna control signals mapping the actual operating RF band over a 4-pin interface provided for the implementation of external antenna tuning solutions -- I2S_RXD, I2S_TXD, I2S_CLK, I2S_WA DSR, DTR, DCD, RI DSR UART data set ready output DSR DSR DTR UART data terminal ready input DTR DTR DCD UART data carrier detect output DCD DCD RI UART ring indicator output RI RI General purpose input Input to sense high or low digital level -- All General purpose output Output to set the high or the low digital level -- All Pin disabled Tri-state with an internal active pull-down enabled -- All Table 13: TOBY-L2 series GPIO custom functions configuration

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 57 of 158 1.12 Mini PCIe specific signals (W_DISABLE#, LED_WWAN#) Mini PCI Express specific signals (W_DISABLE#, LED_WWAN#) are not available on TOBY-L2 series. MPCI-L2 series modules include the W_DISABLE# active-low input signal to disable the radio operations as specified by the PCI Express Mini Card Electromechanical Specification [15]. As described in Figure 25, the W_DISABLE# input is equipped with an internal pull-up to the 3.3Vaux supply. The W_DISABLE# input detailed electrical characteristics are described in the MPCI-L2 series Data Sheet [2]. Baseband Processor20W_DISABLE#MPCI-L2 series3.3VauxW_DISABLE#22k Figure 25: MPCI-L2 series modules W_DISABLE# input circuit description MPCI-L2 series modules include the LED_WWAN# active-low open drain output to provide the Wireless Wide Area Network status indication as specified by the PCI Express Mini Card Electromechanical Specification [15]. For more electrical characteristics details see the MPCI-L2 Data Sheet [2]. 1.13 Reserved pins (RSVD) Pins reserved for future use, marked as RSVD, are not available on MPCI-L2 series. TOBY-L2 series modules have pins reserved for future use, marked as RSVD: they can all be left unconnected on the application board, except the RSVD pin number 6 that must be externally connected to ground. 1.14 Not connected pins (NC) Pins internally not connected, marked as NC, are not available on TOBY-L2 series. MPCI-L2 series modules have pins internally not connected, marked as NC: they can be left unconnected or they can be connected on the application board according to any application requirement, given that none function is provided by the modules over these pins.

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 58 of 158 1.15 System features 1.15.1 Network indication Network status indication over GPIO1 is not available on MPCI-L2 series modules which include the LED_WWAN# active-low open drain output to provide the Wireless Wide Area Network status indication as specified by the PCI Express Mini Card Electromechanical Specification [15]. GPIOs are not supported by TOBY-L2 modules “00”, “01”, “50” product versions, but the Wireless Wide Area Network status indication is by default configured on the GPIO1 of “00”, “01” product version. The GPIO1 can be configured by the AT+UGPIOC command (for further details see the u-blox AT Commands Manual [3]), to indicate network status as described below:  No service (no network coverage or not registered)  Registered 2G / 3G / LTE home network  Registered 2G / 3G / LTE visitor network (roaming)  Call enabled (RF data transmission / reception) 1.15.2 Antenna supervisor Antenna supervisor (i.e. antenna detection) is not available on MPCI-L2 series. Antenna supervisor (i.e. antenna detection) is not supported by TOBY-L2 series modules “00”, “01” and “50” product versions. The antenna detection function provided by the ANT_DET pin is based on an ADC measurement as optional feature that can be implemented if the application requires it. The antenna supervisor is forced by the +UANTR AT command (see the u-blox AT Commands Manual [3] for more details). The requirements to achieve antenna detection functionality are the following:  an RF antenna assembly with a built-in resistor (diagnostic circuit) must be used  an antenna detection circuit must be implemented on the application board See section 1.7.2 for detailed antenna detection interface functional description and see section 2.4.2 for detection circuit on application board and diagnostic circuit on antenna assembly design-in guidelines. 1.15.3 Jamming detection Congestion detection (i.e. jamming detection) is not supported by “00”, “01” and “50” product versions. In real network situations modules can experience various kind of out-of-coverage conditions: limited service conditions when roaming to networks not supporting the specific SIM, limited service in cells which are not suitable or barred due to operators’ choices, no cell condition when moving to poorly served or highly interfered areas. In the latter case, interference can be artificially injected in the environment by a noise generator covering a given spectrum, thus obscuring the operator’s carriers entitled to give access to the LTE/3G/2G service. The congestion (i.e. jamming) detection feature can be enabled and configured by the +UCD AT command: the feature consists of detecting an anomalous source of interference and signaling the start and stop of such conditions to the host application processor with an unsolicited indication, which can react appropriately by e.g. switching off the radio transceiver of the module (i.e. configuring the module in “airplane mode” by means of the +CFUN AT command) in order to reduce power consumption and monitoring the environment at constant periods (for more details see the u-blox AT Commands Manual [3]).

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 59 of 158 1.15.4 IP modes of operation IP modes of operation refer to the TOBY-L2 and MPCI-L2 series modules configuration related to the network IP termination and network interfaces settings in general. IP modes of operation are the following:  Bridge mode: In bridge mode the module acts as a cellular modem dongle connected to the host over serial interface. The IP termination of the network is placed on the host IP stack. The module is configured as a bridge which means the network IP address is assigned to the host (host IP termination).  Router mode: In router mode the module acts as a cellular modem router which means the IP termination of the network is placed on the internal IP stack of the module (on-target IP termination). In particular, in this configuration the application processor belongs to a private network and is not aware of the mobile connectivity setup of the module. For more details about IP modes of operation see the u-blox AT Commands Manual [3]. 1.15.5 Dual stack IPv4/IPv6 TOBY-L2 and MPCI-L2 series support both Internet Protocol version 4 and Internet Protocol version 6 in parallel. For more details about dual stack IPv4/IPv6 see the u-blox AT Commands Manual [3]. 1.15.6 TCP/IP and UDP/IP Embedded TCP/IP and UDP/IP stack as well as Direct Link mode are not supported by the “00” and “50” product versions. TOBY-L2 and MPCI-L2 series modules provide embedded TCP/IP and UDP/IP protocol stack: a PDP context can be configured, established and handled via the data connection management packet switched data commands. TOBY-L2 and MPCI-L2 series modules provide Direct Link mode to establish a transparent end-to-end communication with an already connected TCP or UDP socket via serial interfaces (USB, UART). In Direct Link mode, data sent to the serial interface from an external application processor is forwarded to the network and vice-versa. For more details about embedded TCP/IP and UDP/IP functionalities see the u-blox AT Commands Manual [3]. 1.15.7 FTP Embedded FTP services as well as Direct Link mode are not supported by “00” and “50” product versions. TOBY-L2 and MPCI-L2 series provide embedded File Transfer Protocol (FTP) services. Files are read and stored in the local file system of the module. FTP files can also be transferred using FTP Direct Link:  FTP download: data coming from the FTP server is forwarded to the host processor via USB / UART serial interfaces (for FTP without Direct Link mode the data is always stored in the module’s Flash File System)  FTP upload: data coming from the host processor via USB / UART serial interface is forwarded to the FTP server (for FTP without Direct Link mode the data is read from the module’s Flash File System) When Direct Link is used for a FTP file transfer, only the file content pass through USB / UART serial interface, whereas all the FTP commands handling is managed internally by the FTP application. For more details about embedded FTP functionalities see u-blox AT Commands Manual [3].

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 60 of 158 1.15.8 HTTP Embedded HTTP services are not supported by “00” and “50” product versions. TOBY-L2 and MPCI-L2 series modules provide the embedded Hyper-Text Transfer Protocol (HTTP) services via AT commands for sending requests to a remote HTTP server, receiving the server response and transparently storing it in the module’s Flash File System (FFS). For more details about embedded HTTP functionalities see the u-blox AT Commands Manual [3]. 1.15.9 SSL Embedded Transport Layer Security (TLS) / Secure Sockets Layer (SSL) protocols are not supported by the “00”, “01” and “50” product versions. TOBY-L2 and MPCI-L2 series modules provide the Transport Layer Security (TLS) / Secure Sockets Layer (SSL) encryption protocols to enable security over the FTP and HTTP protocols via AT commands, implementing Secure File Transfer Protocol (FTPS, i.e. FTP with TLS / SSL encryption) and Secure Hyper-Text Transfer Protocol (HTTPS, i.e. HTTP with TLS / SSL encryption) services. For more details about embedded TLS / SSL functionalities see the u-blox AT Commands Manual [3]. 1.15.10 AssistNow clients and GNSS integration AssistNow clients and u-blox GNSS receiver integration are not available on the MPCI-L2 series modules. AssistNow clients and u-blox GNSS receiver integration are not supported by the TOBY-L2 series modules “00”, “01” and “50” product versions. For customers using u-blox GNSS receivers, TOBY-L2 series cellular modules feature embedded AssistNow clients. AssistNow A-GPS provides better GNSS performance and faster Time-To-First-Fix. The clients can be enabled and disabled with an AT command (see the u-blox AT Commands Manual [3]). TOBY-L2 series cellular modules act as a stand-alone AssistNow client, making AssistNow available with no additional requirements for resources or software integration on an external host micro controller. Full access to u-blox GNSS receivers is available via the TOBY-L2 series cellular module, through the DDC (I2C) interface, while the available GPIOs can handle the positioning chipset / module power-on/off. This means that cellular module and GNSS receiver can be controlled through a single serial port from any host processor. 1.15.11 Hybrid positioning and CellLocate® Hybrid positioning and CellLocate® are not available on MPCI-L2 series. Hybrid positioning and CellLocate® are not supported by the TOBY-L2 series modules “00”, “01” and “50” product versions. Although GNSS is a widespread technology, its reliance on the visibility of extremely weak GNSS satellite signals means that positioning is not always possible. Especially difficult environments for GNSS are indoors, in enclosed or underground parking garages, as well as in urban canyons where GNSS signals are blocked or jammed by multipath interference. The situation can be improved by augmenting GNSS receiver data with cellular network information to provide positioning information even when GNSS reception is degraded or absent. This additional information can benefit numerous applications.

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 61 of 158 Positioning through cellular information: CellLocate® u-blox CellLocate® enables the estimation of device position based on the parameters of the mobile network cells visible to the specific device. To estimate its position the u-blox cellular module sends the CellLocate® server the parameters of network cells visible to it using a UDP connection. In return the server provides the estimated position based on the CellLocate® database. The u-blox cellular module can either send the parameters of the visible home network cells only (normal scan) or the parameters of all surrounding cells of all mobile operators (deep scan). The CellLocate® database is compiled from the position of devices which observed, in the past, a specific cell or set of cells (historical observations) as follows: 1. Several devices reported their position to the CellLocate® server when observing a specific cell (the As in the picture represent the position of the devices which observed the same cell A) 2. CellLocate® server defines the area of Cell A visibility

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 62 of 158 3. If a new device reports the observation of Cell A CellLocate® is able to provide the estimated position from the area of visibility 4. The visibility of multiple cells provides increased accuracy based on the intersection of areas of visibility. CellLocate® is implemented using a set of two AT commands that allow configuration of the CellLocate® service (AT+ULOCCELL) and requesting position according to the user configuration (AT+ULOC). The answer is provided in the form of an unsolicited AT command including latitude, longitude and estimated accuracy. The accuracy of the position estimated by CellLocate® depends on the availability of historical observations in the specific area. Hybrid positioning With u-blox Hybrid positioning technology, u-blox cellular devices can be triggered to provide their current position using either a u-blox GNSS receiver or the position estimated from CellLocate®. The choice depends on which positioning method provides the best and fastest solution according to the user configuration, exploiting the benefit of having multiple and complementary positioning methods. Hybrid positioning is implemented through a set of three AT commands that allow configuration of the GNSS receiver (AT+ULOCGNSS), configuration of the CellLocate® service (AT+ULOCCELL), and requesting the position according to the user configuration (AT+ULOC). The answer is provided in the form of an unsolicited AT command including latitude, longitude and estimated accuracy (if the position has been estimated by CellLocate®), and additional parameters if the position has been computed by the GNSS receiver. The configuration of mobile network cells does not remain static (e.g. new cells are continuously added or existing cells are reconfigured by the network operators). For this reason, when a Hybrid positioning method has been triggered and the GNSS receiver calculates the position, a database self-learning mechanism has been implemented so that these positions are sent to the server to update the database and maintain its accuracy.

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 63 of 158 The use of hybrid positioning requires a connection via the DDC (I2C) bus between the TOBY-L2 series cellular module and the u-blox GNSS receiver (see sections 1.9.3 and 2.6.3). See GNSS Implementation Application Note [13] for the complete description of the feature. u-blox is extremely mindful of user privacy. When a position is sent to the CellLocate® server u-blox is unable to track the SIM used or the specific device. 1.15.12 Wi-Fi integration u-blox short range communication Wi-Fi modules integration is not available for MPCI-L2 series modules. u-blox short range communication Wi-Fi modules integration is not supported by the TOBY-L2 series modules “00” and “01” product versions. Full access to u-blox short range communication Wi-Fi modules is available through a dedicated SDIO interface (see sections 1.9.4 and 2.6.4). This means that combining a TOBY-L2 series cellular module with a u-blox short range communication module gives designers full access to the Wi-Fi module directly via the cellular module, so that a second interface connected to the Wi-Fi module is not necessary. AT commands via the AT interfaces of the cellular module (UART, USB) allows a full control of the Wi-Fi module from any host processor, because Wi-Fi control messages are relayed to the Wi-Fi module via the dedicated SDIO interface (for more details, see the Wi-Fi AT commands in the u-blox AT Commands Manual [3]). All the management software for Wi-Fi module operations runs inside the cellular module in addition to those required for cellular-only operation: Wi-Fi driver, Web User Interface (WebUI), Connection Config Manager. For more details, see the Wi-Fi / Cellular Integration Application Note [14]. 1.15.13 Firmware update Over AT (FOAT) This feature allows upgrading the module firmware over USB / UART serial interfaces, using AT commands.  The +UFWUPD AT command triggers a reboot followed by the upgrade procedure at specified a baud rate  A special boot loader on the module performs firmware installation, security verifications and module reboot  Firmware authenticity verification is performed via a security signature during the download. The firmware is then installed, overwriting the current version. In case of power loss during this phase, the boot loader detects a fault at the next wake-up, and restarts the firmware download. After completing the upgrade, the module is reset again and wakes-up in normal boot For more details about Firmware update Over AT procedure see the Firmware Update Application Note [4] and the u-blox AT Commands Manual [3], +UFWUPD AT command. 1.15.14 Firmware update Over The Air (FOTA) Firmware update Over The Air (FOTA) is not supported by “00” and “50” product versions. This feature allows upgrading the module firmware over the LTE/3G/2G air interface. In order to reduce the amount of data to be transmitted over the air, the implemented FOTA feature requires downloading only a “delta file” instead of the full firmware. The delta file contains only the differences between the two firmware versions (old and new), and is compressed. The firmware update procedure can be triggered using dedicated AT command with the delta file stored in the module file system via over the air FTP. For more details about Firmware update Over The Air procedure see the Firmware Update Application Note [4] and the u-blox AT Commands Manual [3], +UFWINSTALL AT command.

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 66 of 158 1.15.17 Smart temperature management Smart temperature management is not supported by “00”, “01”, and “50” product versions. Cellular modules – independent of the specific model – always have a well defined operating temperature range. This range should be respected to guarantee full device functionality and long life span. Nevertheless there are environmental conditions that can affect operating temperature, e.g. if the device is located near a heating/cooling source, if there is/isn’t air circulating, etc. The module itself can also influence the environmental conditions; such as when it is transmitting at full power. In this case its temperature increases very quickly and can raise the temperature nearby. The best solution is always to properly design the system where the module is integrated. Nevertheless an extra check/security mechanism embedded into the module is a good solution to prevent operation of the device outside of the specified range. Smart Temperature Supervisor (STS) The Smart Temperature Supervisor is activated and configured by a dedicated AT+USTS command. See the u-blox AT Commands Manual [3] for more details. The cellular module measures the internal temperature (Ti) and its value is compared with predefined thresholds to identify the actual working temperature range. Temperature measurement is done inside the cellular module: the measured value could be different from the environmental temperature (Ta). Warningareat-1 t+1 t+2t-2Valid temperature rangeSafeareaDangerousarea Dangerousarea Warningarea Figure 29: Temperature range and limits The entire temperature range is divided into sub-regions by limits (see Figure 29) named t-2, t-1, t+1 and t+2.  Within the first limit, (t-1 < Ti < t+1), the cellular module is in the normal working range, the Safe Area  In the Warning Area, (t-2 < Ti < t.1) or (t+1 < Ti < t+2), the cellular module is still inside the valid temperature range, but the measured temperature approaches the limit (upper or lower). The module sends a warning to the user (through the active AT communication interface), which can take, if possible, the necessary actions to return to a safer temperature range or simply ignore the indication. The module is still in a valid and good working condition  Outside the valid temperature range, (Ti < t-2) or (Ti > t+2), the device is working outside the specified range and represents a dangerous working condition. This condition is indicated and the device shuts down to avoid damage For security reasons the shutdown is suspended in case an emergency call in progress. In this case the device will switch off at call termination. The user can decide at anytime to enable/disable the Smart Temperature Supervisor feature. If the feature is disabled there is no embedded protection against disallowed temperature conditions.

TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 67 of 158 Figure 30 shows the flow diagram implemented for the Smart Temperature Supervisor. IF STS enabledRead temperatureIF(t-1<Ti<t+1)IF(t-2<Ti<t+2)Send notification (warning)Send notification(dangerous)Wait emergencycall terminationIFemerg. call in progressShut the device downYesNoYesYesNoNoNoYesSend shutdownnotificationFeature enabled (full logic or indication only)IF Full Logic EnabledFeature disabled: no actionTemperature is within normal operating rangeYesTempetature is within warning areaTempetature is outside valid temperature rangeNoFeatuere enabled in full logic modeFeature enabled in indication only mode:no further actionsSend notification (safe)Previously outside of Safe AreaTempetature is back to safe areaNoNo furtheractionsYes Figure 30: Smart Temperature Supervisor (STS) flow diagram

$TOBY-L2 and MPCI-L2 series - System Integration Manual UBX-13004618 - R08 Early Production Information System description Page 68 of 158 Threshold Definitions When the application of cellular module operates at extreme temperatures with Smart Temperature Supervisor enabled, the user should note that outside the valid temperature range the device will automatically shut down as described above. The input for the algorithm is always the temperature measured within the cellular module (Ti, internal). This value can be higher than the working ambient temperature (Ta, ambient), as (for example) during transmission at maximum power a significant fraction of DC input power is dissipated as heat This behavior is partially compensated by the definition of the upper shutdown threshold (t+2) that is slightly higher than the declared environmental temperature limit. The sensor measures board temperature inside the shields, which can differ from ambient temperature. 1.15.18 Power saving The power saving configuration is by default disabled, but it can be enabled using the AT+UPSV command (for the complete description of the AT+UPSV command, see the u-blox AT Commands Manual [3]). When power saving is enabled, the module automatically enters the low power idle-mode whenever possible, reducing current consumption (see section 1.5.1.5, TOBY-L2 Data Sheet [1] and MPCI-L2 Data Sheet [2]). During the low power idle-mode, the module is not ready to communicate with an external device, as it is configured to reduce power consumption. The module wakes up from low power idle-mode to active-mode in the following events:  Automatic periodic monitoring of the paging channel for the reception of the paging block sent by the base station according to network conditions (see section 1.5.1.5)  The connected USB host forces a remote wakeup of the module as USB device (see section 1.9.1.4)  Automatic periodic enable of the UART interface to receive / send data, with AT+UPSV=1 (see 1.9.2.4)  Data received on UART interface, with HW flow control disabled and AT+UPSV=1 (see 1.9.2.4)  RTS input set ON by the host DTE, with HW flow control disabled and AT+UPSV=2 (see 1.9.2.4)  DTR input set ON by the host DTE, with AT+UPSV=3 (see 1.9.2.4)  The connected SDIO device forces a wakeup of the module as SDIO host (see 1.9.4)  A preset RTC alarm occurs (see u-blox AT Commands Manual [3], AT+CALA) For the definition and the description of TOBY-L2 and MPCI-L2 series modules operating modes, including the events forcing transitions between the different operating modes, see the section 1.4.$

u blox TOBYL280 GSM/UMTS/LTE Data Module User Manual TOBY L2 series

u-blox AG GSM/UMTS/LTE Data Module TOBY L2 series

Contents

System Integrators Manual

Navigation menu

Namespaces

Views

Navigation