Windows 10: Can we compile Azure IoT C SDK for ArmV4I platform?

Lecomte Edwin · May 25, 2023

Hi everyone,I'm currently trying to compile the Azure IoT C SDK in ArmV4I. My system can't be modified or upgraded and the different solutions on internet to compile only Arm ArmV7 doesn't match with my machine. I've already tried to compile the Az IoT SDK on CMAKE with the Windows mobile 5 SDK coupled with VS 2008 but it doens't run.Machine specs :CPU : i.MX6 solo ArmV4IOS : Windows CE 7.00 build 2882I'll try to respond as fast i can, thanks for all the users that will try to help me.

:)

Brink · May 25, 2023

Announcing Microsoft Azure IoT Device Agent V2 general availability

We are excited to announce the general availability of Microsoft Azure IoT Device Agent V2. The Microsoft Azure IoT Device Agent is an open-source, ready-to-build and package solution for Windows 10 IoT Enterprise and Windows 10 IoT Core operating systems that provides you with built-in capabilities to remotely provision, configure, monitor and manage your IoT devices.

When it comes to the widespread deployment of IoT devices, one of the key challenges is around remote manageability. IoT devices are deployed out in the field or on factory floors where direct device access is not always possible or practical. As an operator, you also want to ensure that you can deploy software and security updates across all the IoT devices in the field to protect and secure the data as well as the device.

What’s new

The Microsoft Azure IoT Device Agent has been in public preview since Jan 2019. If you were using our public preview version, we hope you found it useful and we are eager to know your feedback. With GA, you now have access to the following new features:

1) UWP Management Plugin and UWP bridge: You can now remotely manage your UWP app running on your devices using the UWP management plugin. The Device Agent now includes a UWP bridge which allows UWP applications to leverage a subset of the Device Agent capabilities such as TPM access and reboot.

2) Diagnostics and error reporting: Troubleshooting issues on your IoT devices is a lot easier with quick access to collect logs and error information from the device and upload them to Azure Storage.

3) Device Agent extensibility: Ready-to-use Visual Studio templates and Nugets make it easy for a device developer to create their own plugins and extend the Device Agent’s capabilities.

See the complete list of capabilities below for more information.

Microsoft Azure IoT Device Agent capabilities

The Microsoft Azure IoT Device Agent provides you with the following capabilities to support these scenarios:

Device provisioning: The Microsoft Azure IoT Device Agent integrates with the Azure Device Provisioning Service (DPS) client SDK to automatically provision and create the Azure IoT Hub identities of the device using the Azure Device Provisioning Service. The Device Agent registers the device with the Azure IoT Hub, ensuring the identity assignment of the device and applications running on it. The Microsoft Azure IoT Device Agent leverages Azure IoT Module twin such that each process that connects to the IoT Hub is associated to the same IoT Hub device. If your solution demands that you have a custom provisioning client, you can do so by downloading the Azure Device Provisioning Service device SDK and implementing your own provisioning service.

Manage cloud connectivity: Once the Microsoft Azure IoT Device Agent establishes the connection with the IoT Hub, it continues to manage the Azure cloud connection and the renewal of the SAS token before it expires.

Remote device management: The Microsoft Azure IoT Device Agent provides the following remote device management capabilities via built-in plugins:

Device info: Enables you to retrieve information like Device ID, manufacturer information, firmware version, etc.

Reboot: Enables you to remotely reboot the device or schedule a reboot.

Remote wipe: Enables you to wipe out all data on the device and restore the device to a clean state.

Factory reset: Enables you to apply a factory image on the device bringing it back to its original state.

Time management: Enables you to configure an NTP service and set the time zone on the device.

Windows Update management: Enables you to enforce OS update policies on the device.

Certificate management: Enables you to remotely install or uninstall certificates.

Windows telemetry management: Enables you to configure the level of telemetry that is being reported from the device.

Device Agent’s extensibility: As a device builder, you can write your own plugins which can interface with the Microsoft Azure IoT Device Agent. The Device Agent makes it easy for you to build your own custom code by providing you with the following hooks:

Includes a plugin model to bridge platform components with the agent and consequently with IoT Hub. The plugin model enables discovery, initialization, error reporting and state aggregation. The model includes a Visual Studio template and Nugets, which help you to quickly create your own plugin while abstracting the communication between the Device Agent and your plugin.

When a handler has dependencies on other handlers, Azure IoT Device Agent can make sure that the dependencies are processed in the right order.

Handlers have a versioning model to prevent mismatches in twin schemas or mismatches between plugin versions and the Device Agent.

Remote UWP application management: As a solution operator you can now remotely deploy, update, remove, start, or stop UWP applications on your devices using the UWP management plugin. On Windows IoT Core, you can also designate an application to be the start-up application.

Device Agent plugin capabilities in UWP apps: UWP applications can also leverage the UWP bridge, which enables the UWP application to leverage a limited subset of the functionalities of the Device Agent such as retrieving DPS enrollment information from the TPM or accessing admin-privileged functionality such as reboot.

Diagnostics and error reporting: Errors and diagnostics logs are now easily accessible for troubleshooting purposes using the Microsoft Azure IoT Device Agent.

Solution operators can now collect ETW logs on their IoT devices and upload them back to the cloud for inspection.

The error reports have been enhanced to now include details of the sub-system or the process where the error originally occurred helping users to better interpret error messages.

Getting started

Check out the Quick Start for more information or download the code or exe from this GitHub repo.

We want to hear from you!

As always, your feedback is very important to us! Please share your comments, questions, or concerns on our or comment below. We’re listening!
Click to expand...

Source: Microsoft Azure IoT Device Agent V2 general availability - Windows Developer Blog

Tweet

— Twitter API (@user) View on Twiiter
Click to expand...

Brink · May 25, 2023

Device to Device Communication with Azure IoT Hub

We’ve already seen how to get your devices to send data to the cloud. In most cases, the data is then processed by various Azure services. However, in some cases the cloud is nothing more than a means of communication between two devices.

Imagine a Raspberry Pi connected to a garage door. Telling the Raspberry Pi to open or close the door from a phone should only require a minimal amount of cloud programming. There is no data processing; the cloud simply relays a message from the phone to the Pi. Or perhaps the Raspberry Pi is connected to a motion sensor and you’d like an alert on your phone when it detects movement.

In this blog post, we will experiment with implementing device-to-device communication with as little cloud-side programming as possible. A common pipeline for device-to-device communication involves device A sending a message to the cloud, the cloud processing the message and sending it to device B, and device B receiving this message. In minimizing that middle step, you can create a functional app that only requires the free tier of Azure IoT Hub. It’s a cheap and effective way to design device-to-device communication. So, can two devices talk to each other with almost no cloud-based programming?

The answer, of course, is yes. In order to do this, it is important to understand how Azure IoT Hub and the Azure IoT messaging APIs work. Currently, Azure IoT messaging involves two different APIs – Microsoft.Azure.Devices.Client is used in the app running on the device (it can send device-to-cloud and receive cloud-to-device messages) and Microsoft.Azure.Devices SDK and the ServiceBus SDK are used on the service side (it can send cloud-to-device messages and receive device-to-cloud messages). However, our design proposes something slightly unorthodox. We will run the service SDK on the device receiving messages, so less code goes into the cloud.

To take advantage of the latest advances in security, we will provision our device to securely connect to Azure with the help of the TPM (see our earlier blog post that introduced TPM).

This approach uses a many-to-one messaging model. It allows for a simple design, but limits our capabilities. While many devices can send messages, only one can receive. In order to only accept messages from a specific device, the receiver will filter the messages by the device id.

How does all this work?

For a full sample, see the code here. There are two solutions within this project, as described above. The use of the SDKs in each solution remains mostly unchanged from the standard design outlined in here. We decided to run the service side SDK on the receiving device – however, there is one roadblock. One of the two service side SDKs, ServiceBus, does not support UWP. Fortunately, another library called the AMPQNetLite offers a UWP compatible alternative that can be used to send and receive messages on the service side. This requires a little more work: we needed to connect to the event hub port that IoT Hub exposes, create a session and build the receiver link.

All the connection information needed to set up a receiver with AMQPNetLite can be found in your instance of IoT Hub. You can also use this library to filter incoming messages by device id. See this sample for further details.

What next?

This experiment intentionally keeps the amount of cloud-based programming to a minimum (zero, really). Even still, this opens a set of new opportunities. With this, an IoT device can be remote controlled by any Windows device. However, this system has limitations. Any complex message filtering is currently not supported. Extending this solution to be cross platform (using Android or iOS devices) also proves to be difficult, as AMPQNetLite is not compatible with Xamarin.

If you’re willing to do more and utilize more cloud services (including paid ones), advanced messaging patterns, sophisticated data analysis and long term storage become possible. In particular, Azure Functions allow you to run the receiving code in the cloud, which obviates the need of running AMPQNetLite on the client device.

This blog post focused on the simplest pipeline for device-to-device communication, but what we have built is by no means the only solution. We’re eager to hear your feedback and welcome your ideas on what more can be done.

Divya Mahadevan, a software engineer intern, contributed to this piece (thanks, Divya!)
Click to expand...

Source: Device to Device Communication with Azure IoT Hub | Building Apps for Windows

Brink · May 25, 2023

Announcing Microsoft Azure IoT Device Agent V2 general availability

We are excited to announce the general availability of Microsoft Azure IoT Device Agent V2. The Microsoft Azure IoT Device Agent is an open-source, ready-to-build and package solution for Windows 10 IoT Enterprise and Windows 10 IoT Core operating systems that provides you with built-in capabilities to remotely provision, configure, monitor and manage your IoT devices.

When it comes to the widespread deployment of IoT devices, one of the key challenges is around remote manageability. IoT devices are deployed out in the field or on factory floors where direct device access is not always possible or practical. As an operator, you also want to ensure that you can deploy software and security updates across all the IoT devices in the field to protect and secure the data as well as the device.

What’s new

The Microsoft Azure IoT Device Agent has been in public preview since Jan 2019. If you were using our public preview version, we hope you found it useful and we are eager to know your feedback. With GA, you now have access to the following new features:

