Skip to content
Branch: master
Find file History
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
Chirp_MXChip_SDK
Tools
chirpFirmware
chirpweb
cleanEEPROM
prebuilt_firmware
readme.md

readme.md

Chirp and Azure IoT Central Sample Code

Reference firmware implementation for using Chirp with Azure IoT Central. Plus a web browser based provisioning sample application to quickly get MXChip devices onto Azure IoT Central. You can see Chirp and IoT Central in action in this video:

Chirp and IoT Central

If you only want to checkout this one folder from the experimental repository follow the following instructions to do a sparse checkout of just the Chirp_IoT_Central folder:

mkdir azure-iot-experimental
cd azure-iot-experimental
git init
git remote add -f origin git@github.com:Azure/azure-iot-experimental.git
git config core.sparseCheckout true
echo "Chirp_IoT_Central" >> .git/info/sparse-checkout
git pull origin master

Contents

The sub-directories contain the following content:

  • chirpFirmware - MXChip firmware source for building with Visual Studio Code and the Arduino plugin.
  • Chirp_MXChip_SDK - Include and library files for the MXChip SDK along with the platform.local.txt for compiling with the Chirp SDK library
  • prebuilt_firmware - Pre-built firmware for the MXChip that can be drag-and-dropped onto the device.
  • chirpweb - Web browser application to provision MXChip devices onto Azure IoT Central.
  • cleanEEPROM - Code for cleaning a corrupted EEPROM on the MXChip
  • Tools - Miscelaneous tooling including the python script to build a drag-n-drop firmware .bin

Status

This project is provided to illustrate how you can utilize the Chirp SDK on MXChip to provision devices to services like Azure IoT Central using data transmission over sound. This project is not designed to be production ready but provided as a sample of how to build the Chirp feature into your firmware.

Reporting Security Issues

Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) at secure@microsoft.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.

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.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., label, 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.

You can’t perform that action at this time.