Mark Blackburn / Mbed OS mbed-os-example-client

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.

Dependencies:   lwip

Fork of mbed-os-example-client by mbed-os-examples

configs/mesh-mbedignore@63:c73f78fd7982, 2017-02-15 (annotated)

Committer:
mbed_official
Date:
Wed Feb 15 08:00:11 2017 +0000
Revision:
63:c73f78fd7982
Parent:
45:b150e0aa009c 
Integrate easy-connect, fix serial, fix warning (#176)



Integrate easy-connect

- we can remove all the external RF-drivers from main folder

- get easy-connect into use

- remove all the complicated network stuff



Fix serial - we don't need raw serial and we don't need to initialize it

if we set the right stuff to mbed_app.json (added). Plain printf() works

and it even does type checking now. (Points to Kevin Bracey on this).



Start the thread in a non-deprecated way using callback to remove one compiler

warning (again, points to Kevin Bracey).



Easy-connect ESP8266 TX/RX pins in different defines.

mbed-os-example-client has NEVER used 2 sets of WiFi pins, so need

to add a define to hack them into one set - otherwise it will not compile.



The cp command would not have worked if one would have changed

the compiler. Add UBLOX ODIN ETH config to be built as well,

now that we have figured out how to make the the ethernet work

on it.



Change also the WIFI  to work with easy-connect. Easy-connect has 2 separate WIFIs,

so you have to choose between ESP8266 vs. ODIN. Thus, 2 config files are also needed,

one for ESP8266 and one for ODIN.



.

Commit copied from https://github.com/ARMmbed/mbed-os-example-client

Who changed what in which revision?

UserRevisionLine numberNew contents of line
mbed_official 63:c73f78fd7982 1 easy-connect/esp8266-driver/*