nuttx

History

Alan Rosenthal 8defb843aa Remove duplicate linker script definitions ## Summary A lot of linker scripts were listed twice, once for unix, once for windows. This PR cleans up the logic so they're only listed once. ## Impact Any opportunity to use a single source of truth and reduce lines of code is a win! ## Testing CI will test all build		2022-02-17 02:55:25 +08:00
..
configs	sched: Remove SDCLONE_DISABLE option and config	2022-01-31 19:03:20 +01:00
include	include: fix double include pre-processor guards	2022-01-16 11:11:14 -03:00
scripts	Remove duplicate linker script definitions	2022-02-17 02:55:25 +08:00
src	boards: lm32: update licenses to Apache	2021-08-16 07:11:32 -07:00
Kconfig
README.txt	Change all 'Nuttx' to 'NuttX'	2020-10-20 01:45:06 -07: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 boards/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

boards/misoc/lm32/misoc/include/generated
===============================

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

  There is a sample generated directory at boards/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 boards/misoc/lm32/misoc/include/generated-sample boards/misoc/lm32/misoc/include/generated

  That should permit a test build.