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.

TMS320F28P659DK-Q1: Command Line Build Error with Syscfg

Part Number: TMS320F28P659DK-Q1
Other Parts Discussed in Thread: SYSCONFIG, C2000WARE

Hi, 

I trying to setup a build server and do CLI-based build for my project on a Debian-based system. When I run build command, it gives the following cryptic error related to Syscfg.  I could not find any useful info there. 

TypeError: unknown property: selectRegisteredInterrupts
    at e (/home/test/ti/ccs2051/ccs/utils/sysconfig_1.27.1/dist/webpack:/sysconfig/src/pinmux/services/objectManagers/proxyHandlers/managedObjectProxyHandler.ts:186:8)
    at Object.set (/home/test/ti/ccs2051/ccs/utils/sysconfig_1.27.1/dist/webpack:/sysconfig/src/pinmux/services/objectManagers/proxyHandlers/managedObjectProxyHandler.ts:187:1)
    at scriptFunc (/home/test/dspbuild/buildworkspace/ESS_DC_DC_Controller/Controller.syscfg:677:33)
    at cb (/home/test/ti/ccs2051/ccs/utils/sysconfig_1.27.1/dist/webpack:/sysconfig/src/pinmux/services/scripting/runScript.ts:127:13)
    at t.withDeprecatedAccessAsync (/home/test/ti/ccs2051/ccs/utils/sysconfig_1.27.1/dist/webpack:/sysconfig/src/pinmux/services/deprecatedAccessGuard.ts:24:16)
    at t.runAsUserScriptAsync (/home/test/ti/ccs2051/ccs/utils/sysconfig_1.27.1/dist/webpack:/sysconfig/src/pinmux/services/scripting/scriptingGuard.ts:93:41)
    at runScripts (/home/test/ti/ccs2051/ccs/utils/sysconfig_1.27.1/dist/webpack:/sysconfig/src/pinmux/services/scripting/runScript.ts:125:31)
    at t.createFromScripts (/home/test/ti/ccs2051/ccs/utils/sysconfig_1.27.1/dist/webpack:/sysconfig/src/pinmux/services/scripting/runScript.ts:87:8)
    at t.generateOutput (/home/test/ti/ccs2051/ccs/utils/sysconfig_1.27.1/dist/webpack:/sysconfig/src/cli/cli_core.ts:102:20)
    at t.runCLI (/home/test/ti/ccs2051/ccs/utils/sysconfig_1.27.1/dist/webpack:/sysconfig/src/cli/runCli.ts:49:13)

Can you help? Thank you.

  • Hi Jwalant,

    This error is a SysConfig/C2000Ware version compatibility issue. Your Controller.syscfg file (line 677) is attempting to set a property called selectRegisteredInterrupts that doesn't exist in SysConfig 1.27.1 bundled with your CCS 20.5.1 installation. This means the .syscfg file was likely created or last saved with a different version of SysConfig or C2000Ware than what's installed on your Debian build server.

    SysConfig device support modules (which define available properties) come from C2000Ware, not SysConfig itself. When C2000Ware versions are mismatched between your development machine and build server, properties that exist in one version may not exist in another — causing this "unknown property" TypeError [1][2].

    Key compatibility requirement: If using SysConfig 1.21 or newer, C2000Ware must be updated to at least v5.04 [1]. Your build server's C2000Ware version likely doesn't include the interrupt module definition that exposes selectRegisteredInterrupts.

    Resolution Steps

    1. Align your build server's C2000Ware version with the version used on your development machine where the project builds successfully. Update to C2000Ware 6.00.01.00 or later for full F28P65x support [2].

    2. Verify the SysConfig product path in your CLI build command points to the correct C2000Ware installation. The --product argument should reference the .metadata/product.json inside your C2000Ware directory.

    3. If upgrading isn't immediately feasible — as a temporary workaround, open Controller.syscfg at line 677, identify the module setting selectRegisteredInterrupts, and comment out or remove that property assignment. Note this may affect interrupt configuration in the generated code.

    4. Ensure consistency — whatever CCS/SysConfig/C2000Ware combination works on your development machine should be replicated exactly on the build server.

    To help refine this recommendation, it would be helpful to know:

    • Which version of C2000Ware is currently installed on your Debian build server?
    • Which CCS/SysConfig version was used to originally create or last modify Controller.syscfg on your development machine?
    • Was this project migrated from an older or newer CCS installation?

    Resources:

    1. C2000Ware MotorControl SDK 5.04.00.00 Release Notes
    2. C2000Ware 6.00.01.00 Release Notes
    3. E2E: TMS320F28P650DK SysConfig Device Support Problems

    Best Regards,

    Zackary Fleenor

  • Hi Jwalant,

    I wanted to follow up on the SysConfig build error you reported. Have you had a chance to check the C2000Ware version alignment between your development machine and Debian build server?

    To help move this forward, could you provide:

    1. C2000Ware version on your build server (check /home/test/ti/c2000/C2000Ware_*/ or the path referenced in your build script)
    2. CCS/SysConfig version used on your development machine where the project builds successfully
    3. Confirmation whether this .syscfg file was created/modified on a different machine or migrated from another CCS version

    If you're able to share the specific line from Controller.syscfg:677 that's triggering the error, I can also help identify which module/property is causing the mismatch.

    In the meantime, the quickest path forward is typically:

    • Match C2000Ware versions between dev machine and build server (recommend C2000Ware 6.00.01.00+ for F28P65x)
    • Verify the --product path in your CLI build command points to the correct C2000Ware .metadata/product.json

    Let me know if you need any clarification on the resolution steps, or if you'd like guidance on updating C2000Ware on your Debian system.

    Best Regards,
    Zackary Fleenor