Home
last modified time | relevance | path

Searched refs:to (Results 1 – 25 of 28) sorted by relevance

12

/NetX-Duo-v6.2.1/addons/azure_iot/docs/
Dazure_rtos_iot_provisioning_client.md21 <p>This routine initializes the device to the IoT provisioning service.</p>
27 | prov_client_ptr [in] | A pointer to a `NX_AZURE_IOT_PROVISIONING_CLIENT`. |
28 | nx_azure_iot_ptr [in] | A pointer to a `NX_AZURE_IOT`.|
29 | endpoint [in] | A pointer to IoT Provisioning endpoint. Must be NULL terminated string. |
31 | id_scope [in] | A pointer to ID Scope. |
33 | registration_id [in] | A pointer to registration ID. |
35 | crypto_array [in] | A pointer to `NX_CRYPTO_METHOD` |
37 | cipher_map [in] | A pointer to `NX_CRYPTO_CIPHERSUITE` |
39 | metadata_memory [in] | A pointer to metadata memory buffer. |
41 | trusted_certificate [in] | A pointer to `NX_SECURE_X509_CERT`, which is server side certs |
[all …]
Dazure_rtos_iot_hub_client.md95 | hub_client_ptr [in] | A pointer to a `NX_AZURE_IOT_HUB_CLIENT`. |
96 | nx_azure_iot_ptr [in] | A pointer to a `NX_AZURE_IOT`.|
97 | host_name [in] | A pointer to IoTHub hostname. Must be NULL terminated string. |
99 | device_id [in] | A pointer to device ID. |
101 | module_id [in] | A pointer to module ID. |
103 | crypto_array [in] | A pointer to `NX_CRYPTO_METHOD` |
105 | cipher_map [in] | A pointer to `NX_CRYPTO_CIPHERSUITE` |
107 | metadata_memory [in] | A pointer to metadata memory buffer. |
109 | trusted_certificate [in] | A pointer to `NX_SECURE_X509_CERT`, which is server side certs |
113 * NX_AZURE_IOT_INVALID_PARAMETER Fail to initialize the Azure IoT hub client due to invalid paramet…
[all …]
Dazure_rtos_iot.md16 … internal thread is created to manage activities related to Azure IoT services. Only one `NX_AZURE…
21 | nx_azure_iot_ptr [in] | A pointer to a NX_AZURE_IOT |
22 | name_ptr [in] | A pointer to a NULL-terminated string indicating the name of the Azure IoT i…
23 | ip_ptr [in] | A pointer to a `NX_IP`, which is the IP stack used to connect to Azure IoT Services…
24 | pool_ptr [in] | A pointer to a `NX_PACKET_POOL`, which is the packet pool used by Azure IoT Servi…
25 | dns_ptr [in] | A pointer to a `NX_DNS`. |
26 | stack_memory_ptr [in] | A pointer to memory to be used as a stack space for the internal thread. …
29 | unix_time_callback [in] | Callback to fetch unix time from platform. |
34 * NX_AZURE_IOT_INVALID_PARAMETER Fail to create the Azure IoT instance due to invalid parameter.
35 * NX_OPTION_ERROR Fail to create the Azure IoT instance due to invalid priority.
[all …]
Dazure_rtos_iot_adu_agent.md22 …to determine if the update is installed or not, typically it is a version string (1.0.0). The inst…
28 | adu_agent_ptr [in] | A pointer to a `NX_AZURE_IOT_ADU_AGENT`. |
29 | iothub_client_ptr [in] | A pointer to a `NX_AZURE_IOT_HUB_CLIENT`.|
30 | manufacturer [in] | A pointer to the manufacturer. Must be NULL terminated string. |
32 | model [in] | A pointer to the model. Must be NULL terminated string. |
34 | installed_criteria [in] | A pointer to the installed criteria string, such as: version string. M…
36 | adu_agent_update_notify [in] | Pointer to a callback function invoked once update is received. |
41 * NX_AZURE_IOT_INVALID_PARAMETER Fail to start the Azure IoT ADU agent due to invalid parameter.
42 * NX_AZURE_IOT_NO_AVAILABLE_CIPHER Fail to start the Azure IoT ADU agent due to no available cipher.
43 * NX_AZURE_IOT_INSUFFICIENT_BUFFER_SPACE Fail to start the Azure IoT ADU agent due to insufficient …
[all …]
Dazure_rtos_iot_json.md16 <p>Initializes an #NX_AZURE_IOT_JSON_READER to read the JSON payload contained within the provided
22 | reader_ptr [out] | A pointer to an #NX_AZURE_IOT_JSON_READER instance to initialize. |
23 | buffer_ptr [in] | An pointer to buffer containing the JSON text to read. |
50 <p>Initializes an #NX_AZURE_IOT_JSON_READER to read the JSON payload contained within #NX_PACKET</p>
56 | reader_ptr [out] | A pointer to an #NX_AZURE_IOT_JSON_READER instance to initialize. |
57 | packet_ptr [in] | A pointer to #NX_PACKET containing the JSON text. |
89 | reader_ptr [in] | A pointer to an #NX_AZURE_IOT_JSON_READER instance to de-initialize |
106 <div style="text-align: right">Move to next JSON token</div>
121 | reader_ptr [in] | A pointer to an #NX_AZURE_IOT_JSON_READER instance containing the JSON to re…
153 | reader_ptr [in] | A pointer to an #NX_AZURE_IOT_JSON_READER instance containing the JSON to re…
[all …]
Dazure_rtos_iot_hub_client_properties.md5 …"text-align: right">Append the necessary characters to a reported property JSON payload belonging …
16 <p>This routine appends the necessary characters to a reported properties JSON payload belonging to…
36 | hub_client_ptr [in] | A pointer to a `NX_AZURE_IOT_HUB_CLIENT`. |
37 | writer_ptr [in] | A pointer to a #NX_AZURE_IOT_JSON_WRITER. |
38 | component_name_ptr [in] | A pointer to a component name. |
58 …ext-align: right">Append the necessary characters to end a reported property JSON payload belongin…
67 <p>This routine appends the necessary characters to end a reported properties JSON payload</p>
80 | hub_client_ptr [in] | A pointer to a `NX_AZURE_IOT_HUB_CLIENT`. |
81 | writer_ptr [in] | A pointer to a #NX_AZURE_IOT_JSON_WRITER. |
115 <p>This API should be used in response to an incoming writable property. More details can be found
[all …]
/NetX-Duo-v6.2.1/crypto_libraries/src/
Dnx_crypto_initialize.c80 char *from, *to; in _nx_crypto_self_test_memcpy() local
84 to = (char*)dest; in _nx_crypto_self_test_memcpy()
88 to[i] = from[i]; in _nx_crypto_self_test_memcpy()
143 char *to; in _nx_crypto_self_test_memset() local
147 to = (char*)dest; in _nx_crypto_self_test_memset()
151 to[i] = v; in _nx_crypto_self_test_memset()
271 char *from, *to; in _nx_crypto_self_test_memmove() local
275 to = (char*)dest; in _nx_crypto_self_test_memmove()
281 to[i] = from[i]; in _nx_crypto_self_test_memmove()
288 to[i - 1] = from[i - 1]; in _nx_crypto_self_test_memmove()
/NetX-Duo-v6.2.1/docs/
Drevision_history.txt3 For version 6 and higher, please refer to the release notes on GitHub at https://github.com/eclipse…
11 Files are modified to fix window size overflow:
16 Files are modified to improve string length verification:
24 Files are modified to improve RARP logic:
29 File is created to improve string length verification:
32 Files are modified to fix compiler warnings:
36 Files are modified to fix system state check:
48 Files are modified to improve packet length verification:
63 Files are modified to support for 64-bit mode:
133 …nx_ip_delete.c Allowed driver uninit to execute without preempt…
[all …]
/NetX-Duo-v6.2.1/addons/azure_iot/samples/
DREADME.md3 …to connect to Azure IoT and start interacting with Azure IoT services like IoTHub and Device Provi…
6 …to use Device Provisioning service, use [doc](https://docs.microsoft.com/en-us/azure/iot-dps/quick…
10 …to the device in the IoTHub using Symmetric key. To register new device in IoTHub use the [doc](ht…
17 …atures like: Telemetry, Cloud to device message and Direct Methods. To disable anyone, add followi…
33 …to the device in the IoTHub using X509 cert. To generate self signed cert use the same steps menti…
42 ### Steps to create self-signed certs using openssl:
66 # Convert format from key to der.
69 # Convert format from cert pem to der.
78 # Convert format from key to der.
81 # Convert format from cert pem to der.
[all …]
/NetX-Duo-v6.2.1/
DLICENSE.txt5 Permission is hereby granted, free of charge, to any person obtaining a copy
6 of this software and associated documentation files (the "Software"), to deal
8 to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 copies of the Software, and to permit persons to whom the Software is
10 furnished to do so, subject to the following conditions:
DREADME.md11 NetX Duo as part of Eclipse ThreadX has been integrated to the semiconductor's SDKs and development…
37 …lease of the library. Each official release (preview or GA) will be tagged to mark the commit and …
92 We provide sample codes about how to use various addons in the [`samples`](./samples/) folder.
96 …endencies between them, as shown in the following graph. This is important to understand when sett…
100 > You will have to take the dependency graph above into account when building anything other than T…
104 …oolchain and IDE from semiconductor, you might follow its own instructions to use Eclipse ThreadX …
120 …x_user.h` and build together with the component source code. You can refer to [`nx_user_sample.h`]…
126 …to include NetX Duo into your device code source tree to be built & linked with your code, you can…
138 …pse ThreadX are defined in the LICENSE.txt file of this repo. Please refer to this file for all de…
142 The following are references to additional Eclipse ThreadX resources:
[all …]
DCONTRIBUTING.md1 # Contributing to Eclipse ThreadX
17 * TraceX - analysis tool that provides a graphical view of real-time system events to better unders…
23 This repository is subject to the Terms of Use of the Eclipse Foundation
57 In order to be able to contribute to Eclipse Foundation projects you must electronically sign the E…
DCMakeLists.txt8 option(NXD_ENABLE_FILE_SERVERS "Includes a dependency on FileX to support 'server' protocol handler…
35 # A place for generated/copied include files (no need to change)
61 # If the user provided an override, copy it to the custom directory
D.gitattributes4 # Custom attribute to mark sources as using our C code style.
7 # Custom attribute to mark sources as generated.
/NetX-Duo-v6.2.1/.github/ISSUE_TEMPLATE/
Dbug_report.md3 about: Create a report to help us improve Azure RTOS.
13 Please also mention any information which could help others to understand
18 - What have you tried to diagnose or workaround this issue?
21 Steps to reproduce the behavior:
26 A clear and concise description of what you expected to happen.
Dfeature_request.md3 about: Suggest an idea or enhancement to existing feature for Azure RTOS.
10 **Is your feature request related to a problem? Please describe.**
14 A clear and concise description of what you want to happen.
Dhardware-or-architecture-support.md10 **Is this request related to a particular hardware platform, SoC, board? Please describe.**
16 If this is a new board or SoC, please state whether you are willing to maintain the Azure RTOS supp…
/NetX-Duo-v6.2.1/addons/azure_iot/
DREADME.md5 * Expose smart client interfaces (IoTHub_Client, DeviceProvisioning_Client) for the customers, to b…
15 See the following samples on how to get started on development boards with Azure IoT Middleware for…
35 ….com/eclipse-threadx/netxduo/blob/master/common/inc/nx_user_sample.h) to see how to define these m…
45 * Connect to Azure IoT Hub via MQTT.
46 * Support of IoT Hub primitive data format: [device to cloud (D2C) message](https://learn.microsoft…
53 …to deploy over-the-air updates (OTA) for your IoT devices. The [Device Update for IoT Hub agent](h…
55 … development boards with detailed guides to learn configure, build and deploy the over-the-air (OT…
/NetX-Duo-v6.2.1/utility/
DCMakeLists.txt2 # to disable some / all of these, comment out the block(s) in question
/NetX-Duo-v6.2.1/tsn/
DCMakeLists.txt2 # to disable some / all of these, comment out the block(s) in question
/NetX-Duo-v6.2.1/cmake/
Dutilities.cmake13 # Copy the temp back up to the parent list
Darm-none-eabi.cmake15 # this makes the test compiles use static library option so that we don't need to pre-set linker fl…
/NetX-Duo-v6.2.1/test/cmake/azure_iot/configs/
Dwin32.cmake14 # this makes the test compiles use static library option so that we don't need to pre-set linker fl…
Dlinux.cmake30 # this makes the test compiles use static library option so that we don't need to pre-set linker fl…
/NetX-Duo-v6.2.1/test/cmake/crypto/
DCMakeLists.txt57 "Includes a dependency on FileX to support 'server' protocol handlers"

12