• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 1188 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC256XC-BT-SP: mSBC audio data problem for SCO over HCI

Marvin Tsai
Prodigy 30 points
Part Number: CC256XC-BT-SP
Other Parts Discussed in Thread: CC2564C

Hi,

I'm using CC2564C for HFP development.

I need to use SCO over HCI feature and I've turned it on. (Using the HCI VS command: 0x10, 0xfe, 0x05, 0x01, 0x78, 0xd0, 0x02, 0x01)

I've applied CC2564C patch of V1.2.

I can get SCO data from HCI but there is something wrong of the mSBC data.

CC2564C sends the SCO data show as below, but the mSBC header location SHIFT in mSBC frame. It means that the SCO data is incorrect.

I can measure this behavior by probe from UART interface.

So, how can I get correct SCO data from CC2564C? 

SCO data ------>

01 01 3C 01 38 AD 00 00 C5 00 00 00 00 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB 6D B7 76 DB 6C 00
01 01 3C 01 08 AD 00 00 C5 00 00 00 00 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB 6D B7 76 DB 6C 00
01 01 3C 6C 00 01 38 AD 00 00 C5 00 00 00 00 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB 6D B7 76 DB
01 01 3C 6C 00 01 08 AD 00 00 C5 00 00 00 00 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB 6D B7 76 DB
01 01 3C 6C 00 6C 00 01 38 AD 00 00 C5 00 00 00 00 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB 6D B7
01 01 3C 76 DB 6C 00 01 08 AD 00 00 C5 00 00 00 00 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB 6D B7
01 01 3C 76 DB 6C 00 6C 00 01 38 AD 00 00 C5 00 00 00 00 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB
01 01 3C 6D B7 76 DB 6C 00 01 08 AD 00 00 C5 00 00 00 00 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB 6D B7 76 DB 6D DD B6 DB 77 6D B6 DD DB

Thanks a lot.

  • 0
    TI__Mastermind 29250 points

    Hi Marvin,

    Like we discussed in the thread below, eSCO over HCI is not stable in CC256x or WL18xx.

    https://e2e.ti.com/support/wireless-connectivity/wifi/f/968/t/840438

    Please see whether using AVPR (PCM interface for WBS) is an option for your implementation. That is what all of TI stack SDK demos use as well.

    Best regards,

    Vihang

  • 0 in reply to Vihang Parmar
    Prodigy 30 points

    Hi Vihang,

    Thanks for your reply.

    I think that I can't use PCM interface because I have to send the received SCO data to another Bluetooth device.

    I have two more questions.

    Question 1: Is this problem also happened on CVSD NBS over HCI case? (I want to check if CVSD is fine)

    Question 2: Is there any way to make eSCO over HCI more stable? (Ex. disable BLE? or something else...)

    Best regards,

    Marvin.

  • 0 in reply to Marvin Tsai
    TI__Mastermind 29250 points

    Hi Marvin,

    Marvin Tsai said:
    I think that I can't use PCM interface because I have to send the received SCO data to another Bluetooth device.

    Is the other Bluetooth device a TI dual-mode BT controller as well?

    Marvin Tsai said:
    Question 1: Is this problem also happened on CVSD NBS over HCI case? (I want to check if CVSD is fine)

    CVSD has the same limitation due to the asynchronous nature of UART.

    Marvin Tsai said:
    Question 2: Is there any way to make eSCO over HCI more stable? (Ex. disable BLE? or something else...)

    There is no way around the HCI limitation. The best solution is to go with PCM interface.

    Best regards,

    Vihang

  • 0 in reply to Vihang Parmar
    Prodigy 30 points

    Hi Vihang,

    Yes, another Bluetooth device is TI solution too.

    Thanks for your reply for my question.

    Best regards,

    Marvin.

  • 0 in reply to Marvin Tsai
    TI__Mastermind 29250 points

    Marvin,

    You can connect the two TI dual-mode BT controllers using the PCM interface and avoid the whole eSCO over UART scenario. Moreover, it will simplify your application as it does not have to tunnel the data back and forth between two controllers.