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.

  • Resolved

CCS/CC256XQFNEM: Only SPPDemo project Opens the Bluetooth Stack without error, but it can not pair

Prodigy 20 points

Replies: 3

Views: 103

Part Number: CC256XQFNEM

Tool/software: Code Composer Studio

I have purchased   eval kit MSP-EXP430F5438 Experimenter Board and two different version of dual Bluetooth extension modules, one of the is CC256xQFNEM and the other is CC2564MODAEM.

I have install CCs-8.3 version and MSP430 Compiler v 4.15.

The above builds without errors all project examples for TI dual-mode Bluetooth® stack on MSP430 MCUs CC256XMSPBTLESW Version v.15 R2 ( updated with patch for the CC256x devices v.1.7.

and added to BTVS.c the follwing lines - they make no difference) 

#define __SUPPORT_CC256XB_PATCH__
//#define __CC256XBH__

My problem is that only SPPDemo can open the TI Bluetooth stack without any errors. However it can not pair to anything and it is invisible to any Bluetooth enabled devices from Android nor windows and Apple.

Can anybody please shed some light on how to get those TI example working on the above eval boards?

Do I need a different eval board, do I need to fix old library - TI please speak up what am I doing wrong ..what is the right way to use your products?

The Wiki pages for the stack library examples are not helping to resolve it at all.

OpenStack().
Bluetooth Stack ID: 1
Device Chipset: 4.0
BD_ADDR: 0xD4F5135E1BC4

the other examples gives the following errors:

HIDemo:

OpenStack().
Stack Initialization Failed: -4.
Unable to open the stack.

HTPDemo:

OpenStack().
Error - BSC_Initialize returned -4.
Unable to open the stack.

Thank you,

  • Jerzy,

    Please follow the Hardware and Software setup instructions described in the User's Guide.

    Jerzy Smiecinski

    and added to BTVS.c the follwing lines - they make no difference) 

    #define __SUPPORT_CC256XB_PATCH__
    //#define __CC256XBH__

    Defining this macro in BTVS.c will not change anything and download the wrong service-pack to the controller. This is why you are not able to find / connect the demo from any remote device.

    The proper way is to define the __SUPPORT_CC256XB_PATCH__ macro in the BTPSVEND.c as mentioned in the User's Guide.

  • In reply to Vihang Parmar:

    Thanks for your input on the above.

    placing that define in the specified place does not enable clean example builds, I had to add the following to the BTPSVEND.c:

    static unsigned long BasePatchPointer = (unsigned long)BasePatch;
    static unsigned long LowEnergyPatchPointer = (unsigned long)LowEnergyPatch;

    After those two were defined I had to add new library from the compiler directory before applications' examples would be - at least some of them.

    libmath.a found under: CCS MSP430 compilier directory:

    ti\ccsv8\ccs_base\msp430\lib\5xx_6xx_FRxx\libmath.a

    Can you tell me why the information provided in the actual patch v1.7 does not explain what really will have to be done in order to make it work, and instead you are sending me to the user guide website.

    with a generic guide?

    Thank you for pointing me to the right direction. 

     

  • In reply to Jerzy Smiecinski:

    Jerzy,

    Jerzy Smiecinski

    Can you tell me why the information provided in the actual patch v1.7 does not explain what really will have to be done in order to make it work, 

    The cc256xb_bt_sp_v1.7 is the service-pack for the CC256xB controller not the whole Bluetooth stack. Moreover, the CC256XB.h provided in the cc256xb_bt_sp_v1.7 package is compatible and tested with the CC256XMS432BTBLESW and CC256XSTBTBLESW stack SDK releases. It is not tested with the older SDK releases like the CC256XMSPBTBLESW that you are using. Please refer to the release notes of the cc256xb_bt_sp_v1.7 service-pack for details. The CC256XMSPBTBLESW SDK release is several years old and no longer maintained.

    Jerzy Smiecinski

    and instead you are sending me to the user guide website.

    with a generic guide?

    The user's guide mentioned above is not a generic guide, it is specific to the platform you are using. I noticed that the documentation was created using the CCS5 when it was released. So my best guess is using this SDK with CCS8 will require all the changes you mentioned in order to build the sample applications. Using these sample applications with CCS5 should work out-of-box.

    I hope this helps.

    Best regards,

    Vihang

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.