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

Getting started

This particular cellular application uses a cellular network and network-socket APIs that are part of mbed-os.

The program uses a generic cellular modem driver using an external IP stack (LWIP) and standard 3GPP AT 27.007 AT commands to setup the cellular modem and to register to the network.

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.

For more information on Arm Mbed OS cellular APIs and porting guide, please visit the Mbed OS cellular API and contributing documentation.

Download the application

$ mbed import mbed-os-example-cellular
$ cd mbed-os-example-cellular


$ git clone
$ cd mbed-os-example-cellular

Change the network and SIM credentials

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:

        "sim-pin-code": {
            "help": "SIM PIN code",
            "value": "\"1234\""
        "apn": {
            "help": "The APN string to use for this SIM/network, set to 0 if none",
            "value": "\"internet\""
        "username": {
            "help": "The user name string to use for this APN, set to zero if none",
            "value": 0
        "password": {
            "help": "The password string to use for this APN, set to 0 if none",
            "value": 0

Selecting socket type (TCP or UDP)

You can choose which socket type the application should use; however, please note that TCP is a more reliable tranmission protocol. For example:

     "sock-type": "TCP",

Turning modem AT echo trace on

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.

        "modem_trace": {
            "help": "Turns AT command trace on/off from the cellular modem, defaults to off",
            "value": true

Board support

The generic cellular modem driver was written using the standard 3GPP AT 27.007 command set. It uses PPP mode with an Mbed-supported external IP stack, and therefore the modem has to support the PPP mode. For more details, please see our Mbed OS cellular documentation.

Compiling the application

Use Mbed CLI commands to generate a binary for the application. For example, in the case of GCC, use the following command:

$ mbed compile -m YOUR_TARGET_WITH_MODEM -t GCC_ARM

Running the application

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.

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.

You should see an output similar to this:

Establishing connection ...... 

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

Success. Exiting


If you have problems, you can review the documentation for suggestions on what could be wrong and how to fix it.

Files at this revision

API Documentation at this revision

Fri Sep 14 12:30:21 2018 +0100
Commit message:
Merge branch 'adbridge-master'

Commit copied from

Changed in this revision

mbed-os.lib Show annotated file Show diff for this revision Revisions of this file
--- a/mbed-os.lib	Wed Sep 12 13:00:22 2018 +0100
+++ b/mbed-os.lib	Fri Sep 14 12:30:21 2018 +0100
@@ -1,1 +1,1 @@