Texas Instruments SWRU197F User manual

CC Debugger
User’s Guide
SWRU197F

SWRU197F
June 2013
2/23
Table of Contents
1Introduction................................................................................................................................. 3
2Abbreviations and Acronyms.................................................................................................... 3
3Box Contents .............................................................................................................................. 4
4Operating Conditions of the CC Debugger.............................................................................. 4
5Initial Steps.................................................................................................................................. 5
5.1 Installing the USB driver ........................................................................................................... 5
5.2 Supported PC Tools.................................................................................................................. 5
6Connecting the CC Debugger to the Device............................................................................ 6
6.1 Target Connector Details.......................................................................................................... 6
6.2 Connecting the CC Debugger to a System on Chip ................................................................. 8
6.2.1 Minimum connection for debugging....................................................................................................................... 8
6.2.2 Minimum connection for SmartRF Studio .............................................................................................................. 8
6.2.3 Minimum connection for SmartRF Packet Sniffer .................................................................................................. 9
6.3 Connecting the CC Debugger to a Transceiver...................................................................... 10
6.4 Connecting the CC Debugger to a CC85xx............................................................................ 12
7Using the CC Debugger ........................................................................................................... 13
7.1 Understanding the LED........................................................................................................... 13
8Updating the Firmware............................................................................................................. 14
8.1 Updating the firmware automatically in SmartRF Studio........................................................ 14
8.2 Updating the firmware manually in SmartRF Flash Programmer........................................... 16
8.3 Forced boot recovery mode.................................................................................................... 17
8.4 Resurrecting the CC Debugger............................................................................................... 17
9Troubleshooting ....................................................................................................................... 20
10 Schematics................................................................................................................................ 21
11 References ................................................................................................................................ 21
12 Document History..................................................................................................................... 22

SWRU197F
June 2013
3/23
1 Introduction
The CC Debugger is primarily used for flash programming and debugging software running on CCxxxx
8051-based System-on-Chip (SoC) devices from Texas Instruments. The PC tools available for these
purposes are the SmartRF™ Flash Programmer [9] from Texas Instruments and IAR Embedded
Workbench® for 8051 from IAR Systems [15].
When connected to the debugger, the SoC devices can be controlled directly from SmartRF™ Studio
[8]. SmartRF Studio will also be able to control supported CCxxxx RF transceivers (CC2520, CC2500,
CC110x, CC11xL, CC112x, CC120x) when they are connected to the debugger as explained in
chapter 6.3.
In addition, CC Debugger is used for configuring the CC85xx devices with PurePath Wireless
Configurator [12] and controlling them with PurePath Wireless Commander [13].
2 Abbreviations and Acronyms
CSn
Chip Select (active low)
DC
Debug Clock
DD
Debug Data
DUT
Device Under Test
GND
Ground
LED
Light Emitting Diode
MISO
Master In Slave Out
MOSI
Master Out Slave In
RF
Radio Frequency
SCLK
Serial Clock
SoC
System on Chip
SPI
Serial Peripheral Interface
USB
Universal Serial Bus
Vdd
Positive voltage on target

SWRU197F
June 2013
4/23
3 Box Contents
1 x CC Debugger
1 x USB-A to Mini-B USB cable
1 x 10-pin flat cable with 2x5 2.54 mm connector
1 x 10-pin flat cable with 2x5 1.27 mm connector
1 x Converter board 2.54 mm –1.27 mm connector
Documentation
4 Operating Conditions of the CC Debugger
Minimum target voltage: 1.2 Volt
Maximum target voltage: 3.6 Volt
Operating temperature: 0C to 85C
Regulated voltage on CC Debugger: 3.3 Volt
Maximum target current (*): 200 mA (*)
Supported Operating Systems: Microsoft® Windows® 2000
Windows XP SP2/SP3 (32 bit versions)
Windows Vista® (32 & 64 bit)
Windows 7 (32 & 64 bit)
(*) Only applicable if the target is powered from the CC Debugger
Figure 1 - CC Debugger connected to a SoC Battery Board with a CC2530EM

