Etherios Cloud Connector very first porting for mbed. Tested in an LPC1768

Etherios Cloud Connector for Embedded v2.1.0.3 library for mbed. Early porting.

This port is centered mainly in the platform code. So it should work properly with the provided examples of send_data, device_request, data_points, RCI and firmware_update (stub implementation, not a real one... yet ;-)). Filesystem is not implemented yet, and some examples might need changes.

To run, it needs the following libraries: - mbed - mbed-rtos - EthernetInterface

Find more information (and the source code!) about Etherios Cloud Connector for Embedded here: http://www.etherios.com/products/devicecloud/support/connector and in: http://www.etherios.com

Committer:
spastor
Date:
Tue Dec 03 14:10:48 2013 +0000
Revision:
1:908afea5a49d
Parent:
0:1c358ea10753
Use internal Thread.h instead of Threads.h

Who changed what in which revision?

UserRevisionLine numberNew contents of line
spastor 0:1c358ea10753 1 Release Notes PN 93000761_C
spastor 0:1c358ea10753 2 Etherios Cloud Connector for Embedded
spastor 0:1c358ea10753 3 v2.1.0.3
spastor 0:1c358ea10753 4
spastor 0:1c358ea10753 5 INTRODUCTION
spastor 0:1c358ea10753 6
spastor 0:1c358ea10753 7 Cloud Connector for Embedded is a software development
spastor 0:1c358ea10753 8 package used to enable a device to exchange information with
spastor 0:1c358ea10753 9 Device Cloud. Cloud Connector supports application to device
spastor 0:1c358ea10753 10 data interaction (messaging), application and device data
spastor 0:1c358ea10753 11 storage, and remote management of devices. Devices are
spastor 0:1c358ea10753 12 associated with Device Cloud through the Internet or other
spastor 0:1c358ea10753 13 wide area network connections, which allows for communication
spastor 0:1c358ea10753 14 between the device and customer applications, via Device Cloud.
spastor 0:1c358ea10753 15
spastor 0:1c358ea10753 16 SUPPORTED PRODUCTS
spastor 0:1c358ea10753 17
spastor 0:1c358ea10753 18 Etherios Cloud Connector for Embedded
spastor 0:1c358ea10753 19
spastor 0:1c358ea10753 20 ENHANCEMENTS
spastor 0:1c358ea10753 21
spastor 0:1c358ea10753 22 v2.1.0
spastor 0:1c358ea10753 23
spastor 0:1c358ea10753 24 Full SMS transport support for Short Messaging (SM) protocol.
spastor 0:1c358ea10753 25 The example implementation is made through Gammu project.
spastor 0:1c358ea10753 26
spastor 0:1c358ea10753 27 Device ID autoprovision: a device connecting through EDP protocol
spastor 0:1c358ea10753 28 can ask Device Cloud for an autogenerated Device ID instead of
spastor 0:1c358ea10753 29 providing one.
spastor 0:1c358ea10753 30
spastor 0:1c358ea10753 31 Added two new connector_initiate_request_id memebers for canceling
spastor 0:1c358ea10753 32 timed-out SM sessions: connector_initiate_session_cancel and
spastor 0:1c358ea10753 33 connector_initiate_session_cancel_all.
spastor 0:1c358ea10753 34
spastor 0:1c358ea10753 35 Data Service / Data Points: status callback is always called
spastor 0:1c358ea10753 36 in both EDP (TCP) and SM (UDP or SMS) either a response is needed
spastor 0:1c358ea10753 37 or not.
spastor 0:1c358ea10753 38
spastor 0:1c358ea10753 39 Optimization in the SM protocol implementation.
spastor 0:1c358ea10753 40
spastor 0:1c358ea10753 41 Reduce memory usage when CONNECTOR_MSG_MAX_TRANSACTION is set.
spastor 0:1c358ea10753 42 [IC4C-165]
spastor 0:1c358ea10753 43
spastor 0:1c358ea10753 44 v2.0.0
spastor 0:1c358ea10753 45
spastor 0:1c358ea10753 46 This is the initial public release and a replacement product
spastor 0:1c358ea10753 47 for the iDigi Connector for Embedded.
spastor 0:1c358ea10753 48
spastor 0:1c358ea10753 49 With respect to iDigi Connector v1.2, Cloud Connector includes
spastor 0:1c358ea10753 50 optimized Remote Configuration support with significantly
spastor 0:1c358ea10753 51 smaller memory foot print and reduced network bandwidth usage;
spastor 0:1c358ea10753 52 Support for Data Streams, and support for Short Messaging over
spastor 0:1c358ea10753 53 UDP.
spastor 0:1c358ea10753 54
spastor 0:1c358ea10753 55 BUG FIXES
spastor 0:1c358ea10753 56
spastor 0:1c358ea10753 57 v2.1.0
spastor 0:1c358ea10753 58
spastor 0:1c358ea10753 59 Fixed known issue in RCI in which a setting was overwritten if
spastor 0:1c358ea10753 60 a setting was set to a string longer than the maximum allowed.
spastor 0:1c358ea10753 61 [IC4C-180]
spastor 0:1c358ea10753 62
spastor 0:1c358ea10753 63 Completely removed the use of rand() functions. [IC4C-109].
spastor 0:1c358ea10753 64
spastor 0:1c358ea10753 65 Fixed failure when sending very large Data Streams. [IC4C-287]
spastor 0:1c358ea10753 66
spastor 0:1c358ea10753 67 Added macro CONNECTOR_SM_MAX_DATA_POINTS_SEGMENTS to allow
spastor 0:1c358ea10753 68 bigger Data Point uploads in SM transports. [IC4C-290]
spastor 0:1c358ea10753 69
spastor 0:1c358ea10753 70 CLI request was split in different command lines with multipart
spastor 0:1c358ea10753 71 messages. [IC4C-285]
spastor 0:1c358ea10753 72
spastor 0:1c358ea10753 73 Argument 'maxResponseSize' for CLI over SM (UDP & SMS) did not
spastor 0:1c358ea10753 74 work properly. [IC4C-276]
spastor 0:1c358ea10753 75
spastor 0:1c358ea10753 76 Connector was aborted when a "Request Connect" was received
spastor 0:1c358ea10753 77 in an application with no TCP transport enabled. [IC4C-274]
spastor 0:1c358ea10753 78
spastor 0:1c358ea10753 79 UDP transport did not correctly start if the open or send callbacks
spastor 0:1c358ea10753 80 returned connector_callback_busy. [IC4C-241] [IC4C-240]
spastor 0:1c358ea10753 81
spastor 0:1c358ea10753 82 CONNECTOR_NETWORK_UDP_START macro was not working. [IC4C-204]
spastor 0:1c358ea10753 83
spastor 0:1c358ea10753 84 v2.0.1
spastor 0:1c358ea10753 85
spastor 0:1c358ea10753 86 Removed rand_r() which is not C89 compliant. [IC4C-109]
spastor 0:1c358ea10753 87
spastor 0:1c358ea10753 88 connector_initiate_action() connector_initiate_data_point_
spastor 0:1c358ea10753 89 binary request over connector_transport_tcp writes incorrect
spastor 0:1c358ea10753 90 data to Device Cloud. [IC4C-110]
spastor 0:1c358ea10753 91
spastor 0:1c358ea10753 92 Sample project "data_point" in step mode, hangs and throws a
spastor 0:1c358ea10753 93 core dump. [IC4C-111]
spastor 0:1c358ea10753 94
spastor 0:1c358ea10753 95 SM (/UDP) does not work with IMEI WAN Device IDs. [IC4C-115]
spastor 0:1c358ea10753 96
spastor 0:1c358ea10753 97 Datapoints not working when CONNECTOR_NO_MALLOC defined.
spastor 0:1c358ea10753 98 [IC4C-116]
spastor 0:1c358ea10753 99
spastor 0:1c358ea10753 100 Data point native types for int and long are ambiguous.
spastor 0:1c358ea10753 101 [IC4C-118]
spastor 0:1c358ea10753 102
spastor 0:1c358ea10753 103 The connector_callback_unrecognized user return value in SM
spastor 0:1c358ea10753 104 Cloud request callback is not handled correctly. [IC4C-119]
spastor 0:1c358ea10753 105
spastor 0:1c358ea10753 106 Bad termination of hint on DP4D error. [IC4C-139]
spastor 0:1c358ea10753 107
spastor 0:1c358ea10753 108 Function tcp_receive_packet() does not handle connector_
spastor 0:1c358ea10753 109 callback_error case correctly. [IC4C-140] [IC4C-159]
spastor 0:1c358ea10753 110
spastor 0:1c358ea10753 111 Function edp_tcp_send_process() defaults connector_callback_
spastor 0:1c358ea10753 112 error case for tcp_send_buffer(). [IC4C-140] [IC4C-160]
spastor 0:1c358ea10753 113
spastor 0:1c358ea10753 114 Initiate action calls doesn't check if transport is running.
spastor 0:1c358ea10753 115 [IC4C-141]
spastor 0:1c358ea10753 116
spastor 0:1c358ea10753 117 Bad handling of ping_response callback returning unrecognized.
spastor 0:1c358ea10753 118 [IC4C-142]
spastor 0:1c358ea10753 119
spastor 0:1c358ea10753 120 Data Put from platform over SM/UDP continuously sends target
spastor 0:1c358ea10753 121 callback. [IC4C-149]
spastor 0:1c358ea10753 122
spastor 0:1c358ea10753 123 Callback returning error is not correctly handled when
spastor 0:1c358ea10753 124 receiving data from the platform. [IC4C-151]
spastor 0:1c358ea10753 125
spastor 0:1c358ea10753 126 Cloud Connector gives a malformed bRCI command, recovering a
spastor 0:1c358ea10753 127 big string. [IC4C-157]
spastor 0:1c358ea10753 128
spastor 0:1c358ea10753 129 Cloud Connector gives a malformed bRCI command, setting a
spastor 0:1c358ea10753 130 big string. [IC4C-163]
spastor 0:1c358ea10753 131
spastor 0:1c358ea10753 132 Firmware download API no longer provides program size.
spastor 0:1c358ea10753 133 [IC4C-168]
spastor 0:1c358ea10753 134
spastor 0:1c358ea10753 135 Adjusted maximum incoming RCI buffer to CONNECTOR_RCI_
spastor 0:1c358ea10753 136 MAXIMUM_CONTENT_LENGTH define. [IC4C-176] [IC4C-164]
spastor 0:1c358ea10753 137
spastor 0:1c358ea10753 138 v2.0.0
spastor 0:1c358ea10753 139
spastor 0:1c358ea10753 140 Corrected ARM misalignment warnings, which cause compilation
spastor 0:1c358ea10753 141 errors due to -Werror. The casting was between byte and word
spastor 0:1c358ea10753 142 pointers, which verified safe in the original code. A cast
spastor 0:1c358ea10753 143 to void * was used to avoid the warning. [IC4C-49]
spastor 0:1c358ea10753 144
spastor 0:1c358ea10753 145 KNOWN LIMITATIONS
spastor 0:1c358ea10753 146
spastor 0:1c358ea10753 147 v2.1.0
spastor 0:1c358ea10753 148
spastor 0:1c358ea10753 149 If a Data Point over TCP contains a string that does not fit in a
spastor 0:1c358ea10753 150 single message it will not be sent properly, probably creating a
spastor 0:1c358ea10753 151 Data Stream with no Data Points in it on Device Cloud. The maximum
spastor 0:1c358ea10753 152 value for a string among a Data Point is 497. This does not affect
spastor 0:1c358ea10753 153 SM transports.
spastor 0:1c358ea10753 154
spastor 0:1c358ea10753 155 v2.0.1
spastor 0:1c358ea10753 156
spastor 0:1c358ea10753 157 When using RCI facility, if a setting value is set to a string
spastor 0:1c358ea10753 158 longer than CONNECTOR_RCI_MAXIMUM_CONTENT_LENGTH (defined at
spastor 0:1c358ea10753 159 connector_config.h), the setting is overwritten and the response
spastor 0:1c358ea10753 160 received has both success and error fields. [IC4C-180]
spastor 0:1c358ea10753 161
spastor 0:1c358ea10753 162 HISTORY
spastor 0:1c358ea10753 163
spastor 0:1c358ea10753 164 v2.1.0
spastor 0:1c358ea10753 165
spastor 0:1c358ea10753 166 This release includes SM protocol over SMS support and other SM
spastor 0:1c358ea10753 167 protocol implementation improvements. Additionally, it adds support
spastor 0:1c358ea10753 168 for Device ID autoptovision and improves the behavior of Data
spastor 0:1c358ea10753 169 Services and Data Point callbacks to facilitate memory management.
spastor 0:1c358ea10753 170
spastor 0:1c358ea10753 171 v2.0.0
spastor 0:1c358ea10753 172
spastor 0:1c358ea10753 173 This is the initial public release and a replacement product
spastor 0:1c358ea10753 174 for the iDigi Connector for Embedded.
spastor 0:1c358ea10753 175
spastor 0:1c358ea10753 176 With respect to iDigi Connector v1.2, Cloud Connector includes
spastor 0:1c358ea10753 177 optimized Remote Configuration support with significantly
spastor 0:1c358ea10753 178 smaller memory foot print and reduced network bandwidth usage;
spastor 0:1c358ea10753 179 Support for Data Streams, and support for Short Messaging over
spastor 0:1c358ea10753 180 UDP.
spastor 0:1c358ea10753 181
spastor 0:1c358ea10753 182 Corrected ARM misalignment warnings, which cause compilation
spastor 0:1c358ea10753 183 errors due to -Werror. The casting was between byte and word
spastor 0:1c358ea10753 184 pointers, which verified safe in the original code. A cast
spastor 0:1c358ea10753 185 to void * was used to avoid the warning. [IC4C-49]
spastor 0:1c358ea10753 186