<< Chapter < Page Chapter >> Page >
Using the MSP-EXP430FG4618 Development Tool and the MSP430FG4618 device analyse the MSP430’s performance when makes a multiplication operation with the hardware multiplier. Two different situations are analysed: - Using the “*” operator; - Accessing the hardware multiplier registers directly. The execution time is measured with an oscilloscope.

Laboratory hardware multiplier: lab2 - multiplication with hardware multiplier

Introduction

This laboratory explores the hardware multiplier peripheral. It is composed of three different tasks, each of which evaluates a different characteristic of the hardware multiplier peripheral:

- Multiplication operation execution time, with and without the hardware multiplier.

-Differences between the use of the operator “*” and direct write to the hardware multiplier registers.

- Task operational analysis, in which the active power and the RMS value of an electrical system are calculated.

Overview

This laboratory explores and analyses the MSP430’s performance when it performs multiply operations using the hardware multiplier peripheral. Two different variants are analysed:

- Using the “*” operator;

-Accessing the hardware multiplier registers directly.

The execution times are measured with an oscilloscope.

Resources

This laboratory only uses Port P2.1 connected to LED2 in order to measure the execution time of the multiplication operation, when it is performed by the hardware multiplier.

The default configuration of the FLL+ is used. All the clock signals required for the operation of the components of the device take their default values.

Software application organization

The application begins by stopping the Watchdog Timer;

Port P2.1 is configured as an output with the pin at a low level;

The code can be broken down into two parts:

- In the first part of the code, the multiplication is performed with the “*” operator. This task is performed between P2.1 toggles, in order to determine the time required to perform this operation;

- The remaining part of the code is separated by some _NOP() operations. This coding allows analysis of the execution time using an oscilloscope. Here, the multiplication operation is performed by directly accessing the hardware multiplier registers. The multiplication of the variables is performed between toggle P2.1 instructions;

This application ends with the device entering low power mode LPM4.

System configuration

Go to Properties>TI Debug Settings and select the Target tab. Uncheck the automatically step over functions without debug information when source stepping in order to allow stepping into the multiply routine;

Go to Properties>C/C++ Build>Linker MSP430 Linker v3.0>General options and choose the option 16 (default) at the Link in hardware version of RTS mpy routine . With this linker option, the application ( Lab2_HM.c ) will be built with the 16-bit hardware multiplier peripheral contained in the Experimenter’s board.

Rebuild the project and download to the target.

Analysis of operation

Analysis of hardware multiply routine with the “*” operator

- Connect the oscilloscope probe to port P2.1, which is connected to Header 4 pin 2;

- Put the cursor at line of code 55 { c = a*b } and Run to line ;

- Go to Disassembly view and switch to mixed disassembly view in order to show both C and Assembly code;

- Observe that the variables a and b are passed to registers and #__mpyi_hw routine is called;

- Run the code step-by-step with the Disassembly view active. This action will lead to the multiply operation being performed by the hardware multiplier;

- As the hardware multiply routine source code is not available, switch to Assembly view only;

- The routine starts by pushing the Status Register onto the system stack ( PUSH instruction) and disabling the interrupts (this always occurs when using the hardware multiplier peripheral);

- The next line of code exchanges data with the hardware multiplier;

- Then the SR is popped ( POP instruction) from the system stack, restoring the system environment (data interrupt state restored);

- The routine finishes with a RETA instruction.

Analysis of hardware multiply operation with direct registers access

- Switch to the C view;

- Put the cursor at line of code 72 { MPY = a } and Run to line ;

- The routine call operation is avoided, as shown in the Disassembly view. This exemplifies an energy saving procedure because it shows how less CPU clock cycles can be used.

Measurement of execution time of the multiply operation

- Restart the application. It will run from the beginning;

- Put the cursor at line of code 77 {_BIS_SR(LPM4) } and Run to line ;

- Measure the pulse widths using the oscilloscope;

- The first time pulse corresponds to the hardware multiply routine with the operator “*”, and has a width of 42 μsec;

- The second time pulse corresponds to the hardware multiply register operation and has a width of 19 μsec;

- Comparing both time pulses and the time pulse obtained in Lab1: Multiplication without the hardware multiplier , it can be seen that with the hardware multiplier there is a significant reduction of the time required to perform a multiply operation;

- The smaller time pulse corresponds to the hardware multiply operation writing directly to the hardware multiplier registers. This reduction in time means less power consumption, which is very useful for the design of low-power applications.

This example and many others are available on the MSP430 Teaching ROM.

Request this ROM, and our other Teaching Materials here (External Link)

Get Jobilize Job Search Mobile App in your pocket Now!

Get it on Google Play Download on the App Store Now




Source:  OpenStax, Teaching and classroom laboratories based on the “ez430” and "experimenter's board" msp430 microcontroller platforms and code composer essentials. OpenStax CNX. May 19, 2009 Download for free at http://cnx.org/content/col10706/1.3
Google Play and the Google Play logo are trademarks of Google Inc.

Notification Switch

Would you like to follow the 'Teaching and classroom laboratories based on the “ez430” and "experimenter's board" msp430 microcontroller platforms and code composer essentials' conversation and receive update notifications?

Ask