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.

Bluetooth application development with Link layer modification

Other Parts Discussed in Thread: CC2541, CC2540, CC2564

Hello,

I'm new to Bluetooth and seeking advice on the flexibility of the Bluetooth protocol stack for custom modifications.

I'm specially interested in piconet/scatternet formations. I want to know where the developer can get any flexibility in modifying. For example, is it possible to chose a Master depending on the battery life if there are multiple master candidates? Periodically change Masters, and so on.

If I understand correctly this is controlled by the Link layer of the protocol stack. Is it possible to change the behavior programatically?

If someone can provide me with any reference that would be much appreciated.

Thank you.

  • Hello Maduranga,

    Welcome to the Forum!

    The best place to start with Bluetooth would be the www.bluetooth.org.  There are two parts to the Core Bluetooth v4.0 Specs.  This forum is specific to the Low Energy or BLE.  Should you wish to continue with BLE on the CC2540\CC2541, I suggest you read the following post: http://e2e.ti.com/support/low_power_rf/f/538/p/259987/909317.aspx#909317

    BLE only supports piconets as briefly described here:  http://e2e.ti.com/support/low_power_rf/f/538/p/260425/910723.aspx.  

    Role change from master to slave is possible through code.  You can visit the BLE-wiki to see how to dynamically switch between master and slave.

    For a scatternet, you would want the standard Bluetooth and there is a Bluetooth Applications forum for that.  You can further reference the following post: http://e2e.ti.com/support/low_power_rf/f/538/t/136805.aspx

    There is however a device, the CC2564 that combines both (dual mode) BLE and EDR so there may be some back and forth between forums if you choose this device.  It is not an SoC, a MCU of your choice can be used to interface with it.  The search option in both forums should provide you with a quick answer to many of the questions you may have regarding both devices..

    Thanks,

  • Dear greenja,

    Thank you very much for the comprehensive answer. I'm still starting up with BT and absorbing things slowly.

    It's good to know that Master/Slave roles in piconets can be controlled in the code. And I must have scatternets.

    Thank you very much for the references. I am not looking at BLE specifically. My main requirements are EDR and scatternets. 

    Wikipedia says BT Ver. 3 supports very high data rates but I can't seem to find any commercially available products. Most seem to be 2.1+EDR.

    Thank you.

  • The reason for the lack of devices for BT v3 was that there where too many requirements that made it unattractive to developers.  Most developers and manufactures skipped v3 and went to v4.0.  It has all the features of the previous versions plus it adds BLE.  There are a few manufactures of these devices and many more will be coming in the new year running on ARM Cortex M cores.

    Good luck,