• Locked Locked
  • Replies 1 reply
  • Subscribers 101 subscribers
  • Views 356 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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 problems with respect to OMAP-L138

Todd Anderson78572
Guru 14640 points

All:

OMAP-L138-EP

CCS 6.x

XDS100v2

Over the past several months, I have seen the following two problems on a non-regular basis:

C674x_0:Power Failure on Target CPU

   This was somewhat frequent about a month ago, and it was recoverable, although painful to recover:

   1. Power down target board.

   2. Power down computer with CCS6.

   3. Power up computer.

   4. Power up board.

SWT error 

    This was a lot more painful, and appeared to happen when I tried to have multiple editor windows open at the same time, as in looking at .c file in one window and associated .h file in an adjacent window.

   1. Uninstall CCS 6.x

   2. Reinstall CCS 6.x

One workaround that I have used to avoid a recurrence of this catastrophic problem is to use an external editor to view the .h file, and so far it seems to have worked better - I have not had and SWT error since going that direction.

  • TI__Mastermind 35645 points

    Hi,

    Thanks for your post.

    In these cases it is recommended to follow the sequence below to try to pinpoint the source of the issue:

    1.Turn off the board. The JTAG debugger will detect a power failure if it is still "alive" and usually indicates an issue with the running application on the target. CCS control is recovered.

    2.Unplug the JTAG debugger from the USB port. CCS will detect the JTAG debugger is non-existing anymore and may indicate an issue with the JTAG debugger itself. CCS control is recovered.

    3.Kill CCS from the Task Manager/using the console. This indicates the issue is on CCS itself, either caused by an internal error or by the interactions between itself and the JTAG debugger. Also, keep in mind that CCS may need some time to recover after unplugging the JTAG debugger, but that rarely goes longer than 30s.

    Also, just check the below wiki source which might help in debugging connectivity problems as well the CCS handbook :

    http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems#Introduction

    http://processors.wiki.ti.com/index.php/Projects_and_Build_Handbook_for_CCS#Introduction

    Thanks & regards,

    Sivaraj K

    ----------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.

    ----------------------------------------------------------------------------------------------------------