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.

Bug in new 4.0.0.0 C2000 ware.

Part Number: C2000WARE
Other Parts Discussed in Thread: SYSCONFIG

Hi I just downloaded and installed the new C200o ware, as i need some of the new features in there.

But i also found a small bug.

Note: I am using a f28002x device, but based on the location of the error i asume it is general for more processor tyeps.

To trigger bug:

  1. In sysconfig setup a CAN device
  2. Give The Can device another name than the default myCAN..
  3. Build project.

You get an error:

"generated/board.c", line 247: error #20: identifier "myCAN0_BASE" is undefined
1 error detected in the compilation of "generated/board.c".

It appears that the BASE name has become hardcoded to `myCan0_BASE` in one line of the generated board.c

the problem line is:

	//
	// Start CAN module operations
	//
	CAN_startModule(myCAN0_BASE);

Fortunately the fix is easy

--- driverlib/.meta/can/can.board.c.xdt.old     2021-10-21 10:32:27.137006700 +0200
+++ driverlib/.meta/can/can.board.c.xdt.new     2021-10-21 12:36:21.239429700 +0200
@@ -57,7 +57,7 @@
        //
        // Start CAN module operations
        //
-       CAN_startModule(myCAN0_BASE);
+       CAN_startModule(`instance.$name`_BASE);
                % let instancePinmux = instance[nameOfModule];
                % let solution    = instancePinmux.$solution;
                % let peripheral  = system.deviceData.peripherals[solution.peripheralName];