SWRU197F
June 2013
5/23
5 Initial Steps
5.1 Installing the USB driver
To get the required USB driver for the CC Debugger, it is necessary to install one of the tools listed
below:
SmartRF Studio www.ti.com/tool/smartrftm-studio
SmartRF Flash Programmer www.ti.com/tool/flash-programmer
SmartRF Packet Sniffer www.ti.com/tool/packet-sniffer
PurePath Wireless Configurator www.ti.com/tool/purepath-wl-cfg
PurePath Wireless Commander www.ti.com/tool/purepath-wl-cmd
Alternatively, you can download “Cebal –CCxxxx Development Tools USB Driver for Windows x86
and x64”[4] which is a standalone installer including only the device driver.
After having installed the driver, connect the CC Debugger to the PC. The USB driver will be installed
automatically. You can quickly check that the debugger has been associated correctly with the USB
device driver by opening the Windows Device Manager. The debugger should appear as a “Cebal
controlled device”.
Figure 2 - Verify correct driver installation
For further details or troubleshooting the driver installation process, please refer to “DN304 –CCxxxx
Development Tools USB Driver Installation Guide”[5].
5.2 Supported PC Tools
Currently, the CC Debugger can be used together with the following PC Tools
IAR Embedded Workbench for 8051 In circuit debugging of system-on-chips
SmartRF Flash Programmer Flash programming of system-on-chips
SmartRF Studio RF testing of radio devices (transceivers and SoCs)
SmartRF Packet Sniffer Packet sniffing with selected radio devices
PurePath Wireless Configurator Programming of CC85xx devices
PurePath Wireless Commander Advanced control of CC85xx devices
The debugger will operate as the interface between the RF device and the tools listed above. Please
ensure correct connection between the device and CC Debugger before starting to use the tools.
The connection of the device to the CC Debugger will be covered in the next chapter.

SWRU197F
June 2013
6/23
6 Connecting the CC Debugger to the Device
6.1 Target Connector Details
The target connector, located on the lateral side of the debugger, is a 10-pin 2x5 2.54 mm pitch
connector with a direction coded plastic guide. Suggested matching (male) surface mounted headers
would be 95278-101A10LF from FCI or BB02-HP from GradConn.
Figure 3 - Placement of Target Connector Pins
The adapter board, which has a 10-pin 2x5 1.27 mm pitch connector, has the same pin placement.
Suggested matching (male) surface mounted headers would be 20021121-000-10C4LF from FCI or
FTS-105-01-F-DV from Samtec.
Figure 4 - Placement of Target Connector Pins on Adapter Board
The pin-out of the target connector is shown in Figure 5. Note that not all of these pins need to be
connected to the target device for programming and debugging. Only Vdd, GND, DD, DC and RESET
are required for System on Chips. The other pins are optional and/or for special features.
Pin 1
Pin 2
Pin 1
Pin 2

SWRU197F
June 2013
7/23
21
43
65
87
109
GND
DC (Debug Clock)
CSn (SPI Chip Select)
RESETn
3.3V (from debugger)
Target Voltage Sense
DD (Debug Data)
SCLK (SPI Clock)
MOSI (SPI Data Out)
MISO (SPI Data In)
Figure 5 - Target Connector Pin-out
Please note the concept with the target voltage sense signal. This signal is used by the level
converters on the CC Debugger to handle different voltage levels on the target board and the
debugger. Pin 2 on the target connector must be connected to Vdd on the target board.
USB
Controller Level Converter
Vdd from
target
Vdd (local)CC Debugger
TARGET
Target
Connector
Figure 6 - Voltage from target to CC Debugger
Alternatively, it is possible to power the target by connecting pin 9 to Vdd on the target. In that case,
the CC Debugger will supply 3.3V to the target.

