• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 55 subscribers
  • Views 315 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.

CODECOMPOSER: Builtin Sysconfig editor not opening without CCS project

Markus Großer
Prodigy 125 points
Part Number: CODECOMPOSER
Other Parts Discussed in Thread: SYSCONFIG, C2000WARE, TMS320F28386D

Tool/software:

I have a project that uses CMake rather than CCS's native build system to build firmware for a C2000 microcontroller. While I am well aware that this is not supported by TI, this works very reliably using the CMake Tools plugin for Eclipse Theia. TI Sysconfig has been included in the build chain as well, and debugging using the CMake-produced ELF files works as expected.

However, the Sysconfig file can only be edited using the standalone Sysconfig tool. Double-clicking the file in the IDE seemingly does nothing -- no new editor tab is opened, and there is no mention of an error in the log files references under "Help -> Support".

I am fully aware this is not a lot of info to work from. If there is any way for me to provide further diagnostic information, I will happily provide such.

  • 0
    TI__Guru**** 472411 points

    Hello,

    I believe standalone sysconfig files not part of a project in the workspace is not a supported use case. I am following up with engineering for confirmation.

    Thanks

    ki

  • +1 in reply to Ki
    TI__Genius 15710 points

    When an SysConfig editor is opened in CCS it pulls information on SDK(product) and device/board from project. This information is passed to SysConfig editor when it opens. In case of cmake project this information does not exist in a form that CCS build system could extract this information. 

    I am guessing that when sysconfig has been added to cmake the product and board/device is passed in on a command line. 

    This information can also be embedded in syscfg file itself, however, we would most likely need to make changes to allow this fallback. I'll file an enhancement ticket to track this. 

    Martin

  • 0 in reply to MartinS
    Prodigy 125 points

    I am guessing that when sysconfig has been added to cmake the product and board/device is passed in on a command line. 

    The SDK path is indeed passed on the command line (-s C:/ti/c2000/C2000Ware_5_03_00_00). Board/Device is passed in the header of the Sysconfig file (@v2CliArgs --device "TMS320F28386D" --package "337bga" --context "CPU1" --product "C2000WARE@5.03.00.00"). Having to pass the SDK path in the file header would be a very workable solution from our side.