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.

CC2650: Mobile phone can't connect to a custom CC2650-based board

Part Number: CC2650


Hello,

I am working on a custom board using CC2650. At first sight the hardware has no obvious problems, including the RF part - I have tested sending and receiving of packets between custom board and Launchpad using Smart RF studio and this works fine. Advertising also goes well - the device can be seen in the device list of phone when scanning for devices. However, there is a strange situation - when trying to connect the custom device from the phone it is not possible. When downloading a Launchpad board with the same stack & application, it does connect correctly. I am seeking ideas where to search for the problem and how to debug it.

Especially, on the communication side the custom board and Launchpad should not differ, MCU is also identical. In case advertising is fine, and sending and receiving packets by Smart RF studio is fine, could the problem be still in the hardware? There is a strange phenomenon that the connection between mobile phone and target board was once possible in the evening, however, without any modification, on the next day it was able to advertise, but not able to connect...

  • Hello,
    Is there anyone to see my question above? I will simplify my request: I used the "simple BLE peripheral" demo for CC2650 Launchpad - when loading it into Launchpad Board, advertising and connection to board are fine; when loading it into the custom board, advertising is fine, but connection to board does not work. What I need is a hint where to dig to identify the particular problem.
  • Hi Kamen,

    This sounds like a problem with the RTC. What 32 kHz clock source are you using? Have you verified its accuracy? If not, take a look in chapter 11 of the Technical Reference Manual (www.ti.com/lit/pdf/swcu117) for instructions on how to output the clock an a pin for measurement.

    Cheers,
    Fredrik
  • Thanks for support, Fredrik! It turned somehow to be a soldering problem - after replacing the CC2650 with a new one for another problem, the communication started working as intended.
    Kind regards,
    Kamen