LAUNCHXL-F280049C: Sysconfig error message for example project C2000ware 4.01

Hi,

Sorry for the confusion of the file, you are correct in the location of the flags, but they need to be enclosed in the comment tags. Here's a full .syscfg file example for your device and example:

/**
 * 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 "F28004x" --package "F28004x_100PZ" --part "F28004x_100PZ" --context "system" --product "C2000WARE@4.02.00.00"
 * @versions {"tool":"1.0.0+dev"}
 */
/**
 * Import the modules used in this configuration.
 */
 const eqep  = scripting.addModule("/driverlib/eqep.js", {}, false);
 const eqep1 = eqep.addInstance();
 const gpio  = scripting.addModule("/driverlib/gpio.js", {}, false);
 const gpio1 = gpio.addInstance();
 
 /**
  * Write custom configuration values to the imported modules.
  */
 eqep1.$name                  = "myEQEP0";
 eqep1.eqepResolution         = "EQEP_CONFIG_1X_RESOLUTION";
 eqep1.emulationMode          = "EQEP_EMULATIONMODE_RUNFREE";
 eqep1.positionCounterMax     = 4294967295;
 eqep1.enableUnitTimer        = true;
eqep1.unitTimerPeriod      = 1000000;
 eqep1.latchPositionCounter   = "EQEP_LATCH_UNIT_TIME_OUT";
 eqep1.swPositionInit         = true;
 eqep1.enableModule           = true;
 eqep1.captureConfig          = true;
 eqep1.capPrescale            = "EQEP_CAPTURE_CLK_DIV_64";
 eqep1.evntPrescale           = "EQEP_UNIT_POS_EVNT_DIV_32";
 eqep1.enableCapture          = true;
 eqep1.eqep.$assign           = "EQEP1";
eqep1.eqep.eqep_aPin.$assign     = "GPIO6";
eqep1.eqep.eqep_bPin.$assign     = "GPIO7";
eqep1.eqep.eqep_indexPin.$assign = "GPIO9";

gpio1.$name             = "myGPIO0";
gpio1.direction         = "GPIO_DIR_MODE_OUT";
gpio1.writeInitialValue = true;
gpio1.gpioPin.$assign   = "GPIO4";

And here's what the GUI view looks like with Sysconfig GUI opened:

One last thing to check, if it's only opening in the "text" view, then you'll need to choose "Open With->Sysconfig Editor". If that Sysconfig Editor option doesn't show up, then it is either the CCS version being out of date (I had thought 9.3 was supported, but maybe not), or the Sysconfig install did not occur correctly.

Please let me know if I'm misunderstanding the issue too, I think I am understanding most of the issue is that you're seeing, but I may be assuming things that I've seen in similar issues that don't apply here.

Regards,

Vince

GI,

The release notes for C2000Ware 4.01 state that CCSv11 or later is required.  So you could use CCSv11.0.0, 11.1.0 or 11.2.0.  I have no idea if it was just tested with v11 or if the projects actually use features that are only present in CCSv11 or later.  So I would certainly hesitate to use v9.3.0.

These daysSysConfig is generally pretty compatible across CCS versions but in CCSv9.3 CCS did not support switching SysConfig versions. So even though it is detecting the newer SysConfig installs on your machine it will actually be using the one that shipped with CCSv9.3, which I think is 1.3.  The 1.3 version is not new enough for C2000.

You really should be using a newer CCS.  If you really really really have to use 9.3 you could try replacing the SysConfig in the ccs/utils folder with one of the newer ones that you have installed.  i.e rename the existing sysconfig folder to backup_sysconfig.  Then copy in the folder for one of the newer ones and then rename it to sysconfig (without the version on the end).

However I will stress again that a newer CCS is required to be a supported environment.

Regards,

John

CCSv11 still supports Windows 7.  We are actually going to support Windows 7 with CCSv12 as well (that will be the last one).

John