You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+22-3Lines changed: 22 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,12 +45,12 @@ See the file `mbed_app.json` in the root directory of your application. This fil
45
45
"help": "The password string to use for this APN, set to 0 if none",
46
46
"value": 0
47
47
}
48
-
```
48
+
```
49
49
50
50
### Selecting socket type (TCP or UDP)
51
51
52
52
53
-
You can choose which socket type the application should use; however, please note that TCP is a more reliable tranmission protocol. For example:
53
+
You can choose which socket type the application should use; however, please note that TCP is a more reliable transmission protocol. For example:
54
54
55
55
56
56
```json
@@ -70,6 +70,25 @@ If you like details and wish to know about all the AT interactions between the m
70
70
},
71
71
```
72
72
73
+
### Turning on the tracing and trace level
74
+
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
76
+
77
+
```"target_overrides": {
78
+
"*": {
79
+
"target.features_add": ["LWIP", "COMMON_PAL"],
80
+
"mbed-trace.enable": false,
81
+
```
82
+
83
+
After you have defined `mbed-trace.enable: true`, you can set trace levels by changing value in `trace-level`
84
+
85
+
```"trace-level": {
86
+
"help": "Options are TRACE_LEVEL_ERROR,TRACE_LEVEL_WARN,TRACE_LEVEL_INFO,TRACE_LEVEL_DEBUG",
87
+
"macro_name": "MBED_TRACE_MAX_LEVEL",
88
+
"value": "TRACE_LEVEL_INFO"
89
+
}
90
+
```
91
+
73
92
### Board support
74
93
75
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).
@@ -94,7 +113,7 @@ You should see an output similar to this:
94
113
95
114
```
96
115
mbed-os-example-cellular
97
-
Establishing connection ......
116
+
Establishing connection ......
98
117
99
118
Connection Established.
100
119
TCP: connected with echo.mbedcloudtesting.com server
0 commit comments