MSP430F5438A: How to include driverlib into my existing CCS project?

Swamy Jagannatham

Prodigy 80 points

Part Number: MSP430F5438A
Other Parts Discussed in Thread: MSP430WARE

Hello,

I have Smart RF Trx Evaluation Board Rev 1.7. This board has MSP430F5438A micro controller MCU.

I have Code Composer Software CCS 11.1.0 Version

I have created CCS project as shown below:

I am getting following link errors:

There are some unresolved link errors in this program as shown below.

undefined

symbol

---------

GPIO_clearInterrupt

GPIO_disableInterrupt

GPIO_enableInterrupt

GPIO_getInputPinValue

GPIO_selectInterruptEdge

GPIO_setAsInputPin

GPIO_setAsInputPinWithPullDownResistor

GPIO_setAsInputPinWithPullUpResistor

GPIO_setAsOutputPin

GPIO_setOutputHighOnPin

GPIO_setOutputLowOnPin

GPIO_toggleOutputOnPin

Timer_B_clear

Timer_B_clearTimerInterrupt

Timer_B_initUpMode

WDT_A_hold

Please let us know how we can resolve these unresolved symbols?

I looked at MSP430F5xx_6xx_DriverLib_Users_Guide-2_91_13_01.pdf pages 23, 24 and 25 etc.

After right clicking on MSP430_F5438A_Driver_error CCS project,

In the Source drop down menu, I have only Format sub menu. I do not have Apply Project Template ... option in my project as shown on below screen capture of my CCS project:

A colleague of mine in another city of my company, has following project, including the driverlib folder:

I do not have driverlib folder as shown in my CCS project:

In my CCS project, how to have Source -> Apply Project Template … menu option?

And how to have driverlib folder in my CCS project please?

Thanks and best regards,

over 3 years ago

0 Evan Lew over 3 years ago

TI__Genius 10010 points

Hi Swamy Jagannatham ,

If your colleague has a working version. I would ask to see their build output console and compare it against yours to see what the difference is.

Regards,

Evan

0 Swamy Jagannatham over 3 years ago in reply to Evan Lew

Prodigy 80 points

Hi Evan,

Thank you very much for the info.

I will compare and let you know.

Thanks,

SSJ

0 Swamy Jagannatham over 3 years ago in reply to Swamy Jagannatham

Prodigy 80 points

Hi Evan,

I did compare my project build output with my colleague's build output and I know where the differences are. However, I am not clear about how to fix the differences.

I have emailed the two build output txt files to ticsc@service-now.com email.

If possible, please see the two files and please let me know of some specific steps I can do to fix the differences and be able to build my project without errors.

Thanks and best regards,

0 Evan Lew over 3 years ago in reply to Swamy Jagannatham

TI__Genius 10010 points

Please attach the two files to your post as I don't have access to that email address.

Thanks,

Evan

0 Swamy Jagannatham over 3 years ago in reply to Evan Lew

Prodigy 80 points

SmartMot_RBSB_Interface_v1pt1_copy_Build Output_01a.txt

SSJ_build_console_output_01b.txt

Fullscreen

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
**** Build of configuration Debug for project MSP430_F5438A_Driver_error ****
"C:\\ti\\ccs1110\\ccs\\utils\\bin\\gmake" -k -j 8 all -O 
 
Building file: "../main.c"
Invoking: MSP430 Compiler
"C:/ti/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/bin/cl430" -vmspx --data_model=restricted --use_hw_mpy=F5 --include_path="C:/ti/ccs1110/ccs/ccs_base/msp430/include" --include_path="C:/ti/msp/MSP430Ware_3_80_14_01/driverlib/driverlib/MSP430F5xx_6xx" --include_path="C:/ti/msp/MSP430Ware_3_80_14_01/driverlib/driverlib/MSP430F5xx_6xx/inc" --include_path="C:/Antenna_Luneburg_Lens/TI_Driver_error_WS/MSP430_F5438A_Driver_error" --include_path="C:/ti/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include" --advice:power=all --define=__MSP430F5438A__ -g --printf_support=minimal --diag_warning=225 --diag_wrap=off --display_error_number --silicon_errata=CPU21 --silicon_errata=CPU22 --silicon_errata=CPU23 --silicon_errata=CPU40 --preproc_with_compile --preproc_dependency="main.d_raw"  "../main.c"
"../main.c", line 475: warning #225-D: function "Latch_Enable" declared implicitly
"../main.c", line 94: warning #179-D: variable "atten_bit" was declared but never referenced
"../main.c", line 100: warning #179-D: variable "tmp_in" was declared but never referenced
"../main.c", line 127: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 132: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 144: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 196: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 204: remark #1544-D: (ULP 13.1) Detected loop counting up. Recommend loops count down as detecting zeros is easier
"../main.c", line 225: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 226: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 227: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 228: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

**** Build of configuration Debug for project MSP430_F5438A_Driver_error ****

"C:\\ti\\ccs1110\\ccs\\utils\\bin\\gmake" -k -j 8 all -O 
 
