This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TI 430 warning and error codes and solutions

Other Parts Discussed in Thread: MSP430FR4133

Greetings all;

I'm compiling the "Out Of Box MSP430FR4133" project and I get these errors:
BTW This list was shortened to remove duplicate error tags and all of them
repeat more then once..

>> WARNING: --near_data is only applicable for large data models. Option ignored.
"../StopWatchMode.c", line 127: 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
"../StopWatchMode.c", line 158: remark #1530-D: (ULP 5.1) Detected divide operation(s). Recommend moving them to RAM during run time or not using as these are processing/power intensive
Finished building: ../StopWatchMode.c

>> WARNING: --near_data is only applicable for large data models. Option ignored.
"../TempSensorMode.c", line 53: warning #145-D: a value of type "volatile unsigned int *" cannot be used to initialize an entity of type "volatile int *"
"../TempSensorMode.c", line 129: remark #1527-D: (ULP 2.1) Detected SW delay loop using __delay_cycles. Recommend using a timer module instead
"../TempSensorMode.c", line 144: remark #1533-D: (ULP 6.1) Detected use of multiplication on a device that has no hardware multiplier
Finished building: ../TempSensorMode.c

>> WARNING: --near_data is only applicable for large data models. Option ignored.
"../hal_LCD.c", line 101: remark #1546-D: (ULP 15.1) Detected consecutive bitfield assigns. Recommend using bit mask instead
"../hal_LCD.c", line 141: remark #1544-D: (ULP 13.1) Detected loop counting up. Recommend loops count down as detecting zeros is easier
"../hal_LCD.c", line 147: remark #2553-D: (ULP 14.1) Array index (involving "t") of type "int". Recommend using "unsigned int"
"../hal_LCD.c", line 152: remark #1545-D: (ULP 14.1) Array index of type "int". Recommend using "unsigned int"
"../hal_LCD.c", line 163: remark #1527-D: (ULP 2.1) Detected SW delay loop using __delay_cycles. Recommend using a timer module instead
"../hal_LCD.c", line 140: remark #1535-D: (ULP 8.1) variable "buffer" is used as a constant. Recommend declaring variable as either 'static const' or 'const'
"../hal_LCD.c", line 152: remark #1545-D: (ULP 14.1) Array index of type "int". Recommend using "unsigned int"
"../hal_LCD.c", line 186: remark #2553-D: (ULP 14.1) Array index (involving "position") of type "int". Recommend using "unsigned int"
Finished building: ../hal_LCD.c

>> WARNING: --near_data is only applicable for large data models. Option ignored.
"../main.c", line 249: remark #1538-D: (ULP 10.1) ISR PORT1_ISR calls function RTC_start. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 251: remark #1538-D: (ULP 10.1) ISR PORT1_ISR calls function RTC_stop. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 260: remark #1538-D: (ULP 10.1) ISR PORT1_ISR calls function Timer_A_initUpMode. Recommend moving function call away from ISR, or inlining the function, or using pragmas
"../main.c", line 301: remark #1538-D: (ULP 10.1) ISR PORT2_ISR calls function resetStopWatch. Recommend moving function call away from ISR, or inlining the function, or using pragmas
Finished building: ../main.c

>> WARNING: --near_data is only applicable for large data models. Option ignored.
"../driverlib/MSP430FR2xx_4xx/cs.c", line 427: remark #1535-D: (ULP 8.1) variable "dco_FLLD" is used as a constant. Recommend declaring variable as either 'static const' or 'const'
Finished building: ../driverlib/MSP430FR2xx_4xx/cs.c

>> WARNING: --near_data is only applicable for large data models. Option ignored.
"../driverlib/MSP430FR2xx_4xx/eusci_a_uart.c", line 56: remark #1535-D: (ULP 8.1) variable "retVal" is used as a constant. Recommend declaring variable as either 'static const' or 'const'
"../driverlib/MSP430FR2xx_4xx/eusci_a_uart.c", line 122: remark #1528-D: (ULP 3.1) Detected flag polling using UCTXIFG. Recommend using an interrupt combined with enter LPMx and ISR
Finished building: ../driverlib/MSP430FR2xx_4xx/eusci_a_uart.c

>> WARNING: --near_data is only applicable for large data models. Option ignored.
"../driverlib/MSP430FR2xx_4xx/eusci_b_i2c.c", line 208: remark #1528-D: (ULP 3.1) Detected flag polling using UCTXIFG. Recommend using an interrupt combined with enter LPMx and ISR
"../driverlib/MSP430FR2xx_4xx/eusci_b_i2c.c", line 541: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
Finished building: ../driverlib/MSP430FR2xx_4xx/eusci_b_i2c.c

>> WARNING: --near_data is only applicable for large data models. Option ignored.
<Linking>
warning #10420-D: For FRAM devices, at start up, the GPO power-on default high-impedance mode needs to be disabled to activate previously configured port settings. This can be done by clearing the LOCKLPM5 bit in PM5CTL0 register.
remark #10205-D: automatic RTS selection:  linking in "rts430_eabi.lib" in place of index library "libc.a"
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.
Finished building target: OutOfBox_MSP430FR4133.out

I realize that the (ULP) is for the Ultra Low Power adviser. So my question is how do I assign these
variable to different areas of ram to satisfy the ULP?
Also is there a reference for all of the warning and error codes that can be produced by the compiler
and linker?
BTW don't advise about the ">> WARNING: --near_data is only applicable for large data models. Option ignored." I already know what caused that.


Thanks J.B.G.

  • James Grieger said:
    I'm compiling the "Out Of Box MSP430FR4133" project and I get these errors:

    It is likely this project was never tested against more recent versions of the compiler.

    James Grieger said:
    >> WARNING: --near_data is only applicable for large data models. Option ignored.

    You must use --data_model=small in combination with some setting of --near_data.  Unfortunately, the only way to avoid the diagnostic is to change the --data_model setting, or remove --near_data.

    James Grieger said:
    I realize that the (ULP) is for the Ultra Low Power adviser. So my question is how do I assign these
    variable to different areas of ram to satisfy the ULP?

    My understanding of the ULP diagnostics is very incomplete.  But I have the impression that changing the memory configuration won't affect things much.

    To learn more about the ULP diagnostics, please see the section titled Using the ULP Advisor in the MSP430 compiler manual.

    Thanks and regards,

    -George