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 2017/03/03 01:02:38 UTC
[1/7] incubator-mynewt-site git commit: Update newt command
documentation, sysconfig overwrites, events, bsp list
Repository: incubator-mynewt-site
Updated Branches:
refs/heads/asf-site 855b60039 -> 555f6f651
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/command_list/newt_sync/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/command_list/newt_sync/index.html b/latest/newt/command_list/newt_sync/index.html
new file mode 100644
index 0000000..6b4469f
--- /dev/null
+++ b/latest/newt/command_list/newt_sync/index.html
@@ -0,0 +1,584 @@
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <meta charset="utf-8">
+ <meta http-equiv="X-UA-Compatible" content="IE=edge">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+
+ <!-- This is broken by doc revisioning.
+ <link rel="canonical" href="http://mynewt.apache.org/newt/command_list/newt_sync/"> -->
+ <link rel="shortcut icon" href="../../../img/favicon.ico">
+
+ <title>newt sync - Apache Mynewt</title>
+
+ <link href="../../../css/bootstrap-3.0.3.min.css" rel="stylesheet">
+ <link rel="stylesheet" href="../../../css/highlight.css">
+ <link href="../../../css/base.css" rel="stylesheet">
+ <link href="../../../css/custom.css" rel="stylesheet">
+ <link href="../../../css/v2.css" rel="stylesheet">
+ <link href="https://fonts.googleapis.com/css?family=Lato" rel="stylesheet">
+ <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css">
+ <link href="../../../extra.css" rel="stylesheet">
+
+ <!-- HTML5 shim and Respond.js IE8 support of HTML5 elements and media queries -->
+ <!--[if lt IE 9]>
+ <script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script>
+ <script src="https://oss.maxcdn.com/libs/respond.js/1.3.0/respond.min.js"></script>
+ <![endif]-->
+
+
+ <script>
+ (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
+ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
+ m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
+ })(window,document,'script','//www.google-analytics.com/analytics.js','ga');
+
+ ga('create', 'UA-72162311-1', 'auto');
+ ga('send', 'pageview');
+ </script>
+
+ </head>
+
+
+ <body class="newt sync">
+
+
+ <div class="container">
+ <div class="row v2-main-banner">
+ <a class="logo-cell" href="/">
+ <img class="logo" src="/img/logo.png">
+ </a>
+ <div class="tagline-cell">
+ <h4 class="tagline">An OS to build, deploy and securely manage billions of devices</h4>
+ </div>
+ <div class="news-cell">
+ <div class="well">
+ <h4>Latest News:</h4> <a href="/download">Apache Mynewt 1.0.0-b2</a> released (Feb 15, 2017)
+ </div>
+ </div>
+ </div>
+</div>
+
+
+
+
+
+
+
+
+<nav id="navbar" class="navbar navbar-inverse affix-top" data-spy="affix" data-offset-top="150" role="navigation">
+ <div class="container">
+ <!-- Collapsed navigation -->
+ <div class="navbar-header">
+ <!-- Expander button -->
+ <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
+ <span class="sr-only">Toggle navigation</span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ </button>
+
+ </div>
+
+ <!-- Expanded navigation -->
+ <div class="navbar-collapse collapse">
+ <!-- Main navigation -->
+ <ul class="nav navbar-nav navbar-right">
+ <li
+ class=""
+>
+ <a href="/"><i class="fa fa-home" style="font-size: larger;"></i></a>
+ </li>
+ <li
+ class="important"
+>
+ <a href="/quick-start/">Quick Start</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/about/">About</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/talks/">Talks</a>
+ </li>
+ <li
+ class="active"
+>
+ <a href="/latest/os/introduction">Documentation</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/download/">Download</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/community/">Community</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/events/">Events</a>
+ </li>
+ </ul>
+
+ <!-- Search, Navigation and Repo links -->
+ <ul class="nav navbar-nav navbar-right">
+
+ </ul>
+ </div>
+ </div>
+</nav>
+
+
+
+ <div class="container">
+
+ <div class="row">
+ <div class="col-md-3 v2-sidebar sidebar-container"><div id="docSidebar" class="hidden-print" role="complementary">
+ <div class="top">
+ <div role="search">
+ <form id="rtd-search-form" class="wy-form" action="../../../search.html" method="get">
+ <div class="form-group">
+ <input type="text" name="q" class="form-control" placeholder="Search documentation" />
+ </div>
+ </form>
+ </div>
+ </div>
+ <ul class="toc-nav">
+ <li class="doc-version">
+<select class="form-control" onchange="if (this.value) window.location.href=this.value">
+
+ <option
+ value="/develop/os/introduction"
+ selected="selected"
+ >
+ Version: develop (latest)
+ </option>
+
+ <option
+ value="/v0_9_0/os/introduction"
+
+ >
+ Version: 0.9.0
+ </option>
+
+</select>
+</li>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ <li ><a href="../../../os/introduction/">Mynewt Documentation</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../../../os/get_started/get_started/">Basic Setup</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../../os/get_started/vocabulary/">Concepts</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../os/tutorials/tutorials/">Tutorials</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../os/os_user_guide/">OS User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../../network/ble/ble_intro/
+">BLE User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../newt_intro/">Newt Tool Guide</a>
+
+
+ <ul>
+
+
+
+
+
+ <li >
+ <a href="../../newt_operation/">Newt Theory of Ops</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../newt_ops/">Command Guide</a>
+
+
+ <ul>
+
+
+
+
+
+ <li >
+ <a href="../newt_build/">newt build</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_clean/">newt clean</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_create_image/">newt create-image</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_debug/">newt debug</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_help/">newt help</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_info/">newt info</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_install/">newt install</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_load/">newt load</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_mfg/">newt mfg</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_new/">newt new</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_run/">newt run</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_size/">newt size</a>
+ </li>
+
+
+
+
+
+ <li class="active">
+ <a href="./">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_target/">newt target</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_test/">newt test</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_upgrade/">newt upgrade</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_vals/">newt vals</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_version/">newt version</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../newtmgr/overview/">Newt Manager Guide</a>
+
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../../faq/how_to_edit_docs/
+">Appendix</a>
+
+
+ </li>
+
+
+
+ </ul>
+</div></div>
+
+ <div class="col-md-9" role="main">
+ <div class="doc-header">
+ <div role="navigation" aria-label="breadcrumbs navigation">
+ <ul class="wy-breadcrumbs pull-right">
+ <li><a href="/latest/os/introduction">Docs</a></li>
+
+
+
+ <li>» <a href="../../newt_intro/">Newt Tool Guide</a></li>
+
+
+
+ <li>» <a href="../../newt_ops/">Command Guide</a></li>
+
+
+
+ <li>» newt sync</li>
+
+
+
+ </ul>
+</div>
+ </div>
+
+ <h2 id="newt-sync"><font color="#F2853F" style="font-size:24pt">newt sync </font></h2>
+<p>Synchronize and refresh the contents of the local copy of all the repositories used in the project with the latest updates maintained in the remote repositories. </p>
+<h4 id="usage">Usage:</h4>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt sync [flags]
+</pre></div>
+
+
+<h4 id="flags">Flags:</h4>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -f, --force Force overwrite of existing remote repository
+
+#### Global Flags:
+```no-highlight
+ -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
+</pre></div>
+
+
+<h4 id="description">Description</h4>
+<p>Synchronize project dependencies and repositories. Prior to 1.0.0 release, the command deletes and resynchronizes each repository. Post 1.0.0, it will abort the synchronization if there are any local changes to any repository. Using the -f to force overwrite of existing repository will stash and save the changes while pulling in all the latest changes from the remote repository. </p>
+
+ <div class="row">
+
+
+
+
+<ul class="nav nav-pills" style="margin-bottom: 10px">
+ <li>
+
+ <a href=../newt_size/>
+ <span class="fa fa-arrow-left"></span>
+ Previous: newt size
+ </a>
+
+ </li>
+ <li class="pull-right">
+
+ <a href=../newt_target/>
+ Next: newt target
+ <span class="fa fa-arrow-right"></span>
+ </a>
+
+ </li>
+</ul>
+ </div>
+ <footer class="row">
+ <div class="col-xs-12">
+
+ <p class="copyright">Apache Mynewt (incubating) is available under Apache License, version 2.0.</p>
+
+ </div>
+ <div class="col-xs-12">
+ <div class="logos">
+ <img src="/img/asf_logo_wide_small.png" alt="Apache" title="Apache">
+ <small class="footnote">
+ MyNewt is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
+ </small>
+ <img src="/img/egg-logo2.png" alt="Apache Incubator" title="Apache Incubator">
+ </div>
+ </div>
+</footer>
+ </div>
+ </div>
+
+
+ </div>
+
+ <script src="../../../js/jquery-1.10.2.min.js"></script>
+ <script src="../../../js/bootstrap-3.0.3.min.js"></script>
+ <script src="../../../js/highlight.pack.js"></script>
+ <script src="../../../js/base.js"></script>
+ <script src="../../../js/custom.js"></script>
+
+ </body>
+</html>
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/command_list/newt_target/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/command_list/newt_target/index.html b/latest/newt/command_list/newt_target/index.html
index 2dcd63e..5b68983 100644
--- a/latest/newt/command_list/newt_target/index.html
+++ b/latest/newt/command_list/newt_target/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -388,6 +388,14 @@
+ <li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
<li class="active">
<a href="./">newt target</a>
</li>
@@ -496,14 +504,14 @@
</div>
<h2 id="newt-target"><font color="#F2853F" style="font-size:24pt">newt target </font></h2>
-<p>Provides commands to create, build, delete, and query targets. </p>
+<p>Commands to create, delete, configure and query targets. </p>
<h4 id="usage">Usage:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt target [command] input1 [input2]
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt target [command] [flags]
</pre></div>
<h4 id="available-commands">Available Commands:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> config View target system configuration
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> config View or populate a target's system configuration settings
copy Copy target
create Create a target
delete Delete target
@@ -514,21 +522,19 @@
</pre></div>
-<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for target
-</pre></div>
-
-
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -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.
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
</pre></div>
<h4 id="description">Description</h4>
+<p>The target command provides subcommands to create, build, delete, and query targets. The subcommands take one or two <code>target-name</code> arguments. </p>
<table>
<thead>
<tr>
@@ -539,43 +545,35 @@
<tbody>
<tr>
<td>config</td>
-<td>Displays the specified target's system configuration. The configuration for any package is listed in its <code>syscfg.yml</code> file. A target build consists of several packages. The command lists the settings for the config variables from all the included packages. If the default values have not been changed then the default values will be seen.</td>
+<td>The config command allows you to view or populate a target's system configuration settings. A target's system configuration settings include the settings of all the packages it includes. The settings for a package are listed in the package's <code>syscfg.yml</code> file. The <code>config</code> command has two subcommands: <code>show</code> and <code>init</code>. <br><br> The config show <target-name> command displays the system configuration setting definitions and values for all the packages that the <code>target-name</code> target includes. <br><br>The config init <target-name> command populates the target's <code>syscfg.yml</code> file with the system configuration values for all the packages that the <code>target-name</code> target includes.</td>
</tr>
<tr>
<td>copy</td>
-<td>Set variables (attributes) of the target named via <code>input1</code>. Currently the list of possible attributes (variables) are:<code>app</code>, <code>bsp</code>, <code>build_profile</code>, <code>cflags</code>, <code>lflags</code>. For a simulated target, e.g. for software testing purposes, <code>bsp</code> is set to <code>@apache-mynewt-core/hw/bsp/native</code>.</td>
+<td>The copy <src-target> <dst-target> command creates a new target named <code>dst-target</code> by cloning the <code>src-target</code> target.</td>
</tr>
<tr>
<td>create</td>
-<td>Creates an empty target definition by the name of <code>input1</code>.</td>
+<td>The create <target-name> command creates an empty target named <code>target-name</code>. It creates the <code>targets/target-name</code> directory and the skeleton <code>pkg.yml</code> and <code>target.yml</code> files in the directory.</td>
</tr>
<tr>
<td>delete</td>
-<td>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<code>newt clean <target-name></code> <strong>before</strong> deleting the target!</td>
+<td>The delete <target-name> command deletes the description for the <code>target-name</code> target. It deletes the 'targets/target-name' directory. It does not delete the 'bin/targets/target-name' directory where the build artifacts are stored. If you want to delete the build artifacts, run the <code>newt clean <target-name></code> command <strong>before</strong> deleting the target.</td>
</tr>
<tr>
<td>dep</td>
-<td>Creates dependency tree for packages in the code for a target. Display shows each package followed by the list of libraries or packages that it depends on.</td>
+<td>The dep <target-name> command displays a dependency tree for the packages that the <code>target-name</code> target includes. It shows each package followed by the list of libraries or packages that it depends on.</td>
</tr>
<tr>
<td>revdep</td>
-<td>Creates the reverse dependency tree for packages in the code for a target. Display shows each package followed by the list of libraries or packages that depend on it.</td>
+<td>The revdep <target-name> command displays the reverse dependency tree for the packages that the <code>target-name</code> target includes. It shows each package followed by the list of libraries or packages that depend on it.</td>
</tr>
<tr>
<td>set</td>
-<td>Set variables (attributes) of the target named via <code>input1</code>. Currently the list of possible attributes (variables) are:<code>app</code>, <code>bsp</code>, <code>build_profile</code>, <code>features</code>, <code>cflags</code>, <code>lflags</code>. For a simulated target, e.g. for software testing purposes, <code>bsp</code> is set to <code>@apache-mynewt-core/hw/bsp/native</code>.</td>
-</tr>
-<tr>
-<td></td>
-<td>To display all the existing values for a target variable (attribute), you can issue a <code>newt vals <variable-name></code> command. For example, <code>newt vals app</code> displays the valid values available for the variable <code>app</code> for any target.</td>
-</tr>
-<tr>
-<td></td>
-<td>Currently, the only two values available for <code>build_profile</code> are <code>optimized</code> and <code>debug</code>.</td>
+<td>The set <target-name> <var-name=var-value> [var-name=var-value...] command sets variables (attributes) for the <target-name> target. The set command overwrites your current variable values. <br><br>The valid <code>var-name</code> values are: <code>app</code>, <code>bsp</code>, <code>loader</code>, <code>build_profile</code>, <code>cflags</code>, <code>lflags</code>, <code>aflags</code>, <code>syscfg</code>. <br><br>The <code>var-value</code> format depends on the <code>var-name</code> as follows: <ul><li><code>app</code>, <code>bsp</code>, <code>loader</code>: @<source-path>, where <code>source-path</code> is the directory containing the application or bsp source. These variables are stored in the target's target.yml file. For a simulated target, e.g. for software testing purposes, set <code>bsp</code> to <code>@apache-mynewt-core/hw/bsp/native</code>.</li> <li><code>build_profile</code>: <code>optimized</code> or <code>debug</code></li><li><code>cflags
</code>, <code>aflags</code>, <code>lflags</code>: A string of flags, with each flag separated by a space. These variables are saved in the target's <code>pkg.yml</code> file. </li><li><code>syscfg</code>: The <code>syscfg</code> variable allows you to assign values to configuration settings in your target's <code>syscfg.yml</code> file. <br>The format is <code>syscfg=setting-name1=setting-value1[:setting-name2=setting-value2...]</code>, where <code>setting-name1</code> is a configuration setting name and <code>setting-value1</code> is the value to assign to <code>settingname1</code>. If <code>settingvalue1</code> is not specified, the setting is set to value <code>1</code>. You use a <code>:</code> to delimit each setting when you set multiple settings. <br><strong>Warning</strong>: All existing setting values in the <code>syscfg.yml</code> file are deleted. Only new settings that are specified in the command are saved in the <code>syscfg.yml</code> file.</li></ul> You can spec
ify <code>var-name=</code> or <code>var-name=""</code> to unset a variable value.<br><br>To display all the existing values for a target variable (attribute), you can run the <code>newt vals <variable-name></code> command. For example, <code>newt vals app</code> displays the valid values available for the variable <code>app</code> for any target.</td>
</tr>
<tr>
<td>show</td>
-<td>Shows what variables (attributes) are set on the specified target <code>input1</code>. If no <code>input1</code> is specified then show the configuration for all the targets defined so far.</td>
+<td>The show [target-name] command shows the values of the variables (attributes) for the <code>target-name</code> target. When <code>target-name</code> is not specified, the command shows the variables for all the targets that are defined for your project.</td>
</tr>
</tbody>
</table>
@@ -590,34 +588,69 @@
</thead>
<tbody>
<tr>
-<td>config</td>
-<td>newt target config rb_blinky</td>
-<td>Shows all the system configuration settings for all the packages in the target named <code>rb_blinky</code>.</td>
+<td>config show</td>
+<td>newt target config show rb_blinky</td>
+<td>Shows the system configuration settings for all the packages that the <code>rb_blinky</code> target includes.</td>
+</tr>
+<tr>
+<td>config init</td>
+<td>newt target config init my_blinky</td>
+<td>Creates and populates the <code>my_blinky</code> target's <code>syscfg.yml</code> file with the system configuration setting values from all the packages that the <code>my_blinky</code> target includes.</td>
</tr>
<tr>
<td>copy</td>
-<td>newt target copy rb_blinky rb_bletiny</td>
-<td>Clones the target settings in <code>rb_blinky</code> to the destination target <code>rb_bletiny</code></td>
+<td>newt target copy <br>rb_blinky rb_bletiny</td>
+<td>Creates the <code>rb_bletiny</code> target by cloning the <code>rb_blinky</code> target.</td>
</tr>
<tr>
<td>create</td>
-<td>newt target create target1</td>
-<td>Creates an empty target by the name <code>target1</code></td>
+<td>newt target create <br>my_new_target</td>
+<td>Creates the <code>my_newt_target</code> target. It creates the <code>targets/my_new_target</code> directory and creates the skeleton <code>pkg.yml</code> and <code>target.yml</code> files in the directory.</td>
+</tr>
+<tr>
+<td>delete</td>
+<td>newt target delete rb_bletiny</td>
+<td>Deletes the <code>rb_bletiny</code> target. It deletes the <code>targets/rb_bletiny</code> directory.</td>
+</tr>
+<tr>
+<td>dep</td>
+<td>newt target dep myble</td>
+<td>Displays the dependency tree of all the package dependencies for the <code>myble</code> target. It lists each package followed by a list of packages it depends on.</td>
+</tr>
+<tr>
+<td>revdep</td>
+<td>newt target revdep myble</td>
+<td>Displays the reverse dependency tree of all the package dependencies for the <code>myble</code> target. It lists each package followed by a list of packages that depend on it.</td>
+</tr>
+<tr>
+<td>set</td>
+<td>newt target set myble <br>app=@apache-mynewt-core/apps/bletiny</td>
+<td>Use <code>bletiny</code> as the application to build for the <code>myble</code> target.</td>
+</tr>
+<tr>
+<td>set</td>
+<td>newt target set myble <br>cflags="-DNDEBUG -Werror"</td>
+<td>Set <code>pkg.cflags</code> variable with <code>-DNDEBUG -Werror</code> in the <code>myble</code> target's <code>pkg.yml</code> file..</td>
+</tr>
+<tr>
+<td>set</td>
+<td>newt target set myble syscfg=LOG_NEWTMGR=0:CONFIG_NEWTMGR</td>
+<td>Sets the <code>syscfg.vals</code> variable in the <code>myble</code> target's <code>syscfg.yml</code> file with the setting values: LOG_NEWTMGR: 0 and CONFIG_NEWTMGR: 1. CONFIG_NEWTMGR is set to 1 because a value is not specified.</td>
+</tr>
+<tr>
+<td>set</td>
+<td>newt target set myble cflags=</td>
+<td>Unsets the <code>pkg.cflags</code> variable in the <code>myble</code> target's <code>pkg.yml</code> file.</td>
</tr>
<tr>
<td>show</td>
<td>newt target show myble</td>
-<td>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.</td>
+<td>Shows all variable settings for the <code>myble</code> target, i.e. the values that app, bsp, build_profile, cflags, aflags, ldflags, syscfg variables are set to. Note that not all variables have to be set for a target.</td>
</tr>
<tr>
<td>show</td>
<td>newt target show</td>
-<td>Shows all variable settings for all the targets defined.</td>
-</tr>
-<tr>
-<td>set</td>
-<td>newt target set myble app=@apache-mynewt-core/apps/bletiny</td>
-<td>Assign <code>bletiny</code> to be the application to be included in the build for the target named <code>myble</code>.</td>
+<td>Shows all the variable settings for all the targets defined for the project.</td>
</tr>
</tbody>
</table>
@@ -630,9 +663,9 @@
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../newt_size/>
+ <a href=../newt_sync/>
<span class="fa fa-arrow-left"></span>
- Previous: newt size
+ Previous: newt sync
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/command_list/newt_test/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/command_list/newt_test/index.html b/latest/newt/command_list/newt_test/index.html
index 77d624a..2a7fb0e 100644
--- a/latest/newt/command_list/newt_test/index.html
+++ b/latest/newt/command_list/newt_test/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,41 +504,30 @@
</div>
<h2 id="newt-test"><font color="#F2853F" style="font-size:24pt">newt test </font></h2>
-<p>Executes unit tests for one or more packages </p>
+<p>Execute unit tests for one or more packages. </p>
<h4 id="usage">Usage:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt test [flags] input1 [input2] ...
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt test <package-name> [package-names...] | all [flags]
</pre></div>
<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for target
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -e, --exclude string Comma separated list of packages to exclude
</pre></div>
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -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.
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
</pre></div>
<h4 id="description">Description</h4>
-<table>
-<thead>
-<tr>
-<th>Sub-command</th>
-<th>Explanation</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>test</td>
-<td>Test a pkg named <code>input1</code>. You may specify multiple packages separated by space in the same command.</td>
-</tr>
-</tbody>
-</table>
+<p>Executes unit tests for one or more packages. You specify a list of packages, separated by space, to test multiple packages in the same command, or specify <code>all</code> to test all packages. When you use the <code>all</code> option, you may use the <code>-e</code> flag followed by a comma separated list of packages to exclude from the test.</p>
<h4 id="examples">Examples</h4>
<table>
<thead>
@@ -542,19 +539,24 @@
</thead>
<tbody>
<tr>
-<td>test</td>
-<td>newt test targets/myble2</td>
-<td>Tests the pkg named 'targets/myble2'</td>
+<td></td>
+<td>newt test <br>@apache-mynewt-core/kernel/os</td>
+<td>Tests the <code>kernel/os</code> package in the <code>apache-mynewt-core</code> repository.</td>
+</tr>
+<tr>
+<td></td>
+<td>newt test kernel/os encoding/json</td>
+<td>Tests the <code>kernel/os</code> and <code>encoding/json</code> packages in the current repository.</td>
</tr>
<tr>
<td></td>
-<td>newt test @apache-mynewt-core/libs/os</td>
-<td>Tests the libs/os pkg in the repo named apache-mynewt-core</td>
+<td>newt test all</td>
+<td>Tests all packages.</td>
</tr>
<tr>
<td></td>
-<td>newt test libs/os libs/json</td>
-<td>Tests the <code>libs/os</code> and <code>libs/json packages</code> in the current repo. Should indicate at the end of the output: <br> <code>Passed tests: [libs/os libs/json]</code> <br> <code>All tests passed</code></td>
+<td>newt test all -e net/oic,encoding/json</td>
+<td>Tests all packages except for the <code>net/oic</code> and the <code>encoding/json</code> packages.</td>
</tr>
</tbody>
</table>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/command_list/newt_upgrade/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/command_list/newt_upgrade/index.html b/latest/newt/command_list/newt_upgrade/index.html
index 864fcb2..3e3cf3e 100644
--- a/latest/newt/command_list/newt_upgrade/index.html
+++ b/latest/newt/command_list/newt_upgrade/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,40 +504,30 @@
</div>
<h2 id="newt-upgrade"><font color="#F2853F" style="font-size:24pt">newt upgrade </font></h2>
-<p>Upgrade project dependencies</p>
+<p>Upgrade project dependencies.</p>
<h4 id="usage">Usage:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt pkg [command][flag] input1 input2
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt upgrade [flags]
</pre></div>
<h4 id="flags">Flags:</h4>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -f, --force Force upgrade of the repositories to latest state in project.yml
+</pre></div>
-#### 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.
+<h4 id="global-flags">Global Flags:</h4>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
</pre></div>
<h4 id="description">Description</h4>
-<table>
-<thead>
-<tr>
-<th>Sub-command</th>
-<th>Explanation</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>upgrade</td>
-<td>If you have changed the project.yml description for the project, you need to run this command to update all the package dependencies.</td>
-</tr>
-</tbody>
-</table>
+<p>Upagrades your project and package dependencies. If you have changed the project.yml description for the project, you need to run this command to update all the package dependencies. </p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/command_list/newt_vals/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/command_list/newt_vals/index.html b/latest/newt/command_list/newt_vals/index.html
index a5888bd..33db611 100644
--- a/latest/newt/command_list/newt_vals/index.html
+++ b/latest/newt/command_list/newt_vals/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,37 +504,35 @@
</div>
<h2 id="newt-vals"><font color="#F2853F" style="font-size:24pt">newt vals </font></h2>
-<p>Displays valid values for the specified element type(s). Appropriate values must be chosen and assigned to one or more elements when defining a package or target. Element types currently available are the following:</p>
+<p>Display valid values for the specified element type(s).</p>
+<h4 id="usage">Usage:</h4>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt vals <element-type> [element-types...] [flags]
+</pre></div>
+
+
+<h4 id="global-flags">Global Flags:</h4>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
+</pre></div>
+
+
+<h4 id="description">Description</h4>
+<p>Displays valid values for the specified element type(s). You must set valid values for one or more elements when you define a package or a target. Valid element types are:</p>
<ul>
<li>api</li>
<li>app</li>
<li>bsp</li>
<li>build_profile</li>
<li>compiler</li>
-<li>feature</li>
<li>lib</li>
<li>sdk</li>
<li>target</li>
</ul>
-<h4 id="usage">Usage:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt vals <element-type> [element-types...] [flags]
-</pre></div>
-
-
-<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for target
-</pre></div>
-
-
-<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -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.
-</pre></div>
-
-
<h4 id="examples">Examples</h4>
<table>
<thead>
@@ -538,7 +544,7 @@
</thead>
<tbody>
<tr>
-<td>vals</td>
+<td></td>
<td>newt vals api</td>
<td>Shows the possible values for APIs a package may specify as required. For example, the <code>pkg.yml</code> for <code>adc</code> specifies that it requires the api named <code>ADC_HW_IMPL</code>, one of the values listed by the command.</td>
</tr>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/command_list/newt_version/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/command_list/newt_version/index.html b/latest/newt/command_list/newt_version/index.html
index acef10d..84d0acd 100644
--- a/latest/newt/command_list/newt_version/index.html
+++ b/latest/newt/command_list/newt_version/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,23 +504,20 @@
</div>
<h2 id="newt-version"><font color="#F2853F" style="font-size:24pt">newt version </font></h2>
-<p>Allows you to query the version of newt installed in your application space.</p>
+<p>Display the version of the newt tool you have installed</p>
<h4 id="usage">Usage:</h4>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt version [flags]
</pre></div>
-<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for version
-</pre></div>
-
-
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -l, --loglevel string Log level, defaults to WARN. (default "WARN")
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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.
+ -q, --quiet Be quiet; only display error output
+ -s, --silent Be silent; don't output anything
+ -v, --verbose Enable verbose output when executing commands
</pre></div>
@@ -527,9 +532,9 @@
</thead>
<tbody>
<tr>
-<td>version</td>
+<td></td>
<td>newt version</td>
-<td>Displays the version of newt tool installed</td>
+<td>Displays the version of the newt tool you have installed</td>
</tr>
</tbody>
</table>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/newt_intro/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/newt_intro/index.html b/latest/newt/newt_intro/index.html
index 95d1d31..e70aedb 100644
--- a/latest/newt/newt_intro/index.html
+++ b/latest/newt/newt_intro/index.html
@@ -395,32 +395,32 @@ systems with a make system built for embedded systems and create Newt.</p>
<p><br></p>
<p>When Newt sees a directory tree that contains a "project.yml" file, it is smart enough to recognize it as the base directory of a project, and
automatically builds a package tree. It also recognizes two important package directories in the package tree - "apps" and "targets". More on these directories in <a href="../newt_operation/">Newt Theory of Ops</a>.</p>
-<p>When Newt is told to build a project, it recursively resolves all package dependencies and generates artifacts that are placed in the bin/ directory at the top-level of the project. The artifact directory is prefixed by the target name being built - <code>my_blinky_sim</code> for example:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ tree bin
-bin
-\u2514\u2500\u2500 my_blinky_sim
- \u251c\u2500\u2500 apps
- \u2502�� \u2514\u2500\u2500 blinky
- \u2502�� \u251c\u2500\u2500 blinky.a
- \u2502�� \u251c\u2500\u2500 blinky.a.cmd
- \u2502�� \u251c\u2500\u2500 blinky.elf
- \u2502�� \u251c\u2500\u2500 blinky.elf.cmd
- \u2502�� \u251c\u2500\u2500 blinky.elf.dSYM
- \u2502�� \u2502�� \u2514\u2500\u2500 Contents
- \u2502�� \u2502�� \u251c\u2500\u2500 Info.plist
- \u2502�� \u2502�� \u2514\u2500\u2500 Resources
- \u2502�� \u2502�� \u2514\u2500\u2500 DWARF
- \u2502�� \u2502�� \u2514\u2500\u2500 blinky.elf
- \u2502�� \u251c\u2500\u2500 blinky.elf.lst
- \u2502�� \u251c\u2500\u2500 main.d
- \u2502�� \u251c\u2500\u2500 main.o
- \u2502�� \u2514\u2500\u2500 main.o.cmd
- \u251c\u2500\u2500 hw
- \u2502�� \u251c\u2500\u2500 bsp
- \u2502�� \u2502�� \u2514\u2500\u2500 native
- \u2502�� \u2502�� \u251c\u2500\u2500 hal_bsp.d
- \u2502�� \u2502�� \u251c\u2500\u2500 hal_bsp.o
- \u2502�� \u2502�� \u251c\u2500\u2500 hal_bsp.o.cmd
+<p>When Newt builds a target, it recursively resolves all package dependencies, and generates artifacts that are placed in the bin/targets/<target-name>/app/apps/<app-name> directory, where the bin directory is under the project base directory, <code>target-name</code> is the name of the target, and <code>app-name</code> is the name of the application. For our example <code>my_blinky_sim</code> is the name of the target and <code>blinky</code> is the name of the application. The <code>blinky.elf</code> executable is stored in the bin/targets/my_blinky_sim/app/apps/blinky directory as shown in the source tree:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">tree -L 6 bin/
+bin/
+\u2514\u2500\u2500 targets
+ \u251c\u2500\u2500 my_blinky_sim
+ \u2502�� \u251c\u2500\u2500 app
+ \u2502�� \u2502�� \u251c\u2500\u2500 apps
+ \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 blinky
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 apps
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 apps_blinky.a
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 apps_blinky.a.cmd
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 blinky.elf
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 blinky.elf.cmd
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 blinky.elf.dSYM
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 blinky.elf.lst
+ \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 manifest.json
+ \u2502�� \u2502�� \u251c\u2500\u2500 hw
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 bsp
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 native
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 drivers
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 uart
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 hal
+ \u2502�� \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 hw_hal.a
+ \u2502�� \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 hw_hal.a.cmd
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 repos
+
<snip>
</pre></div>
@@ -434,6 +434,7 @@ bin
<li><strong>size</strong>: Get size of target components</li>
<li><strong>create-image</strong>: Add image header to the binary image</li>
<li><strong>run</strong>: Build, create image, load, and finally open a debug session with the target</li>
+<li><strong>target</strong>: Create, delete, configure, and query a target</li>
</ul>
<p>For more details on how Newt works, go to <a href="../newt_operation/">Newt - Theory of Operations</a>.</p>
<p><br></p>
@@ -496,13 +497,13 @@ Repos successfully installed
<p><br></p>
-<p>In order to reference the installed repositories in packages, the "@" notation should be specified in the repository specifier. As an example, the apps/blinky application has the following dependencies in its pkg.yml file. This tells the build system to look in the base directory of repos/apache-mynewt-core for the <code>libs/os</code>, <code>hw/hal</code>, and <code>libs/console/full</code> packages.</p>
+<p>In order to reference the installed repositories in packages, the "@" notation should be specified in the repository specifier. As an example, the apps/blinky application has the following dependencies in its pkg.yml file. This tells the build system to look in the base directory of repos/apache-mynewt-core for the <code>kernel/os</code>, <code>hw/hal</code>, and <code>sys/console/full</code> packages.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ more apps/blinky/pkg.yml
<snip>
pkg.deps:
- - "@apache-mynewt-core/libs/os"
+ - "@apache-mynewt-core/kernel/os"
- "@apache-mynewt-core/hw/hal"
- - "@apache-mynewt-core/libs/console/full"
+ - "@apache-mynewt-core/sys/console/full"
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/newt_operation/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/newt_operation/index.html b/latest/newt/newt_operation/index.html
index c2c6aeb..2ac6a82 100644
--- a/latest/newt/newt_operation/index.html
+++ b/latest/newt/newt_operation/index.html
@@ -378,13 +378,14 @@
<h4 id="apps-package-directory">"apps" Package Directory</h4>
<p><code>apps</code> is where applications are stored, and applications are where the main() function is contained. The base project directory comes with one simple app called <code>blinky</code> in the <code>apps</code> directory. The core repository <code>@apache-mynewt-core</code> comes with many additional sample apps in its <code>apps</code> directory. At the time of this writing, there are several example BLE apps, the boot app, slinky app for using newt manager protocol, and more in that directory.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">@~/dev/myproj$ ls repos/apache-mynewt-core/apps/
-blecent bleprph_oic bleuart ffs2native slinky_oic test
-blehci bletest boot ocf_sample spitest timtest
-bleprph bletiny fat2native slinky splitty
+blecent blesplit boot sensors_test splitty
+blehci bletest fat2native slinky test
+bleprph bletiny ffs2native slinky_oic testbench
+bleprph_oic bleuart ocf_sample spitest timtest
</pre></div>
-<p>Along with the <code>targets</code> directory, <code>apps</code> represents the top-level of the build tree for the particular project, and define the dependencies and features for the rest of the system. Mynewt users and developers can add their own apps to the project's <code>apps</code> directory. </p>
+<p>Along with the <code>targets</code> directory, <code>apps</code> represents the top-level of the build tree for the particular project, and define the dependencies for the rest of the system. Mynewt users and developers can add their own apps to the project's <code>apps</code> directory. </p>
<p>The app definition is contained in a <code>pkg.yml</code> file. For example, blinky's <code>pkg.yml</code> file is:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ more apps/blinky/pkg.yml
<snip>
@@ -403,8 +404,7 @@ pkg.deps:
<p><br></p>
-<p>This file says that the name of the package is apps/blinky, and it
-depends on kernel/os, hw/hal and sys/console/full packages.</p>
+<p>This file says that the name of the package is apps/blinky, and it depends on the <code>kernel/os,</code>hw/hal<code>and</code>sys/console/full` packages.</p>
<p><strong>NOTE:</strong> @apache-mynewt-core is a repository descriptor, and this will be
covered in the "repository" section. </p>
<p><br></p>
@@ -430,17 +430,19 @@ pkg.yml target.yml
<p>There are helper functions to aid the developer specify parameters for a target. </p>
<ul>
<li><strong>vals</strong>: Displays all valid values for the specified parameter type (e.g. bsp for a target)</li>
-<li><strong>target show</strong>: Displays the build artifacts for specified or all targets</li>
+<li><strong>target show</strong>: Displays the variable values for either a specific target or all targets defined for the project</li>
+<li><strong>target set</strong>: Sets values for target variables</li>
</ul>
-<p>In general, the three basic parameters of a target (<code>app</code>, <code>bsp</code>, and <code>build_profile</code>) are stored in the <code>target.yml</code> file in that target's build directory under <code>targets</code>. You will also see a <code>pkg.yml</code> file in the same directory. Since targets are packages, a <code>pkg.yml</code> is expected. It contains typical package descriptors, dependencies, and additional parameters such as the following:</p>
+<p>In general, the three basic parameters of a target (<code>app</code>, <code>bsp</code>, and <code>build_profile</code>) are stored in the target's <code>target.yml</code> file in the targets/<target-name> directory, where <code>target-name</code> is the name of the target. You will also see a <code>pkg.yml</code> file in the same directory. Since targets are packages, a <code>pkg.yml</code> is expected. It contains typical package descriptors, dependencies, and additional parameters such as the following:</p>
<ul>
<li>Cflags: Any additional compiler flags you might want to specify to the build</li>
<li>Aflags: Any additional assembler flags you might want to specify to the build</li>
<li>Lflags: Any additional linker flags you might want to specify to the build</li>
</ul>
+<p>You can also override the values of the system configuration settings that are defined by the packages that your target includes. You override the values in your target's <code>syscfg.yml</code> file (stored in the targets/<target-name> directory). You can use the <code>newt target config show</code> command to see the configuration settings and values for your target, and use the <code>newt target set</code> command to set the <code>syscfg</code> variable and override the configuration setting values. You can also use an editor to create your target's <code>syscfg.yml</code> file and add the setting values to the file. See <a href="../../os/modules/sysinitconfig/sysinitconfig/">System Configuration And Initialization</a> for more information on system configuration settings.</p>
<p><br></p>
<h3 id="resolving-dependencies">Resolving dependencies</h3>
-<p>When newt is told to build a project, it will:</p>
+<p>When newt builds a project, it will:</p>
<ul>
<li>find the top-level project.yml file</li>
<li>recurse the packages in the package tree, and build a list of all
@@ -467,43 +469,48 @@ along with that application.</li>
<p>Newt builds the dependency tree specified by all the packages. While building this tree, it does a few other things:</p>
<ul>
<li>Sets up the include paths for each package. Any package that depends on another package, automatically gets the include directories from the package it includes. Include directories in the
-newt structure must always be prefixed by the package name. For example, libs/os has the following include tree and its include directory files contains the package name "os" before any header files. This is so in order to avoid any header file conflicts.</li>
+newt structure must always be prefixed by the package name. For example, kernel/os has the following include tree and its include directory files contains the package name "os" before any header files. This is so in order to avoid any header file conflicts.</li>
</ul>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ tree
-.
-\u251c\u2500\u2500 README.md
-\u251c\u2500\u2500 include
-\u2502�� \u2514\u2500\u2500 os
-\u2502�� \u251c\u2500\u2500 arch
-\u2502�� \u2502�� \u251c\u2500\u2500 cortex_m0
-\u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 os
-\u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 os_arch.h
-\u2502�� \u2502�� \u251c\u2500\u2500 cortex_m4
-\u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 os
-\u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 os_arch.h
-\u2502�� \u2502�� \u2514\u2500\u2500 sim
-\u2502�� \u2502�� \u2514\u2500\u2500 os
-\u2502�� \u2502�� \u2514\u2500\u2500 os_arch.h
-\u2502�� \u251c\u2500\u2500 endian.h
-\u2502�� \u251c\u2500\u2500 os.h
-\u2502�� \u251c\u2500\u2500 os_callout.h
-\u2502�� \u251c\u2500\u2500 os_cfg.h
-\u2502�� \u251c\u2500\u2500 os_eventq.h
-\u2502�� \u251c\u2500\u2500 os_heap.h
-\u2502�� \u251c\u2500\u2500 os_malloc.h
-\u2502�� \u251c\u2500\u2500 os_mbuf.h
-\u2502�� \u251c\u2500\u2500 os_mempool.h
-\u2502�� \u251c\u2500\u2500 os_mutex.h
-\u2502�� \u251c\u2500\u2500 os_sanity.h
-\u2502�� \u251c\u2500\u2500 os_sched.h
-\u2502�� \u251c\u2500\u2500 os_sem.h
-\u2502�� \u251c\u2500\u2500 os_task.h
-\u2502�� \u251c\u2500\u2500 os_test.h
-\u2502�� \u251c\u2500\u2500 os_time.h
-\u2502�� \u2514\u2500\u2500 queue.h
-\u251c\u2500\u2500 pkg.yml
-\u2514\u2500\u2500 src
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$tree kernel/os/include
+kernel/os/include
+\u2514\u2500\u2500 os
\u251c\u2500\u2500 arch
+ \u2502�� \u251c\u2500\u2500 cortex_m0
+ \u2502�� \u2502�� \u2514\u2500\u2500 os
+ \u2502�� \u2502�� \u2514\u2500\u2500 os_arch.h
+ \u2502�� \u251c\u2500\u2500 cortex_m4
+ \u2502�� \u2502�� \u2514\u2500\u2500 os
+ \u2502�� \u2502�� \u2514\u2500\u2500 os_arch.h
+ \u2502�� \u251c\u2500\u2500 mips
+ \u2502�� \u2502�� \u2514\u2500\u2500 os
+ \u2502�� \u2502�� \u2514\u2500\u2500 os_arch.h
+ \u2502�� \u251c\u2500\u2500 sim
+ \u2502�� \u2502�� \u2514\u2500\u2500 os
+ \u2502�� \u2502�� \u2514\u2500\u2500 os_arch.h
+ \u2502�� \u2514\u2500\u2500 sim-mips
+ \u2502�� \u2514\u2500\u2500 os
+ \u2502�� \u2514\u2500\u2500 os_arch.h
+ \u251c\u2500\u2500 endian.h
+ \u251c\u2500\u2500 os.h
+ \u251c\u2500\u2500 os_callout.h
+ \u251c\u2500\u2500 os_cfg.h
+ \u251c\u2500\u2500 os_cputime.h
+ \u251c\u2500\u2500 os_dev.h
+ \u251c\u2500\u2500 os_eventq.h
+ \u251c\u2500\u2500 os_fault.h
+ \u251c\u2500\u2500 os_heap.h
+ \u251c\u2500\u2500 os_malloc.h
+ \u251c\u2500\u2500 os_mbuf.h
+ \u251c\u2500\u2500 os_mempool.h
+ \u251c\u2500\u2500 os_mutex.h
+ \u251c\u2500\u2500 os_sanity.h
+ \u251c\u2500\u2500 os_sched.h
+ \u251c\u2500\u2500 os_sem.h
+ \u251c\u2500\u2500 os_task.h
+ \u251c\u2500\u2500 os_test.h
+ \u251c\u2500\u2500 os_time.h
+ \u2514\u2500\u2500 queue.h
+
<snip>
</pre></div>
@@ -517,43 +524,50 @@ those APIs (i.e. pkg.req_api: hw-hal-impl).</p>
</li>
<li>
<p>Reads and validates the configuration setting definitions and values from the package <code>syscfg.yml</code> files.
-It generates a <code>syscfg.h</code> header file that packages include in the source files inorder to access the settings.<br />
+It generates a <code>syscfg.h</code> header file that packages include in the source files in order to access the settings.<br />
It also generates a system initialization function to initialize the packages.
See <a href="../../os/modules/sysinitconfig/sysinitconfig/">System Configuration And Initialization</a> for more information.</p>
</li>
</ul>
-<p>In order to properly resolve all dependencies in the build system, newt recursively processes the package dependencies until there are no new dependencies or features (because features can add dependencies.) And it builds a big list of all the packages that need to be build.</p>
+<p>In order to properly resolve all dependencies in the build system, newt recursively processes the package dependencies until there are no new dependencies. And it builds a big list of all the packages that need to be build.</p>
<p>Newt then goes through this package list, and builds every package into
an archive file.</p>
<p><strong>NOTE:</strong> The newt tool generates compiler dependencies for all of these packages, and only rebuilds the packages whose dependencies have changed. Changes in package & project dependencies are also taken into account. It is smart, after all!</p>
<h3 id="producing-artifacts">Producing artifacts</h3>
<p>Once newt has built all the archive files, it then links the archive files together. The linkerscript to use is specified by the board support package (BSP.)</p>
-<p>NOTE: One common use of the "features" option above is to overwrite
-which linkerscript is used, based upon whether or not the BSP is being
-build for a raw image, bootable image or bootloader itself.</p>
-<p>The newt tool places all of it's artifacts into the bin/ directory at
-the top-level of the project, prefixed by the target name being built,
-for example:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ tree -L 4 bin/
-bin/
-\u2514\u2500\u2500 my_blinky_sim
- \u251c\u2500\u2500 apps
- \u2502 \u2514\u2500\u2500 blinky
- \u2502 \u251c\u2500\u2500 blinky.a
- \u2502 \u251c\u2500\u2500 blinky.a.cmd
- \u2502 \u251c\u2500\u2500 blinky.elf
- \u2502 \u251c\u2500\u2500 blinky.elf.cmd
- \u2502 \u251c\u2500\u2500 blinky.elf.dSYM
- \u2502 \u251c\u2500\u2500 blinky.elf.lst
- \u2502 \u251c\u2500\u2500 main.d
- \u2502 \u251c\u2500\u2500 main.o
- \u2502 \u2514\u2500\u2500 main.o.cmd
- \u251c\u2500\u2500 hw
- \u2502 \u251c\u2500\u2500 bsp
- \u2502 \u2502 \u2514\u2500\u2500 native
- \u2502 \u251c\u2500\u2500 hal
- \u2502 \u2502 \u251c\u2500\u2500 flash_map.d
- \u2502 \u2502 \u251c\u2500\u2500 flash_map.o
+<p>The newt tool creates a bin directory under the base project directory, and places a target's build artifacts into the bin/targets/<target-name>/app/apps/<app-name> directory, where <code>target-name</code> is the name of the target and <code>app-name</code> is the name of the application. As an example, the <code>blinky.elf</code> executable for the <code>blinky</code> application defined by the <code>my_blinky_sim</code> target is stored in the bin/targets/my_blinky_sim/app/apps/blinky directory as shown in the following source tree:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$tree -L 9 bin/ bin/
+\u2514\u2500\u2500 targets
+ \u251c\u2500\u2500 my_blinky_sim
+ \u2502�� \u251c\u2500\u2500 app
+ \u2502�� \u2502�� \u251c\u2500\u2500 apps
+ \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 blinky
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 apps
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 blinky
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 src
+ \u2502�� \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 main.d
+ \u2502�� \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 main.o
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 main.o.cmd
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 apps_blinky.a
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 apps_blinky.a.cmd
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 blinky.elf
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 blinky.elf.cmd
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 blinky.elf.dSYM
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 Contents
+ \u2502�� \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 Info.plist
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 Resources
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 DWARF
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 blinky.elf.lst
+ \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 manifest.json
+ \u2502�� \u2502�� \u251c\u2500\u2500 hw
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 bsp
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 native
+ \u2502�� \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 hw_bsp_native.a
+ \u2502�� \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 hw_bsp_native.a.cmd
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 repos
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 apache-mynewt-core
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 hw
+
<snip>
</pre></div>
@@ -564,8 +578,8 @@ bin/
<li>Archive File</li>
<li>*.cmd: The command use to generate the object or archive file</li>
<li>*.lst: The list file where symbols are located</li>
-<li>*.o The object files that get put into the archive file</li>
</ul>
+<p>Note: The *.o object files that get put into the archive file are stored in the bin/targets/my_blinky_sim/app/apps/blinky/apps/blinky/src directory.</p>
<h3 id="downloaddebug-support">Download/Debug Support</h3>
<p>Once a target has been build, there are a number of helper functions
that work on the target. These are:</p>
@@ -575,6 +589,7 @@ that work on the target. These are:</p>
<li><strong>size</strong> Size of target components</li>
<li><strong>create-image</strong> Add image header to target binary</li>
<li><strong>run</strong> The equivalent of build, create-image, load, and debug on specified target</li>
+<li><strong>target</strong> Create, delete, configure, and query a target</li>
</ul>
<p><code>load</code> and <code>debug</code> handles driving GDB and the system debugger. These
commands call out to scripts that are defined by the BSP.</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/newt_ops/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/newt_ops/index.html b/latest/newt/newt_ops/index.html
index 999a3c5..89d808d 100644
--- a/latest/newt/newt_ops/index.html
+++ b/latest/newt/newt_ops/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../command_list/newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../command_list/newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../command_list/newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../command_list/newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../command_list/newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../command_list/newt_target/">newt target</a>
</li>
@@ -494,9 +502,9 @@
</div>
<h2 id="command-structure">Command Structure</h2>
-<p>Just like verbs are actions in a sentence and adverdbs modifiy verbs, so in <em>newt</em> tool, commands are actions and flags modify actions. A command can have subcommands, too. Arguments to commands and subcommands, with appropriate flags, will dictate the execution and result of a command. </p>
-<p>For instance, in the example below, the <em>newt</em> command has the subcommand <code>target set</code> in which the argument 'my_target1' is the target whose attribute, <em>arch</em>, is set to 'cortex_md.' </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt target set my_target1 arch=cortex_m4
+<p>Just like verbs are actions in a sentence and adverbs modifiy verbs, so in the <em>newt</em> tool, commands are actions and flags modify actions. A command can have subcommands. Arguments to commands and subcommands, with appropriate flags, dictate the execution and result of a command. </p>
+<p>For instance, in the example below, the <em>newt</em> command has the subcommand <code>target set</code> in which the argument 'my_target1' is the target whose attribute, <em>app</em>, is set to '@apache-mynewt-core/hw/bsp/nrf52dk'</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt target set my_target1 app=@apache-mynewt-core/hw/bsp/nrf52dk
</pre></div>
@@ -508,14 +516,14 @@
<p>In addition to the <a href="../newt_intro/">Newt Tool Manual</a> in docs, command-line help is available for each command (and subcommand), through the <code>-h</code> or <code>--help</code> options. </p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt target --help
- Command for manipulating targets
+ Commands to create, delete, configure, and query targets
Usage:
newt target [flags]
newt target [command]
Available Commands:
- config View target system configuration
+ config View or populate a target's system configuration
copy Copy target
create Create a target
delete Delete target
@@ -525,6 +533,8 @@
show View target configuration variables
Global Flags:
+ -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
-l, --loglevel string Log level (default "WARN")
-o, --outfile string Filename to tee output to
-q, --quiet Be quiet; only display error output
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/os/modules/sysinitconfig/sysconfig_error/index.html
----------------------------------------------------------------------
diff --git a/latest/os/modules/sysinitconfig/sysconfig_error/index.html b/latest/os/modules/sysinitconfig/sysconfig_error/index.html
index 2050673..2a1892f 100644
--- a/latest/os/modules/sysinitconfig/sysconfig_error/index.html
+++ b/latest/os/modules/sysinitconfig/sysconfig_error/index.html
@@ -821,7 +821,90 @@ outputs when multiple packages define the <code>LOG_NEWTMGR</code> setting:</p>
</pre></div>
-<p><strong>Note:</strong> Newt does not output the <code>Setting history</code> with duplicate setting error messages. </p>
+<p><strong>Note:</strong> Newt does not output the <code>Setting history</code> with duplicate setting error messages.
+<br></p>
+<h3 id="override-of-undefined-system-configuration-setting">Override of Undefined System Configuration Setting</h3>
+<p>The <code>newt build</code> command ignores overrides of undefined system configuration settings. The command does not print a warning when you run it with the default log level. If you override a setting and the value is not assigned to the setting, you may have misspelled the setting name or a package no longer defines the setting. You have two options to troubleshoot this problem:</p>
+<ul>
+<li>Run the <code>newt target config show</code> command to see the configuration setting definitions and overrides.</li>
+<li>Run the <code>newt build -ldebug</code> command to build your target with DEBUG log level. </li>
+</ul>
+<p>Note: The <code>newt build -ldebug</code> command generates lots of output and we recommend that you use the <code>newt target config show</code> command option.
+<br></p>
+<h4 id="example-ignoring-override-of-undefined-setting-message">Example: Ignoring Override of Undefined Setting Message</h4>
+<p>The following example shows that the <code>apps/slinky</code> application overrides the <code>LOG_NEWTMGR</code> setting but omits the <strong>T</strong> as an example of an error and overrides the misspelled <strong>LOG_NEWMGR</strong> setting. Here is an excerpt from its <code>syscfg.yml</code> file: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">#package: apps/slinky
+syscfg.vals:
+ # Enable the shell task.
+ SHELL_TASK: 1
+ ...
+
+ # Enable newtmgr commands.
+ STATS_NEWTMGR: 1
+ LOG_NEWMGR: 1
+</pre></div>
+
+
+<p><br>
+The <code>newt target config show slinky_sim</code> command outputs the following WARNING message:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">2017/02/18 17:19:12.119 [WARNING] Ignoring override of undefined settings:
+2017/02/18 17:19:12.119 [WARNING] LOG_NEWMGR
+2017/02/18 17:19:12.119 [WARNING] NFFS_FLASH_AREA
+2017/02/18 17:19:12.119 [WARNING] Setting history (newest -> oldest):
+2017/02/18 17:19:12.119 [WARNING] LOG_NEWMGR: [apps/slinky:1]
+2017/02/18 17:19:12.119 [WARNING] NFFS_FLASH_AREA: [hw/bsp/native:FLASH_AREA_NFFS]
+</pre></div>
+
+
+<p><br></p>
+<p>The <code>newt build -ldebug slinky_sim</code> command outputs the following DEBUG message: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">2017/02/18 17:06:21.451 [DEBUG] Ignoring override of undefined settings:
+2017/02/18 17:06:21.451 [DEBUG] LOG_NEWMGR
+2017/02/18 17:06:21.451 [DEBUG] NFFS_FLASH_AREA
+2017/02/18 17:06:21.451 [DEBUG] Setting history (newest -> oldest):
+2017/02/18 17:06:21.451 [DEBUG] LOG_NEWMGR: [apps/slinky:1]
+2017/02/18 17:06:21.451 [DEBUG] NFFS_FLASH_AREA: [hw/bsp/native:FLASH_AREA_NFFS]
+</pre></div>
+
+
+<p><br></p>
+<h4 id="bsp-package-overrides-undefined-configuration-settings">BSP Package Overrides Undefined Configuration Settings</h4>
+<p>You might see a warning that indicates your application's BSP package is overriding some undefined settings. As you can see from the previous example, the WARNING message shows that the <code>hw/bsp/native</code> package is overriding the undefined <code>NFFS_FLASH_AREA</code> setting. This is not an error because of the way a BSP package defines and assigns its flash areas to packages that use flash memory.</p>
+<p>A BSP package defines, in its <code>bsp.yml</code> file, a flash area map of the flash areas on the board. A package that uses flash memory must define a flash area configuration setting name. The BSP package overrides the package's flash area setting with one of the flash areas from its flash area map. A BSP package overrides the flash area settings for all packages that use flash memory because it does not know the packages that an application uses. When an application does not include one of these packages, the flash area setting for the package is undefined. You will see a message that indicates the BSP package overrides this undefined setting.</p>
+<p>Here are excerpts from the <code>hw/bsp/native</code> package's <code>bsp.yml</code> and <code>syscfg.yml</code> files for the <code>slinky_sim</code> target. The BSP package defines the flash area map in its <code>bsp.yml</code> file and overrides the flash area settings for all packages in its <code>syscfg.yml</code> file. The <code>slinky_sim</code> target does not use the <code>fs/nffs</code> package which defines the <code>NFFS_FLASH_AREA</code> setting. Newt warns that the <code>hw/bsp/native</code> packages overrides the undefined <code>NFFS_FLASH_AREA</code> setting.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"># hw/bsp/native bsp.yml
+bsp.flash_map:
+ areas:
+ # System areas.
+ FLASH_AREA_BOOTLOADER:
+ device: 0
+ offset: 0x00000000
+ size: 16kB
+
+ ...
+
+ FLASH_AREA_IMAGE_SCRATCH:
+ device: 0
+ offset: 0x000e0000
+ size: 128kB
+
+ # User areas.
+ FLASH_AREA_REBOOT_LOG:
+ user_id: 0
+ device: 0
+ offset: 0x00004000
+ size: 16kB
+ FLASH_AREA_NFFS:
+ user_id: 1
+ device: 0
+ offset: 0x00008000
+
+# hw/bsp/native syscfg.yml
+syscfg.vals:
+ NFFS_FLASH_AREA: FLASH_AREA_NFFS
+ CONFIG_FCB_FLASH_AREA: FLASH_AREA_NFFS
+ REBOOT_LOG_FLASH_AREA: FLASH_AREA_REBOOT_LOG
+</pre></div>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/sitemap.xml
----------------------------------------------------------------------
diff --git a/latest/sitemap.xml b/latest/sitemap.xml
index 3a2a667..0ccc1fb 100644
--- a/latest/sitemap.xml
+++ b/latest/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,7 +13,7 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -22,7 +22,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -30,7 +30,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -38,7 +38,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -46,7 +46,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -54,7 +54,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -62,7 +62,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -71,7 +71,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -83,7 +83,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -123,13 +123,13 @@
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/sitemap.xml
----------------------------------------------------------------------
diff --git a/sitemap.xml b/sitemap.xml
index d7828f1..e7466d3 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,13 +13,13 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/pages/securitybullets/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -28,7 +28,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -36,7 +36,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -44,7 +44,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -52,7 +52,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -60,7 +60,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -68,7 +68,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -77,7 +77,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -89,7 +89,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -129,13 +129,13 @@
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/v0_9_0/index.html
----------------------------------------------------------------------
diff --git a/v0_9_0/index.html b/v0_9_0/index.html
index 9e7f72f..3aa2c75 100644
--- a/v0_9_0/index.html
+++ b/v0_9_0/index.html
@@ -288,6 +288,9 @@
<li>
<a href="http://www.nxp.com/products/software-and-tools/hardware-development-tools/freedom-development-boards/freedom-development-platform-for-kinetis-k64-k63-and-k24-mcus:FRDM-K64F"> FRDM-K64F </a> from NXP (Cortex-M4)
</li>
+ <li>
+ <a href="https://creatordev.io/ci40-iot-dev-kit.html"> Creator Ci40 IoT Kit </a> from Imagination Technologies (MIPS CPU)
+ </li>
</ul>
</div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/v0_9_0/landing.html
----------------------------------------------------------------------
diff --git a/v0_9_0/landing.html b/v0_9_0/landing.html
index e160dec..ccc7ec2 100644
--- a/v0_9_0/landing.html
+++ b/v0_9_0/landing.html
@@ -147,6 +147,9 @@
<li>
<a href="http://www.nxp.com/products/software-and-tools/hardware-development-tools/freedom-development-boards/freedom-development-platform-for-kinetis-k64-k63-and-k24-mcus:FRDM-K64F"> FRDM-K64F </a> from NXP (Cortex-M4)
</li>
+ <li>
+ <a href="https://creatordev.io/ci40-iot-dev-kit.html"> Creator Ci40 IoT Kit </a> from Imagination Technologies (MIPS CPU)
+ </li>
</ul>
</div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/v0_9_0/sitemap.xml
----------------------------------------------------------------------
diff --git a/v0_9_0/sitemap.xml b/v0_9_0/sitemap.xml
index d7828f1..e7466d3 100644
--- a/v0_9_0/sitemap.xml
+++ b/v0_9_0/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,13 +13,13 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/pages/securitybullets/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -28,7 +28,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -36,7 +36,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -44,7 +44,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -52,7 +52,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -60,7 +60,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -68,7 +68,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -77,7 +77,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -89,7 +89,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -129,13 +129,13 @@
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
[3/7] incubator-mynewt-site git commit: Update newt command
documentation, sysconfig overwrites, events, bsp list
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/mkdocs/search_index.json
----------------------------------------------------------------------
diff --git a/latest/mkdocs/search_index.json b/latest/mkdocs/search_index.json
index 1f1695e..84d2e36 100644
--- a/latest/mkdocs/search_index.json
+++ b/latest/mkdocs/search_index.json
@@ -7937,7 +7937,7 @@
},
{
"location": "/os/modules/sysinitconfig/sysconfig_error/",
- "text": "Validation and Error Messages\n\n\nWith multiple packages defining and overriding system configuration settings, it \nis easy to introduce conflicts and violations that are difficult to find. The \n\nnewt build \ntarget-name\n command validates the setting definitions and value \noverrides for all the packages in the target to ensure a valid and consistent build.\nIt aborts the build when it detects violations or ambiguities between packages.\n\nThe following sections describe the error conditions that newt detects and \nthe error messages that it outputs. For most errors, newt also outputs \nthe \nSetting history\n with the order of package overrides to help \nyou resolve the errors.\n\n\nNote:\n The \nnewt target config \ntarget-name\n command also detects \nerrors and outputs error messages at the top of the command output. \nThe command outputs the package setting definitions and values after it \noutputs the error messages. It is easy to miss the error mes
sages at the top. \n\n\nValue Override Violations\n\n\nThe newt tool uses package priorities to resolve override conflicts. It uses \nthe value override from the highest priority package when multiple \npackages override the same setting. Newt checks for the following \noverride violations:\n\n\n\n\nAmbiguity Violation - Two packages of the same priority override a setting with \ndifferent values. And no higher priority package overrides the setting.\n\n\nPriority Violation - A package overrides a setting defined by a package with higher or \nequal priority. \n\n\n\n\nExample: Ambiguity Violation Error Message\n\n\nThe following example shows the error message that newt outputs for an ambiguity violation:\n\n\nError: Syscfg ambiguities detected:\n Setting: LOG_NEWTMGR, Packages: [apps/slinky, apps/splitty]\nSetting history (newest -\n oldest):\n LOG_NEWTMGR: [apps/splitty:0, apps/slinky:1, sys/log/full:0]\n\n\n\n\n\nThe above error occurs because the \napps/slinky\n and \napps
/splitty\n packages \nin the split image target both override the same setting with different \nvalues. The \napps/slinky\n package sets the \nsys/log/full\n package \nLOG_NEWTMGR\n \nsetting to 1, and the \napps/splitty\n package sets the setting to 0. The \noverrides are ambiguous because both are \napp\n packages and \nhave the same priority. The following are excerpts of the defintion \nand the two overrides from the \nsyscfg.yml\n files that cause the error:\n\n\n#Package: sys/log/full\nsyscfg.defs:\n LOG_NEWTMGR:\n description: \nEnables or disables newtmgr command tool logging\n\n value: 0\n\n#Package: apps/slinky\nsyscfg.vals:\n LOG_NEWTMGR: 1\n\n#Package: apps/splitty\nsyscfg.vals:\n LOG_NEWTMGR: 0\n\n\n\n\n\nExample: Priority Violation Error Message\n\n\nThe following example shows the error message that newt outputs for a priority violation \nwhere a package tries to change the setting that was defined by another package at \nthe same priority lev
el:\n\n\nError: Priority violations detected (Packages can only override settings defined by packages of lower priority):\n Package: mgmt/newtmgr overriding setting: LOG_NEWTMGR defined by sys/log/full\n\nSetting history (newest -\n oldest):\n LOG_NEWTMGR: [sys/log/full:0]\n\n\n\n\n\nThe above error occurs because the \nmgmt/newtmgr\n lib package \noverrides the \nLOG_NEWTMGR\n setting that the \nsys/log/full\n lib package \ndefines. The following are excerpts of the definition and the override from the \n\nsyscfg.yml\n files that cause this error: \n\n\n#Package: sys/log/full\nsyscfg.defs:\n LOG_NEWTMGR:\n description: \nEnables or disables newtmgr command tool logging\n\n value: 0\n\n#Package: mgmt/newtmgr\nsyscfg.vals:\n LOG_NEWTMGR: 1\n\n\n\n\n\n\n\nFlash Area Violations\n\n\nFor \nflash_owner\n type setting definitions, newt checks \nfor the following violations:\n\n\n\n\nAn undefined flash area is assigned to a setting.\n\n\nA flash area is assigned
to multiple settings.\n\n\n\n\nExample: Undefined Flash Area Error Message\n\n\nThe following example shows the error message that newt outputs for an undefined flash area.\n\n\nBuilding target targets/sim_slinky\nError: Flash errors detected:\n Setting REBOOT_LOG_FLASH_AREA specifies unknown flash area: FLASH_AREA_NOEXIST\n\nSetting history (newest -\n oldest):\n REBOOT_LOG_FLASH_AREA: [hw/bsp/native:FLASH_AREA_NOEXIST, sys/reboot:]\n\n\n\n\n\nThe above error occurs because the \nhw/bsp/native\n package assigns the \nundefined \nFLASH_AREA_NOEXIST\n flash area to the \nsys/reboot\n package \n\nREBOOT_LOG_FLASH_AREA\n setting. The following are excerpts of the definition \nand the override from the \nsyscfg.yml\n files that cause the error:\n\n\n#Package: sys/reboot\nsyscfg.defs:\n REBOOT_LOG_FLASH_AREA:\n description: \nFlash Area to use for reboot log.\n\n type: flash_owner\n value:\n\n#Package: hw/bsp/native\nsyscfg.vals:\n REBOOT_LOG_FLASH_AREA:
FLASH_AREA_NOEXIST\n\n\n\n\n\nExample: Multiple Flash Area Assignment Error Message\n\n\nThe following example shows the error message that newt outputs when multiple \nsettings are assigned the same flash area:\n\n\nError: Flash errors detected:\n Multiple flash_owner settings specify the same flash area\n settings: REBOOT_LOG_FLASH_AREA, CONFIG_FCB_FLASH_AREA\n flash area: FLASH_AREA_NFFS\n\nSetting history (newest -\n oldest):\n CONFIG_FCB_FLASH_AREA: [hw/bsp/native:FLASH_AREA_NFFS, sys/config:]\n REBOOT_LOG_FLASH_AREA: [apps/slinky:FLASH_AREA_NFFS, sys/reboot:]\n\n\n\n\n\nThe above error occurs because the \nhw/bsp/native\n package assigns \nthe \nFLASH_AREA_NFFS\n flash area to the \nsys/config/\n package \n\nCONFIG_FCB_FLASH_AREA\n setting, and the \napps/slinky\n package \nalso assigns \nFLASH_AREA_NFFS\n to the \nsys/reboot\n package \n\nREBOOT_LOG_FLASH_AREA\n setting. The following are excerpts of the \ntwo definitions and the two overrides from
the \nsyscfg.yml\n files \nthat cause the error:\n\n\n# Package: sys/config\nsyscfg.defs.CONFIG_FCB:\n CONFIG_FCB_FLASH_AREA:\n description: \nThe flash area for the Config Flash Circular Buffer\n\n type: \nflash_owner\n\n value:\n\n# Package: sys/reboot\nsyscfg.defs:\n REBOOT_LOG_FLASH_AREA:\n description: \nThe flash area for the reboot log\n\n type: \nflash_owner\n \n value:\n\n#Package: hw/bsp/native\nsyscfg.vals:\n CONFIG_FCB_FLASH_AREA: FLASH_AREA_NFFS\n\n#Package: apps/slinky\nsyscfg.vals: \n REBOOT_LOG_FLASH_AREA: FLASH_AREA_NFFS\n\n\n\n\n\n\n\nRestriction Violations\n\n\nFor setting definitions with \nrestrictions\n specified, newt checks for \nthe following violations:\n\n\n\n\nA setting with a \n$notnull\n restriction does not have a value. \n\n\nFor a setting with expression restrictions, some required setting \nvalues in the expressions evaluate to false. \n\n\n\n\nExample: $notnull Restriction Violation Error Messa
ge\n\n\nThe following example shows the error message that newt outputs when\na setting with \n$notnull\n restriction does not have a value:\n\n\nError: Syscfg restriction violations detected:\n NFFS_FLASH_AREA must not be null \n\nSetting history (newest -\n oldest):\n NFFS_FLASH_AREA: [fs/nffs:]\n\n\n\n\n\nThe above error occurs because the \nfs/nffs\n package defines the \nNFFS_FLASH_AREA\n \nsetting with a \n$notnull\n restriction and no packages override the setting. The \nfollowing is an excerpt of the definition in the \nsyscfg.yml\n file that causes the error:\n\n\n#Package: fs/nffs\nsyscfg.defs:\n NFFS_FLASH_AREA:\n description: \nThe flash area to use for the Newtron Flash File System\n\n type: flash_owner\n value:\n restrictions:\n - $notnull\n\n\n\n\n\nExample: Expression Restriction Violation Error Message\n\n\nThe following example shows the error message that newt outputs for \nan expression restriction violation:\n\n\n
Error: Syscfg restriction violations detected:\n CONFIG_FCB=1 requires CONFIG_FCB_FLASH_AREA be set, but CONFIG_FCB_FLASH_AREA=\n\nSetting history (newest -\n oldest):\n CONFIG_FCB: [targets/sim_slinky:1, sys/config:0]\n CONFIG_FCB_FLASH_AREA: [sys/config:]\n\n\n\n\n\nThe above error occurs because the \nsys/config\n package defines the \nCONFIG_FCB\n setting with \na restriction that when set, requires that the \nCONFIG_FCB_FLASH_AREA\n setting must \nalso be set. The following are excerpts of the definition and the override from the \nsyscfg.yml\n \nfiles that cause the error:\n\n\n# Package: sys/config\nsyscfg.defs:\n CONFIG_FCB:\n description: \nUses Config Flash Circular Buffer\n\n value: 0\n restrictions:\n - \n!CONFIG_NFFS\n\n - \nCONFIG_FCB_FLASH_AREA\n\n\n# Package: targets/sim_slinky\nsyscfg.vals:\n CONFIG_FCB: 1\n\n\n\n\n\n\n\nTask Priority Violations\n\n\nFor \ntask_priority\n type setting definitions, newt chec
ks for the following violations:\n\n\n\n\nA task priority number is assigned to multiple settings. \n\n\nThe task priority number is greater than 239.\n\n\n\n\nExample: Duplicate Task Priority Assignment Error Message\n\n\nThe following example shows the error message that newt outputs when\na task priority number is assigned to multiple settings.\n\n\nNote:\n The settings used in this example are not actual \napps/slinky\n and \nsys/shell\n settings.\nThese settings are created for this example because currently only one Mynewt package \ndefines a \ntask_priority\n type setting. \n\n\nError: duplicate priority value: setting1=SHELL_TASK_PRIORITY setting2=SLINKY_TASK_PRIORITY pkg1=apps/slinky pkg2=sys/shell value=1\n\n\n\n\n\nThe above error occurs because the \napps/slinky\n package defines a \nSLINKY_TASK_PRIORITY\n \nsetting with a default task priority of 1 and the \nsys/shell\n package also defines a \n\nSHELL_TASK_PRIORITY\n setting with a default task priority of 1.\n\n\nExa
mple: Invalid Task Priority Error Message\n\n\nThe following example shows the error message that newt outputs when\na setting is assigned an invalid task priority value:\n\n\nError: invalid priority value: value too great (\n 239); setting=SLINKY_TASK_PRIORITY value=240 pkg=apps/slinky\n\n\n\n\n\nThe above error occurs because the \napps/slinky\n package defines the \nSLINKY_TASK_PRIORITY\n setting \nwith 240 for the default task priority value. \n\n\nNote:\n Newt does not output the \nSetting history\n with task priority violation error messages. \n\n\n\n\nDuplicate System Configuration Setting Definition\n\n\nA setting definition must be unique. Newt checks that only one package in the \ntarget defines a setting. The following example shows the error message that newt \noutputs when multiple packages define the \nLOG_NEWTMGR\n setting:\n\n\nError: setting LOG_NEWTMGR redefined\n\n\n\n\n\nNote:\n Newt does not output the \nSetting history\n with duplicate setting error messages.
",
+ "text": "Validation and Error Messages\n\n\nWith multiple packages defining and overriding system configuration settings, it \nis easy to introduce conflicts and violations that are difficult to find. The \n\nnewt build \ntarget-name\n command validates the setting definitions and value \noverrides for all the packages in the target to ensure a valid and consistent build.\nIt aborts the build when it detects violations or ambiguities between packages.\n\nThe following sections describe the error conditions that newt detects and \nthe error messages that it outputs. For most errors, newt also outputs \nthe \nSetting history\n with the order of package overrides to help \nyou resolve the errors.\n\n\nNote:\n The \nnewt target config \ntarget-name\n command also detects \nerrors and outputs error messages at the top of the command output. \nThe command outputs the package setting definitions and values after it \noutputs the error messages. It is easy to miss the error mes
sages at the top. \n\n\nValue Override Violations\n\n\nThe newt tool uses package priorities to resolve override conflicts. It uses \nthe value override from the highest priority package when multiple \npackages override the same setting. Newt checks for the following \noverride violations:\n\n\n\n\nAmbiguity Violation - Two packages of the same priority override a setting with \ndifferent values. And no higher priority package overrides the setting.\n\n\nPriority Violation - A package overrides a setting defined by a package with higher or \nequal priority. \n\n\n\n\nExample: Ambiguity Violation Error Message\n\n\nThe following example shows the error message that newt outputs for an ambiguity violation:\n\n\nError: Syscfg ambiguities detected:\n Setting: LOG_NEWTMGR, Packages: [apps/slinky, apps/splitty]\nSetting history (newest -\n oldest):\n LOG_NEWTMGR: [apps/splitty:0, apps/slinky:1, sys/log/full:0]\n\n\n\n\n\nThe above error occurs because the \napps/slinky\n and \napps
/splitty\n packages \nin the split image target both override the same setting with different \nvalues. The \napps/slinky\n package sets the \nsys/log/full\n package \nLOG_NEWTMGR\n \nsetting to 1, and the \napps/splitty\n package sets the setting to 0. The \noverrides are ambiguous because both are \napp\n packages and \nhave the same priority. The following are excerpts of the defintion \nand the two overrides from the \nsyscfg.yml\n files that cause the error:\n\n\n#Package: sys/log/full\nsyscfg.defs:\n LOG_NEWTMGR:\n description: \nEnables or disables newtmgr command tool logging\n\n value: 0\n\n#Package: apps/slinky\nsyscfg.vals:\n LOG_NEWTMGR: 1\n\n#Package: apps/splitty\nsyscfg.vals:\n LOG_NEWTMGR: 0\n\n\n\n\n\nExample: Priority Violation Error Message\n\n\nThe following example shows the error message that newt outputs for a priority violation \nwhere a package tries to change the setting that was defined by another package at \nthe same priority lev
el:\n\n\nError: Priority violations detected (Packages can only override settings defined by packages of lower priority):\n Package: mgmt/newtmgr overriding setting: LOG_NEWTMGR defined by sys/log/full\n\nSetting history (newest -\n oldest):\n LOG_NEWTMGR: [sys/log/full:0]\n\n\n\n\n\nThe above error occurs because the \nmgmt/newtmgr\n lib package \noverrides the \nLOG_NEWTMGR\n setting that the \nsys/log/full\n lib package \ndefines. The following are excerpts of the definition and the override from the \n\nsyscfg.yml\n files that cause this error: \n\n\n#Package: sys/log/full\nsyscfg.defs:\n LOG_NEWTMGR:\n description: \nEnables or disables newtmgr command tool logging\n\n value: 0\n\n#Package: mgmt/newtmgr\nsyscfg.vals:\n LOG_NEWTMGR: 1\n\n\n\n\n\n\n\nFlash Area Violations\n\n\nFor \nflash_owner\n type setting definitions, newt checks \nfor the following violations:\n\n\n\n\nAn undefined flash area is assigned to a setting.\n\n\nA flash area is assigned
to multiple settings.\n\n\n\n\nExample: Undefined Flash Area Error Message\n\n\nThe following example shows the error message that newt outputs for an undefined flash area.\n\n\nBuilding target targets/sim_slinky\nError: Flash errors detected:\n Setting REBOOT_LOG_FLASH_AREA specifies unknown flash area: FLASH_AREA_NOEXIST\n\nSetting history (newest -\n oldest):\n REBOOT_LOG_FLASH_AREA: [hw/bsp/native:FLASH_AREA_NOEXIST, sys/reboot:]\n\n\n\n\n\nThe above error occurs because the \nhw/bsp/native\n package assigns the \nundefined \nFLASH_AREA_NOEXIST\n flash area to the \nsys/reboot\n package \n\nREBOOT_LOG_FLASH_AREA\n setting. The following are excerpts of the definition \nand the override from the \nsyscfg.yml\n files that cause the error:\n\n\n#Package: sys/reboot\nsyscfg.defs:\n REBOOT_LOG_FLASH_AREA:\n description: \nFlash Area to use for reboot log.\n\n type: flash_owner\n value:\n\n#Package: hw/bsp/native\nsyscfg.vals:\n REBOOT_LOG_FLASH_AREA:
FLASH_AREA_NOEXIST\n\n\n\n\n\nExample: Multiple Flash Area Assignment Error Message\n\n\nThe following example shows the error message that newt outputs when multiple \nsettings are assigned the same flash area:\n\n\nError: Flash errors detected:\n Multiple flash_owner settings specify the same flash area\n settings: REBOOT_LOG_FLASH_AREA, CONFIG_FCB_FLASH_AREA\n flash area: FLASH_AREA_NFFS\n\nSetting history (newest -\n oldest):\n CONFIG_FCB_FLASH_AREA: [hw/bsp/native:FLASH_AREA_NFFS, sys/config:]\n REBOOT_LOG_FLASH_AREA: [apps/slinky:FLASH_AREA_NFFS, sys/reboot:]\n\n\n\n\n\nThe above error occurs because the \nhw/bsp/native\n package assigns \nthe \nFLASH_AREA_NFFS\n flash area to the \nsys/config/\n package \n\nCONFIG_FCB_FLASH_AREA\n setting, and the \napps/slinky\n package \nalso assigns \nFLASH_AREA_NFFS\n to the \nsys/reboot\n package \n\nREBOOT_LOG_FLASH_AREA\n setting. The following are excerpts of the \ntwo definitions and the two overrides from
the \nsyscfg.yml\n files \nthat cause the error:\n\n\n# Package: sys/config\nsyscfg.defs.CONFIG_FCB:\n CONFIG_FCB_FLASH_AREA:\n description: \nThe flash area for the Config Flash Circular Buffer\n\n type: \nflash_owner\n\n value:\n\n# Package: sys/reboot\nsyscfg.defs:\n REBOOT_LOG_FLASH_AREA:\n description: \nThe flash area for the reboot log\n\n type: \nflash_owner\n \n value:\n\n#Package: hw/bsp/native\nsyscfg.vals:\n CONFIG_FCB_FLASH_AREA: FLASH_AREA_NFFS\n\n#Package: apps/slinky\nsyscfg.vals: \n REBOOT_LOG_FLASH_AREA: FLASH_AREA_NFFS\n\n\n\n\n\n\n\nRestriction Violations\n\n\nFor setting definitions with \nrestrictions\n specified, newt checks for \nthe following violations:\n\n\n\n\nA setting with a \n$notnull\n restriction does not have a value. \n\n\nFor a setting with expression restrictions, some required setting \nvalues in the expressions evaluate to false. \n\n\n\n\nExample: $notnull Restriction Violation Error Messa
ge\n\n\nThe following example shows the error message that newt outputs when\na setting with \n$notnull\n restriction does not have a value:\n\n\nError: Syscfg restriction violations detected:\n NFFS_FLASH_AREA must not be null \n\nSetting history (newest -\n oldest):\n NFFS_FLASH_AREA: [fs/nffs:]\n\n\n\n\n\nThe above error occurs because the \nfs/nffs\n package defines the \nNFFS_FLASH_AREA\n \nsetting with a \n$notnull\n restriction and no packages override the setting. The \nfollowing is an excerpt of the definition in the \nsyscfg.yml\n file that causes the error:\n\n\n#Package: fs/nffs\nsyscfg.defs:\n NFFS_FLASH_AREA:\n description: \nThe flash area to use for the Newtron Flash File System\n\n type: flash_owner\n value:\n restrictions:\n - $notnull\n\n\n\n\n\nExample: Expression Restriction Violation Error Message\n\n\nThe following example shows the error message that newt outputs for \nan expression restriction violation:\n\n\n
Error: Syscfg restriction violations detected:\n CONFIG_FCB=1 requires CONFIG_FCB_FLASH_AREA be set, but CONFIG_FCB_FLASH_AREA=\n\nSetting history (newest -\n oldest):\n CONFIG_FCB: [targets/sim_slinky:1, sys/config:0]\n CONFIG_FCB_FLASH_AREA: [sys/config:]\n\n\n\n\n\nThe above error occurs because the \nsys/config\n package defines the \nCONFIG_FCB\n setting with \na restriction that when set, requires that the \nCONFIG_FCB_FLASH_AREA\n setting must \nalso be set. The following are excerpts of the definition and the override from the \nsyscfg.yml\n \nfiles that cause the error:\n\n\n# Package: sys/config\nsyscfg.defs:\n CONFIG_FCB:\n description: \nUses Config Flash Circular Buffer\n\n value: 0\n restrictions:\n - \n!CONFIG_NFFS\n\n - \nCONFIG_FCB_FLASH_AREA\n\n\n# Package: targets/sim_slinky\nsyscfg.vals:\n CONFIG_FCB: 1\n\n\n\n\n\n\n\nTask Priority Violations\n\n\nFor \ntask_priority\n type setting definitions, newt chec
ks for the following violations:\n\n\n\n\nA task priority number is assigned to multiple settings. \n\n\nThe task priority number is greater than 239.\n\n\n\n\nExample: Duplicate Task Priority Assignment Error Message\n\n\nThe following example shows the error message that newt outputs when\na task priority number is assigned to multiple settings.\n\n\nNote:\n The settings used in this example are not actual \napps/slinky\n and \nsys/shell\n settings.\nThese settings are created for this example because currently only one Mynewt package \ndefines a \ntask_priority\n type setting. \n\n\nError: duplicate priority value: setting1=SHELL_TASK_PRIORITY setting2=SLINKY_TASK_PRIORITY pkg1=apps/slinky pkg2=sys/shell value=1\n\n\n\n\n\nThe above error occurs because the \napps/slinky\n package defines a \nSLINKY_TASK_PRIORITY\n \nsetting with a default task priority of 1 and the \nsys/shell\n package also defines a \n\nSHELL_TASK_PRIORITY\n setting with a default task priority of 1.\n\n\nExa
mple: Invalid Task Priority Error Message\n\n\nThe following example shows the error message that newt outputs when\na setting is assigned an invalid task priority value:\n\n\nError: invalid priority value: value too great (\n 239); setting=SLINKY_TASK_PRIORITY value=240 pkg=apps/slinky\n\n\n\n\n\nThe above error occurs because the \napps/slinky\n package defines the \nSLINKY_TASK_PRIORITY\n setting \nwith 240 for the default task priority value. \n\n\nNote:\n Newt does not output the \nSetting history\n with task priority violation error messages. \n\n\n\n\nDuplicate System Configuration Setting Definition\n\n\nA setting definition must be unique. Newt checks that only one package in the \ntarget defines a setting. The following example shows the error message that newt \noutputs when multiple packages define the \nLOG_NEWTMGR\n setting:\n\n\nError: setting LOG_NEWTMGR redefined\n\n\n\n\n\nNote:\n Newt does not output the \nSetting history\n with duplicate setting error messages.
\n\n\n\nOverride of Undefined System Configuration Setting\n\n\nThe \nnewt build\n command ignores overrides of undefined system configuration settings. The command does not print a warning when you run it with the default log level. If you override a setting and the value is not assigned to the setting, you may have misspelled the setting name or a package no longer defines the setting. You have two options to troubleshoot this problem:\n\n\n\n\nRun the \nnewt target config show\n command to see the configuration setting definitions and overrides.\n\n\nRun the \nnewt build -ldebug\n command to build your target with DEBUG log level. \n\n\n\n\nNote: The \nnewt build -ldebug\n command generates lots of output and we recommend that you use the \nnewt target config show\n command option.\n\n\n\nExample: Ignoring Override of Undefined Setting Message\n\n\nThe following example shows that the \napps/slinky\n application overrides the \nLOG_NEWTMGR\n setting but omits the \nT\n as an e
xample of an error and overrides the misspelled \nLOG_NEWMGR\n setting. Here is an excerpt from its \nsyscfg.yml\n file: \n\n\n#package: apps/slinky\nsyscfg.vals:\n # Enable the shell task.\n SHELL_TASK: 1\n ...\n\n # Enable newtmgr commands.\n STATS_NEWTMGR: 1\n LOG_NEWMGR: 1\n\n\n\n\n\n\nThe \nnewt target config show slinky_sim\n command outputs the following WARNING message:\n\n\n2017/02/18 17:19:12.119 [WARNING] Ignoring override of undefined settings:\n2017/02/18 17:19:12.119 [WARNING] LOG_NEWMGR\n2017/02/18 17:19:12.119 [WARNING] NFFS_FLASH_AREA\n2017/02/18 17:19:12.119 [WARNING] Setting history (newest -\n oldest):\n2017/02/18 17:19:12.119 [WARNING] LOG_NEWMGR: [apps/slinky:1]\n2017/02/18 17:19:12.119 [WARNING] NFFS_FLASH_AREA: [hw/bsp/native:FLASH_AREA_NFFS]\n\n\n\n\n\n\n\nThe \nnewt build -ldebug slinky_sim\n command outputs the following DEBUG message: \n\n\n2017/02/18 17:06:21.451 [DEBUG] Ignoring override of undefined settings:\n2
017/02/18 17:06:21.451 [DEBUG] LOG_NEWMGR\n2017/02/18 17:06:21.451 [DEBUG] NFFS_FLASH_AREA\n2017/02/18 17:06:21.451 [DEBUG] Setting history (newest -\n oldest):\n2017/02/18 17:06:21.451 [DEBUG] LOG_NEWMGR: [apps/slinky:1]\n2017/02/18 17:06:21.451 [DEBUG] NFFS_FLASH_AREA: [hw/bsp/native:FLASH_AREA_NFFS]\n\n\n\n\n\n\n\nBSP Package Overrides Undefined Configuration Settings\n\n\nYou might see a warning that indicates your application's BSP package is overriding some undefined settings. As you can see from the previous example, the WARNING message shows that the \nhw/bsp/native\n package is overriding the undefined \nNFFS_FLASH_AREA\n setting. This is not an error because of the way a BSP package defines and assigns its flash areas to packages that use flash memory.\n\n\nA BSP package defines, in its \nbsp.yml\n file, a flash area map of the flash areas on the board. A package that uses flash memory must define a flash area configuration setting name. The BSP package ove
rrides the package's flash area setting with one of the flash areas from its flash area map. A BSP package overrides the flash area settings for all packages that use flash memory because it does not know the packages that an application uses. When an application does not include one of these packages, the flash area setting for the package is undefined. You will see a message that indicates the BSP package overrides this undefined setting.\n\n\nHere are excerpts from the \nhw/bsp/native\n package's \nbsp.yml\n and \nsyscfg.yml\n files for the \nslinky_sim\n target. The BSP package defines the flash area map in its \nbsp.yml\n file and overrides the flash area settings for all packages in its \nsyscfg.yml\n file. The \nslinky_sim\n target does not use the \nfs/nffs\n package which defines the \nNFFS_FLASH_AREA\n setting. Newt warns that the \nhw/bsp/native\n packages overrides the undefined \nNFFS_FLASH_AREA\n setting.\n\n\n# hw/bsp/native bsp.yml\nbsp.flash_map:\n areas:\n
# System areas.\n FLASH_AREA_BOOTLOADER:\n device: 0\n offset: 0x00000000\n size: 16kB\n\n ...\n\n FLASH_AREA_IMAGE_SCRATCH:\n device: 0\n offset: 0x000e0000\n size: 128kB\n\n # User areas.\n FLASH_AREA_REBOOT_LOG:\n user_id: 0\n device: 0\n offset: 0x00004000\n size: 16kB\n FLASH_AREA_NFFS:\n user_id: 1\n device: 0\n offset: 0x00008000\n\n# hw/bsp/native syscfg.yml\nsyscfg.vals:\n NFFS_FLASH_AREA: FLASH_AREA_NFFS\n CONFIG_FCB_FLASH_AREA: FLASH_AREA_NFFS\n REBOOT_LOG_FLASH_AREA: FLASH_AREA_REBOOT_LOG",
"title": "Validation and Error Messages"
},
{
@@ -8011,6 +8011,21 @@
"title": "Duplicate System Configuration Setting Definition"
},
{
+ "location": "/os/modules/sysinitconfig/sysconfig_error/#override-of-undefined-system-configuration-setting",
+ "text": "The newt build command ignores overrides of undefined system configuration settings. The command does not print a warning when you run it with the default log level. If you override a setting and the value is not assigned to the setting, you may have misspelled the setting name or a package no longer defines the setting. You have two options to troubleshoot this problem: Run the newt target config show command to see the configuration setting definitions and overrides. Run the newt build -ldebug command to build your target with DEBUG log level. Note: The newt build -ldebug command generates lots of output and we recommend that you use the newt target config show command option.",
+ "title": "Override of Undefined System Configuration Setting"
+ },
+ {
+ "location": "/os/modules/sysinitconfig/sysconfig_error/#example-ignoring-override-of-undefined-setting-message",
+ "text": "The following example shows that the apps/slinky application overrides the LOG_NEWTMGR setting but omits the T as an example of an error and overrides the misspelled LOG_NEWMGR setting. Here is an excerpt from its syscfg.yml file: #package: apps/slinky\nsyscfg.vals:\n # Enable the shell task.\n SHELL_TASK: 1\n ...\n\n # Enable newtmgr commands.\n STATS_NEWTMGR: 1\n LOG_NEWMGR: 1 \nThe newt target config show slinky_sim command outputs the following WARNING message: 2017/02/18 17:19:12.119 [WARNING] Ignoring override of undefined settings:\n2017/02/18 17:19:12.119 [WARNING] LOG_NEWMGR\n2017/02/18 17:19:12.119 [WARNING] NFFS_FLASH_AREA\n2017/02/18 17:19:12.119 [WARNING] Setting history (newest - oldest):\n2017/02/18 17:19:12.119 [WARNING] LOG_NEWMGR: [apps/slinky:1]\n2017/02/18 17:19:12.119 [WARNING] NFFS_FLASH_AREA: [hw/bsp/native:FLASH_AREA_NFFS] The newt build -ldebug slinky_sim command outputs the fo
llowing DEBUG message: 2017/02/18 17:06:21.451 [DEBUG] Ignoring override of undefined settings:\n2017/02/18 17:06:21.451 [DEBUG] LOG_NEWMGR\n2017/02/18 17:06:21.451 [DEBUG] NFFS_FLASH_AREA\n2017/02/18 17:06:21.451 [DEBUG] Setting history (newest - oldest):\n2017/02/18 17:06:21.451 [DEBUG] LOG_NEWMGR: [apps/slinky:1]\n2017/02/18 17:06:21.451 [DEBUG] NFFS_FLASH_AREA: [hw/bsp/native:FLASH_AREA_NFFS]",
+ "title": "Example: Ignoring Override of Undefined Setting Message"
+ },
+ {
+ "location": "/os/modules/sysinitconfig/sysconfig_error/#bsp-package-overrides-undefined-configuration-settings",
+ "text": "You might see a warning that indicates your application's BSP package is overriding some undefined settings. As you can see from the previous example, the WARNING message shows that the hw/bsp/native package is overriding the undefined NFFS_FLASH_AREA setting. This is not an error because of the way a BSP package defines and assigns its flash areas to packages that use flash memory. A BSP package defines, in its bsp.yml file, a flash area map of the flash areas on the board. A package that uses flash memory must define a flash area configuration setting name. The BSP package overrides the package's flash area setting with one of the flash areas from its flash area map. A BSP package overrides the flash area settings for all packages that use flash memory because it does not know the packages that an application uses. When an application does not include one of these packages, the flash area setting for the package is undefined. You will see a message t
hat indicates the BSP package overrides this undefined setting. Here are excerpts from the hw/bsp/native package's bsp.yml and syscfg.yml files for the slinky_sim target. The BSP package defines the flash area map in its bsp.yml file and overrides the flash area settings for all packages in its syscfg.yml file. The slinky_sim target does not use the fs/nffs package which defines the NFFS_FLASH_AREA setting. Newt warns that the hw/bsp/native packages overrides the undefined NFFS_FLASH_AREA setting. # hw/bsp/native bsp.yml\nbsp.flash_map:\n areas:\n # System areas.\n FLASH_AREA_BOOTLOADER:\n device: 0\n offset: 0x00000000\n size: 16kB\n\n ...\n\n FLASH_AREA_IMAGE_SCRATCH:\n device: 0\n offset: 0x000e0000\n size: 128kB\n\n # User areas.\n FLASH_AREA_REBOOT_LOG:\n user_id: 0\n device: 0\n offset: 0x00004000\n
size: 16kB\n FLASH_AREA_NFFS:\n user_id: 1\n device: 0\n offset: 0x00008000\n\n# hw/bsp/native syscfg.yml\nsyscfg.vals:\n NFFS_FLASH_AREA: FLASH_AREA_NFFS\n CONFIG_FCB_FLASH_AREA: FLASH_AREA_NFFS\n REBOOT_LOG_FLASH_AREA: FLASH_AREA_REBOOT_LOG",
+ "title": "BSP Package Overrides Undefined Configuration Settings"
+ },
+ {
"location": "/network/ble/ble_intro/",
"text": "BLE Introduction\n\n\nApache Mynewt offers the world's first fully open-source Bluetooth Low Energy (BLE) or Bluetooth Smart stack fully compliant with BLE 4.2 specifications. It is called NimBLE. \n\n\nBLE technology operates in the unlicensed industrial, scientific and medical (ISM) band at 2.4 to 2.485 GHz which is available in most countries. It uses a spread spectrum, frequency hopping, full-duplex signal. BLE FHSS employs 40 2-MHz-wide channels to ensure greater reliability over longer distances. It also features 0-dBm (1 mW) power output and a typical maximum range of 50 meters. Note that BLE is not compatible with standard Bluetooth.\n\n\n\n\nFeature Support\n\n\nNimBLE complies with Bluetooth Core Specification 4.2 which introduces several new features that make it an ideal wireless technology for the Internet of Things (IoT).\n\n\n\n\nLE Privacy 1.2 for frequent changes to the device address to make it difficult to track for outsiders\n\n\nLE Secure Co
nnections featuring FIPS-compliant algorithms.\n\n\nLE Data Length Extension for higher throughput\n\n\nComing Soon\n: Assigning an Internet Protocol (IP) address (complaint with the IPv6 or 6LoWPAN standard) to a Bluetooth device through Internet Protocol Support Profile (IPSP)\n\n\n\n\nComponents\n\n\nA Bluetooth low energy stack (NimBLE included) consists of two components with several subcomponents:\n\n\n\n\n\n\nController\n\n\n\n\nPhysical Layer\n: adaptive frequency-hopping Gaussian Frequency Shift Keying (GFSK) radio using 40 RF channels (0-39), with 2 MHz spacing.\n\n\nLink Layer\n: with one of five states (Standby, Advertising, Scanning, Initiating, Connection states) active at any time\n\n\n\n\n\n\n\n\nHost\n\n\n\n\nLogical Link Control and Adaptation Protocol (L2CAP)\n: provides logical channels, named L2CAP channels, which are multiplexed over one or more logical links to provide packet segmentation and reassembly, flow control, error control, streaming, QoS etc. \n\n\nS
ecurity Manager (SM)\n: uses Security Manager Protocol (SMP) for pairing and transport specific key distribution for securing radio communication \n\n\nAttribute protocol (ATT)\n: allows a device (\nServer\n) to expose certain pieces of data, known as \nAttributes\n, to another device (\nClient\n)\n\n\nGeneric Attribute Profile (GATT)\n: a framework for using the ATT protocol to exchange attributes encapsulated as \nCharacteristics\n or \nServices\n \n\n\nGeneric Access Profile (GAP)\n: a base profile which all Bluetooth devices implement, which in the case of LE, defines the Physical Layer, Link Layer, L2CAP, Security Manager, Attribute Protocol and Generic Attribute Profile. \n\n\nHost Controller Interface (HCI)\n: the interface between the host and controller either through software API or by a hardware interface such as SPI, UART or USB.\n\n\n\n\n\n\n\n\nSubsequent chapters in this manual will go into the details of the implementation of each component, APIs available, and thing
s to consider while designing a NimBLE app.\n\n\n\n\nExample NimBLE projects\n\n\nMynewt comes with several built-in projects or applications using NimBLE. These allow users to try out NimBLE, understand how to use available services, and build their own applications using one or more of the examples as seed.\n\n\n\n\n\n\nbletiny\n : A simple shell application which provides a basic interface to the host-side of the BLE stack. Supported operations include GAP, GATT, and L2CAP.\n\n\n\n\n\n\nbleprph\n: A basic peripheral device with no user interface. It advertises automatically on startup, and resumes advertising whenever a connection is terminated. It supports a maximum of one connection.\n\n\n\n\n\n\nblecent\n: A basic central device with no user interface. This application scans for a peripheral that supports the alert notification service (ANS). Upon discovering such a peripheral, blecent connects and performs the following actions:\n\n\n\n\nReads the ANS Supported New Alert Ca
tegory characteristic.\n\n\nWrites the ANS Alert Notification Control Point characteristic.\n\n\nSubscribes to notifications for the ANS Unread Alert Status characteristic.\n\n\n\n\n\n\n\n\nblehci\n: Implements a BLE controller-only application. A separate host-only implementation, such as Linux's BlueZ, can interface with this application via HCI over UART.\n\n\n\n\n\n\nbleuart\n: Implements a simple BLE peripheral that supports the Nordic\n\nUART / Serial Port Emulation service",
"title": "NimBLE Introduction"
@@ -10182,7 +10197,7 @@
},
{
"location": "/newt/newt_intro/",
- "text": "Newt Tool\n\n\nIntroduction\n\n\nNewt is a smart build and package management system for embedded contexts. It is a single tool that accomplishes both the following goals:\n\n\n\n\nsource package management \n\n\nbuild, debug and install.\n\n\n\n\nRationale\n\n\nIn order for the Mynewt operating system to work well for constrained environments across the many different types of microcontroller applications (from doorbells to medical devices to power grids), a system is needed that lets you select which packages to install and which packages to build.\n\n\nThe build systems for embedded devices are often fairly complicated and not well served for this purpose. For example, autoconf is designed for detecting system compatibility issues but not well suited when it comes to tasks like:\n\n\n\n\nBuilding for multiple targets\n\n\nDeciding what to build in and what not to build in\n\n\nManaging dependencies between components\n\n\n\n\nFortunately, solutions addressi
ng these very issues can be found in source package management systems in higher level languages such as Javascript \n(Node), Go, PHP and Ruby. We decided to fuse their source management \nsystems with a make system built for embedded systems and create Newt.\n\n\nBuild System\n\n\nA good build system must allow the user to take a few common steps while developing embedded applications:\n\n\n\n\nGenerate full flash images\n\n\nDownload debug images to a target board using a debugger\n\n\nConditionally compile libraries \n code based upon build settings\n\n\n\n\nNewt can read a directory tree, build a dependency tree, and emit the right build artifacts. An example newt source tree is in incubator-mynewt-blinky/develop:\n\n\n$ tree -L 3 \n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\u2500\u2500 README.md\n\n\u251c\u2500\u2500 apps\n\n\u2502 \u2514\u2500\u2500 blinky\n\u2502 \u251c\u2500\u2500 pkg.yml\n\u2502 \u2514\u25
00\u2500 src\n\u251c\u2500\u2500 project.yml\n\n\u2514\u2500\u2500 targets\n\n \u251c\u2500\u2500 my_blinky_sim\n \u2502 \u251c\u2500\u2500 pkg.yml\n \u2502 \u2514\u2500\u2500 target.yml\n \u2514\u2500\u2500 unittest\n \u251c\u2500\u2500 pkg.yml\n \u2514\u2500\u2500 target.yml\n\n6 directories, 10 files\n\n\n\n\n\n\n\nWhen Newt sees a directory tree that contains a \"project.yml\" file, it is smart enough to recognize it as the base directory of a project, and \nautomatically builds a package tree. It also recognizes two important package directories in the package tree - \"apps\" and \"targets\". More on these directories in \nNewt Theory of Ops\n.\n\n\nWhen Newt is told to build a project, it recursively resolves all package dependencies and generates artifacts that are placed in the bin/ directory at the top-level of the project. The artifact directory is prefixed by the target name being built - \nmy_blinky_sim\n for example:\n\n\n$ tree bin\n
bin\n\u2514\u2500\u2500 my_blinky_sim\n \u251c\u2500\u2500 apps\n \u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.a\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.a.cmd\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf.cmd\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf.dSYM\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 Contents\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 Info.plist\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 Resources\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 DWARF\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky.elf\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf.lst\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 main.d\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 main.o\n \
u2502\u00a0\u00a0 \u2514\u2500\u2500 main.o.cmd\n \u251c\u2500\u2500 hw\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 bsp\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 native\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hal_bsp.d\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hal_bsp.o\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hal_bsp.o.cmd\n\nsnip\n\n\n\n\n\n\n\n\nMore operations using Newt\n\n\nOnce a target has been built, Newt allows additional operations on the target. \n\n\n\n\nload\n: Download built target to board\n\n\ndebug\n: Open debugger session to target\n\n\nsize\n: Get size of target components\n\n\ncreate-image\n: Add image header to the binary image\n\n\nrun\n: Build, create image, load, and finally open a debug session with the target\n\n\n\n\nFor more details on how Newt works, go to \nNewt - Theory of Operations\n.\n\n\n\n\nSource Management and Repositories\n\n\nThe other major
element of the Newt tool is the ability to create reusable source distributions from a collection of code. \nA project can be a reusable container of source code.\n In other words, projects can be versioned and redistributed, not packages. A project bundles together packages that are typically needed to work together in a product e.g. RTOS core, filesystem APIs, and networking stack.\n\n\nA project that has been made redistributable is known as a \nrepository\n. \nRepositories can be added to your local project by adding them into your project.yml file. Here is an example of the blinky project's yml file which relies on apache-mynewt-core:\n\n\n$ more project.yml\n\nsnip\n\nproject.repositories:\n - apache-mynewt-core\n\n# Use github\ns distribution mechanism for core ASF libraries.\n# This provides mirroring automatically for us.\n#\nrepository.apache-mynewt-core:\n type: github\n vers: 0-latest\n user: apache\n repo: incubator-mynewt-core\n\n\n\n\n\n\n\nWhen y
ou specify this repository in the blinky's project file, you can then use the Newt tool to install dependencies:\n\n\n$ newt install\nDownloading repository description for apache-mynewt-core... success!\nDownloading repository incubator-mynewt-core (branch: develop) at \nhttps://github.com/apache/incubator-mynewt-core.git\nCloning into \n\n/var/folders/7l/7b3w9m4n2mg3sqmgw2q1b9p80000gn/T/newt-repo814721459\n...\nremote: Counting objects: 17601, done.\nremote: Compressing objects: 100% (300/300), done.\nremote: Total 17601 (delta 142), reused 0 (delta 0), pack-reused 17284\nReceiving objects: 100% (17601/17601), 6.09 MiB | 3.17 MiB/s, done.\nResolving deltas: 100% (10347/10347), done.\nChecking connectivity... done.\nRepos successfully installed\n\n\n\n\n\n\n\nNewt will install this repository in the \n/repos directory. In the case of blinky, the directory structure ends up looking like:\n\n\n$ tree -L 2\n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2
500 NOTICE\n\u251c\u2500\u2500 README.md\n\u251c\u2500\u2500 apps\n\u2502 \u2514\u2500\u2500 blinky\n\u251c\u2500\u2500 project.state\n\u251c\u2500\u2500 project.yml\n\u251c\u2500\u2500 repos\n\u2502 \u2514\u2500\u2500 apache-mynewt-core\n\u2514\u2500\u2500 targets\n \u251c\u2500\u2500 my_blinky_sim\n \u2514\u2500\u2500 unittest\n\n\n\n\n\n\n\nIn order to reference the installed repositories in packages, the \"@\" notation should be specified in the repository specifier. As an example, the apps/blinky application has the following dependencies in its pkg.yml file. This tells the build system to look in the base directory of repos/apache-mynewt-core for the \nlibs/os\n, \nhw/hal\n, and \nlibs/console/full\n packages.\n\n\n$ more apps/blinky/pkg.yml\n\nsnip\n\npkg.deps:\n - \n@apache-mynewt-core/libs/os\n\n - \n@apache-mynewt-core/hw/hal\n\n - \n@apache-mynewt-core/libs/console/full\n\n\n\n\n\n\n\n\nAutocompletion in Bash\n\n\nNewt has the ability to autocompl
ete within \nbash\n. The following instructions allow MAC users to enable autocomplete within \nbash\n.\n\n\n\n\nInstall the autocomplete tools for bash via \nbrew install bash-completion\n\n\nTell your shell to use newt for autocompletion of newt via \ncomplete -C \"newt complete\" newt\n. You can add this to your .bashrc or other init file to have it automatically set for all bash shells.\n\n\n\n\nNotes:\n\n\n\n\nAutocomplete will give you flag hints, but only if you type a '-'. \n\n\nAutocomplete will not give you completion hints for the flag arguments (those optional things after the flag like \n-l DEBUG\n)\n\n\nAutocomplete uses newt to parse the project to find targets and libs.",
+ "text": "Newt Tool\n\n\nIntroduction\n\n\nNewt is a smart build and package management system for embedded contexts. It is a single tool that accomplishes both the following goals:\n\n\n\n\nsource package management \n\n\nbuild, debug and install.\n\n\n\n\nRationale\n\n\nIn order for the Mynewt operating system to work well for constrained environments across the many different types of microcontroller applications (from doorbells to medical devices to power grids), a system is needed that lets you select which packages to install and which packages to build.\n\n\nThe build systems for embedded devices are often fairly complicated and not well served for this purpose. For example, autoconf is designed for detecting system compatibility issues but not well suited when it comes to tasks like:\n\n\n\n\nBuilding for multiple targets\n\n\nDeciding what to build in and what not to build in\n\n\nManaging dependencies between components\n\n\n\n\nFortunately, solutions addressi
ng these very issues can be found in source package management systems in higher level languages such as Javascript \n(Node), Go, PHP and Ruby. We decided to fuse their source management \nsystems with a make system built for embedded systems and create Newt.\n\n\nBuild System\n\n\nA good build system must allow the user to take a few common steps while developing embedded applications:\n\n\n\n\nGenerate full flash images\n\n\nDownload debug images to a target board using a debugger\n\n\nConditionally compile libraries \n code based upon build settings\n\n\n\n\nNewt can read a directory tree, build a dependency tree, and emit the right build artifacts. An example newt source tree is in incubator-mynewt-blinky/develop:\n\n\n$ tree -L 3 \n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\u2500\u2500 README.md\n\n\u251c\u2500\u2500 apps\n\n\u2502 \u2514\u2500\u2500 blinky\n\u2502 \u251c\u2500\u2500 pkg.yml\n\u2502 \u2514\u25
00\u2500 src\n\u251c\u2500\u2500 project.yml\n\n\u2514\u2500\u2500 targets\n\n \u251c\u2500\u2500 my_blinky_sim\n \u2502 \u251c\u2500\u2500 pkg.yml\n \u2502 \u2514\u2500\u2500 target.yml\n \u2514\u2500\u2500 unittest\n \u251c\u2500\u2500 pkg.yml\n \u2514\u2500\u2500 target.yml\n\n6 directories, 10 files\n\n\n\n\n\n\n\nWhen Newt sees a directory tree that contains a \"project.yml\" file, it is smart enough to recognize it as the base directory of a project, and \nautomatically builds a package tree. It also recognizes two important package directories in the package tree - \"apps\" and \"targets\". More on these directories in \nNewt Theory of Ops\n.\n\n\nWhen Newt builds a target, it recursively resolves all package dependencies, and generates artifacts that are placed in the bin/targets/\ntarget-name\n/app/apps/\napp-name\n directory, where the bin directory is under the project base directory, \ntarget-name\n is the name of the target, and \napp
-name\n is the name of the application. For our example \nmy_blinky_sim\n is the name of the target and \nblinky\n is the name of the application. The \nblinky.elf\n executable is stored in the bin/targets/my_blinky_sim/app/apps/blinky directory as shown in the source tree:\n\n\ntree -L 6 bin/\nbin/\n\u2514\u2500\u2500 targets\n \u251c\u2500\u2500 my_blinky_sim\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 app\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 apps\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 apps\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 apps_blinky.a\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 apps_blinky.a.cmd\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf\n \u2502\u00a0\u00a0 \u2502\u00a0\u00
a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf.cmd\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf.dSYM\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf.lst\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 manifest.json\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hw\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 bsp\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 native\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 drivers\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 uart\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hal\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 h
w_hal.a\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hw_hal.a.cmd\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 repos\n\n\nsnip\n\n\n\n\n\n\n\n\nMore operations using Newt\n\n\nOnce a target has been built, Newt allows additional operations on the target. \n\n\n\n\nload\n: Download built target to board\n\n\ndebug\n: Open debugger session to target\n\n\nsize\n: Get size of target components\n\n\ncreate-image\n: Add image header to the binary image\n\n\nrun\n: Build, create image, load, and finally open a debug session with the target\n\n\ntarget\n: Create, delete, configure, and query a target\n\n\n\n\nFor more details on how Newt works, go to \nNewt - Theory of Operations\n.\n\n\n\n\nSource Management and Repositories\n\n\nThe other major element of the Newt tool is the ability to create reusable source distributions from a collection of code. \nA project can be a reusable
container of source code.\n In other words, projects can be versioned and redistributed, not packages. A project bundles together packages that are typically needed to work together in a product e.g. RTOS core, filesystem APIs, and networking stack.\n\n\nA project that has been made redistributable is known as a \nrepository\n. \nRepositories can be added to your local project by adding them into your project.yml file. Here is an example of the blinky project's yml file which relies on apache-mynewt-core:\n\n\n$ more project.yml\n\nsnip\n\nproject.repositories:\n - apache-mynewt-core\n\n# Use github\ns distribution mechanism for core ASF libraries.\n# This provides mirroring automatically for us.\n#\nrepository.apache-mynewt-core:\n type: github\n vers: 0-latest\n user: apache\n repo: incubator-mynewt-core\n\n\n\n\n\n\n\nWhen you specify this repository in the blinky's project file, you can then use the Newt tool to install dependencies:\n\n\n$ newt install\nDow
nloading repository description for apache-mynewt-core... success!\nDownloading repository incubator-mynewt-core (branch: develop) at \nhttps://github.com/apache/incubator-mynewt-core.git\nCloning into \n\n/var/folders/7l/7b3w9m4n2mg3sqmgw2q1b9p80000gn/T/newt-repo814721459\n...\nremote: Counting objects: 17601, done.\nremote: Compressing objects: 100% (300/300), done.\nremote: Total 17601 (delta 142), reused 0 (delta 0), pack-reused 17284\nReceiving objects: 100% (17601/17601), 6.09 MiB | 3.17 MiB/s, done.\nResolving deltas: 100% (10347/10347), done.\nChecking connectivity... done.\nRepos successfully installed\n\n\n\n\n\n\n\nNewt will install this repository in the \n/repos directory. In the case of blinky, the directory structure ends up looking like:\n\n\n$ tree -L 2\n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\u2500\u2500 README.md\n\u251c\u2500\u2500 apps\n\u2502 \u2514\u2500\u2500 blinky\n\u251c\u2500\u2500 project.state\n
\u251c\u2500\u2500 project.yml\n\u251c\u2500\u2500 repos\n\u2502 \u2514\u2500\u2500 apache-mynewt-core\n\u2514\u2500\u2500 targets\n \u251c\u2500\u2500 my_blinky_sim\n \u2514\u2500\u2500 unittest\n\n\n\n\n\n\n\nIn order to reference the installed repositories in packages, the \"@\" notation should be specified in the repository specifier. As an example, the apps/blinky application has the following dependencies in its pkg.yml file. This tells the build system to look in the base directory of repos/apache-mynewt-core for the \nkernel/os\n, \nhw/hal\n, and \nsys/console/full\n packages.\n\n\n$ more apps/blinky/pkg.yml\n\nsnip\n\npkg.deps:\n - \n@apache-mynewt-core/kernel/os\n\n - \n@apache-mynewt-core/hw/hal\n\n - \n@apache-mynewt-core/sys/console/full\n\n\n\n\n\n\n\n\nAutocompletion in Bash\n\n\nNewt has the ability to autocomplete within \nbash\n. The following instructions allow MAC users to enable autocomplete within \nbash\n.\n\n\n\n\nInstall the autocompl
ete tools for bash via \nbrew install bash-completion\n\n\nTell your shell to use newt for autocompletion of newt via \ncomplete -C \"newt complete\" newt\n. You can add this to your .bashrc or other init file to have it automatically set for all bash shells.\n\n\n\n\nNotes:\n\n\n\n\nAutocomplete will give you flag hints, but only if you type a '-'. \n\n\nAutocomplete will not give you completion hints for the flag arguments (those optional things after the flag like \n-l DEBUG\n)\n\n\nAutocomplete uses newt to parse the project to find targets and libs.",
"title": "toc"
},
{
@@ -10202,17 +10217,17 @@
},
{
"location": "/newt/newt_intro/#build-system",
- "text": "A good build system must allow the user to take a few common steps while developing embedded applications: Generate full flash images Download debug images to a target board using a debugger Conditionally compile libraries code based upon build settings Newt can read a directory tree, build a dependency tree, and emit the right build artifacts. An example newt source tree is in incubator-mynewt-blinky/develop: $ tree -L 3 \n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\u2500\u2500 README.md \u251c\u2500\u2500 apps \u2502 \u2514\u2500\u2500 blinky\n\u2502 \u251c\u2500\u2500 pkg.yml\n\u2502 \u2514\u2500\u2500 src\n\u251c\u2500\u2500 project.yml \u2514\u2500\u2500 targets \u251c\u2500\u2500 my_blinky_sim\n \u2502 \u251c\u2500\u2500 pkg.yml\n \u2502 \u2514\u2500\u2500 target.yml\n \u2514\u2500\u2500 unittest\n \u251c\u2500\u2500 pkg.yml\n \u2514\u2500\u2500
target.yml\n\n6 directories, 10 files When Newt sees a directory tree that contains a \"project.yml\" file, it is smart enough to recognize it as the base directory of a project, and \nautomatically builds a package tree. It also recognizes two important package directories in the package tree - \"apps\" and \"targets\". More on these directories in Newt Theory of Ops . When Newt is told to build a project, it recursively resolves all package dependencies and generates artifacts that are placed in the bin/ directory at the top-level of the project. The artifact directory is prefixed by the target name being built - my_blinky_sim for example: $ tree bin\nbin\n\u2514\u2500\u2500 my_blinky_sim\n \u251c\u2500\u2500 apps\n \u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.a\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.a.cmd\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf\n \u2502\u00a0\u00a0 \u251c\u
2500\u2500 blinky.elf.cmd\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf.dSYM\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 Contents\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 Info.plist\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 Resources\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 DWARF\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky.elf\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf.lst\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 main.d\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 main.o\n \u2502\u00a0\u00a0 \u2514\u2500\u2500 main.o.cmd\n \u251c\u2500\u2500 hw\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 bsp\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 native\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hal_bsp.d\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2
500\u2500 hal_bsp.o\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hal_bsp.o.cmd snip",
+ "text": "A good build system must allow the user to take a few common steps while developing embedded applications: Generate full flash images Download debug images to a target board using a debugger Conditionally compile libraries code based upon build settings Newt can read a directory tree, build a dependency tree, and emit the right build artifacts. An example newt source tree is in incubator-mynewt-blinky/develop: $ tree -L 3 \n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\u2500\u2500 README.md \u251c\u2500\u2500 apps \u2502 \u2514\u2500\u2500 blinky\n\u2502 \u251c\u2500\u2500 pkg.yml\n\u2502 \u2514\u2500\u2500 src\n\u251c\u2500\u2500 project.yml \u2514\u2500\u2500 targets \u251c\u2500\u2500 my_blinky_sim\n \u2502 \u251c\u2500\u2500 pkg.yml\n \u2502 \u2514\u2500\u2500 target.yml\n \u2514\u2500\u2500 unittest\n \u251c\u2500\u2500 pkg.yml\n \u2514\u2500\u2500
target.yml\n\n6 directories, 10 files When Newt sees a directory tree that contains a \"project.yml\" file, it is smart enough to recognize it as the base directory of a project, and \nautomatically builds a package tree. It also recognizes two important package directories in the package tree - \"apps\" and \"targets\". More on these directories in Newt Theory of Ops . When Newt builds a target, it recursively resolves all package dependencies, and generates artifacts that are placed in the bin/targets/ target-name /app/apps/ app-name directory, where the bin directory is under the project base directory, target-name is the name of the target, and app-name is the name of the application. For our example my_blinky_sim is the name of the target and blinky is the name of the application. The blinky.elf executable is stored in the bin/targets/my_blinky_sim/app/apps/blinky directory as shown in the source tree: tree -L 6 bin/\nbin/\n\u2514\u2500\u2500 targets\n \u251
c\u2500\u2500 my_blinky_sim\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 app\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 apps\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 apps\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 apps_blinky.a\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 apps_blinky.a.cmd\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf.cmd\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf.dSYM\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf.lst\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500
\u2500 manifest.json\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hw\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 bsp\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 native\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 drivers\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 uart\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hal\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hw_hal.a\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hw_hal.a.cmd\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 repos snip",
"title": "Build System"
},
{
"location": "/newt/newt_intro/#more-operations-using-newt",
- "text": "Once a target has been built, Newt allows additional operations on the target. load : Download built target to board debug : Open debugger session to target size : Get size of target components create-image : Add image header to the binary image run : Build, create image, load, and finally open a debug session with the target For more details on how Newt works, go to Newt - Theory of Operations .",
+ "text": "Once a target has been built, Newt allows additional operations on the target. load : Download built target to board debug : Open debugger session to target size : Get size of target components create-image : Add image header to the binary image run : Build, create image, load, and finally open a debug session with the target target : Create, delete, configure, and query a target For more details on how Newt works, go to Newt - Theory of Operations .",
"title": "More operations using Newt"
},
{
"location": "/newt/newt_intro/#source-management-and-repositories",
- "text": "The other major element of the Newt tool is the ability to create reusable source distributions from a collection of code. A project can be a reusable container of source code. In other words, projects can be versioned and redistributed, not packages. A project bundles together packages that are typically needed to work together in a product e.g. RTOS core, filesystem APIs, and networking stack. A project that has been made redistributable is known as a repository . \nRepositories can be added to your local project by adding them into your project.yml file. Here is an example of the blinky project's yml file which relies on apache-mynewt-core: $ more project.yml snip \nproject.repositories:\n - apache-mynewt-core\n\n# Use github s distribution mechanism for core ASF libraries.\n# This provides mirroring automatically for us.\n#\nrepository.apache-mynewt-core:\n type: github\n vers: 0-latest\n user: apache\n repo: incubator-mynewt-core
When you specify this repository in the blinky's project file, you can then use the Newt tool to install dependencies: $ newt install\nDownloading repository description for apache-mynewt-core... success!\nDownloading repository incubator-mynewt-core (branch: develop) at \nhttps://github.com/apache/incubator-mynewt-core.git\nCloning into /var/folders/7l/7b3w9m4n2mg3sqmgw2q1b9p80000gn/T/newt-repo814721459 ...\nremote: Counting objects: 17601, done.\nremote: Compressing objects: 100% (300/300), done.\nremote: Total 17601 (delta 142), reused 0 (delta 0), pack-reused 17284\nReceiving objects: 100% (17601/17601), 6.09 MiB | 3.17 MiB/s, done.\nResolving deltas: 100% (10347/10347), done.\nChecking connectivity... done.\nRepos successfully installed Newt will install this repository in the /repos directory. In the case of blinky, the directory structure ends up looking like: $ tree -L 2\n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\
u2500\u2500 README.md\n\u251c\u2500\u2500 apps\n\u2502 \u2514\u2500\u2500 blinky\n\u251c\u2500\u2500 project.state\n\u251c\u2500\u2500 project.yml\n\u251c\u2500\u2500 repos\n\u2502 \u2514\u2500\u2500 apache-mynewt-core\n\u2514\u2500\u2500 targets\n \u251c\u2500\u2500 my_blinky_sim\n \u2514\u2500\u2500 unittest In order to reference the installed repositories in packages, the \"@\" notation should be specified in the repository specifier. As an example, the apps/blinky application has the following dependencies in its pkg.yml file. This tells the build system to look in the base directory of repos/apache-mynewt-core for the libs/os , hw/hal , and libs/console/full packages. $ more apps/blinky/pkg.yml snip \npkg.deps:\n - @apache-mynewt-core/libs/os \n - @apache-mynewt-core/hw/hal \n - @apache-mynewt-core/libs/console/full",
+ "text": "The other major element of the Newt tool is the ability to create reusable source distributions from a collection of code. A project can be a reusable container of source code. In other words, projects can be versioned and redistributed, not packages. A project bundles together packages that are typically needed to work together in a product e.g. RTOS core, filesystem APIs, and networking stack. A project that has been made redistributable is known as a repository . \nRepositories can be added to your local project by adding them into your project.yml file. Here is an example of the blinky project's yml file which relies on apache-mynewt-core: $ more project.yml snip \nproject.repositories:\n - apache-mynewt-core\n\n# Use github s distribution mechanism for core ASF libraries.\n# This provides mirroring automatically for us.\n#\nrepository.apache-mynewt-core:\n type: github\n vers: 0-latest\n user: apache\n repo: incubator-mynewt-core
When you specify this repository in the blinky's project file, you can then use the Newt tool to install dependencies: $ newt install\nDownloading repository description for apache-mynewt-core... success!\nDownloading repository incubator-mynewt-core (branch: develop) at \nhttps://github.com/apache/incubator-mynewt-core.git\nCloning into /var/folders/7l/7b3w9m4n2mg3sqmgw2q1b9p80000gn/T/newt-repo814721459 ...\nremote: Counting objects: 17601, done.\nremote: Compressing objects: 100% (300/300), done.\nremote: Total 17601 (delta 142), reused 0 (delta 0), pack-reused 17284\nReceiving objects: 100% (17601/17601), 6.09 MiB | 3.17 MiB/s, done.\nResolving deltas: 100% (10347/10347), done.\nChecking connectivity... done.\nRepos successfully installed Newt will install this repository in the /repos directory. In the case of blinky, the directory structure ends up looking like: $ tree -L 2\n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\
u2500\u2500 README.md\n\u251c\u2500\u2500 apps\n\u2502 \u2514\u2500\u2500 blinky\n\u251c\u2500\u2500 project.state\n\u251c\u2500\u2500 project.yml\n\u251c\u2500\u2500 repos\n\u2502 \u2514\u2500\u2500 apache-mynewt-core\n\u2514\u2500\u2500 targets\n \u251c\u2500\u2500 my_blinky_sim\n \u2514\u2500\u2500 unittest In order to reference the installed repositories in packages, the \"@\" notation should be specified in the repository specifier. As an example, the apps/blinky application has the following dependencies in its pkg.yml file. This tells the build system to look in the base directory of repos/apache-mynewt-core for the kernel/os , hw/hal , and sys/console/full packages. $ more apps/blinky/pkg.yml snip \npkg.deps:\n - @apache-mynewt-core/kernel/os \n - @apache-mynewt-core/hw/hal \n - @apache-mynewt-core/sys/console/full",
"title": "Source Management and Repositories"
},
{
@@ -10222,7 +10237,7 @@
},
{
"location": "/newt/newt_operation/",
- "text": "Newt Tool - Theory of Operations\n\n\nNewt has a fairly smart package manager that can read a directory tree, build a dependency tree, and emit the right build artifacts.\n\n\nBuilding dependencies\n\n\nNewt can read a directory tree, build a dependency tree, and emit the right build artifacts. An example newt source tree is in incubator-mynewt-blinky/develop:\n\n\n$ tree -L 3 \n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\u2500\u2500 README.md\n\n\u251c\u2500\u2500 apps\n\n\u2502 \u2514\u2500\u2500 blinky\n\u2502 \u251c\u2500\u2500 pkg.yml\n\u2502 \u2514\u2500\u2500 src\n\u251c\u2500\u2500 project.yml\n\n\u2514\u2500\u2500 targets\n\n \u251c\u2500\u2500 my_blinky_sim\n \u2502 \u251c\u2500\u2500 pkg.yml\n \u2502 \u2514\u2500\u2500 target.yml\n \u2514\u2500\u2500 unittest\n \u251c\u2500\u2500 pkg.yml\n \u2514\u2500\u2500 target.yml\n\n6 directories, 10 files\n\n\
n\n\n\n\n\nWhen newt sees a directory tree that contains a \"project.yml\" file it knows that it is in the base directory of a project, and automatically builds a package tree. You can see that there are two essential package directories, \"apps\" and \"targets.\" \n\n\n\n\n\"apps\" Package Directory\n\n\napps\n is where applications are stored, and applications are where the main() function is contained. The base project directory comes with one simple app called \nblinky\n in the \napps\n directory. The core repository \n@apache-mynewt-core\n comes with many additional sample apps in its \napps\n directory. At the time of this writing, there are several example BLE apps, the boot app, slinky app for using newt manager protocol, and more in that directory.\n\n\n@~/dev/myproj$ ls repos/apache-mynewt-core/apps/\nblecent bleprph_oic bleuart ffs2native slinky_oic test\nblehci bletest boot ocf_sample spitest timtest\nbleprph bletiny fat2native sl
inky splitty\n\n\n\n\n\nAlong with the \ntargets\n directory, \napps\n represents the top-level of the build tree for the particular project, and define the dependencies and features for the rest of the system. Mynewt users and developers can add their own apps to the project's \napps\n directory. \n\n\nThe app definition is contained in a \npkg.yml\n file. For example, blinky's \npkg.yml\n file is:\n\n\n$ more apps/blinky/pkg.yml\n\nsnip\n\npkg.name: apps/blinky\npkg.type: app\npkg.description: Basic example application which blinks an LED.\npkg.author: \nApache Mynewt \ndev@mynewt.incubator.apache.org\n\npkg.homepage: \nhttp://mynewt.apache.org/\n\npkg.keywords:\n\npkg.deps:\n - \n@apache-mynewt-core/kernel/os\n\n - \n@apache-mynewt-core/hw/hal\n\n - \n@apache-mynewt-core/sys/console/full\n\n\n\n\n\n\n\n\nThis file says that the name of the package is apps/blinky, and it \ndepends on kernel/os, hw/hal and sys/console/full packages.\n\n\nNOTE:\n @apache-mynewt-core
is a repository descriptor, and this will be \ncovered in the \"repository\" section. \n\n\n\n\n\"targets\" Package Directory\n\n\ntargets\n is where targets are stored, and each target is a collection of parameters that must be passed to newt in order to generate a reproducible build. Along with the \napps\n directory, \ntargets\n represents the top of the build tree. Any packages or parameters specified at the target level cascades down to all dependencies.\n\n\nMost targets consist of:\n\n\n\n\napp: The application to build\n\n\nbsp: The board support package to combine with that application\n\n\nbuild_profile: Either debug or optimized.\n\n\n\n\nThe \nmy_blinky_sim\n target that is included by default has the following settings:\n\n\n$ newt target show\ntargets/my_blinky_sim\n app=apps/blinky\n bsp=@apache-mynewt-core/hw/bsp/native\n build_profile=debug\n$ ls targets/my_blinky_sim/\npkg.yml target.yml\n\n\n\n\n\nThere are helper functions to aid the developer specif
y parameters for a target. \n\n\n\n\nvals\n: Displays all valid values for the specified parameter type (e.g. bsp for a target)\n\n\ntarget show\n: Displays the build artifacts for specified or all targets\n\n\n\n\nIn general, the three basic parameters of a target (\napp\n, \nbsp\n, and \nbuild_profile\n) are stored in the \ntarget.yml\n file in that target's build directory under \ntargets\n. You will also see a \npkg.yml\n file in the same directory. Since targets are packages, a \npkg.yml\n is expected. It contains typical package descriptors, dependencies, and additional parameters such as the following:\n\n\n\n\nCflags: Any additional compiler flags you might want to specify to the build\n\n\nAflags: Any additional assembler flags you might want to specify to the build\n\n\nLflags: Any additional linker flags you might want to specify to the build\n\n\n\n\n\n\nResolving dependencies\n\n\nWhen newt is told to build a project, it will:\n\n\n\n\nfind the top-level project.yml fil
e\n\n\nrecurse the packages in the package tree, and build a list of all \nsource packages\n\n\n\n\nNewt then looks at the target that the user set, for example, blinky_sim:\n\n\n$ more targets/my_blinky_sim/\npkg.yml target.yml\n$ more targets/my_blinky_sim/target.yml\n### Target: targets/my_blinky_sim\ntarget.app: \napps/blinky\n\ntarget.bsp: \n@apache-mynewt-core/hw/bsp/native\n\ntarget.build_profile: \ndebug\n\n\n\n\n\n\n\n\nThe target specifies two major things:\n\n\n\n\nApplication (target.app): The application to build\n\n\nBoard Support Package (target.bsp): The board support package to build \nalong with that application.\n\n\n\n\nNewt builds the dependency tree specified by all the packages. While building this tree, it does a few other things:\n\n\n\n\nSets up the include paths for each package. Any package that depends on another package, automatically gets the include directories from the package it includes. Include directories in the\nnewt structure must always b
e prefixed by the package name. For example, libs/os has the following include tree and its include directory files contains the package name \"os\" before any header files. This is so in order to avoid any header file conflicts.\n\n\n\n\n$ tree\n.\n\u251c\u2500\u2500 README.md\n\u251c\u2500\u2500 include\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 os\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 arch\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 cortex_m0\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 os\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 os_arch.h\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 cortex_m4\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 os\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 os_arch.h\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 sim\n\u2502\u00a0\u00a0 \u2502\
u00a0\u00a0 \u2514\u2500\u2500 os\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 os_arch.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 endian.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_callout.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_cfg.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_eventq.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_heap.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_malloc.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_mbuf.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_mempool.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_mutex.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_sanity.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_sched.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_sem.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_task.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_test.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_time.h\n\u2502\u00a0\u00a0 \
u2514\u2500\u2500 queue.h\n\u251c\u2500\u2500 pkg.yml\n\u2514\u2500\u2500 src\n \u251c\u2500\u2500 arch\n\nsnip\n\n\n\n\n\n\n\n\n\n\n\n\nValidates API requirements. Packages can export APIs they \nimplement, (i.e. pkg.api: hw-hal-impl), and other packages can require \nthose APIs (i.e. pkg.req_api: hw-hal-impl).\n\n\n\n\n\n\nReads and validates the configuration setting definitions and values from the package \nsyscfg.yml\n files.\nIt generates a \nsyscfg.h\n header file that packages include in the source files inorder to access the settings.\n\nIt also generates a system initialization function to initialize the packages.\nSee \nSystem Configuration And Initialization\n for more information.\n\n\n\n\n\n\nIn order to properly resolve all dependencies in the build system, newt recursively processes the package dependencies until there are no new dependencies or features (because features can add dependencies.) And it builds a big list of all the packages that need to be build.\
n\n\nNewt then goes through this package list, and builds every package into \nan archive file.\n\n\nNOTE:\n The newt tool generates compiler dependencies for all of these packages, and only rebuilds the packages whose dependencies have changed. Changes in package \n project dependencies are also taken into account. It is smart, after all!\n\n\nProducing artifacts\n\n\nOnce newt has built all the archive files, it then links the archive files together. The linkerscript to use is specified by the board support package (BSP.)\n\n\nNOTE: One common use of the \"features\" option above is to overwrite \nwhich linkerscript is used, based upon whether or not the BSP is being \nbuild for a raw image, bootable image or bootloader itself.\n\n\nThe newt tool places all of it's artifacts into the bin/ directory at \nthe top-level of the project, prefixed by the target name being built, \nfor example:\n\n\n$ tree -L 4 bin/\nbin/\n\u2514\u2500\u2500 my_blinky_sim\n \u251c\u2500\u2500 apps\n
\u2502 \u2514\u2500\u2500 blinky\n \u2502 \u251c\u2500\u2500 blinky.a\n \u2502 \u251c\u2500\u2500 blinky.a.cmd\n \u2502 \u251c\u2500\u2500 blinky.elf\n \u2502 \u251c\u2500\u2500 blinky.elf.cmd\n \u2502 \u251c\u2500\u2500 blinky.elf.dSYM\n \u2502 \u251c\u2500\u2500 blinky.elf.lst\n \u2502 \u251c\u2500\u2500 main.d\n \u2502 \u251c\u2500\u2500 main.o\n \u2502 \u2514\u2500\u2500 main.o.cmd\n \u251c\u2500\u2500 hw\n \u2502 \u251c\u2500\u2500 bsp\n \u2502 \u2502 \u2514\u2500\u2500 native\n \u2502 \u251c\u2500\u2500 hal\n \u2502 \u2502 \u251c\u2500\u2500 flash_map.d\n \u2502 \u2502 \u251c\u2500\u2500 flash_map.o\n\nsnip\n\n\n\n\n\n\n\n\nAs you can see, a number of files are generated:\n\n\n\n\nArchive File\n\n\n*.cmd: The command use to generate the object or archive file\n\n\n*.lst: The list file where symbols are located\n\n\n*.o The object files that g
et put into the archive file\n\n\n\n\nDownload/Debug Support\n\n\nOnce a target has been build, there are a number of helper functions \nthat work on the target. These are:\n\n\n\n\nload\n Download built target to board\n\n\ndebug\n Open debugger session to target\n\n\nsize\n Size of target components\n\n\ncreate-image\n Add image header to target binary\n\n\nrun\n The equivalent of build, create-image, load, and debug on specified target\n\n\n\n\nload\n and \ndebug\n handles driving GDB and the system debugger. These \ncommands call out to scripts that are defined by the BSP.\n\n\n$ more repos/apache-mynewt-core/hw/bsp/nrf52dk/nrf52dk_debug.sh\n\nsnip\n\n. $CORE_PATH/hw/scripts/jlink.sh\n\nFILE_NAME=$BIN_BASENAME.elf\n\nif [ $# -gt 2 ]; then\n SPLIT_ELF_NAME=$3.elf\n # TODO -- this magic number 0x42000 is the location of the second image\n # slot. we should either get this from a flash map file or somehow learn\n # this from the image itself\n
EXTRA_GDB_CMDS=\nadd-symbol-file $SPLIT_ELF_NAME 0x8000 -readnow\n\nfi\n\nJLINK_DEV=\nnRF52\n\n\njlink_debug\n\n\n\n\n\nThe idea is that every BSP will add support for the debugger environment \nfor that board. That way common tools can be used across various development boards and kits.",
+ "text": "Newt Tool - Theory of Operations\n\n\nNewt has a fairly smart package manager that can read a directory tree, build a dependency tree, and emit the right build artifacts.\n\n\nBuilding dependencies\n\n\nNewt can read a directory tree, build a dependency tree, and emit the right build artifacts. An example newt source tree is in incubator-mynewt-blinky/develop:\n\n\n$ tree -L 3 \n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\u2500\u2500 README.md\n\n\u251c\u2500\u2500 apps\n\n\u2502 \u2514\u2500\u2500 blinky\n\u2502 \u251c\u2500\u2500 pkg.yml\n\u2502 \u2514\u2500\u2500 src\n\u251c\u2500\u2500 project.yml\n\n\u2514\u2500\u2500 targets\n\n \u251c\u2500\u2500 my_blinky_sim\n \u2502 \u251c\u2500\u2500 pkg.yml\n \u2502 \u2514\u2500\u2500 target.yml\n \u2514\u2500\u2500 unittest\n \u251c\u2500\u2500 pkg.yml\n \u2514\u2500\u2500 target.yml\n\n6 directories, 10 files\n\n\
n\n\n\n\n\nWhen newt sees a directory tree that contains a \"project.yml\" file it knows that it is in the base directory of a project, and automatically builds a package tree. You can see that there are two essential package directories, \"apps\" and \"targets.\" \n\n\n\n\n\"apps\" Package Directory\n\n\napps\n is where applications are stored, and applications are where the main() function is contained. The base project directory comes with one simple app called \nblinky\n in the \napps\n directory. The core repository \n@apache-mynewt-core\n comes with many additional sample apps in its \napps\n directory. At the time of this writing, there are several example BLE apps, the boot app, slinky app for using newt manager protocol, and more in that directory.\n\n\n@~/dev/myproj$ ls repos/apache-mynewt-core/apps/\nblecent blesplit boot sensors_test splitty\nblehci bletest fat2native slinky test\nbleprph bletiny ffs2native slinky_oic testbench\
nbleprph_oic bleuart ocf_sample spitest timtest\n\n\n\n\n\nAlong with the \ntargets\n directory, \napps\n represents the top-level of the build tree for the particular project, and define the dependencies for the rest of the system. Mynewt users and developers can add their own apps to the project's \napps\n directory. \n\n\nThe app definition is contained in a \npkg.yml\n file. For example, blinky's \npkg.yml\n file is:\n\n\n$ more apps/blinky/pkg.yml\n\nsnip\n\npkg.name: apps/blinky\npkg.type: app\npkg.description: Basic example application which blinks an LED.\npkg.author: \nApache Mynewt \ndev@mynewt.incubator.apache.org\n\npkg.homepage: \nhttp://mynewt.apache.org/\n\npkg.keywords:\n\npkg.deps:\n - \n@apache-mynewt-core/kernel/os\n\n - \n@apache-mynewt-core/hw/hal\n\n - \n@apache-mynewt-core/sys/console/full\n\n\n\n\n\n\n\n\nThis file says that the name of the package is apps/blinky, and it depends on the \nkernel/os,\nhw/hal\nand\nsys/console/full` packages.
\n\n\nNOTE:\n @apache-mynewt-core is a repository descriptor, and this will be \ncovered in the \"repository\" section. \n\n\n\n\n\"targets\" Package Directory\n\n\ntargets\n is where targets are stored, and each target is a collection of parameters that must be passed to newt in order to generate a reproducible build. Along with the \napps\n directory, \ntargets\n represents the top of the build tree. Any packages or parameters specified at the target level cascades down to all dependencies.\n\n\nMost targets consist of:\n\n\n\n\napp: The application to build\n\n\nbsp: The board support package to combine with that application\n\n\nbuild_profile: Either debug or optimized.\n\n\n\n\nThe \nmy_blinky_sim\n target that is included by default has the following settings:\n\n\n$ newt target show\ntargets/my_blinky_sim\n app=apps/blinky\n bsp=@apache-mynewt-core/hw/bsp/native\n build_profile=debug\n$ ls targets/my_blinky_sim/\npkg.yml target.yml\n\n\n\n\n\nThere are helper fun
ctions to aid the developer specify parameters for a target. \n\n\n\n\nvals\n: Displays all valid values for the specified parameter type (e.g. bsp for a target)\n\n\ntarget show\n: Displays the variable values for either a specific target or all targets defined for the project\n\n\ntarget set\n: Sets values for target variables\n\n\n\n\nIn general, the three basic parameters of a target (\napp\n, \nbsp\n, and \nbuild_profile\n) are stored in the target's \ntarget.yml\n file in the targets/\ntarget-name\n directory, where \ntarget-name\n is the name of the target. You will also see a \npkg.yml\n file in the same directory. Since targets are packages, a \npkg.yml\n is expected. It contains typical package descriptors, dependencies, and additional parameters such as the following:\n\n\n\n\nCflags: Any additional compiler flags you might want to specify to the build\n\n\nAflags: Any additional assembler flags you might want to specify to the build\n\n\nLflags: Any additional linker fla
gs you might want to specify to the build\n\n\n\n\nYou can also override the values of the system configuration settings that are defined by the packages that your target includes. You override the values in your target's \nsyscfg.yml\n file (stored in the targets/\ntarget-name\n directory). You can use the \nnewt target config show\n command to see the configuration settings and values for your target, and use the \nnewt target set\n command to set the \nsyscfg\n variable and override the configuration setting values. You can also use an editor to create your target's \nsyscfg.yml\n file and add the setting values to the file. See \nSystem Configuration And Initialization\n for more information on system configuration settings.\n\n\n\n\nResolving dependencies\n\n\nWhen newt builds a project, it will:\n\n\n\n\nfind the top-level project.yml file\n\n\nrecurse the packages in the package tree, and build a list of all \nsource packages\n\n\n\n\nNewt then looks at the target that the
user set, for example, blinky_sim:\n\n\n$ more targets/my_blinky_sim/\npkg.yml target.yml\n$ more targets/my_blinky_sim/target.yml\n### Target: targets/my_blinky_sim\ntarget.app: \napps/blinky\n\ntarget.bsp: \n@apache-mynewt-core/hw/bsp/native\n\ntarget.build_profile: \ndebug\n\n\n\n\n\n\n\n\nThe target specifies two major things:\n\n\n\n\nApplication (target.app): The application to build\n\n\nBoard Support Package (target.bsp): The board support package to build \nalong with that application.\n\n\n\n\nNewt builds the dependency tree specified by all the packages. While building this tree, it does a few other things:\n\n\n\n\nSets up the include paths for each package. Any package that depends on another package, automatically gets the include directories from the package it includes. Include directories in the\nnewt structure must always be prefixed by the package name. For example, kernel/os has the following include tree and its include directory files contains the package
name \"os\" before any header files. This is so in order to avoid any header file conflicts.\n\n\n\n\n$tree kernel/os/include\nkernel/os/include\n\u2514\u2500\u2500 os\n \u251c\u2500\u2500 arch\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 cortex_m0\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 os\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 os_arch.h\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 cortex_m4\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 os\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 os_arch.h\n \u2502\u00a0\u00a0 \u251c\u2500\u2500
<TRUNCATED>
[4/7] incubator-mynewt-site git commit: Update newt command
documentation, sysconfig overwrites, events, bsp list
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/command_list/newt_sync/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/command_list/newt_sync/index.html b/develop/newt/command_list/newt_sync/index.html
new file mode 100644
index 0000000..fd21b3e
--- /dev/null
+++ b/develop/newt/command_list/newt_sync/index.html
@@ -0,0 +1,584 @@
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <meta charset="utf-8">
+ <meta http-equiv="X-UA-Compatible" content="IE=edge">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+
+ <!-- This is broken by doc revisioning.
+ <link rel="canonical" href="http://mynewt.apache.org/newt/command_list/newt_sync/"> -->
+ <link rel="shortcut icon" href="../../../img/favicon.ico">
+
+ <title>newt sync - Apache Mynewt</title>
+
+ <link href="../../../css/bootstrap-3.0.3.min.css" rel="stylesheet">
+ <link rel="stylesheet" href="../../../css/highlight.css">
+ <link href="../../../css/base.css" rel="stylesheet">
+ <link href="../../../css/custom.css" rel="stylesheet">
+ <link href="../../../css/v2.css" rel="stylesheet">
+ <link href="https://fonts.googleapis.com/css?family=Lato" rel="stylesheet">
+ <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css">
+ <link href="../../../extra.css" rel="stylesheet">
+
+ <!-- HTML5 shim and Respond.js IE8 support of HTML5 elements and media queries -->
+ <!--[if lt IE 9]>
+ <script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script>
+ <script src="https://oss.maxcdn.com/libs/respond.js/1.3.0/respond.min.js"></script>
+ <![endif]-->
+
+
+ <script>
+ (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
+ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
+ m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
+ })(window,document,'script','//www.google-analytics.com/analytics.js','ga');
+
+ ga('create', 'UA-72162311-1', 'auto');
+ ga('send', 'pageview');
+ </script>
+
+ </head>
+
+
+ <body class="newt sync">
+
+
+ <div class="container">
+ <div class="row v2-main-banner">
+ <a class="logo-cell" href="/">
+ <img class="logo" src="/img/logo.png">
+ </a>
+ <div class="tagline-cell">
+ <h4 class="tagline">An OS to build, deploy and securely manage billions of devices</h4>
+ </div>
+ <div class="news-cell">
+ <div class="well">
+ <h4>Latest News:</h4> <a href="/download">Apache Mynewt 1.0.0-b2</a> released (Feb 15, 2017)
+ </div>
+ </div>
+ </div>
+</div>
+
+
+
+
+
+
+
+
+<nav id="navbar" class="navbar navbar-inverse affix-top" data-spy="affix" data-offset-top="150" role="navigation">
+ <div class="container">
+ <!-- Collapsed navigation -->
+ <div class="navbar-header">
+ <!-- Expander button -->
+ <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
+ <span class="sr-only">Toggle navigation</span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ </button>
+
+ </div>
+
+ <!-- Expanded navigation -->
+ <div class="navbar-collapse collapse">
+ <!-- Main navigation -->
+ <ul class="nav navbar-nav navbar-right">
+ <li
+ class=""
+>
+ <a href="/"><i class="fa fa-home" style="font-size: larger;"></i></a>
+ </li>
+ <li
+ class="important"
+>
+ <a href="/quick-start/">Quick Start</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/about/">About</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/talks/">Talks</a>
+ </li>
+ <li
+ class="active"
+>
+ <a href="/latest/os/introduction">Documentation</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/download/">Download</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/community/">Community</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/events/">Events</a>
+ </li>
+ </ul>
+
+ <!-- Search, Navigation and Repo links -->
+ <ul class="nav navbar-nav navbar-right">
+
+ </ul>
+ </div>
+ </div>
+</nav>
+
+
+
+ <div class="container">
+
+ <div class="row">
+ <div class="col-md-3 v2-sidebar sidebar-container"><div id="docSidebar" class="hidden-print" role="complementary">
+ <div class="top">
+ <div role="search">
+ <form id="rtd-search-form" class="wy-form" action="../../../search.html" method="get">
+ <div class="form-group">
+ <input type="text" name="q" class="form-control" placeholder="Search documentation" />
+ </div>
+ </form>
+ </div>
+ </div>
+ <ul class="toc-nav">
+ <li class="doc-version">
+<select class="form-control" onchange="if (this.value) window.location.href=this.value">
+
+ <option
+ value="/develop/os/introduction"
+ selected="selected"
+ >
+ Version: develop (latest)
+ </option>
+
+ <option
+ value="/v0_9_0/os/introduction"
+
+ >
+ Version: 0.9.0
+ </option>
+
+</select>
+</li>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ <li ><a href="../../../os/introduction/">Mynewt Documentation</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../../../os/get_started/get_started/">Basic Setup</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../../os/get_started/vocabulary/">Concepts</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../os/tutorials/tutorials/">Tutorials</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../os/os_user_guide/">OS User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../../network/ble/ble_intro/
+">BLE User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../newt_intro/">Newt Tool Guide</a>
+
+
+ <ul>
+
+
+
+
+
+ <li >
+ <a href="../../newt_operation/">Newt Theory of Ops</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../newt_ops/">Command Guide</a>
+
+
+ <ul>
+
+
+
+
+
+ <li >
+ <a href="../newt_build/">newt build</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_clean/">newt clean</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_create_image/">newt create-image</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_debug/">newt debug</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_help/">newt help</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_info/">newt info</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_install/">newt install</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_load/">newt load</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_mfg/">newt mfg</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_new/">newt new</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_run/">newt run</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_size/">newt size</a>
+ </li>
+
+
+
+
+
+ <li class="active">
+ <a href="./">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_target/">newt target</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_test/">newt test</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_upgrade/">newt upgrade</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_vals/">newt vals</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_version/">newt version</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../newtmgr/overview/">Newt Manager Guide</a>
+
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../../faq/how_to_edit_docs/
+">Appendix</a>
+
+
+ </li>
+
+
+
+ </ul>
+</div></div>
+
+ <div class="col-md-9" role="main">
+ <div class="doc-header">
+ <div role="navigation" aria-label="breadcrumbs navigation">
+ <ul class="wy-breadcrumbs pull-right">
+ <li><a href="/develop/os/introduction">Docs</a></li>
+
+
+
+ <li>» <a href="../../newt_intro/">Newt Tool Guide</a></li>
+
+
+
+ <li>» <a href="../../newt_ops/">Command Guide</a></li>
+
+
+
+ <li>» newt sync</li>
+
+
+
+ </ul>
+</div>
+ </div>
+
+ <h2 id="newt-sync"><font color="#F2853F" style="font-size:24pt">newt sync </font></h2>
+<p>Synchronize and refresh the contents of the local copy of all the repositories used in the project with the latest updates maintained in the remote repositories. </p>
+<h4 id="usage">Usage:</h4>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt sync [flags]
+</pre></div>
+
+
+<h4 id="flags">Flags:</h4>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -f, --force Force overwrite of existing remote repository
+
+#### Global Flags:
+```no-highlight
+ -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
+</pre></div>
+
+
+<h4 id="description">Description</h4>
+<p>Synchronize project dependencies and repositories. Prior to 1.0.0 release, the command deletes and resynchronizes each repository. Post 1.0.0, it will abort the synchronization if there are any local changes to any repository. Using the -f to force overwrite of existing repository will stash and save the changes while pulling in all the latest changes from the remote repository. </p>
+
+ <div class="row">
+
+
+
+
+<ul class="nav nav-pills" style="margin-bottom: 10px">
+ <li>
+
+ <a href=../newt_size/>
+ <span class="fa fa-arrow-left"></span>
+ Previous: newt size
+ </a>
+
+ </li>
+ <li class="pull-right">
+
+ <a href=../newt_target/>
+ Next: newt target
+ <span class="fa fa-arrow-right"></span>
+ </a>
+
+ </li>
+</ul>
+ </div>
+ <footer class="row">
+ <div class="col-xs-12">
+
+ <p class="copyright">Apache Mynewt (incubating) is available under Apache License, version 2.0.</p>
+
+ </div>
+ <div class="col-xs-12">
+ <div class="logos">
+ <img src="/img/asf_logo_wide_small.png" alt="Apache" title="Apache">
+ <small class="footnote">
+ MyNewt is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
+ </small>
+ <img src="/img/egg-logo2.png" alt="Apache Incubator" title="Apache Incubator">
+ </div>
+ </div>
+</footer>
+ </div>
+ </div>
+
+
+ </div>
+
+ <script src="../../../js/jquery-1.10.2.min.js"></script>
+ <script src="../../../js/bootstrap-3.0.3.min.js"></script>
+ <script src="../../../js/highlight.pack.js"></script>
+ <script src="../../../js/base.js"></script>
+ <script src="../../../js/custom.js"></script>
+
+ </body>
+</html>
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/command_list/newt_target/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/command_list/newt_target/index.html b/develop/newt/command_list/newt_target/index.html
index ad858a5..f06110d 100644
--- a/develop/newt/command_list/newt_target/index.html
+++ b/develop/newt/command_list/newt_target/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -388,6 +388,14 @@
+ <li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
<li class="active">
<a href="./">newt target</a>
</li>
@@ -496,14 +504,14 @@
</div>
<h2 id="newt-target"><font color="#F2853F" style="font-size:24pt">newt target </font></h2>
-<p>Provides commands to create, build, delete, and query targets. </p>
+<p>Commands to create, delete, configure and query targets. </p>
<h4 id="usage">Usage:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt target [command] input1 [input2]
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt target [command] [flags]
</pre></div>
<h4 id="available-commands">Available Commands:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> config View target system configuration
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> config View or populate a target's system configuration settings
copy Copy target
create Create a target
delete Delete target
@@ -514,21 +522,19 @@
</pre></div>
-<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for target
-</pre></div>
-
-
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -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.
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
</pre></div>
<h4 id="description">Description</h4>
+<p>The target command provides subcommands to create, build, delete, and query targets. The subcommands take one or two <code>target-name</code> arguments. </p>
<table>
<thead>
<tr>
@@ -539,43 +545,35 @@
<tbody>
<tr>
<td>config</td>
-<td>Displays the specified target's system configuration. The configuration for any package is listed in its <code>syscfg.yml</code> file. A target build consists of several packages. The command lists the settings for the config variables from all the included packages. If the default values have not been changed then the default values will be seen.</td>
+<td>The config command allows you to view or populate a target's system configuration settings. A target's system configuration settings include the settings of all the packages it includes. The settings for a package are listed in the package's <code>syscfg.yml</code> file. The <code>config</code> command has two subcommands: <code>show</code> and <code>init</code>. <br><br> The config show <target-name> command displays the system configuration setting definitions and values for all the packages that the <code>target-name</code> target includes. <br><br>The config init <target-name> command populates the target's <code>syscfg.yml</code> file with the system configuration values for all the packages that the <code>target-name</code> target includes.</td>
</tr>
<tr>
<td>copy</td>
-<td>Set variables (attributes) of the target named via <code>input1</code>. Currently the list of possible attributes (variables) are:<code>app</code>, <code>bsp</code>, <code>build_profile</code>, <code>cflags</code>, <code>lflags</code>. For a simulated target, e.g. for software testing purposes, <code>bsp</code> is set to <code>@apache-mynewt-core/hw/bsp/native</code>.</td>
+<td>The copy <src-target> <dst-target> command creates a new target named <code>dst-target</code> by cloning the <code>src-target</code> target.</td>
</tr>
<tr>
<td>create</td>
-<td>Creates an empty target definition by the name of <code>input1</code>.</td>
+<td>The create <target-name> command creates an empty target named <code>target-name</code>. It creates the <code>targets/target-name</code> directory and the skeleton <code>pkg.yml</code> and <code>target.yml</code> files in the directory.</td>
</tr>
<tr>
<td>delete</td>
-<td>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<code>newt clean <target-name></code> <strong>before</strong> deleting the target!</td>
+<td>The delete <target-name> command deletes the description for the <code>target-name</code> target. It deletes the 'targets/target-name' directory. It does not delete the 'bin/targets/target-name' directory where the build artifacts are stored. If you want to delete the build artifacts, run the <code>newt clean <target-name></code> command <strong>before</strong> deleting the target.</td>
</tr>
<tr>
<td>dep</td>
-<td>Creates dependency tree for packages in the code for a target. Display shows each package followed by the list of libraries or packages that it depends on.</td>
+<td>The dep <target-name> command displays a dependency tree for the packages that the <code>target-name</code> target includes. It shows each package followed by the list of libraries or packages that it depends on.</td>
</tr>
<tr>
<td>revdep</td>
-<td>Creates the reverse dependency tree for packages in the code for a target. Display shows each package followed by the list of libraries or packages that depend on it.</td>
+<td>The revdep <target-name> command displays the reverse dependency tree for the packages that the <code>target-name</code> target includes. It shows each package followed by the list of libraries or packages that depend on it.</td>
</tr>
<tr>
<td>set</td>
-<td>Set variables (attributes) of the target named via <code>input1</code>. Currently the list of possible attributes (variables) are:<code>app</code>, <code>bsp</code>, <code>build_profile</code>, <code>features</code>, <code>cflags</code>, <code>lflags</code>. For a simulated target, e.g. for software testing purposes, <code>bsp</code> is set to <code>@apache-mynewt-core/hw/bsp/native</code>.</td>
-</tr>
-<tr>
-<td></td>
-<td>To display all the existing values for a target variable (attribute), you can issue a <code>newt vals <variable-name></code> command. For example, <code>newt vals app</code> displays the valid values available for the variable <code>app</code> for any target.</td>
-</tr>
-<tr>
-<td></td>
-<td>Currently, the only two values available for <code>build_profile</code> are <code>optimized</code> and <code>debug</code>.</td>
+<td>The set <target-name> <var-name=var-value> [var-name=var-value...] command sets variables (attributes) for the <target-name> target. The set command overwrites your current variable values. <br><br>The valid <code>var-name</code> values are: <code>app</code>, <code>bsp</code>, <code>loader</code>, <code>build_profile</code>, <code>cflags</code>, <code>lflags</code>, <code>aflags</code>, <code>syscfg</code>. <br><br>The <code>var-value</code> format depends on the <code>var-name</code> as follows: <ul><li><code>app</code>, <code>bsp</code>, <code>loader</code>: @<source-path>, where <code>source-path</code> is the directory containing the application or bsp source. These variables are stored in the target's target.yml file. For a simulated target, e.g. for software testing purposes, set <code>bsp</code> to <code>@apache-mynewt-core/hw/bsp/native</code>.</li> <li><code>build_profile</code>: <code>optimized</code> or <code>debug</code></li><li><code>cflags
</code>, <code>aflags</code>, <code>lflags</code>: A string of flags, with each flag separated by a space. These variables are saved in the target's <code>pkg.yml</code> file. </li><li><code>syscfg</code>: The <code>syscfg</code> variable allows you to assign values to configuration settings in your target's <code>syscfg.yml</code> file. <br>The format is <code>syscfg=setting-name1=setting-value1[:setting-name2=setting-value2...]</code>, where <code>setting-name1</code> is a configuration setting name and <code>setting-value1</code> is the value to assign to <code>settingname1</code>. If <code>settingvalue1</code> is not specified, the setting is set to value <code>1</code>. You use a <code>:</code> to delimit each setting when you set multiple settings. <br><strong>Warning</strong>: All existing setting values in the <code>syscfg.yml</code> file are deleted. Only new settings that are specified in the command are saved in the <code>syscfg.yml</code> file.</li></ul> You can spec
ify <code>var-name=</code> or <code>var-name=""</code> to unset a variable value.<br><br>To display all the existing values for a target variable (attribute), you can run the <code>newt vals <variable-name></code> command. For example, <code>newt vals app</code> displays the valid values available for the variable <code>app</code> for any target.</td>
</tr>
<tr>
<td>show</td>
-<td>Shows what variables (attributes) are set on the specified target <code>input1</code>. If no <code>input1</code> is specified then show the configuration for all the targets defined so far.</td>
+<td>The show [target-name] command shows the values of the variables (attributes) for the <code>target-name</code> target. When <code>target-name</code> is not specified, the command shows the variables for all the targets that are defined for your project.</td>
</tr>
</tbody>
</table>
@@ -590,34 +588,69 @@
</thead>
<tbody>
<tr>
-<td>config</td>
-<td>newt target config rb_blinky</td>
-<td>Shows all the system configuration settings for all the packages in the target named <code>rb_blinky</code>.</td>
+<td>config show</td>
+<td>newt target config show rb_blinky</td>
+<td>Shows the system configuration settings for all the packages that the <code>rb_blinky</code> target includes.</td>
+</tr>
+<tr>
+<td>config init</td>
+<td>newt target config init my_blinky</td>
+<td>Creates and populates the <code>my_blinky</code> target's <code>syscfg.yml</code> file with the system configuration setting values from all the packages that the <code>my_blinky</code> target includes.</td>
</tr>
<tr>
<td>copy</td>
-<td>newt target copy rb_blinky rb_bletiny</td>
-<td>Clones the target settings in <code>rb_blinky</code> to the destination target <code>rb_bletiny</code></td>
+<td>newt target copy <br>rb_blinky rb_bletiny</td>
+<td>Creates the <code>rb_bletiny</code> target by cloning the <code>rb_blinky</code> target.</td>
</tr>
<tr>
<td>create</td>
-<td>newt target create target1</td>
-<td>Creates an empty target by the name <code>target1</code></td>
+<td>newt target create <br>my_new_target</td>
+<td>Creates the <code>my_newt_target</code> target. It creates the <code>targets/my_new_target</code> directory and creates the skeleton <code>pkg.yml</code> and <code>target.yml</code> files in the directory.</td>
+</tr>
+<tr>
+<td>delete</td>
+<td>newt target delete rb_bletiny</td>
+<td>Deletes the <code>rb_bletiny</code> target. It deletes the <code>targets/rb_bletiny</code> directory.</td>
+</tr>
+<tr>
+<td>dep</td>
+<td>newt target dep myble</td>
+<td>Displays the dependency tree of all the package dependencies for the <code>myble</code> target. It lists each package followed by a list of packages it depends on.</td>
+</tr>
+<tr>
+<td>revdep</td>
+<td>newt target revdep myble</td>
+<td>Displays the reverse dependency tree of all the package dependencies for the <code>myble</code> target. It lists each package followed by a list of packages that depend on it.</td>
+</tr>
+<tr>
+<td>set</td>
+<td>newt target set myble <br>app=@apache-mynewt-core/apps/bletiny</td>
+<td>Use <code>bletiny</code> as the application to build for the <code>myble</code> target.</td>
+</tr>
+<tr>
+<td>set</td>
+<td>newt target set myble <br>cflags="-DNDEBUG -Werror"</td>
+<td>Set <code>pkg.cflags</code> variable with <code>-DNDEBUG -Werror</code> in the <code>myble</code> target's <code>pkg.yml</code> file..</td>
+</tr>
+<tr>
+<td>set</td>
+<td>newt target set myble syscfg=LOG_NEWTMGR=0:CONFIG_NEWTMGR</td>
+<td>Sets the <code>syscfg.vals</code> variable in the <code>myble</code> target's <code>syscfg.yml</code> file with the setting values: LOG_NEWTMGR: 0 and CONFIG_NEWTMGR: 1. CONFIG_NEWTMGR is set to 1 because a value is not specified.</td>
+</tr>
+<tr>
+<td>set</td>
+<td>newt target set myble cflags=</td>
+<td>Unsets the <code>pkg.cflags</code> variable in the <code>myble</code> target's <code>pkg.yml</code> file.</td>
</tr>
<tr>
<td>show</td>
<td>newt target show myble</td>
-<td>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.</td>
+<td>Shows all variable settings for the <code>myble</code> target, i.e. the values that app, bsp, build_profile, cflags, aflags, ldflags, syscfg variables are set to. Note that not all variables have to be set for a target.</td>
</tr>
<tr>
<td>show</td>
<td>newt target show</td>
-<td>Shows all variable settings for all the targets defined.</td>
-</tr>
-<tr>
-<td>set</td>
-<td>newt target set myble app=@apache-mynewt-core/apps/bletiny</td>
-<td>Assign <code>bletiny</code> to be the application to be included in the build for the target named <code>myble</code>.</td>
+<td>Shows all the variable settings for all the targets defined for the project.</td>
</tr>
</tbody>
</table>
@@ -630,9 +663,9 @@
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../newt_size/>
+ <a href=../newt_sync/>
<span class="fa fa-arrow-left"></span>
- Previous: newt size
+ Previous: newt sync
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/command_list/newt_test/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/command_list/newt_test/index.html b/develop/newt/command_list/newt_test/index.html
index 9e2c35f..20c6c2d 100644
--- a/develop/newt/command_list/newt_test/index.html
+++ b/develop/newt/command_list/newt_test/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,41 +504,30 @@
</div>
<h2 id="newt-test"><font color="#F2853F" style="font-size:24pt">newt test </font></h2>
-<p>Executes unit tests for one or more packages </p>
+<p>Execute unit tests for one or more packages. </p>
<h4 id="usage">Usage:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt test [flags] input1 [input2] ...
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt test <package-name> [package-names...] | all [flags]
</pre></div>
<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for target
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -e, --exclude string Comma separated list of packages to exclude
</pre></div>
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -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.
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
</pre></div>
<h4 id="description">Description</h4>
-<table>
-<thead>
-<tr>
-<th>Sub-command</th>
-<th>Explanation</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>test</td>
-<td>Test a pkg named <code>input1</code>. You may specify multiple packages separated by space in the same command.</td>
-</tr>
-</tbody>
-</table>
+<p>Executes unit tests for one or more packages. You specify a list of packages, separated by space, to test multiple packages in the same command, or specify <code>all</code> to test all packages. When you use the <code>all</code> option, you may use the <code>-e</code> flag followed by a comma separated list of packages to exclude from the test.</p>
<h4 id="examples">Examples</h4>
<table>
<thead>
@@ -542,19 +539,24 @@
</thead>
<tbody>
<tr>
-<td>test</td>
-<td>newt test targets/myble2</td>
-<td>Tests the pkg named 'targets/myble2'</td>
+<td></td>
+<td>newt test <br>@apache-mynewt-core/kernel/os</td>
+<td>Tests the <code>kernel/os</code> package in the <code>apache-mynewt-core</code> repository.</td>
+</tr>
+<tr>
+<td></td>
+<td>newt test kernel/os encoding/json</td>
+<td>Tests the <code>kernel/os</code> and <code>encoding/json</code> packages in the current repository.</td>
</tr>
<tr>
<td></td>
-<td>newt test @apache-mynewt-core/libs/os</td>
-<td>Tests the libs/os pkg in the repo named apache-mynewt-core</td>
+<td>newt test all</td>
+<td>Tests all packages.</td>
</tr>
<tr>
<td></td>
-<td>newt test libs/os libs/json</td>
-<td>Tests the <code>libs/os</code> and <code>libs/json packages</code> in the current repo. Should indicate at the end of the output: <br> <code>Passed tests: [libs/os libs/json]</code> <br> <code>All tests passed</code></td>
+<td>newt test all -e net/oic,encoding/json</td>
+<td>Tests all packages except for the <code>net/oic</code> and the <code>encoding/json</code> packages.</td>
</tr>
</tbody>
</table>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/command_list/newt_upgrade/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/command_list/newt_upgrade/index.html b/develop/newt/command_list/newt_upgrade/index.html
index 6648664..984c4e3 100644
--- a/develop/newt/command_list/newt_upgrade/index.html
+++ b/develop/newt/command_list/newt_upgrade/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,40 +504,30 @@
</div>
<h2 id="newt-upgrade"><font color="#F2853F" style="font-size:24pt">newt upgrade </font></h2>
-<p>Upgrade project dependencies</p>
+<p>Upgrade project dependencies.</p>
<h4 id="usage">Usage:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt pkg [command][flag] input1 input2
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt upgrade [flags]
</pre></div>
<h4 id="flags">Flags:</h4>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -f, --force Force upgrade of the repositories to latest state in project.yml
+</pre></div>
-#### 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.
+<h4 id="global-flags">Global Flags:</h4>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
</pre></div>
<h4 id="description">Description</h4>
-<table>
-<thead>
-<tr>
-<th>Sub-command</th>
-<th>Explanation</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>upgrade</td>
-<td>If you have changed the project.yml description for the project, you need to run this command to update all the package dependencies.</td>
-</tr>
-</tbody>
-</table>
+<p>Upagrades your project and package dependencies. If you have changed the project.yml description for the project, you need to run this command to update all the package dependencies. </p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/command_list/newt_vals/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/command_list/newt_vals/index.html b/develop/newt/command_list/newt_vals/index.html
index ea9da76..9f4d479 100644
--- a/develop/newt/command_list/newt_vals/index.html
+++ b/develop/newt/command_list/newt_vals/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,37 +504,35 @@
</div>
<h2 id="newt-vals"><font color="#F2853F" style="font-size:24pt">newt vals </font></h2>
-<p>Displays valid values for the specified element type(s). Appropriate values must be chosen and assigned to one or more elements when defining a package or target. Element types currently available are the following:</p>
+<p>Display valid values for the specified element type(s).</p>
+<h4 id="usage">Usage:</h4>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt vals <element-type> [element-types...] [flags]
+</pre></div>
+
+
+<h4 id="global-flags">Global Flags:</h4>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
+</pre></div>
+
+
+<h4 id="description">Description</h4>
+<p>Displays valid values for the specified element type(s). You must set valid values for one or more elements when you define a package or a target. Valid element types are:</p>
<ul>
<li>api</li>
<li>app</li>
<li>bsp</li>
<li>build_profile</li>
<li>compiler</li>
-<li>feature</li>
<li>lib</li>
<li>sdk</li>
<li>target</li>
</ul>
-<h4 id="usage">Usage:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt vals <element-type> [element-types...] [flags]
-</pre></div>
-
-
-<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for target
-</pre></div>
-
-
-<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -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.
-</pre></div>
-
-
<h4 id="examples">Examples</h4>
<table>
<thead>
@@ -538,7 +544,7 @@
</thead>
<tbody>
<tr>
-<td>vals</td>
+<td></td>
<td>newt vals api</td>
<td>Shows the possible values for APIs a package may specify as required. For example, the <code>pkg.yml</code> for <code>adc</code> specifies that it requires the api named <code>ADC_HW_IMPL</code>, one of the values listed by the command.</td>
</tr>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/command_list/newt_version/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/command_list/newt_version/index.html b/develop/newt/command_list/newt_version/index.html
index c20c421..d546422 100644
--- a/develop/newt/command_list/newt_version/index.html
+++ b/develop/newt/command_list/newt_version/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,23 +504,20 @@
</div>
<h2 id="newt-version"><font color="#F2853F" style="font-size:24pt">newt version </font></h2>
-<p>Allows you to query the version of newt installed in your application space.</p>
+<p>Display the version of the newt tool you have installed</p>
<h4 id="usage">Usage:</h4>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt version [flags]
</pre></div>
-<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for version
-</pre></div>
-
-
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -l, --loglevel string Log level, defaults to WARN. (default "WARN")
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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.
+ -q, --quiet Be quiet; only display error output
+ -s, --silent Be silent; don't output anything
+ -v, --verbose Enable verbose output when executing commands
</pre></div>
@@ -527,9 +532,9 @@
</thead>
<tbody>
<tr>
-<td>version</td>
+<td></td>
<td>newt version</td>
-<td>Displays the version of newt tool installed</td>
+<td>Displays the version of the newt tool you have installed</td>
</tr>
</tbody>
</table>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/newt_intro/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/newt_intro/index.html b/develop/newt/newt_intro/index.html
index 6d82b45..31db5d4 100644
--- a/develop/newt/newt_intro/index.html
+++ b/develop/newt/newt_intro/index.html
@@ -395,32 +395,32 @@ systems with a make system built for embedded systems and create Newt.</p>
<p><br></p>
<p>When Newt sees a directory tree that contains a "project.yml" file, it is smart enough to recognize it as the base directory of a project, and
automatically builds a package tree. It also recognizes two important package directories in the package tree - "apps" and "targets". More on these directories in <a href="../newt_operation/">Newt Theory of Ops</a>.</p>
-<p>When Newt is told to build a project, it recursively resolves all package dependencies and generates artifacts that are placed in the bin/ directory at the top-level of the project. The artifact directory is prefixed by the target name being built - <code>my_blinky_sim</code> for example:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ tree bin
-bin
-\u2514\u2500\u2500 my_blinky_sim
- \u251c\u2500\u2500 apps
- \u2502�� \u2514\u2500\u2500 blinky
- \u2502�� \u251c\u2500\u2500 blinky.a
- \u2502�� \u251c\u2500\u2500 blinky.a.cmd
- \u2502�� \u251c\u2500\u2500 blinky.elf
- \u2502�� \u251c\u2500\u2500 blinky.elf.cmd
- \u2502�� \u251c\u2500\u2500 blinky.elf.dSYM
- \u2502�� \u2502�� \u2514\u2500\u2500 Contents
- \u2502�� \u2502�� \u251c\u2500\u2500 Info.plist
- \u2502�� \u2502�� \u2514\u2500\u2500 Resources
- \u2502�� \u2502�� \u2514\u2500\u2500 DWARF
- \u2502�� \u2502�� \u2514\u2500\u2500 blinky.elf
- \u2502�� \u251c\u2500\u2500 blinky.elf.lst
- \u2502�� \u251c\u2500\u2500 main.d
- \u2502�� \u251c\u2500\u2500 main.o
- \u2502�� \u2514\u2500\u2500 main.o.cmd
- \u251c\u2500\u2500 hw
- \u2502�� \u251c\u2500\u2500 bsp
- \u2502�� \u2502�� \u2514\u2500\u2500 native
- \u2502�� \u2502�� \u251c\u2500\u2500 hal_bsp.d
- \u2502�� \u2502�� \u251c\u2500\u2500 hal_bsp.o
- \u2502�� \u2502�� \u251c\u2500\u2500 hal_bsp.o.cmd
+<p>When Newt builds a target, it recursively resolves all package dependencies, and generates artifacts that are placed in the bin/targets/<target-name>/app/apps/<app-name> directory, where the bin directory is under the project base directory, <code>target-name</code> is the name of the target, and <code>app-name</code> is the name of the application. For our example <code>my_blinky_sim</code> is the name of the target and <code>blinky</code> is the name of the application. The <code>blinky.elf</code> executable is stored in the bin/targets/my_blinky_sim/app/apps/blinky directory as shown in the source tree:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">tree -L 6 bin/
+bin/
+\u2514\u2500\u2500 targets
+ \u251c\u2500\u2500 my_blinky_sim
+ \u2502�� \u251c\u2500\u2500 app
+ \u2502�� \u2502�� \u251c\u2500\u2500 apps
+ \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 blinky
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 apps
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 apps_blinky.a
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 apps_blinky.a.cmd
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 blinky.elf
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 blinky.elf.cmd
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 blinky.elf.dSYM
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 blinky.elf.lst
+ \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 manifest.json
+ \u2502�� \u2502�� \u251c\u2500\u2500 hw
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 bsp
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 native
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 drivers
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 uart
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 hal
+ \u2502�� \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 hw_hal.a
+ \u2502�� \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 hw_hal.a.cmd
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 repos
+
<snip>
</pre></div>
@@ -434,6 +434,7 @@ bin
<li><strong>size</strong>: Get size of target components</li>
<li><strong>create-image</strong>: Add image header to the binary image</li>
<li><strong>run</strong>: Build, create image, load, and finally open a debug session with the target</li>
+<li><strong>target</strong>: Create, delete, configure, and query a target</li>
</ul>
<p>For more details on how Newt works, go to <a href="../newt_operation/">Newt - Theory of Operations</a>.</p>
<p><br></p>
@@ -496,13 +497,13 @@ Repos successfully installed
<p><br></p>
-<p>In order to reference the installed repositories in packages, the "@" notation should be specified in the repository specifier. As an example, the apps/blinky application has the following dependencies in its pkg.yml file. This tells the build system to look in the base directory of repos/apache-mynewt-core for the <code>libs/os</code>, <code>hw/hal</code>, and <code>libs/console/full</code> packages.</p>
+<p>In order to reference the installed repositories in packages, the "@" notation should be specified in the repository specifier. As an example, the apps/blinky application has the following dependencies in its pkg.yml file. This tells the build system to look in the base directory of repos/apache-mynewt-core for the <code>kernel/os</code>, <code>hw/hal</code>, and <code>sys/console/full</code> packages.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ more apps/blinky/pkg.yml
<snip>
pkg.deps:
- - "@apache-mynewt-core/libs/os"
+ - "@apache-mynewt-core/kernel/os"
- "@apache-mynewt-core/hw/hal"
- - "@apache-mynewt-core/libs/console/full"
+ - "@apache-mynewt-core/sys/console/full"
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/newt_operation/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/newt_operation/index.html b/develop/newt/newt_operation/index.html
index 4562aaf..74831d0 100644
--- a/develop/newt/newt_operation/index.html
+++ b/develop/newt/newt_operation/index.html
@@ -378,13 +378,14 @@
<h4 id="apps-package-directory">"apps" Package Directory</h4>
<p><code>apps</code> is where applications are stored, and applications are where the main() function is contained. The base project directory comes with one simple app called <code>blinky</code> in the <code>apps</code> directory. The core repository <code>@apache-mynewt-core</code> comes with many additional sample apps in its <code>apps</code> directory. At the time of this writing, there are several example BLE apps, the boot app, slinky app for using newt manager protocol, and more in that directory.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">@~/dev/myproj$ ls repos/apache-mynewt-core/apps/
-blecent bleprph_oic bleuart ffs2native slinky_oic test
-blehci bletest boot ocf_sample spitest timtest
-bleprph bletiny fat2native slinky splitty
+blecent blesplit boot sensors_test splitty
+blehci bletest fat2native slinky test
+bleprph bletiny ffs2native slinky_oic testbench
+bleprph_oic bleuart ocf_sample spitest timtest
</pre></div>
-<p>Along with the <code>targets</code> directory, <code>apps</code> represents the top-level of the build tree for the particular project, and define the dependencies and features for the rest of the system. Mynewt users and developers can add their own apps to the project's <code>apps</code> directory. </p>
+<p>Along with the <code>targets</code> directory, <code>apps</code> represents the top-level of the build tree for the particular project, and define the dependencies for the rest of the system. Mynewt users and developers can add their own apps to the project's <code>apps</code> directory. </p>
<p>The app definition is contained in a <code>pkg.yml</code> file. For example, blinky's <code>pkg.yml</code> file is:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ more apps/blinky/pkg.yml
<snip>
@@ -403,8 +404,7 @@ pkg.deps:
<p><br></p>
-<p>This file says that the name of the package is apps/blinky, and it
-depends on kernel/os, hw/hal and sys/console/full packages.</p>
+<p>This file says that the name of the package is apps/blinky, and it depends on the <code>kernel/os,</code>hw/hal<code>and</code>sys/console/full` packages.</p>
<p><strong>NOTE:</strong> @apache-mynewt-core is a repository descriptor, and this will be
covered in the "repository" section. </p>
<p><br></p>
@@ -430,17 +430,19 @@ pkg.yml target.yml
<p>There are helper functions to aid the developer specify parameters for a target. </p>
<ul>
<li><strong>vals</strong>: Displays all valid values for the specified parameter type (e.g. bsp for a target)</li>
-<li><strong>target show</strong>: Displays the build artifacts for specified or all targets</li>
+<li><strong>target show</strong>: Displays the variable values for either a specific target or all targets defined for the project</li>
+<li><strong>target set</strong>: Sets values for target variables</li>
</ul>
-<p>In general, the three basic parameters of a target (<code>app</code>, <code>bsp</code>, and <code>build_profile</code>) are stored in the <code>target.yml</code> file in that target's build directory under <code>targets</code>. You will also see a <code>pkg.yml</code> file in the same directory. Since targets are packages, a <code>pkg.yml</code> is expected. It contains typical package descriptors, dependencies, and additional parameters such as the following:</p>
+<p>In general, the three basic parameters of a target (<code>app</code>, <code>bsp</code>, and <code>build_profile</code>) are stored in the target's <code>target.yml</code> file in the targets/<target-name> directory, where <code>target-name</code> is the name of the target. You will also see a <code>pkg.yml</code> file in the same directory. Since targets are packages, a <code>pkg.yml</code> is expected. It contains typical package descriptors, dependencies, and additional parameters such as the following:</p>
<ul>
<li>Cflags: Any additional compiler flags you might want to specify to the build</li>
<li>Aflags: Any additional assembler flags you might want to specify to the build</li>
<li>Lflags: Any additional linker flags you might want to specify to the build</li>
</ul>
+<p>You can also override the values of the system configuration settings that are defined by the packages that your target includes. You override the values in your target's <code>syscfg.yml</code> file (stored in the targets/<target-name> directory). You can use the <code>newt target config show</code> command to see the configuration settings and values for your target, and use the <code>newt target set</code> command to set the <code>syscfg</code> variable and override the configuration setting values. You can also use an editor to create your target's <code>syscfg.yml</code> file and add the setting values to the file. See <a href="../../os/modules/sysinitconfig/sysinitconfig/">System Configuration And Initialization</a> for more information on system configuration settings.</p>
<p><br></p>
<h3 id="resolving-dependencies">Resolving dependencies</h3>
-<p>When newt is told to build a project, it will:</p>
+<p>When newt builds a project, it will:</p>
<ul>
<li>find the top-level project.yml file</li>
<li>recurse the packages in the package tree, and build a list of all
@@ -467,43 +469,48 @@ along with that application.</li>
<p>Newt builds the dependency tree specified by all the packages. While building this tree, it does a few other things:</p>
<ul>
<li>Sets up the include paths for each package. Any package that depends on another package, automatically gets the include directories from the package it includes. Include directories in the
-newt structure must always be prefixed by the package name. For example, libs/os has the following include tree and its include directory files contains the package name "os" before any header files. This is so in order to avoid any header file conflicts.</li>
+newt structure must always be prefixed by the package name. For example, kernel/os has the following include tree and its include directory files contains the package name "os" before any header files. This is so in order to avoid any header file conflicts.</li>
</ul>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ tree
-.
-\u251c\u2500\u2500 README.md
-\u251c\u2500\u2500 include
-\u2502�� \u2514\u2500\u2500 os
-\u2502�� \u251c\u2500\u2500 arch
-\u2502�� \u2502�� \u251c\u2500\u2500 cortex_m0
-\u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 os
-\u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 os_arch.h
-\u2502�� \u2502�� \u251c\u2500\u2500 cortex_m4
-\u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 os
-\u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 os_arch.h
-\u2502�� \u2502�� \u2514\u2500\u2500 sim
-\u2502�� \u2502�� \u2514\u2500\u2500 os
-\u2502�� \u2502�� \u2514\u2500\u2500 os_arch.h
-\u2502�� \u251c\u2500\u2500 endian.h
-\u2502�� \u251c\u2500\u2500 os.h
-\u2502�� \u251c\u2500\u2500 os_callout.h
-\u2502�� \u251c\u2500\u2500 os_cfg.h
-\u2502�� \u251c\u2500\u2500 os_eventq.h
-\u2502�� \u251c\u2500\u2500 os_heap.h
-\u2502�� \u251c\u2500\u2500 os_malloc.h
-\u2502�� \u251c\u2500\u2500 os_mbuf.h
-\u2502�� \u251c\u2500\u2500 os_mempool.h
-\u2502�� \u251c\u2500\u2500 os_mutex.h
-\u2502�� \u251c\u2500\u2500 os_sanity.h
-\u2502�� \u251c\u2500\u2500 os_sched.h
-\u2502�� \u251c\u2500\u2500 os_sem.h
-\u2502�� \u251c\u2500\u2500 os_task.h
-\u2502�� \u251c\u2500\u2500 os_test.h
-\u2502�� \u251c\u2500\u2500 os_time.h
-\u2502�� \u2514\u2500\u2500 queue.h
-\u251c\u2500\u2500 pkg.yml
-\u2514\u2500\u2500 src
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$tree kernel/os/include
+kernel/os/include
+\u2514\u2500\u2500 os
\u251c\u2500\u2500 arch
+ \u2502�� \u251c\u2500\u2500 cortex_m0
+ \u2502�� \u2502�� \u2514\u2500\u2500 os
+ \u2502�� \u2502�� \u2514\u2500\u2500 os_arch.h
+ \u2502�� \u251c\u2500\u2500 cortex_m4
+ \u2502�� \u2502�� \u2514\u2500\u2500 os
+ \u2502�� \u2502�� \u2514\u2500\u2500 os_arch.h
+ \u2502�� \u251c\u2500\u2500 mips
+ \u2502�� \u2502�� \u2514\u2500\u2500 os
+ \u2502�� \u2502�� \u2514\u2500\u2500 os_arch.h
+ \u2502�� \u251c\u2500\u2500 sim
+ \u2502�� \u2502�� \u2514\u2500\u2500 os
+ \u2502�� \u2502�� \u2514\u2500\u2500 os_arch.h
+ \u2502�� \u2514\u2500\u2500 sim-mips
+ \u2502�� \u2514\u2500\u2500 os
+ \u2502�� \u2514\u2500\u2500 os_arch.h
+ \u251c\u2500\u2500 endian.h
+ \u251c\u2500\u2500 os.h
+ \u251c\u2500\u2500 os_callout.h
+ \u251c\u2500\u2500 os_cfg.h
+ \u251c\u2500\u2500 os_cputime.h
+ \u251c\u2500\u2500 os_dev.h
+ \u251c\u2500\u2500 os_eventq.h
+ \u251c\u2500\u2500 os_fault.h
+ \u251c\u2500\u2500 os_heap.h
+ \u251c\u2500\u2500 os_malloc.h
+ \u251c\u2500\u2500 os_mbuf.h
+ \u251c\u2500\u2500 os_mempool.h
+ \u251c\u2500\u2500 os_mutex.h
+ \u251c\u2500\u2500 os_sanity.h
+ \u251c\u2500\u2500 os_sched.h
+ \u251c\u2500\u2500 os_sem.h
+ \u251c\u2500\u2500 os_task.h
+ \u251c\u2500\u2500 os_test.h
+ \u251c\u2500\u2500 os_time.h
+ \u2514\u2500\u2500 queue.h
+
<snip>
</pre></div>
@@ -517,43 +524,50 @@ those APIs (i.e. pkg.req_api: hw-hal-impl).</p>
</li>
<li>
<p>Reads and validates the configuration setting definitions and values from the package <code>syscfg.yml</code> files.
-It generates a <code>syscfg.h</code> header file that packages include in the source files inorder to access the settings.<br />
+It generates a <code>syscfg.h</code> header file that packages include in the source files in order to access the settings.<br />
It also generates a system initialization function to initialize the packages.
See <a href="../../os/modules/sysinitconfig/sysinitconfig/">System Configuration And Initialization</a> for more information.</p>
</li>
</ul>
-<p>In order to properly resolve all dependencies in the build system, newt recursively processes the package dependencies until there are no new dependencies or features (because features can add dependencies.) And it builds a big list of all the packages that need to be build.</p>
+<p>In order to properly resolve all dependencies in the build system, newt recursively processes the package dependencies until there are no new dependencies. And it builds a big list of all the packages that need to be build.</p>
<p>Newt then goes through this package list, and builds every package into
an archive file.</p>
<p><strong>NOTE:</strong> The newt tool generates compiler dependencies for all of these packages, and only rebuilds the packages whose dependencies have changed. Changes in package & project dependencies are also taken into account. It is smart, after all!</p>
<h3 id="producing-artifacts">Producing artifacts</h3>
<p>Once newt has built all the archive files, it then links the archive files together. The linkerscript to use is specified by the board support package (BSP.)</p>
-<p>NOTE: One common use of the "features" option above is to overwrite
-which linkerscript is used, based upon whether or not the BSP is being
-build for a raw image, bootable image or bootloader itself.</p>
-<p>The newt tool places all of it's artifacts into the bin/ directory at
-the top-level of the project, prefixed by the target name being built,
-for example:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ tree -L 4 bin/
-bin/
-\u2514\u2500\u2500 my_blinky_sim
- \u251c\u2500\u2500 apps
- \u2502 \u2514\u2500\u2500 blinky
- \u2502 \u251c\u2500\u2500 blinky.a
- \u2502 \u251c\u2500\u2500 blinky.a.cmd
- \u2502 \u251c\u2500\u2500 blinky.elf
- \u2502 \u251c\u2500\u2500 blinky.elf.cmd
- \u2502 \u251c\u2500\u2500 blinky.elf.dSYM
- \u2502 \u251c\u2500\u2500 blinky.elf.lst
- \u2502 \u251c\u2500\u2500 main.d
- \u2502 \u251c\u2500\u2500 main.o
- \u2502 \u2514\u2500\u2500 main.o.cmd
- \u251c\u2500\u2500 hw
- \u2502 \u251c\u2500\u2500 bsp
- \u2502 \u2502 \u2514\u2500\u2500 native
- \u2502 \u251c\u2500\u2500 hal
- \u2502 \u2502 \u251c\u2500\u2500 flash_map.d
- \u2502 \u2502 \u251c\u2500\u2500 flash_map.o
+<p>The newt tool creates a bin directory under the base project directory, and places a target's build artifacts into the bin/targets/<target-name>/app/apps/<app-name> directory, where <code>target-name</code> is the name of the target and <code>app-name</code> is the name of the application. As an example, the <code>blinky.elf</code> executable for the <code>blinky</code> application defined by the <code>my_blinky_sim</code> target is stored in the bin/targets/my_blinky_sim/app/apps/blinky directory as shown in the following source tree:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$tree -L 9 bin/ bin/
+\u2514\u2500\u2500 targets
+ \u251c\u2500\u2500 my_blinky_sim
+ \u2502�� \u251c\u2500\u2500 app
+ \u2502�� \u2502�� \u251c\u2500\u2500 apps
+ \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 blinky
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 apps
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 blinky
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 src
+ \u2502�� \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 main.d
+ \u2502�� \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 main.o
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 main.o.cmd
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 apps_blinky.a
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 apps_blinky.a.cmd
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 blinky.elf
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 blinky.elf.cmd
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 blinky.elf.dSYM
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 Contents
+ \u2502�� \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 Info.plist
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 Resources
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 DWARF
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 blinky.elf.lst
+ \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 manifest.json
+ \u2502�� \u2502�� \u251c\u2500\u2500 hw
+ \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 bsp
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 native
+ \u2502�� \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 hw_bsp_native.a
+ \u2502�� \u2502�� \u2502�� \u2502�� \u251c\u2500\u2500 hw_bsp_native.a.cmd
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 repos
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 apache-mynewt-core
+ \u2502�� \u2502�� \u2502�� \u2502�� \u2514\u2500\u2500 hw
+
<snip>
</pre></div>
@@ -564,8 +578,8 @@ bin/
<li>Archive File</li>
<li>*.cmd: The command use to generate the object or archive file</li>
<li>*.lst: The list file where symbols are located</li>
-<li>*.o The object files that get put into the archive file</li>
</ul>
+<p>Note: The *.o object files that get put into the archive file are stored in the bin/targets/my_blinky_sim/app/apps/blinky/apps/blinky/src directory.</p>
<h3 id="downloaddebug-support">Download/Debug Support</h3>
<p>Once a target has been build, there are a number of helper functions
that work on the target. These are:</p>
@@ -575,6 +589,7 @@ that work on the target. These are:</p>
<li><strong>size</strong> Size of target components</li>
<li><strong>create-image</strong> Add image header to target binary</li>
<li><strong>run</strong> The equivalent of build, create-image, load, and debug on specified target</li>
+<li><strong>target</strong> Create, delete, configure, and query a target</li>
</ul>
<p><code>load</code> and <code>debug</code> handles driving GDB and the system debugger. These
commands call out to scripts that are defined by the BSP.</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/newt_ops/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/newt_ops/index.html b/develop/newt/newt_ops/index.html
index ba4cca8..2528661 100644
--- a/develop/newt/newt_ops/index.html
+++ b/develop/newt/newt_ops/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../command_list/newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../command_list/newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../command_list/newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../command_list/newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../command_list/newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../command_list/newt_target/">newt target</a>
</li>
@@ -494,9 +502,9 @@
</div>
<h2 id="command-structure">Command Structure</h2>
-<p>Just like verbs are actions in a sentence and adverdbs modifiy verbs, so in <em>newt</em> tool, commands are actions and flags modify actions. A command can have subcommands, too. Arguments to commands and subcommands, with appropriate flags, will dictate the execution and result of a command. </p>
-<p>For instance, in the example below, the <em>newt</em> command has the subcommand <code>target set</code> in which the argument 'my_target1' is the target whose attribute, <em>arch</em>, is set to 'cortex_md.' </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt target set my_target1 arch=cortex_m4
+<p>Just like verbs are actions in a sentence and adverbs modifiy verbs, so in the <em>newt</em> tool, commands are actions and flags modify actions. A command can have subcommands. Arguments to commands and subcommands, with appropriate flags, dictate the execution and result of a command. </p>
+<p>For instance, in the example below, the <em>newt</em> command has the subcommand <code>target set</code> in which the argument 'my_target1' is the target whose attribute, <em>app</em>, is set to '@apache-mynewt-core/hw/bsp/nrf52dk'</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt target set my_target1 app=@apache-mynewt-core/hw/bsp/nrf52dk
</pre></div>
@@ -508,14 +516,14 @@
<p>In addition to the <a href="../newt_intro/">Newt Tool Manual</a> in docs, command-line help is available for each command (and subcommand), through the <code>-h</code> or <code>--help</code> options. </p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt target --help
- Command for manipulating targets
+ Commands to create, delete, configure, and query targets
Usage:
newt target [flags]
newt target [command]
Available Commands:
- config View target system configuration
+ config View or populate a target's system configuration
copy Copy target
create Create a target
delete Delete target
@@ -525,6 +533,8 @@
show View target configuration variables
Global Flags:
+ -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
-l, --loglevel string Log level (default "WARN")
-o, --outfile string Filename to tee output to
-q, --quiet Be quiet; only display error output
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/os/modules/sysinitconfig/sysconfig_error/index.html
----------------------------------------------------------------------
diff --git a/develop/os/modules/sysinitconfig/sysconfig_error/index.html b/develop/os/modules/sysinitconfig/sysconfig_error/index.html
index 1e89cd9..c7d1c4a 100644
--- a/develop/os/modules/sysinitconfig/sysconfig_error/index.html
+++ b/develop/os/modules/sysinitconfig/sysconfig_error/index.html
@@ -821,7 +821,90 @@ outputs when multiple packages define the <code>LOG_NEWTMGR</code> setting:</p>
</pre></div>
-<p><strong>Note:</strong> Newt does not output the <code>Setting history</code> with duplicate setting error messages. </p>
+<p><strong>Note:</strong> Newt does not output the <code>Setting history</code> with duplicate setting error messages.
+<br></p>
+<h3 id="override-of-undefined-system-configuration-setting">Override of Undefined System Configuration Setting</h3>
+<p>The <code>newt build</code> command ignores overrides of undefined system configuration settings. The command does not print a warning when you run it with the default log level. If you override a setting and the value is not assigned to the setting, you may have misspelled the setting name or a package no longer defines the setting. You have two options to troubleshoot this problem:</p>
+<ul>
+<li>Run the <code>newt target config show</code> command to see the configuration setting definitions and overrides.</li>
+<li>Run the <code>newt build -ldebug</code> command to build your target with DEBUG log level. </li>
+</ul>
+<p>Note: The <code>newt build -ldebug</code> command generates lots of output and we recommend that you use the <code>newt target config show</code> command option.
+<br></p>
+<h4 id="example-ignoring-override-of-undefined-setting-message">Example: Ignoring Override of Undefined Setting Message</h4>
+<p>The following example shows that the <code>apps/slinky</code> application overrides the <code>LOG_NEWTMGR</code> setting but omits the <strong>T</strong> as an example of an error and overrides the misspelled <strong>LOG_NEWMGR</strong> setting. Here is an excerpt from its <code>syscfg.yml</code> file: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">#package: apps/slinky
+syscfg.vals:
+ # Enable the shell task.
+ SHELL_TASK: 1
+ ...
+
+ # Enable newtmgr commands.
+ STATS_NEWTMGR: 1
+ LOG_NEWMGR: 1
+</pre></div>
+
+
+<p><br>
+The <code>newt target config show slinky_sim</code> command outputs the following WARNING message:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">2017/02/18 17:19:12.119 [WARNING] Ignoring override of undefined settings:
+2017/02/18 17:19:12.119 [WARNING] LOG_NEWMGR
+2017/02/18 17:19:12.119 [WARNING] NFFS_FLASH_AREA
+2017/02/18 17:19:12.119 [WARNING] Setting history (newest -> oldest):
+2017/02/18 17:19:12.119 [WARNING] LOG_NEWMGR: [apps/slinky:1]
+2017/02/18 17:19:12.119 [WARNING] NFFS_FLASH_AREA: [hw/bsp/native:FLASH_AREA_NFFS]
+</pre></div>
+
+
+<p><br></p>
+<p>The <code>newt build -ldebug slinky_sim</code> command outputs the following DEBUG message: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">2017/02/18 17:06:21.451 [DEBUG] Ignoring override of undefined settings:
+2017/02/18 17:06:21.451 [DEBUG] LOG_NEWMGR
+2017/02/18 17:06:21.451 [DEBUG] NFFS_FLASH_AREA
+2017/02/18 17:06:21.451 [DEBUG] Setting history (newest -> oldest):
+2017/02/18 17:06:21.451 [DEBUG] LOG_NEWMGR: [apps/slinky:1]
+2017/02/18 17:06:21.451 [DEBUG] NFFS_FLASH_AREA: [hw/bsp/native:FLASH_AREA_NFFS]
+</pre></div>
+
+
+<p><br></p>
+<h4 id="bsp-package-overrides-undefined-configuration-settings">BSP Package Overrides Undefined Configuration Settings</h4>
+<p>You might see a warning that indicates your application's BSP package is overriding some undefined settings. As you can see from the previous example, the WARNING message shows that the <code>hw/bsp/native</code> package is overriding the undefined <code>NFFS_FLASH_AREA</code> setting. This is not an error because of the way a BSP package defines and assigns its flash areas to packages that use flash memory.</p>
+<p>A BSP package defines, in its <code>bsp.yml</code> file, a flash area map of the flash areas on the board. A package that uses flash memory must define a flash area configuration setting name. The BSP package overrides the package's flash area setting with one of the flash areas from its flash area map. A BSP package overrides the flash area settings for all packages that use flash memory because it does not know the packages that an application uses. When an application does not include one of these packages, the flash area setting for the package is undefined. You will see a message that indicates the BSP package overrides this undefined setting.</p>
+<p>Here are excerpts from the <code>hw/bsp/native</code> package's <code>bsp.yml</code> and <code>syscfg.yml</code> files for the <code>slinky_sim</code> target. The BSP package defines the flash area map in its <code>bsp.yml</code> file and overrides the flash area settings for all packages in its <code>syscfg.yml</code> file. The <code>slinky_sim</code> target does not use the <code>fs/nffs</code> package which defines the <code>NFFS_FLASH_AREA</code> setting. Newt warns that the <code>hw/bsp/native</code> packages overrides the undefined <code>NFFS_FLASH_AREA</code> setting.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"># hw/bsp/native bsp.yml
+bsp.flash_map:
+ areas:
+ # System areas.
+ FLASH_AREA_BOOTLOADER:
+ device: 0
+ offset: 0x00000000
+ size: 16kB
+
+ ...
+
+ FLASH_AREA_IMAGE_SCRATCH:
+ device: 0
+ offset: 0x000e0000
+ size: 128kB
+
+ # User areas.
+ FLASH_AREA_REBOOT_LOG:
+ user_id: 0
+ device: 0
+ offset: 0x00004000
+ size: 16kB
+ FLASH_AREA_NFFS:
+ user_id: 1
+ device: 0
+ offset: 0x00008000
+
+# hw/bsp/native syscfg.yml
+syscfg.vals:
+ NFFS_FLASH_AREA: FLASH_AREA_NFFS
+ CONFIG_FCB_FLASH_AREA: FLASH_AREA_NFFS
+ REBOOT_LOG_FLASH_AREA: FLASH_AREA_REBOOT_LOG
+</pre></div>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/sitemap.xml
----------------------------------------------------------------------
diff --git a/develop/sitemap.xml b/develop/sitemap.xml
index 3a2a667..0ccc1fb 100644
--- a/develop/sitemap.xml
+++ b/develop/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,7 +13,7 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -22,7 +22,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -30,7 +30,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -38,7 +38,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -46,7 +46,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -54,7 +54,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -62,7 +62,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -71,7 +71,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -83,7 +83,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -123,13 +123,13 @@
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-02-27</lastmod>
+ <lastmod>2017-03-02</lastmod>
<changefreq>daily</changefreq>
</url>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/events/index.html
----------------------------------------------------------------------
diff --git a/events/index.html b/events/index.html
index 3a3395f..b46782d 100644
--- a/events/index.html
+++ b/events/index.html
@@ -150,17 +150,31 @@
<div class="event">
- <h2>CES</h2>
- <p>5-8 January, 2017</p>
- <p>Las Vegas, NV</p>
- <p>Contact runtime.io or email us at dev@mynewt.incubator.apache.org to check out and discuss Apache Mynewt and its many uses.</p>
+ <h2>Embedded World</h2>
+ <p>14-16 March, 2017</p>
+ <p>Nuremberg, Germany</p>
+ <p>Contact runtime.io or email us at dev@mynewt.incubator.apache.org to discuss Apache Mynewt.</p>
</div>
<div class="event">
- <h2>Embedded Systems Conference</h2>
- <p>6-8 December, 2016</p>
- <p>San Jose Convention Center, San Jose, CA, USA</p>
- <p>Meet up to discuss Apache Mynewt.</p>
+ <h2>Bluetooth World</h2>
+ <p>28-29 March, 2017</p>
+ <p>Santa Clara Convention Center, Santa Clara, CA, USA</p>
+ <p>Get to the heart of BLE support from Apache Mynewt at Exhibit Booth #11A.</p>
+ </div>
+
+ <div class="event">
+ <h2>IoTFuse: Conference 2017</h2>
+ <p>21 April, 2017</p>
+ <p>Minneapolis Convention Center, Minneapolis, CA, USA</p>
+ <p>Presentation on managing devices running open source Operating Systems including Apache Mynewt.</p>
+ </div>
+
+ <div class="event">
+ <h2>ApacheIoT, ApacheCon North America</h2>
+ <p>16-18 May, 2017</p>
+ <p>Santa Clara Convention Center, Santa Clara, CA, USA</p>
+ <p>A new conference track that lays the vision, framework, and components for an IoT system. See more at <a href="http://us.apacheiot.org"> http://us.apacheiot.org</a>. Multiple talks will feature Apache Mynewt.</p>
</div>
</div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/index.html
----------------------------------------------------------------------
diff --git a/index.html b/index.html
index 9e7f72f..3aa2c75 100644
--- a/index.html
+++ b/index.html
@@ -288,6 +288,9 @@
<li>
<a href="http://www.nxp.com/products/software-and-tools/hardware-development-tools/freedom-development-boards/freedom-development-platform-for-kinetis-k64-k63-and-k24-mcus:FRDM-K64F"> FRDM-K64F </a> from NXP (Cortex-M4)
</li>
+ <li>
+ <a href="https://creatordev.io/ci40-iot-dev-kit.html"> Creator Ci40 IoT Kit </a> from Imagination Technologies (MIPS CPU)
+ </li>
</ul>
</div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/landing.html
----------------------------------------------------------------------
diff --git a/landing.html b/landing.html
index e160dec..ccc7ec2 100644
--- a/landing.html
+++ b/landing.html
@@ -147,6 +147,9 @@
<li>
<a href="http://www.nxp.com/products/software-and-tools/hardware-development-tools/freedom-development-boards/freedom-development-platform-for-kinetis-k64-k63-and-k24-mcus:FRDM-K64F"> FRDM-K64F </a> from NXP (Cortex-M4)
</li>
+ <li>
+ <a href="https://creatordev.io/ci40-iot-dev-kit.html"> Creator Ci40 IoT Kit </a> from Imagination Technologies (MIPS CPU)
+ </li>
</ul>
</div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/index.html
----------------------------------------------------------------------
diff --git a/latest/index.html b/latest/index.html
index 9e7f72f..3aa2c75 100644
--- a/latest/index.html
+++ b/latest/index.html
@@ -288,6 +288,9 @@
<li>
<a href="http://www.nxp.com/products/software-and-tools/hardware-development-tools/freedom-development-boards/freedom-development-platform-for-kinetis-k64-k63-and-k24-mcus:FRDM-K64F"> FRDM-K64F </a> from NXP (Cortex-M4)
</li>
+ <li>
+ <a href="https://creatordev.io/ci40-iot-dev-kit.html"> Creator Ci40 IoT Kit </a> from Imagination Technologies (MIPS CPU)
+ </li>
</ul>
</div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/landing.html
----------------------------------------------------------------------
diff --git a/latest/landing.html b/latest/landing.html
index e160dec..ccc7ec2 100644
--- a/latest/landing.html
+++ b/latest/landing.html
@@ -147,6 +147,9 @@
<li>
<a href="http://www.nxp.com/products/software-and-tools/hardware-development-tools/freedom-development-boards/freedom-development-platform-for-kinetis-k64-k63-and-k24-mcus:FRDM-K64F"> FRDM-K64F </a> from NXP (Cortex-M4)
</li>
+ <li>
+ <a href="https://creatordev.io/ci40-iot-dev-kit.html"> Creator Ci40 IoT Kit </a> from Imagination Technologies (MIPS CPU)
+ </li>
</ul>
</div>
[7/7] incubator-mynewt-site git commit: Update newt command
documentation, sysconfig overwrites, events, bsp list
Posted by ad...@apache.org.
Update newt command documentation, sysconfig overwrites, events, bsp list
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/555f6f65
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/555f6f65
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/555f6f65
Branch: refs/heads/asf-site
Commit: 555f6f651181920e79b3f97c347365bb3c1079b0
Parents: 855b600
Author: aditihilbert <ad...@runtime.io>
Authored: Thu Mar 2 17:02:29 2017 -0800
Committer: aditihilbert <ad...@runtime.io>
Committed: Thu Mar 2 17:02:29 2017 -0800
----------------------------------------------------------------------
develop/index.html | 3 +
develop/landing.html | 3 +
develop/mkdocs/search_index.json | 377 ++++++-----
develop/newt/command_list/newt_build/index.html | 62 +-
develop/newt/command_list/newt_clean/index.html | 76 +--
.../newt/command_list/newt_complete/index.html | 576 -----------------
.../command_list/newt_create_image/index.html | 74 ++-
develop/newt/command_list/newt_debug/index.html | 65 +-
develop/newt/command_list/newt_help/index.html | 71 +-
develop/newt/command_list/newt_info/index.html | 51 +-
.../newt/command_list/newt_install/index.html | 55 +-
develop/newt/command_list/newt_load/index.html | 55 +-
develop/newt/command_list/newt_mfg/index.html | 47 +-
develop/newt/command_list/newt_new/index.html | 54 +-
develop/newt/command_list/newt_pkg/index.html | 648 +++++++++++++++++++
develop/newt/command_list/newt_run/index.html | 70 +-
develop/newt/command_list/newt_size/index.html | 53 +-
develop/newt/command_list/newt_sync/index.html | 584 +++++++++++++++++
.../newt/command_list/newt_target/index.html | 139 ++--
develop/newt/command_list/newt_test/index.html | 76 +--
.../newt/command_list/newt_upgrade/index.html | 58 +-
develop/newt/command_list/newt_vals/index.html | 66 +-
.../newt/command_list/newt_version/index.html | 45 +-
develop/newt/newt_intro/index.html | 59 +-
develop/newt/newt_operation/index.html | 161 ++---
develop/newt/newt_ops/index.html | 36 +-
.../sysinitconfig/sysconfig_error/index.html | 85 ++-
develop/sitemap.xml | 24 +-
events/index.html | 30 +-
index.html | 3 +
landing.html | 3 +
latest/index.html | 3 +
latest/landing.html | 3 +
latest/mkdocs/search_index.json | 377 ++++++-----
latest/newt/command_list/newt_build/index.html | 62 +-
latest/newt/command_list/newt_clean/index.html | 76 +--
.../newt/command_list/newt_complete/index.html | 576 -----------------
.../command_list/newt_create_image/index.html | 74 ++-
latest/newt/command_list/newt_debug/index.html | 65 +-
latest/newt/command_list/newt_help/index.html | 71 +-
latest/newt/command_list/newt_info/index.html | 51 +-
.../newt/command_list/newt_install/index.html | 55 +-
latest/newt/command_list/newt_load/index.html | 55 +-
latest/newt/command_list/newt_mfg/index.html | 47 +-
latest/newt/command_list/newt_new/index.html | 54 +-
latest/newt/command_list/newt_pkg/index.html | 648 +++++++++++++++++++
latest/newt/command_list/newt_run/index.html | 70 +-
latest/newt/command_list/newt_size/index.html | 53 +-
latest/newt/command_list/newt_sync/index.html | 584 +++++++++++++++++
latest/newt/command_list/newt_target/index.html | 139 ++--
latest/newt/command_list/newt_test/index.html | 76 +--
.../newt/command_list/newt_upgrade/index.html | 58 +-
latest/newt/command_list/newt_vals/index.html | 66 +-
.../newt/command_list/newt_version/index.html | 45 +-
latest/newt/newt_intro/index.html | 59 +-
latest/newt/newt_operation/index.html | 161 ++---
latest/newt/newt_ops/index.html | 36 +-
.../sysinitconfig/sysconfig_error/index.html | 85 ++-
latest/sitemap.xml | 24 +-
sitemap.xml | 26 +-
v0_9_0/index.html | 3 +
v0_9_0/landing.html | 3 +
v0_9_0/sitemap.xml | 26 +-
63 files changed, 4614 insertions(+), 2826 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/index.html
----------------------------------------------------------------------
diff --git a/develop/index.html b/develop/index.html
index 9e7f72f..3aa2c75 100644
--- a/develop/index.html
+++ b/develop/index.html
@@ -288,6 +288,9 @@
<li>
<a href="http://www.nxp.com/products/software-and-tools/hardware-development-tools/freedom-development-boards/freedom-development-platform-for-kinetis-k64-k63-and-k24-mcus:FRDM-K64F"> FRDM-K64F </a> from NXP (Cortex-M4)
</li>
+ <li>
+ <a href="https://creatordev.io/ci40-iot-dev-kit.html"> Creator Ci40 IoT Kit </a> from Imagination Technologies (MIPS CPU)
+ </li>
</ul>
</div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/landing.html
----------------------------------------------------------------------
diff --git a/develop/landing.html b/develop/landing.html
index e160dec..ccc7ec2 100644
--- a/develop/landing.html
+++ b/develop/landing.html
@@ -147,6 +147,9 @@
<li>
<a href="http://www.nxp.com/products/software-and-tools/hardware-development-tools/freedom-development-boards/freedom-development-platform-for-kinetis-k64-k63-and-k24-mcus:FRDM-K64F"> FRDM-K64F </a> from NXP (Cortex-M4)
</li>
+ <li>
+ <a href="https://creatordev.io/ci40-iot-dev-kit.html"> Creator Ci40 IoT Kit </a> from Imagination Technologies (MIPS CPU)
+ </li>
</ul>
</div>
[2/7] incubator-mynewt-site git commit: Update newt command
documentation, sysconfig overwrites, events, bsp list
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/command_list/newt_build/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/command_list/newt_build/index.html b/latest/newt/command_list/newt_build/index.html
index dc64ee0..19768c4 100644
--- a/latest/newt/command_list/newt_build/index.html
+++ b/latest/newt/command_list/newt_build/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,27 +504,26 @@
</div>
<h2 id="newt-build"><font color="#F2853F" style="font-size:24pt">newt build </font></h2>
-<p>Compiles, links, and builds one or more apps. </p>
+<p>Build one or more targets. </p>
<h4 id="usage">Usage:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt build [flags] input1
-</pre></div>
-
-
-<p>where <code>input1</code> is the name of the target to build.</p>
-<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for target
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt build <target-name> [target_name ...] [flags]
</pre></div>
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -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.
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
</pre></div>
+<h4 id="description">Description</h4>
+<p>Compiles, links, and builds an ELF binary for the target named <target-name>. It builds an ELF file for the application specified by the <code>app</code> variable for the <code>target-name</code> target. The image can be loaded and run on the hardware specified by the <code>bsp</code> variable for the target. The command creates the 'bin/' directory under the project's base directory (that the <code>newt new</code> command created) and stores the executable in the 'bin/targets/<target-name>/app/apps/<app-name>' directory.</p>
+<p>You can specify a list of target names, separated by a space, to build multiple targets. </p>
<h4 id="examples">Examples</h4>
<table>
<thead>
@@ -528,19 +535,14 @@
</thead>
<tbody>
<tr>
-<td>build</td>
-<td>newt build <br> <code>input1</code></td>
-<td>Builds the source code into an image that can be loaded on the hardware (<code>bsp</code>) associated with the target named <code>input1</code> to run the application enabled by the <code>app</code> 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.</td>
-</tr>
-<tr>
<td></td>
<td>newt build <br> my_blinky_sim</td>
-<td>For example, if <code>app</code> was set to <code>apps/blinky</code> 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 <code>newt new</code> at the start of the project.</td>
+<td>Builds an executable for the <code>my_blinky_sim</code> target. For example, if the <code>my_blinky_sim</code> target has <code>app</code> set to <code>apps/blinky</code>, you will find the generated .elf, .a, and .lst files in the 'bin/targets/my_blinky_sim/app/apps/blinky' directory.</td>
</tr>
<tr>
-<td>build</td>
-<td>newt build my_blinky_sim myble</td>
-<td>builds the apps defined for both the targets "my_blinky_sim" and "myble".</td>
+<td></td>
+<td>newt build <br> my_blinky_sim myble</td>
+<td>Builds the images for the applications defined by the <code>my_blinky_sim</code> and <code>myble</code> targets.</td>
</tr>
</tbody>
</table>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/command_list/newt_clean/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/command_list/newt_clean/index.html b/latest/newt/command_list/newt_clean/index.html
index 44030da..7e884da 100644
--- a/latest/newt/command_list/newt_clean/index.html
+++ b/latest/newt/command_list/newt_clean/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,55 +504,49 @@
</div>
<h2 id="newt-clean"><font color="#F2853F" style="font-size:24pt">newt clean </font></h2>
-<p>Deletes application build artifacts for a specified target</p>
+<p>Delete build artifacts for one or more targets. </p>
<h4 id="usage">Usage:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt clean [flags] input1
-</pre></div>
-
-
-<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for target
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt clean <target-name> [target-name...] | all [flags]
</pre></div>
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -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.
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
</pre></div>
<h4 id="description">Description</h4>
+<p>Deletes all the build artifacts generated for the <code>target-name</code> target. It does not delete the target definition. You can specify a list of targets, separated by a space, to delete the artifacts for multiple targets, or specify <code>all</code> to delete the artifacts for all targets.</p>
+<h4 id="examples">Examples</h4>
<table>
<thead>
<tr>
<th>Sub-command</th>
+<th>Usage</th>
<th>Explanation</th>
</tr>
</thead>
<tbody>
<tr>
-<td>clean</td>
-<td>Deletes all the build artifacts generated for target specified by <code>input1</code>. It does not delete the target definition.</td>
+<td></td>
+<td>newt clean myble</td>
+<td>Deletes the 'bin/targets/myble' directory where all the build artifacts generated from the <code>myble</code> target build are stored.</td>
</tr>
-</tbody>
-</table>
-<h4 id="examples">Examples</h4>
-<table>
-<thead>
<tr>
-<th>Sub-command</th>
-<th>Usage</th>
-<th>Explanation</th>
+<td></td>
+<td>newt clean my_blinky_sim myble</td>
+<td>Deletes the 'bin/targets/my_blinky_sim' and the 'bin/targets/myble' directories where all the artifacts generated from the <code>my_blinky_sim</code> and <code>myble</code> target builds are stored.</td>
</tr>
-</thead>
-<tbody>
<tr>
-<td>clean</td>
-<td>newt clean myble2</td>
-<td>Removes all the files generated while building the target <code>myble2</code> and placed in the <code>bin/myble2</code> directory created during the build process.</td>
+<td></td>
+<td>newt clean all</td>
+<td>Removes the artifacts for all target builds. Deletes the top level 'bin' directory.</td>
</tr>
</tbody>
</table>
@@ -565,8 +567,8 @@
</li>
<li class="pull-right">
- <a href=../newt_complete/>
- Next: newt complete
+ <a href=../newt_create_image/>
+ Next: newt create-image
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/command_list/newt_complete/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/command_list/newt_complete/index.html b/latest/newt/command_list/newt_complete/index.html
deleted file mode 100644
index 57205e9..0000000
--- a/latest/newt/command_list/newt_complete/index.html
+++ /dev/null
@@ -1,576 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta http-equiv="X-UA-Compatible" content="IE=edge">
- <meta name="viewport" content="width=device-width, initial-scale=1.0">
-
-
- <!-- This is broken by doc revisioning.
- <link rel="canonical" href="http://mynewt.apache.org/newt/command_list/newt_complete/"> -->
- <link rel="shortcut icon" href="../../../img/favicon.ico">
-
- <title>newt complete - Apache Mynewt</title>
-
- <link href="../../../css/bootstrap-3.0.3.min.css" rel="stylesheet">
- <link rel="stylesheet" href="../../../css/highlight.css">
- <link href="../../../css/base.css" rel="stylesheet">
- <link href="../../../css/custom.css" rel="stylesheet">
- <link href="../../../css/v2.css" rel="stylesheet">
- <link href="https://fonts.googleapis.com/css?family=Lato" rel="stylesheet">
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css">
- <link href="../../../extra.css" rel="stylesheet">
-
- <!-- HTML5 shim and Respond.js IE8 support of HTML5 elements and media queries -->
- <!--[if lt IE 9]>
- <script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script>
- <script src="https://oss.maxcdn.com/libs/respond.js/1.3.0/respond.min.js"></script>
- <![endif]-->
-
-
- <script>
- (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
- (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
- m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
- })(window,document,'script','//www.google-analytics.com/analytics.js','ga');
-
- ga('create', 'UA-72162311-1', 'auto');
- ga('send', 'pageview');
- </script>
-
- </head>
-
-
- <body class="newt complete">
-
-
- <div class="container">
- <div class="row v2-main-banner">
- <a class="logo-cell" href="/">
- <img class="logo" src="/img/logo.png">
- </a>
- <div class="tagline-cell">
- <h4 class="tagline">An OS to build, deploy and securely manage billions of devices</h4>
- </div>
- <div class="news-cell">
- <div class="well">
- <h4>Latest News:</h4> <a href="/download">Apache Mynewt 1.0.0-b2</a> released (Feb 15, 2017)
- </div>
- </div>
- </div>
-</div>
-
-
-
-
-
-
-
-
-<nav id="navbar" class="navbar navbar-inverse affix-top" data-spy="affix" data-offset-top="150" role="navigation">
- <div class="container">
- <!-- Collapsed navigation -->
- <div class="navbar-header">
- <!-- Expander button -->
- <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
- <span class="sr-only">Toggle navigation</span>
- <span class="icon-bar"></span>
- <span class="icon-bar"></span>
- <span class="icon-bar"></span>
- </button>
-
- </div>
-
- <!-- Expanded navigation -->
- <div class="navbar-collapse collapse">
- <!-- Main navigation -->
- <ul class="nav navbar-nav navbar-right">
- <li
- class=""
->
- <a href="/"><i class="fa fa-home" style="font-size: larger;"></i></a>
- </li>
- <li
- class="important"
->
- <a href="/quick-start/">Quick Start</a>
- </li>
- <li
- class=""
->
- <a href="/about/">About</a>
- </li>
- <li
- class=""
->
- <a href="/talks/">Talks</a>
- </li>
- <li
- class="active"
->
- <a href="/latest/os/introduction">Documentation</a>
- </li>
- <li
- class=""
->
- <a href="/download/">Download</a>
- </li>
- <li
- class=""
->
- <a href="/community/">Community</a>
- </li>
- <li
- class=""
->
- <a href="/events/">Events</a>
- </li>
- </ul>
-
- <!-- Search, Navigation and Repo links -->
- <ul class="nav navbar-nav navbar-right">
-
- </ul>
- </div>
- </div>
-</nav>
-
-
-
- <div class="container">
-
- <div class="row">
- <div class="col-md-3 v2-sidebar sidebar-container"><div id="docSidebar" class="hidden-print" role="complementary">
- <div class="top">
- <div role="search">
- <form id="rtd-search-form" class="wy-form" action="../../../search.html" method="get">
- <div class="form-group">
- <input type="text" name="q" class="form-control" placeholder="Search documentation" />
- </div>
- </form>
- </div>
- </div>
- <ul class="toc-nav">
- <li class="doc-version">
-<select class="form-control" onchange="if (this.value) window.location.href=this.value">
-
- <option
- value="/develop/os/introduction"
- selected="selected"
- >
- Version: develop (latest)
- </option>
-
- <option
- value="/v0_9_0/os/introduction"
-
- >
- Version: 0.9.0
- </option>
-
-</select>
-</li>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- <li ><a href="../../../os/introduction/">Mynewt Documentation</a>
-
-
- <ul>
-
-
-
-
-
-
-
- <li ><a href="../../../os/get_started/get_started/">Basic Setup</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../../../os/get_started/vocabulary/">Concepts</a>
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../../os/tutorials/tutorials/">Tutorials</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../../os/os_user_guide/">OS User Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../../../network/ble/ble_intro/
-">BLE User Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../newt_intro/">Newt Tool Guide</a>
-
-
- <ul>
-
-
-
-
-
- <li >
- <a href="../../newt_operation/">Newt Theory of Ops</a>
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../newt_ops/">Command Guide</a>
-
-
- <ul>
-
-
-
-
-
- <li >
- <a href="../newt_build/">newt build</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_clean/">newt clean</a>
- </li>
-
-
-
-
-
- <li class="active">
- <a href="./">newt complete</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_create_image/">newt create-image</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_debug/">newt debug</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_help/">newt help</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_info/">newt info</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_install/">newt install</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_load/">newt load</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_mfg/">newt mfg</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_new/">newt new</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_run/">newt run</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_size/">newt size</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_target/">newt target</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_test/">newt test</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_upgrade/">newt upgrade</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_vals/">newt vals</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_version/">newt version</a>
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../../newtmgr/overview/">Newt Manager Guide</a>
-
-
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../../../faq/how_to_edit_docs/
-">Appendix</a>
-
-
- </li>
-
-
-
- </ul>
-</div></div>
-
- <div class="col-md-9" role="main">
- <div class="doc-header">
- <div role="navigation" aria-label="breadcrumbs navigation">
- <ul class="wy-breadcrumbs pull-right">
- <li><a href="/latest/os/introduction">Docs</a></li>
-
-
-
- <li>» <a href="../../newt_intro/">Newt Tool Guide</a></li>
-
-
-
- <li>» <a href="../../newt_ops/">Command Guide</a></li>
-
-
-
- <li>» newt complete</li>
-
-
-
- </ul>
-</div>
- </div>
-
- <h2 id="newt-complete"><font color="#F2853F" style="font-size:24pt">newt complete </font></h2>
-<p>Performs bash autocompletion using tab. It is not intended to be called directly from the command line.</p>
-<h4 id="install-bash-autocompletion">Install bash autocompletion</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ brew install bash-completion
- Updating Homebrew...
- <snip>
- Bash completion has been installed to:
- /usr/local/etc/bash_completion.d
- ==> Summary
- \U0001f37a /usr/local/Cellar/bash-completion/1.3_1: 189 files, 607.8K
-</pre></div>
-
-
-<h4 id="enable-autocompletion-for-newt">Enable autocompletion for newt</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ complete -C "newt complete" newt
-</pre></div>
-
-
-<h4 id="usage">Usage</h4>
-<p>Hit tab and see possible completion options or completed command.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newt target s
- set show
- $ newt target show
-</pre></div>
-
- <div class="row">
-
-
-
-
-<ul class="nav nav-pills" style="margin-bottom: 10px">
- <li>
-
- <a href=../newt_clean/>
- <span class="fa fa-arrow-left"></span>
- Previous: newt clean
- </a>
-
- </li>
- <li class="pull-right">
-
- <a href=../newt_create_image/>
- Next: newt create-image
- <span class="fa fa-arrow-right"></span>
- </a>
-
- </li>
-</ul>
- </div>
- <footer class="row">
- <div class="col-xs-12">
-
- <p class="copyright">Apache Mynewt (incubating) is available under Apache License, version 2.0.</p>
-
- </div>
- <div class="col-xs-12">
- <div class="logos">
- <img src="/img/asf_logo_wide_small.png" alt="Apache" title="Apache">
- <small class="footnote">
- MyNewt is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
- </small>
- <img src="/img/egg-logo2.png" alt="Apache Incubator" title="Apache Incubator">
- </div>
- </div>
-</footer>
- </div>
- </div>
-
-
- </div>
-
- <script src="../../../js/jquery-1.10.2.min.js"></script>
- <script src="../../../js/bootstrap-3.0.3.min.js"></script>
- <script src="../../../js/highlight.pack.js"></script>
- <script src="../../../js/base.js"></script>
- <script src="../../../js/custom.js"></script>
-
- </body>
-</html>
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/command_list/newt_create_image/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/command_list/newt_create_image/index.html b/latest/newt/command_list/newt_create_image/index.html
index 3d0aea4..dbe93a2 100644
--- a/latest/newt/command_list/newt_create_image/index.html
+++ b/latest/newt/command_list/newt_create_image/index.html
@@ -300,14 +300,6 @@
- <li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
<li class="active">
<a href="./">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,41 +504,26 @@
</div>
<h2 id="newt-create-image"><font color="#F2853F" style="font-size:24pt">newt create-image </font></h2>
-<p>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> </p>
+<p>Create and sign an image by adding an image header to the binary file created for a target. Version number in the header is set to <version>. To sign an image provide a .pem file for the signing-key and an optional key-id.</p>
<h4 id="usage">Usage:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt create-image <target-name> <version> [flags]
-</pre></div>
-
-
-<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for target
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt create-image <target-name> <version> [signing-key [key-id]][flags]
</pre></div>
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -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.
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
</pre></div>
<h4 id="description">Description</h4>
-<table>
-<thead>
-<tr>
-<th>Sub-command</th>
-<th>Explanation</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>create-image</td>
-<td>Signs and adds image header to the created binary file for target named <code><target-name></code> and given the version specified as <code><version></code>. The application image generated is <code><app-name>.img</code> where the app-name is the same as the app specified in the target definition. The generated application image can be found in <code>/bin/<target-name>/apps/<app-name>/</code>. <br> <br> A build manifest file <code>manifest.json</code> 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.</td>
-</tr>
-</tbody>
-</table>
+<p>Adds an image header to the created binary file for the <code>target-name</code> target. The image version is set to <code>version</code>. It creates a <code><app-name>.img</code> file for the image, where <code>app-name</code> is the value specified in the target <code>app</code> variable, and stores the file in the '/bin/targets/<target-name>/app/apps/<app-name>/' directory. A <code>manifest.json</code> build manifest file 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.</p>
+<p>To sign an image, provide a .pem file for the <code>signing-key</code> and an optional <code>key-id</code>. <code>key-id</code> must be a value between 0-255.</p>
<h4 id="examples">Examples</h4>
<table>
<thead>
@@ -542,9 +535,14 @@
</thead>
<tbody>
<tr>
-<td>create-image</td>
+<td></td>
<td>newt create-image myble2 1.0.1.0</td>
-<td>Creates a signed image for target <code>myble2</code> and assigns it the version <code>1.0.1.0</code>. <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 <code>bin/myble2/apps/bletiny/bletiny.img</code> and the manifest is <code>bin/myble2/apps/bletiny/manifest.json</code></td>
+<td>Creates an image for target <code>myble2</code> and assigns it version <code>1.0.1.0</code>. <br> <br> For the following target definition: <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> the created image is 'bin/targets/myble2/app/apps/bletiny/bletiny.img' and the manifest is 'bin/targets/myble2/app/apps/bletiny/manifest.json'</td>
+</tr>
+<tr>
+<td></td>
+<td>newt create-image myble2 1.0.1.0 private.pem</td>
+<td>Creates an image for target <code>myble2</code> and assigns it the version <code>1.0.1.0</code>. Signs the image using private key specified by the private.pem file.</td>
</tr>
</tbody>
</table>
@@ -557,9 +555,9 @@
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../newt_complete/>
+ <a href=../newt_clean/>
<span class="fa fa-arrow-left"></span>
- Previous: newt complete
+ Previous: newt clean
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/command_list/newt_debug/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/command_list/newt_debug/index.html b/latest/newt/command_list/newt_debug/index.html
index ac9e3e2..8e88054 100644
--- a/latest/newt/command_list/newt_debug/index.html
+++ b/latest/newt/command_list/newt_debug/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,41 +504,31 @@
</div>
<h2 id="newt-debug"><font color="#F2853F" style="font-size:24pt">newt debug </font></h2>
-<p>Opens debugger session for specified target. </p>
+<p>Open a debugger session to a target. </p>
<h4 id="usage">Usage:</h4>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt debug <target-name> [flag]
</pre></div>
<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for target
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> --extrajtagcmd string Extra commands to send to JTAG software
+ -n, --noGDB Do not start GDB from command line
</pre></div>
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -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.
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
</pre></div>
<h4 id="description">Description</h4>
-<table>
-<thead>
-<tr>
-<th>Sub-command</th>
-<th>Explanation</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>debug</td>
-<td>Opens the appropriate debugging session for the image built for the named target.</td>
-</tr>
-</tbody>
-</table>
+<p>Opens a debugger session to the image built for the <target-name> target.</p>
<h4 id="examples">Examples</h4>
<table>
<thead>
@@ -542,9 +540,14 @@
</thead>
<tbody>
<tr>
-<td>debug</td>
+<td></td>
<td>newt debug myble2</td>
-<td>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</td>
+<td>Opens a J-Link connection and starts a GNU gdb session to debug bin/targets/myble2/app/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</td>
+</tr>
+<tr>
+<td></td>
+<td>newt debug myble2 -n</td>
+<td>Opens a J-Link connection bin/targets/myble2/app/apps/bletiny/bletiny.elf but do not start GDB on the command line.</td>
</tr>
</tbody>
</table>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/command_list/newt_help/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/command_list/newt_help/index.html b/latest/newt/command_list/newt_help/index.html
index 33ffb75..be61654 100644
--- a/latest/newt/command_list/newt_help/index.html
+++ b/latest/newt/command_list/newt_help/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,7 +504,7 @@
</div>
<h2 id="newt-help"><font color="#F2853F" style="font-size:24pt">newt help </font></h2>
-<p>Displays the help text for the newt command line tool:</p>
+<p>Display the help text for the newt command line tool:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">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
@@ -507,35 +515,40 @@ https://mynewt.apache.org/.
<h4 id="usage">Usage:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt help [input1]
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt help [command]
</pre></div>
-<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for newt
+<h4 id="global-flags">Global Flags:</h4>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (default "WARN")
-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.
+ -q, --quiet Be quiet; only display error output
+ -s, --silent Be silent; don't output anything
+ -v, --verbose Enable verbose output when executing commands
</pre></div>
<h4 id="available-commands">Available Commands:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> version Display the Newt version number.
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> build Build one or more targets
+ clean Delete build artifacts for one or more targets
+ create-image Add image header to target binary
+ debug Open debugger session to target
+ info Show project info
install Install project dependencies
- upgrade Upgrade project dependencies
+ load Load built target to board
+ mfg Manufacturing flash image commands
new Create a new project
- info Show project info
+ pkg Create and manage packages in the current workspace
+ run build/create-image/download/debug <target>
+ size Size of target components
+ sync Synchronize project dependencies
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>
+ upgrade Upgrade project dependencies
+ vals Display valid values for the specified element type(s)
+ version Display the Newt version number
</pre></div>
@@ -550,12 +563,12 @@ https://mynewt.apache.org/.
</thead>
<tbody>
<tr>
-<td>help</td>
+<td></td>
<td>newt help target</td>
-<td>Displays the help text for the newt command 'target'</td>
+<td>Displays the help text for the newt <code>target</code> command</td>
</tr>
<tr>
-<td>help</td>
+<td></td>
<td>newt help</td>
<td>Displays the help text for newt tool</td>
</tr>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/command_list/newt_info/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/command_list/newt_info/index.html b/latest/newt/command_list/newt_info/index.html
index 195aa08..065046b 100644
--- a/latest/newt/command_list/newt_info/index.html
+++ b/latest/newt/command_list/newt_info/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,36 +504,25 @@
</div>
<h2 id="newt-info"><font color="#F2853F" style="font-size:24pt">newt info </font></h2>
-<p>Shows information about the current project.</p>
+<p>Show information about the current project.</p>
<h4 id="usage">Usage:</h4>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt info [flags]
</pre></div>
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -l, --loglevel="WARN": Log level, defaults to WARN.
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (default "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.
+ -q, --quiet Be quiet; only display error output
+ -s, --silent Be silent; don't output anything
+ -v, --verbose Enable verbose output when executing commands
</pre></div>
<h4 id="description">Description</h4>
-<table>
-<thead>
-<tr>
-<th>Sub-command</th>
-<th>Explanation</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>info</td>
-<td>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.</td>
-</tr>
-</tbody>
-</table>
+<p>Displays the repositories in the current project (the local as well as all the external repositories fetched). It also displays the packages in the local repository.</p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/command_list/newt_install/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/command_list/newt_install/index.html b/latest/newt/command_list/newt_install/index.html
index 00391fd..c911912 100644
--- a/latest/newt/command_list/newt_install/index.html
+++ b/latest/newt/command_list/newt_install/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,42 +504,31 @@
</div>
<h2 id="newt-install"><font color="#F2853F" style="font-size:24pt">newt install </font></h2>
-<p>Install project dependencies. </p>
+<p>Install project dependencies. </p>
<h4 id="usage">Usage:</h4>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt install [flags]
</pre></div>
<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -f, --force Force install of the repositories in project, regardless of what exists in repos directory
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -f, --force Force install of the repositories in project, regardless of what exists in repos directory
</pre></div>
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for newt
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (default "WARN")
-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.
+ -q, --quiet Be quiet; only display error output
+ -s, --silent Be silent; don't output anything
+ -v, --verbose Enable verbose output when executing commands
</pre></div>
<h4 id="description">Description</h4>
-<table>
-<thead>
-<tr>
-<th>Sub-command</th>
-<th>Explanation</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>install</td>
-<td>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 <code>cd</code> into the app directory after creating a new app using <code>newt new</code>) before running <code>newt install</code>.</td>
-</tr>
-</tbody>
-</table>
+<p>This command downloads the description for all the repositories specified in the <code>project.yml</code> file for the current project, and installs the correct versions of all the packages specified by the project dependencies. </p>
+<p>You must run this command from within the current project directory. (Remember to <code>cd</code> into this project directory after you use <code>newt new</code> to create this project before you run <code>newt install</code>.)</p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/command_list/newt_load/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/command_list/newt_load/index.html b/latest/newt/command_list/newt_load/index.html
index e38539a..4572222 100644
--- a/latest/newt/command_list/newt_load/index.html
+++ b/latest/newt/command_list/newt_load/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,41 +504,30 @@
</div>
<h2 id="newt-load"><font color="#F2853F" style="font-size:24pt">newt load </font></h2>
-<p>Load app image to specified target. </p>
+<p>Load application image onto the board for a target. </p>
<h4 id="usage">Usage:</h4>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt load <target-name> [flags]
</pre></div>
<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for target
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> --extrajtagcmd string Extra commands to send to JTAG software
</pre></div>
-<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -l, --loglevel="WARN": Log level, defaults to WARN.
+<h3 id="global-flags">Global Flags:</h3>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (default "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.
+ -q, --quiet Be quiet; only display error output
+ -s, --silent Be silent; don't output anything
+ -v, --verbose Enable verbose output when executing commands
</pre></div>
<h4 id="description">Description</h4>
-<table>
-<thead>
-<tr>
-<th>Sub-command</th>
-<th>Explanation</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>load</td>
-<td>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 <code>Can not connect to J-Link via USB</code> or <code>Unspecified error -1</code>.</td>
-</tr>
-</tbody>
-</table>
+<p>Uses download scripts to automatically load, onto the connected board, the image built for the app defined by the <code>target-name</code> target If the wrong board is connected or the target definition is incorrect (i.e. the wrong values are given for bsp or app), the command will fail with error messages such as <code>Can not connect to J-Link via USB</code> or <code>Unspecified error -1</code>. </p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/command_list/newt_mfg/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/command_list/newt_mfg/index.html b/latest/newt/command_list/newt_mfg/index.html
index ca63b04..bfb0644 100644
--- a/latest/newt/command_list/newt_mfg/index.html
+++ b/latest/newt/command_list/newt_mfg/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,7 +504,7 @@
</div>
<h2 id="newt-mfg"><font color="#F2853F" style="font-size:24pt">newt mfg </font></h2>
-<p>Provides commands to create, build, and upload manufacturing image. </p>
+<p>Commands to create, build, and upload manufacturing image. </p>
<h4 id="usage">Usage:</h4>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt mfg [flags]
newt mfg [command]
@@ -505,22 +513,19 @@
<h4 id="available-commands">Available Commands:</h4>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> create Create a manufacturing flash image
- deploy Builds and uploads a manufacturing image (build + load)
+ deploy Build and upload a manufacturing image (build + load)
load Load a manufacturing flash image onto a device
</pre></div>
-<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for mfg
-</pre></div>
-
-
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -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.
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
</pre></div>
@@ -535,7 +540,7 @@
<tbody>
<tr>
<td>create</td>
-<td>A manufacturing image specifies 1) a boot loader target, and 2) one or more image targets. Assuming the manufacturing entity has been created and defined in the <code>mfgs/<mfg image name>/</code> package(see Examples below), this command collects the manufacturing related files in the newly created <code>bin/mfgs/<mfg image name></code> directory. The collection includes manifests with the image build time, version, manufacturing package build time, image ID (or hash) etc. It is essentially a snapshot of the image data and metadata uploaded to the device flash at manufacturing time. Note that the command expects the targets and images to have already been built using <code>newt build</code> and <code>newt create-image</code> commands.</td>
+<td>A manufacturing image specifies 1) a boot loader target, and 2) one or more image targets. Assuming the manufacturing entity has been created and defined in the <code>mfgs/<mfg image name>/</code> package (see Examples below), this command collects the manufacturing related files in the newly created <code>bin/mfgs/<mfg image name></code> directory. The collection includes manifests with the image build time, version, manufacturing package build time, image ID (or hash) etc. It is essentially a snapshot of the image data and metadata uploaded to the device flash at manufacturing time. Note that the command expects the targets and images to have already been built using <code>newt build</code> and <code>newt create-image</code> commands.</td>
</tr>
<tr>
<td>deploy</td>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/command_list/newt_new/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/command_list/newt_new/index.html b/latest/newt/command_list/newt_new/index.html
index 9afbe76..6870d8f 100644
--- a/latest/newt/command_list/newt_new/index.html
+++ b/latest/newt/command_list/newt_new/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,27 +504,25 @@
</div>
<h2 id="newt-new"><font color="#F2853F" style="font-size:24pt">newt new </font></h2>
-<p>Create a new application, specified by <app-name>, from a given skeleton. Currently, the default skeleton is the <a href="https://git-wip-us.apache.org/repos/asf/incubator-mynewt-blinky.git">blinky repository</a> in Apache Mynewt (or <a href="https://github.com/apache/incubator-mynewt-blinky">https://github.com/apache/incubator-mynewt-blinky</a> on its github mirror.)</p>
+<p>Create a new project from a skeleton. Currently, the default skeleton is the <a href="https://git-wip-us.apache.org/repos/asf/incubator-mynewt-blinky.git">blinky repository</a> in Apache Mynewt (or <a href="https://github.com/apache/incubator-mynewt-blinky">https://github.com/apache/incubator-mynewt-blinky</a> on its github mirror.)</p>
<h4 id="usage">Usage:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt new [flags] <app-name>
-</pre></div>
-
-
-<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for new
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt new <project-name> [flags]
</pre></div>
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for newt
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (default "WARN")
-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.
+ -q, --quiet Be quiet; only display error output
+ -s, --silent Be silent; don't output anything
+ -v, --verbose Enable verbose output when executing commands
</pre></div>
+<h3 id="description">Description</h3>
+<p>Creates a new project named <code>project-name</code> from the default skeleton <a href="https://git-wip-us.apache.org/repos/asf/incubator-mynewt-blinky.git">blinky repository</a> in Apache Mynewt (or <a href="https://github.com/apache/incubator-mynewt-blinky">https://github.com/apache/incubator-mynewt-blinky</a> on its github mirror.)</p>
<h4 id="examples">Examples</h4>
<table>
<thead>
@@ -528,9 +534,9 @@
</thead>
<tbody>
<tr>
-<td>newt new</td>
+<td></td>
<td>newt new test_project</td>
-<td>Creates a new app named "test_project " using the default skeleton from the <code>apache/incubator-mynewt-blinky</code> repo.</td>
+<td>Creates a new project named <code>test_project</code> using the default skeleton from the <code>apache/incubator-mynewt-blinky</code> repository.</td>
</tr>
</tbody>
</table>
@@ -551,8 +557,8 @@
</li>
<li class="pull-right">
- <a href=../newt_run/>
- Next: newt run
+ <a href=../newt_pkg/>
+ Next: newt pkg
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/command_list/newt_pkg/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/command_list/newt_pkg/index.html b/latest/newt/command_list/newt_pkg/index.html
new file mode 100644
index 0000000..967abc8
--- /dev/null
+++ b/latest/newt/command_list/newt_pkg/index.html
@@ -0,0 +1,648 @@
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <meta charset="utf-8">
+ <meta http-equiv="X-UA-Compatible" content="IE=edge">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+
+ <!-- This is broken by doc revisioning.
+ <link rel="canonical" href="http://mynewt.apache.org/newt/command_list/newt_pkg/"> -->
+ <link rel="shortcut icon" href="../../../img/favicon.ico">
+
+ <title>newt pkg - Apache Mynewt</title>
+
+ <link href="../../../css/bootstrap-3.0.3.min.css" rel="stylesheet">
+ <link rel="stylesheet" href="../../../css/highlight.css">
+ <link href="../../../css/base.css" rel="stylesheet">
+ <link href="../../../css/custom.css" rel="stylesheet">
+ <link href="../../../css/v2.css" rel="stylesheet">
+ <link href="https://fonts.googleapis.com/css?family=Lato" rel="stylesheet">
+ <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css">
+ <link href="../../../extra.css" rel="stylesheet">
+
+ <!-- HTML5 shim and Respond.js IE8 support of HTML5 elements and media queries -->
+ <!--[if lt IE 9]>
+ <script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script>
+ <script src="https://oss.maxcdn.com/libs/respond.js/1.3.0/respond.min.js"></script>
+ <![endif]-->
+
+
+ <script>
+ (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
+ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
+ m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
+ })(window,document,'script','//www.google-analytics.com/analytics.js','ga');
+
+ ga('create', 'UA-72162311-1', 'auto');
+ ga('send', 'pageview');
+ </script>
+
+ </head>
+
+
+ <body class="newt pkg">
+
+
+ <div class="container">
+ <div class="row v2-main-banner">
+ <a class="logo-cell" href="/">
+ <img class="logo" src="/img/logo.png">
+ </a>
+ <div class="tagline-cell">
+ <h4 class="tagline">An OS to build, deploy and securely manage billions of devices</h4>
+ </div>
+ <div class="news-cell">
+ <div class="well">
+ <h4>Latest News:</h4> <a href="/download">Apache Mynewt 1.0.0-b2</a> released (Feb 15, 2017)
+ </div>
+ </div>
+ </div>
+</div>
+
+
+
+
+
+
+
+
+<nav id="navbar" class="navbar navbar-inverse affix-top" data-spy="affix" data-offset-top="150" role="navigation">
+ <div class="container">
+ <!-- Collapsed navigation -->
+ <div class="navbar-header">
+ <!-- Expander button -->
+ <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
+ <span class="sr-only">Toggle navigation</span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ </button>
+
+ </div>
+
+ <!-- Expanded navigation -->
+ <div class="navbar-collapse collapse">
+ <!-- Main navigation -->
+ <ul class="nav navbar-nav navbar-right">
+ <li
+ class=""
+>
+ <a href="/"><i class="fa fa-home" style="font-size: larger;"></i></a>
+ </li>
+ <li
+ class="important"
+>
+ <a href="/quick-start/">Quick Start</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/about/">About</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/talks/">Talks</a>
+ </li>
+ <li
+ class="active"
+>
+ <a href="/latest/os/introduction">Documentation</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/download/">Download</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/community/">Community</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/events/">Events</a>
+ </li>
+ </ul>
+
+ <!-- Search, Navigation and Repo links -->
+ <ul class="nav navbar-nav navbar-right">
+
+ </ul>
+ </div>
+ </div>
+</nav>
+
+
+
+ <div class="container">
+
+ <div class="row">
+ <div class="col-md-3 v2-sidebar sidebar-container"><div id="docSidebar" class="hidden-print" role="complementary">
+ <div class="top">
+ <div role="search">
+ <form id="rtd-search-form" class="wy-form" action="../../../search.html" method="get">
+ <div class="form-group">
+ <input type="text" name="q" class="form-control" placeholder="Search documentation" />
+ </div>
+ </form>
+ </div>
+ </div>
+ <ul class="toc-nav">
+ <li class="doc-version">
+<select class="form-control" onchange="if (this.value) window.location.href=this.value">
+
+ <option
+ value="/develop/os/introduction"
+ selected="selected"
+ >
+ Version: develop (latest)
+ </option>
+
+ <option
+ value="/v0_9_0/os/introduction"
+
+ >
+ Version: 0.9.0
+ </option>
+
+</select>
+</li>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ <li ><a href="../../../os/introduction/">Mynewt Documentation</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../../../os/get_started/get_started/">Basic Setup</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../../os/get_started/vocabulary/">Concepts</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../os/tutorials/tutorials/">Tutorials</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../os/os_user_guide/">OS User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../../network/ble/ble_intro/
+">BLE User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../newt_intro/">Newt Tool Guide</a>
+
+
+ <ul>
+
+
+
+
+
+ <li >
+ <a href="../../newt_operation/">Newt Theory of Ops</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../newt_ops/">Command Guide</a>
+
+
+ <ul>
+
+
+
+
+
+ <li >
+ <a href="../newt_build/">newt build</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_clean/">newt clean</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_create_image/">newt create-image</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_debug/">newt debug</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_help/">newt help</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_info/">newt info</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_install/">newt install</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_load/">newt load</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_mfg/">newt mfg</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_new/">newt new</a>
+ </li>
+
+
+
+
+
+ <li class="active">
+ <a href="./">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_run/">newt run</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_size/">newt size</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_target/">newt target</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_test/">newt test</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_upgrade/">newt upgrade</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_vals/">newt vals</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_version/">newt version</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../newtmgr/overview/">Newt Manager Guide</a>
+
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../../faq/how_to_edit_docs/
+">Appendix</a>
+
+
+ </li>
+
+
+
+ </ul>
+</div></div>
+
+ <div class="col-md-9" role="main">
+ <div class="doc-header">
+ <div role="navigation" aria-label="breadcrumbs navigation">
+ <ul class="wy-breadcrumbs pull-right">
+ <li><a href="/latest/os/introduction">Docs</a></li>
+
+
+
+ <li>» <a href="../../newt_intro/">Newt Tool Guide</a></li>
+
+
+
+ <li>» <a href="../../newt_ops/">Command Guide</a></li>
+
+
+
+ <li>» newt pkg</li>
+
+
+
+ </ul>
+</div>
+ </div>
+
+ <h2 id="newt-pkg"><font color="#F2853F" style="font-size:24pt">newt pkg </font></h2>
+<p>Commands for creating and manipulating packages.</p>
+<h4 id="usage">Usage:</h4>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt pkg [command] [flags]
+</pre></div>
+
+
+<h4 id="flags">Flags:</h4>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -t, --type string Type of package to create: pkg, bsp, sdk. (default "pkg")
+</pre></div>
+
+
+<h4 id="global-flags">Global Flags:</h4>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
+</pre></div>
+
+
+<h4 id="description">Description</h4>
+<p>The pkg command provides subcommands to create and manage packages. The subcommands take one or two <code>package-name</code> arguments.</p>
+<table>
+<thead>
+<tr>
+<th>Sub-command</th>
+<th>Explanation</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>copy</td>
+<td>The copy <src-pkg> <dst-pkg> command creates the new <code>dst-pkg</code> package by cloning the <code>src-pkg</code> package.</td>
+</tr>
+<tr>
+<td>move</td>
+<td>The move <old-pkg> <new-pkg> command moves the <code>old-pkg</code> package to the <code>new-pkg</code> package.</td>
+</tr>
+<tr>
+<td>new</td>
+<td>The new <new-pkg> command creates a new package named <code>new-pkg</code>, from a template, in the current directory. You can create a package of type <code>pkg</code>, <code>bsp</code>, or <code>sdk</code>. The default package type is <code>pkg</code>. You use the -t flag to specify a different package type.</td>
+</tr>
+<tr>
+<td>remove</td>
+<td>The remove <my-pkg> command deletes the <code>my-pkg</code> package.</td>
+</tr>
+</tbody>
+</table>
+<h4 id="examples">Examples</h4>
+<table>
+<thead>
+<tr>
+<th>Sub-command</th>
+<th>Usage</th>
+<th>Explanation</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>copy</td>
+<td>newt pkg copy <br>apps/bletiny apps/new_bletiny</td>
+<td>Copies the <code>apps/bletiny</code> package to the <code>apps/new_bletiny</code>.</td>
+</tr>
+<tr>
+<td>move</td>
+<td>newt pkg move <br>apps/slinky apps/new_slinky</td>
+<td>Moves the <code>apps/slinky</code> package to the <code>apps/new_slinky</code> package.</td>
+</tr>
+<tr>
+<td>new</td>
+<td>newt pkg new apps/new_slinky</td>
+<td>Creates a package named <code>apps/new_slinky</code> of type <code>pkg</code> in the current directory.</td>
+</tr>
+<tr>
+<td>new</td>
+<td>newt pkg new hw/bsp/myboard -t bsp</td>
+<td>Creates a package named <code>hw/bsp/myboard</code> of type <code>bsp</code> in the current directory.</td>
+</tr>
+<tr>
+<td>remove</td>
+<td>newt pkg remove hw/bsp/myboard</td>
+<td>Removes the <code>hw/bsp/myboard</code> package.</td>
+</tr>
+</tbody>
+</table>
+
+ <div class="row">
+
+
+
+
+<ul class="nav nav-pills" style="margin-bottom: 10px">
+ <li>
+
+ <a href=../newt_new/>
+ <span class="fa fa-arrow-left"></span>
+ Previous: newt new
+ </a>
+
+ </li>
+ <li class="pull-right">
+
+ <a href=../newt_run/>
+ Next: newt run
+ <span class="fa fa-arrow-right"></span>
+ </a>
+
+ </li>
+</ul>
+ </div>
+ <footer class="row">
+ <div class="col-xs-12">
+
+ <p class="copyright">Apache Mynewt (incubating) is available under Apache License, version 2.0.</p>
+
+ </div>
+ <div class="col-xs-12">
+ <div class="logos">
+ <img src="/img/asf_logo_wide_small.png" alt="Apache" title="Apache">
+ <small class="footnote">
+ MyNewt is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
+ </small>
+ <img src="/img/egg-logo2.png" alt="Apache Incubator" title="Apache Incubator">
+ </div>
+ </div>
+</footer>
+ </div>
+ </div>
+
+
+ </div>
+
+ <script src="../../../js/jquery-1.10.2.min.js"></script>
+ <script src="../../../js/bootstrap-3.0.3.min.js"></script>
+ <script src="../../../js/highlight.pack.js"></script>
+ <script src="../../../js/base.js"></script>
+ <script src="../../../js/custom.js"></script>
+
+ </body>
+</html>
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/command_list/newt_run/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/command_list/newt_run/index.html b/latest/newt/command_list/newt_run/index.html
index 388f6a5..c32ef89 100644
--- a/latest/newt/command_list/newt_run/index.html
+++ b/latest/newt/command_list/newt_run/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -372,6 +364,14 @@
+ <li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
<li class="active">
<a href="./">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,42 +504,32 @@
</div>
<h2 id="newt-run"><font color="#F2853F" style="font-size:24pt">newt run </font></h2>
-<p>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.</p>
-<p><strong>Note</strong>: If version number is omitted, create-image step is skipped</p>
+<p>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 the board.</p>
+<p><strong>Note</strong>: If the version number is omitted, the create-image step is skipped.</p>
<h4 id="usage">Usage:</h4>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt run <target-name> [<version>][flags]
</pre></div>
<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for target
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> --extrajtagcmd string Extra commands to send to JTAG software
+ -n, --noGDB Do not start GDB from the command line
</pre></div>
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -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.
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
</pre></div>
<h4 id="description">Description</h4>
-<table>
-<thead>
-<tr>
-<th>Sub-command</th>
-<th>Explanation</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>run</td>
-<td>Same as running <code>build <target></code>, <code>create-image <target> <version></code>, <code>load <target></code>, and <code>debug <target></code>.</td>
-</tr>
-</tbody>
-</table>
+<p>Same as running <code>build <target-name></code>, <code>create-image <target-name> <version></code>, <code>load <target-name></code>, and <code>debug <target-name></code>.</p>
<h4 id="examples">Examples</h4>
<table>
<thead>
@@ -543,14 +541,14 @@
</thead>
<tbody>
<tr>
-<td>run</td>
+<td></td>
<td>newt run blink_rigado</td>
-<td>First compiles and builds executable for running the app defined in the target <code>blink_rigado</code> 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.</td>
+<td>Compiles and builds the image for the <code>app</code> and the <code>bsp</code> defined for target <code>blink_rigado</code>, loads the image onto the board, and opens an active GNU gdb debugging session to run the image.</td>
</tr>
<tr>
-<td>run</td>
+<td></td>
<td>newt run ble_rigado 0.1.0.0</td>
-<td>First compiles and builds executable for running the app defined in the target <code>ble_rigado</code> 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.</td>
+<td>Compiles and builds the image for the <code>app</code> and the <code>bsp</code> defined for target <code>ble_rigado</code>, signs and creates the image with version number 0.1.0.0, loads the image onto the board, and 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.</td>
</tr>
</tbody>
</table>
@@ -563,9 +561,9 @@
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../newt_new/>
+ <a href=../newt_pkg/>
<span class="fa fa-arrow-left"></span>
- Previous: newt new
+ Previous: newt pkg
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/latest/newt/command_list/newt_size/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/command_list/newt_size/index.html b/latest/newt/command_list/newt_size/index.html
index 4cec911..416c8a2 100644
--- a/latest/newt/command_list/newt_size/index.html
+++ b/latest/newt/command_list/newt_size/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,26 +504,31 @@
</div>
<h2 id="newt-size"><font color="#F2853F" style="font-size:24pt">newt size </font></h2>
-<p>Calculate the size of target components specified by <target-name></p>
+<p>Calculates the size of target components for a target.</p>
<h4 id="usage">Usage:</h4>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt size <target-name> [flags]
</pre></div>
<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for target
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -F, --flash Print FLASH statistics
+ -R, --ram Print RAM statistics
</pre></div>
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -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.
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
</pre></div>
+<h4 id="description">Description</h4>
+<p>Displays the RAM and FLASH size of each component for the <code>target-name</code> target. </p>
<h4 id="examples">Examples</h4>
<table>
<thead>
@@ -527,13 +540,13 @@
</thead>
<tbody>
<tr>
-<td>size</td>
+<td></td>
<td>newt size blink_rigado</td>
-<td>Inspects and lists the RAM and Flash memory use by each component (object files and libraries) of the target.</td>
+<td>Inspects and lists the RAM and Flash memory that each component (object files and libraries) for the <code>blink_rigado</code> target.</td>
</tr>
</tbody>
</table>
-<h4 id="example-output-for-newt-size-boot_olimex">Example output for <code>newt size boot_olimex</code>:</h4>
+<h4 id="example-output-for-newt-size-blink_rigado">Example output for <code>newt size blink_rigado</code>:</h4>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt size blink_rigado
FLASH RAM
9 223 *fill*
@@ -572,8 +585,8 @@ objsize
</li>
<li class="pull-right">
- <a href=../newt_target/>
- Next: newt target
+ <a href=../newt_sync/>
+ Next: newt sync
<span class="fa fa-arrow-right"></span>
</a>
[6/7] incubator-mynewt-site git commit: Update newt command
documentation, sysconfig overwrites, events, bsp list
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/mkdocs/search_index.json
----------------------------------------------------------------------
diff --git a/develop/mkdocs/search_index.json b/develop/mkdocs/search_index.json
index 1f1695e..84d2e36 100644
--- a/develop/mkdocs/search_index.json
+++ b/develop/mkdocs/search_index.json
@@ -7937,7 +7937,7 @@
},
{
"location": "/os/modules/sysinitconfig/sysconfig_error/",
- "text": "Validation and Error Messages\n\n\nWith multiple packages defining and overriding system configuration settings, it \nis easy to introduce conflicts and violations that are difficult to find. The \n\nnewt build \ntarget-name\n command validates the setting definitions and value \noverrides for all the packages in the target to ensure a valid and consistent build.\nIt aborts the build when it detects violations or ambiguities between packages.\n\nThe following sections describe the error conditions that newt detects and \nthe error messages that it outputs. For most errors, newt also outputs \nthe \nSetting history\n with the order of package overrides to help \nyou resolve the errors.\n\n\nNote:\n The \nnewt target config \ntarget-name\n command also detects \nerrors and outputs error messages at the top of the command output. \nThe command outputs the package setting definitions and values after it \noutputs the error messages. It is easy to miss the error mes
sages at the top. \n\n\nValue Override Violations\n\n\nThe newt tool uses package priorities to resolve override conflicts. It uses \nthe value override from the highest priority package when multiple \npackages override the same setting. Newt checks for the following \noverride violations:\n\n\n\n\nAmbiguity Violation - Two packages of the same priority override a setting with \ndifferent values. And no higher priority package overrides the setting.\n\n\nPriority Violation - A package overrides a setting defined by a package with higher or \nequal priority. \n\n\n\n\nExample: Ambiguity Violation Error Message\n\n\nThe following example shows the error message that newt outputs for an ambiguity violation:\n\n\nError: Syscfg ambiguities detected:\n Setting: LOG_NEWTMGR, Packages: [apps/slinky, apps/splitty]\nSetting history (newest -\n oldest):\n LOG_NEWTMGR: [apps/splitty:0, apps/slinky:1, sys/log/full:0]\n\n\n\n\n\nThe above error occurs because the \napps/slinky\n and \napps
/splitty\n packages \nin the split image target both override the same setting with different \nvalues. The \napps/slinky\n package sets the \nsys/log/full\n package \nLOG_NEWTMGR\n \nsetting to 1, and the \napps/splitty\n package sets the setting to 0. The \noverrides are ambiguous because both are \napp\n packages and \nhave the same priority. The following are excerpts of the defintion \nand the two overrides from the \nsyscfg.yml\n files that cause the error:\n\n\n#Package: sys/log/full\nsyscfg.defs:\n LOG_NEWTMGR:\n description: \nEnables or disables newtmgr command tool logging\n\n value: 0\n\n#Package: apps/slinky\nsyscfg.vals:\n LOG_NEWTMGR: 1\n\n#Package: apps/splitty\nsyscfg.vals:\n LOG_NEWTMGR: 0\n\n\n\n\n\nExample: Priority Violation Error Message\n\n\nThe following example shows the error message that newt outputs for a priority violation \nwhere a package tries to change the setting that was defined by another package at \nthe same priority lev
el:\n\n\nError: Priority violations detected (Packages can only override settings defined by packages of lower priority):\n Package: mgmt/newtmgr overriding setting: LOG_NEWTMGR defined by sys/log/full\n\nSetting history (newest -\n oldest):\n LOG_NEWTMGR: [sys/log/full:0]\n\n\n\n\n\nThe above error occurs because the \nmgmt/newtmgr\n lib package \noverrides the \nLOG_NEWTMGR\n setting that the \nsys/log/full\n lib package \ndefines. The following are excerpts of the definition and the override from the \n\nsyscfg.yml\n files that cause this error: \n\n\n#Package: sys/log/full\nsyscfg.defs:\n LOG_NEWTMGR:\n description: \nEnables or disables newtmgr command tool logging\n\n value: 0\n\n#Package: mgmt/newtmgr\nsyscfg.vals:\n LOG_NEWTMGR: 1\n\n\n\n\n\n\n\nFlash Area Violations\n\n\nFor \nflash_owner\n type setting definitions, newt checks \nfor the following violations:\n\n\n\n\nAn undefined flash area is assigned to a setting.\n\n\nA flash area is assigned
to multiple settings.\n\n\n\n\nExample: Undefined Flash Area Error Message\n\n\nThe following example shows the error message that newt outputs for an undefined flash area.\n\n\nBuilding target targets/sim_slinky\nError: Flash errors detected:\n Setting REBOOT_LOG_FLASH_AREA specifies unknown flash area: FLASH_AREA_NOEXIST\n\nSetting history (newest -\n oldest):\n REBOOT_LOG_FLASH_AREA: [hw/bsp/native:FLASH_AREA_NOEXIST, sys/reboot:]\n\n\n\n\n\nThe above error occurs because the \nhw/bsp/native\n package assigns the \nundefined \nFLASH_AREA_NOEXIST\n flash area to the \nsys/reboot\n package \n\nREBOOT_LOG_FLASH_AREA\n setting. The following are excerpts of the definition \nand the override from the \nsyscfg.yml\n files that cause the error:\n\n\n#Package: sys/reboot\nsyscfg.defs:\n REBOOT_LOG_FLASH_AREA:\n description: \nFlash Area to use for reboot log.\n\n type: flash_owner\n value:\n\n#Package: hw/bsp/native\nsyscfg.vals:\n REBOOT_LOG_FLASH_AREA:
FLASH_AREA_NOEXIST\n\n\n\n\n\nExample: Multiple Flash Area Assignment Error Message\n\n\nThe following example shows the error message that newt outputs when multiple \nsettings are assigned the same flash area:\n\n\nError: Flash errors detected:\n Multiple flash_owner settings specify the same flash area\n settings: REBOOT_LOG_FLASH_AREA, CONFIG_FCB_FLASH_AREA\n flash area: FLASH_AREA_NFFS\n\nSetting history (newest -\n oldest):\n CONFIG_FCB_FLASH_AREA: [hw/bsp/native:FLASH_AREA_NFFS, sys/config:]\n REBOOT_LOG_FLASH_AREA: [apps/slinky:FLASH_AREA_NFFS, sys/reboot:]\n\n\n\n\n\nThe above error occurs because the \nhw/bsp/native\n package assigns \nthe \nFLASH_AREA_NFFS\n flash area to the \nsys/config/\n package \n\nCONFIG_FCB_FLASH_AREA\n setting, and the \napps/slinky\n package \nalso assigns \nFLASH_AREA_NFFS\n to the \nsys/reboot\n package \n\nREBOOT_LOG_FLASH_AREA\n setting. The following are excerpts of the \ntwo definitions and the two overrides from
the \nsyscfg.yml\n files \nthat cause the error:\n\n\n# Package: sys/config\nsyscfg.defs.CONFIG_FCB:\n CONFIG_FCB_FLASH_AREA:\n description: \nThe flash area for the Config Flash Circular Buffer\n\n type: \nflash_owner\n\n value:\n\n# Package: sys/reboot\nsyscfg.defs:\n REBOOT_LOG_FLASH_AREA:\n description: \nThe flash area for the reboot log\n\n type: \nflash_owner\n \n value:\n\n#Package: hw/bsp/native\nsyscfg.vals:\n CONFIG_FCB_FLASH_AREA: FLASH_AREA_NFFS\n\n#Package: apps/slinky\nsyscfg.vals: \n REBOOT_LOG_FLASH_AREA: FLASH_AREA_NFFS\n\n\n\n\n\n\n\nRestriction Violations\n\n\nFor setting definitions with \nrestrictions\n specified, newt checks for \nthe following violations:\n\n\n\n\nA setting with a \n$notnull\n restriction does not have a value. \n\n\nFor a setting with expression restrictions, some required setting \nvalues in the expressions evaluate to false. \n\n\n\n\nExample: $notnull Restriction Violation Error Messa
ge\n\n\nThe following example shows the error message that newt outputs when\na setting with \n$notnull\n restriction does not have a value:\n\n\nError: Syscfg restriction violations detected:\n NFFS_FLASH_AREA must not be null \n\nSetting history (newest -\n oldest):\n NFFS_FLASH_AREA: [fs/nffs:]\n\n\n\n\n\nThe above error occurs because the \nfs/nffs\n package defines the \nNFFS_FLASH_AREA\n \nsetting with a \n$notnull\n restriction and no packages override the setting. The \nfollowing is an excerpt of the definition in the \nsyscfg.yml\n file that causes the error:\n\n\n#Package: fs/nffs\nsyscfg.defs:\n NFFS_FLASH_AREA:\n description: \nThe flash area to use for the Newtron Flash File System\n\n type: flash_owner\n value:\n restrictions:\n - $notnull\n\n\n\n\n\nExample: Expression Restriction Violation Error Message\n\n\nThe following example shows the error message that newt outputs for \nan expression restriction violation:\n\n\n
Error: Syscfg restriction violations detected:\n CONFIG_FCB=1 requires CONFIG_FCB_FLASH_AREA be set, but CONFIG_FCB_FLASH_AREA=\n\nSetting history (newest -\n oldest):\n CONFIG_FCB: [targets/sim_slinky:1, sys/config:0]\n CONFIG_FCB_FLASH_AREA: [sys/config:]\n\n\n\n\n\nThe above error occurs because the \nsys/config\n package defines the \nCONFIG_FCB\n setting with \na restriction that when set, requires that the \nCONFIG_FCB_FLASH_AREA\n setting must \nalso be set. The following are excerpts of the definition and the override from the \nsyscfg.yml\n \nfiles that cause the error:\n\n\n# Package: sys/config\nsyscfg.defs:\n CONFIG_FCB:\n description: \nUses Config Flash Circular Buffer\n\n value: 0\n restrictions:\n - \n!CONFIG_NFFS\n\n - \nCONFIG_FCB_FLASH_AREA\n\n\n# Package: targets/sim_slinky\nsyscfg.vals:\n CONFIG_FCB: 1\n\n\n\n\n\n\n\nTask Priority Violations\n\n\nFor \ntask_priority\n type setting definitions, newt chec
ks for the following violations:\n\n\n\n\nA task priority number is assigned to multiple settings. \n\n\nThe task priority number is greater than 239.\n\n\n\n\nExample: Duplicate Task Priority Assignment Error Message\n\n\nThe following example shows the error message that newt outputs when\na task priority number is assigned to multiple settings.\n\n\nNote:\n The settings used in this example are not actual \napps/slinky\n and \nsys/shell\n settings.\nThese settings are created for this example because currently only one Mynewt package \ndefines a \ntask_priority\n type setting. \n\n\nError: duplicate priority value: setting1=SHELL_TASK_PRIORITY setting2=SLINKY_TASK_PRIORITY pkg1=apps/slinky pkg2=sys/shell value=1\n\n\n\n\n\nThe above error occurs because the \napps/slinky\n package defines a \nSLINKY_TASK_PRIORITY\n \nsetting with a default task priority of 1 and the \nsys/shell\n package also defines a \n\nSHELL_TASK_PRIORITY\n setting with a default task priority of 1.\n\n\nExa
mple: Invalid Task Priority Error Message\n\n\nThe following example shows the error message that newt outputs when\na setting is assigned an invalid task priority value:\n\n\nError: invalid priority value: value too great (\n 239); setting=SLINKY_TASK_PRIORITY value=240 pkg=apps/slinky\n\n\n\n\n\nThe above error occurs because the \napps/slinky\n package defines the \nSLINKY_TASK_PRIORITY\n setting \nwith 240 for the default task priority value. \n\n\nNote:\n Newt does not output the \nSetting history\n with task priority violation error messages. \n\n\n\n\nDuplicate System Configuration Setting Definition\n\n\nA setting definition must be unique. Newt checks that only one package in the \ntarget defines a setting. The following example shows the error message that newt \noutputs when multiple packages define the \nLOG_NEWTMGR\n setting:\n\n\nError: setting LOG_NEWTMGR redefined\n\n\n\n\n\nNote:\n Newt does not output the \nSetting history\n with duplicate setting error messages.
",
+ "text": "Validation and Error Messages\n\n\nWith multiple packages defining and overriding system configuration settings, it \nis easy to introduce conflicts and violations that are difficult to find. The \n\nnewt build \ntarget-name\n command validates the setting definitions and value \noverrides for all the packages in the target to ensure a valid and consistent build.\nIt aborts the build when it detects violations or ambiguities between packages.\n\nThe following sections describe the error conditions that newt detects and \nthe error messages that it outputs. For most errors, newt also outputs \nthe \nSetting history\n with the order of package overrides to help \nyou resolve the errors.\n\n\nNote:\n The \nnewt target config \ntarget-name\n command also detects \nerrors and outputs error messages at the top of the command output. \nThe command outputs the package setting definitions and values after it \noutputs the error messages. It is easy to miss the error mes
sages at the top. \n\n\nValue Override Violations\n\n\nThe newt tool uses package priorities to resolve override conflicts. It uses \nthe value override from the highest priority package when multiple \npackages override the same setting. Newt checks for the following \noverride violations:\n\n\n\n\nAmbiguity Violation - Two packages of the same priority override a setting with \ndifferent values. And no higher priority package overrides the setting.\n\n\nPriority Violation - A package overrides a setting defined by a package with higher or \nequal priority. \n\n\n\n\nExample: Ambiguity Violation Error Message\n\n\nThe following example shows the error message that newt outputs for an ambiguity violation:\n\n\nError: Syscfg ambiguities detected:\n Setting: LOG_NEWTMGR, Packages: [apps/slinky, apps/splitty]\nSetting history (newest -\n oldest):\n LOG_NEWTMGR: [apps/splitty:0, apps/slinky:1, sys/log/full:0]\n\n\n\n\n\nThe above error occurs because the \napps/slinky\n and \napps
/splitty\n packages \nin the split image target both override the same setting with different \nvalues. The \napps/slinky\n package sets the \nsys/log/full\n package \nLOG_NEWTMGR\n \nsetting to 1, and the \napps/splitty\n package sets the setting to 0. The \noverrides are ambiguous because both are \napp\n packages and \nhave the same priority. The following are excerpts of the defintion \nand the two overrides from the \nsyscfg.yml\n files that cause the error:\n\n\n#Package: sys/log/full\nsyscfg.defs:\n LOG_NEWTMGR:\n description: \nEnables or disables newtmgr command tool logging\n\n value: 0\n\n#Package: apps/slinky\nsyscfg.vals:\n LOG_NEWTMGR: 1\n\n#Package: apps/splitty\nsyscfg.vals:\n LOG_NEWTMGR: 0\n\n\n\n\n\nExample: Priority Violation Error Message\n\n\nThe following example shows the error message that newt outputs for a priority violation \nwhere a package tries to change the setting that was defined by another package at \nthe same priority lev
el:\n\n\nError: Priority violations detected (Packages can only override settings defined by packages of lower priority):\n Package: mgmt/newtmgr overriding setting: LOG_NEWTMGR defined by sys/log/full\n\nSetting history (newest -\n oldest):\n LOG_NEWTMGR: [sys/log/full:0]\n\n\n\n\n\nThe above error occurs because the \nmgmt/newtmgr\n lib package \noverrides the \nLOG_NEWTMGR\n setting that the \nsys/log/full\n lib package \ndefines. The following are excerpts of the definition and the override from the \n\nsyscfg.yml\n files that cause this error: \n\n\n#Package: sys/log/full\nsyscfg.defs:\n LOG_NEWTMGR:\n description: \nEnables or disables newtmgr command tool logging\n\n value: 0\n\n#Package: mgmt/newtmgr\nsyscfg.vals:\n LOG_NEWTMGR: 1\n\n\n\n\n\n\n\nFlash Area Violations\n\n\nFor \nflash_owner\n type setting definitions, newt checks \nfor the following violations:\n\n\n\n\nAn undefined flash area is assigned to a setting.\n\n\nA flash area is assigned
to multiple settings.\n\n\n\n\nExample: Undefined Flash Area Error Message\n\n\nThe following example shows the error message that newt outputs for an undefined flash area.\n\n\nBuilding target targets/sim_slinky\nError: Flash errors detected:\n Setting REBOOT_LOG_FLASH_AREA specifies unknown flash area: FLASH_AREA_NOEXIST\n\nSetting history (newest -\n oldest):\n REBOOT_LOG_FLASH_AREA: [hw/bsp/native:FLASH_AREA_NOEXIST, sys/reboot:]\n\n\n\n\n\nThe above error occurs because the \nhw/bsp/native\n package assigns the \nundefined \nFLASH_AREA_NOEXIST\n flash area to the \nsys/reboot\n package \n\nREBOOT_LOG_FLASH_AREA\n setting. The following are excerpts of the definition \nand the override from the \nsyscfg.yml\n files that cause the error:\n\n\n#Package: sys/reboot\nsyscfg.defs:\n REBOOT_LOG_FLASH_AREA:\n description: \nFlash Area to use for reboot log.\n\n type: flash_owner\n value:\n\n#Package: hw/bsp/native\nsyscfg.vals:\n REBOOT_LOG_FLASH_AREA:
FLASH_AREA_NOEXIST\n\n\n\n\n\nExample: Multiple Flash Area Assignment Error Message\n\n\nThe following example shows the error message that newt outputs when multiple \nsettings are assigned the same flash area:\n\n\nError: Flash errors detected:\n Multiple flash_owner settings specify the same flash area\n settings: REBOOT_LOG_FLASH_AREA, CONFIG_FCB_FLASH_AREA\n flash area: FLASH_AREA_NFFS\n\nSetting history (newest -\n oldest):\n CONFIG_FCB_FLASH_AREA: [hw/bsp/native:FLASH_AREA_NFFS, sys/config:]\n REBOOT_LOG_FLASH_AREA: [apps/slinky:FLASH_AREA_NFFS, sys/reboot:]\n\n\n\n\n\nThe above error occurs because the \nhw/bsp/native\n package assigns \nthe \nFLASH_AREA_NFFS\n flash area to the \nsys/config/\n package \n\nCONFIG_FCB_FLASH_AREA\n setting, and the \napps/slinky\n package \nalso assigns \nFLASH_AREA_NFFS\n to the \nsys/reboot\n package \n\nREBOOT_LOG_FLASH_AREA\n setting. The following are excerpts of the \ntwo definitions and the two overrides from
the \nsyscfg.yml\n files \nthat cause the error:\n\n\n# Package: sys/config\nsyscfg.defs.CONFIG_FCB:\n CONFIG_FCB_FLASH_AREA:\n description: \nThe flash area for the Config Flash Circular Buffer\n\n type: \nflash_owner\n\n value:\n\n# Package: sys/reboot\nsyscfg.defs:\n REBOOT_LOG_FLASH_AREA:\n description: \nThe flash area for the reboot log\n\n type: \nflash_owner\n \n value:\n\n#Package: hw/bsp/native\nsyscfg.vals:\n CONFIG_FCB_FLASH_AREA: FLASH_AREA_NFFS\n\n#Package: apps/slinky\nsyscfg.vals: \n REBOOT_LOG_FLASH_AREA: FLASH_AREA_NFFS\n\n\n\n\n\n\n\nRestriction Violations\n\n\nFor setting definitions with \nrestrictions\n specified, newt checks for \nthe following violations:\n\n\n\n\nA setting with a \n$notnull\n restriction does not have a value. \n\n\nFor a setting with expression restrictions, some required setting \nvalues in the expressions evaluate to false. \n\n\n\n\nExample: $notnull Restriction Violation Error Messa
ge\n\n\nThe following example shows the error message that newt outputs when\na setting with \n$notnull\n restriction does not have a value:\n\n\nError: Syscfg restriction violations detected:\n NFFS_FLASH_AREA must not be null \n\nSetting history (newest -\n oldest):\n NFFS_FLASH_AREA: [fs/nffs:]\n\n\n\n\n\nThe above error occurs because the \nfs/nffs\n package defines the \nNFFS_FLASH_AREA\n \nsetting with a \n$notnull\n restriction and no packages override the setting. The \nfollowing is an excerpt of the definition in the \nsyscfg.yml\n file that causes the error:\n\n\n#Package: fs/nffs\nsyscfg.defs:\n NFFS_FLASH_AREA:\n description: \nThe flash area to use for the Newtron Flash File System\n\n type: flash_owner\n value:\n restrictions:\n - $notnull\n\n\n\n\n\nExample: Expression Restriction Violation Error Message\n\n\nThe following example shows the error message that newt outputs for \nan expression restriction violation:\n\n\n
Error: Syscfg restriction violations detected:\n CONFIG_FCB=1 requires CONFIG_FCB_FLASH_AREA be set, but CONFIG_FCB_FLASH_AREA=\n\nSetting history (newest -\n oldest):\n CONFIG_FCB: [targets/sim_slinky:1, sys/config:0]\n CONFIG_FCB_FLASH_AREA: [sys/config:]\n\n\n\n\n\nThe above error occurs because the \nsys/config\n package defines the \nCONFIG_FCB\n setting with \na restriction that when set, requires that the \nCONFIG_FCB_FLASH_AREA\n setting must \nalso be set. The following are excerpts of the definition and the override from the \nsyscfg.yml\n \nfiles that cause the error:\n\n\n# Package: sys/config\nsyscfg.defs:\n CONFIG_FCB:\n description: \nUses Config Flash Circular Buffer\n\n value: 0\n restrictions:\n - \n!CONFIG_NFFS\n\n - \nCONFIG_FCB_FLASH_AREA\n\n\n# Package: targets/sim_slinky\nsyscfg.vals:\n CONFIG_FCB: 1\n\n\n\n\n\n\n\nTask Priority Violations\n\n\nFor \ntask_priority\n type setting definitions, newt chec
ks for the following violations:\n\n\n\n\nA task priority number is assigned to multiple settings. \n\n\nThe task priority number is greater than 239.\n\n\n\n\nExample: Duplicate Task Priority Assignment Error Message\n\n\nThe following example shows the error message that newt outputs when\na task priority number is assigned to multiple settings.\n\n\nNote:\n The settings used in this example are not actual \napps/slinky\n and \nsys/shell\n settings.\nThese settings are created for this example because currently only one Mynewt package \ndefines a \ntask_priority\n type setting. \n\n\nError: duplicate priority value: setting1=SHELL_TASK_PRIORITY setting2=SLINKY_TASK_PRIORITY pkg1=apps/slinky pkg2=sys/shell value=1\n\n\n\n\n\nThe above error occurs because the \napps/slinky\n package defines a \nSLINKY_TASK_PRIORITY\n \nsetting with a default task priority of 1 and the \nsys/shell\n package also defines a \n\nSHELL_TASK_PRIORITY\n setting with a default task priority of 1.\n\n\nExa
mple: Invalid Task Priority Error Message\n\n\nThe following example shows the error message that newt outputs when\na setting is assigned an invalid task priority value:\n\n\nError: invalid priority value: value too great (\n 239); setting=SLINKY_TASK_PRIORITY value=240 pkg=apps/slinky\n\n\n\n\n\nThe above error occurs because the \napps/slinky\n package defines the \nSLINKY_TASK_PRIORITY\n setting \nwith 240 for the default task priority value. \n\n\nNote:\n Newt does not output the \nSetting history\n with task priority violation error messages. \n\n\n\n\nDuplicate System Configuration Setting Definition\n\n\nA setting definition must be unique. Newt checks that only one package in the \ntarget defines a setting. The following example shows the error message that newt \noutputs when multiple packages define the \nLOG_NEWTMGR\n setting:\n\n\nError: setting LOG_NEWTMGR redefined\n\n\n\n\n\nNote:\n Newt does not output the \nSetting history\n with duplicate setting error messages.
\n\n\n\nOverride of Undefined System Configuration Setting\n\n\nThe \nnewt build\n command ignores overrides of undefined system configuration settings. The command does not print a warning when you run it with the default log level. If you override a setting and the value is not assigned to the setting, you may have misspelled the setting name or a package no longer defines the setting. You have two options to troubleshoot this problem:\n\n\n\n\nRun the \nnewt target config show\n command to see the configuration setting definitions and overrides.\n\n\nRun the \nnewt build -ldebug\n command to build your target with DEBUG log level. \n\n\n\n\nNote: The \nnewt build -ldebug\n command generates lots of output and we recommend that you use the \nnewt target config show\n command option.\n\n\n\nExample: Ignoring Override of Undefined Setting Message\n\n\nThe following example shows that the \napps/slinky\n application overrides the \nLOG_NEWTMGR\n setting but omits the \nT\n as an e
xample of an error and overrides the misspelled \nLOG_NEWMGR\n setting. Here is an excerpt from its \nsyscfg.yml\n file: \n\n\n#package: apps/slinky\nsyscfg.vals:\n # Enable the shell task.\n SHELL_TASK: 1\n ...\n\n # Enable newtmgr commands.\n STATS_NEWTMGR: 1\n LOG_NEWMGR: 1\n\n\n\n\n\n\nThe \nnewt target config show slinky_sim\n command outputs the following WARNING message:\n\n\n2017/02/18 17:19:12.119 [WARNING] Ignoring override of undefined settings:\n2017/02/18 17:19:12.119 [WARNING] LOG_NEWMGR\n2017/02/18 17:19:12.119 [WARNING] NFFS_FLASH_AREA\n2017/02/18 17:19:12.119 [WARNING] Setting history (newest -\n oldest):\n2017/02/18 17:19:12.119 [WARNING] LOG_NEWMGR: [apps/slinky:1]\n2017/02/18 17:19:12.119 [WARNING] NFFS_FLASH_AREA: [hw/bsp/native:FLASH_AREA_NFFS]\n\n\n\n\n\n\n\nThe \nnewt build -ldebug slinky_sim\n command outputs the following DEBUG message: \n\n\n2017/02/18 17:06:21.451 [DEBUG] Ignoring override of undefined settings:\n2
017/02/18 17:06:21.451 [DEBUG] LOG_NEWMGR\n2017/02/18 17:06:21.451 [DEBUG] NFFS_FLASH_AREA\n2017/02/18 17:06:21.451 [DEBUG] Setting history (newest -\n oldest):\n2017/02/18 17:06:21.451 [DEBUG] LOG_NEWMGR: [apps/slinky:1]\n2017/02/18 17:06:21.451 [DEBUG] NFFS_FLASH_AREA: [hw/bsp/native:FLASH_AREA_NFFS]\n\n\n\n\n\n\n\nBSP Package Overrides Undefined Configuration Settings\n\n\nYou might see a warning that indicates your application's BSP package is overriding some undefined settings. As you can see from the previous example, the WARNING message shows that the \nhw/bsp/native\n package is overriding the undefined \nNFFS_FLASH_AREA\n setting. This is not an error because of the way a BSP package defines and assigns its flash areas to packages that use flash memory.\n\n\nA BSP package defines, in its \nbsp.yml\n file, a flash area map of the flash areas on the board. A package that uses flash memory must define a flash area configuration setting name. The BSP package ove
rrides the package's flash area setting with one of the flash areas from its flash area map. A BSP package overrides the flash area settings for all packages that use flash memory because it does not know the packages that an application uses. When an application does not include one of these packages, the flash area setting for the package is undefined. You will see a message that indicates the BSP package overrides this undefined setting.\n\n\nHere are excerpts from the \nhw/bsp/native\n package's \nbsp.yml\n and \nsyscfg.yml\n files for the \nslinky_sim\n target. The BSP package defines the flash area map in its \nbsp.yml\n file and overrides the flash area settings for all packages in its \nsyscfg.yml\n file. The \nslinky_sim\n target does not use the \nfs/nffs\n package which defines the \nNFFS_FLASH_AREA\n setting. Newt warns that the \nhw/bsp/native\n packages overrides the undefined \nNFFS_FLASH_AREA\n setting.\n\n\n# hw/bsp/native bsp.yml\nbsp.flash_map:\n areas:\n
# System areas.\n FLASH_AREA_BOOTLOADER:\n device: 0\n offset: 0x00000000\n size: 16kB\n\n ...\n\n FLASH_AREA_IMAGE_SCRATCH:\n device: 0\n offset: 0x000e0000\n size: 128kB\n\n # User areas.\n FLASH_AREA_REBOOT_LOG:\n user_id: 0\n device: 0\n offset: 0x00004000\n size: 16kB\n FLASH_AREA_NFFS:\n user_id: 1\n device: 0\n offset: 0x00008000\n\n# hw/bsp/native syscfg.yml\nsyscfg.vals:\n NFFS_FLASH_AREA: FLASH_AREA_NFFS\n CONFIG_FCB_FLASH_AREA: FLASH_AREA_NFFS\n REBOOT_LOG_FLASH_AREA: FLASH_AREA_REBOOT_LOG",
"title": "Validation and Error Messages"
},
{
@@ -8011,6 +8011,21 @@
"title": "Duplicate System Configuration Setting Definition"
},
{
+ "location": "/os/modules/sysinitconfig/sysconfig_error/#override-of-undefined-system-configuration-setting",
+ "text": "The newt build command ignores overrides of undefined system configuration settings. The command does not print a warning when you run it with the default log level. If you override a setting and the value is not assigned to the setting, you may have misspelled the setting name or a package no longer defines the setting. You have two options to troubleshoot this problem: Run the newt target config show command to see the configuration setting definitions and overrides. Run the newt build -ldebug command to build your target with DEBUG log level. Note: The newt build -ldebug command generates lots of output and we recommend that you use the newt target config show command option.",
+ "title": "Override of Undefined System Configuration Setting"
+ },
+ {
+ "location": "/os/modules/sysinitconfig/sysconfig_error/#example-ignoring-override-of-undefined-setting-message",
+ "text": "The following example shows that the apps/slinky application overrides the LOG_NEWTMGR setting but omits the T as an example of an error and overrides the misspelled LOG_NEWMGR setting. Here is an excerpt from its syscfg.yml file: #package: apps/slinky\nsyscfg.vals:\n # Enable the shell task.\n SHELL_TASK: 1\n ...\n\n # Enable newtmgr commands.\n STATS_NEWTMGR: 1\n LOG_NEWMGR: 1 \nThe newt target config show slinky_sim command outputs the following WARNING message: 2017/02/18 17:19:12.119 [WARNING] Ignoring override of undefined settings:\n2017/02/18 17:19:12.119 [WARNING] LOG_NEWMGR\n2017/02/18 17:19:12.119 [WARNING] NFFS_FLASH_AREA\n2017/02/18 17:19:12.119 [WARNING] Setting history (newest - oldest):\n2017/02/18 17:19:12.119 [WARNING] LOG_NEWMGR: [apps/slinky:1]\n2017/02/18 17:19:12.119 [WARNING] NFFS_FLASH_AREA: [hw/bsp/native:FLASH_AREA_NFFS] The newt build -ldebug slinky_sim command outputs the fo
llowing DEBUG message: 2017/02/18 17:06:21.451 [DEBUG] Ignoring override of undefined settings:\n2017/02/18 17:06:21.451 [DEBUG] LOG_NEWMGR\n2017/02/18 17:06:21.451 [DEBUG] NFFS_FLASH_AREA\n2017/02/18 17:06:21.451 [DEBUG] Setting history (newest - oldest):\n2017/02/18 17:06:21.451 [DEBUG] LOG_NEWMGR: [apps/slinky:1]\n2017/02/18 17:06:21.451 [DEBUG] NFFS_FLASH_AREA: [hw/bsp/native:FLASH_AREA_NFFS]",
+ "title": "Example: Ignoring Override of Undefined Setting Message"
+ },
+ {
+ "location": "/os/modules/sysinitconfig/sysconfig_error/#bsp-package-overrides-undefined-configuration-settings",
+ "text": "You might see a warning that indicates your application's BSP package is overriding some undefined settings. As you can see from the previous example, the WARNING message shows that the hw/bsp/native package is overriding the undefined NFFS_FLASH_AREA setting. This is not an error because of the way a BSP package defines and assigns its flash areas to packages that use flash memory. A BSP package defines, in its bsp.yml file, a flash area map of the flash areas on the board. A package that uses flash memory must define a flash area configuration setting name. The BSP package overrides the package's flash area setting with one of the flash areas from its flash area map. A BSP package overrides the flash area settings for all packages that use flash memory because it does not know the packages that an application uses. When an application does not include one of these packages, the flash area setting for the package is undefined. You will see a message t
hat indicates the BSP package overrides this undefined setting. Here are excerpts from the hw/bsp/native package's bsp.yml and syscfg.yml files for the slinky_sim target. The BSP package defines the flash area map in its bsp.yml file and overrides the flash area settings for all packages in its syscfg.yml file. The slinky_sim target does not use the fs/nffs package which defines the NFFS_FLASH_AREA setting. Newt warns that the hw/bsp/native packages overrides the undefined NFFS_FLASH_AREA setting. # hw/bsp/native bsp.yml\nbsp.flash_map:\n areas:\n # System areas.\n FLASH_AREA_BOOTLOADER:\n device: 0\n offset: 0x00000000\n size: 16kB\n\n ...\n\n FLASH_AREA_IMAGE_SCRATCH:\n device: 0\n offset: 0x000e0000\n size: 128kB\n\n # User areas.\n FLASH_AREA_REBOOT_LOG:\n user_id: 0\n device: 0\n offset: 0x00004000\n
size: 16kB\n FLASH_AREA_NFFS:\n user_id: 1\n device: 0\n offset: 0x00008000\n\n# hw/bsp/native syscfg.yml\nsyscfg.vals:\n NFFS_FLASH_AREA: FLASH_AREA_NFFS\n CONFIG_FCB_FLASH_AREA: FLASH_AREA_NFFS\n REBOOT_LOG_FLASH_AREA: FLASH_AREA_REBOOT_LOG",
+ "title": "BSP Package Overrides Undefined Configuration Settings"
+ },
+ {
"location": "/network/ble/ble_intro/",
"text": "BLE Introduction\n\n\nApache Mynewt offers the world's first fully open-source Bluetooth Low Energy (BLE) or Bluetooth Smart stack fully compliant with BLE 4.2 specifications. It is called NimBLE. \n\n\nBLE technology operates in the unlicensed industrial, scientific and medical (ISM) band at 2.4 to 2.485 GHz which is available in most countries. It uses a spread spectrum, frequency hopping, full-duplex signal. BLE FHSS employs 40 2-MHz-wide channels to ensure greater reliability over longer distances. It also features 0-dBm (1 mW) power output and a typical maximum range of 50 meters. Note that BLE is not compatible with standard Bluetooth.\n\n\n\n\nFeature Support\n\n\nNimBLE complies with Bluetooth Core Specification 4.2 which introduces several new features that make it an ideal wireless technology for the Internet of Things (IoT).\n\n\n\n\nLE Privacy 1.2 for frequent changes to the device address to make it difficult to track for outsiders\n\n\nLE Secure Co
nnections featuring FIPS-compliant algorithms.\n\n\nLE Data Length Extension for higher throughput\n\n\nComing Soon\n: Assigning an Internet Protocol (IP) address (complaint with the IPv6 or 6LoWPAN standard) to a Bluetooth device through Internet Protocol Support Profile (IPSP)\n\n\n\n\nComponents\n\n\nA Bluetooth low energy stack (NimBLE included) consists of two components with several subcomponents:\n\n\n\n\n\n\nController\n\n\n\n\nPhysical Layer\n: adaptive frequency-hopping Gaussian Frequency Shift Keying (GFSK) radio using 40 RF channels (0-39), with 2 MHz spacing.\n\n\nLink Layer\n: with one of five states (Standby, Advertising, Scanning, Initiating, Connection states) active at any time\n\n\n\n\n\n\n\n\nHost\n\n\n\n\nLogical Link Control and Adaptation Protocol (L2CAP)\n: provides logical channels, named L2CAP channels, which are multiplexed over one or more logical links to provide packet segmentation and reassembly, flow control, error control, streaming, QoS etc. \n\n\nS
ecurity Manager (SM)\n: uses Security Manager Protocol (SMP) for pairing and transport specific key distribution for securing radio communication \n\n\nAttribute protocol (ATT)\n: allows a device (\nServer\n) to expose certain pieces of data, known as \nAttributes\n, to another device (\nClient\n)\n\n\nGeneric Attribute Profile (GATT)\n: a framework for using the ATT protocol to exchange attributes encapsulated as \nCharacteristics\n or \nServices\n \n\n\nGeneric Access Profile (GAP)\n: a base profile which all Bluetooth devices implement, which in the case of LE, defines the Physical Layer, Link Layer, L2CAP, Security Manager, Attribute Protocol and Generic Attribute Profile. \n\n\nHost Controller Interface (HCI)\n: the interface between the host and controller either through software API or by a hardware interface such as SPI, UART or USB.\n\n\n\n\n\n\n\n\nSubsequent chapters in this manual will go into the details of the implementation of each component, APIs available, and thing
s to consider while designing a NimBLE app.\n\n\n\n\nExample NimBLE projects\n\n\nMynewt comes with several built-in projects or applications using NimBLE. These allow users to try out NimBLE, understand how to use available services, and build their own applications using one or more of the examples as seed.\n\n\n\n\n\n\nbletiny\n : A simple shell application which provides a basic interface to the host-side of the BLE stack. Supported operations include GAP, GATT, and L2CAP.\n\n\n\n\n\n\nbleprph\n: A basic peripheral device with no user interface. It advertises automatically on startup, and resumes advertising whenever a connection is terminated. It supports a maximum of one connection.\n\n\n\n\n\n\nblecent\n: A basic central device with no user interface. This application scans for a peripheral that supports the alert notification service (ANS). Upon discovering such a peripheral, blecent connects and performs the following actions:\n\n\n\n\nReads the ANS Supported New Alert Ca
tegory characteristic.\n\n\nWrites the ANS Alert Notification Control Point characteristic.\n\n\nSubscribes to notifications for the ANS Unread Alert Status characteristic.\n\n\n\n\n\n\n\n\nblehci\n: Implements a BLE controller-only application. A separate host-only implementation, such as Linux's BlueZ, can interface with this application via HCI over UART.\n\n\n\n\n\n\nbleuart\n: Implements a simple BLE peripheral that supports the Nordic\n\nUART / Serial Port Emulation service",
"title": "NimBLE Introduction"
@@ -10182,7 +10197,7 @@
},
{
"location": "/newt/newt_intro/",
- "text": "Newt Tool\n\n\nIntroduction\n\n\nNewt is a smart build and package management system for embedded contexts. It is a single tool that accomplishes both the following goals:\n\n\n\n\nsource package management \n\n\nbuild, debug and install.\n\n\n\n\nRationale\n\n\nIn order for the Mynewt operating system to work well for constrained environments across the many different types of microcontroller applications (from doorbells to medical devices to power grids), a system is needed that lets you select which packages to install and which packages to build.\n\n\nThe build systems for embedded devices are often fairly complicated and not well served for this purpose. For example, autoconf is designed for detecting system compatibility issues but not well suited when it comes to tasks like:\n\n\n\n\nBuilding for multiple targets\n\n\nDeciding what to build in and what not to build in\n\n\nManaging dependencies between components\n\n\n\n\nFortunately, solutions addressi
ng these very issues can be found in source package management systems in higher level languages such as Javascript \n(Node), Go, PHP and Ruby. We decided to fuse their source management \nsystems with a make system built for embedded systems and create Newt.\n\n\nBuild System\n\n\nA good build system must allow the user to take a few common steps while developing embedded applications:\n\n\n\n\nGenerate full flash images\n\n\nDownload debug images to a target board using a debugger\n\n\nConditionally compile libraries \n code based upon build settings\n\n\n\n\nNewt can read a directory tree, build a dependency tree, and emit the right build artifacts. An example newt source tree is in incubator-mynewt-blinky/develop:\n\n\n$ tree -L 3 \n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\u2500\u2500 README.md\n\n\u251c\u2500\u2500 apps\n\n\u2502 \u2514\u2500\u2500 blinky\n\u2502 \u251c\u2500\u2500 pkg.yml\n\u2502 \u2514\u25
00\u2500 src\n\u251c\u2500\u2500 project.yml\n\n\u2514\u2500\u2500 targets\n\n \u251c\u2500\u2500 my_blinky_sim\n \u2502 \u251c\u2500\u2500 pkg.yml\n \u2502 \u2514\u2500\u2500 target.yml\n \u2514\u2500\u2500 unittest\n \u251c\u2500\u2500 pkg.yml\n \u2514\u2500\u2500 target.yml\n\n6 directories, 10 files\n\n\n\n\n\n\n\nWhen Newt sees a directory tree that contains a \"project.yml\" file, it is smart enough to recognize it as the base directory of a project, and \nautomatically builds a package tree. It also recognizes two important package directories in the package tree - \"apps\" and \"targets\". More on these directories in \nNewt Theory of Ops\n.\n\n\nWhen Newt is told to build a project, it recursively resolves all package dependencies and generates artifacts that are placed in the bin/ directory at the top-level of the project. The artifact directory is prefixed by the target name being built - \nmy_blinky_sim\n for example:\n\n\n$ tree bin\n
bin\n\u2514\u2500\u2500 my_blinky_sim\n \u251c\u2500\u2500 apps\n \u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.a\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.a.cmd\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf.cmd\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf.dSYM\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 Contents\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 Info.plist\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 Resources\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 DWARF\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky.elf\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf.lst\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 main.d\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 main.o\n \
u2502\u00a0\u00a0 \u2514\u2500\u2500 main.o.cmd\n \u251c\u2500\u2500 hw\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 bsp\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 native\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hal_bsp.d\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hal_bsp.o\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hal_bsp.o.cmd\n\nsnip\n\n\n\n\n\n\n\n\nMore operations using Newt\n\n\nOnce a target has been built, Newt allows additional operations on the target. \n\n\n\n\nload\n: Download built target to board\n\n\ndebug\n: Open debugger session to target\n\n\nsize\n: Get size of target components\n\n\ncreate-image\n: Add image header to the binary image\n\n\nrun\n: Build, create image, load, and finally open a debug session with the target\n\n\n\n\nFor more details on how Newt works, go to \nNewt - Theory of Operations\n.\n\n\n\n\nSource Management and Repositories\n\n\nThe other major
element of the Newt tool is the ability to create reusable source distributions from a collection of code. \nA project can be a reusable container of source code.\n In other words, projects can be versioned and redistributed, not packages. A project bundles together packages that are typically needed to work together in a product e.g. RTOS core, filesystem APIs, and networking stack.\n\n\nA project that has been made redistributable is known as a \nrepository\n. \nRepositories can be added to your local project by adding them into your project.yml file. Here is an example of the blinky project's yml file which relies on apache-mynewt-core:\n\n\n$ more project.yml\n\nsnip\n\nproject.repositories:\n - apache-mynewt-core\n\n# Use github\ns distribution mechanism for core ASF libraries.\n# This provides mirroring automatically for us.\n#\nrepository.apache-mynewt-core:\n type: github\n vers: 0-latest\n user: apache\n repo: incubator-mynewt-core\n\n\n\n\n\n\n\nWhen y
ou specify this repository in the blinky's project file, you can then use the Newt tool to install dependencies:\n\n\n$ newt install\nDownloading repository description for apache-mynewt-core... success!\nDownloading repository incubator-mynewt-core (branch: develop) at \nhttps://github.com/apache/incubator-mynewt-core.git\nCloning into \n\n/var/folders/7l/7b3w9m4n2mg3sqmgw2q1b9p80000gn/T/newt-repo814721459\n...\nremote: Counting objects: 17601, done.\nremote: Compressing objects: 100% (300/300), done.\nremote: Total 17601 (delta 142), reused 0 (delta 0), pack-reused 17284\nReceiving objects: 100% (17601/17601), 6.09 MiB | 3.17 MiB/s, done.\nResolving deltas: 100% (10347/10347), done.\nChecking connectivity... done.\nRepos successfully installed\n\n\n\n\n\n\n\nNewt will install this repository in the \n/repos directory. In the case of blinky, the directory structure ends up looking like:\n\n\n$ tree -L 2\n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2
500 NOTICE\n\u251c\u2500\u2500 README.md\n\u251c\u2500\u2500 apps\n\u2502 \u2514\u2500\u2500 blinky\n\u251c\u2500\u2500 project.state\n\u251c\u2500\u2500 project.yml\n\u251c\u2500\u2500 repos\n\u2502 \u2514\u2500\u2500 apache-mynewt-core\n\u2514\u2500\u2500 targets\n \u251c\u2500\u2500 my_blinky_sim\n \u2514\u2500\u2500 unittest\n\n\n\n\n\n\n\nIn order to reference the installed repositories in packages, the \"@\" notation should be specified in the repository specifier. As an example, the apps/blinky application has the following dependencies in its pkg.yml file. This tells the build system to look in the base directory of repos/apache-mynewt-core for the \nlibs/os\n, \nhw/hal\n, and \nlibs/console/full\n packages.\n\n\n$ more apps/blinky/pkg.yml\n\nsnip\n\npkg.deps:\n - \n@apache-mynewt-core/libs/os\n\n - \n@apache-mynewt-core/hw/hal\n\n - \n@apache-mynewt-core/libs/console/full\n\n\n\n\n\n\n\n\nAutocompletion in Bash\n\n\nNewt has the ability to autocompl
ete within \nbash\n. The following instructions allow MAC users to enable autocomplete within \nbash\n.\n\n\n\n\nInstall the autocomplete tools for bash via \nbrew install bash-completion\n\n\nTell your shell to use newt for autocompletion of newt via \ncomplete -C \"newt complete\" newt\n. You can add this to your .bashrc or other init file to have it automatically set for all bash shells.\n\n\n\n\nNotes:\n\n\n\n\nAutocomplete will give you flag hints, but only if you type a '-'. \n\n\nAutocomplete will not give you completion hints for the flag arguments (those optional things after the flag like \n-l DEBUG\n)\n\n\nAutocomplete uses newt to parse the project to find targets and libs.",
+ "text": "Newt Tool\n\n\nIntroduction\n\n\nNewt is a smart build and package management system for embedded contexts. It is a single tool that accomplishes both the following goals:\n\n\n\n\nsource package management \n\n\nbuild, debug and install.\n\n\n\n\nRationale\n\n\nIn order for the Mynewt operating system to work well for constrained environments across the many different types of microcontroller applications (from doorbells to medical devices to power grids), a system is needed that lets you select which packages to install and which packages to build.\n\n\nThe build systems for embedded devices are often fairly complicated and not well served for this purpose. For example, autoconf is designed for detecting system compatibility issues but not well suited when it comes to tasks like:\n\n\n\n\nBuilding for multiple targets\n\n\nDeciding what to build in and what not to build in\n\n\nManaging dependencies between components\n\n\n\n\nFortunately, solutions addressi
ng these very issues can be found in source package management systems in higher level languages such as Javascript \n(Node), Go, PHP and Ruby. We decided to fuse their source management \nsystems with a make system built for embedded systems and create Newt.\n\n\nBuild System\n\n\nA good build system must allow the user to take a few common steps while developing embedded applications:\n\n\n\n\nGenerate full flash images\n\n\nDownload debug images to a target board using a debugger\n\n\nConditionally compile libraries \n code based upon build settings\n\n\n\n\nNewt can read a directory tree, build a dependency tree, and emit the right build artifacts. An example newt source tree is in incubator-mynewt-blinky/develop:\n\n\n$ tree -L 3 \n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\u2500\u2500 README.md\n\n\u251c\u2500\u2500 apps\n\n\u2502 \u2514\u2500\u2500 blinky\n\u2502 \u251c\u2500\u2500 pkg.yml\n\u2502 \u2514\u25
00\u2500 src\n\u251c\u2500\u2500 project.yml\n\n\u2514\u2500\u2500 targets\n\n \u251c\u2500\u2500 my_blinky_sim\n \u2502 \u251c\u2500\u2500 pkg.yml\n \u2502 \u2514\u2500\u2500 target.yml\n \u2514\u2500\u2500 unittest\n \u251c\u2500\u2500 pkg.yml\n \u2514\u2500\u2500 target.yml\n\n6 directories, 10 files\n\n\n\n\n\n\n\nWhen Newt sees a directory tree that contains a \"project.yml\" file, it is smart enough to recognize it as the base directory of a project, and \nautomatically builds a package tree. It also recognizes two important package directories in the package tree - \"apps\" and \"targets\". More on these directories in \nNewt Theory of Ops\n.\n\n\nWhen Newt builds a target, it recursively resolves all package dependencies, and generates artifacts that are placed in the bin/targets/\ntarget-name\n/app/apps/\napp-name\n directory, where the bin directory is under the project base directory, \ntarget-name\n is the name of the target, and \napp
-name\n is the name of the application. For our example \nmy_blinky_sim\n is the name of the target and \nblinky\n is the name of the application. The \nblinky.elf\n executable is stored in the bin/targets/my_blinky_sim/app/apps/blinky directory as shown in the source tree:\n\n\ntree -L 6 bin/\nbin/\n\u2514\u2500\u2500 targets\n \u251c\u2500\u2500 my_blinky_sim\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 app\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 apps\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 apps\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 apps_blinky.a\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 apps_blinky.a.cmd\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf\n \u2502\u00a0\u00a0 \u2502\u00a0\u00
a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf.cmd\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf.dSYM\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf.lst\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 manifest.json\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hw\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 bsp\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 native\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 drivers\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 uart\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hal\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 h
w_hal.a\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hw_hal.a.cmd\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 repos\n\n\nsnip\n\n\n\n\n\n\n\n\nMore operations using Newt\n\n\nOnce a target has been built, Newt allows additional operations on the target. \n\n\n\n\nload\n: Download built target to board\n\n\ndebug\n: Open debugger session to target\n\n\nsize\n: Get size of target components\n\n\ncreate-image\n: Add image header to the binary image\n\n\nrun\n: Build, create image, load, and finally open a debug session with the target\n\n\ntarget\n: Create, delete, configure, and query a target\n\n\n\n\nFor more details on how Newt works, go to \nNewt - Theory of Operations\n.\n\n\n\n\nSource Management and Repositories\n\n\nThe other major element of the Newt tool is the ability to create reusable source distributions from a collection of code. \nA project can be a reusable
container of source code.\n In other words, projects can be versioned and redistributed, not packages. A project bundles together packages that are typically needed to work together in a product e.g. RTOS core, filesystem APIs, and networking stack.\n\n\nA project that has been made redistributable is known as a \nrepository\n. \nRepositories can be added to your local project by adding them into your project.yml file. Here is an example of the blinky project's yml file which relies on apache-mynewt-core:\n\n\n$ more project.yml\n\nsnip\n\nproject.repositories:\n - apache-mynewt-core\n\n# Use github\ns distribution mechanism for core ASF libraries.\n# This provides mirroring automatically for us.\n#\nrepository.apache-mynewt-core:\n type: github\n vers: 0-latest\n user: apache\n repo: incubator-mynewt-core\n\n\n\n\n\n\n\nWhen you specify this repository in the blinky's project file, you can then use the Newt tool to install dependencies:\n\n\n$ newt install\nDow
nloading repository description for apache-mynewt-core... success!\nDownloading repository incubator-mynewt-core (branch: develop) at \nhttps://github.com/apache/incubator-mynewt-core.git\nCloning into \n\n/var/folders/7l/7b3w9m4n2mg3sqmgw2q1b9p80000gn/T/newt-repo814721459\n...\nremote: Counting objects: 17601, done.\nremote: Compressing objects: 100% (300/300), done.\nremote: Total 17601 (delta 142), reused 0 (delta 0), pack-reused 17284\nReceiving objects: 100% (17601/17601), 6.09 MiB | 3.17 MiB/s, done.\nResolving deltas: 100% (10347/10347), done.\nChecking connectivity... done.\nRepos successfully installed\n\n\n\n\n\n\n\nNewt will install this repository in the \n/repos directory. In the case of blinky, the directory structure ends up looking like:\n\n\n$ tree -L 2\n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\u2500\u2500 README.md\n\u251c\u2500\u2500 apps\n\u2502 \u2514\u2500\u2500 blinky\n\u251c\u2500\u2500 project.state\n
\u251c\u2500\u2500 project.yml\n\u251c\u2500\u2500 repos\n\u2502 \u2514\u2500\u2500 apache-mynewt-core\n\u2514\u2500\u2500 targets\n \u251c\u2500\u2500 my_blinky_sim\n \u2514\u2500\u2500 unittest\n\n\n\n\n\n\n\nIn order to reference the installed repositories in packages, the \"@\" notation should be specified in the repository specifier. As an example, the apps/blinky application has the following dependencies in its pkg.yml file. This tells the build system to look in the base directory of repos/apache-mynewt-core for the \nkernel/os\n, \nhw/hal\n, and \nsys/console/full\n packages.\n\n\n$ more apps/blinky/pkg.yml\n\nsnip\n\npkg.deps:\n - \n@apache-mynewt-core/kernel/os\n\n - \n@apache-mynewt-core/hw/hal\n\n - \n@apache-mynewt-core/sys/console/full\n\n\n\n\n\n\n\n\nAutocompletion in Bash\n\n\nNewt has the ability to autocomplete within \nbash\n. The following instructions allow MAC users to enable autocomplete within \nbash\n.\n\n\n\n\nInstall the autocompl
ete tools for bash via \nbrew install bash-completion\n\n\nTell your shell to use newt for autocompletion of newt via \ncomplete -C \"newt complete\" newt\n. You can add this to your .bashrc or other init file to have it automatically set for all bash shells.\n\n\n\n\nNotes:\n\n\n\n\nAutocomplete will give you flag hints, but only if you type a '-'. \n\n\nAutocomplete will not give you completion hints for the flag arguments (those optional things after the flag like \n-l DEBUG\n)\n\n\nAutocomplete uses newt to parse the project to find targets and libs.",
"title": "toc"
},
{
@@ -10202,17 +10217,17 @@
},
{
"location": "/newt/newt_intro/#build-system",
- "text": "A good build system must allow the user to take a few common steps while developing embedded applications: Generate full flash images Download debug images to a target board using a debugger Conditionally compile libraries code based upon build settings Newt can read a directory tree, build a dependency tree, and emit the right build artifacts. An example newt source tree is in incubator-mynewt-blinky/develop: $ tree -L 3 \n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\u2500\u2500 README.md \u251c\u2500\u2500 apps \u2502 \u2514\u2500\u2500 blinky\n\u2502 \u251c\u2500\u2500 pkg.yml\n\u2502 \u2514\u2500\u2500 src\n\u251c\u2500\u2500 project.yml \u2514\u2500\u2500 targets \u251c\u2500\u2500 my_blinky_sim\n \u2502 \u251c\u2500\u2500 pkg.yml\n \u2502 \u2514\u2500\u2500 target.yml\n \u2514\u2500\u2500 unittest\n \u251c\u2500\u2500 pkg.yml\n \u2514\u2500\u2500
target.yml\n\n6 directories, 10 files When Newt sees a directory tree that contains a \"project.yml\" file, it is smart enough to recognize it as the base directory of a project, and \nautomatically builds a package tree. It also recognizes two important package directories in the package tree - \"apps\" and \"targets\". More on these directories in Newt Theory of Ops . When Newt is told to build a project, it recursively resolves all package dependencies and generates artifacts that are placed in the bin/ directory at the top-level of the project. The artifact directory is prefixed by the target name being built - my_blinky_sim for example: $ tree bin\nbin\n\u2514\u2500\u2500 my_blinky_sim\n \u251c\u2500\u2500 apps\n \u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.a\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.a.cmd\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf\n \u2502\u00a0\u00a0 \u251c\u
2500\u2500 blinky.elf.cmd\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf.dSYM\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 Contents\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 Info.plist\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 Resources\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 DWARF\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky.elf\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf.lst\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 main.d\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 main.o\n \u2502\u00a0\u00a0 \u2514\u2500\u2500 main.o.cmd\n \u251c\u2500\u2500 hw\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 bsp\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 native\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hal_bsp.d\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2
500\u2500 hal_bsp.o\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hal_bsp.o.cmd snip",
+ "text": "A good build system must allow the user to take a few common steps while developing embedded applications: Generate full flash images Download debug images to a target board using a debugger Conditionally compile libraries code based upon build settings Newt can read a directory tree, build a dependency tree, and emit the right build artifacts. An example newt source tree is in incubator-mynewt-blinky/develop: $ tree -L 3 \n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\u2500\u2500 README.md \u251c\u2500\u2500 apps \u2502 \u2514\u2500\u2500 blinky\n\u2502 \u251c\u2500\u2500 pkg.yml\n\u2502 \u2514\u2500\u2500 src\n\u251c\u2500\u2500 project.yml \u2514\u2500\u2500 targets \u251c\u2500\u2500 my_blinky_sim\n \u2502 \u251c\u2500\u2500 pkg.yml\n \u2502 \u2514\u2500\u2500 target.yml\n \u2514\u2500\u2500 unittest\n \u251c\u2500\u2500 pkg.yml\n \u2514\u2500\u2500
target.yml\n\n6 directories, 10 files When Newt sees a directory tree that contains a \"project.yml\" file, it is smart enough to recognize it as the base directory of a project, and \nautomatically builds a package tree. It also recognizes two important package directories in the package tree - \"apps\" and \"targets\". More on these directories in Newt Theory of Ops . When Newt builds a target, it recursively resolves all package dependencies, and generates artifacts that are placed in the bin/targets/ target-name /app/apps/ app-name directory, where the bin directory is under the project base directory, target-name is the name of the target, and app-name is the name of the application. For our example my_blinky_sim is the name of the target and blinky is the name of the application. The blinky.elf executable is stored in the bin/targets/my_blinky_sim/app/apps/blinky directory as shown in the source tree: tree -L 6 bin/\nbin/\n\u2514\u2500\u2500 targets\n \u251
c\u2500\u2500 my_blinky_sim\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 app\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 apps\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 apps\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 apps_blinky.a\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 apps_blinky.a.cmd\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf.cmd\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf.dSYM\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 blinky.elf.lst\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500
\u2500 manifest.json\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hw\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 bsp\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 native\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 drivers\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 uart\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hal\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hw_hal.a\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 hw_hal.a.cmd\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 repos snip",
"title": "Build System"
},
{
"location": "/newt/newt_intro/#more-operations-using-newt",
- "text": "Once a target has been built, Newt allows additional operations on the target. load : Download built target to board debug : Open debugger session to target size : Get size of target components create-image : Add image header to the binary image run : Build, create image, load, and finally open a debug session with the target For more details on how Newt works, go to Newt - Theory of Operations .",
+ "text": "Once a target has been built, Newt allows additional operations on the target. load : Download built target to board debug : Open debugger session to target size : Get size of target components create-image : Add image header to the binary image run : Build, create image, load, and finally open a debug session with the target target : Create, delete, configure, and query a target For more details on how Newt works, go to Newt - Theory of Operations .",
"title": "More operations using Newt"
},
{
"location": "/newt/newt_intro/#source-management-and-repositories",
- "text": "The other major element of the Newt tool is the ability to create reusable source distributions from a collection of code. A project can be a reusable container of source code. In other words, projects can be versioned and redistributed, not packages. A project bundles together packages that are typically needed to work together in a product e.g. RTOS core, filesystem APIs, and networking stack. A project that has been made redistributable is known as a repository . \nRepositories can be added to your local project by adding them into your project.yml file. Here is an example of the blinky project's yml file which relies on apache-mynewt-core: $ more project.yml snip \nproject.repositories:\n - apache-mynewt-core\n\n# Use github s distribution mechanism for core ASF libraries.\n# This provides mirroring automatically for us.\n#\nrepository.apache-mynewt-core:\n type: github\n vers: 0-latest\n user: apache\n repo: incubator-mynewt-core
When you specify this repository in the blinky's project file, you can then use the Newt tool to install dependencies: $ newt install\nDownloading repository description for apache-mynewt-core... success!\nDownloading repository incubator-mynewt-core (branch: develop) at \nhttps://github.com/apache/incubator-mynewt-core.git\nCloning into /var/folders/7l/7b3w9m4n2mg3sqmgw2q1b9p80000gn/T/newt-repo814721459 ...\nremote: Counting objects: 17601, done.\nremote: Compressing objects: 100% (300/300), done.\nremote: Total 17601 (delta 142), reused 0 (delta 0), pack-reused 17284\nReceiving objects: 100% (17601/17601), 6.09 MiB | 3.17 MiB/s, done.\nResolving deltas: 100% (10347/10347), done.\nChecking connectivity... done.\nRepos successfully installed Newt will install this repository in the /repos directory. In the case of blinky, the directory structure ends up looking like: $ tree -L 2\n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\
u2500\u2500 README.md\n\u251c\u2500\u2500 apps\n\u2502 \u2514\u2500\u2500 blinky\n\u251c\u2500\u2500 project.state\n\u251c\u2500\u2500 project.yml\n\u251c\u2500\u2500 repos\n\u2502 \u2514\u2500\u2500 apache-mynewt-core\n\u2514\u2500\u2500 targets\n \u251c\u2500\u2500 my_blinky_sim\n \u2514\u2500\u2500 unittest In order to reference the installed repositories in packages, the \"@\" notation should be specified in the repository specifier. As an example, the apps/blinky application has the following dependencies in its pkg.yml file. This tells the build system to look in the base directory of repos/apache-mynewt-core for the libs/os , hw/hal , and libs/console/full packages. $ more apps/blinky/pkg.yml snip \npkg.deps:\n - @apache-mynewt-core/libs/os \n - @apache-mynewt-core/hw/hal \n - @apache-mynewt-core/libs/console/full",
+ "text": "The other major element of the Newt tool is the ability to create reusable source distributions from a collection of code. A project can be a reusable container of source code. In other words, projects can be versioned and redistributed, not packages. A project bundles together packages that are typically needed to work together in a product e.g. RTOS core, filesystem APIs, and networking stack. A project that has been made redistributable is known as a repository . \nRepositories can be added to your local project by adding them into your project.yml file. Here is an example of the blinky project's yml file which relies on apache-mynewt-core: $ more project.yml snip \nproject.repositories:\n - apache-mynewt-core\n\n# Use github s distribution mechanism for core ASF libraries.\n# This provides mirroring automatically for us.\n#\nrepository.apache-mynewt-core:\n type: github\n vers: 0-latest\n user: apache\n repo: incubator-mynewt-core
When you specify this repository in the blinky's project file, you can then use the Newt tool to install dependencies: $ newt install\nDownloading repository description for apache-mynewt-core... success!\nDownloading repository incubator-mynewt-core (branch: develop) at \nhttps://github.com/apache/incubator-mynewt-core.git\nCloning into /var/folders/7l/7b3w9m4n2mg3sqmgw2q1b9p80000gn/T/newt-repo814721459 ...\nremote: Counting objects: 17601, done.\nremote: Compressing objects: 100% (300/300), done.\nremote: Total 17601 (delta 142), reused 0 (delta 0), pack-reused 17284\nReceiving objects: 100% (17601/17601), 6.09 MiB | 3.17 MiB/s, done.\nResolving deltas: 100% (10347/10347), done.\nChecking connectivity... done.\nRepos successfully installed Newt will install this repository in the /repos directory. In the case of blinky, the directory structure ends up looking like: $ tree -L 2\n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\
u2500\u2500 README.md\n\u251c\u2500\u2500 apps\n\u2502 \u2514\u2500\u2500 blinky\n\u251c\u2500\u2500 project.state\n\u251c\u2500\u2500 project.yml\n\u251c\u2500\u2500 repos\n\u2502 \u2514\u2500\u2500 apache-mynewt-core\n\u2514\u2500\u2500 targets\n \u251c\u2500\u2500 my_blinky_sim\n \u2514\u2500\u2500 unittest In order to reference the installed repositories in packages, the \"@\" notation should be specified in the repository specifier. As an example, the apps/blinky application has the following dependencies in its pkg.yml file. This tells the build system to look in the base directory of repos/apache-mynewt-core for the kernel/os , hw/hal , and sys/console/full packages. $ more apps/blinky/pkg.yml snip \npkg.deps:\n - @apache-mynewt-core/kernel/os \n - @apache-mynewt-core/hw/hal \n - @apache-mynewt-core/sys/console/full",
"title": "Source Management and Repositories"
},
{
@@ -10222,7 +10237,7 @@
},
{
"location": "/newt/newt_operation/",
- "text": "Newt Tool - Theory of Operations\n\n\nNewt has a fairly smart package manager that can read a directory tree, build a dependency tree, and emit the right build artifacts.\n\n\nBuilding dependencies\n\n\nNewt can read a directory tree, build a dependency tree, and emit the right build artifacts. An example newt source tree is in incubator-mynewt-blinky/develop:\n\n\n$ tree -L 3 \n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\u2500\u2500 README.md\n\n\u251c\u2500\u2500 apps\n\n\u2502 \u2514\u2500\u2500 blinky\n\u2502 \u251c\u2500\u2500 pkg.yml\n\u2502 \u2514\u2500\u2500 src\n\u251c\u2500\u2500 project.yml\n\n\u2514\u2500\u2500 targets\n\n \u251c\u2500\u2500 my_blinky_sim\n \u2502 \u251c\u2500\u2500 pkg.yml\n \u2502 \u2514\u2500\u2500 target.yml\n \u2514\u2500\u2500 unittest\n \u251c\u2500\u2500 pkg.yml\n \u2514\u2500\u2500 target.yml\n\n6 directories, 10 files\n\n\
n\n\n\n\n\nWhen newt sees a directory tree that contains a \"project.yml\" file it knows that it is in the base directory of a project, and automatically builds a package tree. You can see that there are two essential package directories, \"apps\" and \"targets.\" \n\n\n\n\n\"apps\" Package Directory\n\n\napps\n is where applications are stored, and applications are where the main() function is contained. The base project directory comes with one simple app called \nblinky\n in the \napps\n directory. The core repository \n@apache-mynewt-core\n comes with many additional sample apps in its \napps\n directory. At the time of this writing, there are several example BLE apps, the boot app, slinky app for using newt manager protocol, and more in that directory.\n\n\n@~/dev/myproj$ ls repos/apache-mynewt-core/apps/\nblecent bleprph_oic bleuart ffs2native slinky_oic test\nblehci bletest boot ocf_sample spitest timtest\nbleprph bletiny fat2native sl
inky splitty\n\n\n\n\n\nAlong with the \ntargets\n directory, \napps\n represents the top-level of the build tree for the particular project, and define the dependencies and features for the rest of the system. Mynewt users and developers can add their own apps to the project's \napps\n directory. \n\n\nThe app definition is contained in a \npkg.yml\n file. For example, blinky's \npkg.yml\n file is:\n\n\n$ more apps/blinky/pkg.yml\n\nsnip\n\npkg.name: apps/blinky\npkg.type: app\npkg.description: Basic example application which blinks an LED.\npkg.author: \nApache Mynewt \ndev@mynewt.incubator.apache.org\n\npkg.homepage: \nhttp://mynewt.apache.org/\n\npkg.keywords:\n\npkg.deps:\n - \n@apache-mynewt-core/kernel/os\n\n - \n@apache-mynewt-core/hw/hal\n\n - \n@apache-mynewt-core/sys/console/full\n\n\n\n\n\n\n\n\nThis file says that the name of the package is apps/blinky, and it \ndepends on kernel/os, hw/hal and sys/console/full packages.\n\n\nNOTE:\n @apache-mynewt-core
is a repository descriptor, and this will be \ncovered in the \"repository\" section. \n\n\n\n\n\"targets\" Package Directory\n\n\ntargets\n is where targets are stored, and each target is a collection of parameters that must be passed to newt in order to generate a reproducible build. Along with the \napps\n directory, \ntargets\n represents the top of the build tree. Any packages or parameters specified at the target level cascades down to all dependencies.\n\n\nMost targets consist of:\n\n\n\n\napp: The application to build\n\n\nbsp: The board support package to combine with that application\n\n\nbuild_profile: Either debug or optimized.\n\n\n\n\nThe \nmy_blinky_sim\n target that is included by default has the following settings:\n\n\n$ newt target show\ntargets/my_blinky_sim\n app=apps/blinky\n bsp=@apache-mynewt-core/hw/bsp/native\n build_profile=debug\n$ ls targets/my_blinky_sim/\npkg.yml target.yml\n\n\n\n\n\nThere are helper functions to aid the developer specif
y parameters for a target. \n\n\n\n\nvals\n: Displays all valid values for the specified parameter type (e.g. bsp for a target)\n\n\ntarget show\n: Displays the build artifacts for specified or all targets\n\n\n\n\nIn general, the three basic parameters of a target (\napp\n, \nbsp\n, and \nbuild_profile\n) are stored in the \ntarget.yml\n file in that target's build directory under \ntargets\n. You will also see a \npkg.yml\n file in the same directory. Since targets are packages, a \npkg.yml\n is expected. It contains typical package descriptors, dependencies, and additional parameters such as the following:\n\n\n\n\nCflags: Any additional compiler flags you might want to specify to the build\n\n\nAflags: Any additional assembler flags you might want to specify to the build\n\n\nLflags: Any additional linker flags you might want to specify to the build\n\n\n\n\n\n\nResolving dependencies\n\n\nWhen newt is told to build a project, it will:\n\n\n\n\nfind the top-level project.yml fil
e\n\n\nrecurse the packages in the package tree, and build a list of all \nsource packages\n\n\n\n\nNewt then looks at the target that the user set, for example, blinky_sim:\n\n\n$ more targets/my_blinky_sim/\npkg.yml target.yml\n$ more targets/my_blinky_sim/target.yml\n### Target: targets/my_blinky_sim\ntarget.app: \napps/blinky\n\ntarget.bsp: \n@apache-mynewt-core/hw/bsp/native\n\ntarget.build_profile: \ndebug\n\n\n\n\n\n\n\n\nThe target specifies two major things:\n\n\n\n\nApplication (target.app): The application to build\n\n\nBoard Support Package (target.bsp): The board support package to build \nalong with that application.\n\n\n\n\nNewt builds the dependency tree specified by all the packages. While building this tree, it does a few other things:\n\n\n\n\nSets up the include paths for each package. Any package that depends on another package, automatically gets the include directories from the package it includes. Include directories in the\nnewt structure must always b
e prefixed by the package name. For example, libs/os has the following include tree and its include directory files contains the package name \"os\" before any header files. This is so in order to avoid any header file conflicts.\n\n\n\n\n$ tree\n.\n\u251c\u2500\u2500 README.md\n\u251c\u2500\u2500 include\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 os\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 arch\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 cortex_m0\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 os\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 os_arch.h\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u251c\u2500\u2500 cortex_m4\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 os\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 os_arch.h\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 sim\n\u2502\u00a0\u00a0 \u2502\
u00a0\u00a0 \u2514\u2500\u2500 os\n\u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 os_arch.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 endian.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_callout.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_cfg.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_eventq.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_heap.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_malloc.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_mbuf.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_mempool.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_mutex.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_sanity.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_sched.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_sem.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_task.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_test.h\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 os_time.h\n\u2502\u00a0\u00a0 \
u2514\u2500\u2500 queue.h\n\u251c\u2500\u2500 pkg.yml\n\u2514\u2500\u2500 src\n \u251c\u2500\u2500 arch\n\nsnip\n\n\n\n\n\n\n\n\n\n\n\n\nValidates API requirements. Packages can export APIs they \nimplement, (i.e. pkg.api: hw-hal-impl), and other packages can require \nthose APIs (i.e. pkg.req_api: hw-hal-impl).\n\n\n\n\n\n\nReads and validates the configuration setting definitions and values from the package \nsyscfg.yml\n files.\nIt generates a \nsyscfg.h\n header file that packages include in the source files inorder to access the settings.\n\nIt also generates a system initialization function to initialize the packages.\nSee \nSystem Configuration And Initialization\n for more information.\n\n\n\n\n\n\nIn order to properly resolve all dependencies in the build system, newt recursively processes the package dependencies until there are no new dependencies or features (because features can add dependencies.) And it builds a big list of all the packages that need to be build.\
n\n\nNewt then goes through this package list, and builds every package into \nan archive file.\n\n\nNOTE:\n The newt tool generates compiler dependencies for all of these packages, and only rebuilds the packages whose dependencies have changed. Changes in package \n project dependencies are also taken into account. It is smart, after all!\n\n\nProducing artifacts\n\n\nOnce newt has built all the archive files, it then links the archive files together. The linkerscript to use is specified by the board support package (BSP.)\n\n\nNOTE: One common use of the \"features\" option above is to overwrite \nwhich linkerscript is used, based upon whether or not the BSP is being \nbuild for a raw image, bootable image or bootloader itself.\n\n\nThe newt tool places all of it's artifacts into the bin/ directory at \nthe top-level of the project, prefixed by the target name being built, \nfor example:\n\n\n$ tree -L 4 bin/\nbin/\n\u2514\u2500\u2500 my_blinky_sim\n \u251c\u2500\u2500 apps\n
\u2502 \u2514\u2500\u2500 blinky\n \u2502 \u251c\u2500\u2500 blinky.a\n \u2502 \u251c\u2500\u2500 blinky.a.cmd\n \u2502 \u251c\u2500\u2500 blinky.elf\n \u2502 \u251c\u2500\u2500 blinky.elf.cmd\n \u2502 \u251c\u2500\u2500 blinky.elf.dSYM\n \u2502 \u251c\u2500\u2500 blinky.elf.lst\n \u2502 \u251c\u2500\u2500 main.d\n \u2502 \u251c\u2500\u2500 main.o\n \u2502 \u2514\u2500\u2500 main.o.cmd\n \u251c\u2500\u2500 hw\n \u2502 \u251c\u2500\u2500 bsp\n \u2502 \u2502 \u2514\u2500\u2500 native\n \u2502 \u251c\u2500\u2500 hal\n \u2502 \u2502 \u251c\u2500\u2500 flash_map.d\n \u2502 \u2502 \u251c\u2500\u2500 flash_map.o\n\nsnip\n\n\n\n\n\n\n\n\nAs you can see, a number of files are generated:\n\n\n\n\nArchive File\n\n\n*.cmd: The command use to generate the object or archive file\n\n\n*.lst: The list file where symbols are located\n\n\n*.o The object files that g
et put into the archive file\n\n\n\n\nDownload/Debug Support\n\n\nOnce a target has been build, there are a number of helper functions \nthat work on the target. These are:\n\n\n\n\nload\n Download built target to board\n\n\ndebug\n Open debugger session to target\n\n\nsize\n Size of target components\n\n\ncreate-image\n Add image header to target binary\n\n\nrun\n The equivalent of build, create-image, load, and debug on specified target\n\n\n\n\nload\n and \ndebug\n handles driving GDB and the system debugger. These \ncommands call out to scripts that are defined by the BSP.\n\n\n$ more repos/apache-mynewt-core/hw/bsp/nrf52dk/nrf52dk_debug.sh\n\nsnip\n\n. $CORE_PATH/hw/scripts/jlink.sh\n\nFILE_NAME=$BIN_BASENAME.elf\n\nif [ $# -gt 2 ]; then\n SPLIT_ELF_NAME=$3.elf\n # TODO -- this magic number 0x42000 is the location of the second image\n # slot. we should either get this from a flash map file or somehow learn\n # this from the image itself\n
EXTRA_GDB_CMDS=\nadd-symbol-file $SPLIT_ELF_NAME 0x8000 -readnow\n\nfi\n\nJLINK_DEV=\nnRF52\n\n\njlink_debug\n\n\n\n\n\nThe idea is that every BSP will add support for the debugger environment \nfor that board. That way common tools can be used across various development boards and kits.",
+ "text": "Newt Tool - Theory of Operations\n\n\nNewt has a fairly smart package manager that can read a directory tree, build a dependency tree, and emit the right build artifacts.\n\n\nBuilding dependencies\n\n\nNewt can read a directory tree, build a dependency tree, and emit the right build artifacts. An example newt source tree is in incubator-mynewt-blinky/develop:\n\n\n$ tree -L 3 \n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\u2500\u2500 README.md\n\n\u251c\u2500\u2500 apps\n\n\u2502 \u2514\u2500\u2500 blinky\n\u2502 \u251c\u2500\u2500 pkg.yml\n\u2502 \u2514\u2500\u2500 src\n\u251c\u2500\u2500 project.yml\n\n\u2514\u2500\u2500 targets\n\n \u251c\u2500\u2500 my_blinky_sim\n \u2502 \u251c\u2500\u2500 pkg.yml\n \u2502 \u2514\u2500\u2500 target.yml\n \u2514\u2500\u2500 unittest\n \u251c\u2500\u2500 pkg.yml\n \u2514\u2500\u2500 target.yml\n\n6 directories, 10 files\n\n\
n\n\n\n\n\nWhen newt sees a directory tree that contains a \"project.yml\" file it knows that it is in the base directory of a project, and automatically builds a package tree. You can see that there are two essential package directories, \"apps\" and \"targets.\" \n\n\n\n\n\"apps\" Package Directory\n\n\napps\n is where applications are stored, and applications are where the main() function is contained. The base project directory comes with one simple app called \nblinky\n in the \napps\n directory. The core repository \n@apache-mynewt-core\n comes with many additional sample apps in its \napps\n directory. At the time of this writing, there are several example BLE apps, the boot app, slinky app for using newt manager protocol, and more in that directory.\n\n\n@~/dev/myproj$ ls repos/apache-mynewt-core/apps/\nblecent blesplit boot sensors_test splitty\nblehci bletest fat2native slinky test\nbleprph bletiny ffs2native slinky_oic testbench\
nbleprph_oic bleuart ocf_sample spitest timtest\n\n\n\n\n\nAlong with the \ntargets\n directory, \napps\n represents the top-level of the build tree for the particular project, and define the dependencies for the rest of the system. Mynewt users and developers can add their own apps to the project's \napps\n directory. \n\n\nThe app definition is contained in a \npkg.yml\n file. For example, blinky's \npkg.yml\n file is:\n\n\n$ more apps/blinky/pkg.yml\n\nsnip\n\npkg.name: apps/blinky\npkg.type: app\npkg.description: Basic example application which blinks an LED.\npkg.author: \nApache Mynewt \ndev@mynewt.incubator.apache.org\n\npkg.homepage: \nhttp://mynewt.apache.org/\n\npkg.keywords:\n\npkg.deps:\n - \n@apache-mynewt-core/kernel/os\n\n - \n@apache-mynewt-core/hw/hal\n\n - \n@apache-mynewt-core/sys/console/full\n\n\n\n\n\n\n\n\nThis file says that the name of the package is apps/blinky, and it depends on the \nkernel/os,\nhw/hal\nand\nsys/console/full` packages.
\n\n\nNOTE:\n @apache-mynewt-core is a repository descriptor, and this will be \ncovered in the \"repository\" section. \n\n\n\n\n\"targets\" Package Directory\n\n\ntargets\n is where targets are stored, and each target is a collection of parameters that must be passed to newt in order to generate a reproducible build. Along with the \napps\n directory, \ntargets\n represents the top of the build tree. Any packages or parameters specified at the target level cascades down to all dependencies.\n\n\nMost targets consist of:\n\n\n\n\napp: The application to build\n\n\nbsp: The board support package to combine with that application\n\n\nbuild_profile: Either debug or optimized.\n\n\n\n\nThe \nmy_blinky_sim\n target that is included by default has the following settings:\n\n\n$ newt target show\ntargets/my_blinky_sim\n app=apps/blinky\n bsp=@apache-mynewt-core/hw/bsp/native\n build_profile=debug\n$ ls targets/my_blinky_sim/\npkg.yml target.yml\n\n\n\n\n\nThere are helper fun
ctions to aid the developer specify parameters for a target. \n\n\n\n\nvals\n: Displays all valid values for the specified parameter type (e.g. bsp for a target)\n\n\ntarget show\n: Displays the variable values for either a specific target or all targets defined for the project\n\n\ntarget set\n: Sets values for target variables\n\n\n\n\nIn general, the three basic parameters of a target (\napp\n, \nbsp\n, and \nbuild_profile\n) are stored in the target's \ntarget.yml\n file in the targets/\ntarget-name\n directory, where \ntarget-name\n is the name of the target. You will also see a \npkg.yml\n file in the same directory. Since targets are packages, a \npkg.yml\n is expected. It contains typical package descriptors, dependencies, and additional parameters such as the following:\n\n\n\n\nCflags: Any additional compiler flags you might want to specify to the build\n\n\nAflags: Any additional assembler flags you might want to specify to the build\n\n\nLflags: Any additional linker fla
gs you might want to specify to the build\n\n\n\n\nYou can also override the values of the system configuration settings that are defined by the packages that your target includes. You override the values in your target's \nsyscfg.yml\n file (stored in the targets/\ntarget-name\n directory). You can use the \nnewt target config show\n command to see the configuration settings and values for your target, and use the \nnewt target set\n command to set the \nsyscfg\n variable and override the configuration setting values. You can also use an editor to create your target's \nsyscfg.yml\n file and add the setting values to the file. See \nSystem Configuration And Initialization\n for more information on system configuration settings.\n\n\n\n\nResolving dependencies\n\n\nWhen newt builds a project, it will:\n\n\n\n\nfind the top-level project.yml file\n\n\nrecurse the packages in the package tree, and build a list of all \nsource packages\n\n\n\n\nNewt then looks at the target that the
user set, for example, blinky_sim:\n\n\n$ more targets/my_blinky_sim/\npkg.yml target.yml\n$ more targets/my_blinky_sim/target.yml\n### Target: targets/my_blinky_sim\ntarget.app: \napps/blinky\n\ntarget.bsp: \n@apache-mynewt-core/hw/bsp/native\n\ntarget.build_profile: \ndebug\n\n\n\n\n\n\n\n\nThe target specifies two major things:\n\n\n\n\nApplication (target.app): The application to build\n\n\nBoard Support Package (target.bsp): The board support package to build \nalong with that application.\n\n\n\n\nNewt builds the dependency tree specified by all the packages. While building this tree, it does a few other things:\n\n\n\n\nSets up the include paths for each package. Any package that depends on another package, automatically gets the include directories from the package it includes. Include directories in the\nnewt structure must always be prefixed by the package name. For example, kernel/os has the following include tree and its include directory files contains the package
name \"os\" before any header files. This is so in order to avoid any header file conflicts.\n\n\n\n\n$tree kernel/os/include\nkernel/os/include\n\u2514\u2500\u2500 os\n \u251c\u2500\u2500 arch\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 cortex_m0\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 os\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 os_arch.h\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 cortex_m4\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 os\n \u2502\u00a0\u00a0 \u2502\u00a0\u00a0 \u2514\u2500\u2500 os_arch.h\n \u2502\u00a0\u00a0 \u251c\u2500\
<TRUNCATED>
[5/7] incubator-mynewt-site git commit: Update newt command
documentation, sysconfig overwrites, events, bsp list
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/command_list/newt_build/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/command_list/newt_build/index.html b/develop/newt/command_list/newt_build/index.html
index f658a93..148b740 100644
--- a/develop/newt/command_list/newt_build/index.html
+++ b/develop/newt/command_list/newt_build/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,27 +504,26 @@
</div>
<h2 id="newt-build"><font color="#F2853F" style="font-size:24pt">newt build </font></h2>
-<p>Compiles, links, and builds one or more apps. </p>
+<p>Build one or more targets. </p>
<h4 id="usage">Usage:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt build [flags] input1
-</pre></div>
-
-
-<p>where <code>input1</code> is the name of the target to build.</p>
-<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for target
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt build <target-name> [target_name ...] [flags]
</pre></div>
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -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.
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
</pre></div>
+<h4 id="description">Description</h4>
+<p>Compiles, links, and builds an ELF binary for the target named <target-name>. It builds an ELF file for the application specified by the <code>app</code> variable for the <code>target-name</code> target. The image can be loaded and run on the hardware specified by the <code>bsp</code> variable for the target. The command creates the 'bin/' directory under the project's base directory (that the <code>newt new</code> command created) and stores the executable in the 'bin/targets/<target-name>/app/apps/<app-name>' directory.</p>
+<p>You can specify a list of target names, separated by a space, to build multiple targets. </p>
<h4 id="examples">Examples</h4>
<table>
<thead>
@@ -528,19 +535,14 @@
</thead>
<tbody>
<tr>
-<td>build</td>
-<td>newt build <br> <code>input1</code></td>
-<td>Builds the source code into an image that can be loaded on the hardware (<code>bsp</code>) associated with the target named <code>input1</code> to run the application enabled by the <code>app</code> 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.</td>
-</tr>
-<tr>
<td></td>
<td>newt build <br> my_blinky_sim</td>
-<td>For example, if <code>app</code> was set to <code>apps/blinky</code> 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 <code>newt new</code> at the start of the project.</td>
+<td>Builds an executable for the <code>my_blinky_sim</code> target. For example, if the <code>my_blinky_sim</code> target has <code>app</code> set to <code>apps/blinky</code>, you will find the generated .elf, .a, and .lst files in the 'bin/targets/my_blinky_sim/app/apps/blinky' directory.</td>
</tr>
<tr>
-<td>build</td>
-<td>newt build my_blinky_sim myble</td>
-<td>builds the apps defined for both the targets "my_blinky_sim" and "myble".</td>
+<td></td>
+<td>newt build <br> my_blinky_sim myble</td>
+<td>Builds the images for the applications defined by the <code>my_blinky_sim</code> and <code>myble</code> targets.</td>
</tr>
</tbody>
</table>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/command_list/newt_clean/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/command_list/newt_clean/index.html b/develop/newt/command_list/newt_clean/index.html
index 7dad2dd..58f9763 100644
--- a/develop/newt/command_list/newt_clean/index.html
+++ b/develop/newt/command_list/newt_clean/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,55 +504,49 @@
</div>
<h2 id="newt-clean"><font color="#F2853F" style="font-size:24pt">newt clean </font></h2>
-<p>Deletes application build artifacts for a specified target</p>
+<p>Delete build artifacts for one or more targets. </p>
<h4 id="usage">Usage:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt clean [flags] input1
-</pre></div>
-
-
-<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for target
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt clean <target-name> [target-name...] | all [flags]
</pre></div>
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -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.
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
</pre></div>
<h4 id="description">Description</h4>
+<p>Deletes all the build artifacts generated for the <code>target-name</code> target. It does not delete the target definition. You can specify a list of targets, separated by a space, to delete the artifacts for multiple targets, or specify <code>all</code> to delete the artifacts for all targets.</p>
+<h4 id="examples">Examples</h4>
<table>
<thead>
<tr>
<th>Sub-command</th>
+<th>Usage</th>
<th>Explanation</th>
</tr>
</thead>
<tbody>
<tr>
-<td>clean</td>
-<td>Deletes all the build artifacts generated for target specified by <code>input1</code>. It does not delete the target definition.</td>
+<td></td>
+<td>newt clean myble</td>
+<td>Deletes the 'bin/targets/myble' directory where all the build artifacts generated from the <code>myble</code> target build are stored.</td>
</tr>
-</tbody>
-</table>
-<h4 id="examples">Examples</h4>
-<table>
-<thead>
<tr>
-<th>Sub-command</th>
-<th>Usage</th>
-<th>Explanation</th>
+<td></td>
+<td>newt clean my_blinky_sim myble</td>
+<td>Deletes the 'bin/targets/my_blinky_sim' and the 'bin/targets/myble' directories where all the artifacts generated from the <code>my_blinky_sim</code> and <code>myble</code> target builds are stored.</td>
</tr>
-</thead>
-<tbody>
<tr>
-<td>clean</td>
-<td>newt clean myble2</td>
-<td>Removes all the files generated while building the target <code>myble2</code> and placed in the <code>bin/myble2</code> directory created during the build process.</td>
+<td></td>
+<td>newt clean all</td>
+<td>Removes the artifacts for all target builds. Deletes the top level 'bin' directory.</td>
</tr>
</tbody>
</table>
@@ -565,8 +567,8 @@
</li>
<li class="pull-right">
- <a href=../newt_complete/>
- Next: newt complete
+ <a href=../newt_create_image/>
+ Next: newt create-image
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/command_list/newt_complete/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/command_list/newt_complete/index.html b/develop/newt/command_list/newt_complete/index.html
deleted file mode 100644
index b895444..0000000
--- a/develop/newt/command_list/newt_complete/index.html
+++ /dev/null
@@ -1,576 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta http-equiv="X-UA-Compatible" content="IE=edge">
- <meta name="viewport" content="width=device-width, initial-scale=1.0">
-
-
- <!-- This is broken by doc revisioning.
- <link rel="canonical" href="http://mynewt.apache.org/newt/command_list/newt_complete/"> -->
- <link rel="shortcut icon" href="../../../img/favicon.ico">
-
- <title>newt complete - Apache Mynewt</title>
-
- <link href="../../../css/bootstrap-3.0.3.min.css" rel="stylesheet">
- <link rel="stylesheet" href="../../../css/highlight.css">
- <link href="../../../css/base.css" rel="stylesheet">
- <link href="../../../css/custom.css" rel="stylesheet">
- <link href="../../../css/v2.css" rel="stylesheet">
- <link href="https://fonts.googleapis.com/css?family=Lato" rel="stylesheet">
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css">
- <link href="../../../extra.css" rel="stylesheet">
-
- <!-- HTML5 shim and Respond.js IE8 support of HTML5 elements and media queries -->
- <!--[if lt IE 9]>
- <script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script>
- <script src="https://oss.maxcdn.com/libs/respond.js/1.3.0/respond.min.js"></script>
- <![endif]-->
-
-
- <script>
- (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
- (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
- m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
- })(window,document,'script','//www.google-analytics.com/analytics.js','ga');
-
- ga('create', 'UA-72162311-1', 'auto');
- ga('send', 'pageview');
- </script>
-
- </head>
-
-
- <body class="newt complete">
-
-
- <div class="container">
- <div class="row v2-main-banner">
- <a class="logo-cell" href="/">
- <img class="logo" src="/img/logo.png">
- </a>
- <div class="tagline-cell">
- <h4 class="tagline">An OS to build, deploy and securely manage billions of devices</h4>
- </div>
- <div class="news-cell">
- <div class="well">
- <h4>Latest News:</h4> <a href="/download">Apache Mynewt 1.0.0-b2</a> released (Feb 15, 2017)
- </div>
- </div>
- </div>
-</div>
-
-
-
-
-
-
-
-
-<nav id="navbar" class="navbar navbar-inverse affix-top" data-spy="affix" data-offset-top="150" role="navigation">
- <div class="container">
- <!-- Collapsed navigation -->
- <div class="navbar-header">
- <!-- Expander button -->
- <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
- <span class="sr-only">Toggle navigation</span>
- <span class="icon-bar"></span>
- <span class="icon-bar"></span>
- <span class="icon-bar"></span>
- </button>
-
- </div>
-
- <!-- Expanded navigation -->
- <div class="navbar-collapse collapse">
- <!-- Main navigation -->
- <ul class="nav navbar-nav navbar-right">
- <li
- class=""
->
- <a href="/"><i class="fa fa-home" style="font-size: larger;"></i></a>
- </li>
- <li
- class="important"
->
- <a href="/quick-start/">Quick Start</a>
- </li>
- <li
- class=""
->
- <a href="/about/">About</a>
- </li>
- <li
- class=""
->
- <a href="/talks/">Talks</a>
- </li>
- <li
- class="active"
->
- <a href="/latest/os/introduction">Documentation</a>
- </li>
- <li
- class=""
->
- <a href="/download/">Download</a>
- </li>
- <li
- class=""
->
- <a href="/community/">Community</a>
- </li>
- <li
- class=""
->
- <a href="/events/">Events</a>
- </li>
- </ul>
-
- <!-- Search, Navigation and Repo links -->
- <ul class="nav navbar-nav navbar-right">
-
- </ul>
- </div>
- </div>
-</nav>
-
-
-
- <div class="container">
-
- <div class="row">
- <div class="col-md-3 v2-sidebar sidebar-container"><div id="docSidebar" class="hidden-print" role="complementary">
- <div class="top">
- <div role="search">
- <form id="rtd-search-form" class="wy-form" action="../../../search.html" method="get">
- <div class="form-group">
- <input type="text" name="q" class="form-control" placeholder="Search documentation" />
- </div>
- </form>
- </div>
- </div>
- <ul class="toc-nav">
- <li class="doc-version">
-<select class="form-control" onchange="if (this.value) window.location.href=this.value">
-
- <option
- value="/develop/os/introduction"
- selected="selected"
- >
- Version: develop (latest)
- </option>
-
- <option
- value="/v0_9_0/os/introduction"
-
- >
- Version: 0.9.0
- </option>
-
-</select>
-</li>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- <li ><a href="../../../os/introduction/">Mynewt Documentation</a>
-
-
- <ul>
-
-
-
-
-
-
-
- <li ><a href="../../../os/get_started/get_started/">Basic Setup</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../../../os/get_started/vocabulary/">Concepts</a>
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../../os/tutorials/tutorials/">Tutorials</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../../os/os_user_guide/">OS User Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../../../network/ble/ble_intro/
-">BLE User Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../newt_intro/">Newt Tool Guide</a>
-
-
- <ul>
-
-
-
-
-
- <li >
- <a href="../../newt_operation/">Newt Theory of Ops</a>
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../newt_ops/">Command Guide</a>
-
-
- <ul>
-
-
-
-
-
- <li >
- <a href="../newt_build/">newt build</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_clean/">newt clean</a>
- </li>
-
-
-
-
-
- <li class="active">
- <a href="./">newt complete</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_create_image/">newt create-image</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_debug/">newt debug</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_help/">newt help</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_info/">newt info</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_install/">newt install</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_load/">newt load</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_mfg/">newt mfg</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_new/">newt new</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_run/">newt run</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_size/">newt size</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_target/">newt target</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_test/">newt test</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_upgrade/">newt upgrade</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_vals/">newt vals</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../newt_version/">newt version</a>
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../../newtmgr/overview/">Newt Manager Guide</a>
-
-
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../../../faq/how_to_edit_docs/
-">Appendix</a>
-
-
- </li>
-
-
-
- </ul>
-</div></div>
-
- <div class="col-md-9" role="main">
- <div class="doc-header">
- <div role="navigation" aria-label="breadcrumbs navigation">
- <ul class="wy-breadcrumbs pull-right">
- <li><a href="/develop/os/introduction">Docs</a></li>
-
-
-
- <li>» <a href="../../newt_intro/">Newt Tool Guide</a></li>
-
-
-
- <li>» <a href="../../newt_ops/">Command Guide</a></li>
-
-
-
- <li>» newt complete</li>
-
-
-
- </ul>
-</div>
- </div>
-
- <h2 id="newt-complete"><font color="#F2853F" style="font-size:24pt">newt complete </font></h2>
-<p>Performs bash autocompletion using tab. It is not intended to be called directly from the command line.</p>
-<h4 id="install-bash-autocompletion">Install bash autocompletion</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ brew install bash-completion
- Updating Homebrew...
- <snip>
- Bash completion has been installed to:
- /usr/local/etc/bash_completion.d
- ==> Summary
- \U0001f37a /usr/local/Cellar/bash-completion/1.3_1: 189 files, 607.8K
-</pre></div>
-
-
-<h4 id="enable-autocompletion-for-newt">Enable autocompletion for newt</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ complete -C "newt complete" newt
-</pre></div>
-
-
-<h4 id="usage">Usage</h4>
-<p>Hit tab and see possible completion options or completed command.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newt target s
- set show
- $ newt target show
-</pre></div>
-
- <div class="row">
-
-
-
-
-<ul class="nav nav-pills" style="margin-bottom: 10px">
- <li>
-
- <a href=../newt_clean/>
- <span class="fa fa-arrow-left"></span>
- Previous: newt clean
- </a>
-
- </li>
- <li class="pull-right">
-
- <a href=../newt_create_image/>
- Next: newt create-image
- <span class="fa fa-arrow-right"></span>
- </a>
-
- </li>
-</ul>
- </div>
- <footer class="row">
- <div class="col-xs-12">
-
- <p class="copyright">Apache Mynewt (incubating) is available under Apache License, version 2.0.</p>
-
- </div>
- <div class="col-xs-12">
- <div class="logos">
- <img src="/img/asf_logo_wide_small.png" alt="Apache" title="Apache">
- <small class="footnote">
- MyNewt is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
- </small>
- <img src="/img/egg-logo2.png" alt="Apache Incubator" title="Apache Incubator">
- </div>
- </div>
-</footer>
- </div>
- </div>
-
-
- </div>
-
- <script src="../../../js/jquery-1.10.2.min.js"></script>
- <script src="../../../js/bootstrap-3.0.3.min.js"></script>
- <script src="../../../js/highlight.pack.js"></script>
- <script src="../../../js/base.js"></script>
- <script src="../../../js/custom.js"></script>
-
- </body>
-</html>
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/command_list/newt_create_image/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/command_list/newt_create_image/index.html b/develop/newt/command_list/newt_create_image/index.html
index e3df439..8627af4 100644
--- a/develop/newt/command_list/newt_create_image/index.html
+++ b/develop/newt/command_list/newt_create_image/index.html
@@ -300,14 +300,6 @@
- <li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
<li class="active">
<a href="./">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,41 +504,26 @@
</div>
<h2 id="newt-create-image"><font color="#F2853F" style="font-size:24pt">newt create-image </font></h2>
-<p>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> </p>
+<p>Create and sign an image by adding an image header to the binary file created for a target. Version number in the header is set to <version>. To sign an image provide a .pem file for the signing-key and an optional key-id.</p>
<h4 id="usage">Usage:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt create-image <target-name> <version> [flags]
-</pre></div>
-
-
-<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for target
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt create-image <target-name> <version> [signing-key [key-id]][flags]
</pre></div>
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -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.
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
</pre></div>
<h4 id="description">Description</h4>
-<table>
-<thead>
-<tr>
-<th>Sub-command</th>
-<th>Explanation</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>create-image</td>
-<td>Signs and adds image header to the created binary file for target named <code><target-name></code> and given the version specified as <code><version></code>. The application image generated is <code><app-name>.img</code> where the app-name is the same as the app specified in the target definition. The generated application image can be found in <code>/bin/<target-name>/apps/<app-name>/</code>. <br> <br> A build manifest file <code>manifest.json</code> 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.</td>
-</tr>
-</tbody>
-</table>
+<p>Adds an image header to the created binary file for the <code>target-name</code> target. The image version is set to <code>version</code>. It creates a <code><app-name>.img</code> file for the image, where <code>app-name</code> is the value specified in the target <code>app</code> variable, and stores the file in the '/bin/targets/<target-name>/app/apps/<app-name>/' directory. A <code>manifest.json</code> build manifest file 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.</p>
+<p>To sign an image, provide a .pem file for the <code>signing-key</code> and an optional <code>key-id</code>. <code>key-id</code> must be a value between 0-255.</p>
<h4 id="examples">Examples</h4>
<table>
<thead>
@@ -542,9 +535,14 @@
</thead>
<tbody>
<tr>
-<td>create-image</td>
+<td></td>
<td>newt create-image myble2 1.0.1.0</td>
-<td>Creates a signed image for target <code>myble2</code> and assigns it the version <code>1.0.1.0</code>. <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 <code>bin/myble2/apps/bletiny/bletiny.img</code> and the manifest is <code>bin/myble2/apps/bletiny/manifest.json</code></td>
+<td>Creates an image for target <code>myble2</code> and assigns it version <code>1.0.1.0</code>. <br> <br> For the following target definition: <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> the created image is 'bin/targets/myble2/app/apps/bletiny/bletiny.img' and the manifest is 'bin/targets/myble2/app/apps/bletiny/manifest.json'</td>
+</tr>
+<tr>
+<td></td>
+<td>newt create-image myble2 1.0.1.0 private.pem</td>
+<td>Creates an image for target <code>myble2</code> and assigns it the version <code>1.0.1.0</code>. Signs the image using private key specified by the private.pem file.</td>
</tr>
</tbody>
</table>
@@ -557,9 +555,9 @@
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../newt_complete/>
+ <a href=../newt_clean/>
<span class="fa fa-arrow-left"></span>
- Previous: newt complete
+ Previous: newt clean
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/command_list/newt_debug/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/command_list/newt_debug/index.html b/develop/newt/command_list/newt_debug/index.html
index 814df61..069f0a0 100644
--- a/develop/newt/command_list/newt_debug/index.html
+++ b/develop/newt/command_list/newt_debug/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,41 +504,31 @@
</div>
<h2 id="newt-debug"><font color="#F2853F" style="font-size:24pt">newt debug </font></h2>
-<p>Opens debugger session for specified target. </p>
+<p>Open a debugger session to a target. </p>
<h4 id="usage">Usage:</h4>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt debug <target-name> [flag]
</pre></div>
<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for target
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> --extrajtagcmd string Extra commands to send to JTAG software
+ -n, --noGDB Do not start GDB from command line
</pre></div>
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -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.
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
</pre></div>
<h4 id="description">Description</h4>
-<table>
-<thead>
-<tr>
-<th>Sub-command</th>
-<th>Explanation</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>debug</td>
-<td>Opens the appropriate debugging session for the image built for the named target.</td>
-</tr>
-</tbody>
-</table>
+<p>Opens a debugger session to the image built for the <target-name> target.</p>
<h4 id="examples">Examples</h4>
<table>
<thead>
@@ -542,9 +540,14 @@
</thead>
<tbody>
<tr>
-<td>debug</td>
+<td></td>
<td>newt debug myble2</td>
-<td>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</td>
+<td>Opens a J-Link connection and starts a GNU gdb session to debug bin/targets/myble2/app/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</td>
+</tr>
+<tr>
+<td></td>
+<td>newt debug myble2 -n</td>
+<td>Opens a J-Link connection bin/targets/myble2/app/apps/bletiny/bletiny.elf but do not start GDB on the command line.</td>
</tr>
</tbody>
</table>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/command_list/newt_help/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/command_list/newt_help/index.html b/develop/newt/command_list/newt_help/index.html
index 5393bb0..aa0de6c 100644
--- a/develop/newt/command_list/newt_help/index.html
+++ b/develop/newt/command_list/newt_help/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,7 +504,7 @@
</div>
<h2 id="newt-help"><font color="#F2853F" style="font-size:24pt">newt help </font></h2>
-<p>Displays the help text for the newt command line tool:</p>
+<p>Display the help text for the newt command line tool:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">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
@@ -507,35 +515,40 @@ https://mynewt.apache.org/.
<h4 id="usage">Usage:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt help [input1]
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt help [command]
</pre></div>
-<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for newt
+<h4 id="global-flags">Global Flags:</h4>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (default "WARN")
-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.
+ -q, --quiet Be quiet; only display error output
+ -s, --silent Be silent; don't output anything
+ -v, --verbose Enable verbose output when executing commands
</pre></div>
<h4 id="available-commands">Available Commands:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> version Display the Newt version number.
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> build Build one or more targets
+ clean Delete build artifacts for one or more targets
+ create-image Add image header to target binary
+ debug Open debugger session to target
+ info Show project info
install Install project dependencies
- upgrade Upgrade project dependencies
+ load Load built target to board
+ mfg Manufacturing flash image commands
new Create a new project
- info Show project info
+ pkg Create and manage packages in the current workspace
+ run build/create-image/download/debug <target>
+ size Size of target components
+ sync Synchronize project dependencies
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>
+ upgrade Upgrade project dependencies
+ vals Display valid values for the specified element type(s)
+ version Display the Newt version number
</pre></div>
@@ -550,12 +563,12 @@ https://mynewt.apache.org/.
</thead>
<tbody>
<tr>
-<td>help</td>
+<td></td>
<td>newt help target</td>
-<td>Displays the help text for the newt command 'target'</td>
+<td>Displays the help text for the newt <code>target</code> command</td>
</tr>
<tr>
-<td>help</td>
+<td></td>
<td>newt help</td>
<td>Displays the help text for newt tool</td>
</tr>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/command_list/newt_info/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/command_list/newt_info/index.html b/develop/newt/command_list/newt_info/index.html
index aa64e1c..f7faba0 100644
--- a/develop/newt/command_list/newt_info/index.html
+++ b/develop/newt/command_list/newt_info/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,36 +504,25 @@
</div>
<h2 id="newt-info"><font color="#F2853F" style="font-size:24pt">newt info </font></h2>
-<p>Shows information about the current project.</p>
+<p>Show information about the current project.</p>
<h4 id="usage">Usage:</h4>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt info [flags]
</pre></div>
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -l, --loglevel="WARN": Log level, defaults to WARN.
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (default "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.
+ -q, --quiet Be quiet; only display error output
+ -s, --silent Be silent; don't output anything
+ -v, --verbose Enable verbose output when executing commands
</pre></div>
<h4 id="description">Description</h4>
-<table>
-<thead>
-<tr>
-<th>Sub-command</th>
-<th>Explanation</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>info</td>
-<td>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.</td>
-</tr>
-</tbody>
-</table>
+<p>Displays the repositories in the current project (the local as well as all the external repositories fetched). It also displays the packages in the local repository.</p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/command_list/newt_install/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/command_list/newt_install/index.html b/develop/newt/command_list/newt_install/index.html
index 5dfed10..b708640 100644
--- a/develop/newt/command_list/newt_install/index.html
+++ b/develop/newt/command_list/newt_install/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,42 +504,31 @@
</div>
<h2 id="newt-install"><font color="#F2853F" style="font-size:24pt">newt install </font></h2>
-<p>Install project dependencies. </p>
+<p>Install project dependencies. </p>
<h4 id="usage">Usage:</h4>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt install [flags]
</pre></div>
<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -f, --force Force install of the repositories in project, regardless of what exists in repos directory
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -f, --force Force install of the repositories in project, regardless of what exists in repos directory
</pre></div>
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for newt
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (default "WARN")
-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.
+ -q, --quiet Be quiet; only display error output
+ -s, --silent Be silent; don't output anything
+ -v, --verbose Enable verbose output when executing commands
</pre></div>
<h4 id="description">Description</h4>
-<table>
-<thead>
-<tr>
-<th>Sub-command</th>
-<th>Explanation</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>install</td>
-<td>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 <code>cd</code> into the app directory after creating a new app using <code>newt new</code>) before running <code>newt install</code>.</td>
-</tr>
-</tbody>
-</table>
+<p>This command downloads the description for all the repositories specified in the <code>project.yml</code> file for the current project, and installs the correct versions of all the packages specified by the project dependencies. </p>
+<p>You must run this command from within the current project directory. (Remember to <code>cd</code> into this project directory after you use <code>newt new</code> to create this project before you run <code>newt install</code>.)</p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/command_list/newt_load/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/command_list/newt_load/index.html b/develop/newt/command_list/newt_load/index.html
index 315e423..4250314 100644
--- a/develop/newt/command_list/newt_load/index.html
+++ b/develop/newt/command_list/newt_load/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,41 +504,30 @@
</div>
<h2 id="newt-load"><font color="#F2853F" style="font-size:24pt">newt load </font></h2>
-<p>Load app image to specified target. </p>
+<p>Load application image onto the board for a target. </p>
<h4 id="usage">Usage:</h4>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt load <target-name> [flags]
</pre></div>
<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for target
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> --extrajtagcmd string Extra commands to send to JTAG software
</pre></div>
-<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -l, --loglevel="WARN": Log level, defaults to WARN.
+<h3 id="global-flags">Global Flags:</h3>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (default "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.
+ -q, --quiet Be quiet; only display error output
+ -s, --silent Be silent; don't output anything
+ -v, --verbose Enable verbose output when executing commands
</pre></div>
<h4 id="description">Description</h4>
-<table>
-<thead>
-<tr>
-<th>Sub-command</th>
-<th>Explanation</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>load</td>
-<td>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 <code>Can not connect to J-Link via USB</code> or <code>Unspecified error -1</code>.</td>
-</tr>
-</tbody>
-</table>
+<p>Uses download scripts to automatically load, onto the connected board, the image built for the app defined by the <code>target-name</code> target If the wrong board is connected or the target definition is incorrect (i.e. the wrong values are given for bsp or app), the command will fail with error messages such as <code>Can not connect to J-Link via USB</code> or <code>Unspecified error -1</code>. </p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/command_list/newt_mfg/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/command_list/newt_mfg/index.html b/develop/newt/command_list/newt_mfg/index.html
index 8533b7e..b93f89f 100644
--- a/develop/newt/command_list/newt_mfg/index.html
+++ b/develop/newt/command_list/newt_mfg/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,7 +504,7 @@
</div>
<h2 id="newt-mfg"><font color="#F2853F" style="font-size:24pt">newt mfg </font></h2>
-<p>Provides commands to create, build, and upload manufacturing image. </p>
+<p>Commands to create, build, and upload manufacturing image. </p>
<h4 id="usage">Usage:</h4>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt mfg [flags]
newt mfg [command]
@@ -505,22 +513,19 @@
<h4 id="available-commands">Available Commands:</h4>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> create Create a manufacturing flash image
- deploy Builds and uploads a manufacturing image (build + load)
+ deploy Build and upload a manufacturing image (build + load)
load Load a manufacturing flash image onto a device
</pre></div>
-<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for mfg
-</pre></div>
-
-
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -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.
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
</pre></div>
@@ -535,7 +540,7 @@
<tbody>
<tr>
<td>create</td>
-<td>A manufacturing image specifies 1) a boot loader target, and 2) one or more image targets. Assuming the manufacturing entity has been created and defined in the <code>mfgs/<mfg image name>/</code> package(see Examples below), this command collects the manufacturing related files in the newly created <code>bin/mfgs/<mfg image name></code> directory. The collection includes manifests with the image build time, version, manufacturing package build time, image ID (or hash) etc. It is essentially a snapshot of the image data and metadata uploaded to the device flash at manufacturing time. Note that the command expects the targets and images to have already been built using <code>newt build</code> and <code>newt create-image</code> commands.</td>
+<td>A manufacturing image specifies 1) a boot loader target, and 2) one or more image targets. Assuming the manufacturing entity has been created and defined in the <code>mfgs/<mfg image name>/</code> package (see Examples below), this command collects the manufacturing related files in the newly created <code>bin/mfgs/<mfg image name></code> directory. The collection includes manifests with the image build time, version, manufacturing package build time, image ID (or hash) etc. It is essentially a snapshot of the image data and metadata uploaded to the device flash at manufacturing time. Note that the command expects the targets and images to have already been built using <code>newt build</code> and <code>newt create-image</code> commands.</td>
</tr>
<tr>
<td>deploy</td>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/command_list/newt_new/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/command_list/newt_new/index.html b/develop/newt/command_list/newt_new/index.html
index f261703..aa8eba3 100644
--- a/develop/newt/command_list/newt_new/index.html
+++ b/develop/newt/command_list/newt_new/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,27 +504,25 @@
</div>
<h2 id="newt-new"><font color="#F2853F" style="font-size:24pt">newt new </font></h2>
-<p>Create a new application, specified by <app-name>, from a given skeleton. Currently, the default skeleton is the <a href="https://git-wip-us.apache.org/repos/asf/incubator-mynewt-blinky.git">blinky repository</a> in Apache Mynewt (or <a href="https://github.com/apache/incubator-mynewt-blinky">https://github.com/apache/incubator-mynewt-blinky</a> on its github mirror.)</p>
+<p>Create a new project from a skeleton. Currently, the default skeleton is the <a href="https://git-wip-us.apache.org/repos/asf/incubator-mynewt-blinky.git">blinky repository</a> in Apache Mynewt (or <a href="https://github.com/apache/incubator-mynewt-blinky">https://github.com/apache/incubator-mynewt-blinky</a> on its github mirror.)</p>
<h4 id="usage">Usage:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt new [flags] <app-name>
-</pre></div>
-
-
-<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for new
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt new <project-name> [flags]
</pre></div>
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for newt
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (default "WARN")
-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.
+ -q, --quiet Be quiet; only display error output
+ -s, --silent Be silent; don't output anything
+ -v, --verbose Enable verbose output when executing commands
</pre></div>
+<h3 id="description">Description</h3>
+<p>Creates a new project named <code>project-name</code> from the default skeleton <a href="https://git-wip-us.apache.org/repos/asf/incubator-mynewt-blinky.git">blinky repository</a> in Apache Mynewt (or <a href="https://github.com/apache/incubator-mynewt-blinky">https://github.com/apache/incubator-mynewt-blinky</a> on its github mirror.)</p>
<h4 id="examples">Examples</h4>
<table>
<thead>
@@ -528,9 +534,9 @@
</thead>
<tbody>
<tr>
-<td>newt new</td>
+<td></td>
<td>newt new test_project</td>
-<td>Creates a new app named "test_project " using the default skeleton from the <code>apache/incubator-mynewt-blinky</code> repo.</td>
+<td>Creates a new project named <code>test_project</code> using the default skeleton from the <code>apache/incubator-mynewt-blinky</code> repository.</td>
</tr>
</tbody>
</table>
@@ -551,8 +557,8 @@
</li>
<li class="pull-right">
- <a href=../newt_run/>
- Next: newt run
+ <a href=../newt_pkg/>
+ Next: newt pkg
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/command_list/newt_pkg/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/command_list/newt_pkg/index.html b/develop/newt/command_list/newt_pkg/index.html
new file mode 100644
index 0000000..0afbb60
--- /dev/null
+++ b/develop/newt/command_list/newt_pkg/index.html
@@ -0,0 +1,648 @@
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <meta charset="utf-8">
+ <meta http-equiv="X-UA-Compatible" content="IE=edge">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+
+ <!-- This is broken by doc revisioning.
+ <link rel="canonical" href="http://mynewt.apache.org/newt/command_list/newt_pkg/"> -->
+ <link rel="shortcut icon" href="../../../img/favicon.ico">
+
+ <title>newt pkg - Apache Mynewt</title>
+
+ <link href="../../../css/bootstrap-3.0.3.min.css" rel="stylesheet">
+ <link rel="stylesheet" href="../../../css/highlight.css">
+ <link href="../../../css/base.css" rel="stylesheet">
+ <link href="../../../css/custom.css" rel="stylesheet">
+ <link href="../../../css/v2.css" rel="stylesheet">
+ <link href="https://fonts.googleapis.com/css?family=Lato" rel="stylesheet">
+ <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css">
+ <link href="../../../extra.css" rel="stylesheet">
+
+ <!-- HTML5 shim and Respond.js IE8 support of HTML5 elements and media queries -->
+ <!--[if lt IE 9]>
+ <script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script>
+ <script src="https://oss.maxcdn.com/libs/respond.js/1.3.0/respond.min.js"></script>
+ <![endif]-->
+
+
+ <script>
+ (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
+ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
+ m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
+ })(window,document,'script','//www.google-analytics.com/analytics.js','ga');
+
+ ga('create', 'UA-72162311-1', 'auto');
+ ga('send', 'pageview');
+ </script>
+
+ </head>
+
+
+ <body class="newt pkg">
+
+
+ <div class="container">
+ <div class="row v2-main-banner">
+ <a class="logo-cell" href="/">
+ <img class="logo" src="/img/logo.png">
+ </a>
+ <div class="tagline-cell">
+ <h4 class="tagline">An OS to build, deploy and securely manage billions of devices</h4>
+ </div>
+ <div class="news-cell">
+ <div class="well">
+ <h4>Latest News:</h4> <a href="/download">Apache Mynewt 1.0.0-b2</a> released (Feb 15, 2017)
+ </div>
+ </div>
+ </div>
+</div>
+
+
+
+
+
+
+
+
+<nav id="navbar" class="navbar navbar-inverse affix-top" data-spy="affix" data-offset-top="150" role="navigation">
+ <div class="container">
+ <!-- Collapsed navigation -->
+ <div class="navbar-header">
+ <!-- Expander button -->
+ <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
+ <span class="sr-only">Toggle navigation</span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ </button>
+
+ </div>
+
+ <!-- Expanded navigation -->
+ <div class="navbar-collapse collapse">
+ <!-- Main navigation -->
+ <ul class="nav navbar-nav navbar-right">
+ <li
+ class=""
+>
+ <a href="/"><i class="fa fa-home" style="font-size: larger;"></i></a>
+ </li>
+ <li
+ class="important"
+>
+ <a href="/quick-start/">Quick Start</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/about/">About</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/talks/">Talks</a>
+ </li>
+ <li
+ class="active"
+>
+ <a href="/latest/os/introduction">Documentation</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/download/">Download</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/community/">Community</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/events/">Events</a>
+ </li>
+ </ul>
+
+ <!-- Search, Navigation and Repo links -->
+ <ul class="nav navbar-nav navbar-right">
+
+ </ul>
+ </div>
+ </div>
+</nav>
+
+
+
+ <div class="container">
+
+ <div class="row">
+ <div class="col-md-3 v2-sidebar sidebar-container"><div id="docSidebar" class="hidden-print" role="complementary">
+ <div class="top">
+ <div role="search">
+ <form id="rtd-search-form" class="wy-form" action="../../../search.html" method="get">
+ <div class="form-group">
+ <input type="text" name="q" class="form-control" placeholder="Search documentation" />
+ </div>
+ </form>
+ </div>
+ </div>
+ <ul class="toc-nav">
+ <li class="doc-version">
+<select class="form-control" onchange="if (this.value) window.location.href=this.value">
+
+ <option
+ value="/develop/os/introduction"
+ selected="selected"
+ >
+ Version: develop (latest)
+ </option>
+
+ <option
+ value="/v0_9_0/os/introduction"
+
+ >
+ Version: 0.9.0
+ </option>
+
+</select>
+</li>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ <li ><a href="../../../os/introduction/">Mynewt Documentation</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../../../os/get_started/get_started/">Basic Setup</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../../os/get_started/vocabulary/">Concepts</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../os/tutorials/tutorials/">Tutorials</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../os/os_user_guide/">OS User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../../network/ble/ble_intro/
+">BLE User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../newt_intro/">Newt Tool Guide</a>
+
+
+ <ul>
+
+
+
+
+
+ <li >
+ <a href="../../newt_operation/">Newt Theory of Ops</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../newt_ops/">Command Guide</a>
+
+
+ <ul>
+
+
+
+
+
+ <li >
+ <a href="../newt_build/">newt build</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_clean/">newt clean</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_create_image/">newt create-image</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_debug/">newt debug</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_help/">newt help</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_info/">newt info</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_install/">newt install</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_load/">newt load</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_mfg/">newt mfg</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_new/">newt new</a>
+ </li>
+
+
+
+
+
+ <li class="active">
+ <a href="./">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_run/">newt run</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_size/">newt size</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_target/">newt target</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_test/">newt test</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_upgrade/">newt upgrade</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_vals/">newt vals</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../newt_version/">newt version</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../newtmgr/overview/">Newt Manager Guide</a>
+
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../../faq/how_to_edit_docs/
+">Appendix</a>
+
+
+ </li>
+
+
+
+ </ul>
+</div></div>
+
+ <div class="col-md-9" role="main">
+ <div class="doc-header">
+ <div role="navigation" aria-label="breadcrumbs navigation">
+ <ul class="wy-breadcrumbs pull-right">
+ <li><a href="/develop/os/introduction">Docs</a></li>
+
+
+
+ <li>» <a href="../../newt_intro/">Newt Tool Guide</a></li>
+
+
+
+ <li>» <a href="../../newt_ops/">Command Guide</a></li>
+
+
+
+ <li>» newt pkg</li>
+
+
+
+ </ul>
+</div>
+ </div>
+
+ <h2 id="newt-pkg"><font color="#F2853F" style="font-size:24pt">newt pkg </font></h2>
+<p>Commands for creating and manipulating packages.</p>
+<h4 id="usage">Usage:</h4>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt pkg [command] [flags]
+</pre></div>
+
+
+<h4 id="flags">Flags:</h4>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -t, --type string Type of package to create: pkg, bsp, sdk. (default "pkg")
+</pre></div>
+
+
+<h4 id="global-flags">Global Flags:</h4>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
+</pre></div>
+
+
+<h4 id="description">Description</h4>
+<p>The pkg command provides subcommands to create and manage packages. The subcommands take one or two <code>package-name</code> arguments.</p>
+<table>
+<thead>
+<tr>
+<th>Sub-command</th>
+<th>Explanation</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>copy</td>
+<td>The copy <src-pkg> <dst-pkg> command creates the new <code>dst-pkg</code> package by cloning the <code>src-pkg</code> package.</td>
+</tr>
+<tr>
+<td>move</td>
+<td>The move <old-pkg> <new-pkg> command moves the <code>old-pkg</code> package to the <code>new-pkg</code> package.</td>
+</tr>
+<tr>
+<td>new</td>
+<td>The new <new-pkg> command creates a new package named <code>new-pkg</code>, from a template, in the current directory. You can create a package of type <code>pkg</code>, <code>bsp</code>, or <code>sdk</code>. The default package type is <code>pkg</code>. You use the -t flag to specify a different package type.</td>
+</tr>
+<tr>
+<td>remove</td>
+<td>The remove <my-pkg> command deletes the <code>my-pkg</code> package.</td>
+</tr>
+</tbody>
+</table>
+<h4 id="examples">Examples</h4>
+<table>
+<thead>
+<tr>
+<th>Sub-command</th>
+<th>Usage</th>
+<th>Explanation</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>copy</td>
+<td>newt pkg copy <br>apps/bletiny apps/new_bletiny</td>
+<td>Copies the <code>apps/bletiny</code> package to the <code>apps/new_bletiny</code>.</td>
+</tr>
+<tr>
+<td>move</td>
+<td>newt pkg move <br>apps/slinky apps/new_slinky</td>
+<td>Moves the <code>apps/slinky</code> package to the <code>apps/new_slinky</code> package.</td>
+</tr>
+<tr>
+<td>new</td>
+<td>newt pkg new apps/new_slinky</td>
+<td>Creates a package named <code>apps/new_slinky</code> of type <code>pkg</code> in the current directory.</td>
+</tr>
+<tr>
+<td>new</td>
+<td>newt pkg new hw/bsp/myboard -t bsp</td>
+<td>Creates a package named <code>hw/bsp/myboard</code> of type <code>bsp</code> in the current directory.</td>
+</tr>
+<tr>
+<td>remove</td>
+<td>newt pkg remove hw/bsp/myboard</td>
+<td>Removes the <code>hw/bsp/myboard</code> package.</td>
+</tr>
+</tbody>
+</table>
+
+ <div class="row">
+
+
+
+
+<ul class="nav nav-pills" style="margin-bottom: 10px">
+ <li>
+
+ <a href=../newt_new/>
+ <span class="fa fa-arrow-left"></span>
+ Previous: newt new
+ </a>
+
+ </li>
+ <li class="pull-right">
+
+ <a href=../newt_run/>
+ Next: newt run
+ <span class="fa fa-arrow-right"></span>
+ </a>
+
+ </li>
+</ul>
+ </div>
+ <footer class="row">
+ <div class="col-xs-12">
+
+ <p class="copyright">Apache Mynewt (incubating) is available under Apache License, version 2.0.</p>
+
+ </div>
+ <div class="col-xs-12">
+ <div class="logos">
+ <img src="/img/asf_logo_wide_small.png" alt="Apache" title="Apache">
+ <small class="footnote">
+ MyNewt is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
+ </small>
+ <img src="/img/egg-logo2.png" alt="Apache Incubator" title="Apache Incubator">
+ </div>
+ </div>
+</footer>
+ </div>
+ </div>
+
+
+ </div>
+
+ <script src="../../../js/jquery-1.10.2.min.js"></script>
+ <script src="../../../js/bootstrap-3.0.3.min.js"></script>
+ <script src="../../../js/highlight.pack.js"></script>
+ <script src="../../../js/base.js"></script>
+ <script src="../../../js/custom.js"></script>
+
+ </body>
+</html>
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/command_list/newt_run/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/command_list/newt_run/index.html b/develop/newt/command_list/newt_run/index.html
index 14fb69a..c794c99 100644
--- a/develop/newt/command_list/newt_run/index.html
+++ b/develop/newt/command_list/newt_run/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -372,6 +364,14 @@
+ <li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
<li class="active">
<a href="./">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,42 +504,32 @@
</div>
<h2 id="newt-run"><font color="#F2853F" style="font-size:24pt">newt run </font></h2>
-<p>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.</p>
-<p><strong>Note</strong>: If version number is omitted, create-image step is skipped</p>
+<p>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 the board.</p>
+<p><strong>Note</strong>: If the version number is omitted, the create-image step is skipped.</p>
<h4 id="usage">Usage:</h4>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt run <target-name> [<version>][flags]
</pre></div>
<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for target
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> --extrajtagcmd string Extra commands to send to JTAG software
+ -n, --noGDB Do not start GDB from the command line
</pre></div>
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -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.
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
</pre></div>
<h4 id="description">Description</h4>
-<table>
-<thead>
-<tr>
-<th>Sub-command</th>
-<th>Explanation</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>run</td>
-<td>Same as running <code>build <target></code>, <code>create-image <target> <version></code>, <code>load <target></code>, and <code>debug <target></code>.</td>
-</tr>
-</tbody>
-</table>
+<p>Same as running <code>build <target-name></code>, <code>create-image <target-name> <version></code>, <code>load <target-name></code>, and <code>debug <target-name></code>.</p>
<h4 id="examples">Examples</h4>
<table>
<thead>
@@ -543,14 +541,14 @@
</thead>
<tbody>
<tr>
-<td>run</td>
+<td></td>
<td>newt run blink_rigado</td>
-<td>First compiles and builds executable for running the app defined in the target <code>blink_rigado</code> 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.</td>
+<td>Compiles and builds the image for the <code>app</code> and the <code>bsp</code> defined for target <code>blink_rigado</code>, loads the image onto the board, and opens an active GNU gdb debugging session to run the image.</td>
</tr>
<tr>
-<td>run</td>
+<td></td>
<td>newt run ble_rigado 0.1.0.0</td>
-<td>First compiles and builds executable for running the app defined in the target <code>ble_rigado</code> 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.</td>
+<td>Compiles and builds the image for the <code>app</code> and the <code>bsp</code> defined for target <code>ble_rigado</code>, signs and creates the image with version number 0.1.0.0, loads the image onto the board, and 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.</td>
</tr>
</tbody>
</table>
@@ -563,9 +561,9 @@
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../newt_new/>
+ <a href=../newt_pkg/>
<span class="fa fa-arrow-left"></span>
- Previous: newt new
+ Previous: newt pkg
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/555f6f65/develop/newt/command_list/newt_size/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/command_list/newt_size/index.html b/develop/newt/command_list/newt_size/index.html
index f8fc2bb..a9e5d48 100644
--- a/develop/newt/command_list/newt_size/index.html
+++ b/develop/newt/command_list/newt_size/index.html
@@ -301,14 +301,6 @@
<li >
- <a href="../newt_complete/">newt complete</a>
- </li>
-
-
-
-
-
- <li >
<a href="../newt_create_image/">newt create-image</a>
</li>
@@ -373,6 +365,14 @@
<li >
+ <a href="../newt_pkg/">newt pkg</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_run/">newt run</a>
</li>
@@ -389,6 +389,14 @@
<li >
+ <a href="../newt_sync/">newt sync</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../newt_target/">newt target</a>
</li>
@@ -496,26 +504,31 @@
</div>
<h2 id="newt-size"><font color="#F2853F" style="font-size:24pt">newt size </font></h2>
-<p>Calculate the size of target components specified by <target-name></p>
+<p>Calculates the size of target components for a target.</p>
<h4 id="usage">Usage:</h4>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt size <target-name> [flags]
</pre></div>
<h4 id="flags">Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help=false: help for target
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -F, --flash Print FLASH statistics
+ -R, --ram Print RAM statistics
</pre></div>
<h4 id="global-flags">Global Flags:</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -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.
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (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
</pre></div>
+<h4 id="description">Description</h4>
+<p>Displays the RAM and FLASH size of each component for the <code>target-name</code> target. </p>
<h4 id="examples">Examples</h4>
<table>
<thead>
@@ -527,13 +540,13 @@
</thead>
<tbody>
<tr>
-<td>size</td>
+<td></td>
<td>newt size blink_rigado</td>
-<td>Inspects and lists the RAM and Flash memory use by each component (object files and libraries) of the target.</td>
+<td>Inspects and lists the RAM and Flash memory that each component (object files and libraries) for the <code>blink_rigado</code> target.</td>
</tr>
</tbody>
</table>
-<h4 id="example-output-for-newt-size-boot_olimex">Example output for <code>newt size boot_olimex</code>:</h4>
+<h4 id="example-output-for-newt-size-blink_rigado">Example output for <code>newt size blink_rigado</code>:</h4>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt size blink_rigado
FLASH RAM
9 223 *fill*
@@ -572,8 +585,8 @@ objsize
</li>
<li class="pull-right">
- <a href=../newt_target/>
- Next: newt target
+ <a href=../newt_sync/>
+ Next: newt sync
<span class="fa fa-arrow-right"></span>
</a>