To Dig MT3620 Kits and Discovery Azure Cloud behind

1. MT3620 Kits

The Sphere MT3620 module is based on the MT3620 SoC, which includes built-in Microsoft security, WiFi connectivity, and the combined versatility and power of an Arm Cortex-A7 processor with the low overhead and real-time guarantees of two Arm Cortex-M4F microcontrollers. A suite of on-chip peripherals, real-time clock, Flash, and RAM are also available. In addition to the MT3620, the 33 x 22 mm module includes a dual-band WiFi chip antenna and system clock. Up to 27 configurable GPIOs and three configurable serial ports (UART, I2C, or SPI) are provided as I/Os on the module.

The core part is MT620 SoC, lead to Fast Development to Mass-Commercial Product. This is what I would like to try how long it takes me to build one MVP and prototype design beyond the maker's comfort zone.

With the Click board

2. Azure Cloud

With experience with cloud service like AWS, Azure booming recently.

Like all the cloud service, one shall fully understand the price policy before action, or stunning bill will come unexpectedly.

One small tip, there are chances to waive your misplacing bill with service phone call. Some salary-less university students made the grace, but not for all.

The visual Studio Code comes with installed extension as Azure Sphere and Azure IoT hub for fast development

4. Connect MT3620 Kits

4.1 Claim the device

Every device must be "claimed" by an Azure Sphere tenant. Claiming the device associates its unique, immutable device ID with your Azure Sphere tenant. The Azure Sphere Security Service uses the device ID to identify and authenticate the device.Connect MT3620 to the PC,

azsphere login

4.2 Create an Azure Sphere tenant

An Azure Sphere tenant isolates your Azure Sphere devices and provides a way for you to manage them. The Azure Sphere tenant is used only for Azure Sphere.

azsphere tenant create --name <my-tenant>

4.3 Claim your device. After you claim your device into a tenant, you cannot move it to a different tenant.