• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 375 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: error 1170 and 2134

M S2
Intellectual 580 points
Part Number: CC2640R2F

Tool/software: Code Composer Studio

Hello

I have cc2640r2f

My program is simple peripheral in CCS

It was working fine. But the next time I debugged the program it gave error 1170 and 2134:

Cortex_M3_0: GEL Output: Memory Map Initialization Complete.
Cortex_M3_0: GEL Output: Board Reset Complete.
Cortex_M3_0: Can't Run Target CPU: (Error -2134 @ 0x0) Unable to control device execution state. 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 8.4.0.00006)
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 8.4.0.00006)

I searched in the forum and I did every solution they had, like changing TCLK to 1MHz, 2MHz, 2.5MHz and mass erasing  in flash programmer 2 and waiting fr module to get cold again. I also checked the hardware and it was OK (It is just HM-17 module)

I really don't know what else to do. Can you help me please.

  • 0
    Intellectual 580 points

    I want to add the configuration test. It is attached.

    I am using XDS110

    test config.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    50
    51
    52
    53
    54
    55
    56
    57
    58
    59
    60
    61
    62
    63
    64
    65
    66
    67
    [Start: Texas Instruments XDS110 USB Debug Probe]
    Execute the command:
    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity
    [Result]
    -----[Print the board config pathname(s)]------------------------------------
    C:\Users\win_10\AppData\Local\TEXASI~1\CCS\
    ccs930\0\0\BrdDat\testBoard.dat
    -----[Print the reset-command software log-file]-----------------------------
    This utility has selected a 100- or 510-class product.
    This utility will load the adapter 'jioxds110.dll'.
    The library build date was 'Nov 25 2019'.
    The library build time was '16:55:29'.
    The library package version is '8.4.0.00006'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '5' (0x00000005).
    The controller has an insertion length of '0' (0x00000000).
    This utility will attempt to reset the controller.
    This utility has successfully reset the controller.
    -----[Print the reset-command hardware log-file]-----------------------------
    The scan-path will be reset by toggling the JTAG TRST signal.
    The controller is the XDS110 with USB interface.
    The link from controller to target is direct (without cable).
    The software is configured for XDS110 features.
    The controller cannot monitor the value on the EMU[0] pin.
    The controller cannot monitor the value on the EMU[1] pin.
    The controller cannot control the timing on output pins.
    The controller cannot control the timing on input pins.
    The scan-path link-delay has been set to exactly '0' (0x0000).
    -----[Perform the Integrity scan-test on the JTAG IR]------------------------
    This test will use blocks of 64 32-bit words.
    This test will be applied just once.
    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.
    The JTAG IR Integrity scan-test has succeeded.
    -----[Perform the Integrity scan-test on the JTAG DR]------------------------
    This test will use blocks of 64 32-bit words.
    This test will be applied just once.
    Do a test using 0xFFFFFFFF.
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to M S2
    TI__Guru**** 170084 points

    Hi,

    Thanks for sending a detailed post. A description of the error and additional tips for troubleshooting can be found at the Debugging JTAG page - just search for the error number. 

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

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 580 points

    Thanks for your reply Rafael.

    I tried to mass erase in Flash programmer 2 as it is mentioned as a troubleshoot.

    Flash programmer always wants to update and if not, it doesn't work. So I updated it but it didn't erase it. It said debug is locked

    So I didn't know what to do

    I tried to run it again in CCS so that it doesn't give the errors again. But it also needed to update. So I updated it and suddenly the green LED turned off. I disconnected the cable but the debugger didn't work again. Is it broken?

    Please tell me what to do. Thank you very much.

  • 0 in reply to M S2
    Intellectual 580 points

    I fixed it whith some cmd codes.

    Thank you Rafael