SWRA478D February   2015  – January 2019 CC1310 , CC1312PSIP , CC1312R , CC1314R10 , CC1352P , CC1352P7 , CC1352R , CC2640 , CC2640R2F , CC2640R2F-Q1 , CC2642R , CC2642R-Q1 , CC2650 , CC2650MODA , CC2652P , CC2652R , CC2652R7 , CC2652RB , CC2652RSIP

 

  1.   Trademarks
  2. 1Introduction
    1. 1.1 Acronyms
  3. 2Standby
  4. 3Understanding Bluetooth Low Energy Power Metrics
  5. 4SimpleLink Bluetooth Low Energy Wireless MCUs
  6. 5Power Measurement Setup – Preparing the DUT
    1. 5.1 Requirements
    2. 5.2 Embedded Software
    3. 5.3 Hardware
      1. 5.3.1 CC26x2R LaunchPad
    4. 5.4 BTool (Optional)
  7. 6Measuring Power Consumption With a DC Power Analyzer
    1. 6.1 Test Setup
      1. 6.1.1 Analysis Software Setup
    2. 6.2 Measurement Using Scope
    3. 6.3 Analysis
      1. 6.3.1 Advertising Event
      2. 6.3.2 Connection Event
      3. 6.3.3 Power Consumption Calculator
  8. 7EnergyTrace
    1. 7.1 Modifying the rfPacketTX Example
  9. 8References
  10. 9Revision History

5.4 BTool (Optional)

The BLE-Stack also includes BTool along with drivers and firmware. BTool can be used to emulate a Bluetooth Low Energy application from a PC environment. BTool is used to create a connection with the DUT. If the intention is to measure power consumption of the DUT when being in advertising or beacon mode, BTool is not required.

To connect to the DUT using BTool, a device running a Bluetooth Low Energy wireless network processor image named HostTest is required. This can be found with the other example projects in the BLE-Stack.

With a Launchpad running the HostTest application connected to the PC, open BTool and select the COM port used by the application (see Figure 5-3).

GUID-4F230B55-F2B6-46FF-ADDF-4AC994F3F560-low.png Figure 5-3 BTool Serial Port Settings

Press OK and there should be an initialization process that is observed in the log window.

Before forming the connection, the proper connection parameters should be used. This is dependent on the application that is being considered. The supervision timeout setting should not affect the power measurements. A connection interval of one second, with zero slave latency, is used in this document. Therefore, use the values as shown in Figure 5-4. Be sure to select the “Set” button after entering in the values. Setting up the connection parameters needs to be done before a connection is established.

GUID-DD4C7A13-2BEA-4354-AED2-37178D15B061-low.png Figure 5-4 BTool Connection Settings

With the connection parameters set as needed, setup is completed.

At this point, BTool is ready to discover the DUT. If you left the SimpleBLEPeripheral application running on your DUT, you should be ready to use BTool. As long as the device running SimpleBLEPeripheral is powered up and not connected to anything, it should be in discoverable (advertising) mode.

In the Discovery section, press the “Scan” button, as shown in Figure 5-5.

GUID-8C4B45B0-7035-4330-8887-5C540165DE88-low.png Figure 5-5 BTool Scan

BTool will begin searching for Bluetooth Low Energy devices. When the discovery process finishes, the address of any scanned devices will appear in the “Slave BDA” section, as shown in Figure 5-6.

GUID-9972BCA1-0550-4BFE-BC83-5553B4CD94E9-low.png Figure 5-6 BTool Scan Results

To establish a connection with the peripheral device, select the address of the device to connect with and click the “Establish” button, as shown in Figure 5-7.

GUID-072A2437-4F80-41D5-A0CA-E639CA789AFE-low.png Figure 5-7 BTool Establish Link

As long as the peripheral is powered-up and still in discoverable mode, a connection should be established immediately. Once a connection is established, the message window will return a “GAP_EstablishLink” event message with a “Status” value of “0x00 (Success)”. In BTool, you can see your connected peripheral device in the Device Information field, as shown in Figure 5-8.

GUID-8F8A0BA7-0037-415D-84D7-8705F80866E0-low.png Figure 5-8 BTool Connected Device