• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 265 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.

CC2640R2F: Different Bluetooth behaviour of Firmware on CC2640R2F LAUNCHXL and customer board in combination with some mobile devices

Martin Beisteiner
Prodigy 80 points
Part Number: CC2640R2F

Hello!

We are using the CC2640R2F on our own hardware and Bluetooth works fine with one exception:

A HUAWEI MediaPad M5 lite cannot find our BLE device. During Investigations of this behaviour I switched back to the simple peripheral example without modifications. When running the example on the LAUNCHXL the tablet can find our device, but when the example is running on our hardware it does not. Same behaviour when running our Firmware. When running on the LAUNCHXL board the tablet can find the device, but on our board it does not. When using other smart devices all works fine on our hardware.

Why does it make a difference whether the LAUNCHXL is used, or our Hardware, and why only in combination with some mobile devices?

I also read out the Silicon Revision with the Smart RF Studio and the MUC’s on both boards have the same Revison: Rev. F (2.5).

We are using SDK 2.20.00.49

Many thanks for your help in advance!

Martin

  • 0
    TI__Guru 57865 points
    Hi Martin,
    It sounds like your hardware may have some issues running the firmware. Are you able to download and run the software in debug mode?
  • 0 in reply to J Lindh
    Prodigy 80 points

    Hi Joakim,

    yes, i can download an run the Firmware in debug mode. 

    What i don't understand is, why does it work in general, but not with the special combination of hardware and  mobile device?

    Regards Martin

  • 0 in reply to Martin Beisteiner
    TI__Guru 57865 points
    Hi Martin,
    Are you able to sniff the communication to make sure that the device is advertising properly?
  • 0 in reply to J Lindh
    TI__Guru 57865 points
    Hi Martin,
    Could you please also try with the latest SDK?
  • 0
    Guru 86745 points
    Hi Martin,

    Make sure you set this define correctly at firmware for your custom board. If not will have problems with RF, either very short range or not connect.

    filename: CC2640R2_LAUNCHXL.h

    * Define only one symbol:
    * CC2650EM_7ID - Differential RF and internal biasing
    (default for CC2640R2 LaunchPad)
    * CC2650EM_5XD – Differential RF and external biasing
    * CC2650EM_4XS – Single-ended RF on RF-P and external biasing
    * CC2640R2DK_CXS - WCSP: Single-ended RF on RF-N and external biasing
    * (Note that the WCSP is only tested and characterized for
    * single ended configuration, and it has a WCSP-specific
    * PA table)
    *
    * Note: CC2650EM_xxx reference designs apply to all CC26xx devices.
    * ==========================================================================
    */
    #define CC2650EM_7ID

    -kel;
  • 0 in reply to Markel Robregado
    TI__Guru** 106705 points
    Hi Martin,

    It could be that you have a large frequency offset on the RF carrier, which most devices can handle, but some do not.

    Have you measured the frequency offset of your HW?

    What 24 MHz crystal are you using, and what is the cap-array setting?

    Regards,
    Fredrik