• Resolved

CC3135: CC3135 and CC2652 Launchpad network_terminal example

Prodigy 220 points

Replies: 8

Views: 156

Part Number: CC3135

Dear Support,

I have your CC2652 Launchpad and CC3135 Booster Pack handy and have already downloaded the SDK for CC3135 booster pack.  Moreover, I have already assembled CC2652 Launchpad and CC3135 Booster pack board together and try to run the network_terminal example.  I am able to load the network_terminal example into the CC2652 launchpad and run it successfully.  I also noticed there are other commands like "CoexEnable", "CoexDisable", "AntSelectionEnable",  and "AntSelectionDisable".  Is there a way we could evaluate these commands like accessing the board through your Bluetooth APP? 

Vincent 

  • Hi Vincent,

    I have assigned an expert to comment.

    Best regards,

    __________

    Clément

  • In reply to Clément:

    Hi! Clément

    Any update?

    Vincent

  • In reply to Vincent Chou:

    Hi Vincent,

    Unfortunately, what you are asking for, is not supported.

    Let me put it this way: When you combine the the launchpad and booster pack, you make the CC2652  a "single wi-fi device". Even though it supports BLE, the device does not support being BLE enabled and wi-fi enabled at the same time. The coexistence feature you are referring to is not an internal "dual role" feature, but intended for two separate devices to coexist (not the single device, even though you have a booster pack).

    In the case of two separate devices, there are currently no options to verify this feature through any of our tools either.

    Best regards,

    Vetle 

  • In reply to Vetle G:

    Hi! Vetle,

    I understood what you referred in the email.  In that case, there is no clear configuration and steps for us to set up an environment to test BT and WIFI coexistence scenario.  Although the feature has been explained in the CC3135 datasheet, there is no clear example to set up a BT and WIFI coexistence scenario.  Do you have any configuration you can suggest to test BT and WIFI coexistence with other BT devices? 

    Vincent

  • In reply to Vincent Chou:

    Hi Vincent,

    Currently this is more of an option than a feature with its own example, and so I can't point you to a specific example. However, I can give you some guidance on how to enable the BLE device:

    If you have a look at the board files for either of the CC1352Px devices, located in the following path for the latest SDK:

    <SDK-install-dir>\simplelink_cc13x2_26x2_sdk_3_30_00_03\source\ti\ble5stack\boards

    You will find what you need in the *LAUNCHXL.c file, where the RF driver is configured to subscribe a callback function "rfDriverCallback" on the radio power up/down events, and the *LAUNCHXL_fxns.c  file where this function is defined. From the function definition, you can get an example of how the GPIO pins are toggled according to the radio waking up. By adding similar configuration  to the board files of the BLE example projects, you should be good to go with a BLE device.

    There should not be any restriction on what device CC13x2/CC26x2 you choose to use as your other BLE device.

    Best regards,

    Vetle

  • In reply to Vetle G:

    Hi! Vetle,

    Thanks for your suggestions!  Let me try to implement that.  

    Vincnet

  • In reply to Vetle G:

    Hi! Vetle,

    I could not find an example project which really uses ../source/ti/ble5stack/boards/CC1352P1_LAUNCHXL/CC1352P1_LAUNCHXL_fxns.c.  Could you kindly point me to the right example to look at?  Thanks!

    Vincent

  • In reply to Vincent Chou:

    Hi Vincent,

    All the examples in /examples/rtos/CC1352P1_LAUNCHXL/ble5stack include the CC1352P1_LAUNCHXL_fxns.c file in the project specification, so by opening any of these in CCS you will see the file in the project. If you have your own extension of any of the examples, and you miss any files, you can always just import the file to your project and add the same directory to you include path.

    The important part for your case is that you, as mentioned above, point the RF driver callback function to a function definition of your choosing.

    Best regards,

    Vetle