11.07.2015 Views

MSP430 IAR C/C++ Compiler reference guide - Rice University

MSP430 IAR C/C++ Compiler reference guide - Rice University

MSP430 IAR C/C++ Compiler reference guide - Rice University

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Getting startedSPECIAL FUNCTION TYPESThe special hardware features of the <strong>MSP430</strong> microcontroller are supported by thecompiler’s special function types: interrupt, monitor, task, and raw. You can write acomplete application without having to write any of these functions in assemblerlanguage.For detailed information, see Primitives for interrupts, concurrency, and OS-relatedprogramming, page 23.HEADER FILES FOR I/OStandard peripheral units are defined in device-specific I/O header files callediodevice.h. The product package supplies I/O files for all devices that are available atthe time of the product release. You can find these files in the 430\inc directory. Makesure to include the appropriate include file in your application source files. If you needadditional I/O header files, they can easily be created using one of the provided ones asa template.Note that header files named like msp430device.h are available for backwardscompatibility.For an example, see Accessing special function registers, page 127.ACCESSING LOW-LEVEL FEATURESFor hardware-related parts of your application, accessing low-level features is essential.The <strong>MSP430</strong> <strong>IAR</strong> C/<strong>C++</strong> <strong>Compiler</strong> supports several ways of doing this: intrinsicfunctions, mixing C and assembler modules, and inline assembler. For informationabout the different methods, see Mixing C and assembler, page 83.Part 1. Using the compiler11

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!