Building file: "../main.c"
Invoking: MSP430 Compiler
"C:/ti/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/bin/cl430" -vmspx --data_model=restricted --use_hw_mpy=F5 --include_path="C:/ti/ccs1110/ccs/ccs_base/msp430/include" --include_path="C:/ti/msp/MSP430Ware_3_80_14_01/driverlib/driverlib/MSP430F5xx_6xx" --include_path="C:/ti/msp/MSP430Ware_3_80_14_01/driverlib/driverlib/MSP430F5xx_6xx/inc" --include_path="C:/Antenna_Luneburg_Lens/TI_Driver_error_WS/MSP430_F5438A_Driver_error" --include_path="C:/ti/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include" --advice:power=all --define=__MSP430F5438A__ -g --printf_support=minimal --diag_warning=225 --diag_wrap=off --display_error_number --silicon_errata=CPU21 --silicon_errata=CPU22 --silicon_errata=CPU23 --silicon_errata=CPU40 --preproc_with_compile --preproc_dependency="main.d_raw"  "../main.c"
"../main.c", line 475: warning #225-D: function "Latch_Enable" declared implicitly
"../main.c", line 94: warning #179-D: variable "atten_bit" was declared but never referenced
"../main.c", line 100: warning #179-D: variable "tmp_in" was declared but never referenced
"../main.c", line 127: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 132: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 144: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 196: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 204: remark #1544-D: (ULP 13.1) Detected loop counting up. Recommend loops count down as detecting zeros is easier
"../main.c", line 225: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 226: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 227: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 228: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 230: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 231: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 260: remark #1544-D: (ULP 13.1) Detected loop counting up. Recommend loops count down as detecting zeros is easier
"../main.c", line 267: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 273: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 279: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 285: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 291: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 297: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 303: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 309: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 315: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 321: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 327: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 333: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 339: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 345: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 351: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 357: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 365: remark #1544-D: (ULP 13.1) Detected loop counting up. Recommend loops count down as detecting zeros is easier
"../main.c", line 367: remark #1544-D: (ULP 13.1) Detected loop counting up. Recommend loops count down as detecting zeros is easier
"../main.c", line 383: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 389: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 400: remark #1544-D: (ULP 13.1) Detected loop counting up. Recommend loops count down as detecting zeros is easier
"../main.c", line 432: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 436: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 451: remark #1544-D: (ULP 13.1) Detected loop counting up. Recommend loops count down as detecting zeros is easier
"../main.c", line 467: remark #1544-D: (ULP 13.1) Detected loop counting up. Recommend loops count down as detecting zeros is easier
"../main.c", line 225: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 226: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 227: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 228: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 230: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 231: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 489: warning #161-D: declaration is incompatible with previous "Latch_Enable" (declared at line 475)
"../main.c", line 497: remark #2553-D: (ULP 14.1) Array index (involving "rf_addr") of type "int". Recommend using "unsigned int"
"../main.c", line 498: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 499: remark #2553-D: (ULP 14.1) Array index (involving "rf_addr") of type "int". Recommend using "unsigned int"
"../main.c", line 503: remark #2553-D: (ULP 14.1) Array index (involving "rf_addr") of type "int". Recommend using "unsigned int"
"../main.c", line 507: remark #2553-D: (ULP 14.1) Array index (involving "rf_addr") of type "int". Recommend using "unsigned int"
"../main.c", line 514: remark #2553-D: (ULP 14.1) Array index (involving "rf_addr") of type "int". Recommend using "unsigned int"
"../main.c", line 515: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 516: remark #2553-D: (ULP 14.1) Array index (involving "rf_addr") of type "int". Recommend using "unsigned int"
"../main.c", line 520: remark #2553-D: (ULP 14.1) Array index (involving "rf_addr") of type "int". Recommend using "unsigned int"
"../main.c", line 524: remark #2553-D: (ULP 14.1) Array index (involving "rf_addr") of type "int". Recommend using "unsigned int"
"../main.c", line 553: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function GPIO_toggleOutputOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 555: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function GPIO_toggleOutputOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 556: remark #1530-D: (ULP 5.1) Detected modulo operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"../main.c", line 558: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 561: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function GPIO_toggleOutputOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 563: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function GPIO_getInputPinValue. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 564: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function pow. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 577: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function GPIO_setOutputLowOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 604: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function GPIO_toggleOutputOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 609: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function GPIO_setOutputLowOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 613: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function GPIO_setOutputHighOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 615: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function GPIO_toggleOutputOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 616: remark #1530-D: (ULP 5.1) Detected modulo operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"../main.c", line 633: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 636: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function GPIO_setOutputLowOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 638: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function GPIO_setOutputLowOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 651: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function Timer_B_clearTimerInterrupt. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 671: remark #1538-D: (ULP 10.1) ISR Port_1 calls function GPIO_selectInterruptEdge. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 672: remark #1538-D: (ULP 10.1) ISR Port_1 calls function GPIO_clearInterrupt. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 676: remark #1538-D: (ULP 10.1) ISR Port_1 calls function GPIO_selectInterruptEdge. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 677: remark #1538-D: (ULP 10.1) ISR Port_1 calls function GPIO_clearInterrupt. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 685: remark #1538-D: (ULP 10.1) ISR Port_1 calls function GPIO_toggleOutputOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 686: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 687: remark #1538-D: (ULP 10.1) ISR Port_1 calls function GPIO_toggleOutputOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 688: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 689: remark #1538-D: (ULP 10.1) ISR Port_1 calls function GPIO_setOutputLowOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 692: remark #1538-D: (ULP 10.1) ISR Port_1 calls function GPIO_clearInterrupt. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 696: remark #1538-D: (ULP 10.1) ISR Port_1 calls function GPIO_clearInterrupt. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 39: remark #1534-D: (ULP 7.1) Detected use of global variable "data_port" within one function "main". Recommend placing variable in the function locally
"../main.c", line 39: remark #1535-D: (ULP 8.1) variable "data_port" is used as a constant. Recommend declaring variable as either 'static const' or 'const'
"../main.c", line 57: remark #1534-D: (ULP 7.1) Detected use of global variable "ui_att_le" within one function "main". Recommend placing variable in the function locally
"../main.c", line 57: remark #1535-D: (ULP 8.1) variable "ui_att_le" is used as a constant. Recommend declaring variable as either 'static const' or 'const'
"../main.c", line 58: remark #1534-D: (ULP 7.1) Detected use of global variable "ui_rf_enable" within one function "main". Recommend placing variable in the function locally
"../main.c", line 58: remark #1535-D: (ULP 8.1) variable "ui_rf_enable" is used as a constant. Recommend declaring variable as either 'static const' or 'const'
"../main.c", line 59: remark #1535-D: (ULP 8.1) variable "ui_prog_sel" is used as a constant. Recommend declaring variable as either 'static const' or 'const'
"../main.c", line 60: remark #1534-D: (ULP 7.1) Detected use of global variable "ui_smartmotor5v" within one function "main". Recommend placing variable in the function locally
"../main.c", line 60: remark #1535-D: (ULP 8.1) variable "ui_smartmotor5v" is used as a constant. Recommend declaring variable as either 'static const' or 'const'
"../main.c", line 61: remark #1534-D: (ULP 7.1) Detected use of global variable "ui_att_values_sw_pin" within one function "main". Recommend placing variable in the function locally
"../main.c", line 61: remark #1535-D: (ULP 8.1) variable "ui_att_values_sw_pin" is used as a constant. Recommend declaring variable as either 'static const' or 'const'
"../main.c", line 62: remark #1534-D: (ULP 7.1) Detected use of global variable "ui_rf_enable_sw_pin" within one function "main". Recommend placing variable in the function locally
"../main.c", line 62: remark #1535-D: (ULP 8.1) variable "ui_rf_enable_sw_pin" is used as a constant. Recommend declaring variable as either 'static const' or 'const'
"../main.c", line 63: remark #1535-D: (ULP 8.1) variable "ui_set_enable_sw_pin" is used as a constant. Recommend declaring variable as either 'static const' or 'const'
"../main.c", line 64: remark #1534-D: (ULP 7.1) Detected use of global variable "ui_interface_id_pin" within one function "main". Recommend placing variable in the function locally
"../main.c", line 64: remark #1535-D: (ULP 8.1) variable "ui_interface_id_pin" is used as a constant. Recommend declaring variable as either 'static const' or 'const'
"../main.c", line 49: warning #179-D: variable "ui_fe_address_pin" was declared but never referenced
"C:/ti/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 334 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 335 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 336 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 337 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 338 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 339 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 341 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 342 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 343 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 344 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 345 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 346 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 347 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 348 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 349 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 351 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 352 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 353 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 355 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 356 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 357 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 359 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 360 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 361 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 363 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 364 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 365 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 366 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 367 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 368 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 374 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 375 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 376 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 377 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 378 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 379 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 396 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 398 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 400 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 404 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 406 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 413 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 415 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 417 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 421 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 423 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 430 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 432 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 434 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 438 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 440 (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
"../main.c", line 207 (col. 26): 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
"../main.c", line 470 (col. 41): 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
"../main.c", line 564 (col. 18): 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: "../main.c"
 
