SIMPLELINK-CC13XX-CC26XX-SDK: BTool is unable to connect to the target end.

tian lin

Part Number: SIMPLELINK-CC13XX-CC26XX-SDK
Other Parts Discussed in Thread: CC1352P7, CC1352P

hello,

When I was using two CC1352P-2 to implement BLE OAD, I encountered a problem that the BTool tool couldn't connect to the target device. I followed exactly the operations described in the document, but there was a problem where the connection would be established and then disconnected immediately. However, BTool did not report any errors. Regarding the firmware and programs used, all of them were taken from the SDK. The only modification was to set the transmission power of the target end to 20.The mobile phone can be connected to the target device.

Can you help me please?

Below is the log of BTool

[1] : <Tx> - 10:44:44.902
-Type : 0x01 (Command)
-OpCode : 0xFE62 (GapInit_connect)
-Data Length : 0x0A (10) byte(s)
PeerAddrType : 0x00 (0) (PEER_ADDRTYPE_PUBLIC_OR_PUBLIC_ID)
PeerAddr : 80:6F:B0:29:36:DE
InitiatingPhy : 0x01 (1) (
INIT_PHY_1M)
Timeout : 0x0000 (0)
Dump(Tx):
0000:01 62 FE 0A 00 DE 36 29 B0 6F 80 01 00 00 .b....6).o....
--------------------------------------------------------------------
[2] : <Rx> - 10:44:44.919
-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..
--------------------------------------------------------------------
[3] : <Rx> - 10:44:44.951
-Type : 0x04 (Event)
-EventCode : 0x00FF (HCI_LE_ExtEvent)
-Data Length : 0x14 (20) bytes(s)
Event : 0x0605 (1541) (GAP_EstablishLink)
Status : 0x00 (0) (SUCCESS)
DevAddrType : 0x00 (0) (ADDRTYPE_PUBLIC)
DevAddr : 80:6F:B0:29:36:DE
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 00 DE 36 29 B0 6F 80 00 00 08 ........6).o....
0010:50 00 00 00 D0 07 00 P......
--------------------------------------------------------------------
[4] : <Tx> - 10:44:44.953
-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.
--------------------------------------------------------------------
[5] : <Info> - 10:44:44.997
Device Connected
Handle = 0x0000
Addr Type = 0x00 (ADDRTYPE_PUBLIC)
BDAddr = 80:6F:B0:29:36:DE
--------------------------------------------------------------------
[6] : <Rx> - 10:44:44.983
-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 ...." ...
--------------------------------------------------------------------
[7] : <Info> - 10:44:45.552
Device Disconnected
Handle = 0x0000
Addr Type = 0x00 (ADDRTYPE_PUBLIC)
BDAddr = 80:6F:B0:29:36:DE
--------------------------------------------------------------------
[8] : <Rx> - 10:44:45.552
-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 ........>
--------------------------------------------------------------------

The following is the program at the target end.

1 month ago

0 Daniel Guarecuco Aguiar 1 month ago

TI__Expert 4637 points

Hi Tian,

Does it also happen with a lower TX power? Can you share your SDK version?

I haven't been able to reproduce the issue. I'm attaching here my own bin files

E2E_BTool_Issue.zip

Best regards,

Daniel

0 tian lin 1 month ago in reply to Daniel Guarecuco Aguiar

Prodigy 10 points

hi Daniel,
I conducted experiments on both versions of the SDK, and the results were the same. The default transmission power is 0, but BTool was unable to locate the target end. Therefore, I adjusted the transmission power.
Thank you !

0 tian lin 1 month ago in reply to Daniel Guarecuco Aguiar

Prodigy 10 points

hi Daniel,

I directly used the bin file you sent me, and then conducted the test again following my previous operations. The result was still the same - it connected but then disconnected immediately. I had previously replaced the device with CC1352P7, but the result was the same. So at that time, I ruled out the hardware issue. However, I successfully implemented OAD using the SimpleLink Starter APP.

0 Daniel Guarecuco Aguiar 1 month ago in reply to tian lin

TI__Expert 4637 points

Hi Tian,

That is odd.

From your first test and second, are these different peripheral devices or the same? I see they have different addresses in your screenshot. Can you confirm you have the right address by opening a UART console on the peripheral?

Best regards,

Daniel

0 tian lin 1 month ago in reply to Daniel Guarecuco Aguiar

Prodigy 10 points

hi Daniel,
Sorry, it's my fault. I swapped the roles of two CC1352P2 chips. Before that, I had also used other CC microcontrollers for testing. However, I confirmed the correctness of their addresses through my phone to ensure they could be detected, and the names were correct as well.

Best regards

Tian

0 Daniel Guarecuco Aguiar 1 month ago in reply to tian lin

TI__Expert 4637 points

Thanks!

One additional question, are these CC1352P2 Launchpads (https://www.ti.com/tool/LAUNCHXL-CC1352P) or just the CC1352P MCU in a custom board. If it is custom, do they have a crystal oscillator?

Best regards,

Daniel

0 tian lin 1 month ago in reply to Daniel Guarecuco Aguiar

Prodigy 10 points

hi Daniel,

Yes, I am using the CC1352P2 Launchpads, which are the same development boards as shown in the picture.Apart from my computer, I also tried it on another computer, but it didn't work. One system was Windows 11 and the other was Windows 10.I suspect the problem lies on the computer rather than on the single-chip microcontroller.

Best regards

Tian

0 Daniel Guarecuco Aguiar 1 month ago in reply to tian lin

TI__Expert 4637 points

Hi Tian,

Now I'm a bit puzzled, as that is also my setup.

You mentioned that the peripheral doesn't show when using 0dBm, but it should likely show up if both boards are next to each other. Have you also flashed the .hex file I provided for the host device that connects to the PC?

Best regards,

Daniel

0 tian lin 1 month ago in reply to Daniel Guarecuco Aguiar

Prodigy 10 points

hi Daniel,
Yes, I used the file you provided, correctly burned the re-image, and successfully connected to BTool.

Best regards

Tian

0 Daniel Guarecuco Aguiar 1 month ago in reply to tian lin

TI__Expert 4637 points

Thanks,

Do you get any message on the peripheral console?

0 tian lin 1 month ago in reply to Daniel Guarecuco Aguiar

Prodigy 10 points

The target end has successfully run. I can see the information output through the serial port. Its initialization was successful and it provided me with an address. I can confirm the information is correct using my mobile phone. The UUID of OAD can also be seen on the mobile phone.

0 Daniel Guarecuco Aguiar 1 month ago in reply to tian lin

TI__Expert 4637 points

Hi Tian,

1. Using your phone (with SimpleLink Connect app, for instance) can you read from the characteristics?

2. Have you modified anything inside the btool directory?

Best regards,

Daniel

0 tian lin 1 month ago in reply to Daniel Guarecuco Aguiar

Prodigy 10 points

hi Daniel,

1、Yes, I can see it, and I have successfully run OAD using the SimpleLink starter APP.
2、No, I didn't make any changes to any of the files related to BTool. I merely opened it in the SDK.

Currently, I plan to use this method as a replacement for BTool.

Best regards

Tian

0 Daniel Guarecuco Aguiar 1 month ago in reply to tian lin

TI__Expert 4637 points

Hi Tian,

If you flash your second Launchpad with the peripheral binary, are you also able to run an OAD with the phone?

Best regards,

Daniel

0 tian lin 1 month ago in reply to Daniel Guarecuco Aguiar

Prodigy 10 points

hi Daniel,

I just conducted a test. Another CC1352P2 board can also perform the OAD function by downloading the same program. I tested it on both SDK versions 8.32 and 5.20, and found that the speed on version 8.32 was twice as fast.
I'm currently facing another issue. The SimpleLink starter APP frequently crashes. The version number is 5.14 and it is for the Android platform. I couldn't find the download link for it on the official website.

Best regards

Tian

0 Daniel Guarecuco Aguiar 1 month ago in reply to tian lin

TI__Expert 4637 points

Hi Tian,

Thanks, please use SimpleLink Connect app instead which is actively maintaned https://play.google.com/store/apps/details?id=com.ti.connectivity.simplelinkconnect&hl=en

0 tian lin 1 month ago in reply to Daniel Guarecuco Aguiar

Prodigy 10 points

hi Daniel,

Thank you very much for your professional assistance. The content you shared has been extremely helpful to me, and I hereby express my sincere thanks.

Best regards,

Tian

0 Daniel Guarecuco Aguiar 1 month ago in reply to tian lin

TI__Expert 4637 points

Hi Tian,

Thanks!, unfortunately I think I cannot help you anymore as I cannot replicate it at all. If you try anything else that helps us debug the issue, please let us know.

Best regards,

Daniel

Bluetooth®︎

Bluetooth forum

SIMPLELINK-CC13XX-CC26XX-SDK: BTool is unable to connect to the target end.