Does anyone have experience with porting the kaa-client SDK, which supports only ESP8266, to the newer ESP32?
I have started with adapting the TCP APIs.
-
has somebody experience? is this your question?David Ranieri– David Ranieri2017-02-15 12:59:08 +00:00Commented Feb 15, 2017 at 12:59
-
Welcome to StackOverflow. Please take a look here in order to see how to ask a good question: stackoverflow.com/help/how-to-askyakobom– yakobom2017-02-15 13:01:35 +00:00Commented Feb 15, 2017 at 13:01
-
Moreover, porting an SDK is quite strange....LPs– LPs2017-02-15 13:10:42 +00:00Commented Feb 15, 2017 at 13:10
-
Please, add "kaa" tag to such a questions.Y. Verzun– Y. Verzun2017-02-15 13:58:45 +00:00Commented Feb 15, 2017 at 13:58
Add a comment
|
1 Answer
Currently there is no full description how to port the Kaa C SDK on a specific platform, but we are working on this item. Thus I am going to describe general steps here.
Kaa C SDK doesn't need any OS. To use the Kaa C SDK on a specific platform, you must implement the following routines:
Mandatory:
Dynamic allocation.
Network communication.
Time routine.
Public key generation (it may be some hard-coded key, see the ESP8266 demo).
SHA-1 calculation (you may use a default implementation).
Optional (it means you can provide empty implementation):
File system interaction (one, two).
Debug logging.
This page describes configuration parameters for building the Kaa C SDK on various platforms.
Here are instructions how to develop applications based on the Kaa C SDK on TI СС32XX and ESP8266 platforms.
Also, you can find here the source code of demo applications for these platforms.
Second - if you are using a protocol which is not yet officially supported, you can implement a custom transport.
The alternative option is when you integrate the Kaa SDK into a gateway (we call it "actor gateway"). The actor gateway instantiates an endpoint actor per each physical device. The actor handles communication with the actual device and presents itself to the cloud as a virtual representation of the sensor, etc.
The actor gateway can be effectively used when you can’t install the Kaa SDK on your device or you need to use some sophisticated protocol for device-server connectivity.