Building target: "MSP430_F5438A_Driver_error.out"
Invoking: MSP430 Linker
"C:/ti/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/bin/cl430" -vmspx --data_model=restricted --use_hw_mpy=F5 --advice:power=all --define=__MSP430F5438A__ -g --printf_support=minimal --diag_warning=225 --diag_wrap=off --display_error_number --silicon_errata=CPU21 --silicon_errata=CPU22 --silicon_errata=CPU23 --silicon_errata=CPU40 -z -m"MSP430_F5438A_Driver_error.map" --heap_size=160 --stack_size=160 --cinit_hold_wdt=on -i"C:/ti/ccs1110/ccs/ccs_base/msp430/include" -i"C:/ti/msp/MSP430Ware_3_80_14_01/driverlib/driverlib/MSP430F5xx_6xx" -i"C:/ti/ccs1110/ccs/ccs_base/msp430/lib/5xx_6xx_FRxx" -i"C:/ti/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/lib" -i"C:/ti/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include" --reread_libs --diag_wrap=off --display_error_number --warn_sections --xml_link_info="MSP430_F5438A_Driver_error_linkInfo.xml" --use_hw_mpy=F5 --rom_model -o "MSP430_F5438A_Driver_error.out" "./main.obj" "../lnk_msp430f5438a.cmd"  -llibmath.a -llibc.a 
<Linking>
 
 undefined                              first referenced
  symbol                                    in file     
 ---------                              ----------------
 GPIO_clearInterrupt                    ./main.obj      
 GPIO_disableInterrupt                  ./main.obj      
 GPIO_enableInterrupt                   ./main.obj      
 GPIO_getInputPinValue                  ./main.obj      
 GPIO_selectInterruptEdge               ./main.obj      
 GPIO_setAsInputPin                     ./main.obj      
 GPIO_setAsInputPinWithPullDownResistor ./main.obj      
 GPIO_setAsInputPinWithPullUpResistor   ./main.obj      
 GPIO_setAsOutputPin                    ./main.obj      
 GPIO_setOutputHighOnPin                ./main.obj      
 GPIO_setOutputLowOnPin                 ./main.obj      
 GPIO_toggleOutputOnPin                 ./main.obj      
 Timer_B_clear                          ./main.obj      
 Timer_B_clearTimerInterrupt            ./main.obj      
 Timer_B_initUpMode                     ./main.obj      
