The WSS SDK currently is a C Based SDK so it can be ported to different platforms and chipsets. Firmware developers will need to implement a compatibility layer specific to the platform that you will port the SDK on. Frustration Free Setup team has included an implementation of a compatibility layer that works with Embedded Linux, MAC, and Raspberry Pi so developers can immediately download the sdk and run a demo program within the SDK on any of those platforms. The below tasks are leveraging that compatibility layer and provides a way to accelerate running WSS sdk. The following are the tasks in this category:
-
Download and Run WSS C SDK
-
Build WSS SDK with AWS IoT for embedded Linux.
The following is the list of pre-requisites that you need to make sure are met in order to be able to perform any tasks with WSS CSDK. The prerequisites are:
-
A Valid Provisioner. The following are the list of valid provisioners that should be in proximity of the device running the demo:
-
Echo dot gen2(donut). Only if connected to 2.4 GHz network.
-
Echo dot gen3(crumpet). Only if connected to 2.4 GHz network.
-
Eero mesh, TP-Link Archer A7, or ASUS rt-ax88u Routers that with hidden SSID "simple_setup".
-
Your own router with creating a hidden 2.4GHz SSID called “simple_setup”.
-
-
Valid Keys for the device. Device Keys can be generated following the instructions in Request a New Device Identifier and Attestation Keys. The default location that the sdk libraries load the device keys from is $ffs/ffs-provisionee-sdk-master/ffs_linux/libffs/data/device_certificate
-
Device keys belong to a customer that has his Wi-Fi password stored in Amazon Wi-Fi Locker. This could be verified by setting up any Amazon (echo, echo dot, firetv, firecube, etc..) with the customer account that is associated with the keys being used by the SDK. You can associate multiple devices with a customer account using the developer console form Submit Test Devices