• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 531 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.

TI AM/DM37x EVM- Bluetooth audio-Liba2dp.c

ashish meena
Prodigy 80 points


Hello All,

 I have made some changes in ~../BlueZ/audio/liba2dp.c to integrate our BT audio codec. However, when i flash  the TI AM/DM37x EVM with new rootfs and enabled the BT. I do not see any of my DBG messages from liba2dp.c . Is TI usages some other BT s/w stack? 

Thanks in adv.

AM


  • 0
    TI__Genius 10210 points

    TI Android DevKit uses bluez provided in the android sources at the location: external/bluetooth/bluez

    What are you attempting to do?

  • 0 in reply to Vishveshwar Bhat
    Prodigy 80 points

    Hello Vishveshwar,

    Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4

    Yes, I have made changes to integrate a Non-a2dp audio codec in the file external/bluetooth/bluez/audo/liba2dp.c , unix.c, ipc.h etc.,

    So far it is like mystery, seeing other log messages; it appears TI is not using the standard BlueZ stack which comes with Android source. I have integrated our non-a2dp audio codec in other platforms using CSR chip.  

    I am looking and trying to search log messages such as “a2dp_stop or Bluetooth_stop” coming out while logcat &  w.r.t their source files. I have already changed the similar log message in external/bluetooth/bluez/audo/liba2dp.c.  But still I can see these log messages. So don’t know from where they are coming.  Even find and grep could not find it.

    :-(

    Thanks

    AM

  • 0 in reply to ashish meena
    TI__Genius 10210 points

    IIRC the log messages from bluez are sent to /dev/null due to the way it is invoked from init.rc.

    I am not able to understand why you are debugging liba2dp.c to support your 'non a2dp audio codec'.

     

    What do you mean by 'other platforms using CSR chip' ?

    It would really help if you could explain your problem statement.

  • 0 in reply to ashish meena
    Prodigy 80 points

    Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4

    Hello ,

     If someone can tell me, where SBC encoder is integrated in TI_Android_Froyo_DevKit-V2.2 source tree , this will be enough for me.  

    I know it has been called in liba2dp.c  and in file pcm_bluetooth.c (at ~\TI_Android_Froyo_DevKit-V2.2\Android_Source\external\bluetooth\bluez\audio\).

    I have enabled some LOGD messages there to see if these files are ever used or functions from them (bluetooth_a2dp_setup(),bluetooth_a2dp_init()) are ever called.

    Thanks

    AM

  • 0 in reply to ashish meena
    TI__Genius 10210 points

    We have verified A2DP operation with TI Android Froyo devkit v2.2 on AM37x evm with Nokia BH505 headset. No changes done in android bluez stack or anywhere else to add the A2DP feature.