remark #10371-D: (ULP 1.1) Detected no uses of low power mode state changing instructions
 WDT_A_hold                             ./main.obj      
remark #10372-D: (ULP 4.1) Detected uninitialized Port A in this project. Recommend initializing all unused ports to eliminate wasted current consumption on unused pins.
remark #10372-D: (ULP 4.1) Detected uninitialized Port B in this project. Recommend initializing all unused ports to eliminate wasted current consumption on unused pins.
remark #10372-D: (ULP 4.1) Detected uninitialized Port C in this project. Recommend initializing all unused ports to eliminate wasted current consumption on unused pins.
remark #10372-D: (ULP 4.1) Detected uninitialized Port D in this project. Recommend initializing all unused ports to eliminate wasted current consumption on unused pins.
remark #10372-D: (ULP 4.1) Detected uninitialized Port E in this project. Recommend initializing all unused ports to eliminate wasted current consumption on unused pins.
remark #10372-D: (ULP 4.1) Detected uninitialized Port F in this project. Recommend initializing all unused ports to eliminate wasted current consumption on unused pins.
 
>> Compilation failure
makefile:142: recipe for target 'MSP430_F5438A_Driver_error.out' failed
 
error #10234-D: unresolved symbols remain
error #10010: errors encountered during linking; "MSP430_F5438A_Driver_error.out" not built
gmake[1]: *** [MSP430_F5438A_Driver_error.out] Error 1
gmake: *** [all] Error 2
makefile:138: recipe for target 'all' failed

**** Build Finished ****

0 Swamy Jagannatham over 3 years ago in reply to Swamy Jagannatham

Prodigy 80 points

1212.SSJ_build_console_output_01b.txt

Fullscreen

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
**** Build of configuration Debug for project MSP430_F5438A_Driver_error ****
"C:\\ti\\ccs1110\\ccs\\utils\\bin\\gmake" -k -j 8 all -O 
 
Building file: "../main.c"
Invoking: MSP430 Compiler
"C:/ti/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/bin/cl430" -vmspx --data_model=restricted --use_hw_mpy=F5 --include_path="C:/ti/ccs1110/ccs/ccs_base/msp430/include" --include_path="C:/ti/msp/MSP430Ware_3_80_14_01/driverlib/driverlib/MSP430F5xx_6xx" --include_path="C:/ti/msp/MSP430Ware_3_80_14_01/driverlib/driverlib/MSP430F5xx_6xx/inc" --include_path="C:/Antenna_Luneburg_Lens/TI_Driver_error_WS/MSP430_F5438A_Driver_error" --include_path="C:/ti/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include" --advice:power=all --define=__MSP430F5438A__ -g --printf_support=minimal --diag_warning=225 --diag_wrap=off --display_error_number --silicon_errata=CPU21 --silicon_errata=CPU22 --silicon_errata=CPU23 --silicon_errata=CPU40 --preproc_with_compile --preproc_dependency="main.d_raw"  "../main.c"
"../main.c", line 475: warning #225-D: function "Latch_Enable" declared implicitly
"../main.c", line 94: warning #179-D: variable "atten_bit" was declared but never referenced
"../main.c", line 100: warning #179-D: variable "tmp_in" was declared but never referenced
"../main.c", line 127: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 132: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 144: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 196: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 204: remark #1544-D: (ULP 13.1) Detected loop counting up. Recommend loops count down as detecting zeros is easier
"../main.c", line 225: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 226: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 227: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 228: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

