Blink the Sphere

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active
 

or start with the Seeed Studio solution for Azure Sphere Development Kit

Introduction

These notes were prepared to assist with the preparation of tutorials for the Microsoft Azure Sphere solution using the Seeed Studio Development Kit. The standards for the solution are evolving and the kit may require engineering revisions. This article may not be updated to reflect these later changes. Please consult the references for more authoritative information.

 

Tasks 

The key tasks for the assessment of the Azure Sphere Development Kit (ASDK) are:

 

  • Validate pre-requisites for Azure Sphere
  • Install Azure Sphere
  • Configure access account
  • Configure device
  • Deploy initial application

Prerequisites for Azure Sphere

The prerequisites for conducting assessment of Azure Sphere are:

  • Azure Sphere Development Kit
  • Desktop running Windows 10 Anniversary Update or later
    • e.g. Windows 10, version 1607
  • USB connectivity with aforesaid desktop
  • Integrated Development Environment
    • Visual Studio 2017 version 15.7 or later as one of the following:
      • Enterprise
      • Professional
      • Community

Azure Sphere Development Kit

A representative Azure Sphere Development Kit is available from Seeed Studio. It is currently available in three specific versions only:

  • US
  • Japan
  • EU

 

The key features of the MT3620 development board are: 

  • Programmable buttons and LED
  • Interface headers for Input/Output (4 banks)
  • Configurable main and auxiliary Wi-Fi antennae
  • Ground-loop test point
  • Configurable power supply

 

Buttons and LEDs

The board support supports the following buttons and LEDs: 

Device Description Reference GPIO Pin
Button User button A GPIO12 27
Button User button B GPIO13 28
Button Reset      
LED Red 1 GPIO8 21
LED Green 1 GPIO9 22
LED Blue 1 GPIO10 25
LED Red 2 GPIO8 30
LED Green 2 GPIO9 31
LED Blue 2 GPIO10 32
LED Red 3 GPIO8 33
LED Green 3 GPIO9 34
LED Blue 3 GPIO10 35
LED Red 4 GPIO8 36
LED Green 4 GPIO9 37
LED Blue 4 GPIO10 38
LED Red Application status GPIO45 62
LED Green Application status GPIO46 63
LED Blue Application status GPIO47 64
LED Red Wi-Fi status GPIO48 65
LED Green Wi-Fi status GPIO15 29
LED Blue Wi-Fi status GPIO11 26
LED Green Activity n/a n/a
LED Red Power on n/a n/a

Interface Headers

The diagram below, courtesy Microsoft documentation, illustrates the four banks of interface headers on the board:

ASDK interface header
Interface header 

Naturally, in due course, some third-party solutions may offer Hardware Attach on Top (HAT) board to extend the potential of Azure Sphere. Seeed Studio offers, in their terminology, a shield for the stated purpose of interfacing their rich repertoire of sensors that already have wiring with end plugs for quick and easy connections.

 

The table below enumerates the pin assignments for each of the four header sections on the board:

 

Header

Description

Reference

Pin

Pin

Reference

Description

1 - upper-left

System reset

SYS_RST_B

1

2

GND

Ground

1 - upper-left

GPIO

GPIO59

3

4

GPIO0

GPIO

1 - upper-left

GPIO

GPIO56

5

6

GPIO1

GPIO

1 - upper-left

GPIO

GPIO58

7

8

GPIO2

GPIO

1 - upper-left

GPIO

GPIO57

9

10

GPIO3

GPIO

1 - upper-left

GPIO

GPIO60

11

12

GPIO4

GPIO

2 - lower-left

ISU0 UART

RXD0

1

2

GND

Ground

2 - lower-left

ISU0 UART

TXD0

3

4

GPIO5

GPIO

2 - lower-left

ISUO UART

CTS0

5

6

GPIO6

GPIO

2 - lower-left

ISU0 UART

RTS0

7

8

GPIO7

GPIO

2 - lower-left

GPIO

GPIO30

9

10

 

N/A

2 - lower-left

GPIO

GPIO41

11

12

GPIO43

GPIO

2 - lower-left

GPIO

GPIO42

13

14

GPIO44

GPIO

3 - upper-right

5 V (out)

5V

1

2

GND

Ground

3 - upper-right

3.3 V (in/out)

3.3V

3

4

N/A

N/A

3 - upper-right

