Telit LE910Cx User Manual

[

Software User Guide

LE910Cx

1VV0301556 Rev. 7 – 2020-09-25

1VV0301556 2019-09 Rev.3

09.2019]

SPECIFICATIONS ARE SUBJECT TO CHANGE WITHOUT NOTICE

NOTICES LIST

While reasonable efforts have been made to assure the accuracy of this document, Telit assumes no liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained herein. The information in this document has been carefully checked and is believed to be reliable. However, no responsibility is assumed for inaccuracies or omissions. Telit reserves the right to make changes to any products described herein and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Telit does not assume any liability arising out of the application or use of any product, software, or circuit described herein; neither does it convey license under its patent rights or the rights of others.

It is possible that this publication may contain references to, or information about Telit products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that Telit intends to announce such Telit products, programming, or services in your country.

COPYRIGHTS

This instruction manual and the Telit products described in this instruction manual may be, include or describe copyrighted Telit material, such as computer programs stored in semiconductor memories or other media. Laws in the Italy and other countries preserve for Telit and its licensors certain exclusive rights for copyrighted material, including the exclusive right to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly, any copyrighted material of Telit and its licensors contained herein or in the Telit products described in this instruction manual may not be copied, reproduced, distributed, merged or modified in any manner without the express written permission of Telit. Furthermore, the purchase of Telit products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any license under the copyrights, patents or patent applications of Telit, as arises by operation of law in the sale of a product.

COMPUTER SOFTWARE COPYRIGHTS

The Telit and 3rd Party supplied Software (SW) products described in this instruction manual may include copyrighted Telit and other 3rd Party supplied computer programs stored in semiconductor memories or other media. Laws in the Italy and other countries preserve for Telit and other 3rd Party supplied SW certain exclusive rights for copyrighted computer programs, including the exclusive right to copy or reproduce in any form the copyrighted computer program. Accordingly, any copyrighted Telit or other 3rd Party supplied SW computer programs contained in the Telit products described in this instruction manual may not be copied (reverse engineered) or reproduced in any manner without the express written permission of Telit or the 3rd Party SW supplier. Furthermore, the purchase of Telit products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any license under the copyrights, patents or patent applications of Telit or other 3rd Party supplied SW, except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a product.

1VV0301556 Rev. 7

Page 2 of 145

2020-09-25

USAGE AND DISCLOSURE RESTRICTIONS

I. License Agreements

The software described in this document is the property of Telit and its licensors. It is furnished by express license agreement only and may be used only in accordance with the terms of such an agreement.

II. Copyrighted Materials

Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, without prior written permission of Telit

III. High Risk Materials