SWRU197F
June 2013
8/23
6.2 Connecting the CC Debugger to a System on Chip
6.2.1 Minimum connection for debugging
For successful debugging of a TI 8051-based RF System on Chip, connect the two debug signals
Debug Data (DD) and Debug Clock (DC) and the reset signal RESETn to the device. Note that DD is a
bidirectional signal. In addition, the CC Debugger must be connected to GND and Vdd on the board.
Vdd is used as an input to the level shifters on the CC Debugger, thus allowing a different operating
voltage on the target than internally on the debugger.
For CC111x, CC251x, CC243x, CC253x and CC254x, except CC2544 and CC2545, connect the DD
signal to pin P2.1 and DC to pin P2.2.
For CC2544, connect the DD signal to P1.3 and DC to P1.2.
For CC2545, connect the DD signal to P1.3 and DC to P1.4.
Note that it is possible to power the target board from the debugger by connecting the 3.3V signal on
pin 9 on the connector to the target board.
21
43
65
87
109
GND
DC (Debug Clock)
RESETn
3.3V from debugger. Can
optionally be used to
power the target board
DD (Debug Data)
SoC
P2.2
P2.1
RESETn
Vdd
GND
Vdd
CC Debugger
Connector CCxxxx
System-on-Chip
NOTE 2
Vdd
NOTE 1
10 kΩ
2.7 kΩ
1 nF
Figure 7 - Minimum connection for debugging of 8051 SoC
Note 1: Some early revisions of certain SoCs (CC2430, CC2510 and CC1110) needed an external
pull-up to avoid unwanted transitions on the debug clock line during chip reset –thus inadvertently
setting the device in debug mode. All new revisions of all SoCs now have an internal pull-up on P2.2,
so this external component is not required.
Note 2: The RESETn pin is sensitive to noise and can cause unintended reset of the chip. For reset
lines susceptible to noise, it is recommended to add an external RC filter. Please refer to the
respective SoC datasheet and reference designs for recommended RESET circuitry. The CC
Debugger supports slow transitions on the reset line, using a 2 ms delay between any transition on the
RESET line and other transitions on the DC and/or DD lines.
6.2.2 Minimum connection for SmartRF Studio
Use the same connection as for debugging the SoC.

SWRU197F
June 2013
9/23
6.2.3 Minimum connection for SmartRF Packet Sniffer
In order to use the packet sniffer capabilities of the CC Debugger, it is also necessary to connect the
SPI bus to the SoC. The SPI interface is used by the CC Debugger for reading the captured RF
packets from the SoC.
21
43
65
87
109
GND
DC (Debug Clock)
RESETn
3.3V from debugger. Can
optionally be used to
power the target board
DD (Debug Data) SoC
P2.2
P2.1
RESETn
Vdd
GND
Vdd
CC Debugger
Connector CCxxxx
System-on-Chip
2.7 kΩ
1 nF
CSn
SCLK
MOSI
MISO
P1.7
P1.6
P1.5
P1.4
Figure 8 - Connection to SoC to enable Packet Sniffing
Note that the packet sniffer will overwrite the flash on the SoC with special packet capture firmware.
Note concerning the SPI interface to the SoC used for packet sniffing
All of the current TI RF SoCs can be configured to operate as SPI slaves, with the SPI signals (CS,
SCLK, MISO and MOSI) going to one of the USART peripherals. The packet sniffer application will
program the SoC with firmware that configures one of the USART peripherals in order to communicate
with the CC Debugger. The firmware can use any of the four possible pin configurations (USART 0 or
1, pin out alternative 1 or 2). However, only a subset is currently supported:
USART0, alt 1
USART0, alt 2
USART1, alt 1
USART1, alt 2
CC243x
-
-
-
OK
CC253x/CC254x
-
-
-
OK
CC111x
OK
-
-
OK
CC251x
OK
-
-
OK
Table 1 - Supported SPI connections (marked OK)
USART0, alt 1
USART1, alt 2
SCLK
P0.5
P1.5
CS
P0.4
P1.4
MOSI
P0.3
P1.6
MISO
P0.2
P1.7
Table 2 - USART pin out details
In case of multiple supported interfaces, the Packet Sniffer application will let you choose which
interface to use.

SWRU197F
June 2013
10/23
6.3 Connecting the CC Debugger to a Transceiver
The SPI interface on the CC Debugger can be used to interface many of the CCxxxx transceivers and
control them from SmartRF Studio. The transceivers/transmitters/receivers currently supported are:
CC1100
CC1101
CC1120
CC1121
CC1125
CC1175
CC110L
CC113L
CC115L
CC1200
CC1201
CC2500
CC2520
Note that the CC Debugger operates as the SPI Master. In a multi master system, it is necessary to
make sure the debugger output signals (DC, DD, CSn, SCLK, MOSI and RESETn) do not interfere
with the other SPI master on the board. The other SPI master would typically be the microcontroller on
the board.
The connection diagrams below show the interconnection between the debugger and the various
supported transceivers.
21
43
65
87
109
GND
DC
RESETn
3.3V from debugger. Can
optionally be used to
power the target board
DD
GPIO3
VREG_EN
RESETn
Vdd
GND
Vdd
CC Debugger
Connector CC2520
CSn
SCLK
MOSI
MISO
SO
SI
SCLK
CSn
Figure 9 - CC Debugger connected to CC2520

SWRU197F
June 2013
11/23
21
43
65
87
109
GND
DC
RESETn
3.3V from debugger. Can
optionally be used to
power the target board
DD
GPIO2
GPIO0
RESETn
Vdd
GND
Vdd
CC Debugger
Connector CC112x
CC1175
CC120x
CSn
SCLK
MOSI
MISO
SO
SI
SCLK
CSn
Figure 10 - CC Debugger connected to CC112x/CC1175/CC120x
21
43
65
87
109
GND
DC
3.3V from debugger. Can
optionally be used to
power the target board
DD
GDO2
GDO0
Vdd
GND
Vdd
CC Debugger
Connector CC110x
CC11xL
CC2500
CSn
SCLK
MOSI
MISO
SO
SI
SCLK
CSn
Figure 11 - CC Debugger connected to CC110x/CC11xL/CC2500

SWRU197F
June 2013
12/23
6.4 Connecting the CC Debugger to a CC85xx
In order to configure the CC85xx devices (i.e. program the flash on the device) with PurePath Wireless
Configurator, the device’s SPI interface must be connected to the CC Debugger as shown in the figure
below.
21
43
65
87
109
GND
RESETn
3.3V from debugger. Can
optionally be used to
power the target board
RESETn
Vdd
GND
Vdd
CC Debugger
Connector CC85XX
CSn
SCLK
MOSI
MISO
MISO
MOSI
SCLK
CSn
Figure 12 - CC Debugger connected to CC85XX

SWRU197F
June 2013
13/23
7 Using the CC Debugger
After having connected the debugger to the target device, the debugger can be powered up by
plugging in the USB cable.
The debugger will immediately start a device detection process, looking for all known devices. If no
devices are detected, the LED will be RED. If a device is detected, the LED will be GREEN.
If the LED is GREEN, it is possible to start using the debugger together with one of the supported PC
tools.
7.1 Understanding the LED
OFF
The debugger has no power or there is no valid firmware on the debugger.
Make sure the debugger is properly powered via the USB cable or try to
resurrect the debugger using the method described in chapter 8.4.
AMBER (BOTH LEDS ON)
The debugger is powered, but there is no valid firmware. Try to resurrect
the debugger using the method described in chapter 8.4.
RED LED BLINKING
The Debugger is in Boot Recovery Mode.
The debugger will briefly enter this state while the firmware is being
upgraded (see chapter 8). The board might also enter this state if the
firmware is corrupt or if the user has manually forced to board to start up in
the special “boot recovery mode” (section 8.3).
To go out of the state, reset the debugger by pressing the “Reset” button
or by power-cycling the device. If the LED is still blinking, reprogram the
unit by using the Flash Programmer Application.
RED LED ON
No device detected. This might be due to old firmware on the CC
Debugger. New devices might not be supported with the current firmware
on the debugger. Please refer to chapter 8 for the firmware upgrade
procedure.
There might also be a problem with the hardware connection. Check the
connection to device and make sure the target board is properly powered
and that Vdd on the target board is connected to pin 2 on the debug
connector. Press and release the reset button to retry the target device
detection
GREEN LED ON
The target device has been properly detected. It is possible to start using
the supported tools (see chapter 5.2).

