• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 499 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: When debugging, encountering the Error-1180@0x0.

suafie
Intellectual 490 points
Part Number: EVMK2EX


Tool/software: Code Composer Studio

Hello,

        When  debugging the project called DDR3_EDMA_TEST on the windows os,  I just encountered the error as follows:

        C66xx_0: Error connecting to the target: (Error -1180 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 8.3.0.00003)

        And I have tried to power off and then power on several times, it was stil the same. How to fix this problem?

        Suafie

  • 0
    TI__Guru**** 171309 points

    Suafie,

    This is quite uncommon with Keystone II devices that the C66x is held in reset, but this may be caused by a few factors:

    - Wrong bootmode. That could cause a problem given the bootmode influences the ability to connect. Although I don't think this is applicable to your case, given that you restarted the board several times - unless you inadvertently changed a jumper switch during this process. Check the board documentation for details.

    - Bad code written to flash or another non-volatile memory. In this case, bad code could potentially lock the C66x core into a bad state or in reset, preventing the JTAG to connect. Bootmode can potentially workaround this scenario by simply switching the bootmode away from the built-in Flash or other non-volatile memory (SD card).  

    - Improper power or the entire device being fully held in reset by external means and/or the surrounding circuitry. That would imply a hardware verification around the device. Also, if you are able to connect to the Cortex A15 cores, then it would be an isolated problem with the C66x alone.  

    - Other issues such as device security or embedded High level OS running are not as common with this family of devices. 

    Can you check the small LCD display for any status issues and compare with the board documentation? That could give additional clues as to what may be happening. 

    Hope this helps,

    Rafael