Eric Jung
BG96 Cat.M1 basic sample for WIZnet IoT Shield based on Mbed-OS Cellular APIs (SK telecom network in Korea)
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 and added some features.
Tested with
- NUCLEO_L476RG
- DISCO_L475VG_IOT01A
- K64F
Example functionality
This example showcases the following device functionality:
1. Import the application into your desktop:
mbed import https://os.mbed.com/users/hkjung/code/mbed-os-example-cellular-BG96/ cd mbed-os-example-cellular-BG96
2. Compile and program:
mbed compile -t <toolchain> -m <TARGET_BOARD>
(supported toolchains : GCC_ARM / ARM / IAR)
3. Download binary to a target board
If need more information such as how to test, please look at https://os.mbed.com/teams/mbed-os-examples/code/mbed-os-example-cellular/.
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