**** Build of configuration Debug for project MSP430_F5438A_Driver_error ****

"C:\\ti\\ccs1110\\ccs\\utils\\bin\\gmake" -k -j 8 all -O 
 
Building file: "../main.c"
Invoking: MSP430 Compiler
"C:/ti/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/bin/cl430" -vmspx --data_model=restricted --use_hw_mpy=F5 --include_path="C:/ti/ccs1110/ccs/ccs_base/msp430/include" --include_path="C:/ti/msp/MSP430Ware_3_80_14_01/driverlib/driverlib/MSP430F5xx_6xx" --include_path="C:/ti/msp/MSP430Ware_3_80_14_01/driverlib/driverlib/MSP430F5xx_6xx/inc" --include_path="C:/Antenna_Luneburg_Lens/TI_Driver_error_WS/MSP430_F5438A_Driver_error" --include_path="C:/ti/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include" --advice:power=all --define=__MSP430F5438A__ -g --printf_support=minimal --diag_warning=225 --diag_wrap=off --display_error_number --silicon_errata=CPU21 --silicon_errata=CPU22 --silicon_errata=CPU23 --silicon_errata=CPU40 --preproc_with_compile --preproc_dependency="main.d_raw"  "../main.c"
"../main.c", line 475: warning #225-D: function "Latch_Enable" declared implicitly
"../main.c", line 94: warning #179-D: variable "atten_bit" was declared but never referenced
"../main.c", line 100: warning #179-D: variable "tmp_in" was declared but never referenced
"../main.c", line 127: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 132: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 144: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 196: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 204: remark #1544-D: (ULP 13.1) Detected loop counting up. Recommend loops count down as detecting zeros is easier
"../main.c", line 225: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 226: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 227: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 228: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 230: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 231: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 260: remark #1544-D: (ULP 13.1) Detected loop counting up. Recommend loops count down as detecting zeros is easier
"../main.c", line 267: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 273: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 279: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 285: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 291: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 297: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 303: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 309: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 315: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 321: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 327: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 333: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 339: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 345: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 351: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 357: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 365: remark #1544-D: (ULP 13.1) Detected loop counting up. Recommend loops count down as detecting zeros is easier
"../main.c", line 367: remark #1544-D: (ULP 13.1) Detected loop counting up. Recommend loops count down as detecting zeros is easier
"../main.c", line 383: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 389: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 400: remark #1544-D: (ULP 13.1) Detected loop counting up. Recommend loops count down as detecting zeros is easier
"../main.c", line 432: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 436: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 451: remark #1544-D: (ULP 13.1) Detected loop counting up. Recommend loops count down as detecting zeros is easier
"../main.c", line 467: remark #1544-D: (ULP 13.1) Detected loop counting up. Recommend loops count down as detecting zeros is easier
"../main.c", line 225: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 226: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 227: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 228: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 230: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 231: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../main.c", line 489: warning #161-D: declaration is incompatible with previous "Latch_Enable" (declared at line 475)
"../main.c", line 497: remark #2553-D: (ULP 14.1) Array index (involving "rf_addr") of type "int". Recommend using "unsigned int"
"../main.c", line 498: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 499: remark #2553-D: (ULP 14.1) Array index (involving "rf_addr") of type "int". Recommend using "unsigned int"
"../main.c", line 503: remark #2553-D: (ULP 14.1) Array index (involving "rf_addr") of type "int". Recommend using "unsigned int"
"../main.c", line 507: remark #2553-D: (ULP 14.1) Array index (involving "rf_addr") of type "int". Recommend using "unsigned int"
"../main.c", line 514: remark #2553-D: (ULP 14.1) Array index (involving "rf_addr") of type "int". Recommend using "unsigned int"
"../main.c", line 515: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 516: remark #2553-D: (ULP 14.1) Array index (involving "rf_addr") of type "int". Recommend using "unsigned int"
"../main.c", line 520: remark #2553-D: (ULP 14.1) Array index (involving "rf_addr") of type "int". Recommend using "unsigned int"
"../main.c", line 524: remark #2553-D: (ULP 14.1) Array index (involving "rf_addr") of type "int". Recommend using "unsigned int"
"../main.c", line 553: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function GPIO_toggleOutputOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 555: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function GPIO_toggleOutputOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 556: remark #1530-D: (ULP 5.1) Detected modulo operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"../main.c", line 558: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 561: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function GPIO_toggleOutputOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 563: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function GPIO_getInputPinValue. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 564: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function pow. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 577: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function GPIO_setOutputLowOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 604: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function GPIO_toggleOutputOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 609: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function GPIO_setOutputLowOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 613: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function GPIO_setOutputHighOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 615: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function GPIO_toggleOutputOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 616: remark #1530-D: (ULP 5.1) Detected modulo operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
"../main.c", line 633: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 636: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function GPIO_setOutputLowOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 638: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function GPIO_setOutputLowOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 651: remark #1538-D: (ULP 10.1) ISR TIMERB0_ISR calls function Timer_B_clearTimerInterrupt. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 671: remark #1538-D: (ULP 10.1) ISR Port_1 calls function GPIO_selectInterruptEdge. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 672: remark #1538-D: (ULP 10.1) ISR Port_1 calls function GPIO_clearInterrupt. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 676: remark #1538-D: (ULP 10.1) ISR Port_1 calls function GPIO_selectInterruptEdge. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 677: remark #1538-D: (ULP 10.1) ISR Port_1 calls function GPIO_clearInterrupt. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 685: remark #1538-D: (ULP 10.1) ISR Port_1 calls function GPIO_toggleOutputOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 686: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 687: remark #1538-D: (ULP 10.1) ISR Port_1 calls function GPIO_toggleOutputOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 688: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
"../main.c", line 689: remark #1538-D: (ULP 10.1) ISR Port_1 calls function GPIO_setOutputLowOnPin. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 692: remark #1538-D: (ULP 10.1) ISR Port_1 calls function GPIO_clearInterrupt. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 696: remark #1538-D: (ULP 10.1) ISR Port_1 calls function GPIO_clearInterrupt. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 39: remark #1534-D: (ULP 7.1) Detected use of global variable "data_port" within one function "main". Recommend placing variable in the function locally
"../main.c", line 39: remark #1535-D: (ULP 8.1) variable "data_port" is used as a constant. Recommend declaring variable as either 'static const' or 'const'
"../main.c", line 57: remark #1534-D: (ULP 7.1) Detected use of global variable "ui_att_le" within one function "main". Recommend placing variable in the function locally
"../main.c", line 57: remark #1535-D: (ULP 8.1) variable "ui_att_le" is used as a constant. Recommend declaring variable as either 'static const' or 'const'
"../main.c", line 58: remark #1534-D: (ULP 7.1) Detected use of global variable "ui_rf_enable" within one function "main". Recommend placing variable in the function locally
"../main.c", line 58: remark #1535-D: (ULP 8.1) variable "ui_rf_enable" is used as a constant. Recommend declaring variable as either 'static const' or 'const'
"../main.c", line 59: remark #1535-D: (ULP 8.1) variable "ui_prog_sel" is used as a constant. Recommend declaring variable as either 'static const' or 'const'
"../main.c", line 60: remark #1534-D: (ULP 7.1) Detected use of global variable "ui_smartmotor5v" within one function "main". Recommend placing variable in the function locally
"../main.c", line 60: remark #1535-D: (ULP 8.1) variable "ui_smartmotor5v" is used as a constant. Recommend declaring variable as either 'static const' or 'const'
"../main.c", line 61: remark #1534-D: (ULP 7.1) Detected use of global variable "ui_att_values_sw_pin" within one function "main". Recommend placing variable in the function locally
"../main.c", line 61: remark #1535-D: (ULP 8.1) variable "ui_att_values_sw_pin" is used as a constant. Recommend declaring variable as either 'static const' or 'const'
"../main.c", line 62: remark #1534-D: (ULP 7.1) Detected use of global variable "ui_rf_enable_sw_pin" within one function "main". Recommend placing variable in the function locally
"../main.c", line 62: remark #1535-D: (ULP 8.1) variable "ui_rf_enable_sw_pin" is used as a constant. Recommend declaring variable as either 'static const' or 'const'
"../main.c", line 63: remark #1535-D: (ULP 8.1) variable "ui_set_enable_sw_pin" is used as a constant. Recommend declaring variable as either 'static const' or 'const'
"../main.c", line 64: remark #1534-D: (ULP 7.1) Detected use of global variable "ui_interface_id_pin" within one function "main". Recommend placing variable in the function locally
"../main.c", line 64: remark #1535-D: (ULP 8.1) variable "ui_interface_id_pin" is used as a constant. Recommend declaring variable as either 'static const' or 'const'
"../main.c", line 49: warning #179-D: variable "ui_fe_address_pin" was declared but never referenced
"C:/ti/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 334 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 335 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 336 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 337 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 338 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 339 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 341 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 342 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 343 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 344 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 345 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 346 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 347 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 348 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 349 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 351 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 352 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 353 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 355 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 356 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 357 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 359 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 360 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 361 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 363 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 364 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 365 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 366 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 367 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 368 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 374 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 375 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 376 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 377 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 378 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 379 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 396 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 398 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 400 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 404 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 406 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 413 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 415 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 417 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 421 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 423 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 430 (col. 37): 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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 432 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 434 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 438 (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/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include/_defs.h", line 440 (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
"../main.c", line 207 (col. 26): 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
"../main.c", line 470 (col. 41): 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
"../main.c", line 564 (col. 18): 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: "../main.c"
 
Building target: "MSP430_F5438A_Driver_error.out"
Invoking: MSP430 Linker
"C:/ti/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/bin/cl430" -vmspx --data_model=restricted --use_hw_mpy=F5 --advice:power=all --define=__MSP430F5438A__ -g --printf_support=minimal --diag_warning=225 --diag_wrap=off --display_error_number --silicon_errata=CPU21 --silicon_errata=CPU22 --silicon_errata=CPU23 --silicon_errata=CPU40 -z -m"MSP430_F5438A_Driver_error.map" --heap_size=160 --stack_size=160 --cinit_hold_wdt=on -i"C:/ti/ccs1110/ccs/ccs_base/msp430/include" -i"C:/ti/msp/MSP430Ware_3_80_14_01/driverlib/driverlib/MSP430F5xx_6xx" -i"C:/ti/ccs1110/ccs/ccs_base/msp430/lib/5xx_6xx_FRxx" -i"C:/ti/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/lib" -i"C:/ti/ccs1110/ccs/tools/compiler/ti-cgt-msp430_21.6.0.LTS/include" --reread_libs --diag_wrap=off --display_error_number --warn_sections --xml_link_info="MSP430_F5438A_Driver_error_linkInfo.xml" --use_hw_mpy=F5 --rom_model -o "MSP430_F5438A_Driver_error.out" "./main.obj" "../lnk_msp430f5438a.cmd"  -llibmath.a -llibc.a 
<Linking>
 
 undefined                              first referenced
  symbol                                    in file     
 ---------                              ----------------
 GPIO_clearInterrupt                    ./main.obj      
 GPIO_disableInterrupt                  ./main.obj      
 GPIO_enableInterrupt                   ./main.obj      
 GPIO_getInputPinValue                  ./main.obj      
 GPIO_selectInterruptEdge               ./main.obj      
 GPIO_setAsInputPin                     ./main.obj      
 GPIO_setAsInputPinWithPullDownResistor ./main.obj      
 GPIO_setAsInputPinWithPullUpResistor   ./main.obj      
 GPIO_setAsOutputPin                    ./main.obj      
 GPIO_setOutputHighOnPin                ./main.obj      
 GPIO_setOutputLowOnPin                 ./main.obj      
 GPIO_toggleOutputOnPin                 ./main.obj      
 Timer_B_clear                          ./main.obj      
 Timer_B_clearTimerInterrupt            ./main.obj      
 Timer_B_initUpMode                     ./main.obj      
remark #10371-D: (ULP 1.1) Detected no uses of low power mode state changing instructions
 WDT_A_hold                             ./main.obj      
remark #10372-D: (ULP 4.1) Detected uninitialized Port A in this project. Recommend initializing all unused ports to eliminate wasted current consumption on unused pins.
remark #10372-D: (ULP 4.1) Detected uninitialized Port B in this project. Recommend initializing all unused ports to eliminate wasted current consumption on unused pins.
remark #10372-D: (ULP 4.1) Detected uninitialized Port C in this project. Recommend initializing all unused ports to eliminate wasted current consumption on unused pins.
remark #10372-D: (ULP 4.1) Detected uninitialized Port D in this project. Recommend initializing all unused ports to eliminate wasted current consumption on unused pins.
remark #10372-D: (ULP 4.1) Detected uninitialized Port E in this project. Recommend initializing all unused ports to eliminate wasted current consumption on unused pins.
remark #10372-D: (ULP 4.1) Detected uninitialized Port F in this project. Recommend initializing all unused ports to eliminate wasted current consumption on unused pins.
 
>> Compilation failure
makefile:142: recipe for target 'MSP430_F5438A_Driver_error.out' failed
 
error #10234-D: unresolved symbols remain
error #10010: errors encountered during linking; "MSP430_F5438A_Driver_error.out" not built
gmake[1]: *** [MSP430_F5438A_Driver_error.out] Error 1
gmake: *** [all] Error 2
makefile:138: recipe for target 'all' failed

**** Build Finished ****

0 Swamy Jagannatham over 3 years ago in reply to Swamy Jagannatham

Prodigy 80 points

5265.SmartMot_RBSB_Interface_v1pt1_copy_Build Output_01a.txt

0 Swamy Jagannatham over 3 years ago in reply to Swamy Jagannatham

Prodigy 80 points

I am not sure if I have downloaded the two files correctly or not.

Please let me know if I need to re-upload any of the two files.

Thanks

0 Swamy Jagannatham over 3 years ago in reply to Swamy Jagannatham

Prodigy 80 points

SmartMot_RBSB_Interface_v1pt1_copy Build Output.txt

0 Swamy Jagannatham over 3 years ago in reply to Swamy Jagannatham

Prodigy 80 points

Following compact project explorer of my colleague:

0 Swamy Jagannatham over 3 years ago in reply to Swamy Jagannatham

Prodigy 80 points

Hi Evan,

Any information to fix these link errors please?

Thanks

0 Marvn Arcangel over 3 years ago in reply to Evan Lew

TI__Genius 11655 points

Hi Evan,

I have the build configuration as requested. I sent it to you via email.

Regards,

Marvin

0 Evan Lew over 3 years ago in reply to Marvn Arcangel

TI__Genius 10010 points

Thanks Marvin

0 Evan Lew over 3 years ago in reply to Swamy Jagannatham

TI__Genius 10010 points

Hi Swamy Jagannatham,

I think the problem is coming from the fact that you don't have the correct driverlib assets copied in your project. Have you installed MSPWare (https://www.ti.com/tool/MSPWARE)?

Follow these steps:

1. Import a driverlib example into CCS (Project > Import CCS Projects > Browser to C:\ti\msp430ware_3_80_14_01\driverlib\examples\MSP430F5xx_6xx\adc12_a or your installation direcotry

2. Copy the "driverlib" directory fron the adc12_a project into your project

3. Clean and build you project

I was able to convert a non-driverlib project to a driverlib project following those steps. I will also file a ticket with our team to find out why the steps described in the PDF didn't work.

Evan

0 Swamy Jagannatham over 3 years ago in reply to Evan Lew

Prodigy 80 points

Hi Evan,

Thank you very much for the steps above.

I am working to follow the steps. My colleague and I have difficulty in using the steps in my CCS.

At present my colleague and I are doing some steps to see if we will be successfully build the project.

I will you know if we can resolve the difficulties.

Thanks and best regards,

SSJ

0 Swamy Jagannatham over 3 years ago in reply to Swamy Jagannatham

Prodigy 80 points

Hi Evan,

Is it possible for us to connect on-line, so I can share my screen while I create and build my project, so that you can see my screen and correct my steps, please?

Thanks,

SSJ

0 Evan Lew over 3 years ago in reply to Swamy Jagannatham

TI__Genius 10010 points

Hi Swamy Jagannatham,

Apologies, but I'm only able to provide support via the forum at this time. Please help me understand the following:

Do you have MSPWare installed? If not please install from here https://www.ti.com/tool/MSPWARE
Are you able to import and build the adc12_a project using steps described above? If not then we need to figure out what is wrong with your CCS/MSPWare installation.
Please described the steps you are taking to create and build your project

Regards,

Evan

0 Swamy Jagannatham over 3 years ago in reply to Evan Lew

Prodigy 80 points

Hi Evan,

I have installed MSPWare and CCS on a new laptop. Created CCS project and captured screen of each step and saved to an rtf (Microsoft Wordpad) file.

It is huge 44 MB. So I could not email the huge file. I split it into ten smaller rtf files and emailed to Marvin (Tech Support) in ten emails.

Hopefully Marvin will email the 10 files to you soon.

Is there a way to attach Wordpad (rtf) or MS Word (.doc) file to this forum please?

Thanks and best regards,

SSJ

0 Swamy Jagannatham over 3 years ago in reply to Swamy Jagannatham

Prodigy 80 points

CCS_Project_Steps_01m_part_1.rtf

0 Swamy Jagannatham over 3 years ago in reply to Swamy Jagannatham

Prodigy 80 points

CCS_Project_Steps_01m_part_2.rtf

0 Swamy Jagannatham over 3 years ago in reply to Swamy Jagannatham

Prodigy 80 points

CCS_Project_Steps_01m_part_3.rtf

0 Swamy Jagannatham over 3 years ago in reply to Swamy Jagannatham

Prodigy 80 points

CCS_Project_Steps_01m_part_4.rtf

0 Swamy Jagannatham over 3 years ago in reply to Swamy Jagannatham

Prodigy 80 points

CCS_Project_Steps_01m_part_5.rtf

0 Swamy Jagannatham over 3 years ago in reply to Swamy Jagannatham

Prodigy 80 points

CCS_Project_Steps_01m_part_6.rtf

0 Swamy Jagannatham over 3 years ago in reply to Swamy Jagannatham

Prodigy 80 points

CCS_Project_Steps_01m_part_7.rtf

0 Swamy Jagannatham over 3 years ago in reply to Swamy Jagannatham

Prodigy 80 points

CCS_Project_Steps_01m_part_8.rtf

0 Swamy Jagannatham over 3 years ago in reply to Swamy Jagannatham

Prodigy 80 points

CCS_Project_Steps_01m_part_9.rtf

0 Swamy Jagannatham over 3 years ago in reply to Swamy Jagannatham

Prodigy 80 points

CCS_Project_Steps_01m_part_10.rtf

0 Swamy Jagannatham over 3 years ago in reply to Swamy Jagannatham

Prodigy 80 points

Good morning Evan,

Sorry for ten posts. Please look at the steps and give detailed steps so that I create the project without build errors.

Thanks and best regards,

SSJ

0 Evan Lew over 3 years ago in reply to Swamy Jagannatham

TI__Genius 10010 points

Hi Swamy Jagannatham,

I read through your steps. I didn't see you ever copy the driverlib into your project. If you don't do this CCS wont build the driverlib c assets and the linker will fail. Please make sure you follow step 2 in my post above which I've quoted below. The only reason I had you follow step 1 was so you had an easy place to copy the driverlib folder from.

Evan Lew said:
1. Import a driverlib example into CCS (Project > Import CCS Projects > Browser to C:\ti\msp430ware_3_80_14_01\driverlib\examples\MSP430F5xx_6xx\adc12_a or your installation direcotry

2. Copy the "driverlib" directory fron the adc12_a project into your project

3. Clean and build you project

Your project should have a folder called "driverlib" in it, see my screenshot below: