AVR32000 Datasheet | Atmel

Features - - - - - Register and Bit-Name Definitions Use of Bit-field and Bit-mask Use of type definitions Use of Macros Deviance Between Hardware Registers and Header Register Naming 32-bit Microcontrollers 1 Introduction The purpose of this application note is to give new users a basic introduction to the header files for AVR®32 microcontrollers. The usage of I/O registers, bit-names and module type definitions. It will also cover more advanced usage of the header files like the I/O modules structures. This application note is specific for IAR Systems® AVR32 piler and GNU GCC for AVR32 piler. .. Rev. 32005A-AVR32-05/06 2 Register and Bit-Name Definitions The header files for AVR32 are split into many small files. One header file defines the core and one header file defines each module. This eases the portability of the code to other devices because the source code does not have to know which version of a module is used in a specific device, the only necessary include is the unique device header file. All code, which includes a device module, must start by including the io header file for the AVR32 devices. The io header file for devices uses the following convention: avr32/io.h The io.h header file knows the target device by a flag passed to the piler. Within the io.h file the devices and their specific header file are included, which includes and defines all modules available for the target device. This eases the users need to know what the include file for a specific module is named, since all defines for a module are present by including a single general header file. Registers are named as they are given in the datasheet, and extended with a defined prefix. Naming of registers use the following convention: AVR32_<module name>_<register name> Example for USART control register: AVR32_USART_CR Bit-field names are named as they are given in the datasheet including a prefix. Naming of bit-fields use the following convention: AVR32_<module name>_<register...