Daniel Lee / Mbed OS mbed-os-example-cellular-le910

This is an example based on mbed-os cellular APIs that demonstrates a TCP or UDP echo transaction with a public echo server.

This code is forked from https://os.mbed.com/teams/mbed-os-examples/code/mbed-os-example-cellular/

This is an example showing how to use Skywire board with LE910-x module.

In this example, I had used the LE910-EUG module for 4G communication. Mbed OS code wasn't changed for LE910-x, because the Telit' HE910 is included mainline code on Mbed OS already. HE910 and LE910 are most similar. Therefore you can use LE910 via HE910 driver. Please check to configure of mbed_app.json, and initialize code for Skywire board of main.cpp.

Open mbed_app.json, you need to define a UART for the MCU to communicate with the xE910 module.

            "TELIT_HE910.tx"                 : "D1",
            "TELIT_HE910.rx"                 : "D0",
            "TELIT_HE910.provide-default"    : true

If you are using Pelion CM, make the following settings:

            "nsapi.default-cellular-apn"     : "\"stream.co.uk\"",
            "nsapi.default-cellular-username": "\"streamip\"",
            "nsapi.default-cellular-password": "\"streamip\"",

For your information, please see Pelion Connectivity Quick start guide.

320

You can find Skywire sensor shield information though NimbeLink site.

Tested with

  • DISCO_L475VG_IOT01A
  • K64F

1. Import the application into your desktop:

 mbed import https://os.mbed.com/users/Daniel_Lee/code/mbed-os-example-cellular-le910/

 cd mbed-os-example-cellular-le910

2. Compile and program:

mbed compile -t GCC_ARM -m DISCO_L475VG_IOT01A

(supported toolchains : GCC_ARM / ARM / IAR)

3. Download binary to a target board

4. Result

mbed-os-example-cellular


Built: Feb  7 2020, 07:02:27
Starting Skywire board with LE910-EUG Demo...
Waiting for Skywire to Boot...
Wait 15 seconds..
Establishing connection


Connection Established.
TCP: connected with echo.mbedcloudtesting.com server
TCP: Sent 4 Bytes to echo.mbedcloudtesting.com
Received from echo server 4 Bytes


Success. Exiting

README.md@6:5678c0b6f74e, 2018-05-10 (annotated)

Committer:
mbed_official
Date:
Thu May 10 05:17:02 2018 +0100
Revision:
6:5678c0b6f74e
Parent:
2:0f644d6045cf
Child:
11:23ea0907186e
Merge pull request #63 from ARMmbed/adding_trace_support_and_bug_fixes



Added trace support.

.

Commit copied from https://github.com/ARMmbed/mbed-os-example-cellular

Who changed what in which revision?

