Recent DiscussionsMost RecentNewest TopicsMost LikesSolutionsTagged:TagRe: Why there are 2 azure iot C sdks? Hi DangNH , as Israr_2020 said, the Embedded C SDK is focused on constrained devices (normally based on microcontrollers). For non-constrained devices C SDK is also a good choice. Your correct on your assumption: an application created for C SDK will require some re-work to be migrated over the Embedded C SDK as their underlying architecture designs are different. If you anticipate a need for constrained devices in the future, you should consider leveraging the Embedded C SDK as it's modular approach will make it simpler to enable different device configurations.
Recent Blog ArticlesNewest TopicsMost LikesTagged:TagOver the air updates for MCUs with Azure Device Update Performing OTA updates on MCU-based devices just got easier with Azure IoT middleware for FreeRTOS and Azure Device Update. Arduino library for Azure IoT The new Arduino library for Azure IoT enables you to easily connect your Arduino devices. Expanding Azure Support for Constrained Devices: Azure IoT middleware for FreeRTOS Announcing the GA release of a great development experience to get your FreeRTOS devices connected to Azure IoT. Azure IoT releases a new SDK for constrained devices If you have ever struggled to fit your application into a constrained IoT device, we have great news for you! We released the new Embedded C SDK, built to support microcontrollers, optimized for memo...
