
This is a simple mbed client example demonstrating, registration of a device with mbed Device Connector and reading and writing values as well as deregistering on different Network Interfaces including Ethernet, WiFi, 6LoWPAN ND and Thread respectively.
Fork of mbed-os-example-client by
Revision 52:957eff5f0ee9, committed 2017-01-05
- Comitter:
- mbed_official
- Date:
- Thu Jan 05 11:15:09 2017 +0000
- Parent:
- 51:f2c99fcbcd08
- Child:
- 53:2e40e7d6aed6
- Commit message:
- README.md - compilation issue (#161)
Advice about a common compilation problem issue.
.
Commit copied from https://github.com/ARMmbed/mbed-os-example-client
Changed in this revision
README.md | Show annotated file Show diff for this revision Revisions of this file |
--- a/README.md Wed Jan 04 22:15:09 2017 +0000 +++ b/README.md Thu Jan 05 11:15:09 2017 +0000 @@ -370,3 +370,37 @@ 3. `3201/0/5853`. Blink pattern, used by the blink function to determine how to blink. In the format of `1000:500:1000:500:1000:500` (PUT). To learn how to get notifications when resource 1 changes, or how to use resources 2 and 3, read the [mbed Device Connector Quick Start](https://github.com/ARMmbed/mbed-connector-api-node-quickstart). + +#### Compilation problems? + +If you encounter a problem compiling the application as follows + +``` +Building project mbed-os-example-client (K64F, GCC_ARM) +Scan: . +Scan: FEATURE_LWIP +Scan: FEATURE_UVISOR +Scan: FEATURE_COMMON_PAL +Scan: FEATURE_BLE +Scan: FEATURE_STORAGE +Scan: FEATURE_THREAD_BORDER_ROUTER +Scan: FEATURE_THREAD_ROUTER +Scan: FEATURE_LOWPAN_BORDER_ROUTER +Scan: FEATURE_LOWPAN_ROUTER +Scan: FEATURE_LOWPAN_HOST +Scan: FEATURE_NANOSTACK_FULL +Scan: FEATURE_NANOSTACK +Scan: FEATURE_THREAD_END_DEVICE +Scan: mbed +Scan: env +Compile [ 0.3%]: NanostackRfPhyAtmel.cpp +[ERROR] ./atmel-rf-driver/source/NanostackRfPhyAtmel.cpp:18:44: fatal error: nanostack/platform/arm_hal_phy.h: No such file or directory +compilation terminated. +``` +You are likely having LWIP stack in use with ethernet or WiFi and you have the mesh RF-stacks in the root of this example. You need to tell mbed to NOT compile those, please set up a .mbedignore -file to tell mbed not to compile those files. Example file has been made available in the configs-folder. + +``` +cp configs/eth-wifi-mbedignore ./.mbedignore +``` + +Should resolve the issue.