SWRU197F
June 2013
14/23
8 Updating the Firmware
In order to make sure the CC Debugger works seamlessly with your device, it is important that it has
the latest and greatest firmware. This chapter will describe how you can upgrade the firmware
automatically from SmartRF Studio or manually from SmartRF Flash Programmer. The chapter will
also describe how to resurrect a seemingly broken debugger.
8.1 Updating the firmware automatically in SmartRF Studio
Updating the firmware on the CC Debugger can be done automatically by SmartRF Studio. Please
follow the few steps described below.
1. Start SmartRF Studio.
2. Disconnect the debugger from any target board, and connect it to the PC via the USB cable.
The debugger will appear in the list of connected devices in the lower part of the SmartRF
Studio startup panel.
Figure 13 - Auto FW upgrade
3. Double click on the item in the list, and a new window will appear.

SWRU197F
June 2013
15/23
Figure 14 - Auto FW upgrade
4. Click "Yes" and let SmartRF Studio do the rest.
Figure 15 - Auto FW upgrade
5. Click "Done" and you're good to go. The device should appear in the list of connected devices,
now showing the new firmware revision.

SWRU197F
June 2013
16/23
8.2 Updating the firmware manually in SmartRF Flash Programmer
You can also update the firmware manually using SmartRF Flash Programmer. You can use this
method if you like to have full control of the firmware image to be programmed on the controller of the
debugger (i.e. programming custom firmware or old firmware revisions).
1. Start SmartRF Flash Programmer and select the tab called “EB application (USB)”. This tab
will let you program compatible firmware on the CC Debugger (or evaluation boards) via the
USB interface (i.e. no external programming device required).
2. Disconnect the debugger from any target board, and connect it to the PC via the USB cable.
The debugger will appear in the list of connected devices. Chip type will be listed as N/A.
3. Select the flash image you want to program on the debugger. Normally, you would select:
C:\Program Files (x86)\Texas Instruments\SmartRF Tools\Firmware\CC
Debugger\cebal_fw_srf05dbg.hex
1
4. Select the action “Erase, program and verify”
5. Click the “Perform actions” buttons. The programming procedure will start. Note that this will
take several seconds.
6. The CC Debugger will reappear in the list of connected devices, now showing the new
firmware revision in the device list.
7. Done!
1
Assuming default installation path of SmartRF Flash Programmer.
1
1
2
4
5
3

SWRU197F
June 2013
17/23
8.3 Forced boot recovery mode
If, for some reason, the firmware update fails and the CC Debugger appears to be non responsive,
there is a way to force the board to only run the bootloader and stop all further execution. In this mode,
no attempts will be made to start the firmware, and the board will only allow the user to perform a new
firmware upgrade over USB.
Disconnect the debugger from any power source and open the plastic enclosure.
Figure 16 - Internal view of CC Debugger
Short circuit the pins as depicted in Figure 17: P1.6 on the CC2511 must be connected to GND during
the power-on reset to enter boot recovery mode.
Figure 17 - Short-circuit pins for boot recovery mode
When reconnecting the USB cable, the LED will start to blink with a RED light. This indicates that the
bootloader is running and that the debugger is in boot recovery mode.
At this point, follow the same firmware programming steps as describe at the beginning of this chapter.
Please also note that the boot recovery mode can be used as a check to verify that the bootloader on
the debugger is working.
8.4 Resurrecting the CC Debugger
If the CC Debugger appears to be completely dead when applying power, there is a way to “unbrick”
the board. The method consists of reprogramming the bootloader on the debugger using the debug
connector inside the box. This will require an extra programming device.
When opening the box, locate the debug connector header next to the target connector. Connect this
header to another CC Debugger (see Figure 18) or to a SmartRF05EB (see Figure 19). When using

