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-CC26X2R1: program problem Error -2134 with new launchpad kit

Part Number: LAUNCHXL-CC26X2R1
Other Parts Discussed in Thread: UNIFLASH

Tool/software: Code Composer Studio

Hello,

This week I received the development kit LAUNCHXL-CC26X2R1. 
It was deliverd with ProjectZero. 

Now I like to debug the same example project.
Building the project works without any error.

Debuging will give error -2134.
Also when I try to flash by Uniflash tool. This will give the same error. I tried to program the prebuild hex file "project_zero_unsecure_app.hex"

12-9-2019 16:17:12] [INFO] Cortex_M3_0: GEL Output: Memory Map Initialization Complete.
[12-9-2019 16:17:13] [INFO] Cortex_M4_0: GEL Output: Memory Map Initialization Complete.
[12-9-2019 16:17:14] [INFO] Cortex_M4_0: GEL Output: Board Reset Complete.
[12-9-2019 16:17:15] [ERROR] 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 8.2.0.00004)
[12-9-2019 16:17:15] [ERROR] Cortex_M4_0: File Loader: Memory write failed: Target failed to read 0x20000B34
[12-9-2019 16:17:21] [ERROR] 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 8.2.0.00004)
[12-9-2019 16:17:22] [ERROR] Cortex_M4_0: Unable to determine target status after 20 attempts
[12-9-2019 16:17:22] [ERROR] 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 also removed the jumpers and connect programming in/out connector with a cable. Then I get the same error.
The XDS110 is allready updated.
See below output of 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.2
Manufacturer: Texas Instruments
Serial Num: L1100B9F
Mode: Runtime
Configuration: Standard

Found 1 device.

Anyone knows what could be the problem?