Thales' cellular IoT products business is now part of Telit Cinterion, find out more.

You are here

Telit Cinterion IoT Developer Community

IoT SDK Bootcamp

Showcase, December 8, 2022 - 3:30am, 180 views

A Series of Embedded Processing Modem Modules

PLS83/63, ELS82/62 and TX82/62 modules have a capability to run user applications. It's runtime environment is ThreadX+Cinterion libraries, and you can use the IoT SDK to create applications for it. In this article, you'll learn how to create certificate for the SDK, how to sign the compiled binary, and run the application.

You can find all files mentioned in this cloud storage:

Password: Thales2022

Needed Software

IoT SDK itself: SDKv5.tgz

OpenSSL for Windows

Python 2.7.18

Python libraries: Pyserial, Numpy

cmd_IpCertMgr from plsx3_an62_tls_v01.pdf

TAR, GZIP, 7zip



Java 1.8

You should install all mentioned software packages, and use python -m pip install pyserial numpy to configure the python runtime prior to use the IoT SDK itself.

Test Run the IoT SDK

Let's assume you unpack the IoT SDK in c:\SDK, and connected PLS83-W to the USB; assuming the modem port of PLS83 is enumerated in COM57. You can run these commands under Windows Command Prompt:

C:\Users\<USERNAME>>cd c:\SDK\tools

c:\SDK\tools>python -p COM57
Connection with the target on COM57 at 115200
Done !

c:\SDK\tools>python info
Modem version (rev): 02.000
Applicative version (arn): 01.000.00
Bootloader version (sbl): SBL1_005

Setup App Root Certificate

You need to have root certificate to sign app before testing it inside the modem. To achieve this, use the openssl software installed previously; let's assum we decide to store the certificate and key pairs inside c:\SDK\key, to setup app root certificate, run these commands in Windows Command Prompt:

C:\SDK>md key
C:\SDK>cd key

C:\SDK\key>openssl ecparam -name secp384r1 -out secp384r1.param.pem
C:\SDK\key>openssl ecparam -in secp384r1.param.pem -genkey -noout -out app_rot.key
C:\SDK\key>openssl ec -in app_rot.key -out -pubout
C:\SDK\key>openssl req -new -sha384 -x509 -out app_rot.der -outform DER -key app_rot.key -days 7300 -set_serial 1 -subj /C=DE/ST=Berlin/L=Berlin/O="THALES DIS AIS Deutschland GmbH"/OU="R&D"/CN="Demo App Root of Trust"
openssl x509 -in app_rot.der -inform DER -pubkey -noout >

We have the certificate now, but we need to convert the files into something suitable to install to PLS83. Let's assume we store the cmd_IpCertMgr.jar tool in z:\projs\pls83\pls63-w_pls83- w_tls_tools\Tools\bin\win-x86\cmd_IpCertMgr.jar, run these commands to create certificate files for PLS83 modem:

C:\SDK\key>java -jar "z:\projs\pls83\pls63-w_pls83- w_tls_tools\Tools\bin\win-x86\cmd_IpCertMgr.jar" ***** app_rot -cmd WriteCert -certfile app_rot.der -certindex 0 -sigType NONE -file LoadAppRotCert.bin
Java version: 32-bit
signature skipped

c:\SDK\key>java -jar "z:\projs\pls83\pls63-w_pls83- w_tls_tools\Tools\bin\win-x86\cmd_IpCertMgr.jar" ***** app_rot -cmd DelCert -certfile app_rot.der -certindex 0 -sigType NONE -file DelAppRotCert.bin
Java version: 32-bit
signature skipped

Now we have certificate files for modem, it's time to install them to the PLS83-W. Use tool like TeraTerm to connect to PLS83's modem port, and run these commands to install and check the certificate installation status:

^SSECUC: "SEC/****",0





^SBNR: 0, size: "661", issuer: "/C=DE/ST=Berlin/L=Berlin/O=THALES DIS AIS Deutschland GmbH/OU=R&D/CN=Demo App Root of Trust", serial number: "01", subject: "/C=DE/ST=Berlin/L=Berlin/O=THALES DIS AIS Deutschland GmbH/OU=R&D/CN=Demo App Root of Trust", signature: "sha384ECDSA", thumbprint algorithm: "sha1", thumbprint: "ECB24246F23C3FF6D59F7C1EC90E9E84A68FF478", expiry date: "2042,1,17"


Test the IoT SDK

Now the foundation has laid out, we can test run any apps inside the modem. Use Windows Command Prompt to run these commands and have run and happy codding:

cd ..\tools

C:\SDK\tools>python -p pls ..\examples\helloworld\

C:\SDK\tools>python sign --key ..\key\app_rot.key ..\examples\helloworld\build\helloworld.bin
Signed application available: C:\SDK\examples\helloworld\build\signed\helloworld.bin

C:\SDK\tools>python verify --pubkey ..\key\ --keyform pem ..\examples\helloworld\build\signed\helloworld.bin
Verification OK

C:\SDK\tools>python download ..\examples\helloworld\build\signed\helloworld.bin
Sent 100 %
Done !

C:\SDK\tools>python ls a:/

C:\SDK\tools>python install helloworld
Done !

C:\SDK\tools>python info
Applications in A disk:
Name                Version     Size      Location

Installed applications:
Name                Version     Size      Status
helloworld          7370        14.2 KB   stopped

1 application on target, 0 running
Autostart config: disabled
Secure boot: enabled
App signature config: ECC with sha384

C:\SDK\tools>python start helloworld
Done !

C:\SDK\tools>python stop helloworld
Done !

C:\SDK\tools>python read -d COM56
Cinterion Logging Tool ++++++++++++++++++++++++++++++++++++++++++++++++++++++
Start logging on dedicated logging port (COM56,115200) at 2022-01-21 20:11:15... (use Control-C to exit)
Hello World!
03:09:21:734 CRIT:..\examples\helloworld\helloworld.c,74: cleanup: MY CLEANUP
Hello World!
03:09:31:113 CRIT:..\examples\helloworld\helloworld.c,74: cleanup: MY CLEANUP

C:\SDK\tools>python logstart helloworld
Cinterion Logging Tool ++++++++++++++++++++++++++++++++++++++++++++++++++++++
Start logging on dedicated logging port (COM56,115200) at 2022-01-21 20:14:33... (use Control-C to exit)
Hello World!

Thank you for this tutorial!

You mentioned the ELS62 as well. Does this mean that the SDK and corresponding FW are available for the ELS62? Is MicroEJ available, as well?



Hi Felix,

MicroEJ is applicable to all Cinterion ThreadX modules.

For ELS62 the threadx SDK is still in development, when it's done, user should be able to use threadx or microej on it.

Best Regards,
Antony Shen

You also mentioned the ELS62. Does this imply that the SDK and related FW for the ELS62 are now available? Is MicroEJ also available? idle breakout


antonyshen's picture