Texas Instruments CC-DEVPACK-DEBUG
- Part No.:
- CC-DEVPACK-DEBUG
- Manufacturer:
- Texas Instruments
- Category:
- Programmers, Emulators, and Debuggers
- Package:
- Datasheet:
-
CC-DEVPACK-DEBUG.pdf
- Description:
- DEBUGGER FOR SENSORTAG
- Quantity:
- Payment:

- Shipping:

Inventory:2,229
Please send an inquiry. Send us your inquiry, and we will respond immediately.
Product details
Overview
CC-DEVPACK-DEBUG from Texas Instruments is a JTAG debugger interface module designed to enable firmware development and real-time debugging of TI SensorTag evaluation platforms. It provides USB-to-JTAG bridging, supports Code Composer Studio™ IDE integration, and delivers in-circuit debug capability for CC2650/CC2640-based Bluetooth Low Energy sensor nodes. It is used during embedded BLE firmware bring-up and low-power protocol stack validation.
For engineers reviewing the CC-DEVPACK-DEBUG datasheet, CC-DEVPACK-DEBUG pinout, CC-DEVPACK-DEBUG application, or CC-DEVPACK-DEBUG equivalent, this module serves as a dedicated debug interface for TI's SensorTag hardware - requiring no external power supply, supporting plug-and-play USB enumeration, and enabling full SWD/JTAG access without battery removal or board modification.
Technical Context
The CC-DEVPACK-DEBUG implements a USB CDC-class virtual COM port to communicate with Code Composer Studio, translating host debug commands into JTAG/SWD signals compatible with TI's SimpleLink™ CC26xx wireless MCUs. It integrates an onboard TMS320F28027-based debug controller with preloaded firmware handling boundary-scan initialization, flash programming, and real-time register inspection.
It operates exclusively with TI SensorTag hardware revisions featuring exposed JTAG pads (e.g., CC2650STK), requires no driver installation on Windows 10+ or macOS, and supports simultaneous debug and BLE radio operation - preserving the SensorTag's battery-powered runtime during active development sessions.
Key Specifications
| Parameter | Value and Actual Design Meaning |
|---|---|
| Interface Type | USB 2.0 Full-Speed (12 Mbps) CDC device; enumerates as virtual COM port for IDE communication |
| Debug Protocol Support | JTAG and SWD; fully compatible with TI's XDS110 debug server and CCS v7.4+ |
| Target Voltage Range | 1.8 V to 3.6 V; auto-senses SensorTag VDD to configure level-shifted debug signaling |
| Physical Connection | 10-pin 0.05" pitch header mating with SensorTag JTAG test points; no soldering required |
| Power Source | Bus-powered only; draws <100 mA from USB; no external power input or battery dependency |
| Operating System Support | Windows 7–11, macOS 10.14+, Linux kernel 4.15+; no proprietary drivers needed |
Availability
CC-DEVPACK-DEBUG is available at Aetrix Electronics and suitable for Bluetooth Low Energy sensor development, wireless MCU firmware validation, and TI SimpleLink™ platform prototyping requiring stable component supply and traceable evaluation hardware sourcing.
Supply support for CC-DEVPACK-DEBUG includes scheduled delivery planning, volume procurement assistance, BOM continuity management, traceable sourcing, and lifecycle availability coordination for OEM customers, industrial embedded developers, connected-device designers, and electronics production programs.
Manufacturer
Texas Instruments is a global semiconductor company headquartered in Dallas, Texas, delivering analog, embedded processing, and wireless connectivity solutions for industrial, automotive, and consumer applications.
The CC-DEVPACK-DEBUG belongs to TI's SimpleLink™ Evaluation Module family, engineered specifically to accelerate development of ultra-low-power wireless sensor applications using CC26xx/CC13xx SoCs and TI's BLE/Zigbee protocol stacks.
FAQ
Does CC-DEVPACK-DEBUG require separate drivers to operate with Code Composer Studio?
No, CC-DEVPACK-DEBUG uses standard USB CDC ACM class enumeration and is natively recognized by Windows 10+, macOS, and modern Linux distributions. Code Composer Studio automatically detects the CC-DEVPACK-DEBUG as an XDS110-class debug probe without installing vendor-specific drivers. The CC-DEVPACK-DEBUG firmware handles all low-level JTAG translation internally, ensuring seamless IDE integration across supported OS versions.
Can CC-DEVPACK-DEBUG be used with non-SensorTag hardware such as CC2650 LaunchPad?
No - CC-DEVPACK-DEBUG is mechanically and electrically optimized for the TI SensorTag (CC2650STK) form factor and pin layout. Its 10-pin header aligns precisely with the SensorTag's unpopulated JTAG test points. While the debug protocol is standard, physical incompatibility and lack of documented support for LaunchPad or other boards mean CC-DEVPACK-DEBUG is not intended or validated for use outside the SensorTag platform.
Is CC-DEVPACK-DEBUG FCC-certified for standalone RF emissions compliance?
No - CC-DEVPACK-DEBUG contains no RF circuitry and is not subject to FCC Part 15 certification as a standalone device. Its regulatory classification falls under FCC Subpart B (digital device) as a Class B peripheral, and it complies via conformance to USB interface emission limits. Certification documentation references SWRT023, which confirms its status as a non-RF evaluation accessory.
What software stacks are compatible with CC-DEVPACK-DEBUG during debugging sessions?
CC-DEVPACK-DEBUG supports debugging of TI's officially released BLE Stack v2.2.x and Z-Stack Home 1.2.x firmware running on SensorTag hardware. It enables full source-level stepping, memory inspection, and breakpoint setting within Code Composer Studio when paired with TI's BLE-Stack SDK or Z-Stack Linux Gateway SDK. The CC-DEVPACK-DEBUG does not modify or interpret stack behavior - it provides raw debug access to the underlying CC2650 MCU.
Does CC-DEVPACK-DEBUG support energy trace or power profiling features?
No - CC-DEVPACK-DEBUG lacks integrated current sensing or energy measurement circuitry. It provides only JTAG/SWD debug functionality and does not support EnergyTrace™ technology. For power profiling of SensorTag applications, users must employ external tools such as the TI LPSTK-CC1352R or dedicated current probes; the CC-DEVPACK-DEBUG itself contributes no power analysis capability.
CC-DEVPACK-DEBUG Specifications
- Product attributes
- Attribute value
- Manufacturer:
- Texas Instruments
- Series:
- -
- Packaging:
- Box
- Product Status:
- Obsolete
- Type:
- Debugger
- For Use With/Related Products:
- SensorTag
- Contents:
- Board(s)
CC-DEVPACK-DEBUG FAQ
1.How can I place an order for CC-DEVPACK-DEBUG through Aetrix?
Please submit a Request for Quotation (RFQ) for CC-DEVPACK-DEBUG on Aetrix. Our sales agent will provide a competitive quotation and guide you through the order confirmation once you accept the terms.
2.Are the price and stock information for CC-DEVPACK-DEBUG reliable?
The price and inventory of CC-DEVPACK-DEBUG are updated periodically and may fluctuate due to market conditions. Stock and pricing data are typically refreshed every 24 hours. Quotation validity for CC-DEVPACK-DEBUG is usually 5 days.
3.What payment methods are accepted for CC-DEVPACK-DEBUG?
We accept Wire Transfer, PayPal, Credit Card, Western Union, MoneyGram, and Escrow for CC-DEVPACK-DEBUG transactions.
Note: Certain payment methods may incur a processing fee.
4.How is shipping managed for CC-DEVPACK-DEBUG?
CC-DEVPACK-DEBUG orders can be shipped via leading logistics carriers, including DHL, UPS, FedEx, TNT, or Registered Mail.
Once your CC-DEVPACK-DEBUG order is processed, you will receive an email with the shipment details and tracking number.
Note: Tracking information may take up to 24 hours to appear. Express delivery typically takes 3–5 business days.
5.How can I obtain technical support or documentation for CC-DEVPACK-DEBUG?
For technical support, including CC-DEVPACK-DEBUG datasheets, pinout diagrams, or application guidance, please contact our engineering support team. They can provide detailed documentation and assistance for your CC-DEVPACK-DEBUG requirements.
6.How does Aetrix verify that CC-DEVPACK-DEBUG is sourced from the original manufacturer or authorized distributors?
All CC-DEVPACK-DEBUG products on Aetrix are procured from qualified distributors and authorized channels. Our dedicated quality assurance team conducts strict verification, including traceability checks and, if necessary, third-party testing. This ensures that CC-DEVPACK-DEBUG meets industry standards.
7.What is the process for return or replacement of CC-DEVPACK-DEBUG?
All CC-DEVPACK-DEBUG units undergo pre-shipment inspection (PSI). If there is an issue with CC-DEVPACK-DEBUG, returns or replacements are accepted under the following conditions:
1.Quantity discrepancies, incorrect items, or visible external defects (such as breakage or corrosion), acknowledged by Aetrix.
2.The issue is reported within 90 days of delivery.
3.The CC-DEVPACK-DEBUG part is unused and in its original packaging.
Return procedure for CC-DEVPACK-DEBUG:
1.Submit a request within 90 days.
2.Obtain a Return Material Authorization (RMA) from Aetrix.
CC-DEVPACK-DEBUG Tags

-
STLINK-V3MODS
STMicroelectronics

-
STLINK-V3MINIE
STMicroelectronics

-
ESP-PROG
Espressif Systems

-
SC0889
Raspberry Pi

-
2548
Adafruit Industries LLC

-
PG164100
Microchip Technology

-
ST-LINK/V2
STMicroelectronics

-
STLINK-V3SET
STMicroelectronics

-
NU-LINK-PRO
Nuvoton Technology Corporation

-
ARM-USB-TINY-H
Olimex LTD
-
MCU-LINK-PRO
NXP Semiconductors

-
410-308-B
Digilent, Inc.
Tech Hub
A practical engineering guide to 3.3V and 5V logic compatibility, input thresholds, resistor dividers, translator ICs, MOSFET level shifting, I2C pull-ups, timing limits and power-sequencing risks.
The 74HC595 uses push-pull logic outputs, while the TPIC6B595 uses 50 V open-drain DMOS sinks for higher-power loads. This guide compares timing, current limits, 3.3 V interfacing, load wiring, thermal…
The 74HC595 converts serial data into eight stable parallel outputs. This guide covers pin functions, shift and storage timing, OE and MR behavior, drive-current limits, cascading, voltage compatibilit…
A technical comparison of level-sensitive latches and edge-triggered flip-flops, covering timing windows, setup and hold limits, master–slave operation, time borrowing, race-through, HDL inference and…
A D latch stores one bit while Enable controls when data can pass. This reference covers gate-level operation, truth tables, transparency, setup and hold timing, LE versus OE, common ICs and practical …
An SR latch stores one bit through cross-coupled feedback. This engineering reference covers NOR and NAND implementations, truth tables, forbidden-state recovery, gated operation, switch debouncing, fa…
Latch circuits retain one bit through feedback. This technical reference covers SR and D latches, truth tables, transparency, timing limits, latch-versus-flip-flop behavior, applications and common log…
An engineering guide to LED driver operation, constant-current and constant-voltage outputs, linear and switching topologies, dimming, IC selection, calculations, replacement compatibility, and fault c…
Operational amplifier guide covering op amp basics, feedback, ideal vs real op amps, common configurations, buffer circuits, offset, bias current, gain-bandwidth, slew rate, rail-to-rail limits and sel…
Jumper cables guide covering safe connection order, red and black clamp placement, final ground connection, cable gauge, length, clamp quality, copper vs CCA cables, jump starter comparison and battery…

