• Locked Locked
  • Replies 6 replies
  • Subscribers 54 subscribers
  • Views 3288 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.

Power Failure on Target CPU

Gary Lynch
Expert 1310 points

Other Parts Discussed in Thread: TMS320F2812

I am using CCSv4 with a TMS320F2812 under Windows 7. The
error message in the subject line has come up on this forum
numerous times in the past:
- http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/104344.aspx
- http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/55772/198652.aspx#198652
- http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/87040.aspx
- http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/204431.aspx
- http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/41494/145171.aspx#145171

but I have been unable to learn from prior posts what
condition, signal or lack thereof prompts CCS to issue this
diagnostic.  Up until today I assumed it was caused by a
loss of power on the target CPU.

But this morning I was running a diagnostic on my target
hardware under the debugger.  The application is a fairly
complex finite state machine that must go through several
steps after I flick the "On" switch attached to a digital
input before it can produce a high-frequency waveform on a
digital input.  After finishing the test, I returned to my
monitor to find:
  "C28xx: Power Failure on Target CPU"

on the console.  The only problem was, the target CPU never
knew about this 'power failure.'  It continued to produce the
waveform the whole time I was standing there.  If the
debugger disconnecting from the target caused a reset of the
target CPU, it would have taken several seconds to get back
to the state I was monitoring.  This did not happen.

So has anyone monitoring this thread ever figured out what
exactly CCS is using as a trigger for this condition? I am
now certain it is not related to the actual power to the
target CPU.

Diagnosing the cause of the disconnect would be much easier
to track down if the message actually matched the cause.

  • Expert 1310 points

    Correction:

    The 2nd sentence in the 3rd paragraph of my prior post should
    read:

                                  The application is a fairly
    complex finite state machine that must go through several
    steps after I flick the "On" switch attached to a digital
    input before it can produce a high-frequency waveform on a
    digital output.  

    Apologies for the typo.

  • in reply to Gary Lynch
    TI__Guru**** 480861 points

    Hi Gary,

    The error message most likely covers a broad range of scenarios of which may not accurately describe the actual issue.

    You can try enabling debug server logging to get a more descriptive log of what happened. Generate it, zip it up (otherwise it will be huge) and attached it here so we can take a peek.

    Also I see you are still on v4. I assume you are on it because you do not wish to switch tool version in the middle of development. But note that fixing bugs for v4 is very low priority since any issues found will be addressed in v5.

    Thanks

    ki

  • in reply to Ki
    Expert 1310 points

    On Nov 6, 2012 3:52 PM; Ki-Soo Lee wrote:
    >
    > You can try enabling debug server logging to get a more
    > descriptive log of what happened. Generate it, zip it up
    > (otherwise it will be huge) and attached it here so we can
    > take a peek.
    >
    As it turns out, it just power-failed a few minutes ago.

    Although I have seen dialog boxes indicating it may already
    be enabled, I can't figure out how to tell whether that is
    so, nor can I find anything that looks like a log: it's not
    under the install directory, nor the project directory.

    Nothing in the help system nor on the forums on this,
    either.

    1.  How do I enable/disable debug server logging?
    2.  Where do the logs go?

    >
    > Also I see you are still on v4. I assume you are on it
    > because you do not wish to switch tool version in the middle
    > of development.
    >
    Right on both counts.

  • in reply to Gary Lynch
    TI__Guru**** 480861 points

    Gary Lynch said:
    1.  How do I enable/disable debug server logging?
    2.  Where do the logs go?

    Oops, sorry, I forgot to provide the url in my previous post:

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCSv4#Debug_Server_Logging

    Thanks

    ki

  • in reply to Ki
    Expert 1310 points

    Just to let you know: I still intend to follow through on
    this task, but I fatally shorted my control board yesterday,
    it was the last one in stock, and our chief lab tech is out
    of town. I don't know how long this will take to repair, but
    I will report in when it happens.

    "When it rains--it pours."

  • in reply to Gary Lynch
    TI__Guru**** 480861 points

    yikes! Sorry to hear that. We will be waiting for your post.

    Thanks

    ki