ISU3 UART 3

TXD3

5

6

N/A

N/A

3 - upper-right

ISU3 UART 3

RTS3

7

8

N/A

N/A

3 - upper-right

ISU3 UART 3

RXD3

9

10

N/A

N/A

3 - upper-right

ISU3 UART 3

CTS3

11

12

GPIO70

GPIO

4 - lower-right

N/A

N/A

1

2

GND

Ground

4 - lower-right

N/A

N/A

3

4

N/A

N/A

4 - lower-right

ISU1 UART

RXD1

5

6

RXD2

ISU2 UART

4 - lower-right

ISU1 UART

TXD1

7

8

TXD2

ISU2 UART

4 - lower-right

ISU1 UART

CTS1

9

10

CTS2

ISU2 UART

4 - lower-right

ISU1 UART

RTS1

11

12

RTS2

ISU2 UART

4 - lower-right

GPIO

GPIO35

13

14

GPIO40

GPIO

 

Wi-Fi Antennae

The board has the following options for wireless connectivity:

  • Two dual-band chip antennae (primary and secondary)
  • Two RF connectors for external antennae

 

The default configuration uses the primary on-board antennae. The use of the RF connectors requires re-orientation of the corresponding capacitor. For the limited purposes of this note, the primary on-board chip antenna will be used with the C23 capacitor in the default position.

 

Ground Loop Test Point

The board has a ground loop test point for lab test purposes. This point is adjacent to button B above the barrel connection socket for 5V DC.

 

Power Supply

Power to the board is fed externally either through a 5 V DC supply or the USB connection. If both connections are active then there is internal protection to suppress reverse feed to the USB connection. The circuit prevents over-current conditions. The following table provides reference information on the nominal current consumption:

 

Usage

Current, mA

Max demand

600

Normal operations

225

Wi-Fi data transfer

475

 

The real-time clock on the board must be powered for theA coin battery (CR2032) can provide standalone power to the internal real-time clock on the board.

 

The table below describes the options for the three jumpers related to power supply on the board:

 

Jumper

Reference

Pin Setting

Description

J1

ADC VREF

1,2 linked via jumper connection

2.5 V output from board is ADC VREF

 

 

1 connected to external 1.8 V reference

 

J2

3V3 isolation

1,2 linked via jumper connection

On-board power supply for 3.3 V DC

 

 

2 connected to external 3.3 V reference

External source for 3.3 V DC to board

J3

RTC supply

1,2 linked via jumper connection

RTC uses coin battery for power

 

 

2,3 linked via jumper connection

RTC uses board for power

 

 

2 connected to external 3.3 V source

RTC uses external source for power

  

Install Azure Sphere

The installation of components

  • Hardware
  • Software  

Hardware

This phase of the installation confirms the attachment of the ASDK board to the desktop platform. Use the Device Manager utility on the desktop before and after attaching the board through an available USB port to obtain the names of the three COM ports that assigned to the board. The examples below illustrate the findings with two machines designated as A and B.

Machine A - Before

There are two active COM ports before the connection from the desktop to the ASKD board for Machine A, as shown below:

Machine A - Before

Machine A - After

 

Machine B - Before

There is only one active COM port before the connection from the desktop to the ASDK board for Machine B, as shown below:

COM ports
Machine B - Before

Machine B - After

There are three additional COM ports after the connection from the desktop to ASDK board for Machine B, as shown below:

Machine B - After 

Software

This phase of the installation confirms that the corresponding Azure Sphere SDK is configured for use under Visual Studio. There are two ways to install the SDK for use under Visual Studio:

  • Navigate from the menu bar Tools ==> Extension and Updates and search/install the Azure Sphere SDK under the Online group
  • Down load the installer for Azure Sphere SDK and run the executable file from the command line

 You will have to exit the Visual Studio session (if active) to complete the installation.

VIX packages for ASDK
Tools & Extensions for ASDK

After you restart you can confirm the installation as shown above. There will be an entry for Azure Sphere in the Start menu for command line operations. 

Configure Access Account

Azure Sphere requires an organizational account that is associated with Azure Active Directory. If you do not have an existing account that works with Azure Sphere, your options are to:

  • Create a new account and directory unassociated with any other account
  • Create a work/school account associated with existing personal/MSA account 

