Daniel Lee
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.
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
Diff: README.md
- Revision:
- 6:5678c0b6f74e
- Parent:
- 2:0f644d6045cf
- Child:
- 11:23ea0907186e
--- a/README.md Wed Apr 11 06:30:27 2018 +0100
+++ b/README.md Thu May 10 05:17:02 2018 +0100
@@ -45,12 +45,12 @@
"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:
+You can choose which socket type the application should use; however, please note that TCP is a more reliable transmission protocol. For example:
```json
@@ -70,6 +70,25 @@
},
```
+### Turning on the tracing and trace level
+
+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
+
+```"target_overrides": {
+ "*": {
+ "target.features_add": ["LWIP", "COMMON_PAL"],
+ "mbed-trace.enable": false,
+```
+
+After you have defined `mbed-trace.enable: true`, you can set trace levels by changing value in `trace-level`
+
+ ```"trace-level": {
+ "help": "Options are TRACE_LEVEL_ERROR,TRACE_LEVEL_WARN,TRACE_LEVEL_INFO,TRACE_LEVEL_DEBUG",
+ "macro_name": "MBED_TRACE_MAX_LEVEL",
+ "value": "TRACE_LEVEL_INFO"
+ }
+```
+
### Board support
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).
@@ -94,7 +113,7 @@
```
mbed-os-example-cellular
-Establishing connection ......
+Establishing connection ......
Connection Established.
TCP: connected with echo.mbedcloudtesting.com server