As you follow the individual tutorials in the series Getting Started with Azure RTOS, you might experience some common issues. In general, issues can occur in any of the following sources:
- Your environment. Your machine, software, or network setup and connection.
- Your Azure IoT resources. The IoT hub and device that you created to connect to Azure IoT.
- Your device. The physical board and its configuration.
This troubleshooting guide provides suggested resolutions for the most common issues that can occur as you complete the tutorials.
All the troubleshooting steps require that you've completed the following prerequisites for the tutorial you're working in:
- You installed or acquired all prerequisites, and additional software tools, for the specific tutorial in the series Getting Started with Azure RTOS.
- You created an Azure Iot hub, and registered a device, as directed in the tutorial.
- You built an image for the device, as directed in the tutorial.
This issue can occur when you attempt to build the project. It is the result of the project being incorrectly cloned from GitHub. The project contains multiple submodules that will not be cloned by default unless the --recursive flag is used.
- When you clone the repository using Git, confirm that the --recursive option is present.
The issue can occur after you've created Azure resources, and flashed your device. When you try to connect your newly flashed device to Azure IoT, you see a console message like the following:
- Unable to resolve DNS for MQTT Server
- Check the spelling and case of the configuration values you entered for your IoT configuration in the file azure_config.h. The values for some IoT resource attributes, such as
deviceIDandprimaryKey, are case sensitive.
After you flash a device that uses a Wi-Fi connection and try to connect to your Wi-Fi network, you get an error message that Wi-Fi is unable to connect.
- Check your Wi-Fi network frequency and settings. The devices used in the getting started guide all use 2.4 GHz. Confirm that your Wi-Fi router is configured to support a 2.4 GHz network.
- Check the Wi-Fi mode. Confirm what setting you used for the WIFI_MODE constant in the azure_config.h file. Check your Wi-Fi network security or authentication settings to confirm that the Wi-Fi security mode matches what you have in the configuration file.
You can't complete the process of flashing your device. You will know this if you experience any of the following symptoms:
- The *.bin image file that you built does not copy to the device.
- The utility that you're using to flash the device gives a warning or error.
- The utility that you're using to flash the device does not say that programming completed successfully.
- Try using a different Micro USB cable. Some devices and cables are incompatible.
- Try connecting to a different USB port on your computer. A USB port might be disconnected internally, disabled in software, or temporarily in an unusable state.
- Restart your computer.
After you flash your device and connect it to your computer, you get a message like the following in your terminal software:
Failed to initialize the port.
Please verify the COM port settings.
- In the settings for your terminal software, check the Port setting to confirm that the correct port is selected. If there are multiple ports displayed, you can open Windows Device Manager and select the Ports node to find the correct port for your connected device.
After you flash your device successfully and connect it to your computer, you see garbled text output in your terminal software.
- In the settings for your terminal software, confirm that the Baud rate setting is 115,200.
After you flash your device successfully and connect it to your computer, you see no output in your terminal software.
- Confirm that the settings in your terminal software match the settings in the tutorial.
- Restart your terminal software.
- Press the Reset button on your device.
- Confirm that your USB cable is properly connected.
After you flash your device and connect it to your computer, you get a repeated messages like the following in your terminal window:
Failed to publish temperature
- Confirm that the Pricing and scale tier is one of Free or Standard. Basic is not supported as it doesn't support cloud-to-device and device twin communication.
If you reviewed all the previous issues, and you still cannot monitor your device in a terminal or connect to Azure IoT, there might be an issue with your device's hardware or physical configuration. See the manufacturer's page for your device to find documentation and support options.