Home
last modified time | relevance | path

Searched refs:received (Results 1 – 7 of 7) sorted by relevance

/NetX-Duo-v6.2.1/test/regression/azure_iot/
Ddevice_twin_unit_test.c832 UINT received = 0; in test_nx_azure_iot_hub_client_device_twin_propetries_request_no_blocking_success() local
839 (VOID *)&received), in test_nx_azure_iot_hub_client_device_twin_propetries_request_no_blocking_success()
853 while (!received) in test_nx_azure_iot_hub_client_device_twin_propetries_request_no_blocking_success()
951 UINT received = 0; in test_nx_azure_iot_hub_client_device_twin_desired_properties_receive_no_blocking_success() local
958 (VOID *)&received), in test_nx_azure_iot_hub_client_device_twin_desired_properties_receive_no_blocking_success()
967 while (!received) in test_nx_azure_iot_hub_client_device_twin_desired_properties_receive_no_blocking_success()
Ddirect_method_unit_test.c534 UINT received = 0; in test_nx_azure_iot_hub_client_direct_method_message_receive_no_blocking_success() local
541 (VOID *)&received), in test_nx_azure_iot_hub_client_direct_method_message_receive_no_blocking_success()
548 while (!received) in test_nx_azure_iot_hub_client_direct_method_message_receive_no_blocking_success()
Dnx_azure_iot_pnp_client_command_unit_test.c661 UINT received = 0; in test_nx_azure_iot_hub_client_command_message_receive_no_blocking_success() local
668 (VOID *)&received), in test_nx_azure_iot_hub_client_command_message_receive_no_blocking_success()
672 while (!received) in test_nx_azure_iot_hub_client_command_message_receive_no_blocking_success()
/NetX-Duo-v6.2.1/test/regression/nx_secure_test/
Dnx_secure_tls_non_blocking_test.c267 …atic VOID on_packet_received(NX_SECURE_TLS_SESSION *tls_session, UCHAR *connected, UCHAR *received) in on_packet_received() argument
323 *received = NX_TRUE; in on_packet_received()
/NetX-Duo-v6.2.1/addons/azure_iot/docs/
Dazure_rtos_iot_hub_client.md510 … callback function. This callback function is invoked when a message is received from Azure IoT hu…
518 …lback_ptr [in] | Pointer to a callback function invoked on specified message type is received. |
790 …ack function. This callback function is invoked when a telemetry ack is received from Azure IoT hu…
911 * NX_AZURE_IOT_SUCCESS Successful if C2D message is received.
1070 * NX_AZURE_IOT_SUCCESS Successful if direct method message is received.
1238 * NX_AZURE_IOT_SUCCESS Successful if IoT Hub command message is received.
1391 …ported properties. This callback function is invoked when a response is received from Azure IoT hu…
1529 * NX_AZURE_IOT_SUCCESS Successful if device twin properties is received.
1571 * NX_AZURE_IOT_SUCCESS Successful if desired properties is received.
1815 * NX_AZURE_IOT_SUCCESS Successful if all properties is received.
[all …]
Dazure_rtos_iot_adu_agent.md36 | adu_agent_update_notify [in] | Pointer to a callback function invoked once update is received. |
/NetX-Duo-v6.2.1/docs/
Drevision_history.txt1591 … Optimized the logic when a packet with old data is received.
2686 … Fixed a bug where NA packet is received how queued packets requiring fragmentation are sent
2739 … Update the socket outgoing interface to the received packet interface
3826 no hint is received.
3857 invoke when a certificate is received.
3885 invoke when a certificate is received.
4589 … Fixed a bug that packet may be queued by TLS and can not be received.
5276 … Fixed a bug when multiple packets were received and the first one was invalid,
5308 … is not received within user specified timeout period.
5347 … Modified FIONREAD option to capture the correct number of bytes received on the UDP socket
[all …]