Components, units, or third-party products used in the product described herein are NOT faulttolerant and are NOT designed, manufactured, or intended for use as on-line control equipment in the following hazardous environments requiring fail-safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication Systems, Air Traffic Control, Life Support, or Weapons Systems (High Risk Activities"). Telit and its supplier(s) specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities.

IV. Trademarks

TELIT and the Stylized T Logo are registered in Trademark Office. All other product or service names are the property of their respective owners.

V. Third Party Rights

The software may include Third Party Right software. In this case you agree to comply with all terms and conditions imposed on you in respect of such separate software. In addition to Third Party Terms, the disclaimer of warranty and limitation of liability provisions in this License shall apply to the Third Party Right software.

TELIT HEREBY DISCLAIMS ANY AND ALL WARRANTIES EXPRESS OR IMPLIED FROM ANY THIRD PARTIES REGARDING ANY SEPARATE FILES, ANY THIRD PARTY MATERIALS INCLUDED IN THE SOFTWARE, ANY THIRD PARTY MATERIALS FROM WHICH THE SOFTWARE IS DERIVED (COLLECTIVELY “OTHER CODE”), AND THE USE OF ANY OR ALL THE OTHER CODE IN CONNECTION WITH THE SOFTWARE, INCLUDING (WITHOUT LIMITATION) ANY WARRANTIES OF SATISFACTORY QUALITY OR FITNESS FOR A PARTICULAR PURPOSE.

NO THIRD PARTY LICENSORS OF OTHER CODE SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND WHETHER MADE UNDER CONTRACT, TORT OR OTHER LEGAL THEORY, ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE OTHER CODE OR THE EXERCISE OF ANY RIGHTS GRANTED UNDER EITHER OR BOTH THIS LICENSE AND THE LEGAL TERMS APPLICABLE TO ANY SEPARATE FILES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

1VV0301556 Rev. 7

Page 3 of 145

2020-09-25

APPLICABILITY TABLE

PRODUCTS

LE910C1-NA

LE910C1-NS

LE910CX-NF

LE910CX-EU

LE910CX-AP

LE910CX-LA

LE910CX-CN

LE910C1-SV

LE910C1-SA

LE910C1-ST

LE910C1-EUX

LE910C1-SAX

LE910C1-SVX

Table 1 Products

1VV0301556 Rev. 7

Page 4 of 145

2020-09-25

CONTENTS

NOTICES LIST ............................................................................................... 2

COPYRIGHTS ................................................................................................ 2

COMPUTER SOFTWARE COPYRIGHTS ...................................................... 2

USAGE AND DISCLOSURE RESTRICTIONS ............................................... 3

APPLICABILITY TABLE ................................................................................ 4

CONTENTS .................................................................................................... 5

1. INTRODUCTION .......................................................................... 8

Scope ........................................................................................... 8

Audience....................................................................................... 8

Contact Information, Support ........................................................ 8

Text Conventions ........................................................................ 10

Related Documents .................................................................... 11

2. LE910CX VARIANTS ................................................................. 12

3. HIGH LEVEL SW ARCHITECTURE ........................................... 13

Architecture based on Linux ....................................................... 13

Architecture based on ThreadX .................................................. 14

4. FUNCTIONAL DESCRIPTION ................................................... 15

General Functionality and Main Features.................................... 15

Application system overview ....................................................... 15

4.2.1. Memory configuration ................................................................. 16

4.2.2. Partition Layout ........................................................................... 16

4.2.3. RAM memory .............................................................................. 20

4.2.4. Customer application – Storage & configuration ......................... 21

4.2.5. Power up time ............................................................................. 22

4.2.6. Power up sequence .................................................................... 22

4.2.7. Location Subsystem ................................................................... 22

4.2.8. Application development environment ........................................ 22

4.2.9. Random number generator ......................................................... 23

4.2.10. Wake up Events.......................................................................... 23

4.2.11. SPI.............................................................................................. 33

4.2.12. GPIO-Keys ................................................................................. 34

4.2.13. Serial interfaces .......................................................................... 35

4.2.14. Audio .......................................................................................... 37

1VV0301556 Rev. 7

Page 5 of 145

2020-09-25

4.2.15. UART .......................................................................................... 39

4.2.16. USB Interface ............................................................................. 40

4.2.17. HSIC Interface ............................................................................ 41

4.2.18. SD/MMC Interface ...................................................................... 42

4.2.19. RTC ............................................................................................ 43

4.2.20. Time Services ............................................................................. 43

4.2.21. Data connection .......................................................................... 45

4.2.22. WatchDog ................................................................................... 45

4.2.23. Power Management .................................................................... 48

4.2.24. Performance build(Linux) ............................................................ 50

Basic Operations ........................................................................ 51

4.3.1. Command Syntax ....................................................................... 52

4.3.2. Command Response Timeout .................................................... 52

4.3.3. Basic AT Commands .................................................................. 55

4.3.4. RAT and Band Selection ............................................................. 55

4.3.5. SIM/USIM Management .............................................................. 56

4.3.6. Network Checking ....................................................................... 63

4.3.7. Network Information .................................................................... 65

4.3.8. Network Operator Identification ................................................... 67

4.3.9. Signal Strength & Quality ............................................................ 68

4.3.10. Extended Signal Quality .............................................................. 69

4.3.11. Fast Network Status Check ........................................................ 70

4.3.12. Voice Call Establishment – Originate .......................................... 73

Advanced Operations ................................................................. 74

4.4.1. Call Management ........................................................................ 74

4.4.2. DTMF Tones ............................................................................... 84

4.4.3. SMS Management ...................................................................... 84

4.4.4. GNSS Management .................................................................... 97

Packet Switched Data Operations ............................................ 111

4.5.1. USB Tethering Connection ....................................................... 111

4.5.2. Socket AT Commands .............................................................. 112

4.5.3. SSL AT Commands .................................................................. 117

4.5.4. HTTP AT Commands................................................................ 121

4.5.5. FTP AT Commands .................................................................. 123

4.5.6. Email AT Commands ................................................................ 127

4.5.7. IOT Platform AT Commands ..................................................... 128

4.5.8. Data Concurrency ..................................................................... 131

1VV0301556 Rev. 7

Page 6 of 145

2020-09-25

4.5.9. Maximum number of PDN contexts ........................................... 132

5. PERFORMANCE MEASUREMENTS(LINUX) .......................... 133

Interrupt latencies ..................................................................... 133

Memory bandwidth & Latencies ................................................ 134

6. SERVICE AND FIRMWARE UPDATE ..................................... 137

Firmware Update ...................................................................... 137

6.1.1. TFI update ................................................................................ 137

6.1.2. XFP update ............................................................................... 138

7. GLOSSARY AND ACRONYMS ............................................... 141

8. DOCUMENT HISTORY ............................................................ 143

1VV0301556 Rev. 7

Page 7 of 145

2020-09-25

1. INTRODUCTION

Scope

The aim of this document is to introduce Telit LE910Cx module as well as present possible and recommended Software solutions useful for developing a product based on the LE910Cx module. All the features and solutions detailed are applicable to all LE910Cx variants, where “LE910Cx” refers to the variants listed in the applicability table. If a specific feature is applicable to a specific product, it will be clearly highlighted.

The description text “LE910Cx” refers to all modules listed in the TABLE 1.

In this document all the basic functions of a wireless module will be taken into account; for each one of them a valid hardware solution will be suggested and usually incorrect solutions and common errors to be avoided will be highlighted. Obviously, this document cannot embrace every hardware solution or every product that may be designed. Obviously avoiding invalid solutions must be considered as mandatory. Whereas the suggested hardware configurations need not be considered mandatory, the information given should be used as a guide and a starting point for properly developing your product with the Telit LE910Cx module.

The integration of the GSM/GPRS/EGPRS/WCDMA/HSPA+/LTE LE910Cx cellular

module within user application must be done according to the design rules described

in this manual.

The information presented in this document is believed to be accurate and reliable. However, no responsibility is assumed by Telit Communication S.p.A. for its use, such as any infringement of patents or other rights of third parties which may result from its use. No license is granted by implication or otherwise under any patent rights of Telit Communication S.p.A. other than for circuitry embodied in Telit products. This document is subject to change without notice.

Audience

This document is intended for Telit customers, especially system integrators, about to implement their applications using our LE910Cx module.

Contact Information, Support

For general contact, technical support services, technical questions and report documentation errors contact Telit Technical Support at:

 TS-EMEA@telit.com  TS-AMERICAS@telit.com

1VV0301556 Rev. 7

Page 8 of 145

2020-09-25

 TS-APAC@telit.com  TS-SRD@telit.com (for Short Range Devices)

Alternatively, use:

http://www.telit.com/support

For detailed information about where you can buy the Telit modules or for recommendations on

accessories and components visit:

http://www.telit.com

Our aim is to make this guide as helpful as possible. Keep us informed of your comments and

suggestions for improvements.

Telit appreciates feedback from the users of our information.

1VV0301556 Rev. 7

Page 9 of 145

2020-09-25

Text Conventions

Danger – This information MUST be followed or catastrophic equipment failure or

bodily injury may occur.

Caution or Warning – Alerts the user to important points about integrating the

module, if these points are not followed, the module and end user equipment may

fail or malfunction.

Tip or Information – Provides advice and suggestions that may be useful when

integrating the module.

All dates are in ISO 8601 format, i.e. YYYY-MM-DD.

1VV0301556 Rev. 7

Page 10 of 145

2020-09-25

Related Documents

[1] AT Commands Reference Guide, 80000ST10025a [2] Refer to the specific "Telit Product Description" document [3] Refer to the specific "Telit Hardware User Guide" document [4] IP Easy User Guide, 80000ST10028A [5] ETSI GSM 07.07, 27.07 [6] EVK2 User Guide, 1vv0300704 [7] ETSI GSM 03.38, 23.038 [8] / [9] Device Requirements AT&T, Document Number 13340 [10] Telit 3G Modules Ports Arrangements User Guide, 1vv0300971 [11] Enhanced JDR Technical Note, 30353NT11086A [12] ITU-T Recommendation E.164 [13] ETSI GSM 11.11, 51.011, 31.101, 31.102 [14] ITU-T Recommendation V.24 [15] / [16] ETSI GSM 11.14, 51.014 [17] Telit 3G Modules AT Commands Reference Guide, 80378ST10091A [18] Audio Setting Application Note, 80000NT10007A [19] ETSI GSM 27.005 [20] Telit’s Easy Scan User Guide, 1vv0300972 [21] Jamming Detection – HE910 Series Application Note, 80000NT11408A [22] GE910 Series Ports Arrangements User Guide, 1vv0301049 [23] IP Easy User Guide Application Note, 80000ST10028A [24] Virtual Serial Device Application Note, 80000NT10045A [25] NCM Protocol User Guide, 1vv0301246 [26] Telit LE910 V2 Series AT Commands Reference Guide, 80446ST10707A [27] LE910Cx_Linux_device_driver_Application_Note, 80502NT11769A

1VV0301556 Rev. 7

Page 11 of 145

2020-09-25

Variants

Linux

2. LE910CX VARIANTS

LE910Cx has several variants, but it is divided into 2 types according to the basic operating system. One is Linux base and the other is ThreadX.

Below is the basic OS for each variant.

LE910C1-NA

Linux

LE910C1-NS

LE910CX-NF Linux

LE910CX-EU Linux

LE910CX-AP Linux

LE910CX-LA Linux

LE910C1-SV Linux

LE910CX-CN Linux

LE910C1-SA Linux

LE910C1-ST Linux

LE910C1-EUX

LE910C1-SAX

ThreadX

LE910C1-SVX

ThreadX

Therefore, when referring to the document, please check for differences depending on the OS. Unless otherwise specified, the descriptions are commonly applicable to both Linux and ThreadX variants.

1VV0301556 Rev. 7

Page 12 of 145

2020-09-25

3. HIGH LEVEL SW ARCHITECTURE

Architecture based on Linux

RPM

SBL

App Core

Drivers

USB 2.0

SDIO

UART

I2C

SPI

SBL I2SCSD

Power Mgr

Resource Mgr

SPM

AVS

PBL (boot rom)

AUDIO

SMD\SMEM

QMI

ACDB

Figure 1 : General System Architecture

Drivers

CoreBSP

CLK

SIO

SMD

UART

Data mover

Misc

UIM

Services

CoreBSP

Diag

Timers

INTC

EFS

Sleep

QURT RTOS

REX emulation

POSIX

LPASS

AFE

I2S PP

SPMIUART

Modem subsystem

NAS QOS WDS DMS PBM

GPS

CVD

Encoder

Decoder

IMS

Data

services

HDR

Modem HWNAV coreWTRPMICSIM card

QMI services

MMOC CM SD

UMTS/GERAN/TDSCDM A NAS LTE NAS

Protocol Stack (Acc ess stratum)

GERAN UMTS

Common (CRM, FWS)

GERAN UMTS LTE

MMCP

TDSCDM

MMCP

Common PHY

RX FE Link

Mgr

LTE

RF Driver

TDSCDM

TxC Link

MCPM

1VV0301556 Rev. 7

Page 13 of 145

2020-09-25

Figure 2: Linux Kernel components

Architecture based on ThreadX

1VV0301556 Rev. 7

Page 14 of 145

2020-09-25

4. FUNCTIONAL DESCRIPTION

General Functionality and Main Features

The LE910Cx family of cellular modules feature LTE and multi-RAT modem together with an onchip powerful application processor and a rich set of interfaces.

The major functions and features are listed below:

 Multi RAT cellular modem for voice and data communication

o LTE FDD/TDD Cat4 (150/50Mbps DL/UL). o GSM/GPRS/EDGE o WCDMA up to DC HSPA+ Rel. 9 o Support for SIM profile switching

 Digital audio and analog audio codec  Application processor to run customer application code

o 1.2 GHz Cortex-A7 with Linux version 3.18 o Flash + DDR are large enough to allow for customer’s own software applications

 High speed serial interfaces:

o USB, HSIC

 Tools for firmware update (TFI)  Stream download protocol (SDL)  FOTA (Legacy AT FOTA)  SGMII (optional) for external Ethernet transceiver  SDIO for (optional) external Wi-Fi transceiver

Note: The LE910C1-SV/LE910C1-SA/LE910C1-ST don’t support Wi-Fi.

Note: The ThreadX products don’t support HSIC, SGMII and SDIO.

Application system overview

The Application Processor is a 32bit ARM Cortex-A7 up to 1.2GHz running the Linux operating system. The following software is pre-integrated and is running on the application processor:

 32bit Cortex-A7@1.2GHz running the Linux kernel 3.18.  Telit Unified AT command set, backward compatible with LE920, which is the main control

interface to offer features by the non-application-enabled variant, with the following:

o Hayes standard AT command set o ETSI GSM 07.07 specific AT command and GPRS specific commands. o ETSI GSM 07.05 specific AT commands for SMS (Short Message Service) and

CBS (Cell Broadcast Service)

o Control of pre-integrated Firmware Update Agent (Harman) o Antenna diagnostics

 Firmware Over-The-Air (FOTA) update supporting selective update. Backward compatible

with LE910.

 Operator specific Device management client, backward compatible with LE910  SPI device driver for user space access of the SPI device, including slave to master

interrupt, backward compatible with LE910

 GPIO interrupts driver for user space to listen to interrupts on selected user GPIOs,

backward compatible with LE910

 2G/3G/4G and GNSS jamming detection  Audio subsystem, backward compatible with LE910

o PCM digital audio IO o Limited support for DTMF detection.

1VV0301556 Rev. 7

Page 15 of 145

2020-09-25

Partition name

Permission

(MB)

 FTM support, backward compatible with LE910  Vocoder support and processing

o GSM vocoders (EFR/HR/FR), all rates o AMR-NB, AMR-WB, all rates o VoLTE o Configurable noise suppressor, echo canceller and processing chain

 Pre-integrated Wi-Fi driver via SDIO (QualcommA6574)

o USB for point to point connection (virtual COM)

ThreadX products:

 Do not support SDIO.  Do not support SPI interrupt from slave.

4.2.1. Memory configuration

The LE910Cx memory configuration is as follows:

4.2.1.1. LE

 Extended memory: 512Mbyte Flash /256Mbyte DDR  Regular memory: 256Mbyte Flash /256Mbyte DDR  Small memory: 256Mbyte Flash /128Mbyte DDR

4.2.1.2. TX(Thread-X)

 128Mbyte Flash /128Mbyte DDR

4.2.2. Partition Layout

The below tables show the flash storage allocation on a partition basis.

Note: The size of the flash allocation includes the UBI container overhead

(usually at 15% of the partition)

Partitions marked as Telit: They are specific partitions used by Telit.

4.2.2.1. LE

 Extended Memory

Partition size

1VV0301556 Rev. 7

sbl

mibib

telit

Page 16 of 145

1.25

3.25

2020-09-25

efs2

telit

rpm

telit

aboot

telit

boot

telit

modem

telit

recovery

0.5

11.75

0.625

57.875

0.375

11.75

recoveryfs

Customapps

(0x77e0000 ~

0x153e0000)

System

(0x153e0000

0x20000000)

Summary

fota

telit

rootfs

cachefs

usrfs

0.5

10.25

0.5

3.5

220

172.125

512

1VV0301556 Rev. 7

Available memory: about 180 MB is for customer application

(custom apps partition)

Page 17 of 145

2020-09-25

Partition name

Permission

(MB)

 Regular Memory

Partition size

sbl

mibib

telit

efs2

rpm

aboot

boot

telit

modem

telit

recovery

1.25

3.25

0.5

11.75

0.625

57.875

0.375

11.75

recoveryfs

System

(0x71e0000

0x10000000)

Summary

fota

0.5

10.25

telit

rootfs

cachefs

usrfs

0.5

142.125

256

Available memory: about 7 MB is for customer application

1VV0301556 Rev. 7

Page 18 of 145

2020-09-25

Partition name

Permission

Partition size (MB)

Partition name

Permission

Partition size (MB)

 Small Memory

sbl

mibib

telit

efs2

rpm

aboot

boot

telit

modem

telit

recovery

1.25

3.25

0.5

11.75

0.625

47.875

0.375

11.75

fota

recoveryfs

telit

System

(0x71e0000

0x10000000)

rootfs

cachefs

usrfs

Summary

4.2.2.2. TX(Thread-X)

SBL

MIBIB

Telit

0.5

20.25

0.5

142.125

256

1.25

2.75

1VV0301556 Rev. 7

telit

Page 19 of 145

5.5

2020-09-25

Telit

EFS2

telit

DEVCFG

APDP

MSADP

SEC

MBA

ACDB

RPM

telit

0.5

2.25

0.375

0.5

0.25

0.5

0.375

QDSP

APPS

telit

Cache_APPS

Cache_ACDB

misc

sec

Telit

EFS2APPS

Summary

47.25

25.875

0.25

1.25

2.125

5.5

128

4.2.3. RAM memory

 LE910Cx-NF/EU/AP/LA

256Mbyte DDR, of which ~60MB will be available for customers’ application usage.

1VV0301556 Rev. 7

Page 20 of 145

2020-09-25

 LE910C1-SV/SA/ST

128Mbyte DDR, there is no available for customers’ application usage due to small memory.

No support Telit AppZone Linux

4.2.4. Customer application – Storage & configuration

Using the Telit SDK, the customer application would be installed directly into the USRFS (/data is the mountpoint).

The customer application can also be linked to the powerup process onto predefined hookpoints:

 /data/oem_earlystart.sh – This is at order 38 of the rcS (S is for Single user scripts are run

first)

 /data/oemstart.sh - This is at order 43 of the rc5 (5 is for multi-user scripts)  /data/oem_poststart.sh - This is at order 99 of the rc5

Telit rootfs is RO, hence an application cannot be installed into the etc. The above method allows the application to run at powerup. Selecting one of the above methods for application installation should be made based on when the customer wants the application to run during powerup (early, normal and post).

The above scripts should link to the application binary for execution (at least one of them). The installation method as well as build/installation tools should be covered by the Telit LE910C1 SDK document.

Configuration files are stored in three main areas:

1. Telit Linux RO FS. The configuration stored there (mainly in /etc) cannot be changed.

2. Telit RW USER FS (/data). The configuration stored there can be changed by customer

application. Examples are hosts, iproute, wlan etc. Configuration stored there are

persistent, i.e. written to the flash.

3. Telit RW RAM disk (/var/run). This is a FS mounted on the RAM directly, i.e. not persistent.

Examples are DNS, mobile AP and firewall configuration.

Customer applications are installed onto the usrfs storage (/data). This is a RW mountpoint.

The customer application will be automatically linked to the powerup process via predefined scripts in the /data:

 /data/oem_earlystart.sh – This is at order 38 of the rcS (S is for Single user scripts are run

first)

 /data/oemstart.sh - This is at order 43 of the rc5 (5 is for multi-user scripts)  /data/oem_poststart.sh - This is at order 99 of the rc5

The above scripts should be then linked to any customer application that needs to automatically run during the powerup process. Note the order of the scripts, rcS scripts runs first on a Linux machine, rc5 script runs after (43 is first then 99).

1VV0301556 Rev. 7

Page 21 of 145

2020-09-25

4.2.5. Power up time

4.2.5.1. LE

The following measurements were taken using a special perf build.

Non-secured device:

1. Entering kernel: 0.712747

2. Entering user space: 0.742889

3. Entering customer application: 11.046918

4. Modem out of reset: 13.774010

4.2.5.2. TX(Thread-X)

1. AT On: about 9 seconds.

4.2.6. Power up sequence

The following figure explains the LE910Cx powerup sequence.

4.2.7. Location Subsystem

The following key features are offered by the Location subsystem:

 Support for GPS, GLONASS, BeiDou/Compass Phase II, Galileo and QZSS  Supports following Satellite Based Augmentation Systems (SBAS): WAAS, EGNOS,

MSAS (only tracked for cross correlation improvement)

 Receiver Autonomous Integrity Monitoring (RAIM) & Fault Detection and Exclusion (FDE)

support, internal in the receiver.

 Support of assistance data (Ephemerides, location, time...) provided by customer

application to ensure faster Time To First Fix (TTFF) through SUPL and LTO injection

 Periodic pulse output for synchronization to GPS system clock  NMEA-0183 output on USB

4.2.8. Application development environment

Please refer to the Telit AppZone Linux documentation in the link, below

1VV0301556 Rev. 7

Page 22 of 145

2020-09-25

https://s3.amazonaws.com/site_support/Telit/AppZone-SDK/v4/AppZone_Guide/az-linuxuser-guide/index.html

Telit AppZone Linux is not available on LE910C1-SA, LE910C1-ST, LE910C1-SV

products, which have small memory,128Mbyte DDR and there is no RAM space for

customer application.

4.2.9. Random number generator

The LE910Cx RNG is based on FIPS-140-2 PRNG (aka hw_drbg), seeded with QC designed hw entropy unit

consisting of the ring oscillator (RO) noise source.

There are several Linux devices to generate random numbers (under the /dev node):

1. hw_random – This is an HW random number generator, this is the preferred device to get random data from.

2. random – This is, in most cases, a SW random generator. Linux kernel itself (on latest kernel versions >= msm-3.18) adds HW random data to /dev/random if randomness is not sufficient from SW RNG. Random will block if no sufficient randomness is built up.

3. urandom – This device doesn’t care if not enough randomness exists and is not recommended for use unless the quality of the RNG is not in concern (this device will probably work faster).

The number of entropies used for the RNG can be checked, and modified, with the following sysfs:

/sys/module/rng_core/parameters/current_quality

Max value is 1024.

An example for reading random bytes from the hw_random:

4.2.10. Wake up Events

The Telit Modules provide a function that reduces the power consumption during the period when they are in IDLE state (waiting for a call), allowing a longer activity with a given battery capacity.

The power saving function can be configured in several modes in accordance with the user needs.

In accordance with the response of the AT+CFUN=? Command, you can know the Power Saving Modes supported by Telit Module, refer to AT Commands Reference Guide for more details.

In power saving mode with CFUN=5, UART AT interface disabled. URC is not displayed, and it stored in the buffer on UART AT interface. It flushed to DTE when modem device exit power saving mode by <DTR=ON>

AT#PSMRI=<duration time> must be configured as non-zero value. It enables RI with the specified time if URC event happened during power saving mode with CFUN=5.

1VV0301556 Rev. 7

Page 23 of 145

2020-09-25

The power saving function can be waked up in several event as follows:

CFUN=0 CFUN=4 CFUN=5

Wake up Events

Unsolicited Result

Code

Incoming voice call

Incoming data

call(VoLTE)

Incoming SMS

AT+CNMI=0,0, ...

Incoming SMS

AT+CNMI=1,1, ...

Module enters NONCYCLIC SLEEP mode

The new mode depends on URC

Incoming call is managed, RING is displayed. The module exits power saving state and enters CFUN=1 mode.

Incoming SMS is managed, URC is not displayed. The module stays in power saving state in CFUN=0 mode.

Incoming SMS is managed, URC is displayed. The module exits power saving state and enters CFUN=1 mode.

Module performs network deregistration and SIM deactivation. TX and RX are disabled

The new mode depends on URC

N/A

The power saving is enabled. DTR is used to exit/enter power saving.

AT#PSMRI must be configured as non-zero value to get URC event via RI.

The new mode depends on URC.

Incoming call is managed. RI toggle. DTR is used to exit/ enter power saving state in CFUN=5 mode

Incoming SMS is managed, URC is not displayed. DTR is used to exit/enter power saving state in CFUN=5 mode.

Incoming SMS is managed. DTR is used to exit/ enter power saving state in CFUN=5 mode. URC is displayed when modem device exit power saving mode

Incoming GPRS

packet

RTC alarm CFUN=1 CFUN=4 CFUN=5

RTS toggling CFUN=1 N/A N/A

CFUN=0 N/A CFUN=5

 Since RTS toggle event periodically checks pin status in CFUN=0 mode, in

worst case, it may take up to around 1 second for the module to wake up.

 LE910C1-EU(4G+2G) does not allow power saving mode because HSIC

configuration of LE910C1-EU(4G+2G) is master mode. To support power

saving mode, HSIC configuration need to be disabled by #HSICEN=0

(Manual reboot is required) or please refer to section 4.2.17

1VV0301556 Rev. 7

Page 24 of 145

2020-09-25

4.2.10.1. Wake up Event Examples

4.2.10.1.1. CFUN=0: Call, SMS, #QSS, +CALA

Example 1

The wake-up event is an incoming call. Starting control line configuration, UART AT interface is enabled. <DSR=ON>, RI=OFF, DCD=OFF, <CTS=ON>, RTS=ON, DTR=ON

Type in CFUN=0, the module enters NON-CYCLIC SLEEP mode. AT+CFUN=0 OK

Here is the new control line configuration. The module is in power saving. <DSR=OFF>, RI=OFF, DCD=OFF, <CTS=OFF>, RTS=ON, DTR=ON An incoming call is arrived.

RING

Here is the new control line configuration. The module is no longer in power saving. <DSR=ON>, RI=ON, DCD=OFF, <CTS=ON>, RTS=ON, DTR=ON

RING

Check the current CFUN.

AT+CFUN?

+CFUN: 1  the module is in full functionality mode OK

RING

Hang up the call. ATH OK

Here is the new control line configuration. <DSR=ON>, RI=OFF, DCD=OFF, <CTS=ON>, RTS=ON, DTR=ON

Example 2

The wake-up event is a SMS receiving.

Enable URC created by the SMS receiving. AT+CNMI=1,1,0,0,0 OK

Starting control line configuration, UART AT interface is enabled. <DSR=ON>, RI=OFF, DCD=OFF, <CTS=ON>, RTS=ON, DTR=ON Type in CFUN=0, the module enters NON-CYCLIC SLEEP mode.

AT+CFUN=0

1VV0301556 Rev. 7

Page 25 of 145

2020-09-25

Here is the new control line configuration. The module is in power saving. <DSR=OFF>, RI=OFF, DCD=OFF, <CTS=OFF>, RTS=ON, DTR=ON

A SMS is arrived. +CMTI: "SM",17

Here is the new control line configuration. The module is no longer in power saving. <DSR=ON>, RI=OFF, DCD=OFF, <CTS=ON>, RTS=ON, DTR=ON

Check the current CFUN.

AT+CFUN?

+CFUN: 1  the module is in full functionality mode OK

Example 3

The wake-up event is the #QSS URC.

Starting control line configuration, UART AT interface is enabled. <DSR=ON>, RI=OFF, DCD=OFF, <CTS=ON>, RTS=ON, DTR=ON

Enable Query SIM Status URC. AT#QSS=1 OK

Type in CFUN=0, the module enters NON-CYCLIC SLEEP mode. AT+CFUN=0 OK

Here is the new control line configuration. The module is in power saving. <DSR=OFF>, RI=OFF, DCD=OFF, <CTS=OFF>, RTS=ON, DTR=ON Extract the SIM. After a while, the DTE displays the following URC:

#QSS:0

Here is the new control line configuration. The module is no longer in power saving. <DSR=ON>, RI=OFF, DCD=OFF, <CTS=ON>, RTS=ON, DTR=ON

Check the current CFUN mode.

AT+CFUN?

+CFUN: 1  the module is in full functionality mode

Example 4

+CALA URC event forces the module in CFUN=1 mode. Starting control line configuration, UART AT interface is enabled. <DSR=ON>, RI=OFF, DCD=OFF, <CTS=ON>, RTS=ON, DTR=ON

Set the clock AT+CCLK="08/05/16,09:20:30+00" OK

Set when the alarm wakes up: in two minutes (it is just an example).

1VV0301556 Rev. 7

Page 26 of 145

2020-09-25

AT+CALA="08/05/16,09:22:30+00",0,2,"ALARM, ALARM, ALARM" OK

Type in CFUN=0, the module enters NON-CYCLIC SLEEP mode. AT+CFUN=0 OK

Here is the new control line configuration. The module is in power saving. <DSR=OFF>, RI=OFF, DCD=OFF, <CTS=OFF>, RTS=ON, DTR=ON

During the ALARM waiting, the module is in power saving and UART AT interface is disabled. When the alarm wakes up, the DTE displays the URCs. The module exits power saving in CFUN=0 mode and enters CFUN=1 mode.

+CALA: ALARM, ALARM, ALARM

Here is the new control line configuration. <DSR=ON>, RI=OFF, DCD=OFF, <CTS=ON>, RTS=ON, DTR=ON

+CALA: ALARM, ALARM, ALARM

Check the alarm mode

AT#WAKE?

#WAKE: 1  the module is in alarm mode

+CALA: ALARM, ALARM, ALARM

Check the current CFUN. AT+CFUN? +CFUN: 1  the module is in full functionality mode OK

+CALA: ALARM, ALARM, ALARM

After 90 sec, the module exits alarm mode.

Check the alarm mode.

AT#WAKE?

#WAKE: 0  the module exited alarm mode

4.2.10.1.2. CFUN=4: #QSS, +CALA

Example 1

#QSS URC event leaves the module in CFUN=4 mode. Starting control line configuration, UART AT interface is enabled. <DSR=ON>, RI=OFF, DCD=OFF, <CTS=ON>, RTS=ON, DTR=ON

1VV0301556 Rev. 7

Page 27 of 145

2020-09-25

Type in CFUN=4, the module performs network deregistration, and SIM deactivation. AT+CFUN=4 OK

Control line configuration is not changed. <DSR=ON>, RI=OFF, DCD=OFF, <CTS=ON>, RTS=ON, DTR=ON Enable Query SIM Status URC. AT#QSS=1 OK

Extract the SIM. The URC does not arrive because CFUN=4 mode deactivates the SIM. The module stays in CFUN=4 mode. AT+CFUN? +CFUN: 4 OK

Example 2

+CALA URC event leaves the module in CFUN=4 mode. Starting control line configuration, UART AT interface is enabled. <DSR=ON>, RI=OFF, DCD=OFF, <CTS=ON>, RTS=ON, DTR=ON

Set the clock AT+CCLK="08/05/16,09:20:30+00" OK Set when the alarm wakes up: in two minutes (it is just an example). AT+CALA="08/05/16,09:22:30+00",0,2,"ALARM, ALARM, ALARM" OK

Type in CFUN=4, the module performs network deregistration, and SIM deactivation. AT+CFUN=4 OK

Control line configuration is not changed <DSR=ON>, RI=OFF, DCD=OFF, <CTS=ON>, RTS=ON, DTR=ON

When the alarm wakes up, the DTE displays the URCs.

+CALA: ALARM, ALARM, ALARM

Control line configuration is not changed. <DSR=ON>, RI=OFF, DCD=OFF, <CTS=ON>, RTS=ON, DTR=ON

+CALA: ALARM, ALARM, ALARM

Check the alarm mode

AT#WAKE?

#WAKE: 1  the module is in alarm mode

+CALA: ALARM, ALARM, ALARM

The module does not change CFUN mode. AT+CFUN? +CFUN: 4

1VV0301556 Rev. 7

Page 28 of 145

2020-09-25

+CALA: ALARM, ALARM, ALARM

After 90 sec, the module exits alarm mode.

Check the alarm mode.

AT#WAKE?

#WAKE: 0  the module exited alarm mode

The module does not change CFUN mode. AT+CFUN? +CFUN: 4 OK

4.2.10.1.3. CFUN=5: Call, SMS, +CALA

Example 1

The wake-up event is an incoming call. Starting control line configuration, UART AT interface is enabled. <DSR=ON>, RI=OFF, DCD=OFF, <CTS=ON>, RTS=ON, DTR=ON

Force the module in CFUN=5 mode, the power saving is enabled. AT+CFUN=5 OK

Control line configuration does not change, UART AT interface is still enabled. <DSR=ON>, RI=OFF, DCD=OFF, <CTS=ON>, RTS=ON, DTR=ON

Force the module in power saving. DTR  OFF

The module is in power saving, and UART AT interface is disabled. <DSR=OFF>, RI=OFF, DCD=OFF, <CTS=OFF>, RTS=ON, DTR=OFF An incoming call is arrived

Here is the new control line configuration: RI=ON <DSR=OFF>, RI=ON, DCD=OFF, <CTS=OFF>, RTS=ON, DTR=OFF

Exit power saving, and UART AT interface is enabled

DTR  ON

<DSR=ON>, RI=ON, DCD=OFF, <CTS=ON>, RTS=ON, DTR=ON The module exits power saving, but stays in CFUN=5 mode.

AT+CFUN? +CFUN:5 OK

1VV0301556 Rev. 7

Page 29 of 145

2020-09-25

RING

Hang up the call. ATH OK

Enter power saving. DTR  OFF

The module enters again the power saving mode, and UART AT interface is disabled. <DSR=OFF>, RI=OFF, DCD=OFF, <CTS=OFF>, RTS=ON, DTR=OFF

Example 2

The wake-up event is a SMS receiving.

Enable URC created by the SMS receiving. AT+CNMI=1,1,0,0,0 OK

Set AT#PSMRI to get URC event during power saving mode

AT#PSMRI=1000

Starting control line configuration, UART AT interface is enabled. <DSR=ON>, RI=OFF, DCD=OFF, <CTS=ON>, RTS=ON, DTR=ON

Force the module in CFUN=5 mode, the power saving is enabled. AT+CFUN=5 OK

Control line configuration does not change, UART AT interface is still enabled. <DSR=ON>, RI=OFF, DCD=OFF, <CTS=ON>, RTS=ON, DTR=ON

Force the module in power saving. DTR  OFF

The module is in power saving and UART AT interface is disabled. <DSR=OFF>, RI=OFF, DCD=OFF, <CTS=OFF>, RTS=ON, DTR=OFF

A SMS is arrived and it stored in the buffer on UART AT interface and RI is ON during 1 sec <DSR=OFF>, RI=ON, DCD=OFF, <CTS=OFF>, RTS=ON, DTR=OFF

The module is still in power saving and UART AT interface is disabled. <DSR=OFF>, RI=OFF, DCD=OFF, <CTS=OFF>, RTS=ON, DTR=OFF Exit power saving, and AT interface enabled. The buffered URC displayed DTR  ON

+CMTI: "SM",17

<DSR=ON>, RI=OFF, DCD=OFF, <CTS=ON>, RTS=ON, DTR=ON

1VV0301556 Rev. 7

Page 30 of 145

2020-09-25

+ 115 hidden pages

Telit LE910Cx User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual