LAUNCHXL-CC2640R2: BTool Error - Connection Handle not found

Hello,

I have a few questions that will help us get to the bottom of this more efficiently. Are you using the 1.40 SDK version of BTool and host_test? Can you connect to a device using BTool? Can you try flashing the simple_peripheral project onto your LaunchPad and attempting to connect to it using BTool? All of the examples available for the 1.40 SDK are present in the SDK directory which by default should be in the C:\ti\ folder. There you should be able to find the simple_peripheral_oad_offchip project and many others.

Regards,

Jan

Hello Jan,

Yes, I am currently using SDK 1.40.00.45. I was able to connect to LAUNCHXL-CC2640R2 board using BTool by establishing UART connection on entering BTool. I was able to run the project zero on the development kit and control the LEDS using Sensor Tag iOS application, but didnt test using BTool. But I was never able to establish OAD using BTool due to the Connection handle error that I had attached in my previous question.

Best Regards,

Nandhini Jayapandian

Hi Nandhini,

Would you be able to flash one LaunchPad with the regular simple_peripheral and a second LaunchPad with host_test? If so, can you attempt to connect to the simple_peripheral LaunchPad using host_test in Btool? Afterwards, can you verify if you can modify and interact with the characteristics shown in Btool for the simple_peripheral project? I want to ensure that your Btool installation and host_test project are working properly.

Regards,

Jan

Hello Jan,

As per your suggestion I tried the following steps for testing simple peripheral off chip oad example:

(1) Built the off chip oad bim program in CCSv7 (imported example from simplelink SDK 1.40.00.45 into the CCSv7 workspace)

(2) Built the off chip oad stack program in CCSv7 (imported example from simplelink SDK 1.40.00.45 into the CCSv7 workspace)

(3) Built the off chip oad app program in CCSv7 (imported example from simplelink SDK 1.40.00.45 into the CCSv7 workspace)

(4) Loaded the off chip oad bim program (.hex file) using Smart RF Flash programmer 2 to LAUNCHXL-CC2640R2F

(5) Loaded the off chip oad stack program (.hex file) using Smart RF Flash programmer 2 to LAUNCHXL-CC2640R2F

(6) Loaded the off chip oad app program (.bin file) using Smart RF Flash programmer 2 to LAUNCHXL-CC2640R2F

(7) For steps (4), (5) & (6), selected the "Pages in Image" option available under Eraze section in the Smart RF Flash Programmer 2

(8) Entered BTool (used btool.exe file available under tools -> btool -> btool.exe and was unable to suucessfully establish serial port connection due to device timeout error as shown in the attachment.

The BTool UART setup with the LAUNCHXL-CC2640R2F was successful and was able to scan for peripheral devices by using the scan option in the Discover/Connect subsection after programming the LAUNCHXL-CC2640R2F board with host_test.hex file. But still I am unable to send the image (*oad.bin file) via OAD using the "Send" option available under OAD subsection of the BTool due to Connection Handle error (shown in the attachment).

Can you please review and advise whether I am following the right procedure?

Best Regards,

Nandhini Jayapandian

BTool_Errors_04062021.docx

Hi,

Make sure you are using btool and host_test from SDKv1.40. Try this after you get this error. Close Btool, remove Launchpad USB connection, open Btool, connect launchpad USB connection.

-kel

Hello Nandhini,

Are you establishing a connection with the simple_peripheral device before attempting to start the OAD? In order to perform the OAD, you must be connected to the target device. Can you verify this is the case? Also, can you download the SimpleLink Starter mobile app and use it to perform the OAD process through it as well?

Regards,

Jan

Forgot to mention. Close SmartRF Flash Programmer 2 before using BTool.

-kel

Hello Jan,

I could see that the LAUNCHXL-CC2640R2F board that has the host test (named as Board 1 to avoid confusion) gets connected and identified on BTool, but the second LAUNCHXL-CC2640R2F board that has the simple peripheral off chip oad project files (Board 2) is not identified by Board 1 while scanning for peripheral devices using BTool and Board 1 as the central device.

Previously I didn't receive any debug error while trying to Flash the .hex files of bim and stack projects, .bin file of app project for the simple peripheral off chip oad example to the target board (Board 2 in this case). But today, while I tried debugging the project using Board 2, I am unable to debug the project files due to the below error in CCSv7.2:

Cortex_M3_0: Can't Run Target CPU: (Error -2134 @ 0x0) Unable to control device execution state. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.628.3)

Cortex_M3_0: JTAG Communication Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.628.3)

I later used SmartRF Flash Programmer 2 to write the simple peripheral off chip oad project files to Board 2. But still I am unable to find the device while scanning using central device (Board 1) on BTool application. I tried changing USB port for Board 2 and also changed the USB cable, but the above mentioned debug error still persists for Board 2.

Additional Questions: In SmartRF Flash Programmer 2, while programming the below files to Board 2, should I have selected "Pages in Image" under Erase section while programming bim, app and stack projects? and if so in which order should I program these files on the target board. Also are the below listed file names the right ones to program on the Board 2 for establishing oad connection with Board 1 for simple peripheral off chip oad project?

(1) bim_oad_offchip_cc2640r2lp_app.hex

(2) simple_peripheral_cc2640r2lp_oad_offchip_stack_FlashROM.hex

(3) simple_peripheral_cc2640r2lp_oad_offchip_app_FlashROM_oad.bin

NOTE: I have Board 1 (central device) and Board 2 (peripheral device) connected to a single laptop, but configured targetConfigs .ccxml files available in the subfolders for host test and simple peripheral off chip oad projects by saving the right serial numbers in the "Target Configurations" that uniquely enables host test project to point to Board 1 and simple peripheral offchip oad project to point to Board 2.

It will be great if you will be able to review and advise me regarding this concern. Please let me know in case you need step-by-step details on the project flow I am following to build, debug and load host test project on Board 1, simple peripheral off chip oad project on Board 2, establishing serial port connection with Board 1 using BTool, scanning for peripheral devices and establishing connection with Board 2 using BTool for better clarity.

Best Regards,

Nandhini Jayapandian

Hello Kel,

Thank you very much for suggesting me the workaround, but I started receiving debug errors as mentioned in my reply thread to Jan. I tried using SmartRF Flash Programmer 2 for programming the target board with host test project (Board 1) and a second board (Board 2) with simple peripheral off chip oad project, but is unable to find Board 2 under peripheral devices that are scanned by the central device (Board 1) using BTool. Due to this I am unable to establish an OAD connection using BTool.

NOTE: Board 1 (LAUNCHXL-CC2640R2F development kit) named here corresponds to the central device that is programed with host test project

            Board 2 (LAUNCHXL-CC2640R2F development kit) corresponds to peripheral device that should be scanned by Board 1 using BTool

Please let me know incase the step-by-step details of the project flow I am following is required for further analysis.

Best Regards,

Nandhini Jayapandian

Hi Nandhini,

I have done BTool OAD using SDKv1.40 from my previous work numerous times. When I have time I will try again at my home setup and refresh my memory of the correct procedure. The procedure in the documentation should be correct, so if you follow it as is should work.

I think your issue Board 2 Simple Peripheral OAD not advertising needs to be resolved first. Can you try verifying if it is advertising using Smart Phone App like IOS LightBlue or Android nRF Connect. Also can you verify if your Board 2 does not have any HW problems.

Regarding SmartRF Flash Programmer use version 1.8.0

Also, I would advice you to use the latest SDK

-kel

Hello Nandhini,

As a sanity check, can you run the regular (non-OAD) simple_peripheral project on one board and host_test on a second board? Afterwards, can you attempt to connect to the non-OAD simple_peripheral board through Btool and interact with the simple_peripheral characteristics? Can you also attempt to perform the following lab, Enhanced OAD? The lab is in the latest SDK, but being able to perform the lab ensures that all of the equipment and general process is working properly.

Regards,

Jan

Hello,

I was able to resolve the issue after exchanging the boards I was using to load host test and simple peripheral projects. I am not sure on the reason for receiving the debug errors mentioned in my previous post that constantly occurred before exchaning the boards that are being used to load host test and simple peripheral offchip oad project, and the XDS110 connection testing using Target Configuration always passed with no JTAG connectivity issues.

As I am able to execute OAD for the simple peripheral offchip oad example project using BTool without any issues after exchaning the boards, I am all set for now.

Thanks Kel and Jan for all the support!

Best Regards,

Nandhini Jayapandian

Hi Nandhini,

I am glad to hear we were able to help! I have closed the thread and marked this issue as resolved.

Regards,

Jan