This repo contains sources and links for Azure Sphere Bootcamp labs, amongst other Azure Sphere Samples for connected MCUs, sensors and other peripherals.
Prerequisites: Please make sure to have a Windows 10 laptop capable of running Visual Studio 2019 or Visual Studio Code with the Azure Sphere SDK already installed and a free USB port available.
- Visual Studio 2019 Download: https://visualstudio.microsoft.com/vs/
In Visual Studio please go to Extensions -> Manage Extensions and download the Azure Sphere Extension for Visual Studio. This may also download dependencies like C/C++ and the Linux development evironment for Visual Studio so it may take a little while. - alternatively Visual Studio Code Download: https://code.visualstudio.com/
In Visual Studio Code, please also download the Azure Sphere extension (which will also download the C/C++ and CMake Tools Extensions). Please also follow the instructions on the Extension page to configure your settings.json!
Note: If you run Visual Studio 2019 and Visual Studio Code side by side, you actually don't need to install the CMake tools and Ninja seperately but can refer to the VS2019 versions in settings.json alike:
"AzureSphere.SdkPath": "C:\\Program Files (x86)\\Microsoft Azure Sphere SDK\\", "AzureSphere.ArmGnuPath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Community\\Linux\\gcc_arm", "cmake.cmakePath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Community\\Common7\\IDE\\CommonExtensions\\Microsoft\\CMake\\CMake\\bin\\cmake.exe", "cmake.configureSettings": { "CMAKE_MAKE_PROGRAM" : "C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Community\\Common7\\IDE\\CommonExtensions\\Microsoft\\CMake\\Ninja\\ninja.exe" }The
"AzureSphere.ArmGnuPath"needs to point to your ARM toolchain (compilers are required to be located in the ...\bin... subdirectory underneath. In my example I'm referring to the toolchain installed with Visual Studio 2019 Community edition. For Enterprise edition this would be ...\2019\Enterprise...
- Azure Sphere SDK (for Windows): https://aka.ms/azurespheresdkdownload/Windows
This download package installs the AzSphere.Exe command line tool as well as the network & FTDI drivers
Although you may be able to follow the labs also using Visual Studio Code running on Linux, your milage may vary (i.e. I have mainly tested the lab projects on Windows using Visual Studio and Visual Studio Code and only tried some of them on Ubuntu 20.04 Linux).
You will also need an active Azure subscription and a user account with sufficient rights to create Azure Resources such as
- Azure Resource Groups
- Azure IoT Hub
- Azure IoT Hub Device Provisioning Service amongst others potentially.
To follow the code samples please clone the following GitHub repositories:
- This AzureSphereSamples repo
- The Azure Sphere Product Team Azure Sphere Samples Repo
Please follow the steps as outlined in Install Azure Sphere
- Install the Azure Sphere SDK and set up your development board
- Make sure your device runs the latest Azure Sphere OS version
azsphere device show-os-version. If your OS version is <19.11 please first "recover" your device withazsphere device recover - Claim your device
- Configure networking and update the device OS
Please follow the steps outlined in Quickstart: Building your first high-level application to prepare your Azure Sphere Board for development sideloading and build your first application.
Please follow the steps as outlined in Set up an IoT Hub for Azure Sphere to create and link an Azure IoT Hub and an Azure IoT Hub Device Provisioning Service as well as to configure the Certificate chain using the Certificate Authority (CA) provided by your Azure Sphere tenant.
Pls note
Some older versions of the Azure Sphere SDK contained the "Azure IoT Hub Sample for Mt3620 RDB (Azure Sphere)" application template. Since this application template is no longer available in more recent versions of the SDK I've thus included it here as a starting point. For this lab you'll therefore need this repo cloned.
This lab covers typical IoT scenarios:
- device-to-could messaging
- Azure IoT Hub Device Twins to report device properties and receive desired property states
- command & control scenarios using Azure IoT Hub Direct Methods
Please follow the steps outlined in Mt3620AzureIoTHub to connect Azure Sphere to Azure IoT Hub.
Please follow the steps as outlined in Mt3620DirectDHT to connect the DHT sensor and send telemetry data. It also contains hints to extend the ePoll event_data_t structure to enable event context handling and shows some of the intricacies of running time-sensitive bit-banging protocols in a high-level (POSIX) app.
Lab #4: E2E "Office Climate IoT Solution" with industry grade I2C sensor, Azure IoT PnP and Azure IoT Central
In this example we will connect an industrial grade I2C based sensor and send telemetry data using Azure IoT Plug-and-Play to an Azure IoT Central application.
In this example it is the Bosch BME280 temperature/humidity/pressure sensor (or BMP280 with temperature/pressure accordingly). For this sensor, Bosch Sensortec provides a platform independent libraries on GitHub (BME280_driver or BMP2-Sensor-API respectively. The sensor itself offers I2C as well as SPI connectivety options and depending on your module it may offer either or both of them. As all modules I have at hand offer I2C and this has some cost saving advantages over SPI (i.e. less wiring, multiple sensors on I2C bus) this examples is using I2C.
New: With the 21.10 release I've updated the sample to fully implement Azure IoT Plug-and-Play data models, with a publicly available model id and updated the Azure IoT Central application template accordingly.
Please follow the steps as outlined in SphereBME280 to run this example.
In this lab we'll connect a NodeMCU sending telemetry data through UART to Azure Sphere acting as a secure cloud connectivety option, often also referred to as Guardian Device scenario.
Please follow the steps as outlined in MCUtoMt3620ToAzure to run this lab.
This lab is split into several parts as it covers a variety of topics in an end-to-end scenario.
It starts with the development of multi-core applications with a high-level (POSIX) connectivety app that is acompanied by one or more real-time capable applications that use the mailbox-based inter-core communication mechanism to exchange messages.
We'll also touch on debugging multicore applications and reveal some helpful tips to enable Visual Studio to cope with multiple applications.
In the last part we'll start creating application combinations and deploy them for over-the-air (OTA). This includes setting up the infrastructue in the Azure Sphere Security Service. To showcase how this can be automated, you'll find examples of PowerShell scripts, that wrap the AzSphere.exe tool and allow to build a fully automated CI/CD pipeline.
Please follow the steps as outlined in OTA to run this lab.
This lab covers WiFi provisioning as well as a command & control scenario via Bluetooth, in this example using the Nordic Semiconductor nRF52 Series Bluetooth SoC. Together with a Windows or Smart Phone App it allows to provision the WiFi settings for Azure Sphere as well as showcases how to control actions on Azure Sphere via Bluetooth.
To run this lab you'll need the Nordic Semiconductor nRF52 DK Development Kit available and the Azure Sphere Product Team Azure Sphere Samples repo cloned.
Please follow the steps as outlined in WifiSetupAndDeviceControlViaBle to connect the Nordic Semiconductor nRF52 Development Kit
In case you want to use the AVNET Starter Kit (Rev2) together with the nRF 52 DK Development Kit, the wiring should then look like:
You also need to update the used HW pins as well as the "Capabilities"-section in app_manifest.json:
SAMPLE_NRF52_RESET in main.c#L315
is expanded to MT3620_GPIO5. The RST-pin on the Clickboard socket is connected to GPIO 2 and therefore the line needs to be changed to
GPIO_OpenAsOutput(MT3620_GPIO2, GPIO_OutputMode_OpenDrain, GPIO_Value_Low);The used SAMPLE_NRF52_UART in main.c#L336
is expanded into MT3620_ISU0_UART which is the same ISU routed to Click socket #1 with SPI printout.
The WifiSetupAndDeviceControlViaBle-Sample
doesn't use SAMPLE_NRF52_DFU so no change there.
As Lab #7 already involves the Nordic Semiconductor nRF 52 Development Kit, this lab re-uses it to showcase how to update the firmware of another Micro Controller. This covers scenarios, where Azure Sphere is retro-fit as a Guardian Module to an existing MCU-based controller board.
For this lab you'll need the Azure Sphere Product Team Azure Sphere Samples repo cloned and the Nordic Semiconductor nRF52 DK Development Kit available .
Please follow the steps as outlined in External MCU Update.
In case you want to use the AVNET Starter Kit (Rev2) together with the nRF 52 DK Development Kit, the wiring should then look like:
You also need to update the used HW pins in the software as well as the "Capabilities"-section in the appmanifest.json:
SAMPLE_NRF52_RESETSAMPLE_NRF52_RESET in main.c#L159
is expanded to MT3620_GPIO5. The RST-pin on the Clickboard socket is connected to GPIO 2 and therefore the line needs to be changed to
GPIO_OpenAsOutput(MT3620_GPIO2, GPIO_OutputMode_OpenDrain, GPIO_Value_Low);The used SAMPLE_NRF52_UART in main.c#L1�82
is expanded into MT3620_ISU0_UART which is the same ISU routed to Click socket #1 with SPI printout again.
The SAMPLE_NRF52_DFU in main.c#L190
expands into MT3620_GPIO44 and the AN-pin on the Clickboard socket is routed to GPIO 42 so you need to update the line to
GPIO_OpenAsOutput(MT3620_GPIO44, GPIO_OutputMode_OpenDrain, GPIO_Value_High);This concludes the labs for the Azure Sphere Train-the-Trainer Bootcamp.
In customer workshops we're typically looking at specific customer scenarios and for commercial applications you'd obviously want to rely on commercial peripherals. Where in the labs I on purpose used a cheap sensor with one-wire protocol to show how to port software from other platforms as well as the intricacies of bit-banging in a (non-realtime) POSIX app, here is a selection of examples on how to connect other peripherals:
Although a micro-controller is typically a headless device and the MT3620 misses graphics capabilities, in many cases you'd at least want to
show some kind of textual or numeric information. Typically these are small displays that come with their own driver chip and in this
example we will connect an OLED display based on the Solomon Systech SSD130x
through I2C. One example is the Grove - OLED Display 0.96 Inch
available through SeeedStudio.
Please follow the steps as outlined in SphereOLED to run this example.
Most of the IO options on Azure Sphere are multiplexed between different functions. For reference pls. find the different functional pinouts below:
Azure Sphere has 4 so called ISU-Blocks (I2C, SPI, UART) for serial communication with peripherals.
For your reference pls. find the pinouts of the I2C, SPI and UART for the Azure Sphere Development Board below:
Azure Sphere allows Universal asynchronous receiver-transmitter communication either in software flow control using a three-wire connection (TX->RX & RX<-TX crossed, Gnd) or with hardware flow control additionally using RTS/CTS.
Pls. keep in mind that Azure Sphere runs on 3.3V !
To raise voltage levels to standard RS232 levels (+/-15V) or when connecting to a 5V based
MCU such as the Arduino UNO you'll need level shifters, otherwise you'll eventually fry the Sphere chip.
THE SAMPLE CODE SOFTWARE IS PROVIDED "AS IS" AND WITHOUT WARRANTY.TO THE MAXIMUM EXTENT PERMITTED BY LAW, MICROSOFT DISCLAIMS ANY AND ALL OTHER WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, NON - INFRINGEMENT, OR FITNESS FOR A PARTICULAR PURPOSE, WHETHER ARISING BY A COURSE OF DEALING, USAGE OR TRADE PRACTICE OR COURSE OF PERFORMANCE. In no event shall Microsoft, its licensors, the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or the use thereof.
This code may contain errors and/or may not operate correctly. Microsoft undertakes no duty to correct any errors or update the software. Your use of this code is optional and subject to any license provided therewith or referenced therein, if any. Microsoft does not provide you with any license or other rights to any Microsoft product or service through the code provided to you.