• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 21 subscribers
  • Views 2499 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/CC2640R2F: Unable to debug in CCS 7.2

erdem simsek
Expert 2165 points
Part Number: CC2640R2F

Tool/software: Code Composer Studio

Hi,

I am using CC2640R2 launchpad as debugger to load and debug program in custom board.
My CCS version is 7.2.0.00013 and i am using simplelink sdk 1.35.

Before a few weeks ago, i can debug the program very well.
At the beginning of this week, i was getting errors and ı am nearly unable to debug the code.
I used same custom board and debugger for all time.

When i press the Debug button, i got the following errors.

Cortex_M3_0: File Loader: Memory write failed: Timed out waiting for target flashloader to execute command.
Cortex_M3_0: GEL: File: deneme.out: Load failed.

When i got these errors, i am doing these steps to load program to board and debug.

  • View/Target Configurations
  • Opening CC2640R2F.ccxml
  • Selecting advanced option on the bottom line
  • Clicking the CC2640R2F in All connections panel
  • Then, press debug 
  • Right click on Texas Instruments XDS110 USB Debug and  click the connect the target in Debug panel as shown in pciture
  • Press Load button on the upper panel and select the firmware to load
  • Loaded successfully.

I inserted breakpoint to program.

Cortex_M3_0: JTAG Communication Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.628.3) 

I got these error so much and so frequently. This is also happening TI provided examples.

I tried with disabling POWER_SAVING. However, nothing changes.
I am open to any suggestion and help.

Thanks for your attention

  • 0
    Guru 735455 points
    Try to use Flash Programmer 2 to do mass erase first and try CCS again.
  • 0 in reply to YiKai Chen
    Expert 2165 points
    Hi Yikai,

    I did your suggestion however, i got same errors.

    Cortex_M3_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.628.3)
    Cortex_M3_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.628.3)
    Cortex_M3_0: JTAG Communication Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.628.3)

    i am using separate image configuration.
    Before debug, i load stack hex file to mcu and then i am starting debug session.
    Is this way wrong ?

    Thanks
  • 0 in reply to erdem simsek
    Guru 735455 points
    Try to replace a new USB cable to test again.
  • 0 in reply to YiKai Chen
    TI__Guru**** 317180 points
    With CCS you don't need to do it in two steps. If you press the debug button (looking like a beetle) the hex file generated by the build phase will be uploaded to the target.

    With flash programmer 2, are you able to read back the flash content without any issues? Since you get this problem a bit on and off it could be a good idea to also try a different cable as YK suggests since it could be caused by poor connection.
  • 0 in reply to TER
    Expert 2165 points
    Hi TER,

    I removed the dependency to the stack project. Because of that, i am loading the stack hex file manually.

    I checked the cable, there is no problem on cable.
    Hex files are fine.
    Project works fine by loading firmware via Smart Flash Programmer 2.
    When it comes to debug, I cannot debug.
    When i set a breakpoint inside the simpe_peripheral file. it gives the error message that i wrote above.

    Thanks
  • 0 in reply to erdem simsek
    TI__Genius 12900 points

    My understanding is that you have problems debugging a board on an external target. Do you see the same problem if you try to debug the CC2640R2F on your LaunchPad?

    TIABO

  • 0 in reply to TIABO
    Expert 2165 points
    Hi Tiabo,

    I tried on launchpad. When the code hits breakpoint, after the 3-5 seconds the debugger gives error.
    Error message;
    Cortex_M3_0: JTAG Communication Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.628.3)

    Thanks
  • 0 in reply to erdem simsek
    TI__Mastermind 23730 points
    Hi Erdem,

    Are you still having this issue?
    I'm still curious on what your code does. Can you try again debugging on the LaunchPad?
  • 0 in reply to Severin Suveren
    Expert 2165 points
    Hi Edvard,

    I solved my problem. I forget the close the issue.
    The problem occurred because of debugger usb port.
    Now i fixed my issue. Thanks for your interest.
  • 0 in reply to erdem simsek
    Prodigy 35 points

    hi it seems I have the same issue,can you tell me how do you fix this issue,please give me some advice.

  • 0 in reply to mikoto misaka
    TI__Mastermind 23730 points
    Hi Mikoto,

    What is your setup, namely what device are you using, CSS version, and SDK version? Also, can you try double-check you have a proper connection, do a Mass Force Erase of the device, reprogram the device and try debugging again? Also, try to use a different USB-port?