mirror of
https://github.com/apache/nuttx.git
synced 2026-05-18 00:34:10 +08:00
NuttX graduated the Incubator; update repository links
This commit is contained in:
Nathan Hartman
committed by
Brennan Ashton
Brennan Ashton
parent
83a4b45dd4
commit
03802dad13
@@ -18,7 +18,7 @@ inputs:
|
||||
required: true
|
||||
runs:
|
||||
using: 'docker'
|
||||
image: 'ghcr.io/apache/incubator-nuttx/apache-nuttx-ci-linux'
|
||||
image: 'ghcr.io/apache/nuttx/apache-nuttx-ci-linux'
|
||||
args:
|
||||
- "/bin/bash"
|
||||
- "-ce"
|
||||
|
||||
@@ -66,13 +66,13 @@ jobs:
|
||||
# Determine the repo and leave that unset to use the normal checkout behavior
|
||||
# of using the merge commit instead of HEAD
|
||||
case $GITHUB_REPOSITORY in
|
||||
"apache/incubator-nuttx")
|
||||
"apache/nuttx")
|
||||
# OS
|
||||
echo "Triggered by change in OS"
|
||||
APPS_REF=$REF_NAME
|
||||
;;
|
||||
|
||||
"apache/incubator-nuttx-apps" )
|
||||
"apache/nuttx-apps" )
|
||||
# APPS
|
||||
OS_REF=$REF_NAME
|
||||
echo "Triggered by change in APPS"
|
||||
@@ -90,7 +90,7 @@ jobs:
|
||||
- name: Checkout nuttx repo
|
||||
uses: actions/checkout@v3
|
||||
with:
|
||||
repository: apache/incubator-nuttx
|
||||
repository: apache/nuttx
|
||||
ref: ${{ steps.gittargets.outputs.os_ref }}
|
||||
path: sources/nuttx
|
||||
fetch-depth: 1
|
||||
@@ -100,7 +100,7 @@ jobs:
|
||||
- name: Checkout apps repo
|
||||
uses: actions/checkout@v3
|
||||
with:
|
||||
repository: apache/incubator-nuttx-apps
|
||||
repository: apache/nuttx-apps
|
||||
ref: ${{ steps.gittargets.outputs.apps_ref }}
|
||||
path: sources/apps
|
||||
fetch-depth: 1
|
||||
@@ -142,7 +142,7 @@ jobs:
|
||||
password: ${{ secrets.GITHUB_TOKEN }}
|
||||
|
||||
- name: Docker Pull
|
||||
run: docker pull ghcr.io/apache/incubator-nuttx/apache-nuttx-ci-linux
|
||||
run: docker pull ghcr.io/apache/nuttx/apache-nuttx-ci-linux
|
||||
|
||||
- name: Export NuttX Repo SHA
|
||||
run: echo "nuttx_sha=`git -C sources/nuttx rev-parse HEAD`" >> $GITHUB_ENV
|
||||
|
||||
@@ -32,7 +32,7 @@ jobs:
|
||||
- name: Checkout nuttx repo
|
||||
uses: actions/checkout@v3
|
||||
with:
|
||||
repository: apache/incubator-nuttx
|
||||
repository: apache/nuttx
|
||||
path: nuttx
|
||||
fetch-depth: 0
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
Applications
|
||||
============
|
||||
|
||||
NuttX ships a large number of applications covering a wide spectrum of functionality. These can be found in the `apps <https://github.com/apache/incubator-nuttx-apps>`_ repository. At the moment, these are documented in their individual README files so you can find more information at the repository.
|
||||
NuttX ships a large number of applications covering a wide spectrum of functionality. These can be found in the `apps <https://github.com/apache/nuttx-apps>`_ repository. At the moment, these are documented in their individual README files so you can find more information at the repository.
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
|
||||
@@ -254,10 +254,10 @@ Then create/re-create the ``nsh_romfsimg.h`` file as described below.
|
||||
|
||||
There is a good example of how to do this in the NSH simulation
|
||||
configuration at
|
||||
`boards/sim/sim/sim/configs/nsh <https://github.com/apache/incubator-nuttx/blob/master/boards/sim/sim/sim/configs/nsh/>`__.
|
||||
`boards/sim/sim/sim/configs/nsh <https://github.com/apache/nuttx/blob/master/boards/sim/sim/sim/configs/nsh/>`__.
|
||||
The ROMFS support files are provided at
|
||||
`boards/sim/include <https://github.com/apache/incubator-nuttx/blob/master/boards/sim/sim/sim/include/>`__
|
||||
`boards/sim/include <https://github.com/apache/nuttx/blob/master/boards/sim/sim/sim/include/>`__
|
||||
and the
|
||||
`README.txt <https://github.com/apache/incubator-nuttx/blob/master/boards/sim/sim/sim/README.txt>`__
|
||||
`README.txt <https://github.com/apache/nuttx/blob/master/boards/sim/sim/sim/README.txt>`__
|
||||
file at the location provides detailed information about creating and
|
||||
modifying the ROMFS file system.
|
||||
|
||||
@@ -56,7 +56,7 @@ Timer Example
|
||||
|
||||
The previously selected example will basically consult the timer status, set a timer alarm interval, set a timer signal handler function to be notified at the alarm, which only increments a variable, and then it will start the timer. The application will periodically consult the timer status at the sample rate previously configured through the ``menuconfig`` to follow the time left until the timer expires. After the samples have been read, the application stops de timer.
|
||||
|
||||
The `example code <https://github.com/apache/incubator-nuttx-apps/blob/master/examples/timer/timer_main.c>`_ may be explored, its path is at ``/examples/timer/timer_main.c`` in the apps' repository.
|
||||
The `example code <https://github.com/apache/nuttx-apps/blob/master/examples/timer/timer_main.c>`_ may be explored, its path is at ``/examples/timer/timer_main.c`` in the apps' repository.
|
||||
|
||||
In NuttX, the timer driver is a character driver and when a chip supports multiple timers, each one is accessible through its respective file in ``/dev`` directory. Each timer is registered using a unique numeric identifier (i.e. ``/dev/timer0``, ``/dev/timer1``, ...).
|
||||
|
||||
|
||||
@@ -82,7 +82,7 @@ The previously selected example will basically do the following:
|
||||
* Ping (feed the dog) during the ``pingtime`` with a delay of ``pingdelay`` and print out the wdt status in case debug was enabled.
|
||||
* Enter into an endless loop without pinging. It will cause the watchdog timer to reset the chip on timeout, i.e., after timer expiration.
|
||||
|
||||
The `example code <https://github.com/apache/incubator-nuttx-apps/blob/master/examples/watchdog/watchdog_main.c>`_ may be explored, its path is at ``/examples/watchdog/watchdog_main.c`` in the apps' repository.
|
||||
The `example code <https://github.com/apache/nuttx-apps/blob/master/examples/watchdog/watchdog_main.c>`_ may be explored, its path is at ``/examples/watchdog/watchdog_main.c`` in the apps' repository.
|
||||
|
||||
In NuttX, the watchdog timer driver is a character driver and when a chip supports multiple watchdog timers, each one is accessible through its respective special file in ``/dev`` directory. Each watchdog timer is registered using a unique numeric identifier (i.e. ``/dev/watchdog0``, ``/dev/watchdog1``, ...).
|
||||
|
||||
|
||||
@@ -32,7 +32,7 @@ support execution NXFLAT binaries from an SRAM copy as well.
|
||||
This NuttX feature includes:
|
||||
|
||||
- A dynamic loader that is built into the NuttX core (See
|
||||
`GIT <https://github.com/apache/incubator-nuttx/blob/master/binfmt/>`__).
|
||||
`GIT <https://github.com/apache/nuttx/blob/master/binfmt/>`__).
|
||||
- Minor changes to RTOS to support position independent code, and
|
||||
- A linker to bind ELF binaries to produce the NXFLAT binary format
|
||||
(See GIT).
|
||||
@@ -126,7 +126,7 @@ Development Status
|
||||
The initial release of NXFLAT was made in NuttX version 0.4.9. Testing
|
||||
is limited to the tests found under ``apps/examples/nxflat`` in the
|
||||
source tree. Some known problems exist (see the
|
||||
`TODO <https://github.com/apache/incubator-nuttx/blob/master/TODO>`__ list). As
|
||||
`TODO <https://github.com/apache/nuttx/blob/master/TODO>`__ list). As
|
||||
such, NXFLAT is currently in an early alpha phase.
|
||||
|
||||
NXFLAT Toolchain
|
||||
@@ -243,7 +243,7 @@ Making an NXFLAT module
|
||||
|
||||
Below is a snippet from an NXFLAT make file (simplified from NuttX
|
||||
`Hello,
|
||||
World! <https://github.com/apache/incubator-nuttx-apps/blob/master/examples/nxflat/tests/hello/Makefile>`__
|
||||
World! <https://github.com/apache/nuttx-apps/blob/master/examples/nxflat/tests/hello/Makefile>`__
|
||||
example).
|
||||
|
||||
* Target 1:
|
||||
|
||||
@@ -488,7 +488,7 @@ configurations for building the simulation:
|
||||
install an X11 development package.
|
||||
|
||||
- Refer to the readme file in sim configuration
|
||||
`README.txt <https://github.com/apache/incubator-nuttx/blob/master/boards/sim/sim/sim/README.txt>`__
|
||||
`README.txt <https://github.com/apache/nuttx/blob/master/boards/sim/sim/sim/README.txt>`__
|
||||
file for additional information.
|
||||
|
||||
**Test Coverage**. At present, ``apps/examples/nx``\ t only exercises a
|
||||
|
||||
@@ -32,28 +32,28 @@ Here's how to do it:
|
||||
|
||||
Visit both these links and hit the Fork button in the upper right of the page:
|
||||
|
||||
* `NuttX <https://github.com/apache/incubator-nuttx/>`_
|
||||
* `NuttX Apps <https://github.com/apache/incubator-nuttx-apps/>`_
|
||||
* `NuttX <https://github.com/apache/nuttx/>`_
|
||||
* `NuttX Apps <https://github.com/apache/nuttx-apps/>`_
|
||||
|
||||
#. Clone the Repositories
|
||||
|
||||
On the GitHub web page for your forked ``incubator-nuttx`` project, copy the clone url – get it by hitting the
|
||||
On the GitHub web page for your forked ``nuttx`` project, copy the clone url – get it by hitting the
|
||||
green ``Clone or Download`` button in the upper right. Then do this:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ git clone <your forked incubator-nuttx project clone url> nuttx
|
||||
$ git clone <your forked nuttx project clone url> nuttx
|
||||
$ cd nuttx
|
||||
$ git remote add upstream https://github.com/apache/incubator-nuttx.git
|
||||
$ git remote add upstream https://github.com/apache/nuttx.git
|
||||
|
||||
Do the same for your forked ``incubator-nuttx-apps`` project:
|
||||
Do the same for your forked ``nuttx-apps`` project:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ cd ..
|
||||
$ git clone <your forked incubator-nuttx-apps project clone url> apps
|
||||
$ git clone <your forked nuttx-apps project clone url> apps
|
||||
$ cd apps
|
||||
$ git remote add upstream https://github.com/apache/incubator-nuttx-apps.git
|
||||
$ git remote add upstream https://github.com/apache/nuttx-apps.git
|
||||
|
||||
#. Create a Local Git Branch
|
||||
|
||||
@@ -147,7 +147,7 @@ maybe doing that several times. Then when everything works, I get my branch read
|
||||
Note that there are some bugs in the ``nxstyle`` program that ``checkpatch.sh`` uses, so
|
||||
it may report a few errors that are not actually errors. The committers will help you
|
||||
find these. (Or view the
|
||||
`nxstyle Issues <https://github.com/apache/incubator-nuttx/issues?q=is%3Aissue+is%3Aopen+nxstyle>`_.)
|
||||
`nxstyle Issues <https://github.com/apache/nuttx/issues?q=is%3Aissue+is%3Aopen+nxstyle>`_.)
|
||||
|br|
|
||||
|br|
|
||||
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@@ -47,8 +47,8 @@ Installation
|
||||
3. Download NuttX and the companion applications. These must both be
|
||||
contained in the same directory::
|
||||
|
||||
git clone https://github.com/apache/incubator-nuttx.git nuttx
|
||||
git clone https://github.com/apache/incubator-nuttx-apps.git apps
|
||||
git clone https://github.com/apache/nuttx.git nuttx
|
||||
git clone https://github.com/apache/nuttx-apps.git apps
|
||||
|
||||
Building NuttX
|
||||
==============
|
||||
|
||||
@@ -215,7 +215,7 @@ Now you can design an update and confirm agent to your application. Check the `M
|
||||
`MCUboot Espressif port documentation <https://docs.mcuboot.com/readme-espressif.html>`_ for
|
||||
more information on how to apply MCUboot. Also check some `notes about the NuttX MCUboot port <https://github.com/mcu-tools/mcuboot/blob/main/docs/readme-nuttx.md>`_,
|
||||
the `MCUboot porting guide <https://github.com/mcu-tools/mcuboot/blob/main/docs/PORTING.md>`_ and some
|
||||
`examples of MCUboot applied in Nuttx applications <https://github.com/apache/incubator-nuttx-apps/tree/master/examples/mcuboot>`_.
|
||||
`examples of MCUboot applied in Nuttx applications <https://github.com/apache/nuttx-apps/tree/master/examples/mcuboot>`_.
|
||||
|
||||
After you developed an application which implements all desired functions, you need to flash it into the primary image slot
|
||||
of the device (it will automatically be in the confirmed state, you can learn more about image
|
||||
|
||||
@@ -473,7 +473,7 @@ Now you can design an update and confirm agent to your application. Check the `M
|
||||
`MCUboot Espressif port documentation <https://docs.mcuboot.com/readme-espressif.html>`_ for
|
||||
more information on how to apply MCUboot. Also check some `notes about the NuttX MCUboot port <https://github.com/mcu-tools/mcuboot/blob/main/docs/readme-nuttx.md>`_,
|
||||
the `MCUboot porting guide <https://github.com/mcu-tools/mcuboot/blob/main/docs/PORTING.md>`_ and some
|
||||
`examples of MCUboot applied in Nuttx applications <https://github.com/apache/incubator-nuttx-apps/tree/master/examples/mcuboot>`_.
|
||||
`examples of MCUboot applied in Nuttx applications <https://github.com/apache/nuttx-apps/tree/master/examples/mcuboot>`_.
|
||||
|
||||
After you developed an application which implements all desired functions, you need to flash it into the primary image slot
|
||||
of the device (it will automatically be in the confirmed state, you can learn more about image
|
||||
|
||||
@@ -96,7 +96,7 @@ audio
|
||||
This configuration uses the I2S peripheral and an externally connected audio
|
||||
codec to play an audio file. The easiest way of playing an uncompressed file
|
||||
is embedding into the firmware. This configuration selects
|
||||
`romfs example <https://github.com/apache/incubator-nuttx-apps/tree/master/examples/romfs>`__
|
||||
`romfs example <https://github.com/apache/nuttx-apps/tree/master/examples/romfs>`__
|
||||
to allow that.
|
||||
|
||||
**Audio Codec Setup**
|
||||
|
||||
@@ -356,7 +356,7 @@ Now you can design an update and confirm agent to your application. Check the `M
|
||||
`MCUboot Espressif port documentation <https://docs.mcuboot.com/readme-espressif.html>`_ for
|
||||
more information on how to apply MCUboot. Also check some `notes about the NuttX MCUboot port <https://github.com/mcu-tools/mcuboot/blob/main/docs/readme-nuttx.md>`_,
|
||||
the `MCUboot porting guide <https://github.com/mcu-tools/mcuboot/blob/main/docs/PORTING.md>`_ and some
|
||||
`examples of MCUboot applied in Nuttx applications <https://github.com/apache/incubator-nuttx-apps/tree/master/examples/mcuboot>`_.
|
||||
`examples of MCUboot applied in Nuttx applications <https://github.com/apache/nuttx-apps/tree/master/examples/mcuboot>`_.
|
||||
|
||||
After you developed an application which implements all desired functions, you need to flash it into the primary image slot
|
||||
of the device (it will automatically be in the confirmed state, you can learn more about image
|
||||
|
||||
@@ -39,13 +39,13 @@ used.
|
||||
Note that enabling all these will produce an incredible amount of logging output. Enable the level you want and
|
||||
the area you're interested in, and leave the rest disabled, save the config, and then recompile. You can see the full
|
||||
list of debug feature logging functions in the file
|
||||
`debug.h <https://github.com/apache/incubator-nuttx/blob/master/include/debug.h>`__.
|
||||
`debug.h <https://github.com/apache/nuttx/blob/master/include/debug.h>`__.
|
||||
|
||||
Syslog timestamps can be enabled in the configuration in :menuselection:`Device Drivers --> System Logging --> Prepend
|
||||
timestamp to syslog message` (``CONFIG_SYSLOG_TIMESTAMP``).
|
||||
|
||||
You may need to do a little bit of experimenting to find the combination of logging settings that work for the problem
|
||||
you're trying to solve. See the file `debug.h <https://github.com/apache/incubator-nuttx/blob/master/include/debug.h>`_
|
||||
you're trying to solve. See the file `debug.h <https://github.com/apache/nuttx/blob/master/include/debug.h>`_
|
||||
for available debug settings that are available.
|
||||
|
||||
There are also subsystems that enable USB trace debugging, and you can log to memory too, if you need the logging to be
|
||||
|
||||
@@ -135,16 +135,16 @@ ARM architecture:
|
||||
.. tip::
|
||||
There are hints on how to get the latest tool chains for most supported
|
||||
architectures in the Apache NuttX CI helper
|
||||
`script <https://github.com/apache/incubator-nuttx/tree/master/tools/ci/cibuild.sh>`_
|
||||
and Docker `container <https://github.com/apache/incubator-nuttx/tree/master/tools/ci/docker/linux/Dockerfile>`_
|
||||
`script <https://github.com/apache/nuttx/tree/master/tools/ci/cibuild.sh>`_
|
||||
and Docker `container <https://github.com/apache/nuttx/tree/master/tools/ci/docker/linux/Dockerfile>`_
|
||||
|
||||
.. todo::
|
||||
Required toolchain should be part of each arch documentation (see `relevant issue <https://github.com/apache/incubator-nuttx/issues/2409>`_).
|
||||
Required toolchain should be part of each arch documentation (see `relevant issue <https://github.com/apache/nuttx/issues/2409>`_).
|
||||
|
||||
Download NuttX
|
||||
==============
|
||||
|
||||
Apache NuttX is actively developed on GitHub. There are two main repositories, `nuttx <https://github.com/apache/incubator-nuttx>`_ and `apps <https://github.com/apache/incubator-nuttx-apps>`_, where the latter is technically optional (but recommended for complete set of features). If you intend to contribute changes, you need the absolute latest version or you simply prefer to work using git, you should clone these repositories (recommended). Otherwise you can choose to download any `stable release <https://nuttx.apache.org/download/>`_ archive.
|
||||
Apache NuttX is actively developed on GitHub. There are two main repositories, `nuttx <https://github.com/apache/nuttx>`_ and `apps <https://github.com/apache/nuttx-apps>`_, where the latter is technically optional (but recommended for complete set of features). If you intend to contribute changes, you need the absolute latest version or you simply prefer to work using git, you should clone these repositories (recommended). Otherwise you can choose to download any `stable release <https://nuttx.apache.org/download/>`_ archive.
|
||||
|
||||
.. tabs::
|
||||
|
||||
@@ -154,8 +154,8 @@ Apache NuttX is actively developed on GitHub. There are two main repositories, `
|
||||
|
||||
$ mkdir nuttxspace
|
||||
$ cd nuttxspace
|
||||
$ git clone https://github.com/apache/incubator-nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/incubator-nuttx-apps apps
|
||||
$ git clone https://github.com/apache/nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/nuttx-apps apps
|
||||
|
||||
The development source code is also available as a compressed archive, should you need it:
|
||||
|
||||
@@ -163,8 +163,8 @@ Apache NuttX is actively developed on GitHub. There are two main repositories, `
|
||||
|
||||
$ mkdir nuttxspace
|
||||
$ cd nuttxspace
|
||||
$ curl -L https://github.com/apache/incubator-nuttx/tarball/master -o nuttx.tar.gz
|
||||
$ curl -L https://github.com/apache/incubator-nuttx-apps/tarball/master -o apps.tar.gz
|
||||
$ curl -L https://github.com/apache/nuttx/tarball/master -o nuttx.tar.gz
|
||||
$ curl -L https://github.com/apache/nuttx-apps/tarball/master -o apps.tar.gz
|
||||
$ tar zxf nuttx.tar.gz --one-top-level=nuttx --strip-components 1
|
||||
$ tar zxf apps.tar.gz --one-top-level=apps --strip-components 1
|
||||
|
||||
|
||||
@@ -351,7 +351,7 @@ Supported Boards
|
||||
|
||||
All of the specific boards supported by NuttX are identified in
|
||||
the
|
||||
`README.txt <https://github.com/apache/incubator-nuttx/blob/master/boards/README.txt>`__
|
||||
`README.txt <https://github.com/apache/nuttx/blob/master/boards/README.txt>`__
|
||||
file.
|
||||
|
||||
Adding a New Board Configuration
|
||||
|
||||
@@ -124,26 +124,26 @@ into future releases.
|
||||
|
||||
## Source Code
|
||||
|
||||
The project sources are in two Git repositories. The core OS is in
|
||||
incubator-nuttx and the apps repository is in incubator-nuttx-apps. These
|
||||
are housed in GitBox on ASF servers and also mirrored at GitHub. These
|
||||
are kept in sync, so you can use whichever option you prefer.
|
||||
The project sources are in two Git repositories. The core OS is in nuttx
|
||||
and the apps repository is in nuttx-apps. These are housed in GitBox on
|
||||
ASF servers and also mirrored at GitHub. These are kept in sync, so you
|
||||
can use whichever option you prefer.
|
||||
|
||||
- NuttX core OS repository:
|
||||
|
||||
- Primary:
|
||||
<https://gitbox.apache.org/repos/asf?p=incubator-nuttx.git>
|
||||
<https://gitbox.apache.org/repos/asf?p=nuttx.git>
|
||||
|
||||
- GitHub Mirror:
|
||||
<https://github.com/apache/incubator-nuttx>
|
||||
<https://github.com/apache/nuttx>
|
||||
|
||||
- Apps repository:
|
||||
|
||||
- Primary:
|
||||
<https://gitbox.apache.org/repos/asf?p=incubator-nuttx-apps.git>
|
||||
<https://gitbox.apache.org/repos/asf?p=nuttx-apps.git>
|
||||
|
||||
- GitHub Mirror:
|
||||
<https://github.com/apache/incubator-nuttx-apps>
|
||||
<https://github.com/apache/nuttx-apps>
|
||||
|
||||
## Website Source Code
|
||||
|
||||
@@ -151,10 +151,10 @@ The project website sources are accessible via the website source code
|
||||
repository which is also mirrored in GitHub:
|
||||
|
||||
- Primary:
|
||||
<https://gitbox.apache.org/repos/asf?p=incubator-nuttx-website.git>
|
||||
<https://gitbox.apache.org/repos/asf?p=nuttx-website.git>
|
||||
|
||||
- GitHub Mirror:
|
||||
<https://github.com/apache/incubator-nuttx-website>
|
||||
<https://github.com/apache/nuttx-website>
|
||||
|
||||
# ENVIRONMENTS
|
||||
|
||||
@@ -625,19 +625,19 @@ The current NuttX du jour is available in from a GIT repository. Here are
|
||||
instructions for cloning the core NuttX RTOS (corresponding to the nuttx
|
||||
tarball discussed above):
|
||||
|
||||
git clone https://gitbox.apache.org/repos/asf/incubator-nuttx.git nuttx
|
||||
git clone https://gitbox.apache.org/repos/asf/nuttx.git nuttx
|
||||
|
||||
-or-
|
||||
|
||||
git clone https://github.com/apache/incubator-nuttx.git nuttx
|
||||
git clone https://github.com/apache/nuttx.git nuttx
|
||||
|
||||
And the semi-optional apps/ application directory and be cloned like:
|
||||
|
||||
git clone https://gitbox.apache.org/repos/asf/incubator-nuttx-apps.git apps
|
||||
git clone https://gitbox.apache.org/repos/asf/nuttx-apps.git apps
|
||||
|
||||
-or-
|
||||
|
||||
git clone https://github.com/apache/incubator-nuttx-apps.git apps
|
||||
git clone https://github.com/apache/nuttx-apps.git apps
|
||||
|
||||
That will give you the same directory structure like this:
|
||||
|
||||
@@ -679,9 +679,9 @@ some scripts like configure.sh. Before cloning, do the following:
|
||||
|
||||
These are standalone repositories:
|
||||
|
||||
* <https://gitbox.apache.org/repos/asf/incubator-nuttx-apps>
|
||||
* <https://gitbox.apache.org/repos/asf/nuttx-apps>
|
||||
or
|
||||
<https://github.com/apache/incubator-nuttx-apps.git>
|
||||
<https://github.com/apache/nuttx-apps.git>
|
||||
|
||||
This directory holds an optional package of applications and libraries
|
||||
can be used with the NuttX RTOS. There is a README.txt file there that
|
||||
|
||||
+3267
-3267
File diff suppressed because it is too large
Load Diff
@@ -143,7 +143,7 @@ ifeq ($(CONFIG_ARM_TOOLCHAIN_CLANG),y)
|
||||
|
||||
# Since the no_builtin attribute is not fully supported on Clang
|
||||
# disable the built-in functions, refer:
|
||||
# https://github.com/apache/incubator-nuttx/pull/5971
|
||||
# https://github.com/apache/nuttx/pull/5971
|
||||
|
||||
ARCHOPTIMIZATION += -fno-builtin
|
||||
|
||||
@@ -163,7 +163,7 @@ else ifeq ($(CONFIG_ARM_TOOLCHAIN_ARMCLANG),y)
|
||||
|
||||
# Since the no_builtin attribute is not fully supported on Clang
|
||||
# disable the built-in functions, refer:
|
||||
# https://github.com/apache/incubator-nuttx/pull/5971
|
||||
# https://github.com/apache/nuttx/pull/5971
|
||||
|
||||
ARCHOPTIMIZATION += -fno-builtin
|
||||
ARCHOPTIMIZATION += --target=arm-arm-none-eabi
|
||||
|
||||
@@ -53,8 +53,8 @@ Installation
|
||||
|
||||
3. Configure and build NuttX
|
||||
|
||||
$ git clone https://github.com/apache/incubator-nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/incubator-nuttx-apps.git apps
|
||||
$ git clone https://github.com/apache/nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/nuttx-apps.git apps
|
||||
$ cd nuttx
|
||||
$ make distclean
|
||||
$ ./tools/configure.sh raspberrypi-pico:nsh
|
||||
|
||||
@@ -52,8 +52,8 @@ Installation
|
||||
|
||||
3. Configure and build NuttX
|
||||
|
||||
$ git clone https://github.com/apache/incubator-nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/incubator-nuttx-apps.git apps
|
||||
$ git clone https://github.com/apache/nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/nuttx-apps.git apps
|
||||
$ cd nuttx
|
||||
$ make distclean
|
||||
$ ./tools/configure.sh raspberrypi-pico:nsh
|
||||
|
||||
@@ -47,8 +47,8 @@ Installation
|
||||
|
||||
3. Configure and build NuttX
|
||||
|
||||
$ git clone https://github.com/apache/incubator-nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/incubator-nuttx-apps.git apps
|
||||
$ git clone https://github.com/apache/nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/nuttx-apps.git apps
|
||||
$ cd nuttx
|
||||
$ make distclean
|
||||
$ ./tools/configure.sh raspberrypi-pico:nsh
|
||||
|
||||
@@ -50,8 +50,8 @@ Installation
|
||||
|
||||
3. Configure and build NuttX
|
||||
|
||||
$ git clone https://github.com/apache/incubator-nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/incubator-nuttx-apps.git apps
|
||||
$ git clone https://github.com/apache/nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/nuttx-apps.git apps
|
||||
$ cd nuttx
|
||||
$ make distclean
|
||||
$ ./tools/configure.sh pimoroni-tiny2040:nsh
|
||||
|
||||
@@ -54,8 +54,8 @@ Installation
|
||||
|
||||
3. Configure and build NuttX
|
||||
|
||||
$ git clone https://github.com/apache/incubator-nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/incubator-nuttx-apps.git apps
|
||||
$ git clone https://github.com/apache/nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/nuttx-apps.git apps
|
||||
$ cd nuttx
|
||||
$ make distclean
|
||||
$ ./tools/configure.sh raspberrypi-pico:nsh
|
||||
|
||||
@@ -53,8 +53,8 @@ Installation
|
||||
|
||||
3. Configure and build NuttX
|
||||
|
||||
$ git clone https://github.com/apache/incubator-nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/incubator-nuttx-apps.git apps
|
||||
$ git clone https://github.com/apache/nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/nuttx-apps.git apps
|
||||
$ cd nuttx
|
||||
$ make distclean
|
||||
$ ./tools/configure.sh raspberrypi-pico:nsh
|
||||
|
||||
@@ -28,8 +28,8 @@ index c449421741..5a76600785 100644
|
||||
4. Configure and build NuttX
|
||||
|
||||
$ mkdir ./nuttx; cd ./nuttx
|
||||
$ git clone https://github.com/apache/incubator-nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/incubator-nuttx-apps.git apps
|
||||
$ git clone https://github.com/apache/nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/nuttx-apps.git apps
|
||||
$ cd nuttx
|
||||
$ make distclean
|
||||
$ ./tools/configure.sh hifive1-revb:nsh
|
||||
|
||||
@@ -11,8 +11,8 @@
|
||||
3. Configure and build NuttX
|
||||
|
||||
$ mkdir ./nuttx; cd ./nuttx
|
||||
$ git clone https://github.com/apache/incubator-nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/incubator-nuttx-apps.git apps
|
||||
$ git clone https://github.com/apache/nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/nuttx-apps.git apps
|
||||
$ cd nuttx
|
||||
$ make distclean
|
||||
$ ./tools/configure.sh hifive1-revb:nsh
|
||||
|
||||
@@ -25,8 +25,8 @@
|
||||
4. Configure and build NuttX
|
||||
|
||||
$ mkdir ./nuttx; cd ./nuttx
|
||||
$ git clone https://github.com/apache/incubator-nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/incubator-nuttx-apps.git apps
|
||||
$ git clone https://github.com/apache/nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/nuttx-apps.git apps
|
||||
$ cd nuttx
|
||||
$ make distclean
|
||||
$ ./tools/configure.sh maix-bit:nsh
|
||||
|
||||
@@ -12,8 +12,8 @@
|
||||
3. Configure and build NuttX
|
||||
|
||||
$ mkdir ./nuttx; cd ./nuttx
|
||||
$ git clone https://github.com/apache/incubator-nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/incubator-nuttx-apps.git apps
|
||||
$ git clone https://github.com/apache/nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/nuttx-apps.git apps
|
||||
$ cd nuttx
|
||||
$ make distclean
|
||||
$ ./tools/configure.sh maix-bit:nsh
|
||||
|
||||
@@ -11,8 +11,8 @@
|
||||
3. Configure and build NuttX
|
||||
|
||||
$ mkdir ./nuttx; cd ./nuttx
|
||||
$ git clone https://github.com/apache/incubator-nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/incubator-nuttx-apps.git apps
|
||||
$ git clone https://github.com/apache/nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/nuttx-apps.git apps
|
||||
$ cd nuttx
|
||||
$ make distclean
|
||||
$ ./tools/configure.sh arty_a7:nsh
|
||||
|
||||
@@ -13,8 +13,8 @@
|
||||
3.1. Configure and build NuttX for BUILD_FLAT
|
||||
|
||||
$ mkdir ./nuttx; cd ./nuttx
|
||||
$ git clone https://github.com/apache/incubator-nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/incubator-nuttx-apps.git apps
|
||||
$ git clone https://github.com/apache/nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/nuttx-apps.git apps
|
||||
$ cd nuttx
|
||||
$ make distclean
|
||||
$ ./tools/configure.sh rv-virt:nsh
|
||||
@@ -23,8 +23,8 @@
|
||||
3.2 Configure and build NuttX for BUILD_KERNEL
|
||||
|
||||
$ mkdir ./nuttx; cd ./nuttx
|
||||
$ git clone https://github.com/apache/incubator-nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/incubator-nuttx-apps.git apps
|
||||
$ git clone https://github.com/apache/nuttx.git nuttx
|
||||
$ git clone https://github.com/apache/nuttx-apps.git apps
|
||||
$ cd nuttx
|
||||
$ make distclean
|
||||
$ ./tools/configure.sh rv-virt:knsh64
|
||||
|
||||
+2
-2
@@ -473,7 +473,7 @@ function setup_repos {
|
||||
if [ -d "${nuttx}" ]; then
|
||||
cd "${nuttx}"; git pull
|
||||
else
|
||||
git clone https://github.com/apache/incubator-nuttx.git "${nuttx}"
|
||||
git clone https://github.com/apache/nuttx.git "${nuttx}"
|
||||
cd "${nuttx}"
|
||||
fi
|
||||
git log -1
|
||||
@@ -481,7 +481,7 @@ function setup_repos {
|
||||
if [ -d "${apps}" ]; then
|
||||
cd "${apps}"; git pull
|
||||
else
|
||||
git clone https://github.com/apache/incubator-nuttx-apps.git "${apps}"
|
||||
git clone https://github.com/apache/nuttx-apps.git "${apps}"
|
||||
cd "${apps}"
|
||||
fi
|
||||
git log -1
|
||||
|
||||
@@ -92,7 +92,7 @@ RUN mkdir clang-arm-none-eabi && \
|
||||
RUN mkdir gcc-arm-none-eabi && \
|
||||
curl -s -L "https://developer.arm.com/-/media/Files/downloads/gnu/11.3.rel1/binrel/arm-gnu-toolchain-11.3.rel1-x86_64-arm-none-eabi.tar.xz" \
|
||||
| tar -C gcc-arm-none-eabi --strip-components 1 -xJ \
|
||||
&& curl -s -L -O "https://raw.githubusercontent.com/apache/incubator-nuttx/master/tools/ci/patch/arm-none-eabi-workaround-for-newlib-version-break.patch" \
|
||||
&& curl -s -L -O "https://raw.githubusercontent.com/apache/nuttx/master/tools/ci/patch/arm-none-eabi-workaround-for-newlib-version-break.patch" \
|
||||
&& patch -p0 < arm-none-eabi-workaround-for-newlib-version-break.patch
|
||||
|
||||
###############################################################################
|
||||
|
||||
Reference in New Issue
Block a user