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/TMDSCNCD28379D: Compensation Designer GUI Not Launching Through PowerSuite

Part Number: TMDSCNCD28379D
Other Parts Discussed in Thread: POWERSUITE, SFRA, C2000WARE, CCSTUDIO

Tool/software: Code Composer Studio

Hi All, 

I am experiencing an issue when attempting to open the Compensation Designer through the PowerSuite page. II am currently following the Design Guide: TIDM-1000 and am on Step 3 of 6.4.2.1. Looking at our TI folder, we are able to launch the standalone Compensation Designer window by clicking on the .exe file. However we are unable to open the window through the PowerSuite page. I am running the most up to date version of CCS and using C2000Ware 2.01.00.00. 

To update: we are able to open the SFRA interface located directly to the right of the Compensation Designer button. When we click on the Compensation Designer button, our mouse displays the pinwheel and the CCS window becomes unresponsive.

Best,

Aiden

  • Aiden,

    Please apologize for the delay; I am not very familar with the PowerSuite design package.

    Unfortunately I don't have this development board, so I can't necessarily go through all the steps (I have the F28379D controlCARD)

    Following the TIDUCJ0F section 6.1 (with a few gaps on the steps), I imported the pfc3phvienna_F2837x project and the main.cfg page allows me to open the Compensation Designer normally (as well as the SFRA). This leads me to believe there may be either a slight difference on the versions of the tools or something inherent to your system. 

    Just for your reference, I am using the following versions: CCSv9.3.0, C2000Ware version 2.01.00.00 and C2000Ware_DigitalPower_SDK version 2.00.01.00 and PowerSUITE 2.05.01.00. All the packages (except CCS) are installed under C:\ti 

    I suspect the path where this button is defined is included in the PowerSUITE package, but I would need to further investigate this.

    In the meantime, can you try a different design project and see if the problem persists? This may help isolate the problem to this specific project or a system-wide issue. 

    Regards,

    Rafael

  • No problem, thank you Rafael. 

    I am using the same versions of C2000Ware and PowerSUITE, both of which are at the C:\ti directory. I tried pulling down different projects from the Resource Explorer, and on all of them we faced the same issue: I can open the SFRA window but when clicking on the Compensation Design, we get a loading mouse icon and then nothing occurs. We are however able to open the Compensation Viewer by clicking on the .exe file directly in the Windows File Manager - this suggests to me that our computer can handle opening the window, but the pathway to the executable file from the PowerSUITE main.cfg file may be off? 

    Our project folder is under a different directory, nested within the Workspace folder. But with this topology, which was organized by default, we are able to open SFRA, so I am scratching my head. 

    Thanks for your help. 

  • Aiden,

    I have been trying to find additional information about this particular software, but at this point I could not reproduce this in any of the hosts I tried (Windows 7, Windows 10) and CCSv9.2 and CCSv9.3.

    One idea that occurred to me was a dependency on the Microsoft Runtime Library, but that would prevent running the application in standalone mode. 

    Since CCS spins forever, one wild idea that may be causing a borderline problem in your environment is the heap memory of CCS/Eclipse. You could try to adjust this parameter in the ccstudio.ini - check section 9.4.4 of the CCS User's Guide at:

    https://software-dl.ti.com/ccs/esd/documents/users_guide/index.html

    I really don't think the nested directories should influence in this scenario - in any case, the project I have here is also inside the workspace, but it was fully imported into it from inside CCS. 

    Apart from that, I am really unsure what may be happening in your case and I am running out of ideas. I will try to keep "breaking" my system here, keep an eye on similar reports from other developers and report back to this thread in case I find anything relevant. 

    Hope this helps,

    Rafael