Specifications

6263A–ATARM–10-Oct-06

Application Note

core_usb.h: USB API definitions

core_udp.c: UDP controller driver methods

Makefile: makefile used to build the project

4.2 Headers

When programming your own application, most if not all the headers described in the file archi-

tecture of the framework must be included. However, since each header has its own

dependencies, they must be included in a particular order.

Here is the standard inclusion order:

#include "core_common.h"

#include "core_device.h"

#include "core_board.h"

#include "core_trace.h"

#include "core_usb.h"

#include "core_standard.h"

If a custom class driver has been added, then its header must probably be linked last, after the

core_standard.h file.

4.3 Building the Framework

A Makefile is provided to make it easier to compile the framework. The nmake program is neces-

sary to use it.

Several options are available to build the framework in different ways:

•TARGET

– Target chip for which to build the program.

– Possible values: AT91SAM7S32, AT91SAM7S321, AT91SAM764, AT91SAM7128,

AT91SAM7256, AT91SAM7512, AT91SAM7SE32, AT91SAM7SE256,

AT91SAM7SE512, AT91SAM7X128, AT91SAM7X256, AT91SAM7X512,

AT91SAM7A3.

– Default: AT91SAM7S64.

•BOARD

– Board used with the chip.

– Possible values: AT91SAM7SEK, AT91SAM7SEEK, AT91SAM7XEK,

AT91SAM7A3EK.

– Default: AT91SAM7SEK.

•DEBUG

– This option tells the linker to add debug symbols and create an .axf file for debugging

the project with AXD.

– Possible values: YES, NO.

– Default: NO.

• REMAP

– Optional, compiles the program so it copies itself in RAM and performs a memory

remap operation. This can be useful to save on power consumption or to speed up

the execution.