Texas Instruments SWRU197E User manual

CC Debugger
User’s Guide
SWRU197E

swru197e
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

swru197e
3/23
1 Introduction
The CC Debugger is primarily used for debugging and programming the flash on CCxxxx 8051-based
System-on-Chip (SoC) devices from Texas Instruments. The PC tools available for these purposes are
the SmartRF™ Flash Programmer from Texas Instruments and IAR Embedded Workbench® for 8051
from IAR Systems.
When connected to the debugger, the SoC devices can be controlled directly from SmartRF™ Studio.
SmartRF Studio will also be able to control supported CCxxxx RF transceivers (CC2520, CC112x, and
CC11xL) 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.
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

swru197e
4/23
3 Box Contents
1 CC Debugger
1 USB-A to Mini-B USB cable
1 10-pin flat cable with 2x5 2.54 mm connector
1 10-pin flat cable with 2x5 1.27 mm connector
1 Converter board 2.54mm –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 draw (*): 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

swru197e
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
PurePath Wireless Configurator http://www.ti.com/tool/purepath-wl-cfg
Alternatively, you can download “Cebal –CCxxxx Development Tools USB Driver for Windows x86
and x64”[3] 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”[4].
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
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.

swru197e
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. A suggested matching (male) surface mounted
connector would be 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. A
suggested matching (male) surface mounted connector would be STL21-A01VXX from MPE Garry.
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

swru197e
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.

swru197e
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. 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.
The DD signal should be connected to pin P2.2 and DC to pin P2.1 on the SoC –with the exception of
CC2544, where DD is on P1.3 and DC on P1.2. Please refer to the device data sheets for details on
the pin-out.
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
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.

swru197e
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
Note that the packet sniffer will overwrite the flash of the SoC with special packet capture firmware.
Note concerning the SPI interface to the SoC
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
-
-
-
supported
CC253x/CC254x
-
-
-
supported
CC111x
supported
-
-
supported
CC251x
supported
-
-
supported
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.

swru197e
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:
CC1120
CC1121
CC1125
CC1175
CC110L
CC113L
CC115L
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 7 - CC Debugger connected to CC2520