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.

BOOSTXL-CC3135: CC3135 porting - sl_IfStartWriteSequence and sl_IfEndWriteSequence APIs

Part Number: BOOSTXL-CC3135
Other Parts Discussed in Thread: CC3135

In porting explanation,TI programming guide for CC31xx / 32xx chip, mentions about

1. int sl_IfStartWriteSequence (_SlFd Fd) and

2. int sl_IfEndWriteSequence (_SlFd Fd) API in chapter 19.5

What is the necessity of these APIs in i.MXRT 1052 LPUART / LPSPI implementation in porting?

Can I left these APIs undefined?

  • Hi,

    If you do not need to use those APIs on your platform, then you can leave them undefined. The host driver running on the CC3235 actually has those functions undefined.

    Keep in mind, the documentation in simplelink.h mentions this for those functions:

     By default the driver is writing the command in few transactions to allow zero-copy mechanism. \n
     To enable a Jitter buffer for improving the communication line utilization, the can implement
     also the following defines:
        - sl_IfStartWriteSequence
        - sl_IfEndWriteSequence

    Let me know if you need more clarification on those functions, or have further porting questions on the CC3135.

    Regards,

    Michael

  • Thank you for your quick reply.

    But, i am still not clear about purpose of using these APIs.

    i have following queries:

    1. How zero copy method is achieved through these APIs?

    2. Which higher layer APIs call these two APIs?

    3. Is there any document explaining about these APIs in more detail?