• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 847 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.

LAUNCHXL-CC1352R1: "Timeout Connecting fail from the peripheral" using more than one BLE application

James Mel
Expert 1380 points
Part Number: LAUNCHXL-CC1352R1
Other Parts Discussed in Thread: BLE-STACK,

Hi,

I have an old LaunchPad of cc1352R1 (rev c) and I have my own custom board using the new cc1352R1 (rev e). I connected the debugger on the old LaunchPad to burn the firmware on the new custom board and I didn't encounter any errors. I tried the simple peripheral app and project zero to check that the BLE is working fine. I tried using 3 BLE mobile apps to establish a connection but it has been always a failure.

It keeps telling me "connecting to the peripheral" and after around 20 seconds, it tells me "Timeout Connecting fail from the peripheral". I also tried TI's sensor tag application but it didn't connect to it.

Can anyone help?

Note I am using simplelink_cc13x2_26x2_sdk_3_20_00_68 and CCS v9.1.

Regards
James

  • 0
    TI__Guru 57865 points

    Hi James,

    I assume that the device actually starts advertising since you get connect fail. If so, thats good because it means that the BLE-Stack runs correctly. Could you verify that you have followed this guide when designing your board:

    http://www.ti.com/lit/swra640 

    A wild guess would be that it's something fishy with the 32kHz sleep XTAL in your system. It's a common culprit with custom designs not being able to connect or maintain a connection.

  • 0 in reply to J Lindh
    Expert 1380 points

    Hi Joakim,
    Thanks for your reply :).

    I have checked the 32KHz sleep XTAL and it is working fine.

    Can You guess what shall be the problem in this case?

    Is there anything wrong with the SDK or the CCS versions? Is there a problem using the old LaunchPad to burn the firmware?

    Does the simple peripheral app work by connecting to the mobile using BLE Scanner or nRF Connect?

    Thanks in advance
    James

  • 0
    Expert 1380 points

    Part Number: LAUNCHXL-CC1352R1

    Hi there,
    I want help regarding this question since J Lindh won't be available soon, and I need help regarding this.

    Regards
    James

  • 0 in reply to James Mel
    TI__Guru* 86971 points

    Can you please try and run some of the very simple proprietary examples found here:

    and see if they run as expected or not. We need to figure out if your problems is related to BLE or if you have some kind of HW issue.

    BR

    Siri

  • 0 in reply to Siri
    Expert 1380 points

    Thanks Siri.
    I have managed to solve this problem. The issue was with the soldering of the debug wires, I have searched for the error and it was HCI_ERROR_CODE_CONN_FAILED_TO_ESTABLISH and someone mentioned the soldering so I tried another custom board of mine and it worked perfectly :).
    Regards
    James

  • 0 in reply to James Mel
    TI__Guru* 86971 points

    Glad you were able to figure it out :-)

    Siri