• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 80 subscribers
  • Views 1341 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

[FAQ] How do I add SYSCONFIG support (Pinmux and Peripheral Initialization) to an existing driverlib project?

[FAQ] How do I fix a SysConfig CCS Project which is not building due to "Invalid argument '--product': No product with name "C2000WARE" and version" ?

Nima Eskandari
Guru 51940 points
Other Parts Discussed in Thread: SYSCONFIG, C2000WARE

I added a SysConfig file to a CCS project and now the project is not building due to an error caused by the SysConfig tool. The error is shown below:

Invalid argument '--product': No product with name "C2000WARE" and version

How do I resolve this issue?

Why is the issue above occurring in my CCS project?

  • 0
    TI__Guru 51940 points

    SysConfig Software Product is identified by CCS/SysConfig in one of the two ways below:

    1. The CCS project properties are set up: The entry inside the CCS project properties identifies the path to the product.json/sdk.json in the C2000WARE install

    2. The CCS project properties are not set up: In this scenario, SysConfig (similar to how it would in a standalone/non CCS based tool) looks into the .syscfg file in the project and parses the header at the top of the file which looks as show in the example below.

    /**
 * These arguments were used when this file was generated. They will be automatically applied on subsequent loads
 * via the GUI or CLI. Run CLI with '--help' for additional information on how to override these arguments.
 * @cliArgs --device "F2838x" --package "176pin" --part "F2838x_176pin" --product "C2000WARE@4.01.00.00"
 * @versions {"tool":"1.11.0+2225"}
 */

    The error discussed in this thread only occurs if #1 is not used and the scenario in #2 is executed.

    For scenario #2 to work, the SysConfig tool integrated within CCS must have at one point used the C2000WARE product version identified in the comment header at the top of the .syscfg file. That way it would have internally cached the location for the product.json/sdk.json. If the SysConfig tool integrated in the CCS never used and in turn cached the location of the product.json/sdk.json which refers to the SW product mentioned by the header, it will fail to find it.

    In this case, the use must setup the CCS project property to point to the path of the product.json/sdk.json. This is shown in step #6 in the FAQ below:

    https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/910829/faq-how-do-i-add-sysconfig-support-pinmux-and-peripheral-initialization-to-an-existing-driverlib-project

    Once this is setup in the project properties, the SysConfig tool, upon launching the .syscfg file, will not look in the special comment header for a --product entry.