ATNGW100 Atmel, ATNGW100 Datasheet - Page 5

• Manufacturer Part Number: ATNGW100
• Description: KIT AVR32 NETWORK GATEWAY
• Manufacturer: Atmel
• Series: AVR®32r
• Type: MCUr

Specifications of ATNGW100

• Contents: Board and Linux Dev. and Debug Toolchain
• Processor To Be Evaluated: AT32AP7000
• Data Bus Width: 32 bit
• Interface Type: RS-232, Ethernet, USB
• Silicon Manufacturer: Atmel
• Core Architecture: AVR
• Core Sub-architecture: AVR UC3
• Silicon Core Number: AT32AP7000
• Silicon Family Name: AVR
• Kit Contents: Board CD Docs
• Rohs Compliant: Yes
• For Use With/related Products: AT32AP7000, AT32AP7001, AT32AP7002
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

4.1.7 docs/
4.1.8 include/
4.1.9 Makefile
4.1.10 package/
4.1.11 project/
4.1.12 project_build_avr32/
4.1.13 target/
4.1.14 TODO
4.1.15 toolchain/
4.1.16 toolchain_build_avr32/
32062E-AVR32-11/08
In this directory the documentation for Buildroot can be found.
Directory made by kconfig, used for knowing which values are stored during
configuration setup. Leave it as is, everything is auto generated.
Top level makefile for Buildroot describing the initial rules for how to build a root file
system. This file will again include all the other makefiles spread out in the sub
directories.
Directory containing all the makefiles that describes how each library and application
shall be built.
Directory containing information about project building that allows Buildroot to be able
to have multiple projects ongoing in the same extracted source tree. Buildroot will
share compiled applications, libraries and toolchain whenever possible.
The project specific part of the build is located in this directory. Is populated on the
form project_build_avr32/<project name>/. Here you will find the target specific Linux
kernel; Busybox and uncompressed root file system.
Directory containing information about targets that is where the different boards are
defined, board specific patches to the Linux kernel and board specific files. Typically
this is where the base for the file system is located, called target_skeleton.
TODO list for upstream Buildroot describing what areas is in the works. Feel free to
work on TODO material if you are confident with how Buildroot works.
Directory containing makefiles for the toolchain that describes how it should be built
and what options a user have. The toolchain is a vital part of buildroot, since you are
not capable to build anything without a working toolchain. Given that the user has
chosen an internal toolchain.
Directory containing the extracted toolchain source tarballs and where Buildroot
builds the toolchain.
AVR32003
5