boting ren / Mbed OS BLEClient_mbedDevConn

This is an example of BLE GATT Client, which receives broadcast data from BLE_Server_BME280 ( a GATT server) , then transfers values up to mbed Device Connector (cloud).

Please refer details about BLEClient_mbedDevConn below. https://github.com/soramame21/BLEClient_mbedDevConn

The location of required BLE GATT server, BLE_Server_BME280, is at here. https://developer.mbed.org/users/edamame22/code/BLE_Server_BME280/

mbed-client/docs/known-issues-mbed-client1511.md@2:b894b3508057, 2017-09-05 (annotated)

Committer:
Ren Boting
Date:
Tue Sep 05 11:56:13 2017 +0900
Revision:
2:b894b3508057
Parent:
0:29983394c6b6 
Update all libraries and reform main.cpp

Who changed what in which revision?

UserRevisionLine numberNew contents of line
edamame22 0:29983394c6b6 1 # Known Issues
edamame22 0:29983394c6b6 2
edamame22 0:29983394c6b6 3 ## About this document
edamame22 0:29983394c6b6 4
edamame22 0:29983394c6b6 5 This is the list of known issues for the 15.11 release of [mbed Client](https://github.com/ARMmbed/mbed-client). We publish mbed-client as module in GitHub, and track open issues as tickets in the repository. That makes for an easy development flow, but doesn’t make it very easy for you to get a single view of all the issues that affect the whole release.
edamame22 0:29983394c6b6 6
edamame22 0:29983394c6b6 7 The purpose of this document is to provide that single view of all the key issues we are aware of. It isn’t a complete list; it’s a filtered and reviewed list, focusing on the issues we thought you’d want to be aware of. Each item explains the problem, as well as workarounds if those are possible. For items filed through GitHub, we’ve included a link to the issue so that you can follow the discussion and code - or even suggest a solution.
edamame22 0:29983394c6b6 8
edamame22 0:29983394c6b6 9 For more information about an issue, contact us on the [mbed forums](http://forums.mbed.com).
edamame22 0:29983394c6b6 10
edamame22 0:29983394c6b6 11 ### Other information not in this document
edamame22 0:29983394c6b6 12
edamame22 0:29983394c6b6 13 We’re still very actively building mbed Client and the 15.11 release is a technology preview. As such there are some other limitations of the release that you can find described in the [release note](https://www.mbed.com/en/development/software/mbed-client/releases/mbed-client1511).
edamame22 0:29983394c6b6 14
edamame22 0:29983394c6b6 15 #### Important Note for Windows Users
edamame22 0:29983394c6b6 16
edamame22 0:29983394c6b6 17 If you are using this release on Microsoft Windows, please be advised that because of the way Windows handles filename and paths, you may have problems if you attempt to use this in a deep directory hierarchy with a long path name (e.g. `c:\some\very\long\path`). If you experience problems unpacking or building this release, please try it in a location with a shorter path before filing a bug. Thanks.
edamame22 0:29983394c6b6 18
edamame22 0:29983394c6b6 19 ***
edamame22 0:29983394c6b6 20 ### mbed Client API may not be fully interoperable with other LWM2M servers.
edamame22 0:29983394c6b6 21
edamame22 0:29983394c6b6 22 *Description*: mbed Client API is OMA LWM2M compatible. However, some features may not be fully interoperable against other open source LWM2M servers. This is the first release version and more features will be made interoperable over coming releases.
edamame22 0:29983394c6b6 23
edamame22 0:29983394c6b6 24 *Workaround*: mbed Client is compatible with mbed Device Connector Service, which can be tested at [https://connector.mbed.com](https://connector.mbed.com).
edamame22 0:29983394c6b6 25
edamame22 0:29983394c6b6 26 *Reported Issue*: ARM internal reference IOTCLT-366
edamame22 0:29983394c6b6 27
edamame22 0:29983394c6b6 28 *Priority*: Major
edamame22 0:29983394c6b6 29
edamame22 0:29983394c6b6 30 ### mbed Client for Linux doesn't support IPv6 connectivity
edamame22 0:29983394c6b6 31
edamame22 0:29983394c6b6 32 *Description*: mbed Client for Linux platform currently works only for IPv4-enabled LWM2M server addresses. IPv6 address support is currently broken.
edamame22 0:29983394c6b6 33
edamame22 0:29983394c6b6 34 *Workaround*: mbed Client is compatible with mbed Device Connector Service which can be tested from [https://connector.mbed.com](https://connector.mbed.com) over IPv4 Address.
edamame22 0:29983394c6b6 35
edamame22 0:29983394c6b6 36 *Reported Issue*: https://github.com/ARMmbed/mbed-client-linux/issues/19
edamame22 0:29983394c6b6 37
edamame22 0:29983394c6b6 38 *Priority*: Major
edamame22 0:29983394c6b6 39
edamame22 0:29983394c6b6 40 ### mbed Client will occasionally disconnect from LWM2M Server because of network errors
edamame22 0:29983394c6b6 41
edamame22 0:29983394c6b6 42 *Description*: If mbed Client is kept running for long durations (over 24 hours) with long lifetime values, it occasionally goes offline due to unstable network conditions - and doesn't send periodic updates to LWM2M server.
edamame22 0:29983394c6b6 43
edamame22 0:29983394c6b6 44 *Workaround*: Set the periodic lifetime value to less than 15 minutes if you want to run stability tests. Also, implement a network error handling mechanism on the application side, to handle `error()` callbacks received from the mbed-client library.
edamame22 0:29983394c6b6 45
edamame22 0:29983394c6b6 46 *Reported Issue*: ARM internal reference IOTCLT-206
edamame22 0:29983394c6b6 47
edamame22 0:29983394c6b6 48 *Priority*: Major
edamame22 0:29983394c6b6 49
edamame22 0:29983394c6b6 50 ### mbed Client might experience a memory leak when running for long durations
edamame22 0:29983394c6b6 51
edamame22 0:29983394c6b6 52 *Description*: mbed Client might have memory leak issues when left running for longer than 12 hours.
edamame22 0:29983394c6b6 53
edamame22 0:29983394c6b6 54 *Workaround*: None
edamame22 0:29983394c6b6 55
edamame22 0:29983394c6b6 56 *Reported Issue*: ARM internal reference IOTCLT-290
edamame22 0:29983394c6b6 57
edamame22 0:29983394c6b6 58 *Priority*: Major
edamame22 0:29983394c6b6 59