ULP Advisor > Rule 6.1 Avoid multiplication on devices without hardware multiplier

ULPAdvisorBanner.PNG

ULP Advisor - Rule Table

ULP 1.1 Ensure LPM usage
ULP 2.1 Leverage timer module for delay loops
ULP 3.1 Use ISRs instead of flag polling
ULP 4.1 Terminate unused GPIOs
ULP 5.1 Avoid processing-intensive operations: modulo, divide.
ULP 5.2 Avoid processing-intensive operations: floating point
ULP 5.3 Avoid processing-intensive operations: (s)printf()
ULP 6.1 Avoid multiplication on devices without hardware multiplier
ULP 6.2 Use MATHLIB for complex math operations
ULP 6.3 Use Low Energy Accelerator (LEA) software library
ULP 7.1 Use local instead of global variables where possible
ULP 8.1 Use 'static' & 'const' modifiers for local variables
ULP 9.1 Use pass by reference for large variables
ULP 10.1 Minimize function calls from within ISRs
ULP 11.1 Use lower bits for loop program control flow
ULP 11.2 Use lower bits for port bit-banging
ULP 12.1 Use DMA for large memcpy() calls
ULP 12.1b Use DMA for potentially large memcpy() calls
ULP 12.2 Use DMA for repetitive transfer
ULP 13.1 Count down in loops
ULP 14.1 Use unsigned variables for indexing
ULP 15.1 Use bit-masks instead of bit-fields

Let us know what you think! Feedback, suggestions & comments
are welcome @ ULPAdvisorFeedback@list.ti.com

What it means

On MSP430 microcontrollers without a multiplier hardware module (MPY), any complex multiplications (not with a power of 2) require the compiler to generate extra code to simulate the multiplication algorithm. This could potentially add significant amount of code instructions to the program.

Risks, Severity

In MSP430 devices without a hardware multiplier module, multiply operations are translated into multiply algorithms in assembly code by the compiler. While modern compilers can help generate highly efficient code for mathematical operations, the resultant assembly codes are still typically process-intensive. This results in additional power consumed as well as time needed to execute the additional code. The impact significantly increases if the multiplication takes place inside a loop or as part of the program's regular routine.

Why it is happening

The project is configured for an MSP430 device that does not have a hardware multiplier module and the code contains at least more multiplication(s).

Remedy

If possible, re-architect the program to minimize or remove all multiplications from the code. If the device is part of a more complex system, try to off-load the math-intensive processing to a host/better-equipped processor. For the unavoidable multiply operations, try to ensure that multiplications are replaced by equivalent bit-wise logical operation (rotate, shift, add), whether automatically by the compiler or manually by user-generated code.

Code Example

See the rest of the code examples for all MSP430 devices here!

More Resources

Want to squeeze a few more nanoAmps out of your application? Leverage the e2e (Engineer-to-Engineer) online community to get all of your ULP questions answered! Or, if you are an Ultra-Low Power pro, give back to the community with your expertise.

Go to MSP430's e2e online forum! 

If you are posting on the forums in relation to this rule, try using the tag "ULP_6.1"

E2e.jpg For technical support please post your questions at http://e2e.ti.com. Please post only comments about the article Compiler/diagnostic messages/MSP430/1533 here.