nuttx

History

Ramtin Amin c7382d9db9 This commit adds support for the Minerva architecture Squashed commit of the following: Author: Gregory Nutt <gnutt@nuttx.org> Eliminate complaints from tools/nxstyle Manually fix up kruft left behind by indent.sh Raw application of tools/indent.sh to all new .c and .h files. Still need fixups. Convert all C++ style comments to C style; Covery hex constants to lower case. Convert TABs to spaces Beginning of code review process. The first small dent. configs/misoc: Rename os_start to nx_start. arch/misoc/src/minerva/minerva_exit.c: Make name change to match change made to master. Author: Ramtin Amin <keytwo@gmail.com> configs/Kconfig and misoc/nsh/defconfig: Add support for the Verilator board. Author: Juha Niskanen (Haltian) <juha.niskanen@haltian.com> arch/arm/src/stm32l4/stm32l4_lse.c: Ports Jussi Kivilinna's recent STM32F7 LSE change to STM32L4. Author: David Sidrane <david_s5@usa.net> tools/.gitignore: Ignore new tool binaries. Author: Ramtin Amin <keytwo@gmail.com> arch/misoc/src/minerva: Initial merge of minera port.		2019-02-07 09:41:18 -06:00
..
hello	libs/unistd and other affected files: Hostname support no longer depends on CONFIG_NET since the host name is also useful in the non-network environment. CONFIG_NET_HOSTNAME changed to CONFIG_LIB_HOSTNAME.	2019-01-27 06:56:16 -06:00
include	This commit adds support for the Minerva architecture	2019-02-07 09:41:18 -06:00
nsh	This commit adds support for the Minerva architecture	2019-02-07 09:41:18 -06:00
scripts	This commit adds support for the Minerva architecture	2019-02-07 09:41:18 -06:00
src	Misoc/LM32: Changes to get a clean compilation after initial review and commit	2016-11-02 12:07:52 -06:00
Kconfig
README.txt	Remove instructures to CD to tools/ before running ./configure.sh	2018-05-09 11:41:46 -06:00

README.txt

Misoc README
============

  This README applies to a port to NuttX running on a Qemu LM32 system.  You
  can find the Qemu setup at https://bitbucket.org/key2/qemu

  This initial release supports two UARTs, but does not have a system timer
  or other peripherals.  More to come.

Buildroot Toolchain
===================

  A GNU GCC-based toolchain is assumed.  The PATH environment variable should
  be modified to point to the correct path to the LM32 GCC toolchain (if
  different from the default in your PATH variable).

  If you have no LM32 toolchain, one can be cloned from the NuttX
  Bitbucket GIT repository (https://bitbucket.org/nuttx/buildroot).
  This GNU toolchain builds and executes in the Linux or Cygwin environment.

  1. You must have already configured Nuttx in <some-dir>/nuttx.

     tools/configure.sh misoc/<sub-dir>
     make oldconfig context

  2. Clone the latest buildroot package into <some-dir>/buildroot

       git clone git@bitbucket.org:nuttx/buildroot.git <some-dir>/buildroot

     or

       git clone https://patacongo@bitbucket.org/nuttx/buildroot.git <some-dir>/buildroot

  3. cd <some-dir>/buildroot

  4. cp lm32-elf-defconfig-6.1.0 .config

  5. make oldconfig

  6. make

  7. By default, the tools will be at the absolute path:

       <some-dir>/buildroot/build_lm32/staging_dir/bin

     Or the NuttX relative path:

       ../buildroot/build_lm32/staging_dir/bin

     Make sure that he PATH variable includes the path to the newly built
     binaries.

  See the file configs/README.txt in the buildroot source tree.  That has more
  detailed PLUS some special instructions that you will need to follow if you
  are building a LM32 toolchain for Cygwin under Windows.  Also included in
  that README file is a FAQ of frequent build issues that their work-arounds.

  In order to use the buildroot toolchain, you also must set the following
  in your .config file:

    CONFIG_LM3S_TOOLCHAIN_BUILDROOT=y

configs/misoc/include/generated
===============================

  In order to build this configuration, you must provide the
  configs/misoc/include/generated directory.  It contains the generated
  Misoc files and may be a symbolic link.  The base configurtion will NOT
  build without this directory!

  There is a sample generated directory at configs/misoc/include/generated-sample.
  If you want to do a test build without generating the architecture, then
  you can simply link this sample directory like:

    $ ln -s configs/misoc/include/generated-sample configs/misoc/include/generated

  That should permit a test build.