Forums - GT202 qcom_API on FRDM K22F

1 post / 0 new
GT202 qcom_API on FRDM K22F
a.sur
Join Date: 25 Dec 15
Posts: 1
Posted: Wed, 2016-06-08 01:15

We have built existing mqx(4.1) qcom_api on freescale FRDM-K22F120M board with ARM GCC toolchain 4.9.3.

We wanted to build IoT demo application that collects data from built-in sensors present on FRDM-K22F120M board and have some edge level pre-processing before reporting to cloud. While doing so we couldn't find HTTP client API's to manipulate HTTP headers like x-api-key, Content-type, Headers for method, URLs etc to connect to HTTP server. 

We tried to create TCP client socket conection by referring  throughput_qapi.c and added HTTP headers to make a valid HTTP client request. We used following sequence in a function which is called inside one MQX task in every 1 sec (TCP payload size 662 bytes, buffer alloc size 768 ).

func {

TX:: qcom_socket(); -> qcom_connect(); -> CUSTOM_ALLOC(); -> qcom_send(); -> CUSTOM_FREE();

RX::  A_MALLOC(); -> t_select(); -> qcom_recv();  -> zero_copy_free();

qcom_socket_close();

}

But after running for few secods successfully, it hangs either at qcom_socket() call or qcom_send() call. It takes lot of time and enters into driver ASSERT call. We tried with t_socket() , t_connect(),  t_send() API's . Results are same.

We need one sample high throughput TCP client source or HTTP client with Header options enabled.

Please help.

Regards,

Avijit

 

  • Up0
  • Down0

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.