• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 52 subscribers
  • Views 160 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.

CC2564MODNEM: For BLE audio use case using MSPM0G3507

AnBer
Mastermind 29160 points
Part Number: CC2564MODNEM
Other Parts Discussed in Thread: MSPM0G3507, , CC2564, CC2564MODN, CC2564C

Team,

A description of the issue will be posted soon.

Anber.

  • 0
    Prodigy 60 points

    Hi Together,

    I m the developer and i m having the board MSPM0G3507 and CC2564MODNEM. To connect these two, BOOST CCEMADAPTER is used. From TI side, they have developed sdk kit for CC2564 is with MSP-EXP430F5529, MSP-EXP430F5438, DK-TM4C129X. Unfortunately, these boards are obsolete from TI side and they have no longer manufacturing it. We are developing for Bluetooth audio application and to prepare the prototype, we chose this MSPM0G3507 board because, it has both ADC and DAC for connecting microphone and speaker. 

    we don't have SDK to connect mspm0g3507 to cc2564modnem and we have tried to port the stack code for initiating the UART com with CTS,RTS feature to send HCI command. But could not understand what are the things to consider to change in the library code ( e.g HRDWCFG, HAL.c, GPIO.h etc) 

    NEED SUPPORT here to make communication with this (CC2564 and MSPM0G3507) to proceed further.

    Please let me know if need any information in detail. We can share details appropriately

    Thanks a lot in advance

  • 0 in reply to Beyond Seven
    TI__Genius 10620 points

    Hi,

    I want to start off by saying if this is for a new design that you want to have bluetooth sig certification, then you will not be able to use the cc2564modn as it has been deprecated by the bt sig. The cc2564C is still eligible for qualification up to 5.1 however, ti does not offer a module for it. There are 3rd party vendors that sell modules with the cc2564C (for example BDE).

    In regards to the porting. As I told you this endeavor is not an easy one. First step is to get the code to compile with the M0 driver libraries. This means using the M0 UART api calls, as well as the gpio calls etc.

    I would begin figuring out how to use the m0 first by going over the simple link academies

    https://dev.ti.com/tirex/explore/node?a=IOGqZri__3.80.13.03&node=A__AVkPxX6hRXRpPST-l6LGfQ__MSPM0-ACADEMY__2f1Egw1__LATEST

    this is the uart one.

    From there start figuring out how to use these apis in the bluetopia adaptation layers.

    Best,

    Rogelio

  • 0 in reply to RogelioD
    TI__Mastermind 29160 points

    Hi Beyond Seven,
    Can you please confirm what bluetooth audio profile you need to support?
    This will help Rogelio to confirm what Bluetooth SW stack and TI SOC can (or will) support it.

    Hi Rogelio,
    What TI SOC do you advise then for Bluetooth audio (that is planned to still be supported and certified for future Bluetooth version)?

    Thanks in advance,

    A.

  • 0 in reply to AnBer
    TI__Genius 10620 points

    Hello,

    For Audio you will need to use Bluetooth Classic and unfortunately the only device that TI has that supports BREDR and is certified is the CC2564C. There are multiple third party modules that use the CC2564C. 

    The Catch here however, is TI only supports the bluetopia stack on the MSP432 and STM32 MCU hosts.

    Bluetopia supports all the audio profiles im aware of. A2DP/A3DP, HFP, HSP, etc...

    However, since the cc2564c is a transceiver you can technically use any Bluetooth stack (TI will not offer support) you want as the controller itself is certified. 

    Best,

    Rogelio