Skip to content

Commit 777d79a

Browse files
committed
Address feedback
1 parent fd8c421 commit 777d79a

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/iot/iot-overview-device-development.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.custom: template-overview
1313

1414
# IoT asset and device development
1515

16-
This overview introduces the key concepts around developing assets and devices that connect to typical Azure IoT solutions. Each section includes links to content that provides further detail and guidance. Typically, devices connect directly to cloud services such as IoT Hub and assets connect to services in your edge environment such as Azure IoT Operations. This article includes information about both assets and devices.
16+
This overview introduces the key concepts around developing assets and devices that connect to typical Azure IoT solutions. Each section includes links to content that provides further detail and guidance. Typically, devices connect directly to cloud-based services such as IoT Hub, while assets connect to edge-based services in your environment such as Azure IoT Operations. This article includes information about both assets and devices.
1717

1818
# [Edge-based solution](#tab/edge)
1919

@@ -48,7 +48,7 @@ In Azure IoT, a device developer writes the code to run on the devices in the so
4848

4949
## Asset and device types
5050

51-
An IoT solution can contain many types of [assets](iot-glossary.md#asset) and [devices](iot-glossary.md#device). You typically find devices in cloud-based solutions and assets in edge-based solutions, but this rule isn't absolute.
51+
An IoT solution can contain many types of [assets](iot-glossary.md#asset) and [devices](iot-glossary.md#device). You typically find devices in cloud-based solutions and assets in edge-based solutions. It's also possible to have a hybrid solutions that contain both devices and assets.
5252

5353
# [Edge-based solution](#tab/edge)
5454

@@ -86,6 +86,8 @@ Examples of specialized hardware and operating systems include:
8686

8787
[Eclipse ThreadX](https://github.com/eclipse-threadx/rtos-docs) is a real time operating system for IoT and edge devices powered by MCUs. Eclipse ThreadX is designed to support highly constrained devices that are battery powered and have less than 64 KB of flash memory.
8888

89+
[FreeRTOS](https://www.freertos.org) is a real time operating system for embedded devices. You can use FreeRTOS with the Azure IoT Middleware for FreeRTOS to connect devices to Azure IoT. For an overview of RTOS options for device development, see [C SDK and Embedded C SDK usage scenarios](concepts-using-c-sdk-and-embedded-c-sdk.md).
90+
8991
[Azure Sphere (Integrated)](/azure-sphere/product-overview/what-is-azure-sphere?view=azure-sphere-integrated&preserve-view=true) is a secure, high-level application platform with built-in communication and security features for internet-connected devices. It comprises a secured, connected, crossover MCU, a custom high-level Linux-based operating system, and a cloud-based security service that provides continuous, renewable security.
9092

9193
### Device primitives

0 commit comments

Comments
 (0)