You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by ad...@apache.org on 2016/04/02 00:39:02 UTC
incubator-mynewt-site git commit: added Release Notes link for b2
release, added and updated all the newt commands,
and updated arduino zero instructions to clarify setting of a target's
features to zero and zero_pro
Repository: incubator-mynewt-site
Updated Branches:
refs/heads/master 8a9c29dfc -> 72d6cedb8
added Release Notes link for b2 release, added and updated all the newt commands, and updated arduino zero instructions to clarify setting of a target's features to zero and zero_pro
Project: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/commit/72d6cedb
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/72d6cedb
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/72d6cedb
Branch: refs/heads/master
Commit: 72d6cedb8783b9f78e0a422ee2ace1718b278a6c
Parents: 8a9c29d
Author: aditihilbert <ad...@runtime.io>
Authored: Fri Apr 1 15:38:50 2016 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Fri Apr 1 15:38:50 2016 -0700
----------------------------------------------------------------------
custom-theme/download.html | 4 +-
docs/newt/command_list/newt_app.md | 52 ----------
docs/newt/command_list/newt_build.md | 36 +++++++
docs/newt/command_list/newt_clean.md | 37 +++++++
docs/newt/command_list/newt_create_image.md | 35 +++++++
docs/newt/command_list/newt_debug.md | 35 +++++++
docs/newt/command_list/newt_help.md | 43 +++++++--
docs/newt/command_list/newt_info.md | 25 +++++
docs/newt/command_list/newt_install.md | 29 ++++++
docs/newt/command_list/newt_load.md | 27 ++++++
docs/newt/command_list/newt_new.md | 11 +--
docs/newt/command_list/newt_pkg.md | 61 ------------
docs/newt/command_list/newt_run.md | 39 ++++++++
docs/newt/command_list/newt_size.md | 56 +++++++++++
docs/newt/command_list/newt_target.md | 117 +++++------------------
docs/newt/command_list/newt_test.md | 43 +++++++++
docs/newt/command_list/newt_upgrade.md | 26 +++++
docs/newt/command_list/newt_version.md | 2 +
docs/os/tutorials/arduino_zero.md | 26 +++--
mkdocs.yml | 22 +++--
20 files changed, 488 insertions(+), 238 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/72d6cedb/custom-theme/download.html
----------------------------------------------------------------------
diff --git a/custom-theme/download.html b/custom-theme/download.html
index 25cd0b3..9e0c522 100644
--- a/custom-theme/download.html
+++ b/custom-theme/download.html
@@ -30,7 +30,7 @@
</div>
<div class="row">
<div class="col-md-12">
- <p>Starting with the second release, links to the Release Notes will be published here.</p>
+ <p> <a href="https://cwiki.apache.org/confluence/display/MYNEWT/RN-0.8.0-b2-incubating">For 0.8.0-b2</a> </p>
</div>
</div>
</div>
@@ -46,7 +46,7 @@
</div>
<div class="row">
<div class="col-md-12">
- <p>Links to older releases will be listed here when the newest release becomes available.</p>
+ <p>Links to older releases as they become available</p>
</div>
</div>
</div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/72d6cedb/docs/newt/command_list/newt_app.md
----------------------------------------------------------------------
diff --git a/docs/newt/command_list/newt_app.md b/docs/newt/command_list/newt_app.md
deleted file mode 100644
index 937944c..0000000
--- a/docs/newt/command_list/newt_app.md
+++ /dev/null
@@ -1,52 +0,0 @@
-## <font color="#F2853F" style="font-size:24pt">newt app </font>
-
-
-#### Usage:
-```no-highlight
- newt app [command][flags] input1 input2...
-```
-#### Available commands:
-```no-highlight
- generate-pkg-list Generate a pkg-list file from the pkgs in the current directory
- add-pkg-list Add a remote pkg-list, and put it in the current app
- list-pkg-listes List the pkg-listes installed in the current app
- show-pkg-list Show an individual pkg-list in the current app
-```
-
-#### Flags:
-```no-highlight
- -h, --help=false: help for app
-```
-#### Global Flags:
-```no-highlight
- -h, --help=false: help for newt
- -l, --loglevel="WARN": Log level, defaults to WARN.
- -q, --quiet=false: Be quiet; only display error output.
- -s, --silent=false: Be silent; don't output anything.
- -v, --verbose=false: Enable verbose output when executing commands.
-```
-#### Description
-
-Sub-command | Explanation
--------------| ------------------------
-generate-pkg-list | Takes a snapshot of the pkgs in the current local directory and combines them into a pkg-list by the name of `input1` and with the url of `input2` and generates a standard output of the pkg-list details that can be redirected to a `.yml` pkg-list file. Typically the pkg-list file name is chosen to match the pkg-list name which means the standard output should be directed to a pkg-list file named `input1.yml`
-add-pkg-list | Downloads the pkg-list of the name `input1` from the master branch of the github repository `input2` into the current app. A file named `input1.yml` file is added in the `.app/pkg-lists` subdirectory inside the current local app. The `.app/` directory structure is created automatically if it does not exist.
-list-pkg-lists | Lists all the pkg-lists present in the current app, including pkg-lists that may have been added from other apps on github. The output shows all the remote pkg-list names and the total pkgshells in each of the pkg-lists.
-show-pkg-list | Shows information about the pkg-list that has the name given in the `input1` argument. Output includes the pkg-list name, url, and all the constituent pkgs with their version numbers.
-
-#### Command-specific flags
-
-Sub-command | Available flags | Explanation
--------------| ----------------|------------
-add-pkg-list | -b, --branch="<branch-name>" | Fetches the pkg-list file with name `input1` from the specified branch at `input1` url of the github repository. All subsequent pkg installations will be done from that branch.
-
-#### Examples
-
-Sub-command | Usage | Explanation
--------------| -----------------------|-----------------
-generate-pkg-list | newt app generate-pkg-list mypkg-list https://github.com/apache/incubator-mynewt-larva > mypkg-list.yml| Takes a snapshot of the pkgs in the current app to form a pkg-list named mypkg-list with the url https://github.com/apache/incubator-mynewt-larva. The output is written to a file named `mypkg-list.yml` and describes the properties and contents of the pkg-list (name, url, pkgs).
-add-pkg-list | newt app add-pkg-list larva https://github.com/apache/incubator-mynewt-larva | Adds the remote pkg-list named larva at https://github.com/apache/incubator-mynewt-larva to the local app.
-list-pkg-lists | newt app list-pkg-lists | Shows all the remote pkg-list description files that been downloaded into the current app. Output includes each list with name and summary of included packages e.g. `Remote package list larva@master (num_pkgs: 44)`
-show-pkg-list | newt app show-pkg-list larva | Outputs the details of the pkg-list named larva such as the github url where the remote sits, the constituent pkgs and their versions
-
-
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/72d6cedb/docs/newt/command_list/newt_build.md
----------------------------------------------------------------------
diff --git a/docs/newt/command_list/newt_build.md b/docs/newt/command_list/newt_build.md
new file mode 100644
index 0000000..c785074
--- /dev/null
+++ b/docs/newt/command_list/newt_build.md
@@ -0,0 +1,36 @@
+## <font color="#F2853F" style="font-size:24pt">newt build </font>
+
+Compiles, links, and builds one or more apps.
+
+#### Usage:
+
+```no-highlight
+ newt build [flags] input1
+```
+
+where `input1` is the name of the target to build.
+
+#### Flags:
+
+```no-highlight
+ -h, --help=false: help for target
+```
+
+#### Global Flags:
+
+```no-highlight
+ -l, --loglevel="WARN": Log level, defaults to WARN.
+ -o, --outfile string Filename to tee log output to
+ -q, --quiet=false: Be quiet; only display error output.
+ -s, --silent=false: Be silent; don't output anything.
+ -v, --verbose=false: Enable verbose output when executing commands.
+```
+
+
+#### Examples
+
+ Sub-command | Usage | Explanation
+-------------| -----------------------|-----------------
+build | newt build <br> `input1` | Builds the source code into an image that can be loaded on the hardware (`bsp`) associated with the target named `input1` to run the application enabled by the `app` setting associated with that target. It creates 'bin/' directory and 'bin/<input1>/apps/<app>' subdirectory inside the base directory for the app, compiles and generates binaries and executables, and places them in that subdirectory.
+ | newt build <br> my_blinky_sim | For example, if `app` was set to `apps/blinky` for the target "my_blinky_sim", you will find the generated .elf, .a, and .lst files in bin/my_blinky_sim/apps/blinky directory created under the base directory for the app created using `newt new` at the start of the project.
+build | newt build my_blinky_sim myble | builds the apps defined for both the targets "my_blinky_sim" and "myble".
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/72d6cedb/docs/newt/command_list/newt_clean.md
----------------------------------------------------------------------
diff --git a/docs/newt/command_list/newt_clean.md b/docs/newt/command_list/newt_clean.md
new file mode 100644
index 0000000..a79c216
--- /dev/null
+++ b/docs/newt/command_list/newt_clean.md
@@ -0,0 +1,37 @@
+## <font color="#F2853F" style="font-size:24pt">newt clean </font>
+
+Deletes application build artifacts for a specified target
+
+#### Usage:
+
+```no-highlight
+ newt clean [flags] input1
+```
+
+#### Flags:
+
+```no-highlight
+ -h, --help=false: help for target
+```
+
+#### Global Flags:
+
+```no-highlight
+ -l, --loglevel="WARN": Log level, defaults to WARN.
+ -o, --outfile string Filename to tee log output to
+ -q, --quiet=false: Be quiet; only display error output.
+ -s, --silent=false: Be silent; don't output anything.
+ -v, --verbose=false: Enable verbose output when executing commands.
+```
+#### Description
+
+Sub-command | Explanation
+-------------| ------------------------
+clean | Deletes all the build artifacts generated for target specified by `input1`. It does not delete the target definition.
+
+
+#### Examples
+
+ Sub-command | Usage | Explanation
+-------------| -----------------------|-----------------
+clean | newt clean myble2 | Removes all the files generated while building the target `myble2` and placed in the `bin/myble2` directory created during the build process.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/72d6cedb/docs/newt/command_list/newt_create_image.md
----------------------------------------------------------------------
diff --git a/docs/newt/command_list/newt_create_image.md b/docs/newt/command_list/newt_create_image.md
new file mode 100644
index 0000000..d659a46
--- /dev/null
+++ b/docs/newt/command_list/newt_create_image.md
@@ -0,0 +1,35 @@
+## <font color="#F2853F" style="font-size:24pt">newt create-image </font>
+
+Creates a signed image by adding image header to created binary file for specified target. Version number in the header is set to be <version>
+
+#### Usage:
+
+```no-highlight
+ newt create-image <target-name> <version> [flags]
+```
+
+#### Flags:
+```no-highlight
+ -h, --help=false: help for target
+```
+
+#### Global Flags:
+```no-highlight
+ -l, --loglevel="WARN": Log level, defaults to WARN.
+ -o, --outfile string Filename to tee log output to
+ -q, --quiet=false: Be quiet; only display error output.
+ -s, --silent=false: Be silent; don't output anything.
+ -v, --verbose=false: Enable verbose output when executing commands.
+```
+#### Description
+
+Sub-command | Explanation
+-------------| ------------------------
+create-image | Signs and adds image header to the created binary file for target named `<target-name>` and given the version specified as `<version>`. The application image generated is `<app-name>.img` where the app-name is the same as the app specified in the target definition. The generated application image can be found in `/bin/<target-name>/apps/<app-name>/`. <br> <br> A build manifest file `manifest.json` is also generated in the same directory. This build manifest contains information such as build time, version, image name, a hash to identify the image, packages actually used to create the build, and the target for which the image is built.
+
+
+#### Examples
+
+ Sub-command | Usage | Explanation
+-------------| -----------------------|-----------------
+create-image | newt create-image myble2 1.0.1.0 | Creates a signed image for target `myble2` and assigns it the version `1.0.1.0`. <br> <br> If the target is as follows: <br> targets/myble2 <br> app=@apache-mynewt-core/apps/bletiny <br> bsp=@apache-mynewt-core/hw/bsp/nrf52pdk <br> build_profile=optimized <br> cflags=-DSTATS_NAME_ENABLE <br> <br> then, the created image is `bin/myble2/apps/bletiny/bletiny.img` and the manifest is `bin/myble2/apps/bletiny/manifest.json`
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/72d6cedb/docs/newt/command_list/newt_debug.md
----------------------------------------------------------------------
diff --git a/docs/newt/command_list/newt_debug.md b/docs/newt/command_list/newt_debug.md
new file mode 100644
index 0000000..25725ee
--- /dev/null
+++ b/docs/newt/command_list/newt_debug.md
@@ -0,0 +1,35 @@
+## <font color="#F2853F" style="font-size:24pt">newt debug </font>
+
+Opens debugger session for specified target.
+
+#### Usage:
+
+```no-highlight
+ newt debug <target-name> [flag]
+```
+
+#### Flags:
+```no-highlight
+ -h, --help=false: help for target
+```
+
+#### Global Flags:
+```no-highlight
+ -l, --loglevel="WARN": Log level, defaults to WARN.
+ -o, --outfile string Filename to tee log output to
+ -q, --quiet=false: Be quiet; only display error output.
+ -s, --silent=false: Be silent; don't output anything.
+ -v, --verbose=false: Enable verbose output when executing commands.
+```
+#### Description
+
+Sub-command | Explanation
+-------------| ------------------------
+debug | Opens the appropriate debugging session for the image built for the named target.
+
+
+#### Examples
+
+ Sub-command | Usage | Explanation
+-------------| -----------------------|-----------------
+debug | newt debug myble2 | Opens J-Link connection and starts a GNU gdb session to debug bin/myble2/apps/bletiny/bletiny.elf when the target is as follows: <br> <br> targets/myble2 <br> app=@apache-mynewt-core/apps/bletiny <br> bsp=@apache-mynewt-core/hw/bsp/nrf52pdk <br> build_profile=optimized <br> cflags=-DSTATS_NAME_ENABLE
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/72d6cedb/docs/newt/command_list/newt_help.md
----------------------------------------------------------------------
diff --git a/docs/newt/command_list/newt_help.md b/docs/newt/command_list/newt_help.md
index 8b9f435..1fbfc27 100644
--- a/docs/newt/command_list/newt_help.md
+++ b/docs/newt/command_list/newt_help.md
@@ -1,5 +1,16 @@
## <font color="#F2853F" style="font-size:24pt">newt help </font>
+Displays the help text for the newt command line tool:
+
+```no-highlight
+
+Newt allows you to create your own embedded application based on the Mynewt
+operating system. Newt provides both build and package management in a single
+tool, which allows you to compose an embedded application, and set of
+projects, and then build the necessary artifacts from those projects. For more
+information on the Mynewt operating system, please visit
+https://mynewt.apache.org/.
+```
#### Usage:
```no-highlight
@@ -9,13 +20,33 @@
```no-highlight
--h, --help=false: help for newt
--l, --loglevel="WARN": Log level, defaults to WARN.
--q, --quiet=false: Be quiet; only display error output.
--s, --silent=false: Be silent; don't output anything.
--v, --verbose=false: Enable verbose output when executing commands.
+ -h, --help=false: help for newt
+ -o, --outfile string Filename to tee output to
+ -l, --loglevel="WARN": Log level, defaults to WARN.
+ -q, --quiet=false: Be quiet; only display error output.
+ -s, --silent=false: Be silent; don't output anything.
+ -v, --verbose=false: Enable verbose output when executing commands.
```
-
+
+#### Available Commands:
+
+```no-highlight
+ version Display the Newt version number.
+ install Install project dependencies
+ upgrade Upgrade project dependencies
+ new Create a new project
+ info Show project info
+ target Command for manipulating targets
+ build Builds one or more targets.
+ clean Deletes build artifacts for one or more targets.
+ test Executes unit tests for one or more packages
+ load Load built target to board
+ debug Open debugger session to target
+ size Size of target components
+ create-image Add image header to target binary
+ run build/create-image/download/debug <target>
+```
+
#### Examples
Sub-command | Usage | Explanation
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/72d6cedb/docs/newt/command_list/newt_info.md
----------------------------------------------------------------------
diff --git a/docs/newt/command_list/newt_info.md b/docs/newt/command_list/newt_info.md
new file mode 100644
index 0000000..3f1a066
--- /dev/null
+++ b/docs/newt/command_list/newt_info.md
@@ -0,0 +1,25 @@
+## <font color="#F2853F" style="font-size:24pt">newt info </font>
+
+Shows information about the current project.
+
+#### Usage:
+
+```no-highlight
+ newt info [flags]
+```
+
+
+#### Global Flags:
+```no-highlight
+ -l, --loglevel="WARN": Log level, defaults to WARN.
+ -o, --outfile string Filename to tee output to
+ -q, --quiet=false: Be quiet; only display error output.
+ -s, --silent=false: Be silent; don't output anything.
+ -v, --verbose=false: Enable verbose output when executing commands.
+```
+#### Description
+
+Sub-command | Explanation
+-------------| ------------------------
+info | Displays the repositories in the current project (the local as well as all the external repositories fetched). Also displays the packages in the local repository.
+
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/72d6cedb/docs/newt/command_list/newt_install.md
----------------------------------------------------------------------
diff --git a/docs/newt/command_list/newt_install.md b/docs/newt/command_list/newt_install.md
new file mode 100644
index 0000000..623d17e
--- /dev/null
+++ b/docs/newt/command_list/newt_install.md
@@ -0,0 +1,29 @@
+## <font color="#F2853F" style="font-size:24pt">newt install </font>
+
+Install project dependencies.
+
+#### Usage:
+```no-highlight
+ newt install [flags]
+```
+
+#### Flags:
+```no-highlight
+ -f, --force Force install of the repositories in project, regardless of what exists in repos directory
+```
+
+#### Global Flags:
+```no-highlight
+ -h, --help=false: help for newt
+ -o, --outfile string Filename to tee output to
+ -l, --loglevel="WARN": Log level, defaults to WARN.
+ -q, --quiet=false: Be quiet; only display error output.
+ -s, --silent=false: Be silent; don't output anything.
+ -v, --verbose=false: Enable verbose output when executing commands.
+```
+#### Description
+
+Sub-command | Explanation
+-------------| ------------------------
+install | Downloads description of all the repositories specified in the project.yml file of the current project directory. Installs all the correct versions of all the packages dictated by the project dependencies. <br> <br> Always run the command from within the project directory (i.e. remember to `cd` into the app directory after creating a new app using `newt new`) before running `newt install`.
+
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/72d6cedb/docs/newt/command_list/newt_load.md
----------------------------------------------------------------------
diff --git a/docs/newt/command_list/newt_load.md b/docs/newt/command_list/newt_load.md
new file mode 100644
index 0000000..e7fb2b9
--- /dev/null
+++ b/docs/newt/command_list/newt_load.md
@@ -0,0 +1,27 @@
+## <font color="#F2853F" style="font-size:24pt">newt load </font>
+
+Load app image to specified target.
+
+#### Usage:
+
+```no-highlight
+ newt load <target-name> [flags]
+```
+
+#### Flags:
+```no-highlight
+ -h, --help=false: help for target
+```
+#### Global Flags:
+```no-highlight
+ -l, --loglevel="WARN": Log level, defaults to WARN.
+ -o, --outfile string Filename to tee output to
+ -q, --quiet=false: Be quiet; only display error output.
+ -s, --silent=false: Be silent; don't output anything.
+ -v, --verbose=false: Enable verbose output when executing commands.
+```
+#### Description
+
+Sub-command | Explanation
+-------------| ------------------------
+load | Uses download scripts to automatically load, onto the connected board, the image built for the app defined in the target specified by <target-name>. <br> <br> If the wrong board is connected, or the target definition is wrong (i.e. the wrong values are given for bsp or app), the command will fail with error messages such as `Can not connect to J-Link via USB` or `Unspecified error -1`.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/72d6cedb/docs/newt/command_list/newt_new.md
----------------------------------------------------------------------
diff --git a/docs/newt/command_list/newt_new.md b/docs/newt/command_list/newt_new.md
index 74e3d66..511cbd3 100644
--- a/docs/newt/command_list/newt_new.md
+++ b/docs/newt/command_list/newt_new.md
@@ -1,21 +1,21 @@
## <font color="#F2853F" style="font-size:24pt">newt new </font>
-Create a new application, specified by <app-name>, from a given skeleton. If the optional <app-url> parameter is specified, then download the skeleton of the application from
-that URL instead of using the default, and create a new app directory by the name of <app-name>. Currently, the default skeleton is the [tadpole repository](https://git-wip-us.apache.org/repos/asf/incubator-mynewt-tadpole.git) in Apache Mynewt.
+Create a new application, specified by <app-name>, from a given skeleton. Currently, the default skeleton is the [blinky repository](https://git-wip-us.apache.org/repos/asf/incubator-mynewt-blinky.git) in Apache Mynewt (or [https://github.com/apache/incubator-mynewt-blinky](https://github.com/apache/incubator-mynewt-blinky) on its github mirror.)
#### Usage:
```no-highlight
- newt new [flags] <app-name> [, <app-url>]
+ newt new [flags] <app-name>
```
#### Flags:
```no-highlight
- -h, --help=false: help for app
+ -h, --help=false: help for new
```
#### Global Flags:
```no-highlight
-h, --help=false: help for newt
+ -o, --outfile string Filename to tee output to
-l, --loglevel="WARN": Log level, defaults to WARN.
-q, --quiet=false: Be quiet; only display error output.
-s, --silent=false: Be silent; don't output anything.
@@ -26,7 +26,6 @@ that URL instead of using the default, and create a new app directory by the nam
Sub-command | Usage | Explanation
-------------| -----------------------|-----------------
-newt new | newt new test_project | Creates a new app named "test_project " using the default skeleton
- | newt new myapp <app-url> | Creates a new app named "myapp" using the skeleton at the <app-url> specified
+newt new | newt new test_project | Creates a new app named "test_project " using the default skeleton from the `apache/incubator-mynewt-blinky` repo.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/72d6cedb/docs/newt/command_list/newt_pkg.md
----------------------------------------------------------------------
diff --git a/docs/newt/command_list/newt_pkg.md b/docs/newt/command_list/newt_pkg.md
deleted file mode 100644
index 38ecf33..0000000
--- a/docs/newt/command_list/newt_pkg.md
+++ /dev/null
@@ -1,61 +0,0 @@
-## <font color="#F2853F" style="font-size:24pt">newt pkg </font>
-
-Provides sub-commands to search, display and install packages in your current application or workspace.
-
-#### Usage:
-```no-highlight
- newt pkg [command][flag] input1 input2
-```
-
-#### Available Commands:
-```no-highlight
- list List pkgs in the current app
- checkdeps Check pkg dependencies
- hunt Search for pkg from pkg-lists
- show Show the contents of a pkg.
- install Install a pkg
- remove Remove a pkg
-```
-#### Flags:
-```no-highlight
- -h, --help=false: help for pkg
-
-#### Global Flags:
-
- -l, --loglevel="WARN": Log level, defaults to WARN.
- -q, --quiet=false: Be quiet; only display error output.
- -s, --silent=false: Be silent; don't output anything.
- -v, --verbose=false: Enable verbose output when executing commands.
-```
-#### Description
-
-Sub-command | Explanation
--------------| ------------------------
-list | List all the pkgs in the current app. The output shows the name, version, path, and any additional attributes of each pkg in the app such as dependencies, capabilities, and linker scripts. The newt command gets the attributes of each pkg from the corresponsing pkg.yml description file.
-checkdeps | Resolve all dependencies in the local app. This command goes through all pkgs currently installed, checks their dependencies, and prints any unresolved dependencies between pkgs.
-search | Searches for a pkg, specified by `input1`. The local app, along with all remote apps (pkg-lists) are searched. All matched pkgs are shown along with the pkg-list informaton. Installed pkgs are called out as such. The command can be invoked from anywhere in the app.
-show | Show the contents of the pkg named `input2` found in the pkg-list named `input1`. The pkg-list name is optional; if only the pkg name is given as the argument it is resolved using all the pkg-lists installed in the current app. If the pkg is present in multiple pkg-lists it will list all of them along with the pkg-list information for each.
-install | Install the pkg specified by `input2` from the pkg-list named `input1`. The command downloads the pkg from the github repository using the URL in the pkg-list description file (typically downloaded as 'input1@<branch-name>.yml' in .app/pkg-lists). It also downloads all the dependencies (constituent pkgs) as decribed in the pkg's description file ('pkg.yml') and installs all of them. The pkg-list name is optional. If only the pkg name is given as the argument, the command looks for the pkg name in all the pkg-lists in the local app and installs accordingly. A pkg is installed by this command only if it has not already been installed.
-remove | Remove a pkg named `input2` from pkg-list `input1`, if pkg-list is specified. Otherwise only one input required - that of the name of the pkg to be removed from the local app.
-
-
-
-
-#### Command-specific flags
-
-Sub-command | Available flags | Explanation
--------------| ----------------|------------
-install | -b, --branch="<branch-name>" | Installs the pkgs from the branch name or tag of the pkg-list specified
-
-#### Examples
-
-Sub-command | Usage | Explanation
--------------| -----------------------|-----------------
-list | newt pkg list | CList all of the pkgs in the current app and the details of the pkgs.
-checkdeps | newt pkg checkdeps | Checks all the dependencies between pkgs in the app. Lists any unresolved dependencies.
-hunt | newt pkg hunt blinky| Hunts for the pkg named 'blinky'. The command can be invoked from anywhere in the app. Results show if the pkg is installed and which pkg-list, if any, has the pkg.
-show | newt pkg show larva libs/os | Show the contents of the pkg named 'libs/os' in the pkg-list named larva. The contents are essentially derived from the pkg's 'pkg.yml' file.
-install | newt pkg install hw/bsp/stm32f3discovery | Downloads and installs the pkg named "stm32f3discovery" (specified with its full path name inside the remote app) along with all its dependencies from the remote app on github. Since no pkg-list is specified, the URL for the remote app in the pkg-list description file found in the local app (in .app/pkg-lists for the project) is used.
-remove | newt pkg remove larva blinky| Removes the pkg named blinky only from the pkg-list named larva
-remove | newt pkg remove blinky| Removes the pkg named blinky from the local app
-
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/72d6cedb/docs/newt/command_list/newt_run.md
----------------------------------------------------------------------
diff --git a/docs/newt/command_list/newt_run.md b/docs/newt/command_list/newt_run.md
new file mode 100644
index 0000000..269c244
--- /dev/null
+++ b/docs/newt/command_list/newt_run.md
@@ -0,0 +1,39 @@
+## <font color="#F2853F" style="font-size:24pt">newt run </font>
+
+A single command to do four steps - build a target, create-image, load image on a board, and start a debug session with the image on board.
+
+**Note**: If version number is omitted, create-image step is skipped
+
+#### Usage:
+
+```no-highlight
+ newt run <target-name> [<version>][flags]
+```
+
+#### Flags:
+```no-highlight
+ -h, --help=false: help for target
+```
+
+#### Global Flags:
+```no-highlight
+ -l, --loglevel="WARN": Log level, defaults to WARN.
+ -o, --outfile string Filename to tee log output to
+ -q, --quiet=false: Be quiet; only display error output.
+ -s, --silent=false: Be silent; don't output anything.
+ -v, --verbose=false: Enable verbose output when executing commands.
+```
+
+#### Description
+
+Sub-command | Explanation
+-------------| ------------------------
+run | Same as running `build <target>`, `create-image <target> <version>`, `load <target>`, and `debug <target>`.
+
+
+#### Examples
+
+ Sub-command | Usage | Explanation
+-------------| -----------------------|-----------------
+run | newt run blink_rigado | First compiles and builds executable for running the app defined in the target `blink_rigado` on the board defined in the same target, then loads image onto the board, and finally opens an active GNU gdb debugging session to run the image.
+run | newt run ble_rigado 0.1.0.0 | First compiles and builds executable for running the app defined in the target `ble_rigado` on the board defined in the same target, then signs and creates image with version number 0.1.0.0, loads the image onto the board, and finally opens an active GNU gdb debugging session to run the image. <br> <br> Note that if there is no bootloader available for a particular board/kit, a signed image creation step is not necessary.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/72d6cedb/docs/newt/command_list/newt_size.md
----------------------------------------------------------------------
diff --git a/docs/newt/command_list/newt_size.md b/docs/newt/command_list/newt_size.md
new file mode 100644
index 0000000..b345f4b
--- /dev/null
+++ b/docs/newt/command_list/newt_size.md
@@ -0,0 +1,56 @@
+## <font color="#F2853F" style="font-size:24pt">newt size </font>
+
+Calculate the size of target components specified by <target-name>
+
+#### Usage:
+
+```no-highlight
+ newt size <target-name> [flags]
+```
+
+#### Flags:
+```no-highlight
+ -h, --help=false: help for target
+```
+
+#### Global Flags:
+```no-highlight
+ -l, --loglevel="WARN": Log level, defaults to WARN.
+ -o, --outfile string Filename to tee log output to
+ -q, --quiet=false: Be quiet; only display error output.
+ -s, --silent=false: Be silent; don't output anything.
+ -v, --verbose=false: Enable verbose output when executing commands.
+```
+
+
+#### Examples
+
+ Sub-command | Usage | Explanation
+-------------| -----------------------|-----------------
+size | newt size blink_rigado | Inspects and lists the RAM and Flash memory use by each component (object files and libraries) of the target.
+
+#### Example output for `newt size boot_olimex`:
+
+```no-highlight
+
+$ newt size blink_rigado
+ FLASH RAM
+ 9 223 *fill*
+ 1052 0 baselibc.a
+ 195 1116 blinky.a
+ 616 452 bmd300eval.a
+ 64 0 cmsis-core.a
+ 124 0 crt0.o
+ 8 0 crti.o
+ 16 0 crtn.o
+ 277 196 full.a
+ 20 8 hal.a
+ 96 1068 libg.a
+ 1452 0 libgcc.a
+ 332 28 nrf52xxx.a
+ 3143 677 os.a
+
+objsize
+ text data bss dec hex filename
+ 7404 1172 2212 10788 2a24 /Users/<username>/dev/rigado/bin/blink_rigado/apps/blinky/blinky.elf
+```
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/72d6cedb/docs/newt/command_list/newt_target.md
----------------------------------------------------------------------
diff --git a/docs/newt/command_list/newt_target.md b/docs/newt/command_list/newt_target.md
index 85651aa..2921506 100644
--- a/docs/newt/command_list/newt_target.md
+++ b/docs/newt/command_list/newt_target.md
@@ -5,31 +5,29 @@ Provides commands to create, build, delete, and query targets.
#### Usage:
```no-highlight
- newt target [command] input1 [flag1] [flag2]
+ newt target [command] input1 [input2]
```
#### Available Commands:
```no-highlight
+ show View target configuration variables
set Set target configuration variable
- unset Unset target configuration variable
- delete Delete target
create Create a target
- show View target configuration variables
- build Build target
- test Test target
- size Size of the target
- label Add image header to target binary
- download Download project to target
- debug Open debugger session to target
- export Export target
- import Import target
+ delete Delete target
+ copy Copy target
+ vars Show variable names possible for a target
```
+
#### Flags:
+
```no-highlight
-h, --help=false: help for target
```
+
#### Global Flags:
+
```no-highlight
-l, --loglevel="WARN": Log level, defaults to WARN.
+ -o, --outfile string Filename to tee log output to
-q, --quiet=false: Be quiet; only display error output.
-s, --silent=false: Be silent; don't output anything.
-v, --verbose=false: Enable verbose output when executing commands.
@@ -38,93 +36,24 @@ Provides commands to create, build, delete, and query targets.
Sub-command | Explanation
-------------| ------------------------
-set | Set attributes (variables) of the target. Currently the list of possible attributes (variables) are:``` arch, compiler, compiler_def, project, bsp, pkg, identities, capabilities, dependencies, cflags, lflags```. Typically only the first 5 need to be set for a hardware target. For a simulated target, e.g. for software testing purposes, `arch=sim`, `compiler=sim`, and `pkg=<pkg name to be tested>`. You cannot set both the project and pkg for a target.
- | To display all the existing values for any target attribute (variable), you can simply hit return after that variable. For example, `newt target set target1 arch` displays the valid values available for the attribute `arch` for a target named `target1`.
-unset | Unset attributes of the target in its configuration.
-delete | Deletes only the description for the target. Does not delete the target directory with associated binaries. If you want to clean out the binaries, list files, and executables use`newt target build <target-name> clean` **before** deleting the target!
-create | Creates a target description or build definition by the name `input1`. By default it assigns the sim (simulator) architecture to it which allows you to build new projects and software on your native OS and try it out.
-show | Display the configuration defined for the target named `input1`. If no `input1` is specified then show the details for all the targets in the app.
-build | Build the source code into an image that can be loaded on the hardware associated with the target named `input1` to do the application enabled by the 'project' associated with that target (via the target definition). It creates 'bin/' and 'bin/<input1>/' subdirectories inside the base directory for the project, compiles and generates binaries and executables, and places them in 'bin/<input1>/.
-test | Test a pkg on the target named `input1`. The pkg is either supplied as an argument to the command line invocation of `newt target test` or added as part of the target definition. If only the target is specified as `input1`, then the pkg in the target's definition is automatically chosen to be tested. You currently cannot test an entire project on a hardware target. The test command is envisioned for use if one or two pkgs gets updated and each needs to be tested against a target. Alternatively, a script may be written for a series of tests on several pkgs.
-size | Displays the memory used (in bytes) by the component libraries that have been compiled and linked to form the executable for the specified target build (input1). The memory usage of the different components is shown by each memory type available in the bsp (board support package) used in the target e.g. RAM, flash, CCM etc.
-label | Appends an image header to the created binary file for the target named `input1`. Version number in the header is set to the value given as `[flag1]`. The manifest.json file in the directory with the binaries (project/<project-name>/bin/<target-name>) reflects the version number. A manifest.json file is created if none exists for the target.
-export | Exports the configurations of the specified target `input1`. If -a or -export-all flag is used, then all targets are exported and printed out to standard out. You may redirect the output to a file.
-import | Import one or more target configuration from standard input or a file. Each target starts with `@target=<target-name>` followed by the attributes. The list of targets should end with `@endtargets`.
-download | Downloads the binary executable `<target-name>.elf.bin` to the board.
-debug | Downloads the binary executable `<target-name>.elf.bin` to the board and starts up the openocd/gdb combination session. gdb takes over the terminal.
+show | Shows what variables (attributes) are set on the specified target `input1`. If no `input1` is specified then show the configuration for all the targets defined so far.
+set | Set variables (attributes) of the target named via `input1`. Currently the list of possible attributes (variables) are:`app`, `bsp`, `build_profile`, `features`, `cflags`, `lflags`. For a simulated target, e.g. for software testing purposes, `bsp` is set to `@apache-mynewt-core/hw/bsp/native`.
+ | To display all the existing values for a target variable (attribute), you can simply hit return after that variable. For example, `newt target set input1 app` displays the valid values available for the variable `app` for a target named `input11`.
+ | Currently, the only two values available for `build_profile` are `optimized` and `debug`.
+create | Creates an empty target definition by the name of `input1`.
+delete | Deletes only the description for the target. Does not delete the target directory with associated binaries. If you want to clean out the binaries, list files, and executables use`newt target clean <target-name>` **before** deleting the target!
+copy | Creates a new target by the name of `input2` by cloning the definition of an existing target named `input1`.
+vars | Shows what variables (attributes) are available to set on the target
-#### Command-specific flags
-
-Sub-command | Available flags | Explanation
--------------| ----------------|------------
-build | clean | All the binaries and object files for the specified target will be removed. The subdirectory named after the specified target within that project is removed.
-build clean | all | All the binaries and object files for all targets are removed, and subdirectories of all targets for the project are removed. However, the entire repository is not emptied since any pkgs or projects that the specified target doesn't reference are not touched.
-export | -a, -export-all | Export all targets. `input1` is not necessary when this flag is used.
-import | -a, -import-all | Import all targets typed into standard input or redirected from a file.
-
#### Examples
Sub-command | Usage | Explanation
-------------| -----------------------|-----------------
-set | newt target set myblinky compiler=arm-none-eabi-m4 | Set the compiler for the 'myblinky' target to the gcc compiler for embedded ARM chips.
-set | newt target set myblinky compiler | Lists the valid values currently available to be assigned for target attribute (variable) 'compiler'. For example, arm-none-eabi-m0, arm-none-eabi-m4, sim. As Mynewt grows, the number of possible values will grow.
-unset | newt target unset myblinky compiler | Remove the setting for the compiler for the 'myblinky' target.
-delete | newt target delete myblinky | Delete the target description for the target named 'myblinky'. Note that it does not remove any binaries or clean out the directory for this target.
-create | newt target create blink_f3disc | Create a new target description by the name 'blink_f3disc'. The architecture is 'sim' by default and can be changed using subcommand 'set' above.
-show | newt target show myblinky | Show the target attributes set for 'myblinky'
-build | newt target build blink_f3disc | Compile the source code for the target named blink_f3disc and generate binaries that can be loaded into the target hardware.
-test | newt target test test_target pkg=libs/os | Tests the pkg named 'libs/os' against the target named 'test_target'
-size | newt target size -v boot_olimex | Displays the memory footprint in bytes for all object and linked files for the target named boot_olimex. The -v option shows all the steps of loading and inspecting the different pkgs required for the project on this target as well as the different memory locations available. The memory usage for each component is broken up into the different memory types used. An example output is shown for `newt target size boot_olimex` below.
-label | newt target label boot_olimex 2.0.1 | Appends an image header specifying the version number as 2.0.1 to the binary image file for target named boot_olimex. The version number in the manifest.json file for this target is also updated to 2.0.1.
-export | newt target export -a > my_exports.txt | Export all build targets from the current app, and redirect output to a file named 'my_exports.txt'.
-export | newt target export -export-all | Export all build targets from the current app, and print them to standard output on the screen.
-export | newt target export my_target | Export only target named 'my_target' and print it to standard output on the screen.
-import | newt target import ex_tgt_1 < exported_targets.txt | Imports the target configuration for 'ex_tgt_1' in 'exported_targets.txt'.
-import | newt target import -a < in_targets.txt | Imports all the targets specified in the file named `in_targets.txt`. A sample file is shown after this table.
-import | newt target import test3 | Awaits all the configuration variables for a target named 'test3'. This allows you to define all the attributes in one shot e.g. by cutting and pasting the contents of `in_targets.txt` file shown at the bottom of this page.
-size | newt target size blink_nordic | Inspects and lists the RAM and Flash memory use by each component (object files and libraries) of the target.
-download | newt target -v -lVERBOSE download blinky | Downloads `blinky.elf.bin` to the hardware in verbose mode with logging turned on at VERBOSE level.
-debug | newt target debug blinky | Downloads `blinky.elf.bin` to the hardware, opens up a gdb session with `blinky.elf` in the terminal, and halts for further input in gdb.
-
-
-#### Example output for `newt target size boot_olimex`:
-
-```no-highlight
-
-$ newt target size boot_olimex
-Inspecting target boot_olimex (project = boot)
- FLASH CCM RAM
- 13 0 3 *fill*
- 239 0 0 boot.o
- 124 0 0 crt0.o
- 84 0 40 crtbegin.o
- 4 0 4 crtend.o
- 8 0 0 crti.o
- 16 0 0 crtn.o
- 1396 0 50 libbaselibc.a
- 2054 0 1104 libbootutil.a
- 84 0 0 libcmsis-core.a
- 266 0 4 libfs.a
- 80 0 0 libg.a
- 1452 0 0 libgcc.a
- 940 0 8 libhal.a
- 12130 0 538 libnffs.a
- 1172 3072 68 libolimex_stm32-e407_devboard.a
- 3654 0 645 libos.a
- 1504 0 32 libstm32f4xx.a
-```
+show | newt target show myble | Shows all variable settings for the target named "myble" i.e. what app, bsp, build_profile, features, cflags are set to. Note that all variables are not required to be set in order to successfully define a target.
+show | newt target show | Shows all variable settings for all the targets defined.
+set | newt target set myble app=@apache-mynewt-core/apps/bletiny | Assign `bletiny` to be the application to be included in the build for the target named `myble`.
+copy | newt target copy my_blinky_sim test1 | Creates a new target by the name `test1` by copying the attributes from `my_blinky_sim`
+vars | newt target vars | Shows all the variables newt recognizes - app, bsp, build_profile, features
-#### Example content for `in_targets.txt` file used for importing targets `test3` and `test4`.
-> @target=test3
-project=blinked
-arch=sim
-compiler_def=debug
-compiler=arm-none-eabi-m4
-@target=test4
-project=super_blinky
-arch=sim
-compiler_def=debug
-compiler=arm-none-eabi-m4
-@endtargets
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/72d6cedb/docs/newt/command_list/newt_test.md
----------------------------------------------------------------------
diff --git a/docs/newt/command_list/newt_test.md b/docs/newt/command_list/newt_test.md
new file mode 100644
index 0000000..8a33968
--- /dev/null
+++ b/docs/newt/command_list/newt_test.md
@@ -0,0 +1,43 @@
+## <font color="#F2853F" style="font-size:24pt">newt test </font>
+
+Executes unit tests for one or more packages
+
+#### Usage:
+
+```no-highlight
+ newt test [flags] input1 [input2] ...
+```
+
+#### Flags:
+```no-highlight
+ -h, --help=false: help for target
+```
+
+#### Global Flags:
+```no-highlight
+ -l, --loglevel="WARN": Log level, defaults to WARN.
+ -o, --outfile string Filename to tee log output to
+ -q, --quiet=false: Be quiet; only display error output.
+ -s, --silent=false: Be silent; don't output anything.
+ -v, --verbose=false: Enable verbose output when executing commands.
+```
+
+#### Description
+
+Sub-command | Explanation
+-------------| ------------------------
+test | Test a pkg named `input1`. You may specify multiple packages separated by space in the same command.
+
+
+#### Examples
+
+ Sub-command | Usage | Explanation
+-------------| -----------------------|-----------------
+test | newt test targets/myble2 | Tests the pkg named 'targets/myble2'
+ | newt test @apache-mynewt-core/libs/os | Tests the libs/os pkg in the repo named apache-mynewt-core
+ | newt test libs/os libs/json | Tests the `libs/os` and `libs/json packages` in the current repo. Should indicate at the end of the output: <br> `Passed tests: [libs/os libs/json]` <br> `All tests passed`
+
+
+
+
+
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/72d6cedb/docs/newt/command_list/newt_upgrade.md
----------------------------------------------------------------------
diff --git a/docs/newt/command_list/newt_upgrade.md b/docs/newt/command_list/newt_upgrade.md
new file mode 100644
index 0000000..6c07692
--- /dev/null
+++ b/docs/newt/command_list/newt_upgrade.md
@@ -0,0 +1,26 @@
+## <font color="#F2853F" style="font-size:24pt">newt upgrade </font>
+
+Upgrade project dependencies
+
+#### Usage:
+```no-highlight
+ newt pkg [command][flag] input1 input2
+```
+
+#### Flags:
+```no-highlight
+ -f, --force Force upgrade of the repositories to latest state in project.yml
+
+#### Global Flags:
+
+ -l, --loglevel="WARN": Log level, defaults to WARN.
+ -o, --outfile string Filename to tee log output to
+ -q, --quiet=false: Be quiet; only display error output.
+ -s, --silent=false: Be silent; don't output anything.
+ -v, --verbose=false: Enable verbose output when executing commands.
+```
+#### Description
+
+Sub-command | Explanation
+-------------| ------------------------
+upgrade | If you have changed the project.yml description for the project, you need to run this command to update all the package dependencies.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/72d6cedb/docs/newt/command_list/newt_version.md
----------------------------------------------------------------------
diff --git a/docs/newt/command_list/newt_version.md b/docs/newt/command_list/newt_version.md
index a4d0ffc..956d96e 100644
--- a/docs/newt/command_list/newt_version.md
+++ b/docs/newt/command_list/newt_version.md
@@ -12,9 +12,11 @@ Allows you to query the version of newt installed in your application space.
```no-highlight
-h, --help=false: help for version
```
+
#### Global Flags:
```no-highlight
-l, --loglevel string Log level, defaults to WARN. (default "WARN")
+ -o, --outfile string Filename to tee output to
-q, --quiet Be quiet; only display error output.
-s, --silent Be silent; don't output anything.
-v, --verbose Enable verbose output when executing commands.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/72d6cedb/docs/os/tutorials/arduino_zero.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/arduino_zero.md b/docs/os/tutorials/arduino_zero.md
index 98a99cc..9bee4fa 100644
--- a/docs/os/tutorials/arduino_zero.md
+++ b/docs/os/tutorials/arduino_zero.md
@@ -84,19 +84,27 @@ $
Next, you need to tell Newt what to build. For the Arduino Zero, we are going to
generate both a bootloader, and an image target.
-To generate the bootloader target, you need to specify the following options:
+To generate the bootloader target, you need to specify the following options. The output of the commands (indicating success) have been suppressed for easier readability.
```no-highlight
$ newt target create arduino_boot
-Target targets/arduino_boot successfully created
$ newt target set arduino_boot bsp=@mynewt_arduino_zero/hw/bsp/arduino_zero
-Target targets/arduino_boot successfully set target.bsp to @mynewt_arduino_zero/hw/bsp/arduino_zero
$ newt target set arduino_boot app=@apache-mynewt-core/apps/boot
-Target targets/arduino_boot successfully set target.app to @apache-mynewt-core/apps/boot
$ newt target set arduino_boot build_profile=optimized
-Target targets/arduino_boot successfully set target.build_profile to optimized
+```
+
+<br>
+
+If you have an Arduino Zero Pro, you have to set the following next:
+
+```
$ newt target set arduino_boot features=arduino_zero_pro
-Target targets/arduino_boot successfully set pkg.features to arduino_zero_pro
+```
+
+If you have an Arduino Zero, you have to set the following instead:
+
+```
+$ newt target set arduino_boot features=arduino_zero
```
<br>
@@ -109,12 +117,10 @@ These commands do a few things:
* Set the board support package for the target to
```@mynewt_arduino_zero/hw/bsp/arduino_zero```. This is a reference to the downloaded
Arduino Zero support from Github.
- * Use the "optimized" build profile for the ```arduino_boot``` target. This
+ * Use the "optimized" build profile for the `arduino_boot` target. This
instructs Newt to generate smaller and more efficient code for this target.
This setting is necessary due to the bootloader's strict size constraints.
- * Tells the Board Support Package to enable support for the Arduino Zero Pro, and not
- the Arduino Zero. This is done through setting a build feature. If you are building
- for an Arduino Zero, and not a Zero Pro, this feature should be set to ```arduino_zero```.
+ * Tells the Board Support Package to enable support for the Arduino Zero Pro or the Arduino Zero. Set it to `arduino_zero` or `arduino_zero_pro` depending on the board you have.
<br>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/72d6cedb/mkdocs.yml
----------------------------------------------------------------------
diff --git a/mkdocs.yml b/mkdocs.yml
index dd240c5..890a04b 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -322,13 +322,21 @@ pages:
- Newt Theory of Ops: 'newt/newt_operation.md'
- User Guide:
- toc: 'newt/newt_ops.md'
- - 'Command list':
- - 'newt app': 'newt/command_list/newt_app.md'
- - 'newt help': 'newt/command_list/newt_help.md'
- - 'newt new': 'newt/command_list/newt_new.md'
- - 'newt pkg': 'newt/command_list/newt_pkg.md'
- - 'newt target': 'newt/command_list/newt_target.md'
- - 'newt version': 'newt/command_list/newt_version.md'
+ - 'newt build': 'newt/command_list/newt_build.md'
+ - 'newt clean': 'newt/command_list/newt_clean.md'
+ - 'newt create-image': 'newt/command_list/newt_create_image.md'
+ - 'newt debug': 'newt/command_list/newt_debug.md'
+ - 'newt help': 'newt/command_list/newt_help.md'
+ - 'newt info': 'newt/command_list/newt_info.md'
+ - 'newt install': 'newt/command_list/newt_install.md'
+ - 'newt load': 'newt/command_list/newt_load.md'
+ - 'newt new': 'newt/command_list/newt_new.md'
+ - 'newt run': 'newt/command_list/newt_run.md'
+ - 'newt size': 'newt/command_list/newt_size.md'
+ - 'newt target': 'newt/command_list/newt_target.md'
+ - 'newt test': 'newt/command_list/newt_test.md'
+ - 'newt upgrade': 'newt/command_list/newt_upgrade.md'
+ - 'newt version': 'newt/command_list/newt_version.md'
- Newt Manager Manual:
- 'Introduction': 'newtmgr/overview.md'
- 'Install': 'newtmgr/installing.md'