Skip to content
Snippets Groups Projects
Commit 22fbd809 authored by Gregory Nutt's avatar Gregory Nutt
Browse files

configs/avr32dev1/ostest: Configuration converted to use the kconfig-frontends tools

parent 8e06aa47
No related branches found
No related tags found
No related merge requests found
......@@ -6861,3 +6861,8 @@
kconfig-frontends tools (2014-3-5)
* configs/teensy/nsh: Configuration converted to use the
kconfig-frontends tools (2014-3-5)
* arch/avr/Kconfig, avr32/Kconfig, at32uc3/Kconfig, atmega/Kconfig, and
at90usb/Kconfig: Reshuffle lots of AVR-related configuration names to
make space for AVR32. Populate AVR32 Kconfig file (2014-3-5).
* configs/avr32dev1/ostest: Configuration converted to use the
kconfig-frontends tools (2014-3-5)
......@@ -343,7 +343,7 @@ AVR32DEV1 Configuration Options
CONFIG_ARCH_architecture - For use in C code:
CONFIG_ARCH_AVR32=y
CONFIG_ARCH_FAMILY_AVR32=y
CONFIG_ARCH_CHIP - Identifies the arch/*/chip subdirectory
......@@ -431,28 +431,51 @@ AVR32DEV1 Configuration Options
Configurations
^^^^^^^^^^^^^^
Each Atmel AVR32DEV configuration is maintained in a sub-directory and
can be selected as follow:
Common Configuration Notes
--------------------------
cd tools
./configure.sh avr32dev1/<subdir>
cd -
. ./setenv.sh
1. Each Atmel AVR32DEV configuration is maintained in a sub-directory and
can be selected as follow:
(Or configure.bat in a native Windows environment).
cd tools
./configure.sh avr32dev1/<subdir>
cd -
. ./setenv.sh
Where <subdir> is one of the following:
Where <subdir> is one of the configuration sub-directories described in
the following paragraph.
(Use configure.bat instead of configure.sh in a native Windows environment).
2. These configurations use the mconf-based configuration tool. To
change a configurations using that tool, you should:
a. Build and install the kconfig-mconf tool. See nuttx/README.txt
and misc/tools/
b. Execute 'make menuconfig' in nuttx/ in order to start the
reconfiguration process.
3. By default, all configurations assume the AVR toolchain under Cygwin
with Windows. This is easily reconfigured:
CONFIG_HOST_WINDOWS=y
CONFIG_WINDOWS_CYGWIN=y
CONFIG_AVR32_AVRTOOLSW=y
Configuration Sub-Directories
-----------------------------
nsh:
Configures the NuttShell (nsh) located at examples/nsh. The
Configuration enables only the serial NSH interface.
ostest:
This configuration directory, performs a simple OS test using
examples/ostest.
NOTE: Round-robin scheduling is disabled in this test because
the RR test in examples/ostest declares data structures that
are too large for the poor little uc3 SRAM.
############################################################################
# configs/avr32dev1/ostest/appconfig
#
# Copyright (C) 2011 Gregory Nutt. All rights reserved.
# Author: Gregory Nutt <gnutt@nuttx.org>
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
#
# 1. Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# 2. Redistributions in binary form must reproduce the above copyright
# notice, this list of conditions and the following disclaimer in
# the documentation and/or other materials provided with the
# distribution.
# 3. Neither the name NuttX nor the names of its contributors may be
# used to endorse or promote products derived from this software
# without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
# FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
# COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
# INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
# BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
# OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
# AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
# ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
# POSSIBILITY OF SUCH DAMAGE.
#
############################################################################
# Path to example in apps/examples containing the user_start entry point
CONFIGURED_APPS += examples/ostest
This diff is collapsed.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment