12
Atmel AVR32931
32162A-AVR-03/11
7 How to compile example projects
The compilers generate two files when compiling a project. The “hex” file contains the
actual data that will be programmed into the device. This hex file can be programmed
into the device using one of the programmers listed in Section
2.6
, or by using the
preprogrammed bootloader.
The other file generated is a debug file, which contains both the data to be
programmed into the device and also debug information to make the code readable
during debugging. This file can be opened in
Atmel AVR32 Studio
for single stepping
and debugging. The file extension of the debug file depends on the compiler, and will
be .elf for the
Atmel AVR32 GNU Toolchain
and .dbg or .d82 for the IAR toolchain.
7.1 AVR GNU Toolchain
To make this project using
AVR32 GNU Toolchain
, open the shell/dos prompt and
navigate to the gcc subfolder. Type “make,” and press enter. The binary and debug
files are created as:
avr32_applications_uc3-l0_xplained-
demo_at32uc3l064_uc3_l0_xplained.hex
avr32_applications_uc3-l0_xplained-
demo_at32uc3l064_uc3_l0_xplained.elf
7.2 IAR Embedded Workbench
To open the project in IAR, navigate to the iar subfolder and open the project:
avr32_applications_uc3-l0_xplained-
demo_at32uc3l064_uc3_l0_xplained.eww
The project can be compiled by pressing the F7 key on the keyboard, or select
“make” from the project menu. The binary and debug files are created as:
avr32_applications_uc3-l0_xplained-
demo_at32uc3l064_uc3_l0_xplained.a82
avr32_applications_uc3-l0_xplained-
demo_at32uc3l064_uc3_l0_xplained.d82