SWRU197F
June 2013
18/23
SmartRF05EB, connect a 10-pin flat cable from the “Ext SoC Debug” plug (P3) on the EB to the “USB
Debug” plug (P2) on the CC Debugger. The dead debugger needs power, so connect the USB cable.
Turn on the SmartRF05EB or debugger - it should detect the USB Controller (CC2511) on the
debugger.
Figure 18 - Programming the bootloader on the CC Debugger using another CC Debugger
Figure 19 - Programming the bootloader on the CC Debugger using SmartRF05EB
Next, use the SmartRF Flash Programmer to program the bootloader on the debugger. Follow these
five steps (illustrated in Figure 20 below):

SWRU197F
June 2013
19/23
1. After starting the application, first select “Program Evaluation Board” in the “What do you want
to program?” drop down box, then select the “EB Bootloader” tab.
2. In the upper left corner, select device: Use SmartRF05EB regardless of the device being used
to program the debugger. I.e. select SmartRF05EB both when you are using a CC Debugger
and when you are using a SmartRF05EB for the resurrection.
3. Next, select which flash image to program. The bootloader image is included when installing
the flash programmer and it is usually located at “C:\Program Files (x86)\Texas
Instruments\SmartRF Tools\Firmware\CC Debugger”.
4. It is also necessary to give the debugger a unique ID number –any 4 digit number will work.
This number is used by the driver on the PC to uniquely identify devices if more than one
debugger is connected at the same time.
5. Select “Erase, program and verify”
6. Press the “Perform Actions” buttons. The firmware upgrade takes a few seconds.
Figure 20 - SmartRF Flash Programmer - Updating the bootloader
Once the bootloader is programmed, you might be asked to install a USB driver on the PC. Just follow
the same procedure as when the debugger was connected to the PC the first time (see chapter 5).
The RED LED on the debugger should now be blinking, indicating that the bootloader is running but
that no application has been loaded. If the RED LED is off, there is probably something wrong with the
hardware. The debugger firmware can now be programmed directly over USB by following the
procedure in either chapter 8.1 or 8.2.
1
1
2
4
5
6
3

SWRU197F
June 2013
20/23
9 Troubleshooting
Q1 Help! The debugger does not detect the SoC. What should I do?
A1 There are several things to check.
Upgrade the firmware. Many CC Debuggers have old firmware that will not automatically
detect newer devices, like CC2543/44/45. Refer to chapter 8 for further instructions.
Check that the cable is oriented correctly and that the pins are connected to the right signals
on the debugger.
Check that the debugger gets power from the target (i.e proper connection of the Target
Voltage Sense signal). This is required in order for the level converters on the debugger to
work.
Check that ground on the target is connected to ground on the debugger. This is normally
achieved through the target connector. Note that since the ground planes are the same, please
be aware of any adverse effects caused by different ground planes on the target and on the
PC (grounded via USB cable).
Check that the cable is not broken. Especially the small flat cable is prone to stop working if
handled a lot or being bent and stretched beyond normal operating conditions.
Q2 Does IAR EW8051 support the CC Debugger as debugging device?
A2 Yes –but make sure you have an up to date version of IAR with the new debug driver plug-in
from Texas Instruments. You will need version 7.51A or higher.
Q3 Can the debugger be used as an interface to the RF device for packet sniffing?
A3 Yes, this is supported for selected devices. Use the same interconnection as in the diagrams in
chapter 6.
Q4 Is there a way to remove the plastic casing without damaging it?
A4 Yes, there is. Hold the bottom piece of the plastic in one hand. With your other hand, take a
firm grip on the long lateral sides of the upper part of the plastic and squeeze while moving the
upper part away from the bottom. The two parts should separate from each other.
To reassemble the plastic, just click the two pieces together.
Q5 Is this a Mini or a Micro USB plug?
A5 Mini USB type A.