Azure IoT samples using Azure IoT middleware for FreeRTOS

Getting Started with Azure IoT middleware for FreeRTOS

The Azure IoT middleware for FreeRTOS simplifies the connection of devices running FreeRTOS to the Azure IoT services. It implements a modular approach that brings flexibility to IoT developers by allowing them to bring their own network stack (MQTT, TLS and Socket).

The Azure IoT middleware for FreeRTOS repo has the core functionalities of the middleware and no external dependencies, however to implement the working samples, we need to bring a network stack which is the objective of the samples in this repo.

We have two sets of samples:

• Azure IoT Hub: These samples leverage Azure IoT Hub, DPS (Device Provisioning) and Plug and Play.

• Azure IoT Central: These samples leverage Azure IoT Central, Azure DPS (Device Provisioning Service) and, Plug and Play. Azure subscription is not required during the initial 7 days of the IoT Central Free Trial.

There are several other alternatives to get MCU-based devices connected to Azure. See Other Azure IoT SDKs to learn more.

IoT Hub Samples:

Below you will find samples for development kits and simulators showing how to use the Azure IoT middleware for FreeRTOS connected to Azure IoT hub. The following samples support these development kits:

• ESPRESSIF:

  • ESP32
  • ESP32 Azure IoT Kit

• NXP:

  • MIMXRT1060-EVK

• STMicroelectronics:

  • B-L475E-IOT01A
  • B-L4S5I-IOT01A
  • STM32H745I-DISCO

• PC Simulation:

  • Linux
  • Windows

For a video deep dive into this repo and the source code, please see the Microsoft Developers video below.

Azure Device Update

You can interact with Azure Device Update, remotely updating your Azure IoT Hub devices through the samples below:

• ESPRESSIF:

  • ESP32

• NXP:

  • MIMXRT1060-EVK

• STMicroelectronics:

  • B-L475E-IOT01A

• PC Simulation:

  • Linux

IoT Central Samples

Below you will find samples for development kits showing how to use the Azure IoT middleware for FreeRTOS connected to Azure IoT Central. The following samples support these development kits:

• ESPRESSIF:

  • ESP32-Azure IoT Kit

• STMicroelectronics:

  • B-L475E-IOT01A

Plug and Play Sample

The easiest way to interact with the Plug and Play sample from the IoT service side is to use Azure IoT Explorer. To interact with the device sample:

• Install Azure IoT Explorer.
• Download the Thermostat model to a local directory.
• Start Azure IoT Explorer and then:
  • Configure your hub. Once you've created your thermostat device, you should see it listed in the UX.
  • Go to IoT Plug and Play Settings on the home screen, select Local Folder for the location of the model definitions, and point to the folder you downloaded the thermostat model.
  • Go to the devices list and select your thermostat device. Now select IoT Plug and Play components and then Default Component.
  • You will now be able to interact with the Plug and Play device.

Additional instructions for using Azure IoT Explorer are available here.

Support

If you need support, please see our SUPPORT.md file.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies