• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 474 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.

Original question:

CC1352P: BLE simple peripheral connection problem

CC1352R: BLE connection problem on custom board

user6319636
Intellectual 700 points

Part Number: CC1352R

Hi, 

We are working with CC1352R Custom board and LAUNCHXL-CC1352R1. We are using following tools:

1. SDK V3.40.00.02

2. CCS9.3.0

3. iOS LightBlue Application

4. Our custom board: CC1352R1F3 TI 98J E. PD2T G4

5. LAUNCHXL-CC1352R1: CC1352R1F3 TI 98J E. PD30 G4

We have used simple peripheral OAD onchip application example code.

1. On our own custom board, I can scan "SP OAD on-chip" through LightBlue application but when I am trying to connect peripheral, but I come across a  problem about establishing BLE connection:

According to debug information from serial port, when BLE link is established, it is disconnecting immediately. So I could not able to connect the peripheral through LightBlue application.

2. On LAUNCHXL-CC1352R1, I have flashed same application code. I can scan "SP OAD on-chip" through LightBlue application and I can connect peripheral successfully and everything is ok. 

I have adjusted capacitor array on our custom board and we have checked and verified the frequency error is less or equal than 20 ppm, but the same problem is still there. Now I don't know what is the problem? Can you give me some good suggesions or guide to sovle this problem?

Thank you very much!

BRs.

  • 0
    Intellectual 700 points

    Hi,

    I establish a BLE connection using BTool and add more debug information as follows:

    [321] : <Tx> - 02:53:21.702
    -Type : 0x01 (Command)
    -OpCode : 0xFE62 (GapInit_connect)
    -Data Length : 0x0A (10) byte(s)
    PeerAddrType : 0x01 (1) (PEER_ADDRTYPE_RANDOM_OR_RANDOM_ID)
    PeerAddr : 4E:2B:92:F4:AE:57
    InitiatingPhy : 0x01 (1) (
    INIT_PHY_1M)
    Timeout : 0x0000 (0)
    Dump(Tx):
    0000:01 62 FE 0A 01 57 AE F4 92 2B 4E 01 00 00 .b...W...+N...
    --------------------------------------------------------------------
    [322] : <Rx> - 02:53:21.749
    -Type : 0x04 (Event)
    -EventCode : 0x00FF (HCI_LE_ExtEvent)
    -Data Length : 0x06 (6) bytes(s)
    Event : 0x067F (1663) (GAP_HCI_ExtentionCommandStatus)
    Status : 0x00 (0) (SUCCESS)
    OpCode : 0xFE62 (GapInit_connect)
    DataLength : 0x00 (0)
    Dump(Rx):
    0000:04 FF 06 7F 06 00 62 FE 00 ......b..
    --------------------------------------------------------------------
    [323] : <Rx> - 02:53:22.097
    -Type : 0x04 (Event)
    -EventCode : 0x00FF (HCI_LE_ExtEvent)
    -Data Length : 0x14 (20) bytes(s)
    Event : 0x0605 (1541) (GAP_EstablishLink)
    Status : 0x00 (0) (SUCCESS)
    DevAddrType : 0x01 (1) (ADDRTYPE_RANDOM)
    DevAddr : 4E:2B:92:F4:AE:57
    ConnHandle : 0x0000 (0)
    ConnRole : 0x08 (8) (
    Central)
    ConnInterval : 0x0050 (80)
    ConnLatency : 0x0000 (0)
    ConnTimeout : 0x07D0 (2000)
    ClockAccuracy : 0x00 (0)
    Dump(Rx):
    0000:04 FF 14 05 06 00 01 57 AE F4 92 2B 4E 00 00 08 .......W...+N...
    0010:50 00 00 00 D0 07 00 P......
    --------------------------------------------------------------------
    [324] : <Tx> - 02:53:22.098
    -Type : 0x01 (Command)
    -OpCode : 0x2022 (HCI_LE_SetDataLength)
    -Data Length : 0x06 (6) byte(s)
    Handle : 0x0000 (0)
    TxOctets : 0x00FB (251)
    TxTime : 0x0848 (2120)
    Dump(Tx):
    0000:01 22 20 06 00 00 FB 00 48 08 ." .....H.
    --------------------------------------------------------------------
    [325] : <Info> - 02:53:22.143
    Device Connected
    Handle = 0x0000
    Addr Type = 0x01 (ADDRTYPE_RANDOM)
    BDAddr = 4E:2B:92:F4:AE:57
    --------------------------------------------------------------------
    [326] : <Rx> - 02:53:22.129
    -Type : 0x04 (Event)
    -EventCode : 0x000E (HCI_CommandCompleteEvent)
    -Data Length : 0x06 (6) bytes(s)
    Packets : 0x01 (1)
    OpCode : 0x2022 (HCI_LE_SetDataLength)
    Status : 0x00 (0) (SUCCESS)
    Handle : 0x0000 (0)
    Dump(Rx):
    0000:04 0E 06 01 22 20 00 00 00 ...." ...
    --------------------------------------------------------------------
    [327] : <Info> - 02:53:22.698
    Device Disconnected
    Handle = 0x0000
    Addr Type = 0x01 (ADDRTYPE_RANDOM)
    BDAddr = 4E:2B:92:F4:AE:57
    --------------------------------------------------------------------
    [328] : <Rx> - 02:53:22.697
    -Type : 0x04 (Event)
    -EventCode : 0x00FF (HCI_LE_ExtEvent)
    -Data Length : 0x06 (6) bytes(s)
    Event : 0x0606 (1542) (GAP_TerminateLink)
    Status : 0x00 (0) (SUCCESS)
    ConnHandle : 0x0000 (0)
    Reason : 0x3E (62) (FAILED_TO_ESTABLISH)
    Dump(Rx):
    0000:04 FF 06 06 06 00 00 00 3E ........>
    --------------------------------------------------------------------

  • 0
    Expert 2170 points

    Hi,

    Sounds like your RTC (32 kHz) clock is off. See section 6.3 here: CC13xx/CC26xx Hardware Configuration and PCB Design Considerations (Rev. E)

    Fredrik