CCS/EK-TM4C1294XL: Issue with building the CAN project

Dear Members I included line #include "utils/uartstdio.c" in the main c program (blinky.c ). So there are no error this time

But the CDT Build Console (blinky) shows the following message:

**** Build of configuration Debug for project blinky ****

"C:\\ti\\ccsv7\\utils\\bin\\gmake" -k all
'Building file: ../blinky.c'
'Invoking: ARM Compiler'
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=FPv4SPD16 --abi=eabi -me -O2 --include_path="C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include" --include_path="C:/ti/TivaWare_C_Series-2.1.3.156" --advice:power=all -g --gcc --define=ccs="ccs" --define=PART_TM4C1294NCPDT --define=TARGET_IS_TM4C129_RA1 --diag_wrap=off --diag_warning=225 --display_error_number --gen_func_subsections=on --ual --preproc_with_compile --preproc_dependency="blinky.d" "../blinky.c"
"C:/ti/TivaWare_C_Series-2.1.3.156/utils/uartstdio.c", line 668: remark #2623-D: (ULP 5.4) Detected an assignment to a type with size less than int. To avoid unnecessary sign extension, use int-sized types for local varaibles and convert to smaller types for static storage.
"C:/ti/TivaWare_C_Series-2.1.3.156/utils/uartstdio.c", line 878: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"C:/ti/TivaWare_C_Series-2.1.3.156/utils/uartstdio.c", line 1044: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"C:/ti/TivaWare_C_Series-2.1.3.156/utils/uartstdio.c", line 1139: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../blinky.c", line 110: warning #112-D: statement is unreachable
"C:/ti/TivaWare_C_Series-2.1.3.156/utils/uartstdio.c", line 134: remark #1534-D: (ULP 7.1) Detected use of global variable "g_pcHex" within one function "UARTvprintf". Recommend placing variable in the function locally
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 189 (col. 27): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 190 (col. 10): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 193 (col. 27): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 194 (col. 10): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 196 (col. 27): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 197 (col. 10): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 198 (col. 10): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 202 (col. 27): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 203 (col. 10): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 204 (col. 10): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 206 (col. 27): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 207 (col. 11): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 208 (col. 11): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 214 (col. 27): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 215 (col. 11): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 216 (col. 11): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 218 (col. 27): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 219 (col. 10): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 222 (col. 27): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 223 (col. 10): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 231 (col. 27): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 232 (col. 10): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 233 (col. 27): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 234 (col. 10): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 260 (col. 27): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 262 (col. 9): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 264 (col. 13): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 268 (col. 9): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 270 (col. 13): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 277 (col. 27): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 279 (col. 9): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 281 (col. 13): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 285 (col. 9): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include/_defs.h", line 287 (col. 13): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"../blinky.c", line 93 (col. 50): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"../blinky.c", line 94 (col. 61): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"../blinky.c", line 95 (col. 61): remark #1531-D: (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
'Finished building: ../blinky.c'
' '
'Building target: blinky.out'
'Invoking: ARM Linker'
"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=FPv4SPD16 --abi=eabi -me -O2 --advice:power=all -g --gcc --define=ccs="ccs" --define=PART_TM4C1294NCPDT --define=TARGET_IS_TM4C129_RA1 --diag_wrap=off --diag_warning=225 --display_error_number --gen_func_subsections=on --ual -z -m"blinky_ccs.map" --heap_size=0 --stack_size=512 -i"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/lib" -i"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/include" --reread_libs --display_error_number --diag_wrap=off --warn_sections --xml_link_info="blinky_linkInfo.xml" --rom_model -o "blinky.out" "./blinky.obj" "./startup_ccs.obj" "../blinky_ccs.cmd" -llibc.a -l"C:/ti/TivaWare_C_Series-2.1.3.156/driverlib/ccs/Debug/driverlib.lib"
<Linking>
remark #10371-D: (ULP 1.1) Detected no uses of low power mode state changing instructions
'Finished building target: blinky.out'
' '
"C:/ti/ccsv7/utils/tiobj2bin/tiobj2bin" "blinky.out" "blinky.bin" "C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/bin/armofd" "C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.3.LTS/bin/armhex" "C:/ti/ccsv7/utils/tiobj2bin/mkhex4bin"
' '

**** Build Finished ****

And in the warnings section the following is shown:

Description Resource Path Location Type
This project was created using a version of compiler that is not currently installed - 5.2.6 [ARM]. Another version of the compiler will be used during build - 16.9.3.LTS. See 'Help > Install New Software' and select 'Code Generation Tools Updates' to check if this compiler is available through a CCS update. Visit <a href="liveaction:OpenAppCenter">CCS App Center</a> to get the latest compiler support. Or <a href="software-dl.ti.com/.../a> and install the compiler, then register it with CCS through 'Preferences > CCS > Build > Compilers'. blinky properties Problems
#112-D statement is unreachable blinky.c /blinky line 110 C/C++ Problem

Dear Members here is the code I am compiling (blink.c):

/*
* CAN bus LED controller master firmware
* Written for TI Tiva TM4C1294NCPDT
*/

#include <stdbool.h>
#include <stdint.h>
#include <math.h>

#include "inc/hw_memmap.h"
#include "inc/hw_types.h"
#include "inc/hw_can.h"
#include "inc/hw_ints.h"
#include "driverlib/can.h"
#include "driverlib/interrupt.h"
#include "driverlib/sysctl.h"
#include "driverlib/gpio.h"
#include "driverlib/uart.h"
#include "driverlib/pin_map.h"

#include "utils/uartstdio.h"
#include "utils/uartstdio.c"

#define PI 3.14159265359f

volatile bool errFlag = 0; // transmission error flag
unsigned int sysClock; // clockspeed in hz

void delay(unsigned int milliseconds) {
SysCtlDelay((sysClock / 3) * (milliseconds / 1000.0f));
}

// CAN interrupt handler
void CANIntHandler(void) {

unsigned long status = CANIntStatus(CAN1_BASE, CAN_INT_STS_CAUSE); // read interrupt status

if(status == CAN_INT_INTID_STATUS) { // controller status interrupt
status = CANStatusGet(CAN1_BASE, CAN_STS_CONTROL); // read back error bits, do something with them?
errFlag = 1;
} else if(status == 1) { // message object 1
CANIntClear(CAN1_BASE, 1); // clear interrupt
errFlag = 0; // clear any error flags
} else { // should never happen
UARTprintf("Unexpected CAN bus interrupt\n");
}
}

int main(void) {

tCANMsgObject msg; // the CAN message object
unsigned int msgData; // the message data is four bytes long which we can allocate as an int32
unsigned char *msgDataPtr = (unsigned char *)&msgData; // make a pointer to msgData so we can access individual bytes

// Run from the PLL at 120 MHz.
sysClock = SysCtlClockFreqSet((SYSCTL_XTAL_25MHZ | SYSCTL_OSC_MAIN | SYSCTL_USE_PLL | SYSCTL_CFG_VCO_480), 120000000);

// Set up debugging UART
SysCtlPeripheralEnable(SYSCTL_PERIPH_GPIOA); // enable UART0 GPIO peripheral
SysCtlPeripheralEnable(SYSCTL_PERIPH_UART0);
GPIOPinConfigure(GPIO_PA0_U0RX);
GPIOPinConfigure(GPIO_PA1_U0TX);
GPIOPinTypeUART(GPIO_PORTA_BASE, GPIO_PIN_0 | GPIO_PIN_1);
UARTStdioConfig(0, 115200, sysClock); // 115200 baud

// Set up CAN1
SysCtlPeripheralEnable(SYSCTL_PERIPH_GPIOB); // enable CAN1 GPIO peripheral
GPIOPinConfigure(GPIO_PB0_CAN1RX);
GPIOPinConfigure(GPIO_PB1_CAN1TX);
GPIOPinTypeCAN(GPIO_PORTB_BASE, GPIO_PIN_0 | GPIO_PIN_1);
SysCtlPeripheralEnable(SYSCTL_PERIPH_CAN1);
CANInit(CAN1_BASE);
CANBitRateSet(CAN1_BASE, sysClock, 500000);
CANIntRegister(CAN1_BASE, CANIntHandler); // use dynamic vector table allocation
CANIntEnable(CAN1_BASE, CAN_INT_MASTER | CAN_INT_ERROR | CAN_INT_STATUS);
IntEnable(INT_CAN1);
CANEnable(CAN1_BASE);

// Set up msg object
msgData = 0;
msg.ui32MsgID = 1;
msg.ui32MsgIDMask = 0;
msg.ui32Flags = MSG_OBJ_TX_INT_ENABLE;
msg.ui32MsgLen = sizeof(msgDataPtr);
msg.pui8MsgData = msgDataPtr;

unsigned int t = 0; // loop counter
float freq = 0.3; // frequency scaler

while(1) {

// set up next colour (scale sinf (0-1) to 0-255)
msgDataPtr[0] = (0.5 + 0.5*sinf(t*freq)) * 0xFF;
msgDataPtr[1] = (0.5 + 0.5*sinf(t*freq + (2*PI/3))) * 0xFF; // 120 degrees out of phase
msgDataPtr[2] = (0.5 + 0.5*sinf(t*freq + (4*PI/3))) * 0xFF; // 240 degrees out of phase
msgDataPtr[3] = 128; // 50% intensity

UARTprintf("Sending colour\tr: %d\tg: %d\tb: %d\n", msgDataPtr[0], msgDataPtr[1], msgDataPtr[2]); // write colour to UART for debugging
CANMessageSet(CAN1_BASE, 1, &msg, MSG_OBJ_TYPE_TX); // send as msg object 1

delay(100); // wait 100ms

if(errFlag) { // check for errors
UARTprintf("CAN Bus Error\n");
}

t++; // overflow is fine
}

return 0;
}
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The Output in the warning window:

Description Resource Path Location Type
#112-D statement is unreachable blinky.c /blinky line 110 C/C++ Problem

The second last line having the "return 0" shows the warning
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

But what is this warning:

Description Resource Path Location Type
#112-D statement is unreachable blinky.c /blinky line 110 C/C++ Problem

So I did comment the return 0 and the program is compiling without any errors and warnings.

But I notice certain output in the popped up Advice window as follows:

Description Resource Path Location
Current optimization/debug settings: --opt_level=2 --opt_for_speed=1 -g Current optimization/debug settings: --opt_level=2 --opt_for_speed=1 -g blinky properties
<a href="processors.wiki.ti.com/.../27010">Not all available code size is being used. Recommend running Optimization Assistant to find best speed vs size setting (--opt_for_speed). Double-click to start.</a> Not all available code size is being used. Recommend running Optimization Assistant to find best speed vs size setting (--opt_for_speed). Double-click to start. blinky properties

<a href="processors.wiki.ti.com/.../27008">Detecting compilation with low optimization. Recommend setting --opt_level=3. NOTE: debug ability will decrease.</a> Detecting compilation with low optimization. Recommend setting --opt_level=3. NOTE: debug ability will decrease. blinky properties

Description Resource Path Location
#2623-D (ULP 5.4) Detected an assignment to a type with size less than int. To avoid unnecessary sign extension, use int-sized types for local varaibles and convert to smaller types for static storage. .ccsproject /blinky line 668, external location: C:\ti\TivaWare_C_Series-2.1.3.156\utils\uartstdio.c
#1534-D (ULP 7.1) Detected use of global variable "g_pcHex" within one function "UARTvprintf". Recommend placing variable in the function locally .ccsproject /blinky line 134, external location: C:\ti\TivaWare_C_Series-2.1.3.156\utils\uartstdio.c
#1531-D (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive blinky.c /blinky line 93
#1531-D (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive blinky.c /blinky line 94
#1531-D (ULP 5.2) Detected floating point operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive blinky.c /blinky line 95
#1527-D (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead .ccsproject /blinky line 1044, external location: C:\ti\TivaWare_C_Series-2.1.3.156\utils\uartstdio.c
#1527-D (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead .ccsproject /blinky line 1139, external location: C:\ti\TivaWare_C_Series-2.1.3.156\utils\uartstdio.c
#1527-D (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead .ccsproject /blinky line 878, external location: C:\ti\TivaWare_C_Series-2.1.3.156\utils\uartstdio.c
(ULP 1.1) Detected no uses of low power mode state changing instructions (ULP 1.1) Detected no uses of low power mode state changing instructions blinky

Can all these be ignored ?

Those are all suggestions/recommendations on how to improve performance of your application. You can ignore it if you wish. Or if you wish to optimize your application, you can follow the suggestions.

Thanks

ki

Dear Ki-Soo Lee,

Thank you very much for helping me out. Thank you very much. Bye bye for now