SUNGTAE KIM
Set specific IP Address/Port
Overview
This code could be access via Cat.M1(BG96 module) of SK telecom network in Korea. Need a WIZnet IoT Shield BG96 board and development board. The code forked Daniel_Lee's mbed-os-example-cellular-BG96 repository(https://os.mbed.com/users/Daniel_Lee/code/mbed-os-example-cellular-BG96/) and added some features.
This example is known to work great on the following platforms:
Requirement
- FRDM-K64F or FRDM-K66F
- WIZnet IoT Shield BG96 board
- USIM card
Example functionality
This example showcases the following device functionality:
1. Import into Compiler
2. Compile and Program
3. If successfully connect to cellular networks(SKTelecom) then you can get below message
Device's Result
include the mbed library with this snippet
mbed-os-example-cellular Built: Sep 6 2019, 07:06:26 [MAIN], plmn: NULL Establishing connection M2Mnet(BG96) Power ON [00005500ms][INFO][CELL]: New CellularContext (20004120) [00005500ms][INFO][CELL]: CellularContext plmn NULL [00005501ms][INFO][CELL]: CellularContext connect [00006502ms][INFO][CELL]: Start connecting (timeout 1000 ms) [00006511ms][INFO][CELL]: RSSI unknown [00006519ms][INFO][CELL]: Modem ready [00006523ms][INFO][CELL]: RSSI unknown [00006523ms][INFO][CELL]: Setup SIM (timeout 1000 ms) [00006528ms][INFO][CELL]: SIM is ready [00006555ms][INFO][CELL]: RSSI unknown [00006563ms][INFO][CELL]: Network registration (timeout 1000 ms) [00006567ms][INFO][CELL]: Continue after 1 seconds [00006688ms][ERR ][CELL]: AT overflow [00007572ms][INFO][CELL]: RSSI unknown [00007578ms][INFO][CELL]: Registering network => Attaching network [00007582ms][INFO][CELL]: RSSI unknown [00007582ms][INFO][CELL]: Attaching network (timeout 1000 ms) [00007606ms][INFO][CELL]: Found PDP context 2 [00007609ms][INFO][CELL]: Activate PDP context 2 [00009626ms][INFO][CELL]: Found PDP context 2 Connection Established. [00009635ms][INFO][CELL]: Socket 0 open [00009741ms][INFO][CELL]: Socket 0 sent 4 bytes to 222.98.173.203 port 7878 TCP: Sent 4 Bytes to 222.98.173.203 [00010873ms][INFO][CELL]: Socket 0 recv 4 bytes [00011421ms][INFO][CELL]: Socket 0 closed Received from server 4 Bytes [00011421ms][INFO][CELL]: CellularContext disconnect() [00011422ms][INFO][CELL]: cb: CellularContext disconnected Success. Exiting
Server Result
README.md@0:4611f6cf2413, 2018-03-08 (annotated)
- Committer:
- mbed_official
- Date:
- Thu Mar 08 17:31:37 2018 +0000
- Revision:
- 0:4611f6cf2413
- Child:
- 2:0f644d6045cf
Initial commit.
Commit copied from https://github.com/ARMmbed/mbed-os-example-cellular
Who changed what in which revision?
| User | Revision | Line number | New 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 | 0:4611f6cf2413 | 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 | 0:4611f6cf2413 | 53 | You can choose which socket type the application should use; however, please note that TCP is a more reliable tranmission 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 | 0:4611f6cf2413 | 73 | ### Board support |
| mbed_official | 0:4611f6cf2413 | 74 | |
| mbed_official | 0:4611f6cf2413 | 75 | 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 | 76 | |
| mbed_official | 0:4611f6cf2413 | 77 | 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 | 78 | |
| mbed_official | 0:4611f6cf2413 | 79 | ## Compiling the application |
| mbed_official | 0:4611f6cf2413 | 80 | |
| mbed_official | 0:4611f6cf2413 | 81 | 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 | 82 | |
| mbed_official | 0:4611f6cf2413 | 83 | ```sh |
| mbed_official | 0:4611f6cf2413 | 84 | $ mbed compile -m YOUR_TARGET_WITH_MODEM -t GCC_ARM |
| mbed_official | 0:4611f6cf2413 | 85 | ``` |
| mbed_official | 0:4611f6cf2413 | 86 | |
| mbed_official | 0:4611f6cf2413 | 87 | ## Running the application |
| mbed_official | 0:4611f6cf2413 | 88 | |
| mbed_official | 0:4611f6cf2413 | 89 | 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 | 90 | |
| mbed_official | 0:4611f6cf2413 | 91 | 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 | 92 | |
| mbed_official | 0:4611f6cf2413 | 93 | You should see an output similar to this: |
| mbed_official | 0:4611f6cf2413 | 94 | |
| mbed_official | 0:4611f6cf2413 | 95 | ``` |
| mbed_official | 0:4611f6cf2413 | 96 | mbed-os-example-cellular, Connecting... |
| mbed_official | 0:4611f6cf2413 | 97 | |
| mbed_official | 0:4611f6cf2413 | 98 | |
| mbed_official | 0:4611f6cf2413 | 99 | Connection Established. |
| mbed_official | 0:4611f6cf2413 | 100 | UDP: Sent 4 Bytes to echo.u-blox.com |
| mbed_official | 0:4611f6cf2413 | 101 | Received from echo server 4 Bytes |
| mbed_official | 0:4611f6cf2413 | 102 | |
| mbed_official | 0:4611f6cf2413 | 103 | |
| mbed_official | 0:4611f6cf2413 | 104 | Success. Exiting |
| mbed_official | 0:4611f6cf2413 | 105 | |
| mbed_official | 0:4611f6cf2413 | 106 | ``` |
| mbed_official | 0:4611f6cf2413 | 107 | |
| mbed_official | 0:4611f6cf2413 | 108 | ## Troubleshooting |
| mbed_official | 0:4611f6cf2413 | 109 | |
| mbed_official | 0:4611f6cf2413 | 110 | 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. |