Table of Contents
This section describes the MSP430-specific extensions to the GNU toolset. You should refer to the GNU documentation for information about the standard features of the GNU tools.
The compiler recognises the following MSP430 specific command line parameters:
-mmcu= | Specify the MCU name |
-mno-volatile-workaround | Do not perform a volatile workaround for bitwise operations. |
-mno-stack-init | Do not initialise the stack as main() starts. |
-minit-stack= | Specify the initial stack address. |
-mendup-at= | Jump to the specified routine at the end of main(). |
-mforce-hwmul | Force use of a hardware multiplier. |
-mdisable-hwmul | Do not use the hardware multiplier. |
-minline-hwmul | Issue inline code for 32-bit integer operations for devices with a hardware multiplier. |
-mnoint-hwmul | Do not disable and enable interrupts around hardware multiplier operations. This makes multiplication faster when you are certain no hardware multiplier operations will occur at deeper interrupt levels. |
-mcall-shifts | Use subroutine calls for shift operations. This may save some space for shift intensive applications. |
The following MCU names are currently recognised for the “-mmcu” parameter:
msp1 | msp2 | |||
msp430x110 | msp430x112 | |||
msp430x1101 | ||||
msp430x1111 | msp430x1121 | |||
msp430x122 | msp430x123 | |||
msp430x1222 | msp430x1232 | |||
msp430x133 | msp430x135 | |||
msp430x1331 | msp430x1351 | |||
msp430x147 | msp430x148 | msp430x149 | ||
msp430x1471 | msp430x1481 | msp430x1491 | ||
msp430x155 | msp430x156 | msp430x157 | ||
msp430x167 | msp430x168 | msp430x169 | msp430x1610 | msp430x1611 |
msp430x311 | msp430x312 | msp430x313 | msp430x314 | msp430x315 |
msp430x323 | msp430x325 | msp430x336 | msp430x337 | |
msp430x412 | msp430x413 | |||
msp430xE423 | msp430xE425 | msp430xE427 | ||
msp430xW423 | msp430xW425 | msp430xW427 | ||
msp430x435 | msp430x436 | msp430x437 | ||
msp430x447 | msp430x448 | msp430x449 |
“msp1” means an MCU without a hardware multiplier. “msp2” means an MCU with a hardware multiplier. These can be useful to make the compiler generate the correct code for a new device, before it is fully supported.