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: Bluetooth dual-mode versus Bluetooth Classic + iAP

Part Number: CC2564

Hi,

I have a project that requires concurrent audio streaming and control sequences (from iOS to device). I can see two approaches:

1. Bluetooth dual-mode running concurrent Classic and LE stacks (CC2564 + MSP432) - audio over AD2P, control over LE

2. Bluetooth classic only - audio over AD2P, control over iAP

I am not requesting any technical details on Apple's MFi/iAP technologies so my question is best phrased thus:

 - Is there any compelling reason not to use option 1 above? Are there any "gotchas" such as increased latency, overall performance that would make this approach less desirable than 2?

Regards,

ac

  • Andrew,

    There is indeed a catch with your first option. Currently, the stack with MSP432 only supports assisted A2DP (A3DP), and as it is an assisted mode, it does not allow the coprocessor to simultaneously run BLE.

  • Hi,

    Many thanks for the response. A couple more questions if you don't mind:

    - you say that the stack with MSP432 only supports A3DP. Is A2DP supported with any other processor? (E.g. MSP430, STM32...)

    - are there any plans to support A2DP with MSP432 in future revisions of the stack? (Note that your main competitor in the audio space has supported A2DP + BLE peripheral role for a couple of years now)

    Kind regards,

    Ac

  • Andrew,

    Unassisted A2DP is supported with the STM32 processor. Please see the attached literature for use of A2DP with STM32.  

    My understanding is that the limitation preventing support of A2DP with MSP432 is memory size in the MSP device, but for future versions of MSP432 it is possible that we will be integrating A2DP + BLE capability into the stack.