Chirp + Microsoft: Effortless provisioning for Azure IoT devices

James Nesfield
Aug 14, 2018 · 2 min read

Anyone who has tried to connect a smart device to a new Wi-Fi network can testify that it’s an awkward and often painful process.

That’s why we’re delighted to announce that we’ve been working with Microsoft on a system to seamlessly provision new IoT devices to the Azure Cloud with nothing more than a single Chirp tone.

Microsoft demonstrate their Azure MXChip + Chirp solution

https://channel9.msdn.com/Shows/Internet-of-Things-Show/Chirp-your-device-into-Azure-IoT-Central

Provisioning these IoT devices has traditionally demanded that users spend several minutes turning the device into a WiFi hotspot, connecting to that using a laptop or smartphone, and setting the credentials — a complex and labour-intensive manual process that many customers have long struggled with.

That all changes with Microsoft adoption of Chirp for Azure MXChip onboarding.

The Microsoft Azure MXChip

Here’s how Microsoft’s provisioning for IoT devices using Chirp works:

  1. Credentials are converted into sound and broadcast from a phone or laptop’s loudspeaker.
  2. A nearby offline device running the Chirp Arm SDK receive the data over audio and use the credentials to connect and authenticate with the network.
  3. That’s it.

Now, leveraging Chirp’s leading data-over-sound technology, users can provision IoT devices, including MXChip, frictionlessly and in seconds rather than minutes.

The new Chirp Arm C SDK

Following the announcement of the collaboration between our two companies, Chirp has released for the first time its free C SDK for the MXChip board adding new possibilities for the board to interact with the environment.

The SDK is available for developers to try for free today : developers.chirp.io.

This is a big milestone for data-over-sound, as it marks the first public release of the Chirp SDK for Arm processors. We’ve harnessed the power of Arm’s CMSIS optimised DSP library to enable low-power real-time Chirp encoding and decoding on the Cortex-M4 and Cortex-M7 chips — which means you can add data-over-sound capabilities to your embedded devices at a sub-dollar cost per unit.

And if you already have an M4- or M7-based device with audio I/O, then your system is already Chirp-ready with no addition to your BOM. It works with any consumer MEMS microphone and speaker and is extremely robust to environmental noise and interference.


Chirp enables data to be transferred via sound, using a device’s existing speaker and microphone. It can use audible or ultrasonic frequencies, works in the most challenging acoustic environments, and does not need a network connection.

To learn more visit https://chirp.io.

Chirp

Written by the team at Chirp, the world's most trusted data-over-sound technology used by the leading brands in over 90 countries. Find out more at www.chirp.io

James Nesfield

Written by

Chirp

Chirp

Written by the team at Chirp, the world's most trusted data-over-sound technology used by the leading brands in over 90 countries. Find out more at www.chirp.io

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade