• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 566 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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/LAUNCHXL-CC1352P: Cortex_M4_0: Can't Run Target CPU: (Error -2134 @ 0x0)

Timothy Murtaugh
Expert 1475 points

Part Number: LAUNCHXL-CC1352P

Tool/software: Code Composer Studio

Hello,

I have several CC1352P-2 LaunchPads, Simplelink_cc13x2_26x2_sdk version 4.20.0.35. I have a ZED, ZR and ZC based on the zed_sw, zr_sw and zc_light example projects respectively.

My problem is the ZC "freezes" and the ZR and ZED can no longer send messages to it. If I reset the ZC, all three start working again until the ZC freezes again. This happens fairly often so I've attempted to catch the problem by running the ZC in the debugger. It runs great for awhile but eventually I get this error in the CCS console

Cortex_M4_0: GEL Output: Memory Map Initialization Complete.
Cortex_M4_0: GEL Output: Board Reset Complete.
Cortex_M4_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 9.2.0.00002)
Cortex_M4_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 9.2.0.00002)
Cortex_M4_0: Unable to determine target status after 20 attempts
Cortex_M4_0: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

I actually observed this error as it happened once. I was watching the debugger output in the CCS console (I have several printfs in my code) and all was going well when suddenly the error occurred. I had hoped I could look at the debugger output to determine what was happening at the time, but unfortunately when this error occurs the console is cleared and is replaced by the error above, so all my printf output is lost.

I've googled this error but I didn't find anything useful. What is error -2134 and what causes it? Is there a list of error codes somewhere?

Any help you can provide would be greatly appreciated. We are designing Zigbee devices using the CC1352P, and this error is a show stopper, so I really need to fix.

Tim