Associate Personal/MSA Account

  • Logon to Azure portal using existing personal/MSA account
  • Drill down from Azure Active Directory on the left pane
  • On the right pane, under Manage, click Users
  • On the toolbar on the cascading pane, click New user and enter data for the following fields:
    • Name
    • User name
    • Select Directory role as Global Administrator
    • On the Directory role pane, click OK button to dismiss the pane
  • On the User pane, click Create button 

The list of user names will now have a new account based on the data entered in the current steps.

Azure for ASDK
Azure Access Account 

Claim the device

The following operation, designated as device claim, permits the corresponding discrete device to participate in the Azure Sphere ecosystem through a permanent a permanent assignment to a tenant. This operation can be performed only once owing to g of a unique identifier that cannot be modified for the device.

 

For current preview purposes, the best practice is to restrict to a single tenant for the company or organization in the Azure Sphere operations.

  • Connect the ASDK device to a desktop that will be used for the development exercises
  • From the Start menu on the desktop, launch Azure Sphere Development Command Prompt:
Command line
Azure Sphere Command Terminal
  • At the prompt, enter the following command:
    azsphere login
  • Use the previously established credential to logon; the initial value for this credential is provided by Azure during account setup and it has to be changed upon first logon. Enable consent for access, if required.
  • Sign in using the following command with previously established credentials
C:\Windows\system32>azsphere
tenant create --name ASDK-tenant
Created a new
Azure Sphere tenant:
 --> Tenant Name: ASDK-tenant
 --> Tenant ID:   f9726741-4c56-43fd-b781-c37a7249096e
Selected
Azure Sphere tenant 'ASDK-tenant' as the default.
You may now
wish to claim the attached device into this tenant using 'azsphere device
claim'.
Command
completed successfully in 00:01:20.3447117.
  • A device can be claimed only once owing to security considerations. Claim the device as instructed using the following command:

azure device claim 

C:\Windows\system32>azsphere
device claim
Claiming
device.
Successfully
claimed device ID
'A0B90D018BFC9E9B3A2A9DB2A495A10DA5542044C3E2EAF0919E45F858B5001907A16B9A660FFF296323E627B6620115940A2404AF9ABF2A7A079403586F4E69'
into tenant 'ASDK-tenant' with ID 'f9726741-4c56-43fd-b781-c37a7249096e'.
Command
completed successfully in 00:00:02.8783388.
  • In the event of any warning message about deprecated software, initiate device recovery with the following command:

 

azsphere device recover

  

C:\Windows\system32>azsphere device recover

Starting device recovery. Please note that this may take up to 10 minutes.

Board found. Sending recovery bootloader.

Erasing flash.

Sending images.

Sending image 1 of 16.

Sending image 16 of 16.

Finished writing images; rebooting board.

Device ID: A0B90D018BFC9E9B3A2A9DB2A495A10DA5542044C3E2EAF0919E45F858B5001907A16B9A660FFF296323E627B6620115940A2404AF9ABF2A7A079403586F4E69

Device recovered successfully.

Command completed successfully in 00:02:40.6220829.

 

Configure Wi-Fi for device

 

The following steps configure the Wi-Fi access for the device upon initial configuration after connection to the desktop using the USB connection.

 

  • At the Azure Sphere Development Command prompt, enter the following command:

azsphere device wifi show-status

The output in the terminal window will be similar that shown below:

 

C:\Windows\system32>azsphere
device wifi show-status
SSID                :
Configuration
state : unknown
Connection
state    : disconnected
Security
state      : unknown
Frequency           :
Mode                :
Key
management      : UNKNOWN
WPA
State           : DISCONNECTED
IP
Address          :
MAC
Address         : 2c:f7:f1:08:7e:7e

 

