Merge pull request #180325 from timlt/nxp-iar

Update NXP 1060 for iar

Author: PMEds28

articles/iot-develop/media/quickstart-devkit-nxp-mimxrt1060-evk/iot-central-device-about-iar.png

@@ -6,15 +6,35 @@ ms.author: timlt
 ms.service: iot-develop
 ms.devlang: c
 ms.topic: quickstart
-ms.date: 06/04/2021
+ms.date: 11/16/2021
+zone_pivot_groups: iot-develop-nxp-toolset
+
+# Owner: timlt
+# - id: iot-develop-nxp-toolset
+#   title: IoT Devices
+#   prompt: Choose a build environment
+#   pivots:
+#   - id: iot-toolset-cmake
+#     title: CMake
+#   - id: iot-toolset-iar-ewarm
+#     title: IAR EWARM
+#   - id: iot-toolset-mcuxpresso
+#     title: MCUXpresso
+
+#Customer intent: As a device builder, I want to see a working IoT device sample connecting to IoT Hub and sending properties and telemetry, and responding to commands. As a solution builder, I want to use a tool to view the properties, commands, and telemetry an IoT Plug and Play device reports to the IoT hub it connects to.
 ---
 
 # Quickstart: Connect an NXP MIMXRT1060-EVK Evaluation kit to IoT Central
 
 **Applies to**: [Embedded device development](about-iot-develop.md#embedded-device-development)<br>
 **Total completion time**:  30 minutes
 
+:::zone pivot="iot-toolset-cmake"
 [![Browse code](media/common/browse-code.svg)](https://github.com/azure-rtos/getting-started/tree/master/NXP/MIMXRT1060-EVK)
+:::zone-end
+:::zone pivot="iot-toolset-iar-ewarm"
+[![Browse code](media/common/browse-code.svg)](https://github.com/azure-rtos/samples/)
+:::zone-end
 
 In this quickstart, you use Azure RTOS to connect the NXP MIMXRT1060-EVK Evaluation kit (hereafter, the NXP EVK) to Azure IoT.
 
@@ -24,6 +44,7 @@ You will complete the following tasks:
 * Build an image and flash it onto the NXP EVK
 * Use Azure IoT Central to create cloud components, view properties, view device telemetry, and call direct commands
 
+:::zone pivot="iot-toolset-cmake"
 ## Prerequisites
 
 * A PC running Windows 10
@@ -173,14 +194,118 @@ You can use the **Termite** app to monitor communication and confirm that your d
 
 Keep Termite open to monitor device output in the following steps.
 
+:::zone-end
+:::zone pivot="iot-toolset-iar-ewarm"
+
+
+## Prerequisites
+
+* A PC running Windows 10 or Windows 11
+
+* Hardware
+
+  * The [NXP MIMXRT1060-EVK](https://www.nxp.com/design/development-boards/i-mx-evaluation-and-development-boards/mimxrt1060-evk-i-mx-rt1060-evaluation-kit:MIMXRT1060-EVK) (NXP EVK)
+  * USB 2.0 A male to Micro USB male cable
+  * Wired Ethernet access
+  * Ethernet cable
+
+* IAR Embedded Workbench for ARM (IAR EW). You can download and install a  [14-day free trial of IAR EW for ARM](https://www.iar.com/products/architectures/arm/iar-embedded-workbench-for-arm/).
+
+* Download the [Azure_RTOS_6.1_MIMXRT1060_IAR_Samples_2021_11_03.zip](https://github.com/azure-rtos/samples/releases/download/v6.1_rel/Azure_RTOS_6.1_MIMXRT1060_IAR_Samples_2021_11_03.zip) file and extract it to a working directory. Choose a directory with a short path to avoid compiler errors when you build.
+
+[!INCLUDE [iot-develop-embedded-create-central-app-with-device](../../includes/iot-develop-embedded-create-central-app-with-device.md)]
+
+## Prepare the device
+
+In this section you use IAR EW IDE to modify a configuration file for Azure IoT settings, build the sample client application, then download and run it on the device.
+
+### Connect the device
+
+1. On the NXP EVK, locate the **Reset** button, the Micro USB port, and the Ethernet port.  You use these components in the following steps. All three are highlighted in the following picture:
+
+    :::image type="content" source="media/quickstart-devkit-nxp-mimxrt1060-evk/nxp-evk-board.png" alt-text="Locate key components on the NXP EVK board":::
+
+1. Connect the Micro USB cable to the Micro USB port on the NXP EVK, and then connect it to your computer. After the device powers up, a solid green LED shows the power status.
+1. Use the Ethernet cable to connect the NXP EVK to an Ethernet port.
+
+### Configure, build, flash, and run the image
+
+1. Open the **IAR EW** app on your computer.
+
+1. Select **File > Open workspace**, navigate to the *mimxrt1060\iar* folder in the working folder where you extracted the zip file, and open the ***azure_rtos.eww*** workspace file. 
+
+    :::image type="content" source="media/quickstart-devkit-nxp-mimxrt1060-evk/open-project-iar.png" alt-text="Open the IAR workspace":::
+
+1. Right-click the **sample_azure_iot_embedded_sdk_pnp** project in the left **Workspace** pane and select **Set as active**.
+
+1. Expand the project, then expand the **Sample** subfolder and open the *sample_config.h* file.
+
+1. Near the top of the file uncomment the `#define ENABLE_DPS_SAMPLE` directive.
+
+    ```c
+    #define ENABLE_DPS_SAMPLE
+    ```
+
+1. Set the Azure IoT device information constants to the values that you saved after you created Azure resources. The `ENDPOINT` constant is set to the global endpoint for Azure Device Provisioning Service (DPS).
+
+    |Constant name|Value|
+    |-------------|-----|
+    | `ENDPOINT` | "global.azure-devices-provisioning.net" |
+    | `ID_SCOPE` | {*Your ID scope value*} |
+    | `REGISTRATION_ID` | {*Your Device ID value*} |
+    | `DEVICE_SYMMETRIC_KEY` | {*Your Primary key value*} |
+
+    > [!NOTE]
+    > The`ENDPOINT`, `ID_SCOPE`, and `REGISTRATION_ID` values are set in a `#ifndef ENABLE_DPS_SAMPLE` statement. Make sure you set the values in the `#else` statement, which will be used when the `ENABLE_DPS_SAMPLE` value is defined.
+
+1. Save the file.
+
+1. Select **Project > Batch Build**. Then select **build_all** and **Make** to build all projects. You will see build output in the **Build** pane. Confirm the successful compilation and linking of all sample projects.
+
+1. Select the green **Download and Debug** button in the toolbar to download the program.
+
+1. After the image has finished downloading, Select **Go** to run the sample.
+
+1. Select **View > Terminal I/O** to open a terminal window that prints status and output messages.
+
+### Confirm device connection details
+
+In the terminal window, you should see output like the following, to verify that the device is initialized and connected to Azure IoT.
+
+```output
+DHCP In Progress...
+IP address: 192.168.1.24
+Mask: 255.255.255.0
+Gateway: 192.168.1.1
+DNS Server address: 192.168.1.1
+SNTP Time Sync...0.pool.ntp.org
+SNTP Time Sync successfully.
+[INFO] Azure IoT Security Module has been enabled, status=0
+Start Provisioning Client...
+[INFO] IoTProvisioning client connect pending
+Registered Device Successfully.
+IoTHub Host Name: iotc-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.azure-devices.net; Device ID: mydevice.
+Connected to IoTHub.
+Sent properties request.
+Telemetry message send: {"temperature":22}.
+Received all properties
+[INFO] Azure IoT Security Module message is empty
+Telemetry message send: {"temperature":22}.
+Telemetry message send: {"temperature":22}.
+```
+
+Keep the terminal open to monitor device output in the following steps.
+
+:::zone-end
+
 ## Verify the device status
 
 To view the device status in IoT Central portal:
 1. From the application dashboard, select **Devices** on the side navigation menu.
 1. Confirm that the **Device status** is updated to **Provisioned**.
-1. Confirm that the **Device template** is updated to **Getting Started Guide**.
+1. Confirm that the **Device template** is updated to **Thermostat**.
 
-    :::image type="content" source="media/quickstart-devkit-nxp-mimxrt1060-evk/iot-central-device-view-status.png" alt-text="Screenshot of device status in IoT Central":::
+    :::image type="content" source="media/quickstart-devkit-nxp-mimxrt1060-evk/iot-central-device-view-iar-status.png" alt-text="Screenshot of device status in IoT Central":::
 
 ## View telemetry
 
@@ -193,37 +318,69 @@ To view telemetry in IoT Central portal:
 1. View the telemetry as the device sends messages to the cloud in the **Overview** tab.
 1. The temperature is measured from the MCU wafer.
 
+    :::zone pivot="iot-toolset-cmake"
     :::image type="content" source="media/quickstart-devkit-nxp-mimxrt1060-evk/iot-central-device-telemetry.png" alt-text="Screenshot of device telemetry in IoT Central":::
-
-    > [!NOTE]
-    > You can also monitor telemetry from the device by using the Termite app.
+    :::zone-end
+    :::zone pivot="iot-toolset-iar-ewarm"
+     :::image type="content" source="media/quickstart-devkit-nxp-mimxrt1060-evk/iot-central-device-telemetry-iar.png" alt-text="Screenshot of device telemetry in IoT Central":::
+    :::zone-end
 
 ## Call a direct method on the device
 
-You can also use IoT Central to call a direct method that you've implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout. In this section, you call a method that enables you to turn an LED on or off.
+You can also use IoT Central to call a direct method that you've implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout. 
 
 To call a method in IoT Central portal:
+:::zone pivot="iot-toolset-cmake"
 
 1. Select the **Command** tab from the device page.
 1. In the **State** dropdown, select **True**, and then select **Run**. There will be no change on the device as there isn't an available LED to toggle; however, you can view the output in Termite to monitor the status of the methods.
 
     :::image type="content" source="media/quickstart-devkit-nxp-mimxrt1060-evk/iot-central-invoke-method.png" alt-text="Screenshot of calling a direct method on a device in IoT Central":::
 
 1. In the **State** dropdown, select **False**, and then select **Run**.
+:::zone-end
+:::zone pivot="iot-toolset-iar-ewarm"
+
+1. Select the **Command** tab from the device page.
+
+1. In the **Since** field, use the date picker and time selectors to set a time, then select **Run**.
+
+    :::image type="content" source="media/quickstart-devkit-nxp-mimxrt1060-evk/iot-central-invoke-method-iar.png" alt-text="Screenshot of calling a direct method on a device in IoT Central":::
+
+1. You can see the command invocation in the terminal. In this case, because the sample thermostat application prints a simulated temperature value, there won't be minimum or maximum values during the time range.
+
+    ```output
+    Received command: getMaxMinReport
+    ```
+
+    > [!NOTE]
+    > You can also view the command invocation and response on the **Raw data** tab on the device page in IoT Central.
+
+:::zone-end
 
 ## View device information
 
 You can view the device information from IoT Central.
 
 Select **About** tab from the device page.
 
+:::zone pivot="iot-toolset-cmake"
 :::image type="content" source="media/quickstart-devkit-nxp-mimxrt1060-evk/iot-central-device-about.png" alt-text="Screenshot of device information in IoT Central":::
+:::zone-end
+:::zone pivot="iot-toolset-iar-ewarm"
+:::image type="content" source="media/quickstart-devkit-nxp-mimxrt1060-evk/iot-central-device-about-iar.png" alt-text="Screenshot of device information in IoT Central":::
+:::zone-end
 
 ## Troubleshoot and debug
 
 If you experience issues building the device code, flashing the device, or connecting, see [Troubleshooting](troubleshoot-embedded-device-quickstarts.md).
 
+:::zone pivot="iot-toolset-cmake"
 For debugging the application, see [Debugging with Visual Studio Code](https://github.com/azure-rtos/getting-started/blob/master/docs/debugging.md).
+:::zone-end
+:::zone pivot="iot-toolset-iar-ewarm"
+For help debugging the application, see the selections under **Help** in **IAR EW for ARM**.  
+:::zone-end
 
 ## Clean up resources
 
@@ -240,9 +397,9 @@ In this quickstart, you built a custom image that contains Azure RTOS sample cod
 As a next step, explore the following articles to learn more about using the IoT device SDKs to connect devices to Azure IoT. 
 
 > [!div class="nextstepaction"]
-> [Connect a simulated device to IoT Central](quickstart-send-telemetry-central.md)
+> [Connect a device to IoT Central](quickstart-send-telemetry-central.md)
 > [!div class="nextstepaction"]
-> [Connect a simulated device to IoT Hub](quickstart-send-telemetry-iot-hub.md)
+> [Connect a device to IoT Hub](quickstart-send-telemetry-iot-hub.md)
 
 > [!IMPORTANT]
 > Azure RTOS provides OEMs with components to secure communication and to create code and data isolation using underlying MCU/MPU hardware protection mechanisms. However, each OEM is ultimately responsible for ensuring that their device meets evolving security requirements.

articles/iot-develop/media/quickstart-devkit-nxp-mimxrt1060-evk/iot-central-device-telemetry-iar.png

@@ -1463,4 +1463,13 @@ groups:
   - id: client-clitier
     title: CLI
   - id: client-portaltier
-    title: Azure portal
+    title: Azure portal
+# Owner: timlt
+- id: iot-develop-nxp-toolset
+  title: IoT Devices
+  prompt: Choose a build environment
+  pivots:
+  - id: iot-toolset-cmake
+    title: CMake
+  - id: iot-toolset-iar-ewarm
+    title: IAR EWARM