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.

LAUNCHXL-F28379D: Hardware declaration in SysConfig

Part Number: LAUNCHXL-F28379D
Other Parts Discussed in Thread: SYSCONFIG

Hello,

Till now i ve been declaring the hardware I use in SysConfig file that way:

But dowloading the example TI provides for 2 cores application (led_ex2), there are not such informations:

Where are the part, package, ... defined ? (I want to switch them automatically)

Thank you

  • Hi Vincent,

    You can also switch the part and package via the sysconfig GUI. When you open a .syscfg file in ccs, there will be an icon on the top right corner that says "Show Device View",  click on that and there will be a button to switch parts, package and devices shown here:

    Best,

    Sen Wang

  • Hello,

    Thank you for answering

    That's exactly what I don't want to do.

    In my previous application, I chose the basic SysConfig Options to open directly the device I want.

    In the TI example, the right device is declared although it is certainly not the default one, but the example does not use these options. How is it possible ? how can I change that ?

  • Hi Vincent,

    I'm not sure if I understood your question. The newest sysconfig relies on generated makefiles to pass in any specific parameters to sysconfig. You can edit these parameters manually before you imported the project, when you edit .projectspec files as a text document, you'll find a line that looks similar to this:

    <project
            name="led_ex2_blinky_sysconfig_cpu1"
            device="TMS320F28388D"
            cgtVersion="22.6.1.LTS"
            outputFormat="ELF"
            launchWizard="False"
            linkerCommandFile=""
    	enableSysConfigTool="true"
    	sysConfigBuildOptions="--product ${C2000WARE_ROOT}/.metadata/sdk.json --device F2838x --context CPU1"
            >

    You can edit the device by editing the flags passed into sysConfigBuildOption (options are --device, --package, --part similar to what's shown below).

    You can also try edit the predefined manifest that you showed to see if it still overrides the generated makefile inputs, I've never done it via predefined macros so I'm not sure if it still works or not.

    Strictly speaking parts and package is only necessary when you edit .sysconfigs via GUI. Because sysconfig uses that parts and package info to determine the available pinmux options and perform checks when generating code. You can also edit the .syscfg files manually (although not recommened).

    Best,

    Sen Wang