Command completed successfully in 00:00:01.2698310.

 

  • Use the following command to enable access to the Wi-Fi network (substitute your local values for MySSID and MyKEY below:

azsphere device wifi add --said MySSID --key MyKEY

C:\Windows\system32>azsphere
device wifi add --ssid MySSID --key MyKEY
Add network
succeeded:
ID                  : 0
SSID                : MySSID
Configuration
state : enabled
Connection
state    : unknown
Security
state      : psk
 
Command completed successfully in 00:00:01.7617272.

 

  • Validate the Wi-Fi configuration with the following command:

azsphere device wifi show-status

The output will be similar to that shown below:

 

C:\Windows\system32>azsphere
device wifi show-status
SSID                : MySSID
Configuration
state : enabled
Connection
state    : connected
Security
state      : psk
Frequency           : 5785
Mode                : station
Key
management      : WPA2-PSK
WPA
State           : COMPLETED
IP
Address          : 192.168.2.117
MAC
Address         : 2c:f7:f1:08:7e:7e

 

Command completed successfully in 00:00:01.1902350.

 

  • To stay with updates (if practical), use the following command:

 

azsphere device show-ota-status

 

The output will be similar to that shown below:

 

C:\Windows\system32>azsphere
device show-ota-status
Your device
is running Azure Sphere OS version 18.11.
The Azure
Sphere Security Service is targeting this device with Azure Sphere OS version
18.11.
Your device
has the expected version of the Azure Sphere OS: 18.11.
Command
completed successfully in 00:00:03.7314050.

First Application

The first application to evaluate the Azure Sphere Development Kit is naturally to Blink one of the many on-board LED devices.

 

Prerequisites

The three prerequisites for the demonstration of a starter application to Blink an LED device on the board are:

  • Internet connectivity; use the steps in the preceding sections to establish this connectivity, if necessary
  • The Integrated Development Environment configuration has the required extensions for Azure Sphere Development Kit SDK
  • Development setting; owing to security considerations a board does not permit updates unless authorization for this purpose is explicitly set. The following command prepares the board to receive updates:

azsphere device prep-debug

The output will be similar to that shown below: 

C:\Windows\system32>azsphere
device prep-debug
Getting
device capability configuration for application development.
Downloading
device capability configuration for device ID
'A0B90D018BFC9E9B3A2A9DB2A495A10DA5542044C3E2EAF0919E45F858B5001907A16B9A660FFF296323E627B6620115940A2404AF9ABF2A7A079403586F4E69'.
Successfully
downloaded device capability configuration.
Successfully
wrote device capability configuration file
'C:\Users\Reza\AppData\Local\Temp\tmp7FB.tmp'.
Setting
device group ID 'cd037ae5-27ca-4a13-9e3b-2a9d87f9d7be' for device with ID
'A0B90D018BFC9E9B3A2A9DB2A495A10DA5542044C3E2EAF0919E45F858B5001907A16B9A660FFF296323E627B6620115940A2404AF9ABF2A7A079403586F4E69'.
Successfully
disabled over-the-air updates.
Enabling
application development capability on attached device.
Applying
device capability configuration to device.
Successfully
applied device capability configuration to device.
The device is
rebooting.
Installing
debugging server to device.
Deploying
'C:\Program Files (x86)\Microsoft Azure Sphere
SDK\DebugTools\gdbserver.imagepackage' to the attached device.
Image package
'C:\Program Files (x86)\Microsoft Azure Sphere
SDK\DebugTools\gdbserver.imagepackage' has been deployed to the attached
device.
Application
development capability enabled.
Successfully
set up device
'A0B90D018BFC9E9B3A2A9DB2A495A10DA5542044C3E2EAF0919E45F858B5001907A16B9A660FFF296323E627B6620115940A2404AF9ABF2A7A079403586F4E69'
for application development, and disabled over-the-air updates.
Command
completed successfully in 00:00:36.5658938.

 

Build and deploy application

 

The key steps are:

 

  • Launch Visual Studio 2017
  • Navigate to create a new project:
    • File -> New -> Project
    • Installed -> Visual C++ -> Cross Platform -> Azure Sphere -> Blink Sample
    • Enter a name for the project
    • Click the OK button
New project
ASDK First Blink Project
  • In the primary source code file, main.c, scroll down to the following line (around line # 96 in the version used for this documentation):

        if (newButtonState == GPIO_Value_Low) {

  • Set a breakpoint at this line (F9 key or click the cursor on the left margin of the line:

 

 

  • On the Toolbar, click Remote GDB Debugger and accept the defaults to deploy the program to the board:Remote GDB Debugger
  • The Output pane at the bottom on the Visual Studio window will display the following message:
Output pane
  • On the ASDK board, press Button A; the code will suspend execution at the breakpoint (set in a previous step of this exercise) and the Autos pane will display the values of key variables:
Breakpoint debug 
  • The value of newButtonState (viz. 0) indicates that the button has been pressed.
  • Click the Continue button
Continue debug mode
  •  The value for newButtonState in the Autos pane will change to 1 indicating that it has been released.
Debug continued 
  • The code changes the blink rate with each iteration after pressing Button A. You can press Button A and Continue buttons in succession a few more times to perceive the change in blink rate visually.
  • Stop the execution of the program by pressing the Stop button
Stop the program

The following section illustrates the deployment of code to the ASDK board without a direct physical connection which is important for devices installed in an operating environment.

Over The Air deployment

The previous exercise relied on the direct connection from a desktop to the ASDK board (USB). One of the preparatory steps in the exercise was to disable Over The Air (OTA) deployment using a command line instruction for the setting. This section disables the debug connection and reverts to the Wi-Fi connection to enable OTA deployment.

OTA preparation

The basic LED blink application used in the previous section will serve as the  candidate for the OTA deployment. The board must be locked to OTA mode to receive the updates. The command to accomplish this shown below:

azsphere device prep-field --newdevicegroupname ASDKOTAgroup1 --newskuname ASDKOTAsku1

Where the parameters are used to assign unique values for OTA use. The output from the command will be similar to that shown below:

 

C:\Windows\system32>azsphere device prep-field --newdevicegroupname ASDKOTAgroup1 --newskuname ASDKOTAsku1

 

Removing applications from device.

 

Component '9c299cf0-e41a-4548-9803-7016d29ce531' deleted or was not present beforehand.

 

Removing debugging server from device.

 

Component '8548b129-b16f-4f84-8dbe-d2c847862e78' deleted or was not present beforehand.

 

Successfully removed applications from device.

 

Locking device.

 

Downloading device capability configuration for device ID 'A0B90D018BFC9E9B3A2A9DB2A495A10DA5542044C3E2EAF0919E45F858B5001907A16B9A660FFF296323E627B6620115940A2404AF9ABF2A7A079403586F4E60'.

 

Successfully downloaded device capability configuration.

 

Applying device capability configuration to device.

 

Successfully applied device capability configuration to device.

 

The device is rebooting.

 

Successfully locked device.

 

Creating a new device group with name 'ASDKOTAgroup1'.

 

Setting device group ID 'd316e8f8-3e1a-44ef-a6e1-9d05677c3146' for device with ID 'A0B90D018BFC9E9B3A2A9DB2A495A10DA5542044C3E2EAF0919E45F858B5001907A16B9A660FFF296323E627B6620115940A2404AF9ABF2A7A079403586F4E60'.

 

Creating a new SKU with name 'ASDKOTAsku1'.

 

Setting product SKU to '8e05ec34-4a19-4330-a6ec-77b22dd07519' for device with ID 'A0B90D018BFC9E9B3A2A9DB2A495A10DA5542044C3E2EAF0919E45F858B5001907A16B9A660FFF296323E627B6620115940A2404AF9ABF2A7A079403586F4E60'.

 

Successfully set up device 'A0B90D018BFC9E9B3A2A9DB2A495A10DA5542044C3E2EAF0919E45F858B5001907A16B9A660FFF296323E627B6620115940A2404AF9ABF2A7A079403586F4E60' for OTA loading.

 

Command completed successfully in 00:00:19.3814335.

Feed list

A unique identifier links an image for subsequent deployment to the ASDK board using OTA. The following command enumerates the current list of deployable images:

azsphere feed list

 

C:\Windows\system32>azsphere feed list

 

Listing all feeds.

 

Retrieved feeds:

 

--> [3369f0e1-dedf-49ec-a602-2aa98669fd61] 'Preview MT3620'

 

Command completed successfully in 00:00:01.8238214.

The current exercise will use the ID for 'Preview MT3620' to link the image for OTA deployment.

Feed link

The command to link the feed is shown below:

azsphere device link-feed --dependentfeedid 3369f0e1-dedf-49ec-a602-2aa98669fd61 --imagepath <path-to-image> --newfeedname <unique-name>

Image path

 The following tables describes the values for the current release:

 

Parameter

Description

Value

dependentfeedid

ID from feed list command

3369f0e1-dedf-49ec-a602-2aa98669fd61

imagepath

path to the image package file

C:\Users\Reza\source\repos\ASDK1stBlink\ASDK1stBlink\bin\ARM\Debug\ASDK1stBlink.imagepackage

newfeedname

Unique name for application in Azure tenancy

ASDK1stBlink

 The corresponding command is shown below:

azsphere
device link-feed --dependentfeedid 3369f0e1-dedf-49ec-a602-2aa98669fd61
--imagepath
"C:\Users\Reza\source\repos\ASDK1stBlink\ASDK1stBlink\bin\ARM\Debug\ASDK1stBlink.imagepackage"
--newfeedname ASDK1stBlink

 The ensuing output from the command for the current exercise is shown below:

 

C:\Windows\system32>azsphere device link-feed --dependentfeedid 3369f0e1-dedf-49ec-a602-2aa98669fd61 --imagepath "C:\Users\Reza\source\repos\ASDK1stBlink\ASDK1stBlink\bin\ARM\Debug\ASDK1stBlink.imagepackage" --newfeedname ASDK1stBlink
Getting the details for device with ID 'A0B90D018BFC9E9B3A2A9DB2A495A10DA5542044C3E2EAF0919E45F858B5001907A16B9A660FFF296323E627B6620115940A2404AF9ABF2A7A079403586F4E60'.
Uploading image from file 'C:\Users\Reza\source\repos\ASDK1stBlink\ASDK1stBlink\bin\ARM\Debug\ASDK1stBlink.imagepackage':
 --> Image ID:       d425f83f-9973-492e-b6bc-5a44a264bd91
 --> Component ID:   9c299cf0-e41a-4548-9803-7016d29ce531
 --> Component name: 'ASDK1stBlink'
Removing temporary state for uploaded image.

Conduct OTA deployment

Press the Reset button on the ASDK board to conduct the OTA deployment. The application will start (I.e. blink the LED device) after the deployment is complete. Use the following command for information on the installed image:

azsphere device image list-installed

The corresponding output for the current application is shown below:

 

C:\Windows\system32>azsphere
device image list-installed
Installed
images:
 --> ASDK1stBlink
   --> Image type:   Application
   --> Component ID:
9c299cf0-e41a-4548-9803-7016d29ce531
   --> Image ID:     d425f83f-9973-492e-b6bc-5a44a264bd91
Command
completed successfully in 00:00:01.2094041.

Revert to development mode

The following command will disable the OTA deployment mode and permit Visual Studio to deploy the image through direct connection:

azsphere device prep-debug

The output is shown below:

 

C:\Windows\system32>azsphere
device prep-debug
Getting
device capability configuration for application development.
Downloading
device capability configuration for device ID
'A0B90D018BFC9E9B3A2A9DB2A495A10DA5542044C3E2EAF0919E45F858B5001907A16B9A660FFF296323E627B6620115940A2404AF9ABF2A7A079403586F4E60'.
Successfully
downloaded device capability configuration.
Successfully
wrote device capability configuration file
'C:\Users\Reza\AppData\Local\Temp\tmpE18D.tmp'.
Setting
device group ID 'cd037ae5-27ca-4a13-9e3b-2a9d87f9d7bd' for device with ID
'A0B90D018BFC9E9B3A2A9DB2A495A10DA5542044C3E2EAF0919E45F858B5001907A16B9A660FFF296323E627B6620115940A2404AF9ABF2A7A079403586F4E60'.
Successfully
disabled over-the-air updates.
Enabling
application development capability on attached device.
Applying
device capability configuration to device.
Successfully
applied device capability configuration to device.
The device is
rebooting.
Installing
debugging server to device.
Deploying
'C:\Program Files (x86)\Microsoft Azure Sphere
SDK\DebugTools\gdbserver.imagepackage' to the attached device.
Image package
'C:\Program Files (x86)\Microsoft Azure Sphere
SDK\DebugTools\gdbserver.imagepackage' has been deployed to the attached
device.
Application
development capability enabled.
Successfully
set up device
'A0B90D018BFC9E9B3A2A9DB2A495A10DA5542044C3E2EAF0919E45F858B5001907A16B9A660FFF296323E627B6620115940A2404AF9ABF2A7A079403586F4E60'
for application development, and disabled over-the-air updates.
Command
completed successfully in 00:00:30.6640425.

 

Summary

This note illustrated the development and deployment of a very simple application using Seeed Studio hardware for Microsoft Azure Sphere Development Kit. 

References

Welcome to Azure Sphere

MT3620 Support Status

Claim your device

Unboxing Azure Sphere Development Kit