• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 224 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/LP-CC2652RB: Debugger

Martin Overton
Prodigy 10 points
Part Number: LP-CC2652RB

Tool/software: Code Composer Studio

I just received a LP-CC2652RB and am having issues in Code Composer.

I'm running Windows 10 as a development platform.

I've download and installed the more recent version of Code Composer Studio - Version 10.1.0.00010

I've imported portable_CC26X2R1_LAUNCHXL_tirtos_gcc, which builds wih no issues.

When I try to start the debugger the last thing I see on in the console window is

Cortex_M4_0: GEL Output: Memory Map Initialization Complete.
Cortex_M4_0: GEL Output: Board Reset Complete.

The debug console shows

The red and green LED's are both illuminated.

At this point everything freezes and I have to close CCS.

At one point I got a message directing me to examine the device. The following is what I saw

C:\ti\ccs1010\ccs\ccs_base\common\uscif\xds110>xdsdfu -e

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...


<<<< Device 0 >>>>

VID: 0x0451 PID: 0xbef3
Device Name: XDS110 Embed with CMSIS-DAP
Version: 3.0.0.13
Manufacturer: Texas Instruments
Serial Num: L12000VB
Mode: Runtime
Configuration: Standard

Found 1 device.

Thanks for any input.

  • 0
    TI__Guru**** 168377 points

    Hi,

    Unfortunately the screenshot did not go through, but I tested my LP-CC2652RB and it worked well, therefore ruling something intrinsic to the tools themselves.

    If you are launching your debugger from a project, can you try to instead do a Manual Launch? This usually helps workaround any issues with the code itself that may be causing a delay or a lockup on CCS. Details about the Manual Launch can be found at section 7.3.2 of the CCS User's Guide at:

    https://software-dl.ti.com/ccs/esd/documents/users_guide/index.html

    That should help uncover a few additional details about the issue. You can also try to run the "Test Connection" button and see if there are any issues with the communications between the XDS110 Debug Probe and the device (the output of the xdsdfu.exe utility tells me things are ok between the host and the XDS110 Debug Probe). 

    Hope this helps,

    Rafael