1) UWP Management Plugin and UWP bridge: You can now remotely manage your UWP app running on your devices using the UWP management plugin. The Device Agent now includes a UWP bridge which allows UWP applications to leverage a subset of the Device Agent capabilities such as TPM access and reboot.

2) Diagnostics and error reporting: Troubleshooting issues on your IoT devices is a lot easier with quick access to collect logs and error information from the device and upload them to Azure Storage.

3) Device Agent extensibility: Ready-to-use Visual Studio templates and Nugets make it easy for a device developer to create their own plugins and extend the Device Agent’s capabilities.

See the complete list of capabilities below for more information.

Microsoft Azure IoT Device Agent capabilities

The Microsoft Azure IoT Device Agent provides you with the following capabilities to support these scenarios:

Device provisioning: The Microsoft Azure IoT Device Agent integrates with the Azure Device Provisioning Service (DPS) client SDK to automatically provision and create the Azure IoT Hub identities of the device using the Azure Device Provisioning Service. The Device Agent registers the device with the Azure IoT Hub, ensuring the identity assignment of the device and applications running on it. The Microsoft Azure IoT Device Agent leverages Azure IoT Module twin such that each process that connects to the IoT Hub is associated to the same IoT Hub device. If your solution demands that you have a custom provisioning client, you can do so by downloading the Azure Device Provisioning Service device SDK and implementing your own provisioning service.

Manage cloud connectivity: Once the Microsoft Azure IoT Device Agent establishes the connection with the IoT Hub, it continues to manage the Azure cloud connection and the renewal of the SAS token before it expires.

Remote device management: The Microsoft Azure IoT Device Agent provides the following remote device management capabilities via built-in plugins:

Device info: Enables you to retrieve information like Device ID, manufacturer information, firmware version, etc.

Reboot: Enables you to remotely reboot the device or schedule a reboot.

Remote wipe: Enables you to wipe out all data on the device and restore the device to a clean state.

Factory reset: Enables you to apply a factory image on the device bringing it back to its original state.

Time management: Enables you to configure an NTP service and set the time zone on the device.

Windows Update management: Enables you to enforce OS update policies on the device.

Certificate management: Enables you to remotely install or uninstall certificates.

Windows telemetry management: Enables you to configure the level of telemetry that is being reported from the device.

Device Agent’s extensibility: As a device builder, you can write your own plugins which can interface with the Microsoft Azure IoT Device Agent. The Device Agent makes it easy for you to build your own custom code by providing you with the following hooks:

Includes a plugin model to bridge platform components with the agent and consequently with IoT Hub. The plugin model enables discovery, initialization, error reporting and state aggregation. The model includes a Visual Studio template and Nugets, which help you to quickly create your own plugin while abstracting the communication between the Device Agent and your plugin.

When a handler has dependencies on other handlers, Azure IoT Device Agent can make sure that the dependencies are processed in the right order.

Handlers have a versioning model to prevent mismatches in twin schemas or mismatches between plugin versions and the Device Agent.

Remote UWP application management: As a solution operator you can now remotely deploy, update, remove, start, or stop UWP applications on your devices using the UWP management plugin. On Windows IoT Core, you can also designate an application to be the start-up application.

Device Agent plugin capabilities in UWP apps: UWP applications can also leverage the UWP bridge, which enables the UWP application to leverage a limited subset of the functionalities of the Device Agent such as retrieving DPS enrollment information from the TPM or accessing admin-privileged functionality such as reboot.

Diagnostics and error reporting: Errors and diagnostics logs are now easily accessible for troubleshooting purposes using the Microsoft Azure IoT Device Agent.

Solution operators can now collect ETW logs on their IoT devices and upload them back to the cloud for inspection.

The error reports have been enhanced to now include details of the sub-system or the process where the error originally occurred helping users to better interpret error messages.

Getting started

Check out the Quick Start for more information or download the code or exe from this GitHub repo.

We want to hear from you!

As always, your feedback is very important to us! Please share your comments, questions, or concerns on our or comment below. We’re listening!
Click to expand...

Source: Microsoft Azure IoT Device Agent V2 general availability - Windows Developer Blog

Tweet

— Twitter API (@User) View on Twiiter

Windows 10: Can we compile Azure IoT C SDK for ArmV4I platform?

Can we compile Azure IoT C SDK for ArmV4I platform?

Can we compile Azure IoT C SDK for ArmV4I platform?

Can we compile Azure IoT C SDK for ArmV4I platform?

Can we compile Azure IoT C SDK for ArmV4I platform? - Similar Threads - compile Azure IoT

Windows SDK 10.0.26100 causes compilation error in wchar.h with MSVC 2015 compiler

Windows SDK 10.0.26100 causes compilation error in wchar.h with MSVC 2015 compiler

Can we compile Azure IoT C SDK for ArmV4I platform?

Compile C to HEX

priviledges and compiling c++

Glitches about Microsoft Speech SDK 5.1 and Speech Platform SDK 11

Windows IoT Core and Azure IoT Hub – Putting the ‘I’ in IoT

Azure IoT Suite now available

Kafka Connect for Azure IoT Hub