• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 99 subscribers
  • Views 651 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.

CCSv4 debugging Error Trouble Halting Target

Ayus
Intellectual 825 points
Other Parts Discussed in Thread: CONTROLSUITE

 

 

Hello,

 

We have problem in debugging DM814x EVM with XDS560 and CCSv4.

We get errors when debugging the board for a long duration.

In order to test the reliability of our program,

after loading the program through CCS and pressing "Run", we have to leave the program

running for a while (around 1 hour).

 

But after running for a while(>1 hour), if we try to stop the program on the 

CCS, we get errors as shown below and we are not able to continue debugging.

 

Error type 1:

C674X_0: Trouble Halting Target CPU: (Error -1060 @ 0x0) Device is not responding to the request. 

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). 

 

Error type 2:

C674X_0: Error: (Error -1 @ 0x0) This '-1' value should be returned only during code development. 

It is a temporary value used when a more appropriate error value has not yet been assigned. 

This is the most negative of the three trivial error numbers that are used by USCIF adapters, drivers and utilities. (Release 5.0.429.0) 

C674X_0: Trouble Halting Target CPU: (Error -1044 @ 0x0) The emulator reported an error. 

Confirm emulator configuration and connections, reset the emulator, and retry the operation.

 

We are using the latest GEL file and also tried to slow down the TCLK clock(<3MHz)

but no success.

 

I would like to know if there is any limitation in CCSv4 or the JTAG emulators 

that will not allow to debug or run programs for a long time.

 

 

Regards.

 

  • 0
    TI__Genius 15310 points

    Ayus,

    Look like your program is running in infinite loop.  Have you try the test software in CCS provide by Mistral?  It can be download from their website at: http://www.mistralsolutions.com/pes-products/development-platforms/tmdxevm8148.html.

    Regards,

    Viet

  • 0 in reply to Viet Dinh
    TI__Guru*** 125430 points

    These types of emulation errors are often indicative of something "bad" happening in the software.  For example the software has jumped off into the weeds, corrupted the emulation logic, etc.  It could potentially be a hardware issue too.  Generally speaking you need to keep simplifying things until you figure out what's wrong.  For example, if you reduce your code to just a straight while(1) loop (i.e. remove all the software!) do you still have this problem?  Some common culprits for "bad behavior" are listed on this wiki page:

    http://processors.wiki.ti.com/index.php?title=DSP_BIOS_Debugging_Tips

  • 0 in reply to Brad Griffis
    Intellectual 825 points

    Hi,

     

    Thank you so much for the replies,

    we appreciate your kind support.

     

    One thing I understood with your replies is that, there is no such limitation in  CCS or the JTAG emulator.

    There may be some problems in our software.

    We have already tried TI's sample codes but we into next step, trying to evaluate some other softwares in 

    which we need to test the program running for a long time.

    >" It could potentially be a hardware issue too"

    We are using TI's EVM, do you mean to say the EVM might be wrong, 

    we shall ask this to MIstral solution also..

     

    We shall try reducing the code.

     

    Regards.

     

     

     

  • 0 in reply to Ayus
    TI__Guru*** 125430 points

    Ayus said:
    We are using TI's EVM, do you mean to say the EVM might be wrong, 

    I didn't realize you were using the EVM.  It's not very likely to be an issue in the EVM, though that is always a possibility.  Nobody is perfect!  :)  Most likely I imagine the issue is in your software.

  • 0
    Expert 2085 points

    I have many similar problems in MCU28027 with CCS4.

    so it doesn't look like the problem is related to MCU, but CCS4 probably.

  • 0 in reply to Harrison 2011
    TI__Guru*** 125430 points

    Harrison 2011 said:

    so it doesn't look like the problem is related to MCU, but CCS4 probably.

    If you're using the latest version of CCS then I don't think that's the problem.  I've sat with many a customer that claimed CCS was the problem -- until I found critical bugs in the customers' software that were corrupting things!!!  Then everything was rock solid...

    Go back to something simple -- perhaps just a while(1) loop for starters!  I bet it will be rock solid in that setup.  Start adding code progressively until it gets unstable.  Then you'll know where to focus your attention.

  • 0 in reply to Brad Griffis
    Expert 2085 points

    Brad Griffis said:

    so it doesn't look like the problem is related to MCU, but CCS4 probably.

     

    If you're using the latest version of CCS then I don't think that's the problem.  I've sat with many a customer that claimed CCS was the problem -- until I found critical bugs in the customers' software that were corrupting things!!!  Then everything was rock solid...

    Go back to something simple -- perhaps just a while(1) loop for starters!  I bet it will be rock solid in that setup.  Start adding code progressively until it gets unstable.  Then you'll know where to focus your attention.

    [/quote]

    I guess you might be right but problems only happen when things become complicated.

    if there is no code running on MCU, it would be rocksolid too.

    CCS does have many proven bugs, so do Controlsuite and TI demo kits, thus it is natrual that we first suspect CCS.