Richard Kuo
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 
mbed-os-examples
Revision 53:2e40e7d6aed6, committed 2017-01-05
- Comitter:
- mbed_official
- Date:
- Thu Jan 05 12:30:09 2017 +0000
- Parent:
- 52:957eff5f0ee9
- Child:
- 54:b82f6137dcb1
- Commit message:
- Editorial changes.
.
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 Thu Jan 05 11:15:09 2017 +0000 +++ b/README.md Thu Jan 05 12:30:09 2017 +0000 @@ -373,7 +373,7 @@ #### Compilation problems? -If you encounter a problem compiling the application as follows +If you encounter a problem like this when compiling the application: ``` Building project mbed-os-example-client (K64F, GCC_ARM) @@ -397,10 +397,12 @@ [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. - + +You probably have the 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 NOT to compile the related files. To do that, set up a `.mbedignore` file. An example file is available in the `configs` folder. + +This should resolve the issue: + ``` cp configs/eth-wifi-mbedignore ./.mbedignore ``` -Should resolve the issue.