• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 83 subscribers
  • Views 166 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.

LAUNCHXL-F280049C: how to solve -1015 error?: Debugging Connection Randomly Fails and Recovers

EunSeob Oh
Prodigy 10 points
Part Number: LAUNCHXL-F280049C

Tool/software:

C28xx_CPU1: Error connecting to the target: (Error -1015 @ 0x0) Device is not responding to the request. Device may be locked, or the debug probe connection may be unreliable. Unlock the device if possible (e.g. use wait in reset mode, and power-cycle the board). If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 20.0.0.3178)

I'm experiencing an issue with my LAUNCHXL-F280049C board using the onboard XDS110 USB debugger with Code Composer Studio (CCS) version 12.8.1. Here is a detailed description of the problem:

Issue Description:

  • Initially, I encountered Error -1015: Device is not responding to the request when trying to debug my F280049C device. The complete error message is:
    "(Error -1015 @ 0x0) Device is not responding to the request. Device may be locked, or the debug probe connection may be unreliable. Unlock the device if possible (e.g. use wait in reset mode, and power-cycle the board)."

  • After some time without any intervention, the issue resolved by itself, and I was able to debug normally.

  • Later, the same error occurred again without any changes in the setup, code, or CCS configuration.

  • The problem seems to occur randomly. It sometimes allows debugging, and other times it shows the Error -1015 again.

Setup Information:

  • Board: LAUNCHXL-F280049C

  • Debugger: Onboard XDS110

  • CCS Version: 12.8.1

  • Power Source: USB-powered from PC

  • Boot Mode: GPIO24 and GPIO32 set to Flash Boot (1,1)

  • Code/Project: I used the default launchxl_ex1_f280049c_demo project without any modification.

  • Linker File (.cmd): Configured for RAM-only execution (no Flash access). No DCSM (Dual Code Security Module) settings, no unlock registers modified.

  • No Flash API was used, and I did not manually program the Flash.

  • The device was working fine earlier, but the error appeared without any significant change.

Troubleshooting Attempts:

  • Tried power-cycling the board multiple times.

  • Reconnected the debugger and changed the USB cable.

  • Verified the Boot Mode settings (Flash Boot: 1,1).

  • Checked the CCS target configuration for XDS110 (set to 2-pin cJTAG mode).

  • No other code changes, Flash programming, or DCSM-related operations were performed.

Observations:

  • The issue seems to resolve itself after some time without any action.

  • It then reoccurs again randomly, making debugging unreliable.

  • The device sometimes responds to JTAG commands and allows debugging, but at other times it doesn't.

  • I did not perform any reset, re-flash, or configuration change between the problem occurring and resolving.

Questions:

  1. What could cause the device to recover by itself from Error -1015 without any user action?

  2. Could this be related to a watchdog timer, Boot ROM behavior, or JTAG TAP state automatically recovering?

  3. Are there any other known conditions where Error -1015 can appear and disappear randomly?

  4. Would using Wait-in-Reset mode or other Boot modes help with this issue?

I would appreciate any insights or troubleshooting suggestions.

Thank you.