• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 52 subscribers
  • Views 556 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CC2564 transmit response time

Sh.Sasaki
Guru 13625 points

Other Parts Discussed in Thread: CC2564, CC2564MODAEM

Hi everyone,

I have two question about CC2564.

Q1:
Now, CC2564 transmit response time is 4msec from "SPP_Data_Write"(StringLentgth is 10) to "HCI_Event_Callback etNumber_Of_Completed_Packets_Event".
Is it possible to shorten this time? Or is this the device limit?

Q2:
SPPDEMO projects is there are two types of NonOS and TI-RTOS.
Is there a difference in product performance by these projects?
For example, TI-ROTS project is SW handling is slow because the SW latency is larger, etc...

My customer environment:
HW : Client [DK-TM4C129X, CC2564MODAEM] , Server [DK-TM4C129X, CC2564MODAEM]
SW : CCSv6.2, Stack v1.2 R2(use NoOS SPPDemo), ServicePack v1.5
Profile : BT SPP

Best regards,

Mino.M

  • 0
    TI__Mastermind 35795 points
    hi, your query has been assigned to BT expert. We will get back to you shortly
    Saurabh
  • 0
    TI__Mastermind 29361 points
    Hi Mino,

    Is Q1 related to this post? e2e.ti.com/.../1990015
    If yes, is this question still open?

    Regarding Q2, The ti bluetooth stack has its own task scheduler in either case NoOS or RTOS (non-threaded and threaded versions of the stack respectively). So regardless of whether the application running on top of the stack is threaded or non-threaded, the behavior in terms of timing should be very similar.

    BR,
    Vihang
  • 0 in reply to Vihang Parmar
    Guru 13625 points

    Hi Vihang,

    Thank you for your answer.

    Vihang said:


    Is Q1 related to this post? e2e.ti.com/.../1990015
    If yes, is this question still open?

    Previous post  wanted to transmit in faster than 20msec.

    It was closed because now my customers can transmit in 5msec.

    Q1 want to transmit in faster than 5msec.

    My customer  is thinking 5msec limit of stack.

    Therefor, He want to know whether the stack that can be achieved this is provided. 

    Vihang said:


    Regarding Q2, The ti bluetooth stack has its own task scheduler in either case NoOS or RTOS (non-threaded and threaded versions of the stack respectively). So regardless of whether the application running on top of the stack is threaded or non-threaded, the behavior in terms of timing should be very similar.

    I understood it. Thank you.

    Best ragards,

    Mino.M

  • 0 in reply to Sh.Sasaki
    TI__Mastermind 29361 points
    Mino,

    One way to reduce the time is to increase the HCI baud rate. There is a SetBaudRate command in the SPPDemo that shows how to implement this.

    Is the time delay for the transmission the main concern here or the ultimate goal is to improve throughput? If looking at improving throughput, there are other parameters we can use to obtain higher throughput in addition to improving the transmission time.

    Best Regrads,
    Vihang
  • 0 in reply to Vihang Parmar
    Guru 13625 points

    Hi Vihang,

    Thank you for your response.

    Is other parameters UART buffer size?

    Now, I requested my customer modify HCI baud rate and UART buffer size.

    I report you if some progress.

    Thanks and regards,

    Mino.M