Building the applications

All example applications contain precompiled hex-files that can be downloaded and run out-of-the-box.

In order to rebuild any of the applications for any desired hardware platform one of the following three ways described in the subsequent sections can be chosen generally.

8.2.1 Using GCC makefiles

Each application can be rebuilt using the provided Makefiles. Please follow the procedure as described:

• Change to the directory where the Makefile for the desired platform of the corresponding application is located, for example:

cd Applications\MAC_Examples\Promiscuous_Mode_Demo cd AT86RF212_ATMEGA1281_RCB_5_3_SENS_TERM_BOARD cd GCC

• Run the desired Makefile, for example:

make –f Makefile

or

NOTE Makefile builds a binary optimized for code size without Serial I/O support, whereas Makefile_Debug builds a version for better debug support without optimization but with additional Serial I/O support

• After running one of the Makefiles the same directory contains both a hex-file and an elf-file which can be downloaded onto the hardware (see Section 8.3)

• The above procedure for building the Makefiles is common for Atmel AVR8, Atmel AVR32, and ARM Platforms

8.2.2 Using AVR Studio 4

Each application can be rebuilt using the Atmel AVR Studio directly. Please follow the procedure as described:

• Change to the directory where the AVR Studio project file (aps-file) for the desired platform of the corresponding application is located, for example:

cd Applications\MAC_Examples\Promiscuous_Mode_Demo cd AT86RF212_ATMEGA1281_RCB_5_3_SENS_TERM_BOARD

• Double click on the corresponding AVR Studio 4 Project file (aps-file), for example Promiscuous_Mode_Demo.aps

• Select the desired configuration (Release or Debug). Depending on the selected configuration the corresponding external Makefile is chosen during the build process. These Makefiles are exactly those Makefiles (located in subdirectory GCC) that are used to build the application from command line (see Section 8.2.1) • Rebuild the entire application in AVR Studio 4

• After building the application the subdirectory GCC contains both a hex-file and an elf-file which can be downloaded onto the hardware (see Section 8.3)

8.2.3 Using AVR Studio 5

Each application can be rebuilt using the Atmel AVR Studio 5 directly. Please follow the procedure as described:

• Change to the directory where the AVR Studio 5 project file (avrsln-file) for the desired platform of the corresponding application is located, for example:

cd Applications\MAC_Examples\Promiscuous_Mode_Demo cd AT86RF212_ATMEGA1281_RCB_5_3_SENS_TERM_BOARD

• Double click on the corresponding AVR Studio 5 solution file (avrsln-file), for example Promiscuous_Mode_Demo.avrsln

• Select the desired configuration (Release or Debug). Depending on the selected configuration the corresponding external Makefile is chosen during the build process. These Makefiles are exactly those Makefiles (located in subdirectory GCC) that are used to build the application from command line (see section 8.2.1). • Rebuild the entire application in AVR Studio 5

• After building the application the subdirectory GCC contains executable files and hex-file which can be downloaded onto the hardware (see section 8.3)

8.2.4 Using IAR Embedded Workbench

Each application can be rebuilt using the IAR Embedded Workbench directly. Please follow the procedure as described:

• Change to the directory where the IAR Embedded Workbench workspace file (eww-file) for the desired platform of the corresponding application is located, for example:

cd Applications\MAC_Examples\Promiscuous_Mode_Demo cd AT86RF212_ATMEGA1281_RCB_5_3_SENS_TERM_BOARD

• Double click on the corresponding IAR Embedded Workbench file (eww-file), for example Promiscuous_Mode_Demo.eww

• Select the desired workspace (Release or Debug) and Rebuild the entire application in IAR Embedded Workbench

• After building the application the subdirectory IAR/Exe contains either an a90-file (in case the Release configuration was selected) or a d90-file (in case a Debug configuration was selected). Both binaries can be downloaded onto the hardware (see Section 8.3)

• The Release configuration binary (a90-file) can both be downloaded using IAR Embedded Workbench directly or AVR Studio

• The Debug configuration binary (d90-file) can only be downloaded using IAR Workbench and can be debugged using IAR C-Spy®

• In case is it desired to create a binary with IAR Embedded Workbench, which contains AVR Studio Debug information and can thus directly be downloaded and debugged using AVR Studio, the following changes need to be done with IAR Embedded Workbench:

o Select the Debug configuration o Open the “Options” dialog o Select “Category” “Linker” o Select tab “Output”

o Change “Format” from “Debug information for C-Spy” to “Other” o Select “ubrof 8 (forced)” as “Output format”

o Select “None” as “Format variant” o Rebuild the application

o The generated binary can now contains debug information that can be used directly within AVR Studio

8.2.5 Using IAR AVR32 Embedded Workbench

Each application can be rebuilt using the IAR AVR32 Embedded Workbench directly. Please follow the procedure as described:

• Change to the directory where the IAR Embedded Workbench workspace file (eww-file) for the desired platform of the corresponding application is located, for example:

cd Applications\MAC_Examples\Promiscuous_Mode_Demo cd AT86RF212_ATMEGA1281_RCB_5_3_SENS_TERM_BOARD

• Double click on the corresponding IAR Embedded Workbench file (eww-file), for example Promiscuous_Mode_Demo.eww

• Select the desired workspace (Release or Debug) and Rebuild the entire application in IAR Embedded Workbench

• After building the application the subdirectory IAR/Exe contains either an elf-file (in case the Release or Debug configuration was selected).The binaries can be downloaded onto the hardware (see Section 8.3)

• The Release configuration binary (elf-file) can both be downloaded using IAR AVR32 Embedded Workbench directly or AVR Studio

• The Debug configuration binary (elf-file) can only be downloaded using IAR AVR32 Workbench and can be debugged using IAR AVR32 C-Spy®

8.2.6 Using IAR ARM Embedded Workbench

Each application can be rebuilt using the IAR ARM Embedded Workbench directly. Please follow the procedure as describe:

• Change to the directory where the IAR Embedded Workbench workspace file (eww-file) for the desired platform of the corresponding application is located, for example:

cd Applications\MAC_Examples\Promiscuous_Mode_Demo cd AT86RF231_AT91SAM3S4C_SAM3SEK

• Double click on the corresponding IAR Embedded Workbench file (eww-file), for example Promiscuous_Mode_Demo.eww

• Select the desired workspace (Release or Debug) and Rebuild the entire application in IAR Embedded Workbench

• After building the application the subdirectory IAR/Exe contains either a binary file or an elf-file (in case the Release or Debug configuration was selected). The binaries can be downloaded onto the hardware (see Section 8.3)

• The Release and Debug configuration binary or elf-file can both be downloaded using IAR ARM Embedded Workbench directly

8.2.7 Batch build

If several applications shall be built or all applications need to be re-built, bat-files are provided to initiate an automatic batch build. Please check directory Build and run the corresponding bat-file as desired.