• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 51 subscribers
  • Views 330 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.

CC2564MODA: Required performance fro Bluetooth Stack

user4848255
Prodigy 80 points
Part Number: CC2564MODA


Hello

We am currently looking into the Bluetooth Stack of the dual mode Bluetooth module. We got it running and found following situation (based on the information from our software engineer):

 

-          The BT Stack has to be started each ms

-          The Stack requires for the A2DP Profile only 10 – 20 µs per cycle

-          The function which provides the audio data will be started each second cycle and requires 700 µs. This is a function from the library and is working together with the HCI Interface

 

So we wanted to know if we can used the PCM Interface to speed up and reduce the performance required from the microcontroller. Could you please let us know if this is possible and where we may find examples?

I also wanted to know if we are fully compatible to the A2DP profile if we use the A3DP profile to reduce microcontroller performance requirements?

Thank you very much for your help

Best regards

Markus

  • 0
    TI__Mastermind 29311 points

    Hi Markus,

    The CC2564MODA module is based on CC2564B IC. So as far as the firmware and bluetooth stack is concerned, there is no difference between the two.

    The typical A2DP sink architecture has control (HCI commands) and data (ACL data packets) going over the HCI UART interface.

    user4848255 said:

    -          The BT Stack has to be started each ms

    -          The Stack requires for the A2DP Profile only 10 – 20 µs per cycle

    -          The function which provides the audio data will be started each second cycle and requires 700 µs. This is a function from the library and is working together with the HCI Interface

     

    The observations mentioned above are related to the Data portion where the micro-controller receives the ACL data and decodes it using SBC to finally send it to an audio CODEC. The timing mentioned above indicates this and it is dependent upon the negotiated A2DP parameters (like sample rate, bitpool etc) between the local device and the remote A2DP source device. You can refer to the section 6.4.4.2.1 Assisted A2DP Sink section of CC2564B datasheet for details.

    user4848255 said:

    So we wanted to know if we can used the PCM Interface to speed up and reduce the performance required from the microcontroller. Could you please let us know if this is possible and where we may find examples?

    You can use the Assisted A2DP (A3DP) mode to offload the ACL data processing taks from the host micro-controller. In the A3DP architecture, the ACL data will be decoded using SBC and sent out to the audio CODEC over the PCM lines.You can find the example A3DP Sink implementations in the TI Dual-mode Bluetooth Stack SDK for MCUs (ADPDemo_SNK)

    user4848255 said:

    I also wanted to know if we are fully compatible to the A2DP profile if we use the A3DP profile to reduce microcontroller performance requirements?

    Using the A3DP  will meet all the mandatory requirements specified in the A2DP profile specs. 

    Hope this helps.

    Best regards,

    Vihang