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.

Error connecting to the target: (Error -1015 @ 0x0) Device is not responding to the request. Device may be locked, or the emulator connection may be unreliable.

Other Parts Discussed in Thread: TMS320F28027, UNIFLASH, CONTROLSUITE

Hi,

I am using TMS320F28027 MCU and CCS 5.4 to debug my code using Spectrum Digital XDS100v2 Emulator. The Target Configuration settings are as follows:

Connection: Texas Instruments XDS100v2 USB Emulator

Board or Device: TMS320F28027

Board Data File: auto generate

Emulator Selection: Only one XDS100 installed

The JTAG nTRST Boot-Mode: Disabled - Both EMU pins remain hi-z

The Power-On-Reset Boot-Mode: Disabled - Both EMU pins remain hi-z

The JTAG TCLK Frequency (MHz): Fixed default 1.0MHz frequency

I have my own hardware. Part of the hardware that I am working with is attached. I can program my code and debug it easily but sometimes (without no reason in my point of view) I get the following error:

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

I can not program it anymore. The MCU locks without no reason and the only solution I found was to change it.

Can anyone help me with that? Is there anything wrong with my hardware or settings? Why it works sometimes but it locks suddenly!?

Thanks,

Ali

  • Hi Ali,

    Ali Shagerdmootaab said:
    Can anyone help me with that? Is there anything wrong with my hardware or settings? Why it works sometimes but it locks suddenly!?

    Do you've frequent power failures or instances wherein the programming got halted in middle itself? Locking of devices usually occur due to interruption during flashing process. Other than that if your design engineer follows the reference TI design schematics then there should be no JTAG issue.

    This issue is for the first time or have you already replaced few ICs?

    Regards,

    Gautam

  • Hi Gautam,

    About the power failures, I did not have this issue during the programming. I am using an external power source and it works fine. It is interesting for me to know what is going on.

    I was using C2000 Piccolo LaunchPad as the MCU for my circuit. Then I decided to have the MCU on my board to have an stand alone circuit. In this way and in order to find the proper hardware to run the MCU, I decided to have the MCU and some necessary components like capacitors and resistors on a small board. Then I connected this board to the PC through a 14-pin JTAG connector and the Digital Spectrum Emulator. During the process of finding proper hardware for the MCU and also JTAG connector, I had this issue of locking the MCU 3-4 times and I replaced the IC. At the end, I concluded to the hardware that I attached and it worked fine. I did not have the power supply failures to halt the programming.

    Now, I have my whole circuitry including the MCU, JTAG, and the power converter (in this case flyback converter) on the same board. I was and am able to flash it properly and it works fine. But in this stage, I replaced the IC 3 times. I connect my board to an external power source and its JTAG to the PC. The first IC failed (short circuit between Vcc and GND not locked) I think because I disconnected the power source from MCU without disconnecting the JTAG.The second IC was locked that I do not know why. I put the 3rd IC after my previous post and it works now.

    After this long story and all these experiences, do you think there should be any priority between disconnecting the MCU's power supply and its JTAG connector that is connected to the PC through USB?

    For disconnecting the emulator, do you think I have to disconnect the 14-pin connector from the board or disconnect it from the USB cable because it is hot plugged?

    From now on for shutting down the circuit, I decided to first disconnect the USB cable of the emulator from the PC and then turn off the power supply. On the other hand, for turning the circuit on, first I turn on the power supply and then connect the USB cable of the emulator. Do you think this is a safe way?

    Thanks for your help,

    Ali

  • Ali Shagerdmootaab said:

    After this long story and all these experiences, do you think there should be any priority between disconnecting the MCU's power supply and its JTAG connector that is connected to the PC through USB?

    For disconnecting the emulator, do you think I have to disconnect the 14-pin connector from the board or disconnect it from the USB cable because it is hot plugged?

    From now on for shutting down the circuit, I decided to first disconnect the USB cable of the emulator from the PC and then turn off the power supply. On the other hand, for turning the circuit on, first I turn on the power supply and then connect the USB cable of the emulator. Do you think this is a safe way?

    Ali, the pattern should not matter at all. Just you've to take care that while programming the emulator disconnection should not happen. Other than that, also try avoiding the removal of debugger while in running stage.

    Regards,

    Gautam

  • Hi Gautam,

    As I remember, I removed the debugger while it was running and that might be the reason for the MCU to be locked. I try to avoid this to happen and it still works fine.

    Thanks,

    Ali

  • Ali Shagerdmootaab said:
    As I remember, I removed the debugger while it was running and that might be the reason for the MCU to be locked. I try to avoid this to happen and it still works fine.

    Fine, do let me know if you need any further help.

    Regards,

    Gautam

  • i want to know how to unlock my board? it is locked?i have used uniflash to unlock it,but it is no use
  • If mcu got disconnected from debugger while erasing... its in permanent lock condition and recovering the same is not possible. You'll have to replace the part itself.
    Did you input csm password to lock it?
  • i don't input passwd to lock it。when i first to connect it,the error show the device is locked。
  • This means we've to rule out locking for now and check if there's some other issue. Can you try one experiment? Try loading .out file from any example code to mcu through SCI. Refer the usage document and software present here :
    C:\ti\controlSUITE\device_support\~Utilities\serial_flash_programmer
    This will clear whether the device is locked or not.

    Regards,
    Gautam
  • thanks,i will try。
  • Keep us updated. Simply follow the steps correctly.
  • hi,i can't find f28033_sci_flash_kernels_cpu.txt?how can i get it?
  • hi ,the example files only have these files "F2837xD_sci_flash_kernels_cpu01.txt"and "blinky_cpu01.txt".but I don't know how to get these two files for my mcu f28033.can you help me?
  • Try using CCS Uniflash or C2PROG.