UserRevisionLine numberNew contents of line
mbed_official 0:4611f6cf2413 1 # Example cellular application for Mbed OS
mbed_official 0:4611f6cf2413 2
mbed_official 0:4611f6cf2413 3 This is an example based on `mbed-os` cellular APIs that demonstrates a TCP or UDP echo transaction with a public echo server.
mbed_official 0:4611f6cf2413 4
mbed_official 0:4611f6cf2413 5 ## Getting started
mbed_official 0:4611f6cf2413 6
mbed_official 0:4611f6cf2413 7 This particular cellular application uses a cellular network and network-socket APIs that are part of [`mbed-os`](https://github.com/ARMmbed/mbed-os).
mbed_official 0:4611f6cf2413 8
mbed_official 0:4611f6cf2413 9 The program uses a [generic cellular modem driver](https://github.com/ARMmbed/mbed-os/tree/master/features/netsocket/cellular/generic_modem_driver) using an external IP stack (LWIP) standard 3GPP AT 27.007 AT commands to setup the cellular modem and registers to the network.
mbed_official 0:4611f6cf2413 10
mbed_official 0:4611f6cf2413 11 After registration, the driver opens a point-to-point protocol (PPP) pipe using LWIP with the cellular modem and connects to internet. This driver currently supports UART data connection type only between your cellular modem and MCU.
mbed_official 0:4611f6cf2413 12
mbed_official 0:4611f6cf2413 13 For more information on Arm Mbed OS cellular APIs and porting guide, please visit the [Mbed OS cellular API](https://os.mbed.com/docs/latest/reference/cellular-api.html) and [contributing documentation](https://os.mbed.com/docs/latest/reference/contributing-connectivity.html#cellularinterface).
mbed_official 0:4611f6cf2413 14
mbed_official 0:4611f6cf2413 15 ### Download the application
mbed_official 0:4611f6cf2413 16
mbed_official 0:4611f6cf2413 17 ```sh
mbed_official 0:4611f6cf2413 18 $ mbed import mbed-os-example-cellular
mbed_official 0:4611f6cf2413 19 $ cd mbed-os-example-cellular
mbed_official 0:4611f6cf2413 20
mbed_official 0:4611f6cf2413 21 #OR
mbed_official 0:4611f6cf2413 22
mbed_official 0:4611f6cf2413 23 $ git clone git@github.com:ARMmbed/mbed-os-example-cellular.git
mbed_official 0:4611f6cf2413 24 $ cd mbed-os-example-cellular
mbed_official 0:4611f6cf2413 25 ```
mbed_official 0:4611f6cf2413 26
mbed_official 0:4611f6cf2413 27 ### Change the network and SIM credentials
mbed_official 0:4611f6cf2413 28
mbed_official 0:4611f6cf2413 29 See the file `mbed_app.json` in the root directory of your application. This file contains all the user specific configurations your application needs. Provide the pin code for your SIM card, as well as any APN settings if needed. For example:
mbed_official 0:4611f6cf2413 30
mbed_official 0:4611f6cf2413 31 ```json
mbed_official 0:4611f6cf2413 32 "sim-pin-code": {
mbed_official 0:4611f6cf2413 33 "help": "SIM PIN code",
mbed_official 0:4611f6cf2413 34 "value": "\"1234\""
mbed_official 0:4611f6cf2413 35 },
mbed_official 0:4611f6cf2413 36 "apn": {
mbed_official 0:4611f6cf2413 37 "help": "The APN string to use for this SIM/network, set to 0 if none",
mbed_official 0:4611f6cf2413 38 "value": "\"internet\""
mbed_official 0:4611f6cf2413 39 },
mbed_official 0:4611f6cf2413 40 "username": {
mbed_official 0:4611f6cf2413 41 "help": "The user name string to use for this APN, set to zero if none",
mbed_official 0:4611f6cf2413 42 "value": 0
mbed_official 0:4611f6cf2413 43 },
mbed_official 0:4611f6cf2413 44 "password": {
mbed_official 0:4611f6cf2413 45 "help": "The password string to use for this APN, set to 0 if none",
mbed_official 0:4611f6cf2413 46 "value": 0
mbed_official 0:4611f6cf2413 47 }
mbed_official 6:5678c0b6f74e 48 ```
mbed_official 0:4611f6cf2413 49
mbed_official 0:4611f6cf2413 50 ### Selecting socket type (TCP or UDP)
mbed_official 0:4611f6cf2413 51
mbed_official 0:4611f6cf2413 52
mbed_official 6:5678c0b6f74e 53 You can choose which socket type the application should use; however, please note that TCP is a more reliable transmission protocol. For example:
mbed_official 0:4611f6cf2413 54
mbed_official 0:4611f6cf2413 55
mbed_official 0:4611f6cf2413 56 ```json
mbed_official 0:4611f6cf2413 57
mbed_official 0:4611f6cf2413 58 "sock-type": "TCP",
mbed_official 0:4611f6cf2413 59
mbed_official 0:4611f6cf2413 60 ```
mbed_official 0:4611f6cf2413 61
mbed_official 0:4611f6cf2413 62 ### Turning modem AT echo trace on
mbed_official 0:4611f6cf2413 63
mbed_official 0:4611f6cf2413 64 If you like details and wish to know about all the AT interactions between the modem and your driver, turn on the modem AT echo trace. Set the `modem_trace` field value to be true.
mbed_official 0:4611f6cf2413 65
mbed_official 0:4611f6cf2413 66 ```json
mbed_official 0:4611f6cf2413 67 "modem_trace": {
mbed_official 0:4611f6cf2413 68 "help": "Turns AT command trace on/off from the cellular modem, defaults to off",
mbed_official 0:4611f6cf2413 69 "value": true
mbed_official 0:4611f6cf2413 70 },
mbed_official 0:4611f6cf2413 71 ```
mbed_official 0:4611f6cf2413 72
mbed_official 6:5678c0b6f74e 73 ### Turning on the tracing and trace level
mbed_official 6:5678c0b6f74e 74
mbed_official 6:5678c0b6f74e 75 If you like to add more traces or follow the current ones you can turn traces on by changing `mbed-trace.enable` in mbed_app.json
mbed_official 6:5678c0b6f74e 76
mbed_official 6:5678c0b6f74e 77 ```"target_overrides": {
mbed_official 6:5678c0b6f74e 78 "*": {
mbed_official 6:5678c0b6f74e 79 "target.features_add": ["LWIP", "COMMON_PAL"],
mbed_official 6:5678c0b6f74e 80 "mbed-trace.enable": false,
mbed_official 6:5678c0b6f74e 81 ```
mbed_official 6:5678c0b6f74e 82
mbed_official 6:5678c0b6f74e 83 After you have defined `mbed-trace.enable: true`, you can set trace levels by changing value in `trace-level`
mbed_official 6:5678c0b6f74e 84
mbed_official 6:5678c0b6f74e 85 ```"trace-level": {
mbed_official 6:5678c0b6f74e 86 "help": "Options are TRACE_LEVEL_ERROR,TRACE_LEVEL_WARN,TRACE_LEVEL_INFO,TRACE_LEVEL_DEBUG",
mbed_official 6:5678c0b6f74e 87 "macro_name": "MBED_TRACE_MAX_LEVEL",
mbed_official 6:5678c0b6f74e 88 "value": "TRACE_LEVEL_INFO"
mbed_official 6:5678c0b6f74e 89 }
mbed_official 6:5678c0b6f74e 90 ```
mbed_official 6:5678c0b6f74e 91
mbed_official 0:4611f6cf2413 92 ### Board support
mbed_official 0:4611f6cf2413 93
mbed_official 0:4611f6cf2413 94 The [generic cellular modem driver](https://github.com/ARMmbed/mbed-os/tree/master/features/netsocket/cellular/generic_modem_driver) this application uses was written using only a standard AT command set. It uses PPP with an Mbed-supported external IP stack. These abilities make the driver essentially generic, or nonvendor specific. However, this particular driver is for onboard-modem types. In other words, the modem exists on the Mbed Enabled target as opposed to plug-in modules (shields). For more details, please see our [Mbed OS cellular documentation](https://os.mbed.com/docs/latest/reference/cellular-api.html).
mbed_official 0:4611f6cf2413 95
mbed_official 0:4611f6cf2413 96 Examples of Mbed Enabled boards with onboard modem chips include [u-blox C027](https://os.mbed.com/platforms/u-blox-C027/) and [MultiTech MTS Dragonfly](https://os.mbed.com/platforms/MTS-Dragonfly/).
mbed_official 0:4611f6cf2413 97
mbed_official 0:4611f6cf2413 98 ## Compiling the application
mbed_official 0:4611f6cf2413 99
mbed_official 0:4611f6cf2413 100 Use Mbed CLI commands to generate a binary for the application. For example, in the case of GCC, use the following command:
mbed_official 0:4611f6cf2413 101
mbed_official 0:4611f6cf2413 102 ```sh
mbed_official 0:4611f6cf2413 103 $ mbed compile -m YOUR_TARGET_WITH_MODEM -t GCC_ARM
mbed_official 0:4611f6cf2413 104 ```
mbed_official 0:4611f6cf2413 105
mbed_official 0:4611f6cf2413 106 ## Running the application
mbed_official 0:4611f6cf2413 107
mbed_official 0:4611f6cf2413 108 Drag and drop the application binary from `BUILD/YOUR_TARGET_WITH_MODEM/GCC_ARM/mbed-os-example-cellular.bin` to your Mbed Enabled target hardware, which appears as a USB device on your host machine.
mbed_official 0:4611f6cf2413 109
mbed_official 0:4611f6cf2413 110 Attach a serial console emulator of your choice (for example, PuTTY, Minicom or screen) to your USB device. Set the baudrate to 115200 bit/s, and reset your board by pressing the reset button.
mbed_official 0:4611f6cf2413 111
mbed_official 0:4611f6cf2413 112 You should see an output similar to this:
mbed_official 0:4611f6cf2413 113
mbed_official 0:4611f6cf2413 114 ```
mbed_official 2:0f644d6045cf 115 mbed-os-example-cellular
mbed_official 6:5678c0b6f74e 116 Establishing connection ......
mbed_official 2:0f644d6045cf 117
mbed_official 0:4611f6cf2413 118 Connection Established.
mbed_official 2:0f644d6045cf 119 TCP: connected with echo.mbedcloudtesting.com server
mbed_official 2:0f644d6045cf 120 TCP: Sent 4 Bytes to echo.mbedcloudtesting.com
mbed_official 0:4611f6cf2413 121 Received from echo server 4 Bytes
mbed_official 2:0f644d6045cf 122
mbed_official 2:0f644d6045cf 123
mbed_official 0:4611f6cf2413 124 Success. Exiting
mbed_official 0:4611f6cf2413 125 ```
mbed_official 0:4611f6cf2413 126
mbed_official 0:4611f6cf2413 127 ## Troubleshooting
mbed_official 0:4611f6cf2413 128
mbed_official 0:4611f6cf2413 129 If you have problems, you can review the [documentation](https://os.mbed.com/docs/latest/tutorials/debugging.html) for suggestions on what could be wrong and how to fix it.