FRDM K64F Metronome

Committer:
ram54288
Date:
Sun May 14 18:37:05 2017 +0000
Revision:
0:dbad57390bd1
Initial commit

Who changed what in which revision?

UserRevisionLine numberNew contents of line
ram54288 0:dbad57390bd1 1 # Known Issues
ram54288 0:dbad57390bd1 2
ram54288 0:dbad57390bd1 3 ## About this document
ram54288 0:dbad57390bd1 4
ram54288 0:dbad57390bd1 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.
ram54288 0:dbad57390bd1 6
ram54288 0:dbad57390bd1 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.
ram54288 0:dbad57390bd1 8
ram54288 0:dbad57390bd1 9 For more information about an issue, contact us on the [mbed forums](http://forums.mbed.com).
ram54288 0:dbad57390bd1 10
ram54288 0:dbad57390bd1 11 ### Other information not in this document
ram54288 0:dbad57390bd1 12
ram54288 0:dbad57390bd1 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).
ram54288 0:dbad57390bd1 14
ram54288 0:dbad57390bd1 15 #### Important Note for Windows Users
ram54288 0:dbad57390bd1 16
ram54288 0:dbad57390bd1 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.
ram54288 0:dbad57390bd1 18
ram54288 0:dbad57390bd1 19 ***
ram54288 0:dbad57390bd1 20 ### mbed Client API may not be fully interoperable with other LWM2M servers.
ram54288 0:dbad57390bd1 21
ram54288 0:dbad57390bd1 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.
ram54288 0:dbad57390bd1 23
ram54288 0:dbad57390bd1 24 *Workaround*: mbed Client is compatible with mbed Device Connector Service, which can be tested at [https://connector.mbed.com](https://connector.mbed.com).
ram54288 0:dbad57390bd1 25
ram54288 0:dbad57390bd1 26 *Reported Issue*: ARM internal reference IOTCLT-366
ram54288 0:dbad57390bd1 27
ram54288 0:dbad57390bd1 28 *Priority*: Major
ram54288 0:dbad57390bd1 29
ram54288 0:dbad57390bd1 30 ### mbed Client for Linux doesn't support IPv6 connectivity
ram54288 0:dbad57390bd1 31
ram54288 0:dbad57390bd1 32 *Description*: mbed Client for Linux platform currently works only for IPv4-enabled LWM2M server addresses. IPv6 address support is currently broken.
ram54288 0:dbad57390bd1 33
ram54288 0:dbad57390bd1 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.
ram54288 0:dbad57390bd1 35
ram54288 0:dbad57390bd1 36 *Reported Issue*: https://github.com/ARMmbed/mbed-client-linux/issues/19
ram54288 0:dbad57390bd1 37
ram54288 0:dbad57390bd1 38 *Priority*: Major
ram54288 0:dbad57390bd1 39
ram54288 0:dbad57390bd1 40 ### mbed Client will occasionally disconnect from LWM2M Server because of network errors
ram54288 0:dbad57390bd1 41
ram54288 0:dbad57390bd1 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.
ram54288 0:dbad57390bd1 43
ram54288 0:dbad57390bd1 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.
ram54288 0:dbad57390bd1 45
ram54288 0:dbad57390bd1 46 *Reported Issue*: ARM internal reference IOTCLT-206
ram54288 0:dbad57390bd1 47
ram54288 0:dbad57390bd1 48 *Priority*: Major
ram54288 0:dbad57390bd1 49
ram54288 0:dbad57390bd1 50 ### mbed Client might experience a memory leak when running for long durations
ram54288 0:dbad57390bd1 51
ram54288 0:dbad57390bd1 52 *Description*: mbed Client might have memory leak issues when left running for longer than 12 hours.
ram54288 0:dbad57390bd1 53
ram54288 0:dbad57390bd1 54 *Workaround*: None
ram54288 0:dbad57390bd1 55
ram54288 0:dbad57390bd1 56 *Reported Issue*: ARM internal reference IOTCLT-290
ram54288 0:dbad57390bd1 57
ram54288 0:dbad57390bd1 58 *Priority*: Major
ram54288 0:dbad57390bd1 59