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

CPU Load Graph error

Joe Diederichs
Prodigy 20 points

Other Parts Discussed in Thread: OMAP5912

Running CCS 3.3.82.13, when I try to run the CPU Load Graph by choosing CPU Load Graph from the DSP/BIOS menu, I get an error message dialog: title bar: CPULOA~1; message text: An unsupported operation was attempted.

In the past this feature has worked for me. I'm not sure at what point it quit working. I suspect it may be related to the most recent version of CCS. Other DSP/BIOS diagnostic features still work (Execution Graph, Message Log, Kernal/Object View).

The other thing that is interesting is that I get the exact same error dialog if I try to run the CPU Load Graph before I have a program loaded on my target, and before I have a project loaded, i.e. immediately after connecting to the target. This makes it seem like it's some kind of a conflict on the PC in being able to run software to support the CPU Load Graph - perhaps a plugin or some such.

I am connecting to a C55 core in an OMAP5912, via an XDS510 USB. I am running DSP/BIOS 5.31.08. I am using Code Generation Tools v3.3.6.

 

  • TI__Mastermind 18130 points

    Joe Diederichs said:
    Running CCS 3.3.82.13, when I try to run the CPU Load Graph by choosing CPU Load Graph from the DSP/BIOS menu, I get an error message dialog: title bar: CPULOA~1; message text: An unsupported operation was attempted.

    The only information I could find about repairing this error was to reinstall CCS. I am not sure what causes the Load Graph window to break in this manner, but reinstalling does seem to fix whatever problem popped up. If you are interested in doing this you can also remove the GODSP and Texas Instruments folders from HKEY_LOCAL_MACHINE->SOFTWARE in the registry (Start->Run->regedit). You may want to back up the registry before doing this or double check with your IT group to make sure this is acceptable.

  • in reply to TimHarron
    Expert 1070 points

    Even though this thread is pretty old, I thought this could  be valuable to someone:

    I had the same issue using this CCS3.3: 

     

    After re-registering several plugins manually, it started working again. I don't know which one did the trick, here's the list I tried. 

     

    I believe the issue in my case was caused by installing CCS4.x, but that is speculation.

     

    -Dirk