CC Debugger User's Guide Literature Number: SWRU197H September 2010 – Revised April 2014
Contents 1 2 3 4 5 6 Introduction ......................................................................................................................... Abbreviations and Acronyms ................................................................................................ Box Contents....................................................................................................................... Operating Conditions of the CC Debugger ..........................................................
www.ti.com List of Figures 1 Verify Correct Driver Installation ........................................................................................... 6 2 Placement of Target Connector Pins...................................................................................... 7 3 Placement of Target Connector Pins on Adapter Board 4 Target Connector Pin-Out ..................................................................................................
User's Guide SWRU197H – September 2010 – Revised April 2014 CC Debugger 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].
Abbreviations and Acronyms www.ti.
Initial Steps www.ti.com 5 Initial Steps 5.
Connecting the CC Debugger to the Device www.ti.com 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. Pin 1 Pin 2 Figure 2. Placement of Target Connector Pins The adapter board, which has a 10-pin 2x5 1.
Connecting the CC Debugger to the Device www.ti.com Target Voltage Sense GND 1 2 3 4 5 6 7 8 9 10 DC (Debug Clock) DD (Debug Data) Csn (SPI Chip Select) SCLK (SPI Clock) MOSI (SPI Data Out) RESETn 3.3V (from debugger) MISO (SPI Data In) Figure 4. Target Connector Pin-Out 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.
Connecting the CC Debugger to the Device www.ti.com Vdd CC Debugger Connector NOTE 1 Vdd 10 kΩ Vdd CCxxxx System-on-Chip GND 3.3 V from debugger. Can optionally be used to power the target board 2 3 4 5 6 7 8 9 10 DC (Debug Clock) P2.2 P2.1 DD (Debug Data) SoC 2.7 kΩ RESETn RESETn 1 nF 1 NOTE 2 GND Figure 6.
Connecting the CC Debugger to the Device 6.2.3 www.ti.com 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 (see Figure 7). Vdd Vdd CC Debugger Connector CCxxxx System-on-Chip GND 2 DC (Debug Clock) DD (Debug Data) 3 4 CSn SCLK 5 6 RESETn MOSI 7 8 9 10 P2.2 P2.1 SoC P1.7 P1.
Connecting the CC Debugger to the Device www.ti.com 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, and 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.
Connecting the CC Debugger to the Device www.ti.com Vdd CC Debugger Connector Vdd CC112x CC1175 CC120x GND 1 2 DC 3 4 CSn 5 6 GPIO2 GPIO0 CSn SCLK SI SO DD SCLK 3.3 V from debugger. Can optionally be used to power the target board RESETn MOSI 7 8 9 10 MISO GND RESETn Figure 9. CC Debugger Connected to CC112x/CC1175/CC120x Vdd CC Debugger Connector Vdd Cc110x CC11xL Cc2500 GND 1 2 DC 3 4 CSn 5 6 7 8 9 10 GDO2 GDO0 CSn SCLK SI SO DD SCLK 3.3 V from debugger.
Using the CC Debugger www.ti.com 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 immediately starts 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 Table 3.
Updating the Firmware 8 www.ti.com 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 section describes how you can upgrade the firmware automatically from SmartRF Studio or manually from the SmartRF Flash Programmer. The section also describes how to resurrect a seemingly broken debugger. 8.
Updating the Firmware www.ti.com 3. Double click on the item in the list and a new window will appear (see Figure 13). Figure 13. Auto Firmware Update 4. Click Yes (see Figure 14) and let SmartRF Studio do the rest. Figure 14. Firmware Successfully Updated 5. Click Done (see Figure 14). The device should appear in the list of connected devices, now showing the new firmware revision.
Updating the Firmware 8.2 www.ti.com Updating the Firmware Manually in SmartRF Flash Programmer You can also update the firmware manually using the SmartRF Flash Programmer (illustrated in Figure 15). 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 (for example, programming custom firmware or old firmware revisions). 1. Start the SmartRF Flash Programmer and select the EB application (USB) tab.
Updating the Firmware www.ti.com 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 are 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.
Updating the Firmware www.ti.com 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 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.
Updating the Firmware www.ti.com Next, use the SmartRF Flash Programmer to program the bootloader on the debugger. Follow these five steps (illustrated in Figure 20): 1. Start the application and select Program Evaluation Board in the What do you want to program? drop down box, then select the EB Bootloader tab. 2. In the Device box, select SmartRF05EB regardless of the device being used to program the debugger.
Updating the Firmware www.ti.com 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 Section 8.1 or Section 8.2.
Troubleshooting www.ti.com 9 Troubleshooting Table 4. Troubleshooting FAQs 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. For further instructions, see Section 8. Check that the cable is oriented correctly and that the pins are connected to the right signals on the debugger.
Schematics 10 www.ti.com Schematics For more information, see Appendix A or the complete bundle including gerber files, schematics and layout [3]. 11 References 1. CC-Debugger product web site: http://www.ti.com/tool/cc-debugger 2. CC Debugger Quick Start Guide (SWRU196) 3. CC-Debugger Layout and Schematics www.ti.com/lit/zip/swrr105 4. Cebal – CCxxxx Development Tools USB Driver for Windows x86 and x64 www.ti.com/lit/zip/swrc212 5.
www.ti.
Revision History www.ti.com Revision History Changes from G Revision (January 2014) to H Revision ............................................................................................... Page • 24 Added Windows 8 as a supported operating system in Section 4. .................................................................
IMPORTANT NOTICE Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, enhancements, improvements and other changes to its semiconductor products and services per JESD46, latest issue, and to discontinue any product or service per JESD48, latest issue. Buyers should obtain the latest relevant information before placing orders and should verify that such information is current and complete.
