• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 1748 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/TMS320C6455: Error connecting to the target(Error -1143 @0x0)

user5104219
Prodigy 10 points
Part Number: TMS320C6455


Tool/software: Code Composer Studio

Hi, guys.

Recently, I have met a problem as shown in Fig.1 for my TMS320C6455.

Fig. 1

Two days ago, we written a program for Flash with tool of FlashBurn in EMIFA 8-bit rom boot model. The program works well, however, this problem   appeared when we rewritten. Some information may be helpful for you as shown follows.

1. We use the emulator is XDS200.

2. When we connect the target with debug model in EMIFA 8-bit rom boot model, the problem appeare.  However, it works well in the no boot model.

3. I think a solution is  erasing the Flash. I try to erase the Flash with FlashBurn in no boot model, but it is not successful.

Please help me.

EMIFA 8-bit ROM boot

  • 0
    TI__Guru**** 171309 points
    Hi,

    As per your description, the error message stems from the fact your pre-loaded code is preventing the JTAG Debugger from halting the C64x+ core. You still have control over your device, but the state is unknown as the JTAG forcefully halted it.

    Further explanation about the error is shown in the reference below:
    software-dl.ti.com/.../ccsv7_debugging_jtag_connectivity_issues.html

    Since the main problem is to try and identify where your code may be preventing your connection, you can see where the processor is halted when the JTAG Debugger gains control over the target (you can also load symbols for source code visibility). Usually tight loops or operations where the CPU is hanging due to bus contention (multiple devices/subsystems accessing HPI, EMIF, etc.) can cause this.

    At any rate, you are probably able to reset your device and resume operation under the debugger to better identify if there is any problem.

    Hope this helps,
    Rafael