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.

TMS320F280039C: Can't update Sysconfig 1.15 in Code Composer Studio 12.2 to use the latest C2000ware

Part Number: TMS320F280039C
Other Parts Discussed in Thread: SYSCONFIG, C2000WARE, MOTORWARE

I ran Sysconfig 1.15 standalone on my Mac computer.  I installed the latest C2000ware version 4.03 in Sysconfig so I could use some of the newer features.  In Code Composer Studio I can't seem to get Sysconfig to run anything past 4.02. 

When I copy my sysconfig file to the project, I get the following error and many more similar errors

When I launch Sysconfig in Code Composer I get the following dialog showing that the latest version of C2000Ware is 4.02, not 4.03.  The instructions say to browse to the latest C2000ware but there is no button or way to browse (as there is in the standalone version).  If I hit the big browse button it only lets me select .syscfg files. 

In the standalone version there is a browse button:

I made sure that I am using the latest products in Code Composer Studio:

How can I use my Sysconfig file that I created in the standalone version in my project?

Regards

  • Hello Neil,

    If you click on the "Show Details..." link for the error, can you send me the details about what exactly is causing the error?

    Best regards,

    Omer Amir

  • I found that if I hit "No" and then I get this dialog.

    Now if I hit "Browse" and reselect the same file that I double clicked on, if Works!!  However, every time I close it and reopen it, I have to go through the same process.  This must be a bug in Sysconfig.

  • Spoke too soon.  Sysconfig opens and I see all my changes, however, I get the same error when I try to compile the project.

  • Hello Neil,

    I understand if you cannot share the entire .syscfg file, but can you find what module is using the property divideValue? It looks like SysConfig is trying to set this property, but is not able to find a property by the same name for the module and is crashing as a result. Let me know if this property is something that is present within that file or not (you can open the .syscfg as a text file to view this).

    Best regards,

    Omer Amir

  • Three places:

    const divider3 = system.clockTree["PLL_ODIV"];
    divider3.divideValue = 4;

    const divider4 = system.clockTree["PLL_REFDIV"];
    divider4.divideValue = 2;

    const divider5 = system.clockTree["SYSCLKDIVSEL"];
    divider5.divideValue = 1;

  • Thank you for looking into this for me!

  • I can upload the entire sysconfig file if it helps.

    Thanks

  • Thanks Neil,

    Yes, that will help. It looks like your SysConfig file is trying to set certain properties of the ClockTree tool and failing. When you do manage to open the SysConfig GUI and change settings, are you able to see the ClockTree tool on the left side of the UI? Are you able to open the visual interface to view the ClockTree tool properly?

    Best regards,

    Omer Amir

  • I think I figured out the problem.  If I look at the Sysconfig properties:

    I see the resource ${C2000WARE_ROOT}.  This resource is pointing to the C2000ware located inside of C2000ware_MotorControl_SDK_v4.01.00.0.  This version of C2000ware is out of date.  If I change the resource of ${C2000WARE_ROOT} to point to the installed version of C2000Ware_4.03.00.00 the error goes away.  The bug seems to be that the MotorControl SDK has an outdated C2000ware in it and my project (which was started in an older version) points to the C2000ware in the MotorControl_SDK.

    What is the best way to fix this?  Should I move the latest version of C2000Ware into the MotorWare SDK to replace the older version or just leave it there and  manually change the resource like I did?

  • Hello Neil,

    The C2000Ware within the Motor Control SDK will have the latest C2000Ware version at the time of its release, so if a new C2000Ware version comes out without a new Motor Control SDK version also coming out, then it's unavoidable that it will be out-of-date. The solution to this would be to either point to the newest C2000Ware version (outside of Motor Control SDK, you can change this by altering the Linked Resources option), or yes copy the latest C2000Ware and replace what exists in the Motor Control SDK you're using. Whichever solution works best for you is up to you, there should not be much benefit or drawback either way.

    Best regards,

    Omer Amir