This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Tx descriptor linking procedure

Hi 

I am working on programming BCP for LTE downlink modules on TCI6634K2L device.

In this regard, I wanted to send linked Tx descriptors to BCP.

Suppose A,B,C are Tx descriptors. I would like to link them as A->B->C->NULL

My questions are:

  • After linking the descriptors, is it required to push all the descriptors (A,B & C) on to BCP Tx Q or pushing descriptor A alone is sufficient? 
  • Any pointers to example code for Tx descriptor linking either for BCP or FFTC?
  • There are 2 return policies to choose from. What is the difference between them? What are the use cases of different policies?

I glanced through the documentation and e2e posting. But, I was not lucky enough to find answers to above questions.

Can some one help me ?

Thanks

Rao

  • Hi Rao,

    I've forwarded this to the experts. Their feedback should be posted here.

    BR
    Tsvetolin Shulev
  • Hi ,

    I am also struggling with the same issue.
    I would really appreciate if some one from the community will help me out.

    Thanks and Regards
    Rohan
  • Hi Rohan,

    Please refer to the example project provided in the following thread. This example uses linked descriptors. Refer to the function test_lte_ul in file test_lte_ul.c.

    To answer the questions asked in this thread:

    1. After linking the descriptors, is it required to push all the descriptors (A,B & C) on to BCP Tx Q or pushing descriptor A alone is sufficient?

    -> You push only the Head descriptor to the Tx Q (i.e. descriptor A in your question).

    2. Any pointers to example code for Tx descriptor linking either for BCP or FFTC?

    -> Example project (BCP) provided in the above mentioned thread.

    3. There are 2 return policies to choose from. What is the difference between them? What are the use cases of different policies?

    -> The Return Policy (for the packet) and Return Push Policy (for the descriptor pointers) fields are described in table 3-4 of the Navigator User guide ()  

    Regards

    -Nitin

  • Rohan,

    If you don't have any more questions on this subject, can you please mark the response as a verified answer? Thanks.

    Regards
    -Nitin