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/04/08 00:21:16 UTC
[01/11] incubator-mynewt-site git commit: Updated Blinky and Slinky
tutorials with intro summaries,
remove legacy feature references in the tutorials
Repository: incubator-mynewt-site
Updated Branches:
refs/heads/asf-site 712b19e5a -> 408994010
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/rbnano2/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/rbnano2/index.html b/latest/os/tutorials/rbnano2/index.html
index 0e784fd..9654e16 100644
--- a/latest/os/tutorials/rbnano2/index.html
+++ b/latest/os/tutorials/rbnano2/index.html
@@ -232,14 +232,14 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
<ul>
+
+
<li >
<a href="../arduino_zero/">Blinky on Arduino Zero</a>
@@ -317,8 +317,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -326,7 +329,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -334,7 +337,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -342,20 +345,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -363,7 +361,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -371,7 +369,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -379,18 +377,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -398,15 +393,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -526,7 +524,7 @@
- <li>» <a href="../arduino_zero/">Project Blinky</a></li>
+ <li>» <a href="../blinky/">Project Blinky</a></li>
@@ -539,20 +537,12 @@
</div>
<h2 id="blinky-your-hello-world-on-redbear-nano-2">Blinky, your "Hello World!", on RedBear Nano 2</h2>
-<p><br></p>
-<h3 id="objective">Objective</h3>
-<p>Learn how to use packages from a default application repository of Mynewt to build your first <em>Hello World</em> application (Blinky) on a target board. Once built using the <em>newt</em> tool, this application will blink the LED lights on the target board.</p>
-<p>Create a project with a simple application that blinks an LED on a RedBear Nano 2 board. Download the application to the target and watch it blink!</p>
-<p><br></p>
+<p>This tutorial shows you how to create, build and run the Blinky application on a RedBear Nano 2 board.
+<br></p>
<h3 id="prerequisites">Prerequisites</h3>
-<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
<ul>
+<li>Meet the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
<li>Have a RedBear Nano 2 board. </li>
-<li>Have Internet connectivity to fetch remote Mynewt components.</li>
-<li>Have a computer to build a Mynewt application and connect to the board over USB.</li>
-<li>Install the Newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
-<li>Create a project space (directory structure) and populated it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.</li>
-<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section.</li>
</ul>
<p><strong>Note:</strong> You must install a patched version of OpenOCD .10.0 (See <a href="../../../os/tutorials/blinky_primo">Debugger Option 2 in the Arduino Primo Blinky Tutorial</a>).</p>
<h3 id="create-a-project">Create a Project</h3>
@@ -703,11 +693,6 @@ Loading app image into slot 1
<p>You should see a blue LED on the board blink!</p>
<p>Note: If the LED does not blink, try resetting your board.</p>
-<h3 id="conclusion">Conclusion</h3>
-<p>You have created, setup, compiled, loaded, and ran your first mynewt application for a RedBear Nano 2 board.</p>
-<p>We have more fun tutorials for you to get your hands dirty. Be bold and work on the OS with tutorials on <a href="../unit_test/">writing a test suite</a> or try enabling additional functionality such as <a href="../project-target-slinky/">remote comms</a> or <a href="../bletiny_project/">Bluetooth Low Energy</a> on your current board.</p>
-<p>If you see anything missing or want to send us feedback, please do so by signing up for appropriate mailing lists on our <a href="../../../community/">Community Page</a>.</p>
-<p>Keep on hacking and blinking!</p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/repo/add_repos/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/repo/add_repos/index.html b/latest/os/tutorials/repo/add_repos/index.html
index b1faee1..6a06e08 100644
--- a/latest/os/tutorials/repo/add_repos/index.html
+++ b/latest/os/tutorials/repo/add_repos/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../../blinky/">Project Blinky</a>
</li>
@@ -284,8 +282,11 @@
- <li >
- <a href="../../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -293,7 +294,7 @@
<li >
- <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../../ibeacon/">BLE iBeacon</a>
</li>
@@ -301,7 +302,7 @@
<li >
- <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../../eddystone/">BLE Eddystone</a>
</li>
@@ -309,20 +310,15 @@
<li >
- <a href="../../event_queue/">Events and Event Queues</a>
+ <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -330,7 +326,7 @@
<li >
- <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -338,7 +334,7 @@
<li >
- <a href="../../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -346,18 +342,15 @@
<li >
- <a href="../../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../../event_queue/">Events and Event Queues</a>
</li>
@@ -365,15 +358,18 @@
<li >
- <a href="../../ibeacon/">BLE iBeacon</a>
+ <a href="../../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -562,7 +558,7 @@ information on obtaining the repo.</p>
<p>In the same <code>myproj</code> above you will see the following repo descriptor.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">repository.apache-Mynewt-core:
type: github
- vers: 0-latest
+ vers: 1-latest
user: apache
repo: incubator-mynewt-core
</pre></div>
@@ -624,14 +620,14 @@ project.repositories:
#
repository.apache-Mynewt-core:
type: github
- vers: 0-latest
+ vers: 1-latest
user: apache
repo: incubator-mynewt-core
# a special repo to hold hardware specific stuff for arduino zero
repository.Mynewt_arduino_zero:
type: github
- vers: 0-latest
+ vers: 1-latest
user: runtimeinc
repo: Mynewt_arduino_zero
</pre></div>
@@ -643,8 +639,8 @@ repository.Mynewt_arduino_zero:
systems like github. The repo descriptor in your <code>project.yml</code> file must
specify the version of the repo you will accept into your project.</p>
<p>For now, we are at the beginnings of Mynewt. For testing and evaluation
-please use <code>0-latest</code> in the <code>vers</code> field in your repo descriptor.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> vers:0-latest
+please use <code>1-latest</code> in the <code>vers</code> field in your repo descriptor.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> vers:1-latest
</pre></div>
@@ -659,15 +655,22 @@ specified in your <code>project.yml</code> file. Special care should be taken t
<p>Here is the <code>repository.yml</code> file from the apache-Mynewt-core:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">repo.name: apache-mynewt-core
repo.versions:
- "0.0.0": "develop"
+ "0.0.0": "master"
+ "0.0.1": "master"
"0.7.9": "mynewt_0_8_0_b2_tag"
"0.8.0": "mynewt_0_8_0_tag"
"0.9.0": "mynewt_0_9_0_tag"
- "0.9.1": "master"
- "0-latest": "0.9.0"
- "0-dev": "0.9.1"
+ "0.9.9": "mynewt_1_0_0_b1_tag"
+ "0.9.99": "mynewt_1_0_0_b2_tag"
+ "0.9.999": "mynewt_1_0_0_rc1_tag"
+ "1.0.0": "mynewt_1_0_0_tag"
+
+ "0-latest": "1.0.0" # 1.0.0
+ "0-dev": "0.0.0" # master
+
"0.8-latest": "0.8.0"
"0.9-latest": "0.9.0"
+ "1.0-latest": "1.0.0" # 1.0.0
</pre></div>
@@ -706,7 +709,7 @@ on the settings in their <code>project.yml</code> file. </li>
<p>In your <code>project.yml</code> file you can specify different combinations of
the version number and stability value. For example:</p>
<ul>
-<li><code>0-latest</code> -- The latest version with major number 0</li>
+<li><code>1-latest</code> -- The latest version with major number 1</li>
<li><code>1.2-stable</code> -- The latest stable version with major and minor number 1.2</li>
<li><code>1.2-dev</code> -- The development version from 1.2</li>
<li><code>1.1.1</code> -- a specific version 1.1.1</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/repo/create_repo/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/repo/create_repo/index.html b/latest/os/tutorials/repo/create_repo/index.html
index ac64e81..248d90f 100644
--- a/latest/os/tutorials/repo/create_repo/index.html
+++ b/latest/os/tutorials/repo/create_repo/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../../blinky/">Project Blinky</a>
</li>
@@ -284,8 +282,11 @@
- <li >
- <a href="../../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -293,7 +294,7 @@
<li >
- <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../../ibeacon/">BLE iBeacon</a>
</li>
@@ -301,7 +302,7 @@
<li >
- <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../../eddystone/">BLE Eddystone</a>
</li>
@@ -309,20 +310,15 @@
<li >
- <a href="../../event_queue/">Events and Event Queues</a>
+ <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -330,7 +326,7 @@
<li >
- <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -338,7 +334,7 @@
<li >
- <a href="../../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -346,18 +342,15 @@
<li >
- <a href="../../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../../event_queue/">Events and Event Queues</a>
</li>
@@ -365,15 +358,18 @@
<li >
- <a href="../../ibeacon/">BLE iBeacon</a>
+ <a href="../../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -579,7 +575,7 @@ on versioning. Its a flexible mapping between version numbers and git branches.<
<p>In your <code>project.yml</code> file you can specify different combinations of
the version number and stability value. For example:</p>
<ul>
-<li><code>0-latest</code> -- The latest version with major number 0</li>
+<li><code>1-latest</code> -- The latest version with major number 1</li>
<li><code>1.2-stable</code> -- The latest stable version with major and minor number 1.2</li>
<li><code>1.2-dev</code> -- The development version from 1.2</li>
<li><code>1.1.1</code> -- a specific version 1.1.1</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/repo/private_repo/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/repo/private_repo/index.html b/latest/os/tutorials/repo/private_repo/index.html
index dd55a27..4ce1b9c 100644
--- a/latest/os/tutorials/repo/private_repo/index.html
+++ b/latest/os/tutorials/repo/private_repo/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../../blinky/">Project Blinky</a>
</li>
@@ -284,8 +282,11 @@
- <li >
- <a href="../../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -293,7 +294,7 @@
<li >
- <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../../ibeacon/">BLE iBeacon</a>
</li>
@@ -301,7 +302,7 @@
<li >
- <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../../eddystone/">BLE Eddystone</a>
</li>
@@ -309,20 +310,15 @@
<li >
- <a href="../../event_queue/">Events and Event Queues</a>
+ <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -330,7 +326,7 @@
<li >
- <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -338,7 +334,7 @@
<li >
- <a href="../../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -346,18 +342,15 @@
<li >
- <a href="../../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../../event_queue/">Events and Event Queues</a>
</li>
@@ -365,15 +358,18 @@
<li >
- <a href="../../ibeacon/">BLE iBeacon</a>
+ <a href="../../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -561,8 +557,8 @@ operations. This is something that will be fixed in the future.</p>
</li>
<li class="pull-right">
- <a href=../../tasks_lesson/>
- Next: Tasks and Priority Management
+ <a href=../../project-slinky/>
+ Next: Project Slinky for Remote Comms
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/repo/upgrade_repo/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/repo/upgrade_repo/index.html b/latest/os/tutorials/repo/upgrade_repo/index.html
index b3aa23e..53f3c58 100644
--- a/latest/os/tutorials/repo/upgrade_repo/index.html
+++ b/latest/os/tutorials/repo/upgrade_repo/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../../blinky/">Project Blinky</a>
</li>
@@ -284,8 +282,11 @@
- <li >
- <a href="../../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -293,7 +294,7 @@
<li >
- <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../../ibeacon/">BLE iBeacon</a>
</li>
@@ -301,7 +302,7 @@
<li >
- <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../../eddystone/">BLE Eddystone</a>
</li>
@@ -309,20 +310,15 @@
<li >
- <a href="../../event_queue/">Events and Event Queues</a>
+ <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -330,7 +326,7 @@
<li >
- <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -338,7 +334,7 @@
<li >
- <a href="../../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -346,18 +342,15 @@
<li >
- <a href="../../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../../event_queue/">Events and Event Queues</a>
</li>
@@ -365,15 +358,18 @@
<li >
- <a href="../../ibeacon/">BLE iBeacon</a>
+ <a href="../../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/tasks_lesson/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/tasks_lesson/index.html b/latest/os/tutorials/tasks_lesson/index.html
index fe9c6f7..62cddea 100644
--- a/latest/os/tutorials/tasks_lesson/index.html
+++ b/latest/os/tutorials/tasks_lesson/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li class="active">
- <a href="./">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,7 +264,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -271,7 +272,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -279,28 +280,23 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
- <li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <li class="active">
+ <a href="./">Tasks and Priority Management</a>
</li>
@@ -308,7 +304,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,18 +312,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -699,9 +695,9 @@ the <code>main</code> task sleeps, saving us idle time compared to the first cas
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../repo/private_repo/>
+ <a href=../add_shell/>
<span class="fa fa-arrow-left"></span>
- Previous: Access a private Repo
+ Previous: Enable the OS Shell and Console
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/tutorials/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/tutorials/index.html b/latest/os/tutorials/tutorials/index.html
index 6cffce2..83ab7c7 100644
--- a/latest/os/tutorials/tutorials/index.html
+++ b/latest/os/tutorials/tutorials/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,7 +264,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -271,7 +272,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -279,20 +280,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -300,7 +296,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -308,7 +304,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,18 +312,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -561,8 +557,8 @@
</li>
<li class="pull-right">
- <a href=../arduino_zero/>
- Next: Blinky on Arduino Zero
+ <a href=../blinky/>
+ Next: Project Blinky
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/unit_test/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/unit_test/index.html b/latest/os/tutorials/unit_test/index.html
index a4065e0..ba71dfc 100644
--- a/latest/os/tutorials/unit_test/index.html
+++ b/latest/os/tutorials/unit_test/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,15 +264,15 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
- <li class="active">
- <a href="./">Write a Test Suite for a Package</a>
+ <li >
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -279,20 +280,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -300,7 +296,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -308,26 +304,23 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
- <li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <li class="active">
+ <a href="./">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/wi-fi_on_arduino/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/wi-fi_on_arduino/index.html b/latest/os/tutorials/wi-fi_on_arduino/index.html
index 1d327c8..0dba558 100644
--- a/latest/os/tutorials/wi-fi_on_arduino/index.html
+++ b/latest/os/tutorials/wi-fi_on_arduino/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,16 +252,19 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
- <li class="active">
- <a href="./">Enable Wi-Fi on Arduino MKR1000</a>
+ <li >
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -271,7 +272,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -279,20 +280,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -300,15 +296,15 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
- <li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <li class="active">
+ <a href="./">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,18 +312,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/sitemap.xml
----------------------------------------------------------------------
diff --git a/latest/sitemap.xml b/latest/sitemap.xml
index be0fcd9..69ea288 100644
--- a/latest/sitemap.xml
+++ b/latest/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,7 +13,7 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -22,7 +22,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -30,7 +30,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -38,7 +38,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -46,7 +46,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -54,7 +54,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -62,7 +62,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -71,7 +71,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -83,7 +83,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -123,13 +123,13 @@
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/sitemap.xml
----------------------------------------------------------------------
diff --git a/sitemap.xml b/sitemap.xml
index 947ef46..e6b3f19 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,13 +13,13 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/pages/securitybullets/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -28,7 +28,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -36,7 +36,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -44,7 +44,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -52,7 +52,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -60,7 +60,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -68,7 +68,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -77,7 +77,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -89,7 +89,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -129,13 +129,13 @@
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/v0_9_0/sitemap.xml
----------------------------------------------------------------------
diff --git a/v0_9_0/sitemap.xml b/v0_9_0/sitemap.xml
index 947ef46..e6b3f19 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-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,13 +13,13 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/pages/securitybullets/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -28,7 +28,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -36,7 +36,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -44,7 +44,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -52,7 +52,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -60,7 +60,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -68,7 +68,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -77,7 +77,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -89,7 +89,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -129,13 +129,13 @@
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
[06/11] incubator-mynewt-site git commit: Updated Blinky and Slinky
tutorials with intro summaries,
remove legacy feature references in the tutorials
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/rbnano2/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/rbnano2/index.html b/develop/os/tutorials/rbnano2/index.html
index adc7e3a..c511d1f 100644
--- a/develop/os/tutorials/rbnano2/index.html
+++ b/develop/os/tutorials/rbnano2/index.html
@@ -232,14 +232,14 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
<ul>
+
+
<li >
<a href="../arduino_zero/">Blinky on Arduino Zero</a>
@@ -317,8 +317,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -326,7 +329,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -334,7 +337,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -342,20 +345,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -363,7 +361,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -371,7 +369,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -379,18 +377,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -398,15 +393,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -526,7 +524,7 @@
- <li>» <a href="../arduino_zero/">Project Blinky</a></li>
+ <li>» <a href="../blinky/">Project Blinky</a></li>
@@ -539,20 +537,12 @@
</div>
<h2 id="blinky-your-hello-world-on-redbear-nano-2">Blinky, your "Hello World!", on RedBear Nano 2</h2>
-<p><br></p>
-<h3 id="objective">Objective</h3>
-<p>Learn how to use packages from a default application repository of Mynewt to build your first <em>Hello World</em> application (Blinky) on a target board. Once built using the <em>newt</em> tool, this application will blink the LED lights on the target board.</p>
-<p>Create a project with a simple application that blinks an LED on a RedBear Nano 2 board. Download the application to the target and watch it blink!</p>
-<p><br></p>
+<p>This tutorial shows you how to create, build and run the Blinky application on a RedBear Nano 2 board.
+<br></p>
<h3 id="prerequisites">Prerequisites</h3>
-<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
<ul>
+<li>Meet the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
<li>Have a RedBear Nano 2 board. </li>
-<li>Have Internet connectivity to fetch remote Mynewt components.</li>
-<li>Have a computer to build a Mynewt application and connect to the board over USB.</li>
-<li>Install the Newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
-<li>Create a project space (directory structure) and populated it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.</li>
-<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section.</li>
</ul>
<p><strong>Note:</strong> You must install a patched version of OpenOCD .10.0 (See <a href="../../../os/tutorials/blinky_primo">Debugger Option 2 in the Arduino Primo Blinky Tutorial</a>).</p>
<h3 id="create-a-project">Create a Project</h3>
@@ -703,11 +693,6 @@ Loading app image into slot 1
<p>You should see a blue LED on the board blink!</p>
<p>Note: If the LED does not blink, try resetting your board.</p>
-<h3 id="conclusion">Conclusion</h3>
-<p>You have created, setup, compiled, loaded, and ran your first mynewt application for a RedBear Nano 2 board.</p>
-<p>We have more fun tutorials for you to get your hands dirty. Be bold and work on the OS with tutorials on <a href="../unit_test/">writing a test suite</a> or try enabling additional functionality such as <a href="../project-target-slinky/">remote comms</a> or <a href="../bletiny_project/">Bluetooth Low Energy</a> on your current board.</p>
-<p>If you see anything missing or want to send us feedback, please do so by signing up for appropriate mailing lists on our <a href="../../../community/">Community Page</a>.</p>
-<p>Keep on hacking and blinking!</p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/repo/add_repos/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/repo/add_repos/index.html b/develop/os/tutorials/repo/add_repos/index.html
index 9b27494..55ff272 100644
--- a/develop/os/tutorials/repo/add_repos/index.html
+++ b/develop/os/tutorials/repo/add_repos/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../../blinky/">Project Blinky</a>
</li>
@@ -284,8 +282,11 @@
- <li >
- <a href="../../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -293,7 +294,7 @@
<li >
- <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../../ibeacon/">BLE iBeacon</a>
</li>
@@ -301,7 +302,7 @@
<li >
- <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../../eddystone/">BLE Eddystone</a>
</li>
@@ -309,20 +310,15 @@
<li >
- <a href="../../event_queue/">Events and Event Queues</a>
+ <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -330,7 +326,7 @@
<li >
- <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -338,7 +334,7 @@
<li >
- <a href="../../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -346,18 +342,15 @@
<li >
- <a href="../../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../../event_queue/">Events and Event Queues</a>
</li>
@@ -365,15 +358,18 @@
<li >
- <a href="../../ibeacon/">BLE iBeacon</a>
+ <a href="../../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -562,7 +558,7 @@ information on obtaining the repo.</p>
<p>In the same <code>myproj</code> above you will see the following repo descriptor.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">repository.apache-Mynewt-core:
type: github
- vers: 0-latest
+ vers: 1-latest
user: apache
repo: incubator-mynewt-core
</pre></div>
@@ -624,14 +620,14 @@ project.repositories:
#
repository.apache-Mynewt-core:
type: github
- vers: 0-latest
+ vers: 1-latest
user: apache
repo: incubator-mynewt-core
# a special repo to hold hardware specific stuff for arduino zero
repository.Mynewt_arduino_zero:
type: github
- vers: 0-latest
+ vers: 1-latest
user: runtimeinc
repo: Mynewt_arduino_zero
</pre></div>
@@ -643,8 +639,8 @@ repository.Mynewt_arduino_zero:
systems like github. The repo descriptor in your <code>project.yml</code> file must
specify the version of the repo you will accept into your project.</p>
<p>For now, we are at the beginnings of Mynewt. For testing and evaluation
-please use <code>0-latest</code> in the <code>vers</code> field in your repo descriptor.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> vers:0-latest
+please use <code>1-latest</code> in the <code>vers</code> field in your repo descriptor.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> vers:1-latest
</pre></div>
@@ -659,15 +655,22 @@ specified in your <code>project.yml</code> file. Special care should be taken t
<p>Here is the <code>repository.yml</code> file from the apache-Mynewt-core:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">repo.name: apache-mynewt-core
repo.versions:
- "0.0.0": "develop"
+ "0.0.0": "master"
+ "0.0.1": "master"
"0.7.9": "mynewt_0_8_0_b2_tag"
"0.8.0": "mynewt_0_8_0_tag"
"0.9.0": "mynewt_0_9_0_tag"
- "0.9.1": "master"
- "0-latest": "0.9.0"
- "0-dev": "0.9.1"
+ "0.9.9": "mynewt_1_0_0_b1_tag"
+ "0.9.99": "mynewt_1_0_0_b2_tag"
+ "0.9.999": "mynewt_1_0_0_rc1_tag"
+ "1.0.0": "mynewt_1_0_0_tag"
+
+ "0-latest": "1.0.0" # 1.0.0
+ "0-dev": "0.0.0" # master
+
"0.8-latest": "0.8.0"
"0.9-latest": "0.9.0"
+ "1.0-latest": "1.0.0" # 1.0.0
</pre></div>
@@ -706,7 +709,7 @@ on the settings in their <code>project.yml</code> file. </li>
<p>In your <code>project.yml</code> file you can specify different combinations of
the version number and stability value. For example:</p>
<ul>
-<li><code>0-latest</code> -- The latest version with major number 0</li>
+<li><code>1-latest</code> -- The latest version with major number 1</li>
<li><code>1.2-stable</code> -- The latest stable version with major and minor number 1.2</li>
<li><code>1.2-dev</code> -- The development version from 1.2</li>
<li><code>1.1.1</code> -- a specific version 1.1.1</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/repo/create_repo/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/repo/create_repo/index.html b/develop/os/tutorials/repo/create_repo/index.html
index b1100c4..d7b2774 100644
--- a/develop/os/tutorials/repo/create_repo/index.html
+++ b/develop/os/tutorials/repo/create_repo/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../../blinky/">Project Blinky</a>
</li>
@@ -284,8 +282,11 @@
- <li >
- <a href="../../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -293,7 +294,7 @@
<li >
- <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../../ibeacon/">BLE iBeacon</a>
</li>
@@ -301,7 +302,7 @@
<li >
- <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../../eddystone/">BLE Eddystone</a>
</li>
@@ -309,20 +310,15 @@
<li >
- <a href="../../event_queue/">Events and Event Queues</a>
+ <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -330,7 +326,7 @@
<li >
- <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -338,7 +334,7 @@
<li >
- <a href="../../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -346,18 +342,15 @@
<li >
- <a href="../../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../../event_queue/">Events and Event Queues</a>
</li>
@@ -365,15 +358,18 @@
<li >
- <a href="../../ibeacon/">BLE iBeacon</a>
+ <a href="../../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -579,7 +575,7 @@ on versioning. Its a flexible mapping between version numbers and git branches.<
<p>In your <code>project.yml</code> file you can specify different combinations of
the version number and stability value. For example:</p>
<ul>
-<li><code>0-latest</code> -- The latest version with major number 0</li>
+<li><code>1-latest</code> -- The latest version with major number 1</li>
<li><code>1.2-stable</code> -- The latest stable version with major and minor number 1.2</li>
<li><code>1.2-dev</code> -- The development version from 1.2</li>
<li><code>1.1.1</code> -- a specific version 1.1.1</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/repo/private_repo/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/repo/private_repo/index.html b/develop/os/tutorials/repo/private_repo/index.html
index ff319af..dbc726e 100644
--- a/develop/os/tutorials/repo/private_repo/index.html
+++ b/develop/os/tutorials/repo/private_repo/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../../blinky/">Project Blinky</a>
</li>
@@ -284,8 +282,11 @@
- <li >
- <a href="../../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -293,7 +294,7 @@
<li >
- <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../../ibeacon/">BLE iBeacon</a>
</li>
@@ -301,7 +302,7 @@
<li >
- <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../../eddystone/">BLE Eddystone</a>
</li>
@@ -309,20 +310,15 @@
<li >
- <a href="../../event_queue/">Events and Event Queues</a>
+ <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -330,7 +326,7 @@
<li >
- <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -338,7 +334,7 @@
<li >
- <a href="../../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -346,18 +342,15 @@
<li >
- <a href="../../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../../event_queue/">Events and Event Queues</a>
</li>
@@ -365,15 +358,18 @@
<li >
- <a href="../../ibeacon/">BLE iBeacon</a>
+ <a href="../../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -561,8 +557,8 @@ operations. This is something that will be fixed in the future.</p>
</li>
<li class="pull-right">
- <a href=../../tasks_lesson/>
- Next: Tasks and Priority Management
+ <a href=../../project-slinky/>
+ Next: Project Slinky for Remote Comms
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/repo/upgrade_repo/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/repo/upgrade_repo/index.html b/develop/os/tutorials/repo/upgrade_repo/index.html
index 676cdf2..e68578e 100644
--- a/develop/os/tutorials/repo/upgrade_repo/index.html
+++ b/develop/os/tutorials/repo/upgrade_repo/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../../blinky/">Project Blinky</a>
</li>
@@ -284,8 +282,11 @@
- <li >
- <a href="../../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -293,7 +294,7 @@
<li >
- <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../../ibeacon/">BLE iBeacon</a>
</li>
@@ -301,7 +302,7 @@
<li >
- <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../../eddystone/">BLE Eddystone</a>
</li>
@@ -309,20 +310,15 @@
<li >
- <a href="../../event_queue/">Events and Event Queues</a>
+ <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -330,7 +326,7 @@
<li >
- <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -338,7 +334,7 @@
<li >
- <a href="../../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -346,18 +342,15 @@
<li >
- <a href="../../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../../event_queue/">Events and Event Queues</a>
</li>
@@ -365,15 +358,18 @@
<li >
- <a href="../../ibeacon/">BLE iBeacon</a>
+ <a href="../../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/tasks_lesson/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/tasks_lesson/index.html b/develop/os/tutorials/tasks_lesson/index.html
index ed23597..2b0dd0c 100644
--- a/develop/os/tutorials/tasks_lesson/index.html
+++ b/develop/os/tutorials/tasks_lesson/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li class="active">
- <a href="./">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,7 +264,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -271,7 +272,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -279,28 +280,23 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
- <li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <li class="active">
+ <a href="./">Tasks and Priority Management</a>
</li>
@@ -308,7 +304,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,18 +312,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -699,9 +695,9 @@ the <code>main</code> task sleeps, saving us idle time compared to the first cas
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../repo/private_repo/>
+ <a href=../add_shell/>
<span class="fa fa-arrow-left"></span>
- Previous: Access a private Repo
+ Previous: Enable the OS Shell and Console
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/tutorials/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/tutorials/index.html b/develop/os/tutorials/tutorials/index.html
index cbe8ee2..ef056df 100644
--- a/develop/os/tutorials/tutorials/index.html
+++ b/develop/os/tutorials/tutorials/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,7 +264,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -271,7 +272,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -279,20 +280,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -300,7 +296,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -308,7 +304,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,18 +312,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -561,8 +557,8 @@
</li>
<li class="pull-right">
- <a href=../arduino_zero/>
- Next: Blinky on Arduino Zero
+ <a href=../blinky/>
+ Next: Project Blinky
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/unit_test/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/unit_test/index.html b/develop/os/tutorials/unit_test/index.html
index a99af80..691e4a4 100644
--- a/develop/os/tutorials/unit_test/index.html
+++ b/develop/os/tutorials/unit_test/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,15 +264,15 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
- <li class="active">
- <a href="./">Write a Test Suite for a Package</a>
+ <li >
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -279,20 +280,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -300,7 +296,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -308,26 +304,23 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
- <li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <li class="active">
+ <a href="./">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/wi-fi_on_arduino/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/wi-fi_on_arduino/index.html b/develop/os/tutorials/wi-fi_on_arduino/index.html
index 3752121..c4bfb3e 100644
--- a/develop/os/tutorials/wi-fi_on_arduino/index.html
+++ b/develop/os/tutorials/wi-fi_on_arduino/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,16 +252,19 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
- <li class="active">
- <a href="./">Enable Wi-Fi on Arduino MKR1000</a>
+ <li >
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -271,7 +272,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -279,20 +280,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -300,15 +296,15 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
- <li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <li class="active">
+ <a href="./">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,18 +312,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/sitemap.xml
----------------------------------------------------------------------
diff --git a/develop/sitemap.xml b/develop/sitemap.xml
index be0fcd9..69ea288 100644
--- a/develop/sitemap.xml
+++ b/develop/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,7 +13,7 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -22,7 +22,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -30,7 +30,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -38,7 +38,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -46,7 +46,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -54,7 +54,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -62,7 +62,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -71,7 +71,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -83,7 +83,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -123,13 +123,13 @@
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-03-31</lastmod>
+ <lastmod>2017-04-07</lastmod>
<changefreq>daily</changefreq>
</url>
[07/11] incubator-mynewt-site git commit: Updated Blinky and Slinky
tutorials with intro summaries,
remove legacy feature references in the tutorials
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/project-nrf52-slinky/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/project-nrf52-slinky/index.html b/develop/os/tutorials/project-nrf52-slinky/index.html
new file mode 100644
index 0000000..70442cc
--- /dev/null
+++ b/develop/os/tutorials/project-nrf52-slinky/index.html
@@ -0,0 +1,742 @@
+<!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/os/tutorials/project-nrf52-slinky/"> -->
+ <link rel="shortcut icon" href="../../../img/favicon.ico">
+
+ <title>Slinky on Nordic nRF52 - 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="Slinky on Nordic nRF52">
+
+
+ <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</a> released (March 22, 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="../../introduction/">Mynewt Documentation</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../../get_started/get_started/">Basic Setup</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../get_started/vocabulary/">Concepts</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../tutorials/">Tutorials</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../blinky/">Project Blinky</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../repo/add_repos/">Work with repositories</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
+ <ul>
+
+
+
+
+
+ <li >
+ <a href="../project-sim-slinky/">Slinky on sim device</a>
+ </li>
+
+
+
+
+
+ <li class="active">
+ <a href="./">Slinky on Nordic nRF52</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../project-stm32-slinky/">Slinky on Olimex</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../ibeacon/">BLE iBeacon</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../eddystone/">BLE Eddystone</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../blehci_project/">BLE HCI interface</a>
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../air_quality_sensor/
+">Air-quality Sensor project</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../nrf52_adc/">Add an Analog Sensor</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../os_user_guide/">OS User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../../network/ble/ble_intro/
+">BLE User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../newt/newt_intro/">Newt Tool Guide</a>
+
+
+ </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="../tutorials/">Tutorials</a></li>
+
+
+
+ <li>» <a href="../project-slinky/">Project Slinky for Remote Comms</a></li>
+
+
+
+ <li>» Slinky on Nordic nRF52</li>
+
+
+
+ </ul>
+</div>
+ </div>
+
+ <h2 id="project-slinky-using-the-nordic-nrf52-board">Project Slinky using the Nordic nRF52 Board</h2>
+<p>This tutorial shows you how to create, build and run the Slinky application and communicate with newtmgr for a Nordic nRF52 board.</p>
+<h3 id="prerequisites">Prerequisites</h3>
+<ul>
+<li>Meet the prerequisites listed in <a href="../project-slinky/">Project Slinky</a>. </li>
+<li>Have a Nordic nRF52-DK board. </li>
+</ul>
+<h3 id="create-a-new-project">Create a New Project</h3>
+<p>Create a new project if you do not have an existing one. You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already have a project created or completed the <a href="../project-slinky/">Sim Slinky</a> tutorial. </p>
+<p>Run the following commands to create a new project. We name the project <code>slinky</code>. </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt new slinky
+Downloading project skeleton from apache/incubator-mynewt-blinky...
+...
+Installing skeleton in slink...
+Project slinky successfully created
+$ cd slinky
+$newt install
+apache-mynewt-core
+</pre></div>
+
+
+<p><br></p>
+<h3 id="create-the-targets"><a name="create_targets"></a> Create the Targets</h3>
+<p>Create two targets for the nRF52-DK board - one for the bootloader and one for the Slinky application.</p>
+<p>Run the following <code>newt target</code> commands, from your project directory, to create a bootloader target. We name the target <code>nrf52_boot</code>.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create nrf52_boot
+$ newt target set nrf52_boot bsp=@apache-mynewt-core/hw/bsp/nrf52dk
+$ newt target set nrf52_boot build_profile=optimized
+$ newt target set nrf52_boot app=@apache-mynewt-core/apps/boot
+</pre></div>
+
+
+<p><br>
+Run the following <code>newt target</code> commands to create a target for the Slinky application. We name the target <code>nrf52_slinky</code>.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create nrf52_slinky
+$ newt target set nrf52_slinky bsp=@apache-mynewt-core/hw/bsp/nrf52dk
+$ newt target set nrf52_slinky build_profile=debug
+$ newt target set nrf52_slinky app=@apache-mynewt-core/apps/slinky
+</pre></div>
+
+
+<p><br></p>
+<h3 id="build-the-targets">Build the Targets</h3>
+<p>Run the <code>newt build nrf52_boot</code> command to build the bootloader:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt build nrf52-boot
+Building target targets/nrf52_boot
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c
+Compiling repos/apache-mynewt-core/crypto/mbedtls/src/aes.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/loader.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c
+Compiling repos/apache-mynewt-core/apps/boot/src/boot.c
+ ...
+
+Archiving sys_mfg.a
+Archiving sys_sysinit.a
+Archiving util_mem.a
+Linking ~/dev/slinky/bin/targets/nrf52_boot/app/apps/boot/boot.elf
+Target successfully built: targets/nrf52_boot
+</pre></div>
+
+
+<p><br></p>
+<p>Run the <code>newt build nrf52_slinky</code> command to build the Slinky application:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt build nrf52_slinky
+Building target targets/nrf52_slinky
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c
+Compiling repos/apache-mynewt-core/boot/split/src/split.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/loader.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c
+Compiling repos/apache-mynewt-core/boot/split/src/split_config.c
+Compiling repos/apache-mynewt-core/crypto/mbedtls/src/aesni.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c
+Compiling repos/apache-mynewt-core/crypto/mbedtls/src/aes.c
+Compiling repos/apache-mynewt-core/apps/slinky/src/main.c
+
+ ...
+
+Archiving util_mem.a
+Linking ~/dev/slinky/bin/targets/nrf52_slinky/app/apps/slinky/slinky.elf
+Target successfully built: targets/nrf52_slinky
+</pre></div>
+
+
+<p><br></p>
+<h3 id="sign-and-create-the-slinky-application-image">Sign and Create the Slinky Application Image</h3>
+<p>Run the <code>newt create-image nrf52_slinky 1.0.0</code> command to create and sign the application image. You may assign an arbitrary version (e.g. 1.0.0) to the image.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt create-image nrf52_slinky 1.0.0
+App image succesfully generated: ~/dev/slinky/bin/targets/nrf52_slinky/app/apps/slinky/slinky.img
+$
+</pre></div>
+
+
+<p><br></p>
+<h3 id="connect-to-the-board">Connect to the Board</h3>
+<ul>
+<li>Connect a micro-USB cable from your computer to the micro-USB port on the nRF52-DK board.</li>
+<li>Turn the power on the board to ON. You should see the green LED light up on the board.</li>
+</ul>
+<p><br></p>
+<h3 id="load-the-bootloader-and-the-slinky-application-image">Load the Bootloader and the Slinky Application Image</h3>
+<p>Run the <code>newt load nrf52_boot</code> command to load the bootloader onto the board:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load nrf52_boot
+Loading bootloader
+$
+</pre></div>
+
+
+<p><br>
+Run the <code>newt load nrf52_slinky</code> command to load the Slinky application image onto the board:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load nrf52_slinky
+Loading app image into slot 1
+$
+</pre></div>
+
+
+<p><br></p>
+<h3 id="connect-newtmgr-with-the-board-using-a-serial-connection">Connect Newtmgr with the Board using a Serial Connection</h3>
+<p>Set up a serial connection from your computer to the nRF52-DK board (See <a href="../../get_started/serial_access/">Serial Port Setup</a>). </p>
+<p>Locate the port, in the /dev directory on your computer, that the serial connection uses. It should be of the type <code>tty.usbserial-<some identifier></code>.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ ls /dev/tty*usbserial*
+/dev/tty.usbserial-1d11
+$
+</pre></div>
+
+
+<p><br>
+Setup a newtmgr connection profile for the serial port. For our example, the port is <code>/dev/tty.usbserial-1d11</code>. </p>
+<p>Run the <code>newtmgr conn add</code> command to define a newtmgr connection profile for the serial port. We name the connection profile <code>nrf52serial</code>. You will need to replace the <code>connstring</code> with the specific port for your serial connection. </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr conn add nrf52serial type=serial connstring=/dev/tty.usbserial-1d11
+Connection profile nrf52serial successfully added
+$
+</pre></div>
+
+
+<p><br>
+You can run the <code>newt conn show</code> command to see all the newtmgr connection profiles:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr conn show
+Connection profiles:
+ nrf52serial: type=serial, connstring='/dev/tty.usbserial-1d11'
+ sim1: type=serial, connstring='/dev/ttys012'
+$
+</pre></div>
+
+
+<p><br></p>
+<h3 id="use-newtmgr-to-query-the-board">Use Newtmgr to Query the Board</h3>
+<p>Run some newtmgr commands to query and receive responses back from the board (See the <a href="../newtmgr/overview">Newt Manager Guide</a> for more information on the newtmgr commands). </p>
+<p>Run the <code>newtmgr echo hello -c nrf52serial</code> command. This is the simplest command that requests the board to echo back the text. </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr echo hello -c nrf52serial
+hello
+$
+</pre></div>
+
+
+<p><br>
+Run the <code>newtmgr image list -c nrf52serial</code> command to list the images on the board:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr image list -c nrf52serial
+Images:
+ slot=0
+ version: 1.0.0
+ bootable: true
+ flags: active confirmed
+ hash: f411a55d7a5f54eb8880d380bf47521d8c41ed77fd0a7bd5373b0ae87ddabd42
+Split status: N/A
+$
+</pre></div>
+
+
+<p><br>
+Run the <code>newtmgr taskstats -c nrf52serial</code> command to display the task statistics on the board:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr taskstats -c nrf52serial
+Return Code = 0
+ task pri tid runtime csw stksz stkuse last_checkin next_checkin
+ task1 8 2 0 1751 192 110 0 0
+ task2 9 3 0 1751 64 31 0 0
+ idle 255 0 224081 2068 64 32 0 0
+ main 127 1 3 29 1024 365 0 0
+$
+</pre></div>
+
+ <div class="row">
+
+
+
+
+<ul class="nav nav-pills" style="margin-bottom: 10px">
+ <li>
+
+ <a href=../project-sim-slinky/>
+ <span class="fa fa-arrow-left"></span>
+ Previous: Slinky on sim device
+ </a>
+
+ </li>
+ <li class="pull-right">
+
+ <a href=../project-stm32-slinky/>
+ Next: Slinky on Olimex
+ <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/40899401/develop/os/tutorials/project-sim-slinky/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/project-sim-slinky/index.html b/develop/os/tutorials/project-sim-slinky/index.html
new file mode 100644
index 0000000..fa08269
--- /dev/null
+++ b/develop/os/tutorials/project-sim-slinky/index.html
@@ -0,0 +1,653 @@
+<!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/os/tutorials/project-sim-slinky/"> -->
+ <link rel="shortcut icon" href="../../../img/favicon.ico">
+
+ <title>Slinky on sim device - 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="Slinky on sim device">
+
+
+ <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</a> released (March 22, 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="../../introduction/">Mynewt Documentation</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../../get_started/get_started/">Basic Setup</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../get_started/vocabulary/">Concepts</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../tutorials/">Tutorials</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../blinky/">Project Blinky</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../repo/add_repos/">Work with repositories</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
+ <ul>
+
+
+
+
+
+ <li class="active">
+ <a href="./">Slinky on sim device</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../project-nrf52-slinky/">Slinky on Nordic nRF52</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../project-stm32-slinky/">Slinky on Olimex</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../ibeacon/">BLE iBeacon</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../eddystone/">BLE Eddystone</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../blehci_project/">BLE HCI interface</a>
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../air_quality_sensor/
+">Air-quality Sensor project</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../nrf52_adc/">Add an Analog Sensor</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../os_user_guide/">OS User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../../network/ble/ble_intro/
+">BLE User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../newt/newt_intro/">Newt Tool Guide</a>
+
+
+ </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="../tutorials/">Tutorials</a></li>
+
+
+
+ <li>» <a href="../project-slinky/">Project Slinky for Remote Comms</a></li>
+
+
+
+ <li>» Slinky on sim device</li>
+
+
+
+ </ul>
+</div>
+ </div>
+
+ <h2 id="project-sim-slinky">Project Sim Slinky</h2>
+<p>This tutorial shows you how to create, build and run the Slinky application and communicate with newtmgr for a simulated device.</p>
+<p><br></p>
+<h3 id="prerequisites">Prerequisites</h3>
+<p>Meet the prerequisites listed in <a href="../project-slinky/">Project Slinky</a>.</p>
+<h3 id="creating-a-new-project">Creating a new project</h3>
+<p>Instructions for creating a project are located in the <a href="../../get_started/project_create/">Basic Setup</a> section of the <a href="../../introduction/">Mynewt Documentation</a></p>
+<p>We will list only the steps here for brevity. We will name the project <code>slinky</code>.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt new slinky
+Downloading project skeleton from apache/incubator-mynewt-blinky...
+...
+Installing skeleton in slink...
+Project slinky successfully created
+$ cd slinky
+$newt install
+apache-mynewt-core
+</pre></div>
+
+
+<h3 id="setting-up-your-target-build">Setting up your target build</h3>
+<p>Create a target for <code>slinky</code> using the native bsp. We will list only the steps and suppress the tool output here for brevity.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newt target create sim_slinky
+ $ newt target set sim_slinky bsp=@apache-mynewt-core/hw/bsp/native
+ $ newt target set sim_slinky build_profile=debug
+ $ newt target set sim_slinky app=@apache-mynewt-core/apps/slinky
+</pre></div>
+
+
+<h3 id="building-your-target">Building Your target</h3>
+<p>To build your target, use <code>newt build</code>. When complete, an executable file
+is created.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newt build sim_slinky
+ Building target targets/sim_slinky
+ Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c
+ Compiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c
+ Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c
+ Compiling repos/apache-mynewt-core/boot/split/src/split.c
+ Compiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c
+ Compiling repos/apache-mynewt-core/boot/bootutil/src/loader.c
+ Compiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c
+ Compiling repos/apache-mynewt-core/crypto/mbedtls/src/aesni.c
+ Compiling repos/apache-mynewt-core/crypto/mbedtls/src/aes.c
+ Compiling repos/apache-mynewt-core/boot/split/src/split_config.c
+ Compiling repos/apache-mynewt-core/apps/slinky/src/main.c
+
+ ...
+
+ Archiving util_crc.a
+ Archiving util_mem.a
+ Linking ~/dev/slinky/bin/targets/sim_slinky/app/apps/slinky/slinky.elf
+ Target successfully built: targets/sim_slinky
+</pre></div>
+
+
+<h3 id="run-the-target">Run the target</h3>
+<p>Run the executable you have build for the simulated environment. The serial port name on which the simulated target is connected is shown in the output when mynewt slinky starts.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ ~/dev/slinky/bin/targets/sim_slinky/app/apps/slinky/slinky.elf
+ uart0 at /dev/ttys005
+</pre></div>
+
+
+<p><br></p>
+<p>In this example, the slinky app opened up a com port <code>/dev/ttys005</code> for communications with newtmgr. </p>
+<p><strong>NOTE:</strong> This application will block. You will need to open a new console (or execute this in another console) to continue the tutorial.*</p>
+<p><br></p>
+<h3 id="setting-up-a-connection-profile">Setting up a connection profile</h3>
+<p>You will now set up a connection profile using <code>newtmgr</code> for the serial port connection and start communicating with the simulated remote device.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newtmgr conn add sim1 type=serial connstring=/dev/ttys005
+ Connection profile sim1 successfully added
+ $ newtmgr conn show
+ Connection profiles:
+ sim1: type=serial, connstring='/dev/ttys005'
+</pre></div>
+
+
+<h3 id="executing-newtmgr-commands-with-the-target">Executing newtmgr commands with the target</h3>
+<p>You can now use connection profile <code>sim1</code> to talk to the running sim_slinky.
+As an example, we will query the running mynewt OS for the usage of its
+memory pools. </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newtmgr -c sim1 mpstats
+ Return Code = 0
+ name blksz cnt free min
+ msys_1 292 12 10 10
+</pre></div>
+
+
+<p>As a test command, you can send an arbitrary string to the target and it
+will echo that string back in a response to newtmgr.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newtmgr -c sim1 echo "Hello Mynewt"
+ Hello Mynewt
+</pre></div>
+
+
+<p>In addition to these, you can also examine running tasks, statistics,
+logs, image status (not on sim), and configuration.</p>
+
+ <div class="row">
+
+
+
+
+<ul class="nav nav-pills" style="margin-bottom: 10px">
+ <li>
+
+ <a href=../project-slinky/>
+ <span class="fa fa-arrow-left"></span>
+ Previous: Project Slinky for Remote Comms
+ </a>
+
+ </li>
+ <li class="pull-right">
+
+ <a href=../project-nrf52-slinky/>
+ Next: Slinky on Nordic nRF52
+ <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/40899401/develop/os/tutorials/project-slinky/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/project-slinky/index.html b/develop/os/tutorials/project-slinky/index.html
index 30c42f6..cdb2167 100644
--- a/develop/os/tutorials/project-slinky/index.html
+++ b/develop/os/tutorials/project-slinky/index.html
@@ -10,7 +10,7 @@
<link rel="canonical" href="http://mynewt.apache.org/os/tutorials/project-slinky/"> -->
<link rel="shortcut icon" href="../../../img/favicon.ico">
- <title>Slinky on sim device - Apache Mynewt</title>
+ <title>toc - Apache Mynewt</title>
<link href="../../../css/bootstrap-3.0.3.min.css" rel="stylesheet">
<link rel="stylesheet" href="../../../css/highlight.css">
@@ -41,7 +41,7 @@
</head>
- <body class="Slinky on sim device">
+ <body class="toc">
<div class="container">
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,16 +252,19 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
- </li>
-
+
+
+ <li class="active"><a href="./">Project Slinky for Remote Comms</a>
+
+
+ <ul>
+
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../project-sim-slinky/">Slinky on sim device</a>
</li>
@@ -271,7 +272,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../project-nrf52-slinky/">Slinky on Nordic nRF52</a>
</li>
@@ -279,26 +280,21 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../project-stm32-slinky/">Slinky on Olimex</a>
</li>
-
-
-
-
- <li><a href="
- ./
-">Project Slinky for remote comms</a>
-
+ </ul>
- <ul>
+ </li>
+
+
- <li class="active">
- <a href="./">Slinky on sim device</a>
+ <li >
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -306,7 +302,7 @@
<li >
- <a href="../project-target-slinky/">Slinky on Nordic nRF52 board</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -314,13 +310,15 @@
<li >
- <a href="../project-stm32-slinky/">Slinky on STM32 board</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
- </ul>
-
+
+
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -328,7 +326,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -336,7 +334,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -344,18 +342,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -363,15 +358,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -491,134 +489,50 @@
- <li>» Project Slinky for remote comms</li>
+ <li>» Project Slinky for Remote Comms</li>
- <li>» Slinky on sim device</li>
-
</ul>
</div>
</div>
- <h2 id="project-sim-slinky">Project Sim Slinky</h2>
-<p><br></p>
-<p>The goal of the project is to use a sample app called "Slinky" included in the Mynewt repository to enable remote communications with a device running the Mynewt OS. The protocol for remote communications is called newt manager (newtmgr). In this tutorial we will create a target for a simulated device and define it with the sample app "Slinky". </p>
-<p>If you have an existing project using a target that does not use the Slinky app and you wish to add newtmgt functonality to it, check out the tutorial titled <a href="../add_newtmgr/">Enable newtmgr in any app</a>. </p>
-<p><br></p>
+ <h2 id="project-slinky">Project Slinky</h2>
+<p>The goal of the project is to use a sample application called "Slinky" included in the Mynewt repository to enable remote communications with a device running the Mynewt OS. The protocol for remote communications is called newt manager (newtmgr). </p>
+<p>If you have an existing project using a target that does not use the Slinky application and you wish to add newtmgr functionality to it, check out the tutorial titled <a href="../add_newtmgr/">Enable newtmgr in any app</a>. </p>
+<h3 id="available-tutorials">Available Tutorials</h3>
+<p>Tutorials are available for the following boards:</p>
+<ul>
+<li><a href="../../../os/tutorials/project-sim-slinky">Slinky on a simulated device</a>.</li>
+<li><a href="../../../os/tutorials/project-nrf52-slinky">Slinky on a nRF52</a>.</li>
+<li><a href="../../../os/tutorials/project-stm32-slinky">Slinky on an Olimex</a>.
+<br></li>
+</ul>
<h3 id="prerequisites">Prerequisites</h3>
-<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
+<p>Ensure that you meet the following prerequisites before continuing with this tutorial:</p>
<ul>
<li>Have Internet connectivity to fetch remote Mynewt components.</li>
-<li>Have a computer to build a Mynewt application.</li>
+<li>Have a computer to build a Mynewt application and connect to the board over USB.</li>
+<li>Have a Micro-USB cable to connect the board and the computer.</li>
+<li>Have a <a href="../../get_started/serial_access/">serial port setup</a>.</li>
<li>Install the newt tool and the toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
<li>Install the <a href="../../../newtmgr/installing/">newtmgr tool</a>.</li>
<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section.</li>
+<li>Create a project space (directory structure) and populated it with the core code repository (apache-mynewt-core) or kn
+ow how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.</li>
</ul>
-<h3 id="overview-of-steps">Overview of steps</h3>
+<h3 id="overview-of-steps">Overview of Steps</h3>
<ul>
-<li>Install dependencies</li>
-<li>Define a target using the newt tool</li>
-<li>Build executables for the targets using the newt tool</li>
-<li>Set up serial connection with the targets </li>
-<li>Create a connection profile using the newtmgr tool</li>
-<li>Use the newtmgr tool to communicate with the targets</li>
+<li>Install dependencies.</li>
+<li>Define the bootloader and Slinky application target for the target board.</li>
+<li>Build the bootloader target.</li>
+<li>Build the Slinky application target and create an application image.</li>
+<li>Set a up serial connection with the targets.</li>
+<li>Create a connection profile using the newtmgr tool.</li>
+<li>Use the newtmgr tool to communicate with the targets.</li>
</ul>
-<h3 id="creating-a-new-project">Creating a new project</h3>
-<p>Instructions for creating a project are located in the <a href="../../get_started/project_create/">Basic Setup</a> section of the <a href="../../introduction/">Mynewt Documentation</a></p>
-<p>We will list only the steps here for brevity. We will name the project
-<code>slinky</code>.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newt new slinky
- Downloading project skeleton from apache/incubator-mynewt-blinky...
- ...
- Installing skeleton in slink...
- Project slink successfully created
- $ cd slinky
- $ newt install -v
- Downloading repository description for apache-mynewt-core... success!
- ...
- Repos successfully installed
-</pre></div>
-
-
-<h3 id="setting-up-your-target-build">Setting up your target build</h3>
-<p>Create a target for <code>slinky</code> using the native bsp. We will list only the steps and suppress the tool output here for brevity.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newt target create sim_slinky
- $ newt target set sim_slinky bsp=@apache-mynewt-core/hw/bsp/native
- $ newt target set sim_slinky build_profile=debug
- $ newt target set sim_slinky app=@apache-mynewt-core/apps/slinky
-</pre></div>
-
-
-<h3 id="building-your-target">Building Your target</h3>
-<p>To build your target, use <code>newt build</code>. When complete, an executable file
-is created.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newt build sim_slinky
- Building target targets/sim_slinky
- Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c
- Compiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c
- Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c
- Compiling repos/apache-mynewt-core/boot/split/src/split.c
- Compiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c
- Compiling repos/apache-mynewt-core/boot/bootutil/src/loader.c
- Compiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c
- Compiling repos/apache-mynewt-core/crypto/mbedtls/src/aesni.c
- Compiling repos/apache-mynewt-core/crypto/mbedtls/src/aes.c
- Compiling repos/apache-mynewt-core/boot/split/src/split_config.c
- Compiling repos/apache-mynewt-core/apps/slinky/src/main.c
-
- ...
-
- Archiving util_crc.a
- Archiving util_mem.a
- Linking ~/dev/slinky/bin/targets/sim_slinky/app/apps/slinky/slinky.elf
- Target successfully built: targets/sim_slinky
-</pre></div>
-
-
-<h3 id="run-the-target">Run the target</h3>
-<p>Run the executable you have build for the simulated environment. The serial port name on which the simulated target is connected is shown in the output when mynewt slinky starts.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ ~/dev/slinky/bin/targets/sim_slinky/app/apps/slinky/slinky.elf
- uart0 at /dev/ttys005
-</pre></div>
-
-
-<p><br></p>
-<p>In this example, the slinky app opened up a com port <code>/dev/ttys005</code> for communications with newtmgr. </p>
-<p><strong>NOTE:</strong> This application will block. You will need to open a new console (or execute this in another console) to continue the tutorial.*</p>
-<p><br></p>
-<h3 id="setting-up-a-connection-profile">Setting up a connection profile</h3>
-<p>You will now set up a connection profile using <code>newtmgr</code> for the serial port connection and start communicating with the simulated remote device.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newtmgr conn add sim1 type=serial connstring=/dev/ttys005
- Connection profile sim1 successfully added
- $ newtmgr conn show
- Connection profiles:
- sim1: type=serial, connstring='/dev/ttys005'
-</pre></div>
-
-
-<h3 id="executing-newtmgr-commands-with-the-target">Executing newtmgr commands with the target</h3>
-<p>You can now use connection profile <code>sim1</code> to talk to the running sim_slinky.
-As an example, we will query the running mynewt OS for the usage of its
-memory pools. </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newtmgr -c sim1 mpstats
- Return Code = 0
- name blksz cnt free min
- msys_1 292 12 10 10
-</pre></div>
-
-
-<p>As a test command, you can send an arbitrary string to the target and it
-will echo that string back in a response to newtmgr.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newtmgr -c sim1 echo "Hello Mynewt"
- Hello Mynewt
-</pre></div>
-
-
-<p>In addition to these, you can also examine running tasks, statistics,
-logs, image status (not on sim), and configuration.</p>
<div class="row">
@@ -628,16 +542,16 @@ logs, image status (not on sim), and configuration.</p>
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../event_queue/>
+ <a href=../repo/private_repo/>
<span class="fa fa-arrow-left"></span>
- Previous: Events and Event Queues
+ Previous: Access a private Repo
</a>
</li>
<li class="pull-right">
- <a href=../project-target-slinky/>
- Next: Slinky on Nordic nRF52 board
+ <a href=../project-sim-slinky/>
+ Next: Slinky on sim device
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/project-stm32-slinky/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/project-stm32-slinky/index.html b/develop/os/tutorials/project-stm32-slinky/index.html
index 1a0da70..707b21c 100644
--- a/develop/os/tutorials/project-stm32-slinky/index.html
+++ b/develop/os/tutorials/project-stm32-slinky/index.html
@@ -10,7 +10,7 @@
<link rel="canonical" href="http://mynewt.apache.org/os/tutorials/project-stm32-slinky/"> -->
<link rel="shortcut icon" href="../../../img/favicon.ico">
- <title>Slinky on STM32 board - Apache Mynewt</title>
+ <title>Slinky on Olimex - Apache Mynewt</title>
<link href="../../../css/bootstrap-3.0.3.min.css" rel="stylesheet">
<link rel="stylesheet" href="../../../css/highlight.css">
@@ -41,7 +41,7 @@
</head>
- <body class="Slinky on STM32 board">
+ <body class="Slinky on Olimex">
<div class="container">
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,16 +252,19 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
- </li>
-
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
+ <ul>
+
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../project-sim-slinky/">Slinky on sim device</a>
</li>
@@ -271,34 +272,29 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../project-nrf52-slinky/">Slinky on Nordic nRF52</a>
</li>
- <li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <li class="active">
+ <a href="./">Slinky on Olimex</a>
</li>
-
-
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
+ </ul>
- <ul>
+ </li>
+
+
<li >
- <a href="../project-slinky/">Slinky on sim device</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -306,21 +302,23 @@
<li >
- <a href="../project-target-slinky/">Slinky on Nordic nRF52 board</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
- <li class="active">
- <a href="./">Slinky on STM32 board</a>
+ <li >
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
- </ul>
-
+
+
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -328,7 +326,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -336,7 +334,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -344,18 +342,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -363,15 +358,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -491,11 +489,11 @@
- <li>» <a href="../project-slinky/">Project Slinky for remote comms</a></li>
+ <li>» <a href="../project-slinky/">Project Slinky for Remote Comms</a></li>
- <li>» Slinky on STM32 board</li>
+ <li>» Slinky on Olimex</li>
@@ -503,32 +501,16 @@
</div>
</div>
- <h2 id="project-slinky-using-stm32-board">Project Slinky Using STM32 Board</h2>
-<p>The goal of the project is to enable and demonstrate remote communications with the Mynewt OS via newt manager (newtmgr) by leveraging a sample app "Slinky" included under the /apps directory in the repository. In this project we will define a target for the STM32-E407 board and assign the app "Slinky" to it.</p>
-<p>If you have an existing project that has a different application and you wish to add newtmgr functionality to it, check out the <a href="../add_newtmgr/">Enable newtmgr in any app</a> tutorial.</p>
-<p><br></p>
+ <h2 id="project-slinky-using-olimex-board">Project Slinky Using Olimex Board</h2>
+<p>This tutorial shows you how to create, build and run the Slinky application and communicate with newtmgr for an Olimex STM-E407 board.
+<br></p>
<h3 id="prerequisites">Prerequisites</h3>
-<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
<ul>
+<li>Meet the prerequisites listed in <a href="../project-slinky/">Project Slinky</a>.</li>
<li>Have a STM32-E407 development board from Olimex. </li>
<li>Have a ARM-USB-TINY-H connector with JTAG interface for debugging ARM microcontrollers (comes with the ribbon cable to hook up to the board)</li>
+<li>Have a USB A-B type cable to connect the debugger to your computer. </li>
<li>Have a USB to TTL Serial Cable with female wiring harness.</li>
-<li>Have a USB Micro-A cable to connect your computer to the board.</li>
-<li>Have Internet connectivity to fetch remote Mynewt components.</li>
-<li>Have a computer to build a Mynewt application and connect to the board over USB.</li>
-<li>Install the newt tool and the toolchains (See Basic Setup).</li>
-<li>Install the newtmgr tool.</li>
-<li>Create a project space (directory structure) and populated it with the core code repository (apache-mynewt-core) or know how to as explained in Creating Your First Project.</li>
-<li>Read the Mynewt OS Concepts section.</li>
-</ul>
-<h3 id="overview-of-steps">Overview of Steps</h3>
-<ul>
-<li>Install dependencies</li>
-<li>Define a target using the newt tool</li>
-<li>Build executables for the targets using the newt tool</li>
-<li>Set up serial connection with the targets</li>
-<li>Create a connection profile using the newtmgr tool</li>
-<li>Use the newtmgr tool to communicate with the targets</li>
</ul>
<h3 id="create-a-new-project">Create a New Project</h3>
<p>Create a new project if you do not have an existing one. You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already have a project created or completed the <a href="../project-slinky/">Sim Slinky</a> tutorial.</p>
@@ -727,16 +709,16 @@ $
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../project-target-slinky/>
+ <a href=../project-nrf52-slinky/>
<span class="fa fa-arrow-left"></span>
- Previous: Slinky on Nordic nRF52 board
+ Previous: Slinky on Nordic nRF52
</a>
</li>
<li class="pull-right">
- <a href=../add_newtmgr/>
- Next: Enable Newt Manager in any app
+ <a href=../ibeacon/>
+ Next: BLE iBeacon
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/project-target-slinky/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/project-target-slinky/index.html b/develop/os/tutorials/project-target-slinky/index.html
deleted file mode 100644
index d618092..0000000
--- a/develop/os/tutorials/project-target-slinky/index.html
+++ /dev/null
@@ -1,763 +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/os/tutorials/project-target-slinky/"> -->
- <link rel="shortcut icon" href="../../../img/favicon.ico">
-
- <title>Slinky on Nordic nRF52 board - 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="Slinky on Nordic nRF52 board">
-
-
- <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</a> released (March 22, 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="../../introduction/">Mynewt Documentation</a>
-
-
- <ul>
-
-
-
-
-
-
-
- <li ><a href="../../get_started/get_started/">Basic Setup</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../../get_started/vocabulary/">Concepts</a>
- </li>
-
-
-
-
-
-
-
- <li ><a href="../tutorials/">Tutorials</a>
-
-
- <ul>
-
-
-
-
-
-
-
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../repo/add_repos/">Work with repositories</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../event_queue/">Events and Event Queues</a>
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
- <ul>
-
-
-
- <li >
- <a href="../project-slinky/">Slinky on sim device</a>
- </li>
-
-
-
-
-
- <li class="active">
- <a href="./">Slinky on Nordic nRF52 board</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../project-stm32-slinky/">Slinky on STM32 board</a>
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
- <li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
- </li>
-
-
-
-
-
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../ibeacon/">BLE iBeacon</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../blehci_project/">BLE HCI interface</a>
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../air_quality_sensor/
-">Air-quality Sensor project</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../nrf52_adc/">Add an Analog Sensor</a>
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../os_user_guide/">OS User Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../../../network/ble/ble_intro/
-">BLE User Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../../newt/newt_intro/">Newt Tool Guide</a>
-
-
- </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="../tutorials/">Tutorials</a></li>
-
-
-
- <li>» <a href="../project-slinky/">Project Slinky for remote comms</a></li>
-
-
-
- <li>» Slinky on Nordic nRF52 board</li>
-
-
-
- </ul>
-</div>
- </div>
-
- <h2 id="project-slinky-using-the-nordic-nrf52-board">Project Slinky using the Nordic nRF52 Board</h2>
-<p><br></p>
-<p>The goal of this tutorial is to enable and demonstrate remote communications with a Mynewt application running on a device via newt manager (newtmgr). It uses the "Slinky" sample application that is included in the apache-mynewt-core/apps directory and the Nordic nRF52-DK board.</p>
-<p>If you have an existing project that has a different application and you wish to add newtmgr functionality to it, check out the <a href="../add_newtmgr/">Enable newtmgr in any app</a> tutorial.</p>
-<h3 id="prerequisites">Prerequisites</h3>
-<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
-<ul>
-<li>Have a Nordic nRF52-DK board. </li>
-<li>Have Internet connectivity to fetch remote Mynewt components.</li>
-<li>Have a computer to build a Mynewt application and connect to the board over USB.</li>
-<li>Have a Micro-USB cable to connect the board and the computer.</li>
-<li>Have a <a href="../../get_started/serial_access/">Serial Port Setup</a>. </li>
-<li>Install the newt tool and the toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
-<li>Install the <a href="../../../newtmgr/installing/">newtmgr tool</a>. </li>
-<li>Create a project space (directory structure) and populated it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.</li>
-<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section.</li>
-</ul>
-<h3 id="overview-of-steps">Overview of Steps</h3>
-<ul>
-<li>Install dependencies</li>
-<li>Define targets using the newt tool</li>
-<li>Build executables for the targets using the newt tool</li>
-<li>Set up serial connection with the targets</li>
-<li>Create a connection profile using the newtmgr tool</li>
-<li>Use the newtmgr tool to communicate with the targets</li>
-</ul>
-<h3 id="create-a-new-project">Create a New Project</h3>
-<p>Create a new project if you do not have an existing one. You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already have a project created or completed the <a href="../project-slinky/">Sim Slinky</a> tutorial. </p>
-<p>Run the following commands to create a new project. We name the project <code>slinky</code>. </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt new slinky
-Downloading project skeleton from apache/incubator-mynewt-blinky...
-...
-Installing skeleton in slink...
-Project slinky successfully created
-$ cd slinky
-$newt install
-apache-mynewt-core
-</pre></div>
-
-
-<p><br></p>
-<h3 id="create-the-targets"><a name="create_targets"></a> Create the Targets</h3>
-<p>Create two targets for the nRF52-DK board - one for the bootloader and one for the Slinky application.</p>
-<p>Run the following <code>newt target</code> commands, from your project directory, to create a bootloader target. We name the target <code>nrf52_boot</code>.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create nrf52_boot
-$ newt target set nrf52_boot bsp=@apache-mynewt-core/hw/bsp/nrf52dk
-$ newt target set nrf52_boot build_profile=optimized
-$ newt target set nrf52_boot app=@apache-mynewt-core/apps/boot
-</pre></div>
-
-
-<p><br>
-Run the following <code>newt target</code> commands to create a target for the Slinky application. We name the target <code>nrf52_slinky</code>.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create nrf52_slinky
-$ newt target set nrf52_slinky bsp=@apache-mynewt-core/hw/bsp/nrf52dk
-$ newt target set nrf52_slinky build_profile=debug
-$ newt target set nrf52_slinky app=@apache-mynewt-core/apps/slinky
-</pre></div>
-
-
-<p><br></p>
-<h3 id="build-the-targets">Build the Targets</h3>
-<p>Run the <code>newt build nrf52_boot</code> command to build the bootloader:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt build nrf52-boot
-Building target targets/nrf52_boot
-Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c
-Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c
-Compiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c
-Compiling repos/apache-mynewt-core/crypto/mbedtls/src/aes.c
-Compiling repos/apache-mynewt-core/boot/bootutil/src/loader.c
-Compiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c
-Compiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c
-Compiling repos/apache-mynewt-core/apps/boot/src/boot.c
- ...
-
-Archiving sys_mfg.a
-Archiving sys_sysinit.a
-Archiving util_mem.a
-Linking ~/dev/slinky/bin/targets/nrf52_boot/app/apps/boot/boot.elf
-Target successfully built: targets/nrf52_boot
-</pre></div>
-
-
-<p><br></p>
-<p>Run the <code>newt build nrf52_slinky</code> command to build the Slinky application:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt build nrf52_slinky
-Building target targets/nrf52_slinky
-Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c
-Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c
-Compiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c
-Compiling repos/apache-mynewt-core/boot/split/src/split.c
-Compiling repos/apache-mynewt-core/boot/bootutil/src/loader.c
-Compiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c
-Compiling repos/apache-mynewt-core/boot/split/src/split_config.c
-Compiling repos/apache-mynewt-core/crypto/mbedtls/src/aesni.c
-Compiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c
-Compiling repos/apache-mynewt-core/crypto/mbedtls/src/aes.c
-Compiling repos/apache-mynewt-core/apps/slinky/src/main.c
-
- ...
-
-Archiving util_mem.a
-Linking ~/dev/slinky/bin/targets/nrf52_slinky/app/apps/slinky/slinky.elf
-Target successfully built: targets/nrf52_slinky
-</pre></div>
-
-
-<p><br></p>
-<h3 id="sign-and-create-the-slinky-application-image">Sign and Create the Slinky Application Image</h3>
-<p>Run the <code>newt create-image nrf52_slinky 1.0.0</code> command to create and sign the application image. You may assign an arbitrary version (e.g. 1.0.0) to the image.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt create-image nrf52_slinky 1.0.0
-App image succesfully generated: ~/dev/slinky/bin/targets/nrf52_slinky/app/apps/slinky/slinky.img
-$
-</pre></div>
-
-
-<p><br></p>
-<h3 id="connect-to-the-board">Connect to the Board</h3>
-<ul>
-<li>Connect a micro-USB cable from your computer to the micro-USB port on the nRF52-DK board.</li>
-<li>Turn the power on the board to ON. You should see the green LED light up on the board.</li>
-</ul>
-<p><br></p>
-<h3 id="load-the-bootloader-and-the-slinky-application-image">Load the Bootloader and the Slinky Application Image</h3>
-<p>Run the <code>newt load nrf52_boot</code> command to load the bootloader onto the board:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load nrf52_boot
-Loading bootloader
-$
-</pre></div>
-
-
-<p><br>
-Run the <code>newt load nrf52_slinky</code> command to load the Slinky application image onto the board:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load nrf52_slinky
-Loading app image into slot 1
-$
-</pre></div>
-
-
-<p><br></p>
-<h3 id="connect-newtmgr-with-the-board-using-a-serial-connection">Connect Newtmgr with the Board using a Serial Connection</h3>
-<p>Set up a serial connection from your computer to the nRF52-DK board (See <a href="../../get_started/serial_access/">Serial Port Setup</a>). </p>
-<p>Locate the port, in the /dev directory on your computer, that the serial connection uses. It should be of the type <code>tty.usbserial-<some identifier></code>.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ ls /dev/tty*usbserial*
-/dev/tty.usbserial-1d11
-$
-</pre></div>
-
-
-<p><br>
-Setup a newtmgr connection profile for the serial port. For our example, the port is <code>/dev/tty.usbserial-1d11</code>. </p>
-<p>Run the <code>newtmgr conn add</code> command to define a newtmgr connection profile for the serial port. We name the connection profile <code>nrf52serial</code>. You will need to replace the <code>connstring</code> with the specific port for your serial connection. </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr conn add nrf52serial type=serial connstring=/dev/tty.usbserial-1d11
-Connection profile nrf52serial successfully added
-$
-</pre></div>
-
-
-<p><br>
-You can run the <code>newt conn show</code> command to see all the newtmgr connection profiles:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr conn show
-Connection profiles:
- nrf52serial: type=serial, connstring='/dev/tty.usbserial-1d11'
- sim1: type=serial, connstring='/dev/ttys012'
-$
-</pre></div>
-
-
-<p><br></p>
-<h3 id="use-newtmgr-to-query-the-board">Use Newtmgr to Query the Board</h3>
-<p>Run some newtmgr commands to query and receive responses back from the board (See the <a href="../newtmgr/overview">Newt Manager Guide</a> for more information on the newtmgr commands). </p>
-<p>Run the <code>newtmgr echo hello -c nrf52serial</code> command. This is the simplest command that requests the board to echo back the text. </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr echo hello -c nrf52serial
-hello
-$
-</pre></div>
-
-
-<p><br>
-Run the <code>newtmgr image list -c nrf52serial</code> command to list the images on the board:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr image list -c nrf52serial
-Images:
- slot=0
- version: 1.0.0
- bootable: true
- flags: active confirmed
- hash: f411a55d7a5f54eb8880d380bf47521d8c41ed77fd0a7bd5373b0ae87ddabd42
-Split status: N/A
-$
-</pre></div>
-
-
-<p><br>
-Run the <code>newtmgr taskstats -c nrf52serial</code> command to display the task statistics on the board:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr taskstats -c nrf52serial
-Return Code = 0
- task pri tid runtime csw stksz stkuse last_checkin next_checkin
- task1 8 2 0 1751 192 110 0 0
- task2 9 3 0 1751 64 31 0 0
- idle 255 0 224081 2068 64 32 0 0
- main 127 1 3 29 1024 365 0 0
-$
-</pre></div>
-
- <div class="row">
-
-
-
-
-<ul class="nav nav-pills" style="margin-bottom: 10px">
- <li>
-
- <a href=../project-slinky/>
- <span class="fa fa-arrow-left"></span>
- Previous: Slinky on sim device
- </a>
-
- </li>
- <li class="pull-right">
-
- <a href=../project-stm32-slinky/>
- Next: Slinky on STM32 board
- <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
[08/11] incubator-mynewt-site git commit: Updated Blinky and Slinky
tutorials with intro summaries,
remove legacy feature references in the tutorials
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/bletiny_project/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/bletiny_project/index.html b/develop/os/tutorials/bletiny_project/index.html
index 01ebb02..868cc7b 100644
--- a/develop/os/tutorials/bletiny_project/index.html
+++ b/develop/os/tutorials/bletiny_project/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,7 +264,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -271,7 +272,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -279,20 +280,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -300,7 +296,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -308,42 +304,42 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
- <li class="active">
- <a href="./">BLE app to check stats via console</a>
+ <li >
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
- <li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <li class="active">
+ <a href="./">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -475,11 +471,11 @@
</div>
</div>
- <h2 id="check-stats-on-a-ble-device">Check stats on a BLE device</h2>
+ <h2 id="check-stats-for-a-ble-application-the-nrf52-board">Check stats for a BLE Application the NRF52 Board</h2>
<p><br></p>
<p>This tutorial explains how to run an example BLE app on a board and command it to scan and spew some stats. The stats will be seen over a serial port, not a BLE wireless connection.</p>
<p><br></p>
-<h3 id="pre-requisites">Pre-Requisites</h3>
+<h3 id="prerequisites">Prerequisites</h3>
<ul>
<li>Ensure you have installed <a href="../../../newt/install/newt_mac/">newt</a> and that the
newt command is in your system path. </li>
@@ -493,17 +489,13 @@ support native compiling to build the project this tutorial creates. </li>
<p><br></p>
<h3 id="create-a-project">Create a project</h3>
<p>Use the Newt tool to create a new project directory containing a skeletal Mynewt framework. Change into the newly created directory.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt new myapp1
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt new myproj
Downloading project skeleton from apache/incubator-mynewt-blinky...
-Installing skeleton in myapp1...
-Project myapp1 successfully created.
-$ cd myapp1
-
-$ newt install -v
-apache-mynewt-core
-Downloading repository description for apache-mynewt-core... success!
-...
-apache-mynewt-core successfully installed version 0.7.9-none
+Installing skeleton in myproj...
+Project myproj successfully created.
+$ cd myproj
+
+$ newt install
</pre></div>
@@ -555,7 +547,6 @@ targets/myble
app=@apache-mynewt-core/apps/bletiny
bsp=@apache-mynewt-core/hw/bsp/nrf52dk
build_profile=optimized
- cflags=-DSTATS_NAME_ENABLE
targets/nrf52_boot
app=@apache-mynewt-core/apps/boot
bsp=@apache-mynewt-core/hw/bsp/nrf52dk
@@ -578,24 +569,49 @@ syscfg.vals:
<p>The first configuration value turns on the Shell Task, and we'll need this to get to the shell. The next 2 enable the names for the various stats, and then turns on the stats CLI option.</p>
<h3 id="build-targets">Build targets</h3>
<p>Then build the two targets.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt build nrf52_boot
-<snip>
-App successfully built: ./bin/nrf52_boot/apps/boot/boot.elf
-$ newt build myble
-Compiling hci_common.c
-Compiling util.c
-Archiving nimble.a
-Compiling os.c
-<snip>
+<p>Run the <code>newt build nrf52_boot</code> command to build the bootloader:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">Building target targets/nrf52_boot
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/loader.c
+Compiling repos/apache-mynewt-core/apps/boot/src/boot.c
+
+Archiving sys_sysinit.a
+Archiving util_mem.a
+Linking ~/myproj/bin/targets/nrf52_boot/app/apps/boot/boot.elf
+Target successfully built: targets/nrf52_boot
+</pre></div>
+
+
+<p><br>
+Run the <code>newt build myble</code> command to build the bletiny application:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt build myble
+Building target targets/myble
+Compiling repos/apache-mynewt-core/encoding/base64/src/base64.c
+Compiling repos/apache-mynewt-core/encoding/base64/src/hex.c
+Compiling repos/apache-mynewt-core/hw/bsp/nrf52dk/src/hal_bsp.c
+Compiling repos/apache-mynewt-core/apps/bletiny/src/parse.c
+Compiling repos/apache-mynewt-core/apps/bletiny/src/misc.c
+Compiling repos/apache-mynewt-core/apps/bletiny/src/gatt_svr.c
+Compiling repos/apache-mynewt-core/apps/bletiny/src/cmd.c
+Compiling repos/apache-mynewt-core/apps/bletiny/src/main.c
+
+Archiving util_mem.a
+Linking ~/dev/myproj/bin/targets/myble/app/apps/bletiny/bletiny.elf
+Target successfully built: targets/myble
</pre></div>
<p><br></p>
<h3 id="create-the-app-image">Create the app image</h3>
-<p>Generate a signed application image for the <code>myble</code> target. The version number is arbitrary.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt create-image myble 1.0.0
-App image succesfully generated: ./bin/makerbeacon/apps/bletiny/bletiny.img
-Build manifest: ./bin/makerbeacon/apps/bletiny/manifest.json
+<p>Run the <code>newt create-image myble 1.0.0</code> command to generate a signed application image for the <code>myble</code> target. The version number is arbitrary.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt create-image myble 1.0.0
+Compiling bin/targets/myble/generated/src/myble-sysinit-app.c
+Archiving myble-sysinit-app.a
+Linking ~/dev/myproj/bin/targets/myble/app/apps/bletiny/bletiny.elf
+App image succesfully generated: ~/dev/myproj/bin/targets/myble/app/apps/bletiny/bletiny.img
</pre></div>
@@ -614,7 +630,7 @@ If you haven't done so already, make sure you're familiar with the <a href="../.
section. </p>
<p><br></p>
<p>You may use any terminal emulation program to communicate with the board. This tutorial shows a Minicom set up. </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ minicom -D /dev/tty.usbserial-AJ03HAQQ -b 115200
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ minicom -D /dev/tty.usbserial-1a12 -b 115200
</pre></div>
@@ -623,15 +639,15 @@ section. </p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">Welcome to minicom 2.7
OPTIONS:
-Compiled on Nov 24 2015, 16:14:21.
-Port /dev/tty.usbserial-AJ03HAQQ, 09:57:17
+Compiled on Mar 18 2016, 04:59:47.
+Port /dev/tty.usbserial-1a12, 21:24:09
Press Meta-Z for help on special keys
<span style="background-color: #ffffcc">?
-</span>4754:Commands:
-4754: echo ? prompt tasks mempools date
-4756: b
+</span>7471:Commands:
+7471: stat echo ? prompt ticks tasks
+7474: mempools date b
</pre></div>
@@ -651,90 +667,102 @@ This is just a counter kept by the MCU.</p>
<p><strong>Note</strong>: If you want to have a shell prompt by default, simply add the line: <code>CONSOLE_PROMPT: 1</code> to your <code>syscfg.yml</code> file and it will be turned on by default.</p>
<p><br></p>
<p>Try the <code>tasks</code> command. </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="background-color: #ffffcc">27365: > tasks
-</span>Tasks:
-28330: idle (prio: 255, tid: 0, lcheck: 0, ncheck: 0, flags: 0x0, ssize: 64, susage: 34, cswcnt: 233, tot_run_time: 28330ms)
-28333: ble_ll (prio: 0, tid: 1, lcheck: 0, ncheck: 0, flags: 0x0, ssize: 80, susage: 60, cswcnt: 11, tot_run_time: 0ms)
-28336: shell (prio: 1, tid: 2, lcheck: 0, ncheck: 0, flags: 0x0, ssize: 512, susage: 115, cswcnt: 18, tot_run_time: 0ms)
-28339: bletiny (prio: 1, tid: 3, lcheck: 0, ncheck: 0, flags: 0x0, ssize: 512, susage: 138, cswcnt: 456, tot_run_time: 0ms)
-28342: >
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="background-color: #ffffcc">> tasks
+</span>Tasks:
+46682: task pri tid runtime csw stksz stkuse lcheck ncheck fg
+46684: idle 255 0 46683 99 64 31 0 0 0
+46686: main 127 1 1 29 512 156 0 0 0
+46688: ble_ll 0 2 0 12 80 58 0 0 0
+46691: >
</pre></div>
<p><br></p>
<p>Try specifying a BLE related stat, for example <code>ble_ll</code>. You should see some HCI (Host Controller Interface) command counts. </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="background-color: #ffffcc">241133: > stat ble_ll
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="background-color: #ffffcc">113136: > stat ble_ll
</span>hci_cmds: 11
-241888:hci_cmd_errs: 0
-241888:hci_events_sent: 11
-241890:bad_ll_state: 0
-241890:bad_acl_hdr: 0
-241891:no_bufs: 0
-241891:rx_adv_pdu_crc_ok: 0
-241892:rx_adv_pdu_crc_err: 0
-241893:rx_adv_bytes_crc_ok: 0
-241894:rx_adv_bytes_crc_err: 0
-241895:rx_data_pdu_crc_ok: 0
-241895:rx_data_pdu_crc_err: 0
-<snip>
+155545:hci_cmd_errs: 0
+155545:hci_events_sent: 11
+155547:bad_ll_state: 0
+155547:bad_acl_hdr: 0
+155548:no_bufs: 0
+155548:rx_adv_pdu_crc_ok: 0
+155549:rx_adv_pdu_crc_err: 0
+155550:rx_adv_bytes_crc_ok: 0
+155551:rx_adv_bytes_crc_err: 0
+155552:rx_data_pdu_crc_ok: 0
+
+ ...
+
+155564:scan_req_txf: 0
+155565:scan_req_txg: 0
+155565:scan_rsp_txg: 0
+155566: >
</pre></div>
<p><br></p>
-<p>For a more exciting output, try scanning your surroundings for BLE adverstisements. The HCI command shown below specifies a scan duration in ms, sets discovery mode to general (as opposed to limited), the filter to no-whitelist, and type of scan to passive. You should see some scan data flying by!</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="background-color: #ffffcc">139088: > b scan dur=10000 disc=gen filt=no_wl type=passive
-</span>...
-146055:received advertisement; event_type=0 addr_type=1 addr=6b:aa:49:b7:46:e6 length_data=24 rssi=-42 data=0x02:0x01:0x1a:0x14:0xff:0x4c:0x00:0x01:0x00:0x00:0x00:0x00:0x04:0x00:0x00:0x00:0x00:0x00:0x00:0x00:0x00:0x00:0x00:0x00 fields:
-146061: flags=0x1a
-146062: mfg_data=0x4c:0x00:0x01:0x00:0x00:0x00:0x00:0x04:0x00:0x00:0x00:0x00:0x00:0x00:0x00:0x00:0x00:0x00:0x00
-146065:
-146065:received advertisement; event_type=0 addr_type=0 addr=ac:bc:32:ac:4f:e4 length_data=11 rssi=-36 data=0x02:0x01:0x06:0x07:0xff:0x4c:0x00:0x10:0x02:0x0b:0x00 fields:
-146069: flags=0x06
-146070: mfg_data=0x4c:0x00:0x10:0x02:0x0b:0x00
-146071:
-146072:scanning finished
-...
-<snip>
+<p>For a more exciting output, try scanning your surroundings for BLE advertisements. The HCI command shown below specifies a scan duration in ms, scan to passive, and no duplicates. You should see some scan data flying by!</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="background-color: #ffffcc">b scan dur=10000 passive=1 nodups=1
+</span>37266:[ts=291140616ssb, mod=4 level=1] GAP procedure initiated: discovery; own_as
+
+37641:
+38256:received advertisement; event_type=0 rssi=-48 addr_type=1 addr=59:cc:3d:a3:
+38261: flags=0x1a:
+38261: General discoverable mode
+38262: uuids16(complete)=0x1802
+38263: name(complete)=Find Me
+38264:
+38551:scanning finished
</pre></div>
<p><br></p>
<p>If you're still not seeing any output from the device, try running the debugger and see if you are seeing the program execute properly. </p>
<p><br></p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt debug myble
-Debugging ./bin/myble/apps/bletiny/bletiny.elf
-GNU gdb (GNU Tools for ARM Embedded Processors) 7.6.0.20140731-cvs
-Copyright (C) 2013 Free Software Foundation, Inc.
-
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt debug myble
+[~/dev/myproj/repos/apache-mynewt-core/hw/bsp/nrf52dk/nrf52dk_debug.sh ~/dev/myproj/repos/apache-mynewt-core/hw/bsp/nrf52dk ~/dev/wanda/dev/myproj/bin/targets/myble/app/apps/bletiny/bletiny]
+~/dev/myproj/repos/apache-mynewt-core/hw/scripts/common.sh: line 38: [: =: unary operator expected
+Debugging ~/dev/myproj/bin/targets/myble/app/apps/bletiny/bletiny.elf
+GNU gdb (GNU Tools for ARM Embedded Processors) 7.8.0.20150604-cvs
+Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=x86_64-apple-darwin10 --target=arm-none-eabi".
+Type "show configuration" for configuration details.
For bug reporting instructions, please see:
-<http://www.gnu.org/software/gdb/bugs/>...
-Reading symbols from ./bin/myble/apps/bletiny/bletiny.elf...done.
-0x00002f08 in ?? ()
+<http://www.gnu.org/software/gdb/bugs/>.
+Find the GDB manual and other documentation resources online at:
+<http://www.gnu.org/software/gdb/documentation/>.
+For help, type "help".
+Type "apropos word" to search for commands related to "word"...
+Reading symbols from ~/dev/myproj/bin/targets/myble/app/apps/bletiny/bletiny.elf...done.
+os_tick_idle (ticks=1920)
+ at repos/apache-mynewt-core/hw/mcu/nordic/nrf52xxx/src/hal_os_tick.c:200
+200 if (ticks > 0) {
(gdb) monitor reset
Resetting target
(gdb) c
Continuing.
^C
Program received signal SIGTRAP, Trace/breakpoint trap.
-os_tick_idle (ticks=1000) at hal_os_tick.c:117
-117 if (ticks > 0) {
+os_tick_idle (ticks=1907)
+ at repos/apache-mynewt-core/hw/mcu/nordic/nrf52xxx/src/hal_os_tick.c:200
+200 if (ticks > 0) {
(gdb) p g_os_time
-$1 = 37991
+$1 = 13
(gdb) c
Continuing.
^C
Program received signal SIGTRAP, Trace/breakpoint trap.
-os_tick_idle (ticks=1000) at hal_os_tick.c:117
-117 if (ticks > 0) {
+os_tick_idle (ticks=1920)
+ at repos/apache-mynewt-core/hw/mcu/nordic/nrf52xxx/src/hal_os_tick.c:200
+200 if (ticks > 0) {
(gdb) p g_os_time
-$2 = 51888
-(gdb) c
-Continuing.
+$2 = 6611
+(gdb)
</pre></div>
@@ -749,9 +777,9 @@ Continuing.
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../add_shell/>
+ <a href=../event_queue/>
<span class="fa fa-arrow-left"></span>
- Previous: Enable the OS Shell and Console
+ Previous: Events and Event Queues
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/blinky/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/blinky/index.html b/develop/os/tutorials/blinky/index.html
new file mode 100644
index 0000000..c5644bb
--- /dev/null
+++ b/develop/os/tutorials/blinky/index.html
@@ -0,0 +1,634 @@
+<!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/os/tutorials/blinky/"> -->
+ <link rel="shortcut icon" href="../../../img/favicon.ico">
+
+ <title>toc - 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="toc">
+
+
+ <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</a> released (March 22, 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="../../introduction/">Mynewt Documentation</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../../get_started/get_started/">Basic Setup</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../get_started/vocabulary/">Concepts</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../tutorials/">Tutorials</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li class="active"><a href="./">Project Blinky</a>
+
+
+ <ul>
+
+
+
+
+
+ <li >
+ <a href="../arduino_zero/">Blinky on Arduino Zero</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../blinky_primo/">Blinky on Arduino Primo</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../olimex/">Blinky on Olimex</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../STM32F303/">Blinky on STM32F303</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../nRF52/">Blinky on nRF52</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../rbnano2/">Blinky on RedBear Nano 2</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../blinky_console/">Add Console and Shell to Blinky</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../repo/add_repos/">Work with repositories</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../ibeacon/">BLE iBeacon</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../eddystone/">BLE Eddystone</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../blehci_project/">BLE HCI interface</a>
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../air_quality_sensor/
+">Air-quality Sensor project</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../nrf52_adc/">Add an Analog Sensor</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../os_user_guide/">OS User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../../network/ble/ble_intro/
+">BLE User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../newt/newt_intro/">Newt Tool Guide</a>
+
+
+ </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="../tutorials/">Tutorials</a></li>
+
+
+
+ <li>» Project Blinky</li>
+
+
+
+
+
+ </ul>
+</div>
+ </div>
+
+ <h2 id="blinky-your-hello-world-on-a-target-board">Blinky, your "Hello World!" on a Target Board</h2>
+<p>The set of Blinky tutorials show you how to create, build, and run a "Hello World" application that blinks a LED on the various target boards that Mynewt supports. The tutorials use the same Blinky application from the <a href="../../../os/get_started/project_create">Creating Your First Project</a> tutorial. </p>
+<h3 id="objective">Objective</h3>
+<p>Learn how to use packages from a default application repository of Mynewt to build your first <em>Hello World</em> application (Blinky) on a target board. Once built using the <em>newt</em> tool, this application will blink a LED light on the target board.</p>
+<h3 id="available-tutorials">Available Tutorials</h3>
+<p>Tutorials are available for the following boards:</p>
+<ul>
+<li><a href="../arduino_zero/">Blinky on an Arduino Zero</a></li>
+<li><a href="../blinky_primo/">Blinky on an Arduino Primo</a></li>
+<li><a href="../olimex/">Blinky on an Olimex</a></li>
+<li><a href="../nRF52/">Blinky on a nRF52</a></li>
+<li><a href="../rbnano2/">Blinky on a RedBear Nano 2</a></li>
+</ul>
+<p>We also have a tutorial that shows you how to add <a href="../blinky_console/">Console and Shell to the Blinky Application</a>.
+<br></p>
+<h3 id="prerequisites">Prerequisites</h3>
+<p>Ensure that you meet the following prerequisites before continuing with one of the tutorials. </p>
+<ul>
+<li>Have Internet connectivity to fetch remote Mynewt components.</li>
+<li>Have a computer to build a Mynewt application and connect to the board over USB.</li>
+<li>Have a Micro-USB cable to connect the board and the computer.</li>
+<li>Install the Newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
+<li>Install either the Jlink or OpenOCD debugger.</li>
+<li>Create a project space (directory structure) and populate it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.</li>
+<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section.
+<br></li>
+</ul>
+<h3 id="overview-of-steps">Overview of Steps</h3>
+<p>These are the general steps to create, load and run the Blinky application on your board:</p>
+<ul>
+<li>Create a project.</li>
+<li>Define the bootloader and Blinky application targets for the board.</li>
+<li>Build the bootloader target.</li>
+<li>Build the Blinky application target and create an application image.</li>
+<li>Connect to the board.</li>
+<li>Load the bootloader onto the board.</li>
+<li>Load the Blinky application image onto the board.</li>
+<li>See the LED on your board blink.</li>
+</ul>
+<p><br></p>
+<p>After you try the Blinky application on your boards, checkout out other tutorials to enable additional functionality such as <a href="../project-slinky/">remote comms</a> on the current board. If you have BLE (Bluetooth Low Energy) chip (e.g. nRF52) on your board, you can try turning it into an <a href="../ibeacon/">iBeacon</a> or <a href="../eddystone/">Eddystone Beacon</a>! </p>
+<p>If you see anything missing or want to send us feedback, please sign up for
+appropriate mailing lists on our <a href="../../../community/">Community Page</a>.</p>
+
+ <div class="row">
+
+
+
+
+<ul class="nav nav-pills" style="margin-bottom: 10px">
+ <li>
+
+ <a href=../tutorials/>
+ <span class="fa fa-arrow-left"></span>
+ Previous: Tutorials
+ </a>
+
+ </li>
+ <li class="pull-right">
+
+ <a href=../arduino_zero/>
+ Next: Blinky on Arduino Zero
+ <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/40899401/develop/os/tutorials/blinky_console/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/blinky_console/index.html b/develop/os/tutorials/blinky_console/index.html
index b19b882..d0157d9 100644
--- a/develop/os/tutorials/blinky_console/index.html
+++ b/develop/os/tutorials/blinky_console/index.html
@@ -232,14 +232,14 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
<ul>
+
+
<li >
<a href="../arduino_zero/">Blinky on Arduino Zero</a>
@@ -317,8 +317,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -326,7 +329,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -334,7 +337,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -342,20 +345,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -363,7 +361,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -371,7 +369,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -379,18 +377,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -398,15 +393,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -526,7 +524,7 @@
- <li>» <a href="../arduino_zero/">Project Blinky</a></li>
+ <li>» <a href="../blinky/">Project Blinky</a></li>
@@ -539,12 +537,12 @@
</div>
<h2 id="enabling-the-console-and-shell-for-blinky">Enabling The Console and Shell for Blinky</h2>
-<p><br></p>
-<p>This tutorial explains how to add the Console and Shell task to the blinky application so that you can interact with it over a serial line connection.</p>
-<p><br></p>
+<p>This tutorial shows you how to add the Console and Shell to the Blinky application and interact with it over a serial line connection.
+<br></p>
<h3 id="prerequisites">Prerequisites</h3>
<ul>
<li>Work through one of the Blinky Tutorials to create and build a Blinky application for one of the boards.</li>
+<li>Have a <a href="../../get_started/serial_access/">serial setup</a>.</li>
</ul>
<p><br></p>
<h3 id="use-an-existing-project">Use an Existing Project</h3>
@@ -576,13 +574,13 @@ the shell and console connectivity. You can use blinky on a different board.</p>
<p><br></p>
<h3 id="use-the-os-default-event-queue-to-process-blinky-timer-and-shell-events">Use the OS Default Event Queue to Process Blinky Timer and Shell Events</h3>
-<p>Mynewt creates a default task that executes the application <code>main()</code> function. It also creates an OS default event queue that packages can use to queue their events. Shell uses the OS default event queue for Shell events, and <code>main()</code> can process the events in the context of the default task. </p>
+<p>Mynewt creates a main task that executes the application <code>main()</code> function. It also creates an OS default event queue that packages can use to queue their events. Shell uses the OS default event queue for Shell events, and <code>main()</code> can process the events in the context of the main task. </p>
<p>Blinky's main.c is very simple. It only has a <code>main()</code> function that executes an infinite loop to toggle the LED and sleep for one second. We will modify blinky:</p>
<ul>
<li>To use os_callout to generate a timer event every one second instead of sleeping. The timer events are added to the OS default event queue.</li>
<li>To process events from the OS default event queue inside the infinite loop in <code>main()</code>.</li>
</ul>
-<p>This allows the default task to process both Shell events and the timer events to toggle the LED from the OS default event queue.</p>
+<p>This allows the main task to process both Shell events and the timer events to toggle the LED from the OS default event queue.</p>
<p><br></p>
<h3 id="modify-mainc">Modify main.c</h3>
<p>Initialize a os_callout timer and move the toggle code from the while loop in <code>main()</code> to the event callback function. Add the following code above the <code>main()</code> function:</p>
@@ -678,7 +676,7 @@ Loading app image into slot 1
Tutorial for more information on setting up your serial communication.</p>
<p><br></p>
<h3 id="communicate-with-the-application">Communicate with the Application</h3>
-<p>Once you have a connection set up, run <code>minicom -D /dev/tty.usbmodem<port> -b 115200</code> to connect to the application console.</p>
+<p>Once you have a connection set up, run <code>minicom -D /dev/tty.usbserial<port> -b 115200</code> to connect to the application console.</p>
<p>To test and make sure that the Shell is running, first just hit <return>:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">3534: >
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/blinky_primo/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/blinky_primo/index.html b/develop/os/tutorials/blinky_primo/index.html
index 8001c04..5b2ee74 100644
--- a/develop/os/tutorials/blinky_primo/index.html
+++ b/develop/os/tutorials/blinky_primo/index.html
@@ -232,14 +232,14 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
<ul>
+
+
<li >
<a href="../arduino_zero/">Blinky on Arduino Zero</a>
@@ -317,8 +317,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -326,7 +329,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -334,7 +337,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -342,20 +345,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -363,7 +361,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -371,7 +369,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -379,18 +377,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -398,15 +393,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -526,7 +524,7 @@
- <li>» <a href="../arduino_zero/">Project Blinky</a></li>
+ <li>» <a href="../blinky/">Project Blinky</a></li>
@@ -539,23 +537,14 @@
</div>
<h2 id="blinky-your-hello-world-on-arduino-primo">Blinky, your "Hello World!", on Arduino Primo</h2>
-<p><br></p>
-<h3 id="objective">Objective</h3>
-<p>Learn how to use packages from a default application repository of Mynewt to build your first <em>Hello World</em> application (Blinky) on a target board. Once built using the <em>newt</em> tool, this application will blink the LED lights on the target board.</p>
-<p>Create a project with a simple app that blinks an LED on the Arduino Primo board. Download the application to the target and watch it blink!</p>
-<p>Note that the Mynewt OS will run on the nRF52 chip in the Arduino Primo board. However, the board support package for the Arduino Primo is different from the nRF52 dev kit board support package.</p>
-<p><br></p>
+<p>This tutorial shows you how to create, build, and run the Blinky application on an Arduino Primo board.</p>
+<p>Note that the Mynewt OS will run on the nRF52 chip in the Arduino Primo board. However, the board support package for the Arduino Primo is different from the nRF52 dev kit board support package.
+<br></p>
<h3 id="prerequisites">Prerequisites</h3>
-<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
<ul>
-<li>Have an Arduino Primo</li>
-<li>Have Internet connectivity to fetch remote Mynewt components.</li>
-<li>Have a computer to build a Mynewt application and connect to the` board over USB.</li>
-<li>Have a Micro-USB cable to connect the board and the computer.</li>
-<li>Install the Newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
-<li>Create a project space (directory structure) and populated it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.</li>
-<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section.</li>
-<li>Install a debugger - choose one of the two options below. Option 1 requires additional hardware but very easy to set up. Option 2 is free software but not as simple as Option 1.</li>
+<li>Meet the the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
+<li>Have an Arduino Primo board.</li>
+<li>Install a debugger choose one of the two options below: Option 1 requires additional hardware but very easy to set up. </li>
</ul>
<p><br></p>
<h5 id="option-1">Option 1</h5>
@@ -580,7 +569,6 @@ For bug reports, read
<p>You can now use openocd to upload to Arduino Primo board via the USB port itself.</p>
-<p><br></p>
<h3 id="create-a-project">Create a Project</h3>
<p>Create a new project if you do not have an existing one. You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already created a project.</p>
<p>Run the following commands to create a new project:</p>
@@ -761,12 +749,6 @@ warning: Source file is more recent than executable.
<p><br></p>
-<h3 id="conclusion">Conclusion</h3>
-<p>You have created, setup, compiled, loaded, and ran your first mynewt application
-for an Arduino Primo board.</p>
-<p>We have more fun tutorials for you to get your hands dirty. Be bold and work on the OS with tutorials on <a href="../unit_test/">writing a test suite</a> or try enabling additional functionality such as <a href="../project-target-slinky/">remote comms</a> or <a href="../bletiny_project/">Bluetooth Low Energy</a> on your current board.</p>
-<p>If you see anything missing or want to send us feedback, please do so by signing up for appropriate mailing lists on our <a href="../../../community/">Community Page</a>.</p>
-<p>Keep on hacking and blinking!</p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/eddystone/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/eddystone/index.html b/develop/os/tutorials/eddystone/index.html
index 302472d..63b2dc74 100644
--- a/develop/os/tutorials/eddystone/index.html
+++ b/develop/os/tutorials/eddystone/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,15 +264,15 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
- <li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <li class="active">
+ <a href="./">BLE Eddystone</a>
</li>
@@ -279,20 +280,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -300,7 +296,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -308,7 +304,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,18 +312,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li class="active">
- <a href="./">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -694,8 +690,8 @@ your Eddystone-aware devices.</p>
</li>
<li class="pull-right">
- <a href=../blehci_project/>
- Next: BLE HCI interface
+ <a href=../add_newtmgr/>
+ Next: Enable Newt Manager in any app
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/event_queue/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/event_queue/index.html b/develop/os/tutorials/event_queue/index.html
index c291ff2..514c3fd 100644
--- a/develop/os/tutorials/event_queue/index.html
+++ b/develop/os/tutorials/event_queue/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,7 +264,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -271,28 +272,23 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
- <li class="active">
- <a href="./">Events and Event Queues</a>
+ <li >
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -300,7 +296,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -308,7 +304,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,18 +312,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li class="active">
+ <a href="./">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -947,8 +943,8 @@ Implement the <code>my_interrupt_ev_cb()</code> callback function to process an
</li>
<li class="pull-right">
- <a href=../project-slinky/>
- Next: Slinky on sim device
+ <a href=../bletiny_project/>
+ Next: BLE app to check stats via console
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/ibeacon/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/ibeacon/index.html b/develop/os/tutorials/ibeacon/index.html
index 5f092a9..f593b2b 100644
--- a/develop/os/tutorials/ibeacon/index.html
+++ b/develop/os/tutorials/ibeacon/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,16 +252,19 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
- <li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <li class="active">
+ <a href="./">BLE iBeacon</a>
</li>
@@ -271,7 +272,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -279,20 +280,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -300,7 +296,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -308,7 +304,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,34 +312,34 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
- <li class="active">
- <a href="./">BLE iBeacon</a>
+ <li >
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -641,9 +637,9 @@ your iBeacon-aware devices.</p>
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../bleprph/bleprph-app/>
+ <a href=../project-stm32-slinky/>
<span class="fa fa-arrow-left"></span>
- Previous: BLE Peripheral App
+ Previous: Slinky on Olimex
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/nRF52/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/nRF52/index.html b/develop/os/tutorials/nRF52/index.html
index afbd3bc..595a972 100644
--- a/develop/os/tutorials/nRF52/index.html
+++ b/develop/os/tutorials/nRF52/index.html
@@ -232,14 +232,14 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
<ul>
+
+
<li >
<a href="../arduino_zero/">Blinky on Arduino Zero</a>
@@ -317,8 +317,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -326,7 +329,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -334,7 +337,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -342,20 +345,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -363,7 +361,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -371,7 +369,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -379,18 +377,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -398,15 +393,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -526,7 +524,7 @@
- <li>» <a href="../arduino_zero/">Project Blinky</a></li>
+ <li>» <a href="../blinky/">Project Blinky</a></li>
@@ -539,27 +537,18 @@
</div>
<h2 id="blinky-your-hello-world-on-nrf52">Blinky, your "Hello World!", on nRF52</h2>
-<p><br></p>
-<h3 id="objective">Objective</h3>
-<p>Learn how to use packages from a default application repository of Mynewt to build your first <em>Hello World</em> application (Blinky) on a target board. Once built using the <em>newt</em> tool, this application will blink the LED lights on the target board.</p>
-<p>Create a project with a simple application that blinks an LED on the nRF52 board from Nordic Semiconductors. Download the application to the target and watch it blink!</p>
+<p>This tutorial shows you how to create, build, and run the Blinky application on the nRF52 board.
+<br></p>
<p>Note that there are several versions of the nRF52 in the market. The boards tested with this tutorial are listed under "Prerequisites".</p>
<p><br></p>
<h3 id="prerequisites">Prerequisites</h3>
-<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
<ul>
+<li>Meet the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
<li>Have a nRF52 Development Kit (one of the following)<ul>
<li>Dev Kit from Nordic - PCA 10040</li>
<li>Eval Kit from Rigado - BMD-300-EVAL-ES</li>
</ul>
</li>
-<li>Have Internet connectivity to fetch remote Mynewt components.</li>
-<li>Have a computer to build a Mynewt application and connect to the board over USB.</li>
-<li>Have a Micro-USB cable to connect the board and the computer.</li>
-<li>Install the Newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
-<li>Install the <a href="https://www.segger.com/jlink-software.html">Segger JLINK package</a> to load your project on the board.</li>
-<li>Create a project space (directory structure) and populated it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.</li>
-<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section.</li>
</ul>
<p>This tutorial uses the Nordic nRF52-DK board.</p>
<h3 id="create-a-project">Create a Project</h3>
@@ -718,13 +707,6 @@ Erasing done.
J-Link>exit
$
</pre></div>
-
-
-<h3 id="conclusion">Conclusion</h3>
-<p>You have created, setup, compiled, loaded, and ran your first mynewt application for an nrf52 board.</p>
-<p>We have more fun tutorials for you to get your hands dirty. Be bold and work on the OS with tutorials on <a href="../unit_test/">writing a test suite</a> or try enabling additional functionality such as <a href="../project-target-slinky/">remote comms</a> or <a href="../bletiny_project/">Bluetooth Low Energy</a> on your current board.</p>
-<p>If you see anything missing or want to send us feedback, please do so by signing up for appropriate mailing lists on our <a href="../../../community/">Community Page</a>.</p>
-<p>Keep on hacking and blinking!</p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/nrf52_adc/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/nrf52_adc/index.html b/develop/os/tutorials/nrf52_adc/index.html
index 3c3e3de..9924212 100644
--- a/develop/os/tutorials/nrf52_adc/index.html
+++ b/develop/os/tutorials/nrf52_adc/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,7 +264,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -271,7 +272,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -279,20 +280,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -300,7 +296,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -308,7 +304,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,18 +312,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -530,12 +526,12 @@ project.repositories:
#
repository.apache-mynewt-core:
type: github
- vers: 0-dev
+ vers: 1-dev
user: apache
repo: incubator-mynewt-core
<span style="background-color: #ffffcc">repository.mynewt_nordic:
</span><span style="background-color: #ffffcc"> type: github
-</span><span style="background-color: #ffffcc"> vers: 0-latest
+</span><span style="background-color: #ffffcc"> vers: 1-latest
</span><span style="background-color: #ffffcc"> user: runtimeinc
</span><span style="background-color: #ffffcc"> repo: mynewt_nordic
</span></pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/olimex/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/olimex/index.html b/develop/os/tutorials/olimex/index.html
index 01f4dd3..ccc522f 100644
--- a/develop/os/tutorials/olimex/index.html
+++ b/develop/os/tutorials/olimex/index.html
@@ -232,14 +232,14 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
<ul>
+
+
<li >
<a href="../arduino_zero/">Blinky on Arduino Zero</a>
@@ -317,8 +317,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -326,7 +329,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -334,7 +337,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -342,20 +345,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -363,7 +361,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -371,7 +369,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -379,18 +377,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -398,15 +393,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -526,7 +524,7 @@
- <li>» <a href="../arduino_zero/">Project Blinky</a></li>
+ <li>» <a href="../blinky/">Project Blinky</a></li>
@@ -539,24 +537,16 @@
</div>
<h2 id="blinky-your-hello-world-on-olimex">Blinky, your "Hello World!", on Olimex</h2>
-<h3 id="objective">Objective</h3>
-<p>Learn how to use packages from a default application repository of Mynewt to build your first <em>Hello World</em> application (Blinky) on a target board. Once built using the <em>newt</em> tool, this application will blink the LED lights on the target board. Fun stuff!</p>
-<p>This tutorial shows you how to create a blinky application for the Olimex board. It also shows you how to load the application onto the board's flash memory and run the application.</p>
-<p><br></p>
+<p>This tutorial shows you how to create, build, and run the Blinky application on an Olimex STM32-E407 board.
+<br></p>
<h3 id="prerequisites">Prerequisites</h3>
-<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
<ul>
+<li>Meet the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
<li>Have a STM32-E407 development board from Olimex. </li>
<li>Have a ARM-USB-TINY-H connector with JTAG interface for debugging ARM microcontrollers (comes with the ribbon cable to hook up to the board)</li>
-<li>Have Internet connectivity to fetch remote Mynewt components.</li>
-<li>Have a computer to build a Mynewt application and connect to the board over USB.</li>
-<li>Have a USB A-B type cable to connect the debugger to your computer.</li>
-<li>Have a USB Micro-A cable to connect your computer to the board.</li>
-<li>Install the Newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
-<li>Create a project space (directory structure) and populated it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.</li>
-<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section.</li>
+<li>Have a USB A-B type cable to connect the debugger to your computer.
+<br></li>
</ul>
-<p><br></p>
<h3 id="create-a-project">Create a Project</h3>
<p>Create a new project if you do not have an existing one. You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already created a project.</p>
<p>Run the following commands to create a new project:</p>
@@ -740,13 +730,6 @@ Let's double check that it is indeed booting from flash and making the LED blink
(0x08000020: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
(gdb) monitor flash info 0
</pre></div>
-
-
-<h3 id="conclusion">Conclusion</h3>
-<p>Congratulations! You have now tried out a project on actual hardware. If this is your first time to embedded systems, this must feel like the best hands-on and low-level "Hello World" program ever.</p>
-<p>Good, we have more fun tutorials for you to get your hands dirty. Be bold and try other Blinky-like <a href="../nRF52/">tutorials</a> or try enabling additional functionality such as <a href="../project-target-slinky/">remote comms</a> on the current board.</p>
-<p>If you see anything missing or want to send us feedback, please do so by signing up for appropriate mailing lists on our <a href="../../../community/">Community Page</a>.</p>
-<p>Keep on hacking and blinking!</p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/pin-wheel-mods/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/pin-wheel-mods/index.html b/develop/os/tutorials/pin-wheel-mods/index.html
index e83b049..5e3883b 100644
--- a/develop/os/tutorials/pin-wheel-mods/index.html
+++ b/develop/os/tutorials/pin-wheel-mods/index.html
@@ -232,14 +232,14 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
<ul>
+
+
<li >
<a href="../arduino_zero/">Blinky on Arduino Zero</a>
@@ -331,8 +331,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -340,7 +343,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -348,7 +351,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -356,20 +359,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -377,7 +375,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -385,7 +383,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -393,18 +391,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -412,15 +407,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -536,7 +534,7 @@
- <li>» <a href="../arduino_zero/">Project Blinky</a></li>
+ <li>» <a href="../blinky/">Project Blinky</a></li>
[05/11] incubator-mynewt-site git commit: Updated Blinky and Slinky
tutorials with intro summaries,
remove legacy feature references in the tutorials
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/mkdocs/search_index.json
----------------------------------------------------------------------
diff --git a/latest/mkdocs/search_index.json b/latest/mkdocs/search_index.json
index 42a20f1..23eceed 100644
--- a/latest/mkdocs/search_index.json
+++ b/latest/mkdocs/search_index.json
@@ -277,7 +277,7 @@
},
{
"location": "/newt/install/newt_linux/",
- "text": "Install newt tool on Linux\n\n\n\n\nGetting your Linux box Ready\n\n\nIf you want to build the \nnewt\n tool from its source code, follow the following steps:\n\n\n1. Install git, libcurl\n\n\n $ sudo apt-get install git \n $ sudo apt-get install libcurl4-gnutls-dev \n\n\n\n\n\nNOTE:\n On 64-bit host, you may also need to install gcc-multilib, if you encounter compilation errors related to 'sys/cdefs.h'\n\n\n\n\n2. Install Go, the programming language\n\n\n\n\n\n\nGo language environment dictates a directory structure. Known in Go parlance as a workspace, it must contain three sibling directories with the directory names src, pkg and bin, as explained below. \n\n\n\n\n\n\nsrc contains Go source files organized into packages (one package per directory),\n\n\n\n\n\n\npkg contains package objects, and\n\n\n\n\n\n\nbin contains executable commands.\n\n\n\n\n\n\nThe GOPATH environment variable specifies the location of your workspace. To setup this work
space environment, create a 'dev' directory and then a 'go' directory under it. Set the GOPATH environment variable to this directory where you will soon clone the \nnewt\n tool repository.\n\n\n\n\n\n\n $ cd $HOME\n $ mkdir -p dev/go \n $ cd dev/go\n $ export GOPATH=`pwd`\n\n\n\n\n\n(Note that you need to add export statements to ~/.bash_profile to export variables permanently. Don't forget to source the file for the change to go into effect.)\n\n\n\n\n $ vi ~/.bash_profile\n $ source ~/.bash_profile\n\n\n\n\n\n\n\n\n\n\n\nNext, install Go. When installed, Go offers you as a developer a language environment (to compile Go code), construct Go packages (to assemble Go packages) and import Go code (from github). In the next step, you will use the Go commands to import \nnewt\n repo into your local Go environment.\n\n\nNote\n: The Newt tool requires Go version 1.6 or later. Depending on the Ubuntu version you have, the following may install an
earlier version. In that case, download the latest package of Go 1.6 from \nhttps://golang.org/dl/\n. You can search for more detailed instructions such as installing Go 1.6 on Ubuntu 14.04 which can be found at \nhttps://www.digitalocean.com/community/tutorials/how-to-install-go-1-6-on-ubuntu-14-04\n.\n\n\n\n\n\n\n $ sudo apt-get install golang \n\n\n\n\n\n \n\n\n3. Create local repository\n\n\n\n\nUse Go commands to copy the directory (currently the ASF incubator directory). Be patient as it may take a minute or two. Check the directories installed.\n\n\n\n\n $ go get mynewt.apache.org/newt/...\n\n\n\n\n\n\n\n\n\nCheck that newt.go is in place.\n\n\n\n\n $ ls $GOPATH/src/mynewt.apache.org/newt\n DISCLAIMER NOTICE newt newtvm viper\n LICENSE README.md newtmgr util yaml\n\n\n\n\n\n\n\n4. Build the Newt tool\n\n\n\n\nUse Go to run the newt.go program to build the \nnewt\n tool. The command \ngo install\n compil
es and writes the resulting executable to an output file named \nnewt\n, which is then installed, along with its dependencies, in $GOPATH/bin. If you get errors it is likely because of path resolution issues. Try \ngo build\n followed by \ngo install\n in that case.\n\n\n\n\n $ cd $GOPATH/src/mynewt.apache.org/newt/newt\n $ go install\n $ ls \n$GOPATH\n/bin/\n newt newtmgr newtvm\n\n\n\n\n\n\n\n\n\nAt this point, you can try using \nnewt\n. For example, check for the version number by typing 'newt version'. See all the possible commands available to a user of newt by typing 'newt -h'.\n\n\n\n\n(Note: If you are going to be modifying the \nnewt\n often and going to be compile the program every time you call it, you will want to store the command in a variable in your .bash_profile. So type in \nexport newt=\"go run $GOPATH/mynewt.apache.org/newt/newt/newt.go\"\n in your .bash_profile and execute it by calling \n$newt\n at the prompt instead of \nnewt\n. E
ssentially, \n$newt\n calls \ngo run\n which runs the compiled binary directly without producing an executable. Don't forget to reload the updated bash profile by typing \nsource ~/.bash_profile\n at the prompt! )\n\n\n $ newt version\n Newt version: 1.0\n $ newt -h\n Newt allows you to create your own embedded application based on the Mynewt \n operating system. Newt provides both build and package management in a single \n tool, which allows you to compose an embedded application, and set of \n projects, and then build the necessary artifacts from those projects. For more \n information on the Mynewt operating system, please visit \n https://mynewt.apache.org/. \n\n Please use the newt help command, and specify the name of the command you want \n help for, for help on how to use a specific command\n\n Usage:\n newt [flags]\n newt [command]\n\n Examples:\n newt\n
newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\n Available Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Execu
tes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\n Flags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing commands\n\n Use \nnewt [command] --help\n for more information about a comma\n\n\n\n\n\n\n\n5. Updating the Newt tool\n\n\n\n\nYou will update the newt tool in the same place as you initially installed the newt tool.\n\n\nStart by updating the git repository of the new
t tool (you can change to a different branch using git checkout [branch] if you need to)\n\n\nThen update each of the tools newt, newtmgr and newtvm as needed\n\n\n\n\n $ cd $GOPATH/src/mynewt.apache.org/newt\n $ git pull\n $ cd newt\n $ go install\n $ cd ../newtmgr\n $ go install\n $ cd ../newtvm\n $ go install\n $ ls \n$GOPATH\n/bin/\n newt newtmgr newtvm\n\n\n\n\n\nThat should have updated your newt, newtmgr and newtvm to the latest versions based on the git repository you used.",
+ "text": "Install newt tool on Linux\n\n\n\n\nGetting your Linux box Ready\n\n\nIf you want to build the \nnewt\n tool from its source code, follow the following steps:\n\n\n1. Install git, libcurl\n\n\n $ sudo apt-get install git \n $ sudo apt-get install libcurl4-gnutls-dev \n\n\n\n\n\nNOTE:\n On 64-bit host, you may also need to install gcc-multilib, if you encounter compilation errors related to 'sys/cdefs.h'\n\n\n\n\n2. Install Go, the programming language\n\n\n\n\n\n\nGo language environment dictates a directory structure. Known in Go parlance as a workspace, it must contain three sibling directories with the directory names src, pkg and bin, as explained below. \n\n\n\n\n\n\nsrc contains Go source files organized into packages (one package per directory),\n\n\n\n\n\n\npkg contains package objects, and\n\n\n\n\n\n\nbin contains executable commands.\n\n\n\n\n\n\nThe GOPATH environment variable specifies the location of your workspace. To setup this work
space environment, create a 'dev' directory and then a 'go' directory under it. Set the GOPATH environment variable to this directory where you will soon clone the \nnewt\n tool repository.\n\n\n\n\n\n\n $ cd $HOME\n $ mkdir -p dev/go \n $ cd dev/go\n $ export GOPATH=`pwd`\n\n\n\n\n\n(Note that you need to add export statements to ~/.bash_profile to export variables permanently. Don't forget to source the file for the change to go into effect.)\n\n\n\n\n $ vi ~/.bash_profile\n $ source ~/.bash_profile\n\n\n\n\n\n\n\n\n\n\n\nNext, install Go. When installed, Go offers you as a developer a language environment (to compile Go code), construct Go packages (to assemble Go packages) and import Go code (from github). In the next step, you will use the Go commands to import \nnewt\n repo into your local Go environment.\n\n\nNote\n: The Newt tool requires Go version 1.7 or later. Currently, the latest Go version that Ubuntu installs is 1.6. You can
run \napt-get install golang-1.7-go\n to install version 1.7. You can also download version 1.7 from \nhttps://golang.org/dl/\n. \n\n\n\n\n\n\n$sudo apt-get install golang-1.7-go\nReading package lists... Done\n ...\nUnpacking golang-1.7-go (1.7.1-2ubuntu1) ...\nSetting up golang-1.7-go (1.7.1-2ubuntu1) ...\n$\n$sudo ln -s /usr/lib/go-1.7/bin/go /usr/bin/go\n$go version\ngo version go1.7.1 linux/amd64\n\n\n\n\n\n \n\n\n3. Create local repository\n\n\n\n\nUse Go commands to copy the directory (currently the ASF incubator directory). Be patient as it may take a minute or two. Check the directories installed.\n\n\n\n\n $ go get mynewt.apache.org/newt/...\n\n\n\n\n\n\n\n\n\nCheck that newt.go is in place.\n\n\n\n\n $ ls $GOPATH/src/mynewt.apache.org/newt\n DISCLAIMER NOTICE newt newtvm viper\n LICENSE README.md newtmgr util yaml\n\n\n\n\n\n\n\n4. Build the Newt tool\n\n\n\n\nUse Go to run the newt.go program to build
the \nnewt\n tool. The command \ngo install\n compiles and writes the resulting executable to an output file named \nnewt\n, which is then installed, along with its dependencies, in $GOPATH/bin. If you get errors it is likely because of path resolution issues. Try \ngo build\n followed by \ngo install\n in that case.\n\n\n\n\n $ cd $GOPATH/src/mynewt.apache.org/newt/newt\n $ go install\n $ ls \n$GOPATH\n/bin/\n newt newtmgr newtvm\n\n\n\n\n\n\n\n\n\nAt this point, you can try using \nnewt\n. For example, check for the version number by typing 'newt version'. See all the possible commands available to a user of newt by typing 'newt -h'.\n\n\n\n\n(Note: If you are going to be modifying the \nnewt\n often and going to be compile the program every time you call it, you will want to store the command in a variable in your .bash_profile. So type in \nexport newt=\"go run $GOPATH/mynewt.apache.org/newt/newt/newt.go\"\n in your .bash_profile and execute it by c
alling \n$newt\n at the prompt instead of \nnewt\n. Essentially, \n$newt\n calls \ngo run\n which runs the compiled binary directly without producing an executable. Don't forget to reload the updated bash profile by typing \nsource ~/.bash_profile\n at the prompt! )\n\n\n $ newt version\n Newt version: 1.0\n $ newt -h\n Newt allows you to create your own embedded application based on the Mynewt \n operating system. Newt provides both build and package management in a single \n tool, which allows you to compose an embedded application, and set of \n projects, and then build the necessary artifacts from those projects. For more \n information on the Mynewt operating system, please visit \n https://mynewt.apache.org/. \n\n Please use the newt help command, and specify the name of the command you want \n help for, for help on how to use a specific command\n\n Usage:\n newt [flags]\n ne
wt [command]\n\n Examples:\n newt\n newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\n Available Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, confi
gure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\n Flags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing commands\n\n Use \nnewt [command] --help\n for more information about a comma\n\n\n\n\n\n\n\n5. Updating the Newt tool\n\n\n\n\nYou will update the newt tool in the same place as you initially installed the newt tool.
\n\n\nStart by updating the git repository of the newt tool (you can change to a different branch using git checkout [branch] if you need to)\n\n\nThen update each of the tools newt, newtmgr and newtvm as needed\n\n\n\n\n $ cd $GOPATH/src/mynewt.apache.org/newt\n $ git pull\n $ cd newt\n $ go install\n $ cd ../newtmgr\n $ go install\n $ cd ../newtvm\n $ go install\n $ ls \n$GOPATH\n/bin/\n newt newtmgr newtvm\n\n\n\n\n\nThat should have updated your newt, newtmgr and newtvm to the latest versions based on the git repository you used.",
"title": "Install Newt on Linux"
},
{
@@ -297,7 +297,7 @@
},
{
"location": "/newt/install/newt_linux/#2-install-go-the-programming-language",
- "text": "Go language environment dictates a directory structure. Known in Go parlance as a workspace, it must contain three sibling directories with the directory names src, pkg and bin, as explained below. src contains Go source files organized into packages (one package per directory), pkg contains package objects, and bin contains executable commands. The GOPATH environment variable specifies the location of your workspace. To setup this workspace environment, create a 'dev' directory and then a 'go' directory under it. Set the GOPATH environment variable to this directory where you will soon clone the newt tool repository. $ cd $HOME\n $ mkdir -p dev/go \n $ cd dev/go\n $ export GOPATH=`pwd` (Note that you need to add export statements to ~/.bash_profile to export variables permanently. Don't forget to source the file for the change to go into effect.) $ vi ~/.bash_profile\n $ source ~/.bash_profile
Next, install Go. When installed, Go offers you as a developer a language environment (to compile Go code), construct Go packages (to assemble Go packages) and import Go code (from github). In the next step, you will use the Go commands to import newt repo into your local Go environment. Note : The Newt tool requires Go version 1.6 or later. Depending on the Ubuntu version you have, the following may install an earlier version. In that case, download the latest package of Go 1.6 from https://golang.org/dl/ . You can search for more detailed instructions such as installing Go 1.6 on Ubuntu 14.04 which can be found at https://www.digitalocean.com/community/tutorials/how-to-install-go-1-6-on-ubuntu-14-04 . $ sudo apt-get install golang",
+ "text": "Go language environment dictates a directory structure. Known in Go parlance as a workspace, it must contain three sibling directories with the directory names src, pkg and bin, as explained below. src contains Go source files organized into packages (one package per directory), pkg contains package objects, and bin contains executable commands. The GOPATH environment variable specifies the location of your workspace. To setup this workspace environment, create a 'dev' directory and then a 'go' directory under it. Set the GOPATH environment variable to this directory where you will soon clone the newt tool repository. $ cd $HOME\n $ mkdir -p dev/go \n $ cd dev/go\n $ export GOPATH=`pwd` (Note that you need to add export statements to ~/.bash_profile to export variables permanently. Don't forget to source the file for the change to go into effect.) $ vi ~/.bash_profile\n $ source ~/.bash_profile
Next, install Go. When installed, Go offers you as a developer a language environment (to compile Go code), construct Go packages (to assemble Go packages) and import Go code (from github). In the next step, you will use the Go commands to import newt repo into your local Go environment. Note : The Newt tool requires Go version 1.7 or later. Currently, the latest Go version that Ubuntu installs is 1.6. You can run apt-get install golang-1.7-go to install version 1.7. You can also download version 1.7 from https://golang.org/dl/ . $sudo apt-get install golang-1.7-go\nReading package lists... Done\n ...\nUnpacking golang-1.7-go (1.7.1-2ubuntu1) ...\nSetting up golang-1.7-go (1.7.1-2ubuntu1) ...\n$\n$sudo ln -s /usr/lib/go-1.7/bin/go /usr/bin/go\n$go version\ngo version go1.7.1 linux/amd64",
"title": "2. Install Go, the programming language"
},
{
@@ -357,7 +357,7 @@
},
{
"location": "/os/get_started/project_create/",
- "text": "Create Your First Mynewt Project\n\n\nThis page shows how to create a Mynewt Project using the \nnewt\n command-line tool.\n\n\n\n\nPre-Requisites\n\n\n\n\nNewt:\n\n\nIf you have taken the Docker route, you have already installed Newt.\n\n\nIf you have taken the native install route, you have to ensure that you have installed the Newt tool following the instructions for \nMac\n or \nLinux\n as appropriate, and that the \nnewt\n command is in your system path. \n\n\n\n\n\n\nYou must have Internet connectivity to fetch remote Mynewt components.\n\n\nYou must \ninstall the compiler tools\n to \nsupport native compiling to build the project this tutorial creates. \n\n\n\n\n\n\nNewt New\n\n\nChoose a project name. For this tutorial we will call this project \nmyproj\n.\nEnter the \nnewt new myproj\n command. \n\n\n$ newt new myproj\nDownloading project skeleton from apache/incubator-mynewt-blinky...\nInstalling skeleton in myproj...\nProject myproj successfully crea
ted.\n\n\n\n\n\n\n\nNewt populates this new project with a base skeleton of a new Apache Mynewt \nproject. It has the following structure. \n\n\nNote\n: If you do not have \ntree\n, install it by running \nbrew install tree\n.\n\n\n$ cd myproj\n$ tree \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\u00a0\u00a0 \u2514\u2500\u2500 blinky\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 pkg.yml\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 src\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 main.c\n\u251c\u2500\u2500 project.yml\n\u2514\u2500\u2500 targets\n \u251c\u2500\u2500 my_blinky_sim\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 pkg.yml\n \u2502\u00a0\u00a0 \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, 11 files\n\n\n\n\n\n\n\nThe Newt tool has installed the base files for a
project comprising the following:\n\n\n\n\nThe file \nproject.yml\n contains the repository list that the project uses to fetch\nits packages. Your project is a collection of repositories. In this case, the project just\ncomprises the core mynewt repository. Later you will add more repositories\nto include other mynewt components.\n\n\nThe file \napps/blinky/pkg.yml\n contains the description of your application\nand its package dependencies.\n\n\nA \ntarget\n directory containing \nmy_blinky_sim\n, a target descriptor used to\nbuild a version of myproj. Use \nnewt target show\n to see available build \ntargets.\n\n\nA non-buildable target called \nunittest\n. This is used internally by \nnewt\n and is not a formal build target.\n\n\n\n\nNOTE:\n The actual code and package files are not installed \n(except the template for \nmain.c\n). See the next step for installing the packages.\n\n\nNOTE:\n By default newt uses the code in the master branch. This is the latest stable\ncode
for newt. If you need to use a different branch, you can set this in the project.yml\nfile. \n\n\nrepository.apache-mynewt-core:\n type: github\n vers: 1-latest\n user: apache\n repo: incubator-mynewt-core\n\n\n\n\n\nChanging to 1-dev will put you on the develop branch. \nThe Develop Branch may not be stable and you may encounter bugs or other problems.\n\n\n\n\nNewt Install\n\n\nOnce you've switched into your new project's directory, the next step is to fetch\nany dependencies this project has. By default, all Newt projects rely on a\nsingle remote repository, apache-mynewt-core. The \nnewt install\n command will\nfetch this repository.\n\n\n$ newt install\napache-mynewt-core\n\n\n\n\n\nNOTE:\n \napache-mynewt-core\n may take a while to download. To see progress,\nuse the \n-v\n (verbose) option to install. \n\n\n\n\nOnce \nnewt install\n has successfully finished, the contents of \napache-mynewt-core\n will have been downloaded into your local directory. You can v
iew them by issuing the following commands in the base directory of the new project. The actual output will depend on what is in the latest 'master' branch you have pulled from.\n\n\n$ tree -L 2 repos/apache-mynewt-core/\n\nrepos/apache-mynewt-core/\n\u251c\u2500\u2500 CODING_STANDARDS.md\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 RELEASE_NOTES.md\n\u251c\u2500\u2500 apps\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 blecent\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 blehci\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bleprph\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bleprph_oic\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 blesplit\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bletest\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bletiny\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bleuart\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 boot\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fat2native\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 ffs2native\n\u25
02\u00a0\u00a0 \u251c\u2500\u2500 ocf_sample\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 slinky\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 slinky_oic\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 spitest\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 splitty\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 testbench\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 timtest\n\u251c\u2500\u2500 boot\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 boot_serial\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bootutil\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 split\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 split_app\n\u251c\u2500\u2500 compiler\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 arm-none-eabi-m0\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 arm-none-eabi-m4\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 gdbmacros\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mips\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 sim\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 sim-mips\n\u251c\u2500\u2500 crypto\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mbedtls\n\u25
02\u00a0\u00a0 \u2514\u2500\u2500 tinycrypt\n\u251c\u2500\u2500 docs\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 doxygen.xml\n\u251c\u2500\u2500 encoding\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 base64\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 cborattr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 json\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 tinycbor\n\u251c\u2500\u2500 fs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 disk\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fatfs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fcb\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fs\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 nffs\n\u251c\u2500\u2500 hw\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bsp\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 cmsis-core\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 drivers\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 hal\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mcu\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 scripts\n\u251c\u2500\u2500 kernel\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 os\n\u251c\u2500\u2500 libc\n\u2502\u00a0\u00a0 \u2514\u250
0\u2500 baselibc\n\u251c\u2500\u2500 mgmt\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 imgmgr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mgmt\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 newtmgr\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 oicmgr\n\u251c\u2500\u2500 net\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 ip\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 nimble\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 oic\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 wifi\n\u251c\u2500\u2500 project.yml\n\u251c\u2500\u2500 repository.yml\n\u251c\u2500\u2500 sys\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 config\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 console\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 coredump\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 defs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 flash_map\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 id\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 log\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mfg\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 reboot\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 shell\n\u2502\u00a0\u00a0 \u251c\u2
500\u2500 stats\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 sysinit\n\u251c\u2500\u2500 targets\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 unittest\n\u251c\u2500\u2500 test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 crash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 flash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 runtest\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 testutil\n\u251c\u2500\u2500 time\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 datetime\n\u2514\u2500\u2500 util\n \u251c\u2500\u2500 cbmem\n \u251c\u2500\u2500 crc\n \u2514\u2500\u2500 mem\n\n94 directories, 9 files\n\n\n\n\n\nAs you can see, the core of the Apache Mynewt operating system has been brought \ninto your local directory. \n\n\n\n\nTest the project's packages\n\n\nYou have already built your first basic project. You can ask Newt to execute the unit tests in a package. For example, to test the \nlibs/os\n package in the \napache-mynewt-core\n repo, call newt as shown below.\n\n\n$ newt test @apache-mynewt-core/sys/config\nTe
sting package @apache-mynewt-core/sys/config/test-fcb\nCompiling bootutil_misc.c\nCompiling image_ec.c\nCompiling image_rsa.c\nCompiling image_validate.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nTesting package @apache-mynewt-core/sys/config/test-nffs\nCompiling repos/apache-mynewt-core/encoding/base64/src/hex.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_cli.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_dirent.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_mkdir.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_mount.c\nCompiling repos/apache-mynewt-core/encoding/base64/src/base64.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_file.c\nCompiling repos/apache-mynewt-core/fs/disk/src/disk.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_nmgr.c\nCompiling repos/apac
he-mynewt-core/fs/fs/src/fsutil.c\nCompiling repos/apache-mynewt-core/fs/nffs/src/nffs.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nPassed tests: [sys/config/test-fcb sys/config/test-nffs]\nAll tests passed\n\n\n\n\n\nNOTE:\n If you've installed the latest gcc using homebrew on your Mac, you will likely be running gcc-6. Make sure you have adjusted the compiler.yml configuration to reflect that as noted in \nNative Install Option\n. You can choose to downgrade to gcc-5 in order to use the default gcc compiler configuration for MyNewt.\n\n\nNOTE:\n If you are running the standard gcc for 64-bit machines, it does not support 32-bit. In that case you will see compilation errors. You need to install multiboot gcc (e.g. gcc-multilib if you running on a 64-bit Ubuntu).\n\n\n$ brew uni
nstall gcc-6\n$ brew link gcc-5\n\n\n\n\n\n\n\nTo test all the packages in a project, specify \nall\n instead of the package name.\n\n\n$ newt test all\nTesting package @apache-mynewt-core/boot/boot_serial/test\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/boot_test.c\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/testcases/boot_serial_setup.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/boot_boot_serial_test/app/boot/boot_serial/test/boot_boot_serial_test.elf\n\n...lots of compiling and testing...\n\nLinking ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nPassed tests: [boot/boot_serial/test boot/bootutil/test crypto/mbedtls/test encoding/base64/test encoding/cborattr/test encoding/json/test fs/fcb/test fs/nffs/test kernel/os/test net/ip/mn_socket/test net/nimble/host/test net/oic/test sys/co
nfig/test-fcb sys/config/test-nffs sys/flash_map/test sys/log/full/test util/cbmem/test]\nAll tests passed\n\n\n\n\n\n\n\nBuild the Project\n\n\nTo build and run your new application, simply issue the following command:\n\n\n$ newt build my_blinky_sim \nBuilding target targets/my_blinky_sim\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_common.c\nCompiling repos/apache-mynewt-core/hw/drivers/uart/src/uart.c\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c\nCompiling repos/apache-mynewt-core/hw/bsp/native/src/hal_bsp.c\nCompiling repos/apache-mynewt-core/hw/drivers/uart/uart_hal/src/uart_hal.c\nCompiling apps/blinky/src/main.c\n\n ...\n\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nTarget successfully built: targets/my_blinky_sim\n\n\n\n\n\n\n\nRun the Project\n\n\nYou can run the simulated version of your project and see the simulated LED\nblink. If you are using newt
docker, use \nnewt run\n to run the simulated binary.\n\n\n$ newt run my_blinky_sim\nNo download script for BSP hw/bsp/native\nDebugging /workspace/bin/my_blinky_sim/apps/blinky/blinky.elf\n\nsnip\n\nReading symbols from /bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf...done.\n(gdb)\n\n\n\n\n\nType \nr\n at the \n(gdb)\n prompt to run the project. You will see an output indicating that the hal_gpio pin is toggling between 1 and 0 in a simulated blink.\n\n\nIf you natively install the toolchain, you can either use \nnewt run\n or call the binary directly. Generally, \nnewt run\n is the expected way to call things.\n\n\n$ ./bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nhal_gpio set pin 1 to 0\n\n\n\n\n\n\n\nComplete\n\n\nCongratulations, you have created your first project! The blinky application\nis not terribly exciting when it is run in the simulator, as there is no LED to\nblink. Apache Mynewt has a lot more functionality than just running simulated\napplications
. It provides all the features you'll need to cross-compile your\napplication, run it on real hardware and develop a full featured application.\n\n\nIf you're interested in learning more, a good next step is to dig in to one of\nthe \ntutorials\n and get a Mynewt project running on real hardware.\n\n\nHappy Hacking!",
+ "text": "Create Your First Mynewt Project\n\n\nThis page shows how to create a Mynewt Project using the \nnewt\n command-line tool.\n\n\n\n\nPre-Requisites\n\n\n\n\nNewt:\n\n\nIf you have taken the Docker route, you have already installed Newt.\n\n\nIf you have taken the native install route, you have to ensure that you have installed the Newt tool following the instructions for \nMac\n or \nLinux\n as appropriate, and that the \nnewt\n command is in your system path. \n\n\n\n\n\n\nYou must have Internet connectivity to fetch remote Mynewt components.\n\n\nYou must \ninstall the compiler tools\n to \nsupport native compiling to build the project this tutorial creates. \n\n\n\n\n\n\nNewt New\n\n\nChoose a project name. For this tutorial we will call this project \nmyproj\n.\nEnter the \nnewt new myproj\n command. \n\n\n$ newt new myproj\nDownloading project skeleton from apache/incubator-mynewt-blinky...\nInstalling skeleton in myproj...\nProject myproj successfully crea
ted.\n\n\n\n\n\n\n\nNewt populates this new project with a base skeleton of a new Apache Mynewt \nproject. It has the following structure. \n\n\nNote\n: If you do not have \ntree\n, install it by running \nbrew install tree\n.\n\n\n$ cd myproj\n$ tree \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\u00a0\u00a0 \u2514\u2500\u2500 blinky\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 pkg.yml\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 src\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 main.c\n\u251c\u2500\u2500 project.yml\n\u2514\u2500\u2500 targets\n \u251c\u2500\u2500 my_blinky_sim\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 pkg.yml\n \u2502\u00a0\u00a0 \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, 11 files\n\n\n\n\n\n\n\nThe Newt tool has installed the base files for a
project comprising the following:\n\n\n\n\nThe file \nproject.yml\n contains the repository list that the project uses to fetch\nits packages. Your project is a collection of repositories. In this case, the project just\ncomprises the core mynewt repository. Later you will add more repositories\nto include other mynewt components.\n\n\nThe file \napps/blinky/pkg.yml\n contains the description of your application\nand its package dependencies.\n\n\nA \ntarget\n directory containing \nmy_blinky_sim\n, a target descriptor used to\nbuild a version of myproj. Use \nnewt target show\n to see available build \ntargets.\n\n\nA non-buildable target called \nunittest\n. This is used internally by \nnewt\n and is not a formal build target.\n\n\n\n\nNOTE:\n The actual code and package files are not installed \n(except the template for \nmain.c\n). See the next step for installing the packages.\n\n\nNOTE:\n By default newt uses the code in the master branch. This is the latest stable\ncode
for newt. If you need to use a different branch, you can set this in the project.yml\nfile. \n\n\nrepository.apache-mynewt-core:\n type: github\n vers: 1-latest\n user: apache\n repo: incubator-mynewt-core\n\n\n\n\n\nChanging to 1-dev will put you on the develop branch. \nThe Develop Branch may not be stable and you may encounter bugs or other problems.\n\n\n\n\nNewt Install\n\n\nOnce you've switched into your new project's directory, the next step is to fetch\nany dependencies this project has. By default, all Newt projects rely on a\nsingle remote repository, apache-mynewt-core. The \nnewt install\n command will\nfetch this repository.\n\n\n$ newt install\napache-mynewt-core\n\n\n\n\n\nNOTE:\n \napache-mynewt-core\n may take a while to download. To see progress,\nuse the \n-v\n (verbose) option to install. \n\n\n\n\nOnce \nnewt install\n has successfully finished, the contents of \napache-mynewt-core\n will have been downloaded into your local directory. You can v
iew them by issuing the following commands in the base directory of the new project. The actual output will depend on what is in the latest 'master' branch you have pulled from.\n\n\n$ tree -L 2 repos/apache-mynewt-core/\n\nrepos/apache-mynewt-core/\n\u251c\u2500\u2500 CODING_STANDARDS.md\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 RELEASE_NOTES.md\n\u251c\u2500\u2500 apps\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 blecent\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 blehci\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bleprph\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bleprph_oic\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 blesplit\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bletest\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bletiny\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bleuart\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 boot\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fat2native\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 ffs2native\n\u25
02\u00a0\u00a0 \u251c\u2500\u2500 ocf_sample\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 slinky\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 slinky_oic\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 spitest\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 splitty\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 testbench\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 timtest\n\u251c\u2500\u2500 boot\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 boot_serial\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bootutil\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 split\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 split_app\n\u251c\u2500\u2500 compiler\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 arm-none-eabi-m0\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 arm-none-eabi-m4\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 gdbmacros\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mips\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 sim\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 sim-mips\n\u251c\u2500\u2500 crypto\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mbedtls\n\u25
02\u00a0\u00a0 \u2514\u2500\u2500 tinycrypt\n\u251c\u2500\u2500 docs\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 doxygen.xml\n\u251c\u2500\u2500 encoding\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 base64\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 cborattr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 json\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 tinycbor\n\u251c\u2500\u2500 fs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 disk\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fatfs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fcb\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fs\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 nffs\n\u251c\u2500\u2500 hw\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bsp\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 cmsis-core\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 drivers\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 hal\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mcu\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 scripts\n\u251c\u2500\u2500 kernel\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 os\n\u251c\u2500\u2500 libc\n\u2502\u00a0\u00a0 \u2514\u250
0\u2500 baselibc\n\u251c\u2500\u2500 mgmt\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 imgmgr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mgmt\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 newtmgr\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 oicmgr\n\u251c\u2500\u2500 net\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 ip\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 nimble\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 oic\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 wifi\n\u251c\u2500\u2500 project.yml\n\u251c\u2500\u2500 repository.yml\n\u251c\u2500\u2500 sys\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 config\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 console\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 coredump\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 defs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 flash_map\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 id\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 log\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mfg\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 reboot\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 shell\n\u2502\u00a0\u00a0 \u251c\u2
500\u2500 stats\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 sysinit\n\u251c\u2500\u2500 targets\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 unittest\n\u251c\u2500\u2500 test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 crash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 flash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 runtest\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 testutil\n\u251c\u2500\u2500 time\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 datetime\n\u2514\u2500\u2500 util\n \u251c\u2500\u2500 cbmem\n \u251c\u2500\u2500 crc\n \u2514\u2500\u2500 mem\n\n94 directories, 9 files\n\n\n\n\n\nAs you can see, the core of the Apache Mynewt operating system has been brought \ninto your local directory. \n\n\n\n\nTest the project's packages\n\n\nYou have already built your first basic project. You can ask Newt to execute the unit tests in a package. For example, to test the \nsys/config\n package in the \napache-mynewt-core\n repo, call newt as shown below.\n\n\n$ newt test @apache-mynewt-core/sys/config\
nTesting package @apache-mynewt-core/sys/config/test-fcb\nCompiling bootutil_misc.c\nCompiling image_ec.c\nCompiling image_rsa.c\nCompiling image_validate.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nTesting package @apache-mynewt-core/sys/config/test-nffs\nCompiling repos/apache-mynewt-core/encoding/base64/src/hex.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_cli.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_dirent.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_mkdir.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_mount.c\nCompiling repos/apache-mynewt-core/encoding/base64/src/base64.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_file.c\nCompiling repos/apache-mynewt-core/fs/disk/src/disk.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_nmgr.c\nCompiling repos/a
pache-mynewt-core/fs/fs/src/fsutil.c\nCompiling repos/apache-mynewt-core/fs/nffs/src/nffs.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nPassed tests: [sys/config/test-fcb sys/config/test-nffs]\nAll tests passed\n\n\n\n\n\nNOTE:\n If you've installed the latest gcc using homebrew on your Mac, you will likely be running gcc-6. Make sure you have adjusted the compiler.yml configuration to reflect that as noted in \nNative Install Option\n. You can choose to downgrade to gcc-5 in order to use the default gcc compiler configuration for MyNewt.\n\n\nNOTE:\n If you are running the standard gcc for 64-bit machines, it does not support 32-bit. In that case you will see compilation errors. You need to install multiboot gcc (e.g. gcc-multilib if you running on a 64-bit Ubuntu).\n\n\n$ brew
uninstall gcc-6\n$ brew link gcc-5\n\n\n\n\n\n\n\nTo test all the packages in a project, specify \nall\n instead of the package name.\n\n\n$ newt test all\nTesting package @apache-mynewt-core/boot/boot_serial/test\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/boot_test.c\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/testcases/boot_serial_setup.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/boot_boot_serial_test/app/boot/boot_serial/test/boot_boot_serial_test.elf\n\n...lots of compiling and testing...\n\nLinking ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nPassed tests: [boot/boot_serial/test boot/bootutil/test crypto/mbedtls/test encoding/base64/test encoding/cborattr/test encoding/json/test fs/fcb/test fs/nffs/test kernel/os/test net/ip/mn_socket/test net/nimble/host/test net/oic/test sys
/config/test-fcb sys/config/test-nffs sys/flash_map/test sys/log/full/test util/cbmem/test]\nAll tests passed\n\n\n\n\n\n\n\nBuild the Project\n\n\nTo build and run your new application, simply issue the following command:\n\n\n$ newt build my_blinky_sim \nBuilding target targets/my_blinky_sim\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_common.c\nCompiling repos/apache-mynewt-core/hw/drivers/uart/src/uart.c\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c\nCompiling repos/apache-mynewt-core/hw/bsp/native/src/hal_bsp.c\nCompiling repos/apache-mynewt-core/hw/drivers/uart/uart_hal/src/uart_hal.c\nCompiling apps/blinky/src/main.c\n\n ...\n\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nTarget successfully built: targets/my_blinky_sim\n\n\n\n\n\n\n\nRun the Project\n\n\nYou can run the simulated version of your project and see the simulated LED\nblink. If you are using n
ewt docker, use \nnewt run\n to run the simulated binary.\n\n\n$ newt run my_blinky_sim\nLoading app image into slot 1\n ...\nDebugging ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\n ...\nReading symbols from /bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf...done.\n(gdb)\n\n\n\n\n\nType \nr\n at the \n(gdb)\n prompt to run the project. You will see an output indicating that the hal_gpio pin is toggling between 1 and 0 in a simulated blink.\n\n\nIf you natively install the toolchain, you can either use \nnewt run\n or call the binary directly. Generally, \nnewt run\n is the expected way to call things.\n\n\n$ ./bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nhal_gpio set pin 1 to 0\n\n\n\n\n\n\n\nComplete\n\n\nCongratulations, you have created your first project! The blinky application\nis not terribly exciting when it is run in the simulator, as there is no LED to\nblink. Apache Mynewt has a lot more functionality than just running simulated
\napplications. It provides all the features you'll need to cross-compile your\napplication, run it on real hardware and develop a full featured application.\n\n\nIf you're interested in learning more, a good next step is to dig in to one of\nthe \ntutorials\n and get a Mynewt project running on real hardware.\n\n\nHappy Hacking!",
"title": "Create Your First Project"
},
{
@@ -382,7 +382,7 @@
},
{
"location": "/os/get_started/project_create/#test-the-projects-packages",
- "text": "You have already built your first basic project. You can ask Newt to execute the unit tests in a package. For example, to test the libs/os package in the apache-mynewt-core repo, call newt as shown below. $ newt test @apache-mynewt-core/sys/config\nTesting package @apache-mynewt-core/sys/config/test-fcb\nCompiling bootutil_misc.c\nCompiling image_ec.c\nCompiling image_rsa.c\nCompiling image_validate.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nTesting package @apache-mynewt-core/sys/config/test-nffs\nCompiling repos/apache-mynewt-core/encoding/base64/src/hex.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_cli.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_dirent.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_mkdir.c\nCompiling repos/apache-mynewt-co
re/fs/fs/src/fs_mount.c\nCompiling repos/apache-mynewt-core/encoding/base64/src/base64.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_file.c\nCompiling repos/apache-mynewt-core/fs/disk/src/disk.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_nmgr.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fsutil.c\nCompiling repos/apache-mynewt-core/fs/nffs/src/nffs.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nPassed tests: [sys/config/test-fcb sys/config/test-nffs]\nAll tests passed NOTE: If you've installed the latest gcc using homebrew on your Mac, you will likely be running gcc-6. Make sure you have adjusted the compiler.yml configuration to reflect that as noted in Native Install Option . You can choose to downgrade to gcc-5 in order to use the default gcc compiler configurat
ion for MyNewt. NOTE: If you are running the standard gcc for 64-bit machines, it does not support 32-bit. In that case you will see compilation errors. You need to install multiboot gcc (e.g. gcc-multilib if you running on a 64-bit Ubuntu). $ brew uninstall gcc-6\n$ brew link gcc-5 To test all the packages in a project, specify all instead of the package name. $ newt test all\nTesting package @apache-mynewt-core/boot/boot_serial/test\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/boot_test.c\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/testcases/boot_serial_setup.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/boot_boot_serial_test/app/boot/boot_serial/test/boot_boot_serial_test.elf\n\n...lots of compiling and testing...\n\nLinking ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nPasse
d tests: [boot/boot_serial/test boot/bootutil/test crypto/mbedtls/test encoding/base64/test encoding/cborattr/test encoding/json/test fs/fcb/test fs/nffs/test kernel/os/test net/ip/mn_socket/test net/nimble/host/test net/oic/test sys/config/test-fcb sys/config/test-nffs sys/flash_map/test sys/log/full/test util/cbmem/test]\nAll tests passed",
+ "text": "You have already built your first basic project. You can ask Newt to execute the unit tests in a package. For example, to test the sys/config package in the apache-mynewt-core repo, call newt as shown below. $ newt test @apache-mynewt-core/sys/config\nTesting package @apache-mynewt-core/sys/config/test-fcb\nCompiling bootutil_misc.c\nCompiling image_ec.c\nCompiling image_rsa.c\nCompiling image_validate.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nTesting package @apache-mynewt-core/sys/config/test-nffs\nCompiling repos/apache-mynewt-core/encoding/base64/src/hex.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_cli.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_dirent.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_mkdir.c\nCompiling repos/apache-mynewt
-core/fs/fs/src/fs_mount.c\nCompiling repos/apache-mynewt-core/encoding/base64/src/base64.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_file.c\nCompiling repos/apache-mynewt-core/fs/disk/src/disk.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_nmgr.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fsutil.c\nCompiling repos/apache-mynewt-core/fs/nffs/src/nffs.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nPassed tests: [sys/config/test-fcb sys/config/test-nffs]\nAll tests passed NOTE: If you've installed the latest gcc using homebrew on your Mac, you will likely be running gcc-6. Make sure you have adjusted the compiler.yml configuration to reflect that as noted in Native Install Option . You can choose to downgrade to gcc-5 in order to use the default gcc compiler configu
ration for MyNewt. NOTE: If you are running the standard gcc for 64-bit machines, it does not support 32-bit. In that case you will see compilation errors. You need to install multiboot gcc (e.g. gcc-multilib if you running on a 64-bit Ubuntu). $ brew uninstall gcc-6\n$ brew link gcc-5 To test all the packages in a project, specify all instead of the package name. $ newt test all\nTesting package @apache-mynewt-core/boot/boot_serial/test\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/boot_test.c\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/testcases/boot_serial_setup.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/boot_boot_serial_test/app/boot/boot_serial/test/boot_boot_serial_test.elf\n\n...lots of compiling and testing...\n\nLinking ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nPa
ssed tests: [boot/boot_serial/test boot/bootutil/test crypto/mbedtls/test encoding/base64/test encoding/cborattr/test encoding/json/test fs/fcb/test fs/nffs/test kernel/os/test net/ip/mn_socket/test net/nimble/host/test net/oic/test sys/config/test-fcb sys/config/test-nffs sys/flash_map/test sys/log/full/test util/cbmem/test]\nAll tests passed",
"title": "Test the project's packages"
},
{
@@ -392,7 +392,7 @@
},
{
"location": "/os/get_started/project_create/#run-the-project",
- "text": "You can run the simulated version of your project and see the simulated LED\nblink. If you are using newt docker, use newt run to run the simulated binary. $ newt run my_blinky_sim\nNo download script for BSP hw/bsp/native\nDebugging /workspace/bin/my_blinky_sim/apps/blinky/blinky.elf snip \nReading symbols from /bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf...done.\n(gdb) Type r at the (gdb) prompt to run the project. You will see an output indicating that the hal_gpio pin is toggling between 1 and 0 in a simulated blink. If you natively install the toolchain, you can either use newt run or call the binary directly. Generally, newt run is the expected way to call things. $ ./bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nhal_gpio set pin 1 to 0",
+ "text": "You can run the simulated version of your project and see the simulated LED\nblink. If you are using newt docker, use newt run to run the simulated binary. $ newt run my_blinky_sim\nLoading app image into slot 1\n ...\nDebugging ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\n ...\nReading symbols from /bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf...done.\n(gdb) Type r at the (gdb) prompt to run the project. You will see an output indicating that the hal_gpio pin is toggling between 1 and 0 in a simulated blink. If you natively install the toolchain, you can either use newt run or call the binary directly. Generally, newt run is the expected way to call things. $ ./bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nhal_gpio set pin 1 to 0",
"title": "Run the Project"
},
{
@@ -432,7 +432,7 @@
},
{
"location": "/os/get_started/vocabulary/",
- "text": "Concepts\n\n\nThis page is meant to introduce you to some of the concepts inherent to \nthe Apache Mynewt Operating System, and \nNewt\n the tool that stitches a \nproject built on Apache Mynewt together.\n\n\nProject\n\n\nThe project is the base directory of your embedded software tree. It is a \nworkspace that contains a logical collection of source code, for one or \nmore of your applications. A project consists of the following items:\n\n\n\n\nProject Definition: defines project level dependencies, and parameters\n (located in \nproject.yml\n)\n\n\nPackages\n\n\n\n\nPackages\n are described in detail in the section below. \n\n\nHere is an example project definition file from the default Apache Mynewt \nproject: \n\n\n$ more project.yml \n\nsnip\n\nproject.name: \nmy_project\n\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#\nrepositor
y.apache-mynewt-core:\n type: github\n vers: 1-latest\n user: apache\n repo: incubator-mynewt-core\n$ \n\n\n\n\n\nA couple of things to note in the project definition:\n\n\n\n\n\n\nproject.repositories\n: Defines the remote repositories that this project\nrelies upon.\n\n\n\n\n\n\nrepository.apache-mynewt-core\n: Defines the repository information for \nthe \napache-mynewt-core\n repository.\n\n\n\n\n\n\nvers=1-latest\n: Defines the repository version. This string will use the \nlatest code in the 'Master' github branch. To use the latest version in the \ndevelop branch, just change it to \nvers=1-dev\n\n\n\n\n\n\nRepositories are versioned collections of packages. \n\n\nProjects can rely on remote repositories for functionality, and the newt tool \nwill resolve those remote repositories, and download the correct version into \nyour local source tree. Newly fetched repositories are put in the \nrepos\n\ndirectory of your project, and can be referenced throughout the sy
stem by using\nthe \n@\n specifier. \n\n\nBy default, the \n@apache-mynewt-core\n repository is included in every \nproject. Apache Mynewt Core contains all the base functionality of the Apache \nMynewt Operating System, including the Real Time Kernel, Bluetooth Networking \nStack, Flash File System, Console, Shell and Bootloader.\n\n\nNOTE:\n Any project can be converted into a repository by providing it with a \n\nrepository.yml\n file and putting it up onto Github. More information\nabout repositories can be found in the Newt documentation.\n\n\nPackage\n\n\nA package is a collection items that form a fundamental unit in the Mynewt \nOperating System. Packages can be:\n\n\n\n\nApplications\n\n\nLibraries\n\n\nCompiler definitions\n\n\nTargets\n\n\n\n\nA package is identified by having a \npkg.yml\n file in it's base \ndirectory. Here is a sample \npkg.yml\n file for the blinky applicaton:\n\n\n$ more 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/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\nPackages have a few features worth noting:\n\n\n\n\nDependencies: Packages can rely upon other packages, and when they do\n they will inherit their functionality (header files, library definitions, etc.)\n\n\nAPIs: Packages can export named APIs, and they can require that certain \n APIs be present, in order to compile.\n\n\nFeatures: Packages can operate differently depending on what named features are \n present in the system. Packages can also export features to the rest of the \n Mynewt system.\n\n\n\n\nEverything that newt knows about within a project's directory is a package. This \nmakes it very clean and easy to write re-usable components, which
can describe their \nDependencies and APIs to the rest of the system.\n\n\nTarget\n\n\nA target in Apache Mynewt is very similar to a target in \nmake\n. It is the collection\nof parameters that must be passed to Newt in order to generate a reproducible build. A \ntarget represents the top of the build tree, and any packages or parameters specified at \nthe target level, cascade down to all dependencies.\n\n\nTargets are also packages, and are stored in the \ntargets/\n directory at the base \nof your project. Most targets consist of: \n\n\n\n\napp\n: The application to build.\n\n\nbsp\n: The board support package to combine with that application\n\n\nbuild_profile\n: Either \ndebug\n or \noptimized\n. \n\n\n\n\nTargets can also have additional items specified, including: \n\n\n\n\ncflags\n: Any additional compiler flags you might want to specify to the build.\n\n\nfeatures\n: Any system level features you want to enable.\n\n\n\n\nIn order to create and manipulate targets, the \
nnewt\n tool offers a set of helper commands,\nyou can find more information about these by issuing:\n\n\n$ newt target\n\n\nnewt target\nUsage:\n newt target [flags]\n newt target [command]\n\nAvailable Commands:\n config View or populate a target\ns system configuration\n copy Copy target\n create Create a target\n delete Delete target\n dep View target\ns dependency graph\n revdep View target\ns reverse-dependency graph\n set Set target configuration variable\n show View target configuration variables\n\nGlobal Flags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when ex
ecuting commands\n\nUse \nnewt target [command] --help\n for more information about a command.\n\n$ \n\n\n\n\n\nConfiguration\n\n\nThere are a lot of configuration options available when building your application in MyNewt. System Configuration options are set in \na file called \nsyscfg.yml\n and you will find these configuration files throughout the MyNewt packages. While you can edit these\nfiles directly to change some default settings, it is best to override the default settings in a \nsyscfg.yml\n file in your project\ndirectory rather than editing the package configurations directly.\n\n\nTo see all \nall\n the system configuration settings, simply type\n\n\n$ newt target config show \ntarget-name\n\n...\n* PACKAGE: sys/stats\n * Setting: STATS_CLI\n * Description: Expose the \nstat\n shell command.\n * Value: 0\n * Setting: STATS_NAMES\n * Description: Include and report the textual name of each statistic.\n * Value: 0\n * Setting: STATS_NEWTMGR\n * Descrip
tion: Expose the \nstat\n newtmgr command.\n * Value: 0\n...\n$\n\n\n\n\n\nKeep in mind that this will only show the configuration options for any packages that are included in your applicaiton. \n\n\nIf you really want to see \nall\n the available configuration options, you can go rough each package and look at the\n\nsyscfg.yml\n file in each.",
+ "text": "Concepts\n\n\nThis page is meant to introduce you to some of the concepts inherent to \nthe Apache Mynewt Operating System, and \nNewt\n the tool that stitches a \nproject built on Apache Mynewt together.\n\n\nProject\n\n\nThe project is the base directory of your embedded software tree. It is a \nworkspace that contains a logical collection of source code, for one or \nmore of your applications. A project consists of the following items:\n\n\n\n\nProject Definition: defines project level dependencies, and parameters\n (located in \nproject.yml\n)\n\n\nPackages\n\n\n\n\nPackages\n are described in detail in the section below. \n\n\nHere is an example project definition file from the default Apache Mynewt \nproject: \n\n\n$ more project.yml \n\nsnip\n\nproject.name: \nmy_project\n\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#\nrepositor
y.apache-mynewt-core:\n type: github\n vers: 1-latest\n user: apache\n repo: incubator-mynewt-core\n$ \n\n\n\n\n\nA couple of things to note in the project definition:\n\n\n\n\n\n\nproject.repositories\n: Defines the remote repositories that this project\nrelies upon.\n\n\n\n\n\n\nrepository.apache-mynewt-core\n: Defines the repository information for \nthe \napache-mynewt-core\n repository.\n\n\n\n\n\n\nvers=1-latest\n: Defines the repository version. This string will use the \nlatest code in the 'Master' github branch. To use the latest version in the \ndevelop branch, just change it to \nvers=1-dev\n\n\n\n\n\n\nRepositories are versioned collections of packages. \n\n\nProjects can rely on remote repositories for functionality, and the newt tool \nwill resolve those remote repositories, and download the correct version into \nyour local source tree. Newly fetched repositories are put in the \nrepos\n\ndirectory of your project, and can be referenced throughout the sy
stem by using\nthe \n@\n specifier. \n\n\nBy default, the \n@apache-mynewt-core\n repository is included in every \nproject. Apache Mynewt Core contains all the base functionality of the Apache \nMynewt Operating System, including the Real Time Kernel, Bluetooth Networking \nStack, Flash File System, Console, Shell and Bootloader.\n\n\nNOTE:\n Any project can be converted into a repository by providing it with a \n\nrepository.yml\n file and putting it up onto Github. More information\nabout repositories can be found in the Newt documentation.\n\n\nPackage\n\n\nA package is a collection items that form a fundamental unit in the Mynewt \nOperating System. Packages can be:\n\n\n\n\nApplications\n\n\nLibraries\n\n\nCompiler definitions\n\n\nTargets\n\n\n\n\nA package is identified by having a \npkg.yml\n file in it's base \ndirectory. Here is a sample \npkg.yml\n file for the blinky applicaton:\n\n\n$ more 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/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\nPackages have a few features worth noting:\n\n\n\n\nDependencies: Packages can rely upon other packages, and when they do\n they will inherit their functionality (header files, library definitions, etc.)\n\n\nAPIs: Packages can export named APIs, and they can require that certain \n APIs be present, in order to compile.\n\n\n\n\nEverything that newt knows about within a project's directory is a package. This \nmakes it very clean and easy to write re-usable components, which can describe their \nDependencies and APIs to the rest of the system.\n\n\nTarget\n\n\nA target in Apache Mynewt is very similar to a target in \nmake\n. It is the collection\nof paramete
rs that must be passed to Newt in order to generate a reproducible build. A \ntarget represents the top of the build tree, and any packages or parameters specified at \nthe target level, cascade down to all dependencies.\n\n\nTargets are also packages, and are stored in the \ntargets/\n directory at the base \nof your project. Most targets consist of: \n\n\n\n\napp\n: The application to build.\n\n\nbsp\n: The board support package to combine with that application\n\n\nbuild_profile\n: Either \ndebug\n or \noptimized\n. \n\n\n\n\nTargets can also have additional items specified, including: \n\n\n\n\naflags\n: Any additional assembler flags you might want to specify to the build.\n\n\ncflags\n: Any additional compiler flags you might want to specify to the build.\n\n\nlflags\n: Any additional linker flags you might want to specify to the build.\n\n\n\n\nIn order to create and manipulate targets, the \nnewt\n tool offers a set of helper commands,\nyou can find more information about
these by issuing:\n\n\n$ newt target\n\n\nnewt target\nUsage:\n newt target [flags]\n newt target [command]\n\nAvailable Commands:\n config View or populate a target\ns system configuration\n copy Copy target\n create Create a target\n delete Delete target\n dep View target\ns dependency graph\n revdep View target\ns reverse-dependency graph\n set Set target configuration variable\n show View target configuration variables\n\nGlobal Flags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse \nnewt target [command] --help\n for more information about
a command.\n\n$ \n\n\n\n\n\nConfiguration\n\n\nThere are a lot of configuration options available when building your application in MyNewt. System Configuration options are set in \na file called \nsyscfg.yml\n and you will find these configuration files throughout the MyNewt packages. While you can edit these\nfiles directly to change some default settings, it is best to override the default settings in a \nsyscfg.yml\n file in your project\ndirectory rather than editing the package configurations directly.\n\n\nTo see all \nall\n the system configuration settings, simply type\n\n\n$ newt target config show \ntarget-name\n\n...\n* PACKAGE: sys/stats\n * Setting: STATS_CLI\n * Description: Expose the \nstat\n shell command.\n * Value: 0\n * Setting: STATS_NAMES\n * Description: Include and report the textual name of each statistic.\n * Value: 0\n * Setting: STATS_NEWTMGR\n * Description: Expose the \nstat\n newtmgr command.\n * Value: 0\n...\n$\n\n\n\n\n\nKeep
in mind that this will only show the configuration options for any packages that are included in your applicaiton. \n\n\nIf you really want to see \nall\n the available configuration options, you can go rough each package and look at the\n\nsyscfg.yml\n file in each.",
"title": "Concepts"
},
{
@@ -447,12 +447,12 @@
},
{
"location": "/os/get_started/vocabulary/#package",
- "text": "A package is a collection items that form a fundamental unit in the Mynewt \nOperating System. Packages can be: Applications Libraries Compiler definitions Targets A package is identified by having a pkg.yml file in it's base \ndirectory. Here is a sample pkg.yml file for the blinky applicaton: $ more pkg.yml snip \npkg.name: apps/blinky\npkg.type: app\npkg.description: Basic example application which blinks an LED.\npkg.author: Apache Mynewt dev@mynewt.incubator.apache.org \npkg.homepage: http://mynewt.apache.org/ \npkg.keywords:\n\npkg.deps:\n - @apache-mynewt-core/libs/os \n - @apache-mynewt-core/hw/hal \n - @apache-mynewt-core/libs/console/full Packages have a few features worth noting: Dependencies: Packages can rely upon other packages, and when they do\n they will inherit their functionality (header files, library definitions, etc.) APIs: Packages can export named APIs, and they can require that certain \n APIs be
present, in order to compile. Features: Packages can operate differently depending on what named features are \n present in the system. Packages can also export features to the rest of the \n Mynewt system. Everything that newt knows about within a project's directory is a package. This \nmakes it very clean and easy to write re-usable components, which can describe their \nDependencies and APIs to the rest of the system.",
+ "text": "A package is a collection items that form a fundamental unit in the Mynewt \nOperating System. Packages can be: Applications Libraries Compiler definitions Targets A package is identified by having a pkg.yml file in it's base \ndirectory. Here is a sample pkg.yml file for the blinky applicaton: $ more pkg.yml snip \npkg.name: apps/blinky\npkg.type: app\npkg.description: Basic example application which blinks an LED.\npkg.author: Apache Mynewt dev@mynewt.incubator.apache.org \npkg.homepage: http://mynewt.apache.org/ \npkg.keywords:\n\npkg.deps:\n - @apache-mynewt-core/libs/os \n - @apache-mynewt-core/hw/hal \n - @apache-mynewt-core/libs/console/full Packages have a few features worth noting: Dependencies: Packages can rely upon other packages, and when they do\n they will inherit their functionality (header files, library definitions, etc.) APIs: Packages can export named APIs, and they can require that certain \n APIs be
present, in order to compile. Everything that newt knows about within a project's directory is a package. This \nmakes it very clean and easy to write re-usable components, which can describe their \nDependencies and APIs to the rest of the system.",
"title": "Package"
},
{
"location": "/os/get_started/vocabulary/#target",
- "text": "A target in Apache Mynewt is very similar to a target in make . It is the collection\nof parameters that must be passed to Newt in order to generate a reproducible build. A \ntarget represents the top of the build tree, and any packages or parameters specified at \nthe target level, cascade down to all dependencies. Targets are also packages, and are stored in the targets/ directory at the base \nof your project. Most targets consist of: app : The application to build. bsp : The board support package to combine with that application build_profile : Either debug or optimized . Targets can also have additional items specified, including: cflags : Any additional compiler flags you might want to specify to the build. features : Any system level features you want to enable. In order to create and manipulate targets, the newt tool offers a set of helper commands,\nyou can find more information about these by issuing: $ newt target newt targ
et\nUsage:\n newt target [flags]\n newt target [command]\n\nAvailable Commands:\n config View or populate a target s system configuration\n copy Copy target\n create Create a target\n delete Delete target\n dep View target s dependency graph\n revdep View target s reverse-dependency graph\n set Set target configuration variable\n show View target configuration variables\n\nGlobal Flags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default WARN )\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don t output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse newt target [command] --help for more information about a command.\n\n$",
+ "text": "A target in Apache Mynewt is very similar to a target in make . It is the collection\nof parameters that must be passed to Newt in order to generate a reproducible build. A \ntarget represents the top of the build tree, and any packages or parameters specified at \nthe target level, cascade down to all dependencies. Targets are also packages, and are stored in the targets/ directory at the base \nof your project. Most targets consist of: app : The application to build. bsp : The board support package to combine with that application build_profile : Either debug or optimized . Targets can also have additional items specified, including: aflags : Any additional assembler flags you might want to specify to the build. cflags : Any additional compiler flags you might want to specify to the build. lflags : Any additional linker flags you might want to specify to the build. In order to create and manipulate targets, the newt tool offers a set
of helper commands,\nyou can find more information about these by issuing: $ newt target newt target\nUsage:\n newt target [flags]\n newt target [command]\n\nAvailable Commands:\n config View or populate a target s system configuration\n copy Copy target\n create Create a target\n delete Delete target\n dep View target s dependency graph\n revdep View target s reverse-dependency graph\n set Set target configuration variable\n show View target configuration variables\n\nGlobal Flags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default WARN )\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don t output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse newt target [c
ommand] --help for more information about a command.\n\n$",
"title": "Target"
},
{
@@ -481,18 +481,48 @@
"title": "Tutorial categories:"
},
{
+ "location": "/os/tutorials/blinky/",
+ "text": "Blinky, your \"Hello World!\" on a Target Board\n\n\nThe set of Blinky tutorials show you how to create, build, and run a \"Hello World\" application that blinks a LED on the various target boards that Mynewt supports. The tutorials use the same Blinky application from the \nCreating Your First Project\n tutorial. \n\n\nObjective\n\n\nLearn how to use packages from a default application repository of Mynewt to build your first \nHello World\n application (Blinky) on a target board. Once built using the \nnewt\n tool, this application will blink a LED light on the target board.\n\n\nAvailable Tutorials\n\n\nTutorials are available for the following boards:\n\n\n\n\nBlinky on an Arduino Zero\n\n\nBlinky on an Arduino Primo\n\n\nBlinky on an Olimex\n\n\nBlinky on a nRF52\n\n\nBlinky on a RedBear Nano 2\n\n\n\n\nWe also have a tutorial that shows you how to add \nConsole and Shell to the Blinky Application\n.\n\n\n\nPrerequisites\n\n\nEnsure that you meet the foll
owing prerequisites before continuing with one of the tutorials. \n\n\n\n\nHave Internet connectivity to fetch remote Mynewt components.\n\n\nHave a computer to build a Mynewt application and connect to the board over USB.\n\n\nHave a Micro-USB cable to connect the board and the computer.\n\n\nInstall the Newt tool and toolchains (See \nBasic Setup\n).\n\n\nInstall either the Jlink or OpenOCD debugger.\n\n\nCreate a project space (directory structure) and populate it with the core code repository (apache-mynewt-core) or know how to as explained in \nCreating Your First Project\n.\n\n\nRead the Mynewt OS \nConcepts\n section. \n\n\n\n\n\nOverview of Steps\n\n\nThese are the general steps to create, load and run the Blinky application on your board:\n\n\n\n\nCreate a project.\n\n\nDefine the bootloader and Blinky application targets for the board.\n\n\nBuild the bootloader target.\n\n\nBuild the Blinky application target and create an application image.\n\n\nConnect to the board.\n\n\
nLoad the bootloader onto the board.\n\n\nLoad the Blinky application image onto the board.\n\n\nSee the LED on your board blink.\n\n\n\n\n\n\nAfter you try the Blinky application on your boards, checkout out other tutorials to enable additional functionality such as \nremote comms\n on the current board. If you have BLE (Bluetooth Low Energy) chip (e.g. nRF52) on your board, you can try turning it into an \niBeacon\n or \nEddystone Beacon\n! \n\n\nIf you see anything missing or want to send us feedback, please sign up for \nappropriate mailing lists on our \nCommunity Page\n.",
+ "title": "toc"
+ },
+ {
+ "location": "/os/tutorials/blinky/#blinky-your-hello-world-on-a-target-board",
+ "text": "The set of Blinky tutorials show you how to create, build, and run a \"Hello World\" application that blinks a LED on the various target boards that Mynewt supports. The tutorials use the same Blinky application from the Creating Your First Project tutorial.",
+ "title": "Blinky, your \"Hello World!\" on a Target Board"
+ },
+ {
+ "location": "/os/tutorials/blinky/#objective",
+ "text": "Learn how to use packages from a default application repository of Mynewt to build your first Hello World application (Blinky) on a target board. Once built using the newt tool, this application will blink a LED light on the target board.",
+ "title": "Objective"
+ },
+ {
+ "location": "/os/tutorials/blinky/#available-tutorials",
+ "text": "Tutorials are available for the following boards: Blinky on an Arduino Zero Blinky on an Arduino Primo Blinky on an Olimex Blinky on a nRF52 Blinky on a RedBear Nano 2 We also have a tutorial that shows you how to add Console and Shell to the Blinky Application .",
+ "title": "Available Tutorials"
+ },
+ {
+ "location": "/os/tutorials/blinky/#prerequisites",
+ "text": "Ensure that you meet the following prerequisites before continuing with one of the tutorials. Have Internet connectivity to fetch remote Mynewt components. Have a computer to build a Mynewt application and connect to the board over USB. Have a Micro-USB cable to connect the board and the computer. Install the Newt tool and toolchains (See Basic Setup ). Install either the Jlink or OpenOCD debugger. Create a project space (directory structure) and populate it with the core code repository (apache-mynewt-core) or know how to as explained in Creating Your First Project . Read the Mynewt OS Concepts section.",
+ "title": "Prerequisites"
+ },
+ {
+ "location": "/os/tutorials/blinky/#overview-of-steps",
+ "text": "These are the general steps to create, load and run the Blinky application on your board: Create a project. Define the bootloader and Blinky application targets for the board. Build the bootloader target. Build the Blinky application target and create an application image. Connect to the board. Load the bootloader onto the board. Load the Blinky application image onto the board. See the LED on your board blink. After you try the Blinky application on your boards, checkout out other tutorials to enable additional functionality such as remote comms on the current board. If you have BLE (Bluetooth Low Energy) chip (e.g. nRF52) on your board, you can try turning it into an iBeacon or Eddystone Beacon ! If you see anything missing or want to send us feedback, please sign up for \nappropriate mailing lists on our Community Page .",
+ "title": "Overview of Steps"
+ },
+ {
"location": "/os/tutorials/arduino_zero/",
- "text": "Blinky, your \"Hello World!\", on Arduino Zero\n\n\nLearn how to use packages from a default application repository of Mynewt to build your first \nHello World\n application (Blinky) on a target board. Once built using the \nnewt\n tool, this application will blink the LED lights on the target board.\n\n\nThis tutorial describes how to run Mynewt OS on Arduino Zero. Follow these simple steps and your board will be blinking in no time!\n\n\nPrerequisites\n\n\nEnsure that you have met the following prerequisites before continuing with this tutorial:\n\n\n\n\nHave an Arduino Zero board.\n\nNote: There are many flavors of Arduino. Make sure you are using an Arduino Zero. See below for the versions of Arduino Zero that are compatible with this tutorial.\n\n\nHave Internet connectivity to fetch remote Mynewt components.\n\n\nHave a computer to build a Mynewt application and connect to the board over USB.\n\n\nHave a Micro-USB cable to connect the board and the compute
r.\n\n\nInstall the Newt tool and toolchains (See \nBasic Setup\n).\n\n\nCreate a project space (directory structure) and populated it with the core code repository (apache-mynewt-core) or know how to as explained in \nCreating Your First Project\n.\n\n\nRead the Mynewt OS \nConcepts\n section. \n\n\n\n\nThis tutorial uses the Arduino Zero Pro board. The tutorial has been tested on the following three Arduino Zero boards - Zero, M0 Pro, and Zero-Pro.\n\n\n\n\n\n\n\n\nMynewt has not been tested on Arduino M0 which has no internal debugger support.\n\n\n\n\nCreate a Project\n\n\nCreate a new project if you do not have an existing one. You can skip this step and proceed to \nfetch external packages\n if you already created a project. \n\n\nRun the following commands to create a new project: \n\n\n $ mkdir ~/dev\n $ cd ~/dev\n $ newt new myproj\n Downloading project skeleton from apache/incubator-mynewt-blinky...\n Installing skeleton in myproj...\n Project myproj su
ccessfully created.\n $ cd myproj\n $ newt install\n apache-mynewt-core\n $\n\n\n\n\n\n\n\n Fetch External Packages\n\n\nMynewt uses source code provided directly from the chip manufacturer for\nlow level operations. Sometimes this code is licensed only for the specific manufacturer of the chipset and cannot live in the Apache Mynewt repository. That happens to be the case for the Arduino Zero board which uses Atmel SAMD21. Runtime's github repository hosts such external third-party packages and the Newt tool can fetch them.\n\n\nTo fetch the package with MCU support for Atmel SAMD21 for Arduino Zero from the Runtime git repository, you need to add\nthe repository to the \nproject.yml\n file in your base project directory.\n\n\nHere is an example \nproject.yml\n file with the Arduino Zero repository\nadded. The sections with \nmynewt_arduino_zero\n that need to be added to\nyour project file are highlighted.\n\n\n$ more project.yml\nproject.name: \nmy_project\n\n\nprojec
t.repositories:\n - apache-mynewt-core\n\n - mynewt_arduino_zero\n\n\nrepository.apache-mynewt-core:\n type: github\n vers: 1-latest\n user: apache\n repo: incubator-mynewt-core\n\n\nrepository.mynewt_arduino_zero:\n\n type: github\n\n vers: 1-latest\n\n user: runtimeinc\n\n repo: mynewt_arduino_zero\n\n$\n\n\n\n\n\n\nInstall the project dependencies using the \nnewt install\n command (you can specify \n-v\n for verbose output):\n\n\n$ newt install\napache-mynewt-core\nmynewt_arduino_zero\n$\n\n\n\n\n\n\n\nNOTE:\n If there has been a new release of a repo used in your project since you last installed it, the \n1-latest\n version for the repo in the \nproject.yml\n file will refer to the new release and will not match the installed files. In that case you will get an error message saying so and you will need to run \nnewt upgrade\n to overwrite the existing files with the latest codebase.\n\n\n\nYou need to create two targets for the Arduino Zero Pro boa
rd, one for the bootloader and one for the Blinky application.\n\n\n\nRun the following \nnewt target\n commands, from your project directory, to create a bootloader target. We name the target \narduino_boot\n.\n\n\n$ newt target create arduino_boot\n$ newt target set arduino_boot bsp=@mynewt_arduino_zero/hw/bsp/arduino_zero\nTarget targets/arduino_boot successfully created\n$ newt target set arduino_boot app=@apache-mynewt-core/apps/boot\nTarget targets/arduino_boot successfully set target.app to @apache-mynewt-core/apps/boot\n$ newt target set arduino_boot build_profile=optimized\nTarget targets/arduino_boot successfully set target.build_profile to optimized\n$ newt target set arduino_boot syscfg=BSP_ARDUINO_ZERO_PRO=1\nTarget targets/arduino_boot successfully set target.syscfg to BSP_ARDUINO_ZERO_PRO=1\n$\n\n\n\n\n\nNote:\n If you have an Arduino Zero instead of an Arduino Zero Pro or Arduino
<TRUNCATED>
[04/11] incubator-mynewt-site git commit: Updated Blinky and Slinky
tutorials with intro summaries,
remove legacy feature references in the tutorials
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/newt/install/newt_linux/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/install/newt_linux/index.html b/latest/newt/install/newt_linux/index.html
index 2e481ee..efbfbca 100644
--- a/latest/newt/install/newt_linux/index.html
+++ b/latest/newt/install/newt_linux/index.html
@@ -439,10 +439,18 @@
<ul>
<li>
<p>Next, install Go. When installed, Go offers you as a developer a language environment (to compile Go code), construct Go packages (to assemble Go packages) and import Go code (from github). In the next step, you will use the Go commands to import <em>newt</em> repo into your local Go environment.</p>
-<p><strong>Note</strong>: The Newt tool requires Go version 1.6 or later. Depending on the Ubuntu version you have, the following may install an earlier version. In that case, download the latest package of Go 1.6 from <a href="https://golang.org/dl/">https://golang.org/dl/</a>. You can search for more detailed instructions such as installing Go 1.6 on Ubuntu 14.04 which can be found at <a href="https://www.digitalocean.com/community/tutorials/how-to-install-go-1-6-on-ubuntu-14-04">https://www.digitalocean.com/community/tutorials/how-to-install-go-1-6-on-ubuntu-14-04</a>.</p>
+<p><strong>Note</strong>: The Newt tool requires Go version 1.7 or later. Currently, the latest Go version that Ubuntu installs is 1.6. You can run <code>apt-get install golang-1.7-go</code> to install version 1.7. You can also download version 1.7 from <a href="https://golang.org/dl/">https://golang.org/dl/</a>. </p>
</li>
</ul>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ sudo apt-get install golang
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get install golang-1.7-go
+Reading package lists... Done
+ ...
+Unpacking golang-1.7-go (1.7.1-2ubuntu1) ...
+Setting up golang-1.7-go (1.7.1-2ubuntu1) ...
+$
+$sudo ln -s /usr/lib/go-1.7/bin/go /usr/bin/go
+$go version
+go version go1.7.1 linux/amd64
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/newt/newt_intro/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/newt_intro/index.html b/latest/newt/newt_intro/index.html
index d21ee01..5431df7 100644
--- a/latest/newt/newt_intro/index.html
+++ b/latest/newt/newt_intro/index.html
@@ -452,7 +452,7 @@ project.repositories:
#
repository.apache-mynewt-core:
type: github
- vers: 0-latest
+ vers: 1-latest
user: apache
repo: incubator-mynewt-core
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/core_os/cputime/os_cputime/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/cputime/os_cputime/index.html b/latest/os/core_os/cputime/os_cputime/index.html
index 0e28665..555beca 100644
--- a/latest/os/core_os/cputime/os_cputime/index.html
+++ b/latest/os/core_os/cputime/os_cputime/index.html
@@ -700,7 +700,7 @@
</div>
<h1 id="cpu-time">CPU Time</h1>
-<p>The MyNewt <code>cputime</code> module provides high resolution time and timer support. This module is intended for use by BSPs, drivers, and network controllers. </p>
+<p>The MyNewt <code>cputime</code> module provides high resolution time and timer support. </p>
<h2 id="description">Description</h2>
<p>The <code>cputime</code> API provides high resolution time and timer support. The module must be initialized, using the <code>os_cputime_init()</code> function, with the clock frequency to use. The module uses the <code>hal_timer</code> API, defined in hal/hal_timer.h, to access the hardware timers. It uses the hardware timer number specified by the <code>OS_CPUTIME_TIMER_NUM</code> system configuration setting.</p>
<h2 id="data-structures">Data Structures</h2>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/get_started/project_create/index.html
----------------------------------------------------------------------
diff --git a/latest/os/get_started/project_create/index.html b/latest/os/get_started/project_create/index.html
index 5cad4fc..f91e279 100644
--- a/latest/os/get_started/project_create/index.html
+++ b/latest/os/get_started/project_create/index.html
@@ -573,7 +573,7 @@ repos/apache-mynewt-core/
into your local directory. </p>
<p><br></p>
<h3 id="test-the-projects-packages">Test the project's packages</h3>
-<p>You have already built your first basic project. You can ask Newt to execute the unit tests in a package. For example, to test the <code>libs/os</code> package in the <code>apache-mynewt-core</code> repo, call newt as shown below.</p>
+<p>You have already built your first basic project. You can ask Newt to execute the unit tests in a package. For example, to test the <code>sys/config</code> package in the <code>apache-mynewt-core</code> repo, call newt as shown below.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt test @apache-mynewt-core/sys/config
Testing package @apache-mynewt-core/sys/config/test-fcb
Compiling bootutil_misc.c
@@ -662,9 +662,10 @@ Target successfully built: targets/my_blinky_sim
<p>You can run the simulated version of your project and see the simulated LED
blink. If you are using newt docker, use <code>newt run</code> to run the simulated binary.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt run my_blinky_sim
-No download script for BSP hw/bsp/native
-Debugging /workspace/bin/my_blinky_sim/apps/blinky/blinky.elf
-<snip>
+Loading app image into slot 1
+ ...
+Debugging ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf
+ ...
Reading symbols from /bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf...done.
(gdb)
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/get_started/vocabulary/index.html
----------------------------------------------------------------------
diff --git a/latest/os/get_started/vocabulary/index.html b/latest/os/get_started/vocabulary/index.html
index 0782e2d..8b907b7 100644
--- a/latest/os/get_started/vocabulary/index.html
+++ b/latest/os/get_started/vocabulary/index.html
@@ -413,9 +413,6 @@ pkg.deps:
they will inherit their functionality (header files, library definitions, etc.)</li>
<li>APIs: Packages can export named APIs, and they can require that certain
APIs be present, in order to compile.</li>
-<li>Features: Packages can operate differently depending on what named features are
- present in the system. Packages can also export features to the rest of the
- Mynewt system.</li>
</ul>
<p>Everything that newt knows about within a project's directory is a package. This
makes it very clean and easy to write re-usable components, which can describe their
@@ -434,8 +431,9 @@ of your project. Most targets consist of: </p>
</ul>
<p>Targets can also have additional items specified, including: </p>
<ul>
+<li><code>aflags</code>: Any additional assembler flags you might want to specify to the build.</li>
<li><code>cflags</code>: Any additional compiler flags you might want to specify to the build.</li>
-<li><code>features</code>: Any system level features you want to enable.</li>
+<li><code>lflags</code>: Any additional linker flags you might want to specify to the build.</li>
</ul>
<p>In order to create and manipulate targets, the <em>newt</em> tool offers a set of helper commands,
you can find more information about these by issuing:</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/modules/bootloader/bootloader/index.html
----------------------------------------------------------------------
diff --git a/latest/os/modules/bootloader/bootloader/index.html b/latest/os/modules/bootloader/bootloader/index.html
index c472ff4..20975b2 100644
--- a/latest/os/modules/bootloader/bootloader/index.html
+++ b/latest/os/modules/bootloader/bootloader/index.html
@@ -544,7 +544,7 @@
</div>
<h1 id="bootloader">Bootloader</h1>
-<p>The "bootloader" is the code that loads the Mynewt OS image into memory and conducts some checks before allowing the OS to be run. It manages images for the embedded system and upgrades of those images using protocols over various interfaces (e.g. serial, BLE etc.). Typically, systems with bootloaders have at least two program images coexisting on the same microcontroller, and hence must include branch code that performs a check to see if an attempt to update software is already underway and manage the progress of the process.</p>
+<p>The "bootloader" is the code that loads the Mynewt OS image into memory and conducts some checks before allowing the OS to be run. It manages images for the embedded system and upgrades of those images using protocols over various interfaces (e.g. serial, BLE, etc.). Typically, systems with bootloaders have at least two program images coexisting on the same microcontroller, and hence must include branch code that performs a check to see if an attempt to update software is already underway and manage the progress of the process.</p>
<p>The bootloader in the Apache Mynewt project verifies the cryptographic signature of the firmware image before running it. It maintains a detailed status log for each stage of the boot process. For verification of the authenticity of the OS image, it:</p>
<ul>
<li>Calculates hash of the image.</li>
@@ -590,7 +590,7 @@ characteristics:</p>
<span style="color: #A90D91">uint16_t</span> <span style="color: #000000">ih_tlv_size</span>; <span style="color: #177500">/* Trailing TLVs */</span>
<span style="color: #A90D91">uint8_t</span> <span style="color: #000000">ih_key_id</span>;
<span style="color: #A90D91">uint8_t</span> <span style="color: #000000">_pad1</span>;
- <span style="color: #A90D91">uint16_t</span> <span style="color: #000000">ih_hdr_s<</span> <span style="color: #000000">bok@bok</span>.<span style="color: #000000">net</span>
+ <span style="color: #A90D91">uint16_t</span> <span style="color: #000000">ih_hdr_size</span>;
<span style="color: #A90D91">uint16_t</span> <span style="color: #000000">_pad2</span>;
<span style="color: #A90D91">uint32_t</span> <span style="color: #000000">ih_img_size</span>; <span style="color: #177500">/* Does not include header. */</span>
<span style="color: #A90D91">uint32_t</span> <span style="color: #000000">ih_flags</span>;
@@ -604,12 +604,12 @@ characteristics:</p>
offset of the image itself. This field provides for backwards compatibility in
case of changes to the format of the image header.</p>
<p>The following are the image header flags available.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #633820">#define IMAGE_F_PIC 0x00000001</span>
-<span style="color: #633820">#define IMAGE_F_SHA256 0x00000002 </span><span style="color: #177500">/* Image contains hash TLV */</span><span style="color: #633820"></span>
-<span style="color: #633820">#define IMAGE_F_PKCS15_RSA2048_SHA256 0x00000004 </span><span style="color: #177500">/* PKCS15 w/RSA and SHA */</span><span style="color: #633820"></span>
-<span style="color: #633820">#define IMAGE_F_ECDSA224_SHA256 0x00000008 </span><span style="color: #177500">/* ECDSA256 over SHA256 */</span><span style="color: #633820"></span>
-<span style="color: #633820">#define IMAGE_F_NON_BOOTABLE 0x00000010</span>
-<span style="color: #633820">#define IMAGE_HEADER_SIZE 32</span>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #633820">#define IMAGE_F_PIC 0x00000001</span>
+<span style="color: #633820">#define IMAGE_F_SHA256 0x00000002 </span><span style="color: #177500">/* Image contains hash TLV */</span><span style="color: #633820"></span>
+<span style="color: #633820">#define IMAGE_F_PKCS15_RSA2048_SHA256 0x00000004 </span><span style="color: #177500">/* PKCS15 w/RSA and SHA */</span><span style="color: #633820"></span>
+<span style="color: #633820">#define IMAGE_F_ECDSA224_SHA256 0x00000008 </span><span style="color: #177500">/* ECDSA256 over SHA256 */</span><span style="color: #633820"></span>
+<span style="color: #633820">#define IMAGE_F_NON_BOOTABLE 0x00000010</span>
+<span style="color: #633820">#define IMAGE_HEADER_SIZE 32</span>
</pre></div>
@@ -635,11 +635,10 @@ after the end of the image. For example, security data gets added as a footer at
<p>A Mynewt device's flash is partitioned according to its <em>flash map</em>. At a high
level, the flash map maps numeric IDs to <em>flash areas</em>. A flash area is a
region of disk with the following properties:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">1. An area can be fully erased without affecting any other areas.
-2. A write to one area does not restrict writes to other areas.
-</pre></div>
-
-
+<ol>
+<li>An area can be fully erased without affecting any other areas.</li>
+<li>A write to one area does not restrict writes to other areas.</li>
+</ol>
<p>The boot loader uses the following flash areas:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #633820">#define FLASH_AREA_BOOTLOADER 0</span>
<span style="color: #633820">#define FLASH_AREA_IMAGE_0 1</span>
@@ -731,20 +730,23 @@ An image trailer has the following structure:</p>
<p>These records are at the end of each image slot. The offset immediately
following such a record represents the start of the next flash area.</p>
-<p>Note: "min-write-size" is a property of the flash hardware. If the hardware
+<p>Note: <code>min-write-size</code> is a property of the flash hardware. If the hardware
allows individual bytes to be written at arbitrary addresses, then
-min-write-size is 1. If the hardware only allows writes at even addresses,
-then min-write-size is 2, and so on.</p>
+<code>min-write-size</code> is 1. If the hardware only allows writes at even addresses,
+then <code>min-write-size</code> is 2, and so on.</p>
<p>The fields are defined as follows:</p>
<ol>
<li>
<p>MAGIC: The following 16 bytes, written in host-byte-order:</p>
-<p>const uint32_t boot_img_magic[4] = {
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">const uint32_t boot_img_magic[4] = {
0xf395c277,
0x7fefd260,
0x0f505235,
0x8079b62c,
-};</p>
+};
+</pre></div>
+
+
</li>
<li>
<p>Swap status: A series of single-byte records. Each record corresponds to a
@@ -755,18 +757,18 @@ if the device rebooted before a swap operation completed.</p>
</li>
<li>
<p>Copy done: A single byte indicating whether the image in this slot is
-complete (0x01=done, 0xff=not done).</p>
+complete (<code>0x01=done, 0xff=not done</code>).</p>
</li>
<li>
<p>Image OK: A single byte indicating whether the image in this slot has been
-confirmed as good by the user (0x01=confirmed; 0xff=not confirmed).</p>
+confirmed as good by the user (<code>0x01=confirmed; 0xff=not confirmed</code>).</p>
</li>
</ol>
<p>The boot vector records are structured around the limitations imposed by flash
hardware. As a consequence, they do not have a very intuitive design, and it
is difficult to get a sense of the state of the device just by looking at the
-boot vector. It is better to map all the possible vector states to the swap types (None, Test, Revert)
-via a set of tables. These tables are reproduced below.
+boot vector. It is better to map all the possible vector states to the swap types
+(None, Test, Revert) via a set of tables. These tables are reproduced below.
In these tables, the "pending" and "confirmed" flags are shown for illustrative
purposes; they are not actually present in the boot vector.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">State I
@@ -827,10 +829,11 @@ State IV
a high-level overview of the boot process is presented. Then, the following
sections describe each step of the process in more detail.</p>
<p>Procedure:</p>
-<p>A. Inspect swap status region; is an interrupted swap is being resumed?
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">A. Inspect swap status region; is an interrupted swap is being resumed?
Yes: Complete the partial swap operation; skip to step C.
- No: Proceed to step B.</p>
-<p>B. Insect boot vector; is a swap requested?
+ No: Proceed to step B.
+
+B. Inspect boot vector; is a swap requested?
Yes.
1. Is the requested image valid (integrity and security check)?
Yes.
@@ -841,14 +844,20 @@ sections describe each step of the process in more detail.</p>
a. Erase invalid image.
b. Persist failure of swap procedure to boot vector.
c. Proceed to step C.
- No: Proceed to step C.</p>
-<p>C. Boot into image in slot 0.</p>
+ No: Proceed to step C.
+
+C. Boot into image in slot 0.
+</pre></div>
+
+
<h3 id="image-swapping">Image Swapping</h3>
-<p>The boot loader swaps the contents of the two image slots for two reasons:
- * User has issued an "image test" operation; the image in slot-1 should be
- run once (state II).
- * Test image rebooted without being confirmed; the boot loader should
- revert to the original image currently in slot-1 (state III).</p>
+<p>The boot loader swaps the contents of the two image slots for two reasons:</p>
+<ul>
+<li>User has issued an "image test" operation; the image in slot-1 should be
+ run once (state II).</li>
+<li>Test image rebooted without being confirmed; the boot loader should
+ revert to the original image currently in slot-1 (state III).</li>
+</ul>
<p>If the boot vector indicates that the image in the secondary slot should be
run, the boot loader needs to copy it to the primary slot. The image currently
in the primary slot also needs to be retained in flash so that it can be used
@@ -882,11 +891,12 @@ according to the following procedure:</p>
can be written by the user at a later time. With the image trailer unwritten,
the user can test the image in slot 1 (i.e., transition to state II).</p>
<p>The particulars of step 3 vary depending on whether an image is being tested or
-reverted:
- * test:
- o Write slot0.copy_done = 1
- (should now be in state III)</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">* revert:
+reverted:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">* test:
+ o Write slot0.copy_done = 1
+ (should now be in state III)
+
+* revert:
o Write slot0.magic = BOOT_MAGIC
o Write slot0.copy_done = 1
o Write slot0.image_ok = 1
@@ -899,9 +909,9 @@ reverted:
the middle of an image swap operation. The swap status region consists of a
series of single-byte records. These records are written independently, and
therefore must be padded according to the minimum write size imposed by the
-flash hardware. In the below figure, a min-write-size of 1 is assumed for
+flash hardware. In the below figure, a <code>min-write-size</code> of 1 is assumed for
simplicity. The structure of the swap status region is illustrated below. In
-this figure, a min-write-size of 1 is assumed for simplicity.</p>
+this figure, a <code>min-write-size</code> of 1 is assumed for simplicity.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
@@ -931,11 +941,14 @@ sectors, the flash layout is not compatible with this boot loader. Finally,
reverse the list of indices such that the list starts with index 127 and ends
with 0. The swap status region is a representation of this reversed list.</p>
<p>During a swap operation, each sector index transitions through four separate
-states:
- 0. slot 0: image 0, slot 1: image 1, scratch: N/A
- 1. slot 0: image 0, slot 1: N/A, scratch: image 1 (1->s, erase 1)
- 2. slot 0: N/A, slot 1: image 0, scratch: image 1 (0->1, erase 0)
- 3. slot 0: image 1, slot 1: image 0, scratch: N/A (s->0)</p>
+states:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">0. slot 0: image 0, slot 1: image 1, scratch: N/A
+1. slot 0: image 0, slot 1: N/A, scratch: image 1 (1->s, erase 1)
+2. slot 0: N/A, slot 1: image 0, scratch: image 1 (0->1, erase 0)
+3. slot 0: image 1, slot 1: image 0, scratch: N/A (s->0)
+</pre></div>
+
+
<p>Each time a sector index transitions to a new state, the boot loader writes a
record to the swap status region. Logically, the boot loader only needs one
record per sector index to keep track of the current swap state. However, due
@@ -954,7 +967,7 @@ state 3 | 0x01 | 0x02 | 0x03
<p>The swap status region can accommodate 128 sector indices. Hence, the size of
-the region, in bytes, is 128 * min-write-size * 3. The number 128 is chosen
+the region, in bytes, is <code>128 * min-write-size * 3</code>. The number 128 is chosen
somewhat arbitrarily and will likely be made configurable. The only
requirement for the index count is that is is great enough to account for a
maximum-sized image (i.e., at least as great as the total sector count in an
@@ -1024,12 +1037,14 @@ it had just been started.</p>
primary slot. If the boot loader doesn't perform an image swap, then it
doesn't perform an integrity check.</p>
<p>During the integrity check, the boot loader verifies the following aspects of
-an image:
- * 32-bit magic number must be correct (0x96f3b83c).
- * Image must contain a SHA256 TLV.
- * Calculated SHA256 must matche SHA256 TLV contents.
- * Image <em>may</em> contain a signature TLV. If it does, its contents must be
- verifiable using a key embedded in the boot loader.</p>
+an image:</p>
+<ul>
+<li>32-bit magic number must be correct (0x96f3b83c).</li>
+<li>Image must contain a SHA256 TLV.</li>
+<li>Calculated SHA256 must matche SHA256 TLV contents.</li>
+<li>Image <em>may</em> contain a signature TLV. If it does, its contents must be
+ verifiable using a key embedded in the boot loader.</li>
+</ul>
<h3 id="image-signing-and-verification">Image Signing and Verification</h3>
<p>As indicated above, the final step of the integrity check is signature
verification. The boot loader can have one or more public keys embedded in it
@@ -1039,7 +1054,7 @@ The image signature TLV indicates the index of the key that is has been signed
with. The boot loader uses this index to identify the corresponding public
key.</p>
<p>For information on embedding public keys in the boot loader, as well as
-producing signed images, see: boot/bootutil/signed_images.md </p>
+producing signed images, see: boot/bootutil/signed_images.md</p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/modules/console/console/index.html
----------------------------------------------------------------------
diff --git a/latest/os/modules/console/console/index.html b/latest/os/modules/console/console/index.html
index 99a552c..ccae748 100644
--- a/latest/os/modules/console/console/index.html
+++ b/latest/os/modules/console/console/index.html
@@ -549,18 +549,13 @@ application. A user typically inputs text from a keyboard and reads the OS outp
monitor. The text are sent as a sequence of characters between the user and the OS. </p>
<p>Support is currently available for console access via the serial port on the hardware board.</p>
<h3 id="description">Description</h3>
-<p>In the Mynewt OS, the console library comes in two versions:</p>
+<p>In the Mynewt OS, the console library comes in three versions:</p>
<ul>
-<li>
-<p>The <code>sys/console/full</code> package implements the complete console functionality and API.</p>
-</li>
-<li>
-<p>The <code>sys/console/stub</code> package implements stubs for the API.</p>
-</li>
+<li>The <code>sys/console/full</code> package implements the complete console functionality and API.</li>
+<li>The <code>sys/console/stub</code> package implements stubs for the API.</li>
+<li>The <code>sys/console/minimal</code> package implements minimal console functionality of reading from and writing to console. It implements the <code>console_read()</code> and <code>console_write()</code> functions and stubs for all the other console functions.</li>
</ul>
-<p>Both packages export the <code>console</code> API, and any package that uses
-the console API must list <code>console</code> as a requirement. For example, the shell package defines the following <code>pkg.yml</code>
-file:</p>
+<p>All the packages export the <code>console</code> API, and any package that uses the console API must list <code>console</code> as a requirement its <code>pkg.yml</code> file: </p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">pkg.name: sys/shell
pkg.deps:
- kernel/os
@@ -572,9 +567,11 @@ pkg.req_apis:
</pre></div>
-<p>The project <code>pkg.yml</code> file specifies the version of the console package to use.
-A project that requires the full console capability must list the <code>sys/console/full</code> package as a dependency
-in its <code>pkg.yml</code> file.</p>
+<p><br>
+The project <code>pkg.yml</code> file also specifies the version of the console package to use.</p>
+<p><br></p>
+<h4 id="using-the-full-console-package">Using the Full Console Package</h4>
+<p>A project that requires the full console capability must list the <code>sys/console/full</code> package as a dependency in its <code>pkg.yml</code> file.</p>
<p>An example is the <code>slinky</code> application. It requires the full console capability and has the following
<code>pkg.yml</code> file: </p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">pkg.name: apps/slinky
@@ -592,22 +589,51 @@ pkg.deps:
</pre></div>
-<p>On the other hand, a project may not have a physical console (e.g. a UART port to connect a terminal to)
-but may have a dependency on a package that has console capability. In this case, you use
-the console stub API and list the <code>sys/console/stub</code> package as a dependency in its <code>pkg.yml</code> file. </p>
-<p>An example is the bootloader project where we want to keep the size of the image small. It includes
+<p><br></p>
+<h4 id="using-the-stub-console-package">Using the Stub Console Package</h4>
+<p>A project that uses console stub API must list the <code>sys/console/stub</code> package as a dependency in its <code>pkg.yml</code> file.</p>
+<p>Examples of when a project would use the console stubs might be:</p>
+<ul>
+<li>A project may not have a physical console (e.g. a UART port to connect a terminal to)
+but may have a dependency on a package that has console capability. </li>
+<li>A bootloader project where we want to keep the size of the image small. It includes
the <code>kernel/os</code> package that can print out messages on a console (e.g. if there is a hard fault).
However, we do not want to use any console I/O capability in this particular bootloader project to
-keep the size small. The project uses the console stub API and has the following <code>pkg.yml</code> file: </p>
+keep the size small. </li>
+</ul>
+<p>The project would use the console stub API and has the following <code>pkg.yml</code> file: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">pkg.name: apps/boot
+pkg.deps:
+ - boot/bootutil
+ - kernel/os
+ - sys/console/stub
+</pre></div>
+
+
+<p><br></p>
+<h4 id="using-the-minimal-console-package">Using the Minimal Console Package</h4>
+<p>There might be projects that need to read and write data on a serial connection but do not need the full console capability. An example might be a project that supports serial image upgrade but does not need full newtmgr capability. The project would use the console minimal API and has the following <code>pkg.yml</code> file: </p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">pkg.name: apps/boot
+pkg.type: app
+pkg.description: Boot loader application.
+pkg.author: "Apache Mynewt <dev@mynewt.incubator.apache.org>"
+pkg.homepage: "http://mynewt.apache.org/"
+pkg.keywords:
+ - loader
+
pkg.deps:
- boot/bootutil
- kernel/os
- sys/console/stub
+
+pkg.deps.BOOT_SERIAL.OVERWRITE:
+ - sys/console/minimal
+ - boot/boot_serial
</pre></div>
-<p>Console has 2 modes for transmit; <em>blocking mode</em> and <em>non-blocking mode</em>. Usually the <em>non-blocking mode</em> is the
+<p><br>
+Console has 2 modes for transmit; <em>blocking mode</em> and <em>non-blocking mode</em>. Usually the <em>non-blocking mode</em> is the
active one; the output buffer is drained by getting TX completion interrupts from hardware, and more data is added
based on these interrupts.</p>
<p><em>Blocking mode</em> is used when we don't want TX completion interrupts. It is used when system crashes, and we still
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/modules/console/console_read/index.html
----------------------------------------------------------------------
diff --git a/latest/os/modules/console/console_read/index.html b/latest/os/modules/console/console_read/index.html
index f11568c..4515512 100644
--- a/latest/os/modules/console/console_read/index.html
+++ b/latest/os/modules/console/console_read/index.html
@@ -606,7 +606,7 @@
</div>
<h2 id="console_read"><font color="#F2853F" style="font-size:24pt"> console_read </font></h2>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #A90D91">int</span> <span style="color: #000000">console_read</span>(<span style="color: #A90D91">char</span> <span style="color: #000000">*str</span>, <span style="color: #A90D91">int</span> <span style="color: #000000">cnt</span>)
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #A90D91">int</span> <span style="color: #000000">console_read</span>(<span style="color: #A90D91">char</span> <span style="color: #000000">*str</span>, <span style="color: #A90D91">int</span> <span style="color: #000000">cnt</span>, <span style="color: #A90D91">int</span> <span style="color: #000000">*newline</span>)
</pre></div>
@@ -629,6 +629,10 @@ separate lines; once it encounters a newline character, it replaces that with en
<td><code>cnt</code></td>
<td>Maximum number of characters to copy.</td>
</tr>
+<tr>
+<td><code>newline</code></td>
+<td>Pointer to an integer variable that is set to 1 when an newline character is received and set to 0 otherwise.</td>
+</tr>
</tbody>
</table>
<h4 id="returned-values">Returned values</h4>
@@ -641,12 +645,13 @@ available, or if the first received character was '\n'.</p>
<span style="color: #A90D91">struct</span> <span style="color: #000000">os_event</span> <span style="color: #000000">*ev</span>;
<span style="color: #A90D91">char</span> <span style="color: #000000">rx_msg</span>[<span style="color: #1C01CE">128</span>];
<span style="color: #A90D91">int</span> <span style="color: #000000">rx_len</span>;
+ <span style="color: #A90D91">int</span> <span style="color: #000000">newline</span>;
<span style="color: #A90D91">while</span> (<span style="color: #1C01CE">1</span>) {
<span style="color: #000000">ev</span> <span style="color: #000000">=</span> <span style="color: #000000">os_eventq_get</span>(<span style="color: #000000">&task1_evq</span>);
<span style="color: #000000">assert</span>(<span style="color: #000000">ev</span>);
<span style="color: #A90D91">if</span> (<span style="color: #000000">ev->ev_type</span> <span style="color: #000000">==</span> <span style="color: #000000">CONS_EV_TYPE</span>) {
- <span style="color: #000000">rx_len</span> <span style="color: #000000">=</span> <span style="color: #000000">console_read</span>(<span style="color: #000000">rx_msg</span>, <span style="color: #A90D91">sizeof</span>(<span style="color: #000000">rx_msg</span>));
+ <span style="color: #000000">rx_len</span> <span style="color: #000000">=</span> <span style="color: #000000">console_read</span>(<span style="color: #000000">rx_msg</span>, <span style="color: #A90D91">sizeof</span>(<span style="color: #000000">rx_msg</span>), <span style="color: #000000">&newline</span>);
<span style="color: #A90D91">if</span> (<span style="color: #000000">rx_len</span>) {
<span style="color: #A90D91">if</span> (<span style="color: #000000">!strncmp</span>(<span style="color: #000000">rx_msg</span>, <span style="color: #C41A16">"reset"</span>, <span style="color: #000000">rx_len</span>)) {
<span style="color: #000000">assert</span>(<span style="color: #1C01CE">0</span>);
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/STM32F303/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/STM32F303/index.html b/latest/os/tutorials/STM32F303/index.html
index 1f9304b..f1ab01b 100644
--- a/latest/os/tutorials/STM32F303/index.html
+++ b/latest/os/tutorials/STM32F303/index.html
@@ -232,14 +232,14 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
<ul>
+
+
<li >
<a href="../arduino_zero/">Blinky on Arduino Zero</a>
@@ -331,8 +331,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -340,7 +343,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -348,7 +351,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -356,20 +359,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -377,7 +375,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -385,7 +383,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -393,18 +391,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -412,15 +407,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -536,7 +534,7 @@
- <li>» <a href="../arduino_zero/">Project Blinky</a></li>
+ <li>» <a href="../blinky/">Project Blinky</a></li>
@@ -716,7 +714,7 @@ $ newt -v load stmf3_blinky
<p><br></p>
<h3 id="want-more">Want more?</h3>
<p>Want to make your board do something a little more exciting with the LEDs? Then try making the modifications to the Blinky app to make it a <a href="../pin-wheel-mods/">pin-wheel app</a> and you can light all the LEDs in a pin-wheel fashion.</p>
-<p>We have more fun tutorials for you to get your hands dirty. Be bold and try other Blinky-like <a href="../nRF52/">tutorials</a> or try enabling additional functionality such as <a href="../project-target-slinky/">remote comms</a> on the current board.</p>
+<p>We have more fun tutorials for you to get your hands dirty. Be bold and try other Blinky-like <a href="../nRF52/">tutorials</a> or try enabling additional functionality such as <a href="../project-slinky/">remote comms</a> on the current board.</p>
<p>If you see anything missing or want to send us feedback, please do so by signing up for appropriate mailing lists on our <a href="../../../community/">Community Page</a>.</p>
<p>Keep on hacking and blinking!</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/add_newtmgr/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/add_newtmgr/index.html b/latest/os/tutorials/add_newtmgr/index.html
index 9cb1a53..e3f9ce1 100644
--- a/latest/os/tutorials/add_newtmgr/index.html
+++ b/latest/os/tutorials/add_newtmgr/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,7 +264,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -271,36 +272,31 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
- <li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <li class="active">
+ <a href="./">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
- <li class="active">
- <a href="./">Enable Newt Manager in any app</a>
+ <li >
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -308,7 +304,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,18 +312,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -696,9 +692,9 @@ your device has limited flash memory and cannot support Over-The-Air (OTA) firmw
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../project-stm32-slinky/>
+ <a href=../eddystone/>
<span class="fa fa-arrow-left"></span>
- Previous: Slinky on STM32 board
+ Previous: BLE Eddystone
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/add_shell/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/add_shell/index.html b/latest/os/tutorials/add_shell/index.html
index abf9f80..c35de7a 100644
--- a/latest/os/tutorials/add_shell/index.html
+++ b/latest/os/tutorials/add_shell/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,7 +264,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -271,7 +272,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -279,20 +280,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li class="active">
+ <a href="./">Enable the OS Shell and Console</a>
</li>
@@ -300,15 +296,15 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
- <li class="active">
- <a href="./">Enable the OS Shell and Console</a>
+ <li >
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,18 +312,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -602,8 +598,8 @@ prompt on
</li>
<li class="pull-right">
- <a href=../bletiny_project/>
- Next: BLE app to check stats via console
+ <a href=../tasks_lesson/>
+ Next: Tasks and Priority Management
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/air_quality_ble/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/air_quality_ble/index.html b/latest/os/tutorials/air_quality_ble/index.html
index 07bb912..0beea21 100644
--- a/latest/os/tutorials/air_quality_ble/index.html
+++ b/latest/os/tutorials/air_quality_ble/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,7 +264,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -271,7 +272,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -279,20 +280,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -300,7 +296,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -308,7 +304,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,18 +312,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/air_quality_sensor/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/air_quality_sensor/index.html b/latest/os/tutorials/air_quality_sensor/index.html
index d632a96..d0cd4f2 100644
--- a/latest/os/tutorials/air_quality_sensor/index.html
+++ b/latest/os/tutorials/air_quality_sensor/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,7 +264,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -271,7 +272,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -279,20 +280,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -300,7 +296,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -308,7 +304,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,18 +312,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/arduino_zero/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/arduino_zero/index.html b/latest/os/tutorials/arduino_zero/index.html
index c9c8e2d..5943b12 100644
--- a/latest/os/tutorials/arduino_zero/index.html
+++ b/latest/os/tutorials/arduino_zero/index.html
@@ -232,14 +232,14 @@
- <li><a href="
- ./
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
<ul>
+
+
<li class="active">
<a href="./">Blinky on Arduino Zero</a>
@@ -317,8 +317,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -326,7 +329,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -334,7 +337,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -342,20 +345,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -363,7 +361,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -371,7 +369,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -379,18 +377,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -398,15 +393,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -526,7 +524,7 @@
- <li>» Project Blinky</li>
+ <li>» <a href="../blinky/">Project Blinky</a></li>
@@ -539,19 +537,12 @@
</div>
<h2 id="blinky-your-hello-world-on-arduino-zero">Blinky, your "Hello World!", on Arduino Zero</h2>
-<p>Learn how to use packages from a default application repository of Mynewt to build your first <em>Hello World</em> application (Blinky) on a target board. Once built using the <em>newt</em> tool, this application will blink the LED lights on the target board.</p>
-<p>This tutorial describes how to run Mynewt OS on Arduino Zero. Follow these simple steps and your board will be blinking in no time!</p>
+<p>This tutorial shows you how to create, build and run the Blinky application on an Arduino Zero board.</p>
<h3 id="prerequisites">Prerequisites</h3>
-<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
<ul>
+<li>Meet the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
<li>Have an Arduino Zero board.<br />
Note: There are many flavors of Arduino. Make sure you are using an Arduino Zero. See below for the versions of Arduino Zero that are compatible with this tutorial.</li>
-<li>Have Internet connectivity to fetch remote Mynewt components.</li>
-<li>Have a computer to build a Mynewt application and connect to the board over USB.</li>
-<li>Have a Micro-USB cable to connect the board and the computer.</li>
-<li>Install the Newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
-<li>Create a project space (directory structure) and populated it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.</li>
-<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section. </li>
</ul>
<p>This tutorial uses the Arduino Zero Pro board. The tutorial has been tested on the following three Arduino Zero boards - Zero, M0 Pro, and Zero-Pro.</p>
<p><img src="https://www.arduino.cc/en/uploads/Main/Zero_Usb_Ports.jpg" alt="Drawing" style="width: 390px;"/>
@@ -848,17 +839,8 @@ Continuing.
<p>If you want the image to run without the debugger connected, simply quit the
debugger and restart the board. The image you programmed will come up and run on
the Arduino on the next boot! </p>
-<p><br></p>
-<h3 id="watch-the-led-blink">Watch the LED Blink</h3>
-<p>Congratulations! You have created an Mynewt application running on the
-Arduino Zero. The LED right next to the power LED should be blinking. It is toggled
-by one task running on the Mynewt OS. </p>
-<p>We have more fun tutorials for you to get your hands dirty. Be bold and try other
-Blinky-like <a href="../nRF52/">tutorials</a> or try enabling additional functionality
-such as <a href="../project-target-slinky/">remote comms</a> on the current board.</p>
-<p>If you see anything missing or want to send us feedback, please do so by signing up for
-appropriate mailing lists on our <a href="../../../community/">Community Page</a>.</p>
-<p>Keep on hacking and blinking!</p>
+<p><br>
+You should see the LED blink!</p>
<div class="row">
@@ -868,9 +850,9 @@ appropriate mailing lists on our <a href="../../../community/">Community Page</a
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../tutorials/>
+ <a href=../blinky/>
<span class="fa fa-arrow-left"></span>
- Previous: Tutorials
+ Previous: Project Blinky
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/blehci_project/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/blehci_project/index.html b/latest/os/tutorials/blehci_project/index.html
index 9cac008..5b5347c 100644
--- a/latest/os/tutorials/blehci_project/index.html
+++ b/latest/os/tutorials/blehci_project/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,7 +264,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -271,7 +272,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -279,20 +280,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -300,7 +296,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -308,7 +304,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,18 +312,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -493,18 +489,15 @@ support native compiling to build the project this tutorial creates. </li>
</ul>
<p><br></p>
<h3 id="create-a-project">Create a project</h3>
-<p>Use the Newt tool to create a new project directory containing a skeletal Mynewt framework. Change into the newly created directory. Make sure the downloaded version is 0.9.0 or later.</p>
+<p>Use the Newt tool to create a new project directory containing a skeletal Mynewt framework. Change into the newly created directory. </p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt new blehciproj
Downloading project skeleton from apache/incubator-mynewt-blinky...
Installing skeleton in blehciproj ...
Project blehciproj successfully created.
$ cd mblehciproj
-$ newt install -v
+$ newt install
apache-mynewt-core
-Downloading repository description for apache-mynewt-core... success!
-...
-apache-mynewt-core successfully installed version 0.9.0-none
</pre></div>
@@ -548,13 +541,14 @@ $ newt target set myble2 build_profile=optimized
<p>Then build the two targets.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt build nrf52_boot
<snip>
-App successfully built: ./bin/nrf52_boot/apps/boot/boot.elf
+Linking ~/dev/blehciproj/bin/targets/nrf52_boot/app/apps/boot/boot.elf
+Target successfully built: targets/nrf52_boot
+
$ newt build myble2
-Compiling hci_common.c
-Compiling util.c
-Archiving nimble.a
-Compiling os.c
<snip>
+Linking ~/dev/blehciproj/bin/targets/myble2/app/apps/blehci/blehci.elf
+Target successfully built: targets/myble2
+$
</pre></div>
@@ -562,15 +556,25 @@ Compiling os.c
<h3 id="create-the-app-image">Create the app image</h3>
<p>Generate a signed application image for the <code>myble2</code> target. The version number is arbitrary.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt create-image myble2 1.0.0
-App image succesfully generated: ./bin/makerbeacon/apps/bletiny/bletiny.img
-Build manifest: ./bin/makerbeacon/apps/bletiny/manifest.json
+App image succesfully generated: ~/dev/blehciproj/bin/targets/myble2/app/apps/bletiny/bletiny.img
</pre></div>
<p><br></p>
-<h3 id="load-the-image">Load the image</h3>
+<h3 id="load-the-bootloader-and-the-application-image">Load the bootloader and the application image</h3>
<p>Make sure the USB connector is in place and the power LED on the board is lit. Use the Power ON/OFF switch to reset the board after loading the image.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt -v load myble
+<p>Load the bootloader:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load nrf52_boot
+Loading bootloader
+$
+</pre></div>
+
+
+<p><br>
+Load the application image:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load myble2
+Loading app image into slot 1
+$
</pre></div>
@@ -635,9 +639,9 @@ eir_len 23
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../eddystone/>
+ <a href=../bleprph/bleprph-app/>
<span class="fa fa-arrow-left"></span>
- Previous: BLE Eddystone
+ Previous: BLE Peripheral App
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/bleprph/bleprph-adv/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/bleprph/bleprph-adv/index.html b/latest/os/tutorials/bleprph/bleprph-adv/index.html
index e50a352..b0f4dba 100644
--- a/latest/os/tutorials/bleprph/bleprph-adv/index.html
+++ b/latest/os/tutorials/bleprph/bleprph-adv/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,19 @@
+
+
+ <li ><a href="../../project-slinky/">Project Slinky for Remote Comms</a>
+
+
+ </li>
+
+
+
+
+
<li >
- <a href="../../tasks_lesson/">Tasks and Priority Management</a>
+ <a href="../../ibeacon/">BLE iBeacon</a>
</li>
@@ -263,7 +272,7 @@
<li >
- <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../../eddystone/">BLE Eddystone</a>
</li>
@@ -271,7 +280,7 @@
<li >
- <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
@@ -279,20 +288,15 @@
<li >
- <a href="../../event_queue/">Events and Event Queues</a>
+ <a href="../../add_shell/">Enable the OS Shell and Console</a>
</li>
-
-
- <li><a href="
- ../../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -300,7 +304,7 @@
<li >
- <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -308,7 +312,15 @@
<li >
- <a href="../../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../event_queue/">Events and Event Queues</a>
</li>
@@ -381,22 +393,6 @@
<li >
- <a href="../../ibeacon/">BLE iBeacon</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../../eddystone/">BLE Eddystone</a>
- </li>
-
-
-
-
-
- <li >
<a href="../../blehci_project/">BLE HCI interface</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/bleprph/bleprph-app/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/bleprph/bleprph-app/index.html b/latest/os/tutorials/bleprph/bleprph-app/index.html
index d717455..c8b58dc 100644
--- a/latest/os/tutorials/bleprph/bleprph-app/index.html
+++ b/latest/os/tutorials/bleprph/bleprph-app/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,19 @@
+
+
+ <li ><a href="../../project-slinky/">Project Slinky for Remote Comms</a>
+
+
+ </li>
+
+
+
+
+
<li >
- <a href="../../tasks_lesson/">Tasks and Priority Management</a>
+ <a href="../../ibeacon/">BLE iBeacon</a>
</li>
@@ -263,7 +272,7 @@
<li >
- <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../../eddystone/">BLE Eddystone</a>
</li>
@@ -271,7 +280,7 @@
<li >
- <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
@@ -279,20 +288,15 @@
<li >
- <a href="../../event_queue/">Events and Event Queues</a>
+ <a href="../../add_shell/">Enable the OS Shell and Console</a>
</li>
-
-
- <li><a href="
- ../../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -300,7 +304,7 @@
<li >
- <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -308,7 +312,15 @@
<li >
- <a href="../../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../event_queue/">Events and Event Queues</a>
</li>
@@ -381,22 +393,6 @@
<li >
- <a href="../../ibeacon/">BLE iBeacon</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../../eddystone/">BLE Eddystone</a>
- </li>
-
-
-
-
-
- <li >
<a href="../../blehci_project/">BLE HCI interface</a>
</li>
@@ -610,8 +606,8 @@ happen on the device as well.</p>
</li>
<li class="pull-right">
- <a href=../../ibeacon/>
- Next: BLE iBeacon
+ <a href=../../blehci_project/>
+ Next: BLE HCI interface
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/bleprph/bleprph-chr-access/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/bleprph/bleprph-chr-access/index.html b/latest/os/tutorials/bleprph/bleprph-chr-access/index.html
index 182ed12..0c39d5b 100644
--- a/latest/os/tutorials/bleprph/bleprph-chr-access/index.html
+++ b/latest/os/tutorials/bleprph/bleprph-chr-access/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,19 @@
+
+
+ <li ><a href="../../project-slinky/">Project Slinky for Remote Comms</a>
+
+
+ </li>
+
+
+
+
+
<li >
- <a href="../../tasks_lesson/">Tasks and Priority Management</a>
+ <a href="../../ibeacon/">BLE iBeacon</a>
</li>
@@ -263,7 +272,7 @@
<li >
- <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../../eddystone/">BLE Eddystone</a>
</li>
@@ -271,7 +280,7 @@
<li >
- <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
@@ -279,20 +288,15 @@
<li >
- <a href="../../event_queue/">Events and Event Queues</a>
+ <a href="../../add_shell/">Enable the OS Shell and Console</a>
</li>
-
-
- <li><a href="
- ../../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -300,7 +304,7 @@
<li >
- <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -308,7 +312,15 @@
<li >
- <a href="../../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../event_queue/">Events and Event Queues</a>
</li>
@@ -381,22 +393,6 @@
<li >
- <a href="../../ibeacon/">BLE iBeacon</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../../eddystone/">BLE Eddystone</a>
- </li>
-
-
-
-
-
- <li >
<a href="../../blehci_project/">BLE HCI interface</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/bleprph/bleprph-gap-event/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/bleprph/bleprph-gap-event/index.html b/latest/os/tutorials/bleprph/bleprph-gap-event/index.html
index 73ede47..2467831 100644
--- a/latest/os/tutorials/bleprph/bleprph-gap-event/index.html
+++ b/latest/os/tutorials/bleprph/bleprph-gap-event/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,19 @@
+
+
+ <li ><a href="../../project-slinky/">Project Slinky for Remote Comms</a>
+
+
+ </li>
+
+
+
+
+
<li >
- <a href="../../tasks_lesson/">Tasks and Priority Management</a>
+ <a href="../../ibeacon/">BLE iBeacon</a>
</li>
@@ -263,7 +272,7 @@
<li >
- <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../../eddystone/">BLE Eddystone</a>
</li>
@@ -271,7 +280,7 @@
<li >
- <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
@@ -279,20 +288,15 @@
<li >
- <a href="../../event_queue/">Events and Event Queues</a>
+ <a href="../../add_shell/">Enable the OS Shell and Console</a>
</li>
-
-
- <li><a href="
- ../../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -300,7 +304,7 @@
<li >
- <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -308,7 +312,15 @@
<li >
- <a href="../../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../event_queue/">Events and Event Queues</a>
</li>
@@ -381,22 +393,6 @@
<li >
- <a href="../../ibeacon/">BLE iBeacon</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../../eddystone/">BLE Eddystone</a>
- </li>
-
-
-
-
-
- <li >
<a href="../../blehci_project/">BLE HCI interface</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/bleprph/bleprph-intro/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/bleprph/bleprph-intro/index.html b/latest/os/tutorials/bleprph/bleprph-intro/index.html
index ce4053c..28261e2 100644
--- a/latest/os/tutorials/bleprph/bleprph-intro/index.html
+++ b/latest/os/tutorials/bleprph/bleprph-intro/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,19 @@
+
+
+ <li ><a href="../../project-slinky/">Project Slinky for Remote Comms</a>
+
+
+ </li>
+
+
+
+
+
<li >
- <a href="../../tasks_lesson/">Tasks and Priority Management</a>
+ <a href="../../ibeacon/">BLE iBeacon</a>
</li>
@@ -263,7 +272,7 @@
<li >
- <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../../eddystone/">BLE Eddystone</a>
</li>
@@ -271,7 +280,7 @@
<li >
- <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
@@ -279,20 +288,15 @@
<li >
- <a href="../../event_queue/">Events and Event Queues</a>
+ <a href="../../add_shell/">Enable the OS Shell and Console</a>
</li>
-
-
- <li><a href="
- ../../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -300,7 +304,7 @@
<li >
- <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -308,7 +312,15 @@
<li >
- <a href="../../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../event_queue/">Events and Event Queues</a>
</li>
@@ -381,22 +393,6 @@
<li >
- <a href="../../ibeacon/">BLE iBeacon</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../../eddystone/">BLE Eddystone</a>
- </li>
-
-
-
-
-
- <li >
<a href="../../blehci_project/">BLE HCI interface</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/bleprph/bleprph-svc-reg/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/bleprph/bleprph-svc-reg/index.html b/latest/os/tutorials/bleprph/bleprph-svc-reg/index.html
index 0cbd8a3..485a50d 100644
--- a/latest/os/tutorials/bleprph/bleprph-svc-reg/index.html
+++ b/latest/os/tutorials/bleprph/bleprph-svc-reg/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,19 @@
+
+
+ <li ><a href="../../project-slinky/">Project Slinky for Remote Comms</a>
+
+
+ </li>
+
+
+
+
+
<li >
- <a href="../../tasks_lesson/">Tasks and Priority Management</a>
+ <a href="../../ibeacon/">BLE iBeacon</a>
</li>
@@ -263,7 +272,7 @@
<li >
- <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../../eddystone/">BLE Eddystone</a>
</li>
@@ -271,7 +280,7 @@
<li >
- <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
@@ -279,20 +288,15 @@
<li >
- <a href="../../event_queue/">Events and Event Queues</a>
+ <a href="../../add_shell/">Enable the OS Shell and Console</a>
</li>
-
-
- <li><a href="
- ../../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -300,7 +304,7 @@
<li >
- <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -308,7 +312,15 @@
<li >
- <a href="../../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../event_queue/">Events and Event Queues</a>
</li>
@@ -381,22 +393,6 @@
<li >
- <a href="../../ibeacon/">BLE iBeacon</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../../eddystone/">BLE Eddystone</a>
- </li>
-
-
-
-
-
- <li >
<a href="../../blehci_project/">BLE HCI interface</a>
</li>
[10/11] incubator-mynewt-site git commit: Updated Blinky and Slinky
tutorials with intro summaries,
remove legacy feature references in the tutorials
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/mkdocs/search_index.json
----------------------------------------------------------------------
diff --git a/develop/mkdocs/search_index.json b/develop/mkdocs/search_index.json
index 42a20f1..23eceed 100644
--- a/develop/mkdocs/search_index.json
+++ b/develop/mkdocs/search_index.json
@@ -277,7 +277,7 @@
},
{
"location": "/newt/install/newt_linux/",
- "text": "Install newt tool on Linux\n\n\n\n\nGetting your Linux box Ready\n\n\nIf you want to build the \nnewt\n tool from its source code, follow the following steps:\n\n\n1. Install git, libcurl\n\n\n $ sudo apt-get install git \n $ sudo apt-get install libcurl4-gnutls-dev \n\n\n\n\n\nNOTE:\n On 64-bit host, you may also need to install gcc-multilib, if you encounter compilation errors related to 'sys/cdefs.h'\n\n\n\n\n2. Install Go, the programming language\n\n\n\n\n\n\nGo language environment dictates a directory structure. Known in Go parlance as a workspace, it must contain three sibling directories with the directory names src, pkg and bin, as explained below. \n\n\n\n\n\n\nsrc contains Go source files organized into packages (one package per directory),\n\n\n\n\n\n\npkg contains package objects, and\n\n\n\n\n\n\nbin contains executable commands.\n\n\n\n\n\n\nThe GOPATH environment variable specifies the location of your workspace. To setup this work
space environment, create a 'dev' directory and then a 'go' directory under it. Set the GOPATH environment variable to this directory where you will soon clone the \nnewt\n tool repository.\n\n\n\n\n\n\n $ cd $HOME\n $ mkdir -p dev/go \n $ cd dev/go\n $ export GOPATH=`pwd`\n\n\n\n\n\n(Note that you need to add export statements to ~/.bash_profile to export variables permanently. Don't forget to source the file for the change to go into effect.)\n\n\n\n\n $ vi ~/.bash_profile\n $ source ~/.bash_profile\n\n\n\n\n\n\n\n\n\n\n\nNext, install Go. When installed, Go offers you as a developer a language environment (to compile Go code), construct Go packages (to assemble Go packages) and import Go code (from github). In the next step, you will use the Go commands to import \nnewt\n repo into your local Go environment.\n\n\nNote\n: The Newt tool requires Go version 1.6 or later. Depending on the Ubuntu version you have, the following may install an
earlier version. In that case, download the latest package of Go 1.6 from \nhttps://golang.org/dl/\n. You can search for more detailed instructions such as installing Go 1.6 on Ubuntu 14.04 which can be found at \nhttps://www.digitalocean.com/community/tutorials/how-to-install-go-1-6-on-ubuntu-14-04\n.\n\n\n\n\n\n\n $ sudo apt-get install golang \n\n\n\n\n\n \n\n\n3. Create local repository\n\n\n\n\nUse Go commands to copy the directory (currently the ASF incubator directory). Be patient as it may take a minute or two. Check the directories installed.\n\n\n\n\n $ go get mynewt.apache.org/newt/...\n\n\n\n\n\n\n\n\n\nCheck that newt.go is in place.\n\n\n\n\n $ ls $GOPATH/src/mynewt.apache.org/newt\n DISCLAIMER NOTICE newt newtvm viper\n LICENSE README.md newtmgr util yaml\n\n\n\n\n\n\n\n4. Build the Newt tool\n\n\n\n\nUse Go to run the newt.go program to build the \nnewt\n tool. The command \ngo install\n compil
es and writes the resulting executable to an output file named \nnewt\n, which is then installed, along with its dependencies, in $GOPATH/bin. If you get errors it is likely because of path resolution issues. Try \ngo build\n followed by \ngo install\n in that case.\n\n\n\n\n $ cd $GOPATH/src/mynewt.apache.org/newt/newt\n $ go install\n $ ls \n$GOPATH\n/bin/\n newt newtmgr newtvm\n\n\n\n\n\n\n\n\n\nAt this point, you can try using \nnewt\n. For example, check for the version number by typing 'newt version'. See all the possible commands available to a user of newt by typing 'newt -h'.\n\n\n\n\n(Note: If you are going to be modifying the \nnewt\n often and going to be compile the program every time you call it, you will want to store the command in a variable in your .bash_profile. So type in \nexport newt=\"go run $GOPATH/mynewt.apache.org/newt/newt/newt.go\"\n in your .bash_profile and execute it by calling \n$newt\n at the prompt instead of \nnewt\n. E
ssentially, \n$newt\n calls \ngo run\n which runs the compiled binary directly without producing an executable. Don't forget to reload the updated bash profile by typing \nsource ~/.bash_profile\n at the prompt! )\n\n\n $ newt version\n Newt version: 1.0\n $ newt -h\n Newt allows you to create your own embedded application based on the Mynewt \n operating system. Newt provides both build and package management in a single \n tool, which allows you to compose an embedded application, and set of \n projects, and then build the necessary artifacts from those projects. For more \n information on the Mynewt operating system, please visit \n https://mynewt.apache.org/. \n\n Please use the newt help command, and specify the name of the command you want \n help for, for help on how to use a specific command\n\n Usage:\n newt [flags]\n newt [command]\n\n Examples:\n newt\n
newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\n Available Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Execu
tes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\n Flags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing commands\n\n Use \nnewt [command] --help\n for more information about a comma\n\n\n\n\n\n\n\n5. Updating the Newt tool\n\n\n\n\nYou will update the newt tool in the same place as you initially installed the newt tool.\n\n\nStart by updating the git repository of the new
t tool (you can change to a different branch using git checkout [branch] if you need to)\n\n\nThen update each of the tools newt, newtmgr and newtvm as needed\n\n\n\n\n $ cd $GOPATH/src/mynewt.apache.org/newt\n $ git pull\n $ cd newt\n $ go install\n $ cd ../newtmgr\n $ go install\n $ cd ../newtvm\n $ go install\n $ ls \n$GOPATH\n/bin/\n newt newtmgr newtvm\n\n\n\n\n\nThat should have updated your newt, newtmgr and newtvm to the latest versions based on the git repository you used.",
+ "text": "Install newt tool on Linux\n\n\n\n\nGetting your Linux box Ready\n\n\nIf you want to build the \nnewt\n tool from its source code, follow the following steps:\n\n\n1. Install git, libcurl\n\n\n $ sudo apt-get install git \n $ sudo apt-get install libcurl4-gnutls-dev \n\n\n\n\n\nNOTE:\n On 64-bit host, you may also need to install gcc-multilib, if you encounter compilation errors related to 'sys/cdefs.h'\n\n\n\n\n2. Install Go, the programming language\n\n\n\n\n\n\nGo language environment dictates a directory structure. Known in Go parlance as a workspace, it must contain three sibling directories with the directory names src, pkg and bin, as explained below. \n\n\n\n\n\n\nsrc contains Go source files organized into packages (one package per directory),\n\n\n\n\n\n\npkg contains package objects, and\n\n\n\n\n\n\nbin contains executable commands.\n\n\n\n\n\n\nThe GOPATH environment variable specifies the location of your workspace. To setup this work
space environment, create a 'dev' directory and then a 'go' directory under it. Set the GOPATH environment variable to this directory where you will soon clone the \nnewt\n tool repository.\n\n\n\n\n\n\n $ cd $HOME\n $ mkdir -p dev/go \n $ cd dev/go\n $ export GOPATH=`pwd`\n\n\n\n\n\n(Note that you need to add export statements to ~/.bash_profile to export variables permanently. Don't forget to source the file for the change to go into effect.)\n\n\n\n\n $ vi ~/.bash_profile\n $ source ~/.bash_profile\n\n\n\n\n\n\n\n\n\n\n\nNext, install Go. When installed, Go offers you as a developer a language environment (to compile Go code), construct Go packages (to assemble Go packages) and import Go code (from github). In the next step, you will use the Go commands to import \nnewt\n repo into your local Go environment.\n\n\nNote\n: The Newt tool requires Go version 1.7 or later. Currently, the latest Go version that Ubuntu installs is 1.6. You can
run \napt-get install golang-1.7-go\n to install version 1.7. You can also download version 1.7 from \nhttps://golang.org/dl/\n. \n\n\n\n\n\n\n$sudo apt-get install golang-1.7-go\nReading package lists... Done\n ...\nUnpacking golang-1.7-go (1.7.1-2ubuntu1) ...\nSetting up golang-1.7-go (1.7.1-2ubuntu1) ...\n$\n$sudo ln -s /usr/lib/go-1.7/bin/go /usr/bin/go\n$go version\ngo version go1.7.1 linux/amd64\n\n\n\n\n\n \n\n\n3. Create local repository\n\n\n\n\nUse Go commands to copy the directory (currently the ASF incubator directory). Be patient as it may take a minute or two. Check the directories installed.\n\n\n\n\n $ go get mynewt.apache.org/newt/...\n\n\n\n\n\n\n\n\n\nCheck that newt.go is in place.\n\n\n\n\n $ ls $GOPATH/src/mynewt.apache.org/newt\n DISCLAIMER NOTICE newt newtvm viper\n LICENSE README.md newtmgr util yaml\n\n\n\n\n\n\n\n4. Build the Newt tool\n\n\n\n\nUse Go to run the newt.go program to build
the \nnewt\n tool. The command \ngo install\n compiles and writes the resulting executable to an output file named \nnewt\n, which is then installed, along with its dependencies, in $GOPATH/bin. If you get errors it is likely because of path resolution issues. Try \ngo build\n followed by \ngo install\n in that case.\n\n\n\n\n $ cd $GOPATH/src/mynewt.apache.org/newt/newt\n $ go install\n $ ls \n$GOPATH\n/bin/\n newt newtmgr newtvm\n\n\n\n\n\n\n\n\n\nAt this point, you can try using \nnewt\n. For example, check for the version number by typing 'newt version'. See all the possible commands available to a user of newt by typing 'newt -h'.\n\n\n\n\n(Note: If you are going to be modifying the \nnewt\n often and going to be compile the program every time you call it, you will want to store the command in a variable in your .bash_profile. So type in \nexport newt=\"go run $GOPATH/mynewt.apache.org/newt/newt/newt.go\"\n in your .bash_profile and execute it by c
alling \n$newt\n at the prompt instead of \nnewt\n. Essentially, \n$newt\n calls \ngo run\n which runs the compiled binary directly without producing an executable. Don't forget to reload the updated bash profile by typing \nsource ~/.bash_profile\n at the prompt! )\n\n\n $ newt version\n Newt version: 1.0\n $ newt -h\n Newt allows you to create your own embedded application based on the Mynewt \n operating system. Newt provides both build and package management in a single \n tool, which allows you to compose an embedded application, and set of \n projects, and then build the necessary artifacts from those projects. For more \n information on the Mynewt operating system, please visit \n https://mynewt.apache.org/. \n\n Please use the newt help command, and specify the name of the command you want \n help for, for help on how to use a specific command\n\n Usage:\n newt [flags]\n ne
wt [command]\n\n Examples:\n newt\n newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\n Available Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, confi
gure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\n Flags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing commands\n\n Use \nnewt [command] --help\n for more information about a comma\n\n\n\n\n\n\n\n5. Updating the Newt tool\n\n\n\n\nYou will update the newt tool in the same place as you initially installed the newt tool.
\n\n\nStart by updating the git repository of the newt tool (you can change to a different branch using git checkout [branch] if you need to)\n\n\nThen update each of the tools newt, newtmgr and newtvm as needed\n\n\n\n\n $ cd $GOPATH/src/mynewt.apache.org/newt\n $ git pull\n $ cd newt\n $ go install\n $ cd ../newtmgr\n $ go install\n $ cd ../newtvm\n $ go install\n $ ls \n$GOPATH\n/bin/\n newt newtmgr newtvm\n\n\n\n\n\nThat should have updated your newt, newtmgr and newtvm to the latest versions based on the git repository you used.",
"title": "Install Newt on Linux"
},
{
@@ -297,7 +297,7 @@
},
{
"location": "/newt/install/newt_linux/#2-install-go-the-programming-language",
- "text": "Go language environment dictates a directory structure. Known in Go parlance as a workspace, it must contain three sibling directories with the directory names src, pkg and bin, as explained below. src contains Go source files organized into packages (one package per directory), pkg contains package objects, and bin contains executable commands. The GOPATH environment variable specifies the location of your workspace. To setup this workspace environment, create a 'dev' directory and then a 'go' directory under it. Set the GOPATH environment variable to this directory where you will soon clone the newt tool repository. $ cd $HOME\n $ mkdir -p dev/go \n $ cd dev/go\n $ export GOPATH=`pwd` (Note that you need to add export statements to ~/.bash_profile to export variables permanently. Don't forget to source the file for the change to go into effect.) $ vi ~/.bash_profile\n $ source ~/.bash_profile
Next, install Go. When installed, Go offers you as a developer a language environment (to compile Go code), construct Go packages (to assemble Go packages) and import Go code (from github). In the next step, you will use the Go commands to import newt repo into your local Go environment. Note : The Newt tool requires Go version 1.6 or later. Depending on the Ubuntu version you have, the following may install an earlier version. In that case, download the latest package of Go 1.6 from https://golang.org/dl/ . You can search for more detailed instructions such as installing Go 1.6 on Ubuntu 14.04 which can be found at https://www.digitalocean.com/community/tutorials/how-to-install-go-1-6-on-ubuntu-14-04 . $ sudo apt-get install golang",
+ "text": "Go language environment dictates a directory structure. Known in Go parlance as a workspace, it must contain three sibling directories with the directory names src, pkg and bin, as explained below. src contains Go source files organized into packages (one package per directory), pkg contains package objects, and bin contains executable commands. The GOPATH environment variable specifies the location of your workspace. To setup this workspace environment, create a 'dev' directory and then a 'go' directory under it. Set the GOPATH environment variable to this directory where you will soon clone the newt tool repository. $ cd $HOME\n $ mkdir -p dev/go \n $ cd dev/go\n $ export GOPATH=`pwd` (Note that you need to add export statements to ~/.bash_profile to export variables permanently. Don't forget to source the file for the change to go into effect.) $ vi ~/.bash_profile\n $ source ~/.bash_profile
Next, install Go. When installed, Go offers you as a developer a language environment (to compile Go code), construct Go packages (to assemble Go packages) and import Go code (from github). In the next step, you will use the Go commands to import newt repo into your local Go environment. Note : The Newt tool requires Go version 1.7 or later. Currently, the latest Go version that Ubuntu installs is 1.6. You can run apt-get install golang-1.7-go to install version 1.7. You can also download version 1.7 from https://golang.org/dl/ . $sudo apt-get install golang-1.7-go\nReading package lists... Done\n ...\nUnpacking golang-1.7-go (1.7.1-2ubuntu1) ...\nSetting up golang-1.7-go (1.7.1-2ubuntu1) ...\n$\n$sudo ln -s /usr/lib/go-1.7/bin/go /usr/bin/go\n$go version\ngo version go1.7.1 linux/amd64",
"title": "2. Install Go, the programming language"
},
{
@@ -357,7 +357,7 @@
},
{
"location": "/os/get_started/project_create/",
- "text": "Create Your First Mynewt Project\n\n\nThis page shows how to create a Mynewt Project using the \nnewt\n command-line tool.\n\n\n\n\nPre-Requisites\n\n\n\n\nNewt:\n\n\nIf you have taken the Docker route, you have already installed Newt.\n\n\nIf you have taken the native install route, you have to ensure that you have installed the Newt tool following the instructions for \nMac\n or \nLinux\n as appropriate, and that the \nnewt\n command is in your system path. \n\n\n\n\n\n\nYou must have Internet connectivity to fetch remote Mynewt components.\n\n\nYou must \ninstall the compiler tools\n to \nsupport native compiling to build the project this tutorial creates. \n\n\n\n\n\n\nNewt New\n\n\nChoose a project name. For this tutorial we will call this project \nmyproj\n.\nEnter the \nnewt new myproj\n command. \n\n\n$ newt new myproj\nDownloading project skeleton from apache/incubator-mynewt-blinky...\nInstalling skeleton in myproj...\nProject myproj successfully crea
ted.\n\n\n\n\n\n\n\nNewt populates this new project with a base skeleton of a new Apache Mynewt \nproject. It has the following structure. \n\n\nNote\n: If you do not have \ntree\n, install it by running \nbrew install tree\n.\n\n\n$ cd myproj\n$ tree \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\u00a0\u00a0 \u2514\u2500\u2500 blinky\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 pkg.yml\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 src\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 main.c\n\u251c\u2500\u2500 project.yml\n\u2514\u2500\u2500 targets\n \u251c\u2500\u2500 my_blinky_sim\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 pkg.yml\n \u2502\u00a0\u00a0 \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, 11 files\n\n\n\n\n\n\n\nThe Newt tool has installed the base files for a
project comprising the following:\n\n\n\n\nThe file \nproject.yml\n contains the repository list that the project uses to fetch\nits packages. Your project is a collection of repositories. In this case, the project just\ncomprises the core mynewt repository. Later you will add more repositories\nto include other mynewt components.\n\n\nThe file \napps/blinky/pkg.yml\n contains the description of your application\nand its package dependencies.\n\n\nA \ntarget\n directory containing \nmy_blinky_sim\n, a target descriptor used to\nbuild a version of myproj. Use \nnewt target show\n to see available build \ntargets.\n\n\nA non-buildable target called \nunittest\n. This is used internally by \nnewt\n and is not a formal build target.\n\n\n\n\nNOTE:\n The actual code and package files are not installed \n(except the template for \nmain.c\n). See the next step for installing the packages.\n\n\nNOTE:\n By default newt uses the code in the master branch. This is the latest stable\ncode
for newt. If you need to use a different branch, you can set this in the project.yml\nfile. \n\n\nrepository.apache-mynewt-core:\n type: github\n vers: 1-latest\n user: apache\n repo: incubator-mynewt-core\n\n\n\n\n\nChanging to 1-dev will put you on the develop branch. \nThe Develop Branch may not be stable and you may encounter bugs or other problems.\n\n\n\n\nNewt Install\n\n\nOnce you've switched into your new project's directory, the next step is to fetch\nany dependencies this project has. By default, all Newt projects rely on a\nsingle remote repository, apache-mynewt-core. The \nnewt install\n command will\nfetch this repository.\n\n\n$ newt install\napache-mynewt-core\n\n\n\n\n\nNOTE:\n \napache-mynewt-core\n may take a while to download. To see progress,\nuse the \n-v\n (verbose) option to install. \n\n\n\n\nOnce \nnewt install\n has successfully finished, the contents of \napache-mynewt-core\n will have been downloaded into your local directory. You can v
iew them by issuing the following commands in the base directory of the new project. The actual output will depend on what is in the latest 'master' branch you have pulled from.\n\n\n$ tree -L 2 repos/apache-mynewt-core/\n\nrepos/apache-mynewt-core/\n\u251c\u2500\u2500 CODING_STANDARDS.md\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 RELEASE_NOTES.md\n\u251c\u2500\u2500 apps\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 blecent\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 blehci\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bleprph\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bleprph_oic\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 blesplit\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bletest\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bletiny\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bleuart\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 boot\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fat2native\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 ffs2native\n\u25
02\u00a0\u00a0 \u251c\u2500\u2500 ocf_sample\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 slinky\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 slinky_oic\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 spitest\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 splitty\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 testbench\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 timtest\n\u251c\u2500\u2500 boot\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 boot_serial\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bootutil\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 split\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 split_app\n\u251c\u2500\u2500 compiler\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 arm-none-eabi-m0\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 arm-none-eabi-m4\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 gdbmacros\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mips\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 sim\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 sim-mips\n\u251c\u2500\u2500 crypto\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mbedtls\n\u25
02\u00a0\u00a0 \u2514\u2500\u2500 tinycrypt\n\u251c\u2500\u2500 docs\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 doxygen.xml\n\u251c\u2500\u2500 encoding\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 base64\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 cborattr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 json\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 tinycbor\n\u251c\u2500\u2500 fs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 disk\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fatfs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fcb\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fs\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 nffs\n\u251c\u2500\u2500 hw\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bsp\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 cmsis-core\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 drivers\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 hal\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mcu\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 scripts\n\u251c\u2500\u2500 kernel\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 os\n\u251c\u2500\u2500 libc\n\u2502\u00a0\u00a0 \u2514\u250
0\u2500 baselibc\n\u251c\u2500\u2500 mgmt\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 imgmgr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mgmt\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 newtmgr\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 oicmgr\n\u251c\u2500\u2500 net\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 ip\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 nimble\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 oic\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 wifi\n\u251c\u2500\u2500 project.yml\n\u251c\u2500\u2500 repository.yml\n\u251c\u2500\u2500 sys\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 config\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 console\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 coredump\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 defs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 flash_map\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 id\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 log\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mfg\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 reboot\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 shell\n\u2502\u00a0\u00a0 \u251c\u2
500\u2500 stats\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 sysinit\n\u251c\u2500\u2500 targets\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 unittest\n\u251c\u2500\u2500 test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 crash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 flash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 runtest\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 testutil\n\u251c\u2500\u2500 time\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 datetime\n\u2514\u2500\u2500 util\n \u251c\u2500\u2500 cbmem\n \u251c\u2500\u2500 crc\n \u2514\u2500\u2500 mem\n\n94 directories, 9 files\n\n\n\n\n\nAs you can see, the core of the Apache Mynewt operating system has been brought \ninto your local directory. \n\n\n\n\nTest the project's packages\n\n\nYou have already built your first basic project. You can ask Newt to execute the unit tests in a package. For example, to test the \nlibs/os\n package in the \napache-mynewt-core\n repo, call newt as shown below.\n\n\n$ newt test @apache-mynewt-core/sys/config\nTe
sting package @apache-mynewt-core/sys/config/test-fcb\nCompiling bootutil_misc.c\nCompiling image_ec.c\nCompiling image_rsa.c\nCompiling image_validate.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nTesting package @apache-mynewt-core/sys/config/test-nffs\nCompiling repos/apache-mynewt-core/encoding/base64/src/hex.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_cli.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_dirent.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_mkdir.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_mount.c\nCompiling repos/apache-mynewt-core/encoding/base64/src/base64.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_file.c\nCompiling repos/apache-mynewt-core/fs/disk/src/disk.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_nmgr.c\nCompiling repos/apac
he-mynewt-core/fs/fs/src/fsutil.c\nCompiling repos/apache-mynewt-core/fs/nffs/src/nffs.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nPassed tests: [sys/config/test-fcb sys/config/test-nffs]\nAll tests passed\n\n\n\n\n\nNOTE:\n If you've installed the latest gcc using homebrew on your Mac, you will likely be running gcc-6. Make sure you have adjusted the compiler.yml configuration to reflect that as noted in \nNative Install Option\n. You can choose to downgrade to gcc-5 in order to use the default gcc compiler configuration for MyNewt.\n\n\nNOTE:\n If you are running the standard gcc for 64-bit machines, it does not support 32-bit. In that case you will see compilation errors. You need to install multiboot gcc (e.g. gcc-multilib if you running on a 64-bit Ubuntu).\n\n\n$ brew uni
nstall gcc-6\n$ brew link gcc-5\n\n\n\n\n\n\n\nTo test all the packages in a project, specify \nall\n instead of the package name.\n\n\n$ newt test all\nTesting package @apache-mynewt-core/boot/boot_serial/test\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/boot_test.c\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/testcases/boot_serial_setup.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/boot_boot_serial_test/app/boot/boot_serial/test/boot_boot_serial_test.elf\n\n...lots of compiling and testing...\n\nLinking ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nPassed tests: [boot/boot_serial/test boot/bootutil/test crypto/mbedtls/test encoding/base64/test encoding/cborattr/test encoding/json/test fs/fcb/test fs/nffs/test kernel/os/test net/ip/mn_socket/test net/nimble/host/test net/oic/test sys/co
nfig/test-fcb sys/config/test-nffs sys/flash_map/test sys/log/full/test util/cbmem/test]\nAll tests passed\n\n\n\n\n\n\n\nBuild the Project\n\n\nTo build and run your new application, simply issue the following command:\n\n\n$ newt build my_blinky_sim \nBuilding target targets/my_blinky_sim\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_common.c\nCompiling repos/apache-mynewt-core/hw/drivers/uart/src/uart.c\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c\nCompiling repos/apache-mynewt-core/hw/bsp/native/src/hal_bsp.c\nCompiling repos/apache-mynewt-core/hw/drivers/uart/uart_hal/src/uart_hal.c\nCompiling apps/blinky/src/main.c\n\n ...\n\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nTarget successfully built: targets/my_blinky_sim\n\n\n\n\n\n\n\nRun the Project\n\n\nYou can run the simulated version of your project and see the simulated LED\nblink. If you are using newt
docker, use \nnewt run\n to run the simulated binary.\n\n\n$ newt run my_blinky_sim\nNo download script for BSP hw/bsp/native\nDebugging /workspace/bin/my_blinky_sim/apps/blinky/blinky.elf\n\nsnip\n\nReading symbols from /bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf...done.\n(gdb)\n\n\n\n\n\nType \nr\n at the \n(gdb)\n prompt to run the project. You will see an output indicating that the hal_gpio pin is toggling between 1 and 0 in a simulated blink.\n\n\nIf you natively install the toolchain, you can either use \nnewt run\n or call the binary directly. Generally, \nnewt run\n is the expected way to call things.\n\n\n$ ./bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nhal_gpio set pin 1 to 0\n\n\n\n\n\n\n\nComplete\n\n\nCongratulations, you have created your first project! The blinky application\nis not terribly exciting when it is run in the simulator, as there is no LED to\nblink. Apache Mynewt has a lot more functionality than just running simulated\napplications
. It provides all the features you'll need to cross-compile your\napplication, run it on real hardware and develop a full featured application.\n\n\nIf you're interested in learning more, a good next step is to dig in to one of\nthe \ntutorials\n and get a Mynewt project running on real hardware.\n\n\nHappy Hacking!",
+ "text": "Create Your First Mynewt Project\n\n\nThis page shows how to create a Mynewt Project using the \nnewt\n command-line tool.\n\n\n\n\nPre-Requisites\n\n\n\n\nNewt:\n\n\nIf you have taken the Docker route, you have already installed Newt.\n\n\nIf you have taken the native install route, you have to ensure that you have installed the Newt tool following the instructions for \nMac\n or \nLinux\n as appropriate, and that the \nnewt\n command is in your system path. \n\n\n\n\n\n\nYou must have Internet connectivity to fetch remote Mynewt components.\n\n\nYou must \ninstall the compiler tools\n to \nsupport native compiling to build the project this tutorial creates. \n\n\n\n\n\n\nNewt New\n\n\nChoose a project name. For this tutorial we will call this project \nmyproj\n.\nEnter the \nnewt new myproj\n command. \n\n\n$ newt new myproj\nDownloading project skeleton from apache/incubator-mynewt-blinky...\nInstalling skeleton in myproj...\nProject myproj successfully crea
ted.\n\n\n\n\n\n\n\nNewt populates this new project with a base skeleton of a new Apache Mynewt \nproject. It has the following structure. \n\n\nNote\n: If you do not have \ntree\n, install it by running \nbrew install tree\n.\n\n\n$ cd myproj\n$ tree \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\u00a0\u00a0 \u2514\u2500\u2500 blinky\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 pkg.yml\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 src\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 main.c\n\u251c\u2500\u2500 project.yml\n\u2514\u2500\u2500 targets\n \u251c\u2500\u2500 my_blinky_sim\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 pkg.yml\n \u2502\u00a0\u00a0 \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, 11 files\n\n\n\n\n\n\n\nThe Newt tool has installed the base files for a
project comprising the following:\n\n\n\n\nThe file \nproject.yml\n contains the repository list that the project uses to fetch\nits packages. Your project is a collection of repositories. In this case, the project just\ncomprises the core mynewt repository. Later you will add more repositories\nto include other mynewt components.\n\n\nThe file \napps/blinky/pkg.yml\n contains the description of your application\nand its package dependencies.\n\n\nA \ntarget\n directory containing \nmy_blinky_sim\n, a target descriptor used to\nbuild a version of myproj. Use \nnewt target show\n to see available build \ntargets.\n\n\nA non-buildable target called \nunittest\n. This is used internally by \nnewt\n and is not a formal build target.\n\n\n\n\nNOTE:\n The actual code and package files are not installed \n(except the template for \nmain.c\n). See the next step for installing the packages.\n\n\nNOTE:\n By default newt uses the code in the master branch. This is the latest stable\ncode
for newt. If you need to use a different branch, you can set this in the project.yml\nfile. \n\n\nrepository.apache-mynewt-core:\n type: github\n vers: 1-latest\n user: apache\n repo: incubator-mynewt-core\n\n\n\n\n\nChanging to 1-dev will put you on the develop branch. \nThe Develop Branch may not be stable and you may encounter bugs or other problems.\n\n\n\n\nNewt Install\n\n\nOnce you've switched into your new project's directory, the next step is to fetch\nany dependencies this project has. By default, all Newt projects rely on a\nsingle remote repository, apache-mynewt-core. The \nnewt install\n command will\nfetch this repository.\n\n\n$ newt install\napache-mynewt-core\n\n\n\n\n\nNOTE:\n \napache-mynewt-core\n may take a while to download. To see progress,\nuse the \n-v\n (verbose) option to install. \n\n\n\n\nOnce \nnewt install\n has successfully finished, the contents of \napache-mynewt-core\n will have been downloaded into your local directory. You can v
iew them by issuing the following commands in the base directory of the new project. The actual output will depend on what is in the latest 'master' branch you have pulled from.\n\n\n$ tree -L 2 repos/apache-mynewt-core/\n\nrepos/apache-mynewt-core/\n\u251c\u2500\u2500 CODING_STANDARDS.md\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 RELEASE_NOTES.md\n\u251c\u2500\u2500 apps\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 blecent\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 blehci\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bleprph\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bleprph_oic\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 blesplit\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bletest\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bletiny\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bleuart\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 boot\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fat2native\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 ffs2native\n\u25
02\u00a0\u00a0 \u251c\u2500\u2500 ocf_sample\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 slinky\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 slinky_oic\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 spitest\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 splitty\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 testbench\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 timtest\n\u251c\u2500\u2500 boot\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 boot_serial\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bootutil\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 split\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 split_app\n\u251c\u2500\u2500 compiler\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 arm-none-eabi-m0\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 arm-none-eabi-m4\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 gdbmacros\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mips\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 sim\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 sim-mips\n\u251c\u2500\u2500 crypto\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mbedtls\n\u25
02\u00a0\u00a0 \u2514\u2500\u2500 tinycrypt\n\u251c\u2500\u2500 docs\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 doxygen.xml\n\u251c\u2500\u2500 encoding\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 base64\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 cborattr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 json\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 tinycbor\n\u251c\u2500\u2500 fs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 disk\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fatfs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fcb\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 fs\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 nffs\n\u251c\u2500\u2500 hw\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 bsp\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 cmsis-core\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 drivers\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 hal\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mcu\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 scripts\n\u251c\u2500\u2500 kernel\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 os\n\u251c\u2500\u2500 libc\n\u2502\u00a0\u00a0 \u2514\u250
0\u2500 baselibc\n\u251c\u2500\u2500 mgmt\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 imgmgr\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mgmt\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 newtmgr\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 oicmgr\n\u251c\u2500\u2500 net\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 ip\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 nimble\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 oic\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 wifi\n\u251c\u2500\u2500 project.yml\n\u251c\u2500\u2500 repository.yml\n\u251c\u2500\u2500 sys\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 config\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 console\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 coredump\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 defs\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 flash_map\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 id\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 log\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mfg\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 reboot\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 shell\n\u2502\u00a0\u00a0 \u251c\u2
500\u2500 stats\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 sysinit\n\u251c\u2500\u2500 targets\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 unittest\n\u251c\u2500\u2500 test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 crash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 flash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 runtest\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 testutil\n\u251c\u2500\u2500 time\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 datetime\n\u2514\u2500\u2500 util\n \u251c\u2500\u2500 cbmem\n \u251c\u2500\u2500 crc\n \u2514\u2500\u2500 mem\n\n94 directories, 9 files\n\n\n\n\n\nAs you can see, the core of the Apache Mynewt operating system has been brought \ninto your local directory. \n\n\n\n\nTest the project's packages\n\n\nYou have already built your first basic project. You can ask Newt to execute the unit tests in a package. For example, to test the \nsys/config\n package in the \napache-mynewt-core\n repo, call newt as shown below.\n\n\n$ newt test @apache-mynewt-core/sys/config\
nTesting package @apache-mynewt-core/sys/config/test-fcb\nCompiling bootutil_misc.c\nCompiling image_ec.c\nCompiling image_rsa.c\nCompiling image_validate.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nTesting package @apache-mynewt-core/sys/config/test-nffs\nCompiling repos/apache-mynewt-core/encoding/base64/src/hex.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_cli.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_dirent.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_mkdir.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_mount.c\nCompiling repos/apache-mynewt-core/encoding/base64/src/base64.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_file.c\nCompiling repos/apache-mynewt-core/fs/disk/src/disk.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_nmgr.c\nCompiling repos/a
pache-mynewt-core/fs/fs/src/fsutil.c\nCompiling repos/apache-mynewt-core/fs/nffs/src/nffs.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nPassed tests: [sys/config/test-fcb sys/config/test-nffs]\nAll tests passed\n\n\n\n\n\nNOTE:\n If you've installed the latest gcc using homebrew on your Mac, you will likely be running gcc-6. Make sure you have adjusted the compiler.yml configuration to reflect that as noted in \nNative Install Option\n. You can choose to downgrade to gcc-5 in order to use the default gcc compiler configuration for MyNewt.\n\n\nNOTE:\n If you are running the standard gcc for 64-bit machines, it does not support 32-bit. In that case you will see compilation errors. You need to install multiboot gcc (e.g. gcc-multilib if you running on a 64-bit Ubuntu).\n\n\n$ brew
uninstall gcc-6\n$ brew link gcc-5\n\n\n\n\n\n\n\nTo test all the packages in a project, specify \nall\n instead of the package name.\n\n\n$ newt test all\nTesting package @apache-mynewt-core/boot/boot_serial/test\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/boot_test.c\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/testcases/boot_serial_setup.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/boot_boot_serial_test/app/boot/boot_serial/test/boot_boot_serial_test.elf\n\n...lots of compiling and testing...\n\nLinking ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nPassed tests: [boot/boot_serial/test boot/bootutil/test crypto/mbedtls/test encoding/base64/test encoding/cborattr/test encoding/json/test fs/fcb/test fs/nffs/test kernel/os/test net/ip/mn_socket/test net/nimble/host/test net/oic/test sys
/config/test-fcb sys/config/test-nffs sys/flash_map/test sys/log/full/test util/cbmem/test]\nAll tests passed\n\n\n\n\n\n\n\nBuild the Project\n\n\nTo build and run your new application, simply issue the following command:\n\n\n$ newt build my_blinky_sim \nBuilding target targets/my_blinky_sim\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_common.c\nCompiling repos/apache-mynewt-core/hw/drivers/uart/src/uart.c\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c\nCompiling repos/apache-mynewt-core/hw/bsp/native/src/hal_bsp.c\nCompiling repos/apache-mynewt-core/hw/drivers/uart/uart_hal/src/uart_hal.c\nCompiling apps/blinky/src/main.c\n\n ...\n\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nTarget successfully built: targets/my_blinky_sim\n\n\n\n\n\n\n\nRun the Project\n\n\nYou can run the simulated version of your project and see the simulated LED\nblink. If you are using n
ewt docker, use \nnewt run\n to run the simulated binary.\n\n\n$ newt run my_blinky_sim\nLoading app image into slot 1\n ...\nDebugging ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\n ...\nReading symbols from /bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf...done.\n(gdb)\n\n\n\n\n\nType \nr\n at the \n(gdb)\n prompt to run the project. You will see an output indicating that the hal_gpio pin is toggling between 1 and 0 in a simulated blink.\n\n\nIf you natively install the toolchain, you can either use \nnewt run\n or call the binary directly. Generally, \nnewt run\n is the expected way to call things.\n\n\n$ ./bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nhal_gpio set pin 1 to 0\n\n\n\n\n\n\n\nComplete\n\n\nCongratulations, you have created your first project! The blinky application\nis not terribly exciting when it is run in the simulator, as there is no LED to\nblink. Apache Mynewt has a lot more functionality than just running simulated
\napplications. It provides all the features you'll need to cross-compile your\napplication, run it on real hardware and develop a full featured application.\n\n\nIf you're interested in learning more, a good next step is to dig in to one of\nthe \ntutorials\n and get a Mynewt project running on real hardware.\n\n\nHappy Hacking!",
"title": "Create Your First Project"
},
{
@@ -382,7 +382,7 @@
},
{
"location": "/os/get_started/project_create/#test-the-projects-packages",
- "text": "You have already built your first basic project. You can ask Newt to execute the unit tests in a package. For example, to test the libs/os package in the apache-mynewt-core repo, call newt as shown below. $ newt test @apache-mynewt-core/sys/config\nTesting package @apache-mynewt-core/sys/config/test-fcb\nCompiling bootutil_misc.c\nCompiling image_ec.c\nCompiling image_rsa.c\nCompiling image_validate.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nTesting package @apache-mynewt-core/sys/config/test-nffs\nCompiling repos/apache-mynewt-core/encoding/base64/src/hex.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_cli.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_dirent.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_mkdir.c\nCompiling repos/apache-mynewt-co
re/fs/fs/src/fs_mount.c\nCompiling repos/apache-mynewt-core/encoding/base64/src/base64.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_file.c\nCompiling repos/apache-mynewt-core/fs/disk/src/disk.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_nmgr.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fsutil.c\nCompiling repos/apache-mynewt-core/fs/nffs/src/nffs.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nPassed tests: [sys/config/test-fcb sys/config/test-nffs]\nAll tests passed NOTE: If you've installed the latest gcc using homebrew on your Mac, you will likely be running gcc-6. Make sure you have adjusted the compiler.yml configuration to reflect that as noted in Native Install Option . You can choose to downgrade to gcc-5 in order to use the default gcc compiler configurat
ion for MyNewt. NOTE: If you are running the standard gcc for 64-bit machines, it does not support 32-bit. In that case you will see compilation errors. You need to install multiboot gcc (e.g. gcc-multilib if you running on a 64-bit Ubuntu). $ brew uninstall gcc-6\n$ brew link gcc-5 To test all the packages in a project, specify all instead of the package name. $ newt test all\nTesting package @apache-mynewt-core/boot/boot_serial/test\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/boot_test.c\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/testcases/boot_serial_setup.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/boot_boot_serial_test/app/boot/boot_serial/test/boot_boot_serial_test.elf\n\n...lots of compiling and testing...\n\nLinking ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nPasse
d tests: [boot/boot_serial/test boot/bootutil/test crypto/mbedtls/test encoding/base64/test encoding/cborattr/test encoding/json/test fs/fcb/test fs/nffs/test kernel/os/test net/ip/mn_socket/test net/nimble/host/test net/oic/test sys/config/test-fcb sys/config/test-nffs sys/flash_map/test sys/log/full/test util/cbmem/test]\nAll tests passed",
+ "text": "You have already built your first basic project. You can ask Newt to execute the unit tests in a package. For example, to test the sys/config package in the apache-mynewt-core repo, call newt as shown below. $ newt test @apache-mynewt-core/sys/config\nTesting package @apache-mynewt-core/sys/config/test-fcb\nCompiling bootutil_misc.c\nCompiling image_ec.c\nCompiling image_rsa.c\nCompiling image_validate.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nTesting package @apache-mynewt-core/sys/config/test-nffs\nCompiling repos/apache-mynewt-core/encoding/base64/src/hex.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_cli.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_dirent.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_mkdir.c\nCompiling repos/apache-mynewt
-core/fs/fs/src/fs_mount.c\nCompiling repos/apache-mynewt-core/encoding/base64/src/base64.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_file.c\nCompiling repos/apache-mynewt-core/fs/disk/src/disk.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_nmgr.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fsutil.c\nCompiling repos/apache-mynewt-core/fs/nffs/src/nffs.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nPassed tests: [sys/config/test-fcb sys/config/test-nffs]\nAll tests passed NOTE: If you've installed the latest gcc using homebrew on your Mac, you will likely be running gcc-6. Make sure you have adjusted the compiler.yml configuration to reflect that as noted in Native Install Option . You can choose to downgrade to gcc-5 in order to use the default gcc compiler configu
ration for MyNewt. NOTE: If you are running the standard gcc for 64-bit machines, it does not support 32-bit. In that case you will see compilation errors. You need to install multiboot gcc (e.g. gcc-multilib if you running on a 64-bit Ubuntu). $ brew uninstall gcc-6\n$ brew link gcc-5 To test all the packages in a project, specify all instead of the package name. $ newt test all\nTesting package @apache-mynewt-core/boot/boot_serial/test\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/boot_test.c\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/testcases/boot_serial_setup.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/boot_boot_serial_test/app/boot/boot_serial/test/boot_boot_serial_test.elf\n\n...lots of compiling and testing...\n\nLinking ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nPa
ssed tests: [boot/boot_serial/test boot/bootutil/test crypto/mbedtls/test encoding/base64/test encoding/cborattr/test encoding/json/test fs/fcb/test fs/nffs/test kernel/os/test net/ip/mn_socket/test net/nimble/host/test net/oic/test sys/config/test-fcb sys/config/test-nffs sys/flash_map/test sys/log/full/test util/cbmem/test]\nAll tests passed",
"title": "Test the project's packages"
},
{
@@ -392,7 +392,7 @@
},
{
"location": "/os/get_started/project_create/#run-the-project",
- "text": "You can run the simulated version of your project and see the simulated LED\nblink. If you are using newt docker, use newt run to run the simulated binary. $ newt run my_blinky_sim\nNo download script for BSP hw/bsp/native\nDebugging /workspace/bin/my_blinky_sim/apps/blinky/blinky.elf snip \nReading symbols from /bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf...done.\n(gdb) Type r at the (gdb) prompt to run the project. You will see an output indicating that the hal_gpio pin is toggling between 1 and 0 in a simulated blink. If you natively install the toolchain, you can either use newt run or call the binary directly. Generally, newt run is the expected way to call things. $ ./bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nhal_gpio set pin 1 to 0",
+ "text": "You can run the simulated version of your project and see the simulated LED\nblink. If you are using newt docker, use newt run to run the simulated binary. $ newt run my_blinky_sim\nLoading app image into slot 1\n ...\nDebugging ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\n ...\nReading symbols from /bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf...done.\n(gdb) Type r at the (gdb) prompt to run the project. You will see an output indicating that the hal_gpio pin is toggling between 1 and 0 in a simulated blink. If you natively install the toolchain, you can either use newt run or call the binary directly. Generally, newt run is the expected way to call things. $ ./bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nhal_gpio set pin 1 to 0",
"title": "Run the Project"
},
{
@@ -432,7 +432,7 @@
},
{
"location": "/os/get_started/vocabulary/",
- "text": "Concepts\n\n\nThis page is meant to introduce you to some of the concepts inherent to \nthe Apache Mynewt Operating System, and \nNewt\n the tool that stitches a \nproject built on Apache Mynewt together.\n\n\nProject\n\n\nThe project is the base directory of your embedded software tree. It is a \nworkspace that contains a logical collection of source code, for one or \nmore of your applications. A project consists of the following items:\n\n\n\n\nProject Definition: defines project level dependencies, and parameters\n (located in \nproject.yml\n)\n\n\nPackages\n\n\n\n\nPackages\n are described in detail in the section below. \n\n\nHere is an example project definition file from the default Apache Mynewt \nproject: \n\n\n$ more project.yml \n\nsnip\n\nproject.name: \nmy_project\n\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#\nrepositor
y.apache-mynewt-core:\n type: github\n vers: 1-latest\n user: apache\n repo: incubator-mynewt-core\n$ \n\n\n\n\n\nA couple of things to note in the project definition:\n\n\n\n\n\n\nproject.repositories\n: Defines the remote repositories that this project\nrelies upon.\n\n\n\n\n\n\nrepository.apache-mynewt-core\n: Defines the repository information for \nthe \napache-mynewt-core\n repository.\n\n\n\n\n\n\nvers=1-latest\n: Defines the repository version. This string will use the \nlatest code in the 'Master' github branch. To use the latest version in the \ndevelop branch, just change it to \nvers=1-dev\n\n\n\n\n\n\nRepositories are versioned collections of packages. \n\n\nProjects can rely on remote repositories for functionality, and the newt tool \nwill resolve those remote repositories, and download the correct version into \nyour local source tree. Newly fetched repositories are put in the \nrepos\n\ndirectory of your project, and can be referenced throughout the sy
stem by using\nthe \n@\n specifier. \n\n\nBy default, the \n@apache-mynewt-core\n repository is included in every \nproject. Apache Mynewt Core contains all the base functionality of the Apache \nMynewt Operating System, including the Real Time Kernel, Bluetooth Networking \nStack, Flash File System, Console, Shell and Bootloader.\n\n\nNOTE:\n Any project can be converted into a repository by providing it with a \n\nrepository.yml\n file and putting it up onto Github. More information\nabout repositories can be found in the Newt documentation.\n\n\nPackage\n\n\nA package is a collection items that form a fundamental unit in the Mynewt \nOperating System. Packages can be:\n\n\n\n\nApplications\n\n\nLibraries\n\n\nCompiler definitions\n\n\nTargets\n\n\n\n\nA package is identified by having a \npkg.yml\n file in it's base \ndirectory. Here is a sample \npkg.yml\n file for the blinky applicaton:\n\n\n$ more 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/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\nPackages have a few features worth noting:\n\n\n\n\nDependencies: Packages can rely upon other packages, and when they do\n they will inherit their functionality (header files, library definitions, etc.)\n\n\nAPIs: Packages can export named APIs, and they can require that certain \n APIs be present, in order to compile.\n\n\nFeatures: Packages can operate differently depending on what named features are \n present in the system. Packages can also export features to the rest of the \n Mynewt system.\n\n\n\n\nEverything that newt knows about within a project's directory is a package. This \nmakes it very clean and easy to write re-usable components, which
can describe their \nDependencies and APIs to the rest of the system.\n\n\nTarget\n\n\nA target in Apache Mynewt is very similar to a target in \nmake\n. It is the collection\nof parameters that must be passed to Newt in order to generate a reproducible build. A \ntarget represents the top of the build tree, and any packages or parameters specified at \nthe target level, cascade down to all dependencies.\n\n\nTargets are also packages, and are stored in the \ntargets/\n directory at the base \nof your project. Most targets consist of: \n\n\n\n\napp\n: The application to build.\n\n\nbsp\n: The board support package to combine with that application\n\n\nbuild_profile\n: Either \ndebug\n or \noptimized\n. \n\n\n\n\nTargets can also have additional items specified, including: \n\n\n\n\ncflags\n: Any additional compiler flags you might want to specify to the build.\n\n\nfeatures\n: Any system level features you want to enable.\n\n\n\n\nIn order to create and manipulate targets, the \
nnewt\n tool offers a set of helper commands,\nyou can find more information about these by issuing:\n\n\n$ newt target\n\n\nnewt target\nUsage:\n newt target [flags]\n newt target [command]\n\nAvailable Commands:\n config View or populate a target\ns system configuration\n copy Copy target\n create Create a target\n delete Delete target\n dep View target\ns dependency graph\n revdep View target\ns reverse-dependency graph\n set Set target configuration variable\n show View target configuration variables\n\nGlobal Flags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when ex
ecuting commands\n\nUse \nnewt target [command] --help\n for more information about a command.\n\n$ \n\n\n\n\n\nConfiguration\n\n\nThere are a lot of configuration options available when building your application in MyNewt. System Configuration options are set in \na file called \nsyscfg.yml\n and you will find these configuration files throughout the MyNewt packages. While you can edit these\nfiles directly to change some default settings, it is best to override the default settings in a \nsyscfg.yml\n file in your project\ndirectory rather than editing the package configurations directly.\n\n\nTo see all \nall\n the system configuration settings, simply type\n\n\n$ newt target config show \ntarget-name\n\n...\n* PACKAGE: sys/stats\n * Setting: STATS_CLI\n * Description: Expose the \nstat\n shell command.\n * Value: 0\n * Setting: STATS_NAMES\n * Description: Include and report the textual name of each statistic.\n * Value: 0\n * Setting: STATS_NEWTMGR\n * Descrip
tion: Expose the \nstat\n newtmgr command.\n * Value: 0\n...\n$\n\n\n\n\n\nKeep in mind that this will only show the configuration options for any packages that are included in your applicaiton. \n\n\nIf you really want to see \nall\n the available configuration options, you can go rough each package and look at the\n\nsyscfg.yml\n file in each.",
+ "text": "Concepts\n\n\nThis page is meant to introduce you to some of the concepts inherent to \nthe Apache Mynewt Operating System, and \nNewt\n the tool that stitches a \nproject built on Apache Mynewt together.\n\n\nProject\n\n\nThe project is the base directory of your embedded software tree. It is a \nworkspace that contains a logical collection of source code, for one or \nmore of your applications. A project consists of the following items:\n\n\n\n\nProject Definition: defines project level dependencies, and parameters\n (located in \nproject.yml\n)\n\n\nPackages\n\n\n\n\nPackages\n are described in detail in the section below. \n\n\nHere is an example project definition file from the default Apache Mynewt \nproject: \n\n\n$ more project.yml \n\nsnip\n\nproject.name: \nmy_project\n\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#\nrepositor
y.apache-mynewt-core:\n type: github\n vers: 1-latest\n user: apache\n repo: incubator-mynewt-core\n$ \n\n\n\n\n\nA couple of things to note in the project definition:\n\n\n\n\n\n\nproject.repositories\n: Defines the remote repositories that this project\nrelies upon.\n\n\n\n\n\n\nrepository.apache-mynewt-core\n: Defines the repository information for \nthe \napache-mynewt-core\n repository.\n\n\n\n\n\n\nvers=1-latest\n: Defines the repository version. This string will use the \nlatest code in the 'Master' github branch. To use the latest version in the \ndevelop branch, just change it to \nvers=1-dev\n\n\n\n\n\n\nRepositories are versioned collections of packages. \n\n\nProjects can rely on remote repositories for functionality, and the newt tool \nwill resolve those remote repositories, and download the correct version into \nyour local source tree. Newly fetched repositories are put in the \nrepos\n\ndirectory of your project, and can be referenced throughout the sy
stem by using\nthe \n@\n specifier. \n\n\nBy default, the \n@apache-mynewt-core\n repository is included in every \nproject. Apache Mynewt Core contains all the base functionality of the Apache \nMynewt Operating System, including the Real Time Kernel, Bluetooth Networking \nStack, Flash File System, Console, Shell and Bootloader.\n\n\nNOTE:\n Any project can be converted into a repository by providing it with a \n\nrepository.yml\n file and putting it up onto Github. More information\nabout repositories can be found in the Newt documentation.\n\n\nPackage\n\n\nA package is a collection items that form a fundamental unit in the Mynewt \nOperating System. Packages can be:\n\n\n\n\nApplications\n\n\nLibraries\n\n\nCompiler definitions\n\n\nTargets\n\n\n\n\nA package is identified by having a \npkg.yml\n file in it's base \ndirectory. Here is a sample \npkg.yml\n file for the blinky applicaton:\n\n\n$ more 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/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\nPackages have a few features worth noting:\n\n\n\n\nDependencies: Packages can rely upon other packages, and when they do\n they will inherit their functionality (header files, library definitions, etc.)\n\n\nAPIs: Packages can export named APIs, and they can require that certain \n APIs be present, in order to compile.\n\n\n\n\nEverything that newt knows about within a project's directory is a package. This \nmakes it very clean and easy to write re-usable components, which can describe their \nDependencies and APIs to the rest of the system.\n\n\nTarget\n\n\nA target in Apache Mynewt is very similar to a target in \nmake\n. It is the collection\nof paramete
rs that must be passed to Newt in order to generate a reproducible build. A \ntarget represents the top of the build tree, and any packages or parameters specified at \nthe target level, cascade down to all dependencies.\n\n\nTargets are also packages, and are stored in the \ntargets/\n directory at the base \nof your project. Most targets consist of: \n\n\n\n\napp\n: The application to build.\n\n\nbsp\n: The board support package to combine with that application\n\n\nbuild_profile\n: Either \ndebug\n or \noptimized\n. \n\n\n\n\nTargets can also have additional items specified, including: \n\n\n\n\naflags\n: Any additional assembler flags you might want to specify to the build.\n\n\ncflags\n: Any additional compiler flags you might want to specify to the build.\n\n\nlflags\n: Any additional linker flags you might want to specify to the build.\n\n\n\n\nIn order to create and manipulate targets, the \nnewt\n tool offers a set of helper commands,\nyou can find more information about
these by issuing:\n\n\n$ newt target\n\n\nnewt target\nUsage:\n newt target [flags]\n newt target [command]\n\nAvailable Commands:\n config View or populate a target\ns system configuration\n copy Copy target\n create Create a target\n delete Delete target\n dep View target\ns dependency graph\n revdep View target\ns reverse-dependency graph\n set Set target configuration variable\n show View target configuration variables\n\nGlobal Flags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse \nnewt target [command] --help\n for more information about
a command.\n\n$ \n\n\n\n\n\nConfiguration\n\n\nThere are a lot of configuration options available when building your application in MyNewt. System Configuration options are set in \na file called \nsyscfg.yml\n and you will find these configuration files throughout the MyNewt packages. While you can edit these\nfiles directly to change some default settings, it is best to override the default settings in a \nsyscfg.yml\n file in your project\ndirectory rather than editing the package configurations directly.\n\n\nTo see all \nall\n the system configuration settings, simply type\n\n\n$ newt target config show \ntarget-name\n\n...\n* PACKAGE: sys/stats\n * Setting: STATS_CLI\n * Description: Expose the \nstat\n shell command.\n * Value: 0\n * Setting: STATS_NAMES\n * Description: Include and report the textual name of each statistic.\n * Value: 0\n * Setting: STATS_NEWTMGR\n * Description: Expose the \nstat\n newtmgr command.\n * Value: 0\n...\n$\n\n\n\n\n\nKeep
in mind that this will only show the configuration options for any packages that are included in your applicaiton. \n\n\nIf you really want to see \nall\n the available configuration options, you can go rough each package and look at the\n\nsyscfg.yml\n file in each.",
"title": "Concepts"
},
{
@@ -447,12 +447,12 @@
},
{
"location": "/os/get_started/vocabulary/#package",
- "text": "A package is a collection items that form a fundamental unit in the Mynewt \nOperating System. Packages can be: Applications Libraries Compiler definitions Targets A package is identified by having a pkg.yml file in it's base \ndirectory. Here is a sample pkg.yml file for the blinky applicaton: $ more pkg.yml snip \npkg.name: apps/blinky\npkg.type: app\npkg.description: Basic example application which blinks an LED.\npkg.author: Apache Mynewt dev@mynewt.incubator.apache.org \npkg.homepage: http://mynewt.apache.org/ \npkg.keywords:\n\npkg.deps:\n - @apache-mynewt-core/libs/os \n - @apache-mynewt-core/hw/hal \n - @apache-mynewt-core/libs/console/full Packages have a few features worth noting: Dependencies: Packages can rely upon other packages, and when they do\n they will inherit their functionality (header files, library definitions, etc.) APIs: Packages can export named APIs, and they can require that certain \n APIs be
present, in order to compile. Features: Packages can operate differently depending on what named features are \n present in the system. Packages can also export features to the rest of the \n Mynewt system. Everything that newt knows about within a project's directory is a package. This \nmakes it very clean and easy to write re-usable components, which can describe their \nDependencies and APIs to the rest of the system.",
+ "text": "A package is a collection items that form a fundamental unit in the Mynewt \nOperating System. Packages can be: Applications Libraries Compiler definitions Targets A package is identified by having a pkg.yml file in it's base \ndirectory. Here is a sample pkg.yml file for the blinky applicaton: $ more pkg.yml snip \npkg.name: apps/blinky\npkg.type: app\npkg.description: Basic example application which blinks an LED.\npkg.author: Apache Mynewt dev@mynewt.incubator.apache.org \npkg.homepage: http://mynewt.apache.org/ \npkg.keywords:\n\npkg.deps:\n - @apache-mynewt-core/libs/os \n - @apache-mynewt-core/hw/hal \n - @apache-mynewt-core/libs/console/full Packages have a few features worth noting: Dependencies: Packages can rely upon other packages, and when they do\n they will inherit their functionality (header files, library definitions, etc.) APIs: Packages can export named APIs, and they can require that certain \n APIs be
present, in order to compile. Everything that newt knows about within a project's directory is a package. This \nmakes it very clean and easy to write re-usable components, which can describe their \nDependencies and APIs to the rest of the system.",
"title": "Package"
},
{
"location": "/os/get_started/vocabulary/#target",
- "text": "A target in Apache Mynewt is very similar to a target in make . It is the collection\nof parameters that must be passed to Newt in order to generate a reproducible build. A \ntarget represents the top of the build tree, and any packages or parameters specified at \nthe target level, cascade down to all dependencies. Targets are also packages, and are stored in the targets/ directory at the base \nof your project. Most targets consist of: app : The application to build. bsp : The board support package to combine with that application build_profile : Either debug or optimized . Targets can also have additional items specified, including: cflags : Any additional compiler flags you might want to specify to the build. features : Any system level features you want to enable. In order to create and manipulate targets, the newt tool offers a set of helper commands,\nyou can find more information about these by issuing: $ newt target newt targ
et\nUsage:\n newt target [flags]\n newt target [command]\n\nAvailable Commands:\n config View or populate a target s system configuration\n copy Copy target\n create Create a target\n delete Delete target\n dep View target s dependency graph\n revdep View target s reverse-dependency graph\n set Set target configuration variable\n show View target configuration variables\n\nGlobal Flags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default WARN )\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don t output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse newt target [command] --help for more information about a command.\n\n$",
+ "text": "A target in Apache Mynewt is very similar to a target in make . It is the collection\nof parameters that must be passed to Newt in order to generate a reproducible build. A \ntarget represents the top of the build tree, and any packages or parameters specified at \nthe target level, cascade down to all dependencies. Targets are also packages, and are stored in the targets/ directory at the base \nof your project. Most targets consist of: app : The application to build. bsp : The board support package to combine with that application build_profile : Either debug or optimized . Targets can also have additional items specified, including: aflags : Any additional assembler flags you might want to specify to the build. cflags : Any additional compiler flags you might want to specify to the build. lflags : Any additional linker flags you might want to specify to the build. In order to create and manipulate targets, the newt tool offers a set
of helper commands,\nyou can find more information about these by issuing: $ newt target newt target\nUsage:\n newt target [flags]\n newt target [command]\n\nAvailable Commands:\n config View or populate a target s system configuration\n copy Copy target\n create Create a target\n delete Delete target\n dep View target s dependency graph\n revdep View target s reverse-dependency graph\n set Set target configuration variable\n show View target configuration variables\n\nGlobal Flags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default WARN )\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don t output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse newt target [c
ommand] --help for more information about a command.\n\n$",
"title": "Target"
},
{
@@ -481,18 +481,48 @@
"title": "Tutorial categories:"
},
{
+ "location": "/os/tutorials/blinky/",
+ "text": "Blinky, your \"Hello World!\" on a Target Board\n\n\nThe set of Blinky tutorials show you how to create, build, and run a \"Hello World\" application that blinks a LED on the various target boards that Mynewt supports. The tutorials use the same Blinky application from the \nCreating Your First Project\n tutorial. \n\n\nObjective\n\n\nLearn how to use packages from a default application repository of Mynewt to build your first \nHello World\n application (Blinky) on a target board. Once built using the \nnewt\n tool, this application will blink a LED light on the target board.\n\n\nAvailable Tutorials\n\n\nTutorials are available for the following boards:\n\n\n\n\nBlinky on an Arduino Zero\n\n\nBlinky on an Arduino Primo\n\n\nBlinky on an Olimex\n\n\nBlinky on a nRF52\n\n\nBlinky on a RedBear Nano 2\n\n\n\n\nWe also have a tutorial that shows you how to add \nConsole and Shell to the Blinky Application\n.\n\n\n\nPrerequisites\n\n\nEnsure that you meet the foll
owing prerequisites before continuing with one of the tutorials. \n\n\n\n\nHave Internet connectivity to fetch remote Mynewt components.\n\n\nHave a computer to build a Mynewt application and connect to the board over USB.\n\n\nHave a Micro-USB cable to connect the board and the computer.\n\n\nInstall the Newt tool and toolchains (See \nBasic Setup\n).\n\n\nInstall either the Jlink or OpenOCD debugger.\n\n\nCreate a project space (directory structure) and populate it with the core code repository (apache-mynewt-core) or know how to as explained in \nCreating Your First Project\n.\n\n\nRead the Mynewt OS \nConcepts\n section. \n\n\n\n\n\nOverview of Steps\n\n\nThese are the general steps to create, load and run the Blinky application on your board:\n\n\n\n\nCreate a project.\n\n\nDefine the bootloader and Blinky application targets for the board.\n\n\nBuild the bootloader target.\n\n\nBuild the Blinky application target and create an application image.\n\n\nConnect to the board.\n\n\
nLoad the bootloader onto the board.\n\n\nLoad the Blinky application image onto the board.\n\n\nSee the LED on your board blink.\n\n\n\n\n\n\nAfter you try the Blinky application on your boards, checkout out other tutorials to enable additional functionality such as \nremote comms\n on the current board. If you have BLE (Bluetooth Low Energy) chip (e.g. nRF52) on your board, you can try turning it into an \niBeacon\n or \nEddystone Beacon\n! \n\n\nIf you see anything missing or want to send us feedback, please sign up for \nappropriate mailing lists on our \nCommunity Page\n.",
+ "title": "toc"
+ },
+ {
+ "location": "/os/tutorials/blinky/#blinky-your-hello-world-on-a-target-board",
+ "text": "The set of Blinky tutorials show you how to create, build, and run a \"Hello World\" application that blinks a LED on the various target boards that Mynewt supports. The tutorials use the same Blinky application from the Creating Your First Project tutorial.",
+ "title": "Blinky, your \"Hello World!\" on a Target Board"
+ },
+ {
+ "location": "/os/tutorials/blinky/#objective",
+ "text": "Learn how to use packages from a default application repository of Mynewt to build your first Hello World application (Blinky) on a target board. Once built using the newt tool, this application will blink a LED light on the target board.",
+ "title": "Objective"
+ },
+ {
+ "location": "/os/tutorials/blinky/#available-tutorials",
+ "text": "Tutorials are available for the following boards: Blinky on an Arduino Zero Blinky on an Arduino Primo Blinky on an Olimex Blinky on a nRF52 Blinky on a RedBear Nano 2 We also have a tutorial that shows you how to add Console and Shell to the Blinky Application .",
+ "title": "Available Tutorials"
+ },
+ {
+ "location": "/os/tutorials/blinky/#prerequisites",
+ "text": "Ensure that you meet the following prerequisites before continuing with one of the tutorials. Have Internet connectivity to fetch remote Mynewt components. Have a computer to build a Mynewt application and connect to the board over USB. Have a Micro-USB cable to connect the board and the computer. Install the Newt tool and toolchains (See Basic Setup ). Install either the Jlink or OpenOCD debugger. Create a project space (directory structure) and populate it with the core code repository (apache-mynewt-core) or know how to as explained in Creating Your First Project . Read the Mynewt OS Concepts section.",
+ "title": "Prerequisites"
+ },
+ {
+ "location": "/os/tutorials/blinky/#overview-of-steps",
+ "text": "These are the general steps to create, load and run the Blinky application on your board: Create a project. Define the bootloader and Blinky application targets for the board. Build the bootloader target. Build the Blinky application target and create an application image. Connect to the board. Load the bootloader onto the board. Load the Blinky application image onto the board. See the LED on your board blink. After you try the Blinky application on your boards, checkout out other tutorials to enable additional functionality such as remote comms on the current board. If you have BLE (Bluetooth Low Energy) chip (e.g. nRF52) on your board, you can try turning it into an iBeacon or Eddystone Beacon ! If you see anything missing or want to send us feedback, please sign up for \nappropriate mailing lists on our Community Page .",
+ "title": "Overview of Steps"
+ },
+ {
"location": "/os/tutorials/arduino_zero/",
- "text": "Blinky, your \"Hello World!\", on Arduino Zero\n\n\nLearn how to use packages from a default application repository of Mynewt to build your first \nHello World\n application (Blinky) on a target board. Once built using the \nnewt\n tool, this application will blink the LED lights on the target board.\n\n\nThis tutorial describes how to run Mynewt OS on Arduino Zero. Follow these simple steps and your board will be blinking in no time!\n\n\nPrerequisites\n\n\nEnsure that you have met the following prerequisites before continuing with this tutorial:\n\n\n\n\nHave an Arduino Zero board.\n\nNote: There are many flavors of Arduino. Make sure you are using an Arduino Zero. See below for the versions of Arduino Zero that are compatible with this tutorial.\n\n\nHave Internet connectivity to fetch remote Mynewt components.\n\n\nHave a computer to build a Mynewt application and connect to the board over USB.\n\n\nHave a Micro-USB cable to connect the board and the compute
r.\n\n\nInstall the Newt tool and toolchains (See \nBasic Setup\n).\n\n\nCreate a project space (directory structure) and populated it with the core code repository (apache-mynewt-core) or know how to as explained in \nCreating Your First Project\n.\n\n\nRead the Mynewt OS \nConcepts\n section. \n\n\n\n\nThis tutorial uses the Arduino Zero Pro board. The tutorial has been tested on the following three Arduino Zero boards - Zero, M0 Pro, and Zero-Pro.\n\n\n\n\n\n\n\n\nMynewt has not been tested on Arduino M0 which has no internal debugger support.\n\n\n\n\nCreate a Project\n\n\nCreate a new project if you do not have an existing one. You can skip this step and proceed to \nfetch external packages\n if you already created a project. \n\n\nRun the following commands to create a new project: \n\n\n $ mkdir ~/dev\n $ cd ~/dev\n $ newt new myproj\n Downloading project skeleton from apache/incubator-mynewt-blinky...\n Installing skeleton in myproj...\n Project myproj su
ccessfully created.\n $ cd myproj\n $ newt install\n apache-mynewt-core\n $\n\n\n\n\n\n\n\n Fetch External Packages\n\n\nMynewt uses source code provided directly from the chip manufacturer for\nlow level operations. Sometimes this code is licensed only for the specific manufacturer of the chipset and cannot live in the Apache Mynewt repository. That happens to be the case for the Arduino Zero board which uses Atmel SAMD21. Runtime's github repository hosts such external third-party packages and the Newt tool can fetch them.\n\n\nTo fetch the package with MCU support for Atmel SAMD21 for Arduino Zero from the Runtime git repository, you need to add\nthe repository to the \nproject.yml\n file in your base project directory.\n\n\nHere is an example \nproject.yml\n file with the Arduino Zero repository\nadded. The sections with \nmynewt_arduino_zero\n that need to be added to\nyour project file are highlighted.\n\n\n$ more project.yml\nproject.name: \nmy_project\n\n\nprojec
t.repositories:\n - apache-mynewt-core\n\n - mynewt_arduino_zero\n\n\nrepository.apache-mynewt-core:\n type: github\n vers: 1-latest\n user: apache\n repo: incubator-mynewt-core\n\n\nrepository.mynewt_arduino_zero:\n\n type: github\n\n vers: 1-latest\n\n user: runtimeinc\n\n repo: mynewt_arduino_zero\n\n$\n\n\n\n\n\n\nInstall the project dependencies using the \nnewt install\n command (you can specify \n-v\n for verbose output):\n\n\n$ newt install\napache-mynewt-core\nmynewt_arduino_zero\n$\n\n\n\n\n\n\n\nNOTE:\n If there has been a new release of a repo used in your project since you last installed it, the \n1-latest\n version for the repo in the \nproject.yml\n file will refer to the new release and will not match the installed files. In that case you will get an error message saying so and you will need to run \nnewt upgrade\n to overwrite the existing files with the latest codebase.\n\n\n\nYou need to create two targets for the Arduino Zero Pro boa
rd, one for the bootloader and one for the Blinky application.\n\n\n\nRun the following \nnewt target\n commands, from your project directory, to create a bootloader target. We name the target \narduino_boot\n.\n\n\n$ newt target create arduino_boot\n$ newt target set arduino_boot bsp=@mynewt_arduino_zero/hw/bsp/arduino_zero\nTarget targets/arduino_boot successfully created\n$ newt target set arduino_boot app=@apache-mynewt-core/apps/boot\nTarget targets/arduino_boot successfully set target.app to @apache-mynewt-core/apps/boot\n$ newt target set arduino_boot build_profile=optimized\nTarget targets/arduino_boot successfully set target.build_profile to optimized\n$ newt target set arduino_boot syscfg=BSP_ARDUINO_ZERO_PRO=1\nTarget targets/arduino_boot successfully set target.syscfg to BSP_ARDUINO_ZERO_PRO=1\n$\n\n\n\n\n\nNote:\n If you have an Arduino Zero instead of an Arduino Zero Pro or Ard
<TRUNCATED>
[11/11] incubator-mynewt-site git commit: Updated Blinky and Slinky
tutorials with intro summaries,
remove legacy feature references in the tutorials
Posted by ad...@apache.org.
Updated Blinky and Slinky tutorials with intro summaries, remove legacy feature references in the tutorials
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/40899401
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/40899401
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/40899401
Branch: refs/heads/asf-site
Commit: 40899401079f73b0636437de20c89b255ccbf8e7
Parents: 712b19e
Author: aditihilbert <ad...@runtime.io>
Authored: Fri Apr 7 17:20:56 2017 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Fri Apr 7 17:20:56 2017 -0700
----------------------------------------------------------------------
develop/mkdocs/search_index.json | 990 ++++++++++---------
develop/newt/install/newt_linux/index.html | 12 +-
develop/newt/newt_intro/index.html | 2 +-
.../os/core_os/cputime/os_cputime/index.html | 2 +-
.../os/get_started/project_create/index.html | 9 +-
develop/os/get_started/vocabulary/index.html | 6 +-
.../os/modules/bootloader/bootloader/index.html | 119 ++-
develop/os/modules/console/console/index.html | 64 +-
.../os/modules/console/console_read/index.html | 9 +-
develop/os/tutorials/STM32F303/index.html | 54 +-
develop/os/tutorials/add_newtmgr/index.html | 56 +-
develop/os/tutorials/add_shell/index.html | 54 +-
develop/os/tutorials/air_quality_ble/index.html | 48 +-
.../os/tutorials/air_quality_sensor/index.html | 48 +-
develop/os/tutorials/arduino_zero/index.html | 80 +-
develop/os/tutorials/blehci_project/index.html | 88 +-
.../os/tutorials/bleprph/bleprph-adv/index.html | 60 +-
.../os/tutorials/bleprph/bleprph-app/index.html | 64 +-
.../bleprph/bleprph-chr-access/index.html | 60 +-
.../bleprph/bleprph-gap-event/index.html | 60 +-
.../tutorials/bleprph/bleprph-intro/index.html | 60 +-
.../bleprph/bleprph-svc-reg/index.html | 60 +-
develop/os/tutorials/bletiny_project/index.html | 252 ++---
develop/os/tutorials/blinky/index.html | 634 ++++++++++++
develop/os/tutorials/blinky_console/index.html | 64 +-
develop/os/tutorials/blinky_primo/index.html | 80 +-
develop/os/tutorials/eddystone/index.html | 54 +-
develop/os/tutorials/event_queue/index.html | 54 +-
develop/os/tutorials/ibeacon/index.html | 56 +-
develop/os/tutorials/nRF52/index.html | 74 +-
develop/os/tutorials/nrf52_adc/index.html | 52 +-
develop/os/tutorials/olimex/index.html | 77 +-
develop/os/tutorials/pin-wheel-mods/index.html | 52 +-
.../tutorials/project-nrf52-slinky/index.html | 742 ++++++++++++++
.../os/tutorials/project-sim-slinky/index.html | 653 ++++++++++++
develop/os/tutorials/project-slinky/index.html | 218 ++--
.../tutorials/project-stm32-slinky/index.html | 114 +--
.../tutorials/project-target-slinky/index.html | 763 --------------
develop/os/tutorials/rbnano2/index.html | 71 +-
develop/os/tutorials/repo/add_repos/index.html | 75 +-
.../os/tutorials/repo/create_repo/index.html | 50 +-
.../os/tutorials/repo/private_repo/index.html | 52 +-
.../os/tutorials/repo/upgrade_repo/index.html | 48 +-
develop/os/tutorials/tasks_lesson/index.html | 54 +-
develop/os/tutorials/tutorials/index.html | 52 +-
develop/os/tutorials/unit_test/index.html | 52 +-
.../os/tutorials/wi-fi_on_arduino/index.html | 52 +-
develop/sitemap.xml | 24 +-
latest/mkdocs/search_index.json | 990 ++++++++++---------
latest/newt/install/newt_linux/index.html | 12 +-
latest/newt/newt_intro/index.html | 2 +-
latest/os/core_os/cputime/os_cputime/index.html | 2 +-
latest/os/get_started/project_create/index.html | 9 +-
latest/os/get_started/vocabulary/index.html | 6 +-
.../os/modules/bootloader/bootloader/index.html | 119 ++-
latest/os/modules/console/console/index.html | 64 +-
.../os/modules/console/console_read/index.html | 9 +-
latest/os/tutorials/STM32F303/index.html | 54 +-
latest/os/tutorials/add_newtmgr/index.html | 56 +-
latest/os/tutorials/add_shell/index.html | 54 +-
latest/os/tutorials/air_quality_ble/index.html | 48 +-
.../os/tutorials/air_quality_sensor/index.html | 48 +-
latest/os/tutorials/arduino_zero/index.html | 80 +-
latest/os/tutorials/blehci_project/index.html | 88 +-
.../os/tutorials/bleprph/bleprph-adv/index.html | 60 +-
.../os/tutorials/bleprph/bleprph-app/index.html | 64 +-
.../bleprph/bleprph-chr-access/index.html | 60 +-
.../bleprph/bleprph-gap-event/index.html | 60 +-
.../tutorials/bleprph/bleprph-intro/index.html | 60 +-
.../bleprph/bleprph-svc-reg/index.html | 60 +-
latest/os/tutorials/bletiny_project/index.html | 252 ++---
latest/os/tutorials/blinky/index.html | 634 ++++++++++++
latest/os/tutorials/blinky_console/index.html | 64 +-
latest/os/tutorials/blinky_primo/index.html | 80 +-
latest/os/tutorials/eddystone/index.html | 54 +-
latest/os/tutorials/event_queue/index.html | 54 +-
latest/os/tutorials/ibeacon/index.html | 56 +-
latest/os/tutorials/nRF52/index.html | 74 +-
latest/os/tutorials/nrf52_adc/index.html | 52 +-
latest/os/tutorials/olimex/index.html | 77 +-
latest/os/tutorials/pin-wheel-mods/index.html | 52 +-
.../tutorials/project-nrf52-slinky/index.html | 742 ++++++++++++++
.../os/tutorials/project-sim-slinky/index.html | 653 ++++++++++++
latest/os/tutorials/project-slinky/index.html | 218 ++--
.../tutorials/project-stm32-slinky/index.html | 114 +--
.../tutorials/project-target-slinky/index.html | 763 --------------
latest/os/tutorials/rbnano2/index.html | 71 +-
latest/os/tutorials/repo/add_repos/index.html | 75 +-
latest/os/tutorials/repo/create_repo/index.html | 50 +-
.../os/tutorials/repo/private_repo/index.html | 52 +-
.../os/tutorials/repo/upgrade_repo/index.html | 48 +-
latest/os/tutorials/tasks_lesson/index.html | 54 +-
latest/os/tutorials/tutorials/index.html | 52 +-
latest/os/tutorials/unit_test/index.html | 52 +-
latest/os/tutorials/wi-fi_on_arduino/index.html | 52 +-
latest/sitemap.xml | 24 +-
sitemap.xml | 26 +-
v0_9_0/sitemap.xml | 26 +-
98 files changed, 7584 insertions(+), 5416 deletions(-)
----------------------------------------------------------------------
[09/11] incubator-mynewt-site git commit: Updated Blinky and Slinky
tutorials with intro summaries,
remove legacy feature references in the tutorials
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/newt/install/newt_linux/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/install/newt_linux/index.html b/develop/newt/install/newt_linux/index.html
index 5f8cd09..0aad009 100644
--- a/develop/newt/install/newt_linux/index.html
+++ b/develop/newt/install/newt_linux/index.html
@@ -439,10 +439,18 @@
<ul>
<li>
<p>Next, install Go. When installed, Go offers you as a developer a language environment (to compile Go code), construct Go packages (to assemble Go packages) and import Go code (from github). In the next step, you will use the Go commands to import <em>newt</em> repo into your local Go environment.</p>
-<p><strong>Note</strong>: The Newt tool requires Go version 1.6 or later. Depending on the Ubuntu version you have, the following may install an earlier version. In that case, download the latest package of Go 1.6 from <a href="https://golang.org/dl/">https://golang.org/dl/</a>. You can search for more detailed instructions such as installing Go 1.6 on Ubuntu 14.04 which can be found at <a href="https://www.digitalocean.com/community/tutorials/how-to-install-go-1-6-on-ubuntu-14-04">https://www.digitalocean.com/community/tutorials/how-to-install-go-1-6-on-ubuntu-14-04</a>.</p>
+<p><strong>Note</strong>: The Newt tool requires Go version 1.7 or later. Currently, the latest Go version that Ubuntu installs is 1.6. You can run <code>apt-get install golang-1.7-go</code> to install version 1.7. You can also download version 1.7 from <a href="https://golang.org/dl/">https://golang.org/dl/</a>. </p>
</li>
</ul>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ sudo apt-get install golang
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get install golang-1.7-go
+Reading package lists... Done
+ ...
+Unpacking golang-1.7-go (1.7.1-2ubuntu1) ...
+Setting up golang-1.7-go (1.7.1-2ubuntu1) ...
+$
+$sudo ln -s /usr/lib/go-1.7/bin/go /usr/bin/go
+$go version
+go version go1.7.1 linux/amd64
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/newt/newt_intro/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/newt_intro/index.html b/develop/newt/newt_intro/index.html
index 82b7d3c..93a46bb 100644
--- a/develop/newt/newt_intro/index.html
+++ b/develop/newt/newt_intro/index.html
@@ -452,7 +452,7 @@ project.repositories:
#
repository.apache-mynewt-core:
type: github
- vers: 0-latest
+ vers: 1-latest
user: apache
repo: incubator-mynewt-core
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/core_os/cputime/os_cputime/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/cputime/os_cputime/index.html b/develop/os/core_os/cputime/os_cputime/index.html
index 4f872df..7843a9b 100644
--- a/develop/os/core_os/cputime/os_cputime/index.html
+++ b/develop/os/core_os/cputime/os_cputime/index.html
@@ -700,7 +700,7 @@
</div>
<h1 id="cpu-time">CPU Time</h1>
-<p>The MyNewt <code>cputime</code> module provides high resolution time and timer support. This module is intended for use by BSPs, drivers, and network controllers. </p>
+<p>The MyNewt <code>cputime</code> module provides high resolution time and timer support. </p>
<h2 id="description">Description</h2>
<p>The <code>cputime</code> API provides high resolution time and timer support. The module must be initialized, using the <code>os_cputime_init()</code> function, with the clock frequency to use. The module uses the <code>hal_timer</code> API, defined in hal/hal_timer.h, to access the hardware timers. It uses the hardware timer number specified by the <code>OS_CPUTIME_TIMER_NUM</code> system configuration setting.</p>
<h2 id="data-structures">Data Structures</h2>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/get_started/project_create/index.html
----------------------------------------------------------------------
diff --git a/develop/os/get_started/project_create/index.html b/develop/os/get_started/project_create/index.html
index 2f5038e..1a5caaf 100644
--- a/develop/os/get_started/project_create/index.html
+++ b/develop/os/get_started/project_create/index.html
@@ -573,7 +573,7 @@ repos/apache-mynewt-core/
into your local directory. </p>
<p><br></p>
<h3 id="test-the-projects-packages">Test the project's packages</h3>
-<p>You have already built your first basic project. You can ask Newt to execute the unit tests in a package. For example, to test the <code>libs/os</code> package in the <code>apache-mynewt-core</code> repo, call newt as shown below.</p>
+<p>You have already built your first basic project. You can ask Newt to execute the unit tests in a package. For example, to test the <code>sys/config</code> package in the <code>apache-mynewt-core</code> repo, call newt as shown below.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt test @apache-mynewt-core/sys/config
Testing package @apache-mynewt-core/sys/config/test-fcb
Compiling bootutil_misc.c
@@ -662,9 +662,10 @@ Target successfully built: targets/my_blinky_sim
<p>You can run the simulated version of your project and see the simulated LED
blink. If you are using newt docker, use <code>newt run</code> to run the simulated binary.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt run my_blinky_sim
-No download script for BSP hw/bsp/native
-Debugging /workspace/bin/my_blinky_sim/apps/blinky/blinky.elf
-<snip>
+Loading app image into slot 1
+ ...
+Debugging ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf
+ ...
Reading symbols from /bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf...done.
(gdb)
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/get_started/vocabulary/index.html
----------------------------------------------------------------------
diff --git a/develop/os/get_started/vocabulary/index.html b/develop/os/get_started/vocabulary/index.html
index 01868d9..af393c3 100644
--- a/develop/os/get_started/vocabulary/index.html
+++ b/develop/os/get_started/vocabulary/index.html
@@ -413,9 +413,6 @@ pkg.deps:
they will inherit their functionality (header files, library definitions, etc.)</li>
<li>APIs: Packages can export named APIs, and they can require that certain
APIs be present, in order to compile.</li>
-<li>Features: Packages can operate differently depending on what named features are
- present in the system. Packages can also export features to the rest of the
- Mynewt system.</li>
</ul>
<p>Everything that newt knows about within a project's directory is a package. This
makes it very clean and easy to write re-usable components, which can describe their
@@ -434,8 +431,9 @@ of your project. Most targets consist of: </p>
</ul>
<p>Targets can also have additional items specified, including: </p>
<ul>
+<li><code>aflags</code>: Any additional assembler flags you might want to specify to the build.</li>
<li><code>cflags</code>: Any additional compiler flags you might want to specify to the build.</li>
-<li><code>features</code>: Any system level features you want to enable.</li>
+<li><code>lflags</code>: Any additional linker flags you might want to specify to the build.</li>
</ul>
<p>In order to create and manipulate targets, the <em>newt</em> tool offers a set of helper commands,
you can find more information about these by issuing:</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/modules/bootloader/bootloader/index.html
----------------------------------------------------------------------
diff --git a/develop/os/modules/bootloader/bootloader/index.html b/develop/os/modules/bootloader/bootloader/index.html
index bc0dcc9..71cb64e 100644
--- a/develop/os/modules/bootloader/bootloader/index.html
+++ b/develop/os/modules/bootloader/bootloader/index.html
@@ -544,7 +544,7 @@
</div>
<h1 id="bootloader">Bootloader</h1>
-<p>The "bootloader" is the code that loads the Mynewt OS image into memory and conducts some checks before allowing the OS to be run. It manages images for the embedded system and upgrades of those images using protocols over various interfaces (e.g. serial, BLE etc.). Typically, systems with bootloaders have at least two program images coexisting on the same microcontroller, and hence must include branch code that performs a check to see if an attempt to update software is already underway and manage the progress of the process.</p>
+<p>The "bootloader" is the code that loads the Mynewt OS image into memory and conducts some checks before allowing the OS to be run. It manages images for the embedded system and upgrades of those images using protocols over various interfaces (e.g. serial, BLE, etc.). Typically, systems with bootloaders have at least two program images coexisting on the same microcontroller, and hence must include branch code that performs a check to see if an attempt to update software is already underway and manage the progress of the process.</p>
<p>The bootloader in the Apache Mynewt project verifies the cryptographic signature of the firmware image before running it. It maintains a detailed status log for each stage of the boot process. For verification of the authenticity of the OS image, it:</p>
<ul>
<li>Calculates hash of the image.</li>
@@ -590,7 +590,7 @@ characteristics:</p>
<span style="color: #A90D91">uint16_t</span> <span style="color: #000000">ih_tlv_size</span>; <span style="color: #177500">/* Trailing TLVs */</span>
<span style="color: #A90D91">uint8_t</span> <span style="color: #000000">ih_key_id</span>;
<span style="color: #A90D91">uint8_t</span> <span style="color: #000000">_pad1</span>;
- <span style="color: #A90D91">uint16_t</span> <span style="color: #000000">ih_hdr_s<</span> <span style="color: #000000">bok@bok</span>.<span style="color: #000000">net</span>
+ <span style="color: #A90D91">uint16_t</span> <span style="color: #000000">ih_hdr_size</span>;
<span style="color: #A90D91">uint16_t</span> <span style="color: #000000">_pad2</span>;
<span style="color: #A90D91">uint32_t</span> <span style="color: #000000">ih_img_size</span>; <span style="color: #177500">/* Does not include header. */</span>
<span style="color: #A90D91">uint32_t</span> <span style="color: #000000">ih_flags</span>;
@@ -604,12 +604,12 @@ characteristics:</p>
offset of the image itself. This field provides for backwards compatibility in
case of changes to the format of the image header.</p>
<p>The following are the image header flags available.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #633820">#define IMAGE_F_PIC 0x00000001</span>
-<span style="color: #633820">#define IMAGE_F_SHA256 0x00000002 </span><span style="color: #177500">/* Image contains hash TLV */</span><span style="color: #633820"></span>
-<span style="color: #633820">#define IMAGE_F_PKCS15_RSA2048_SHA256 0x00000004 </span><span style="color: #177500">/* PKCS15 w/RSA and SHA */</span><span style="color: #633820"></span>
-<span style="color: #633820">#define IMAGE_F_ECDSA224_SHA256 0x00000008 </span><span style="color: #177500">/* ECDSA256 over SHA256 */</span><span style="color: #633820"></span>
-<span style="color: #633820">#define IMAGE_F_NON_BOOTABLE 0x00000010</span>
-<span style="color: #633820">#define IMAGE_HEADER_SIZE 32</span>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #633820">#define IMAGE_F_PIC 0x00000001</span>
+<span style="color: #633820">#define IMAGE_F_SHA256 0x00000002 </span><span style="color: #177500">/* Image contains hash TLV */</span><span style="color: #633820"></span>
+<span style="color: #633820">#define IMAGE_F_PKCS15_RSA2048_SHA256 0x00000004 </span><span style="color: #177500">/* PKCS15 w/RSA and SHA */</span><span style="color: #633820"></span>
+<span style="color: #633820">#define IMAGE_F_ECDSA224_SHA256 0x00000008 </span><span style="color: #177500">/* ECDSA256 over SHA256 */</span><span style="color: #633820"></span>
+<span style="color: #633820">#define IMAGE_F_NON_BOOTABLE 0x00000010</span>
+<span style="color: #633820">#define IMAGE_HEADER_SIZE 32</span>
</pre></div>
@@ -635,11 +635,10 @@ after the end of the image. For example, security data gets added as a footer at
<p>A Mynewt device's flash is partitioned according to its <em>flash map</em>. At a high
level, the flash map maps numeric IDs to <em>flash areas</em>. A flash area is a
region of disk with the following properties:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">1. An area can be fully erased without affecting any other areas.
-2. A write to one area does not restrict writes to other areas.
-</pre></div>
-
-
+<ol>
+<li>An area can be fully erased without affecting any other areas.</li>
+<li>A write to one area does not restrict writes to other areas.</li>
+</ol>
<p>The boot loader uses the following flash areas:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #633820">#define FLASH_AREA_BOOTLOADER 0</span>
<span style="color: #633820">#define FLASH_AREA_IMAGE_0 1</span>
@@ -731,20 +730,23 @@ An image trailer has the following structure:</p>
<p>These records are at the end of each image slot. The offset immediately
following such a record represents the start of the next flash area.</p>
-<p>Note: "min-write-size" is a property of the flash hardware. If the hardware
+<p>Note: <code>min-write-size</code> is a property of the flash hardware. If the hardware
allows individual bytes to be written at arbitrary addresses, then
-min-write-size is 1. If the hardware only allows writes at even addresses,
-then min-write-size is 2, and so on.</p>
+<code>min-write-size</code> is 1. If the hardware only allows writes at even addresses,
+then <code>min-write-size</code> is 2, and so on.</p>
<p>The fields are defined as follows:</p>
<ol>
<li>
<p>MAGIC: The following 16 bytes, written in host-byte-order:</p>
-<p>const uint32_t boot_img_magic[4] = {
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">const uint32_t boot_img_magic[4] = {
0xf395c277,
0x7fefd260,
0x0f505235,
0x8079b62c,
-};</p>
+};
+</pre></div>
+
+
</li>
<li>
<p>Swap status: A series of single-byte records. Each record corresponds to a
@@ -755,18 +757,18 @@ if the device rebooted before a swap operation completed.</p>
</li>
<li>
<p>Copy done: A single byte indicating whether the image in this slot is
-complete (0x01=done, 0xff=not done).</p>
+complete (<code>0x01=done, 0xff=not done</code>).</p>
</li>
<li>
<p>Image OK: A single byte indicating whether the image in this slot has been
-confirmed as good by the user (0x01=confirmed; 0xff=not confirmed).</p>
+confirmed as good by the user (<code>0x01=confirmed; 0xff=not confirmed</code>).</p>
</li>
</ol>
<p>The boot vector records are structured around the limitations imposed by flash
hardware. As a consequence, they do not have a very intuitive design, and it
is difficult to get a sense of the state of the device just by looking at the
-boot vector. It is better to map all the possible vector states to the swap types (None, Test, Revert)
-via a set of tables. These tables are reproduced below.
+boot vector. It is better to map all the possible vector states to the swap types
+(None, Test, Revert) via a set of tables. These tables are reproduced below.
In these tables, the "pending" and "confirmed" flags are shown for illustrative
purposes; they are not actually present in the boot vector.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">State I
@@ -827,10 +829,11 @@ State IV
a high-level overview of the boot process is presented. Then, the following
sections describe each step of the process in more detail.</p>
<p>Procedure:</p>
-<p>A. Inspect swap status region; is an interrupted swap is being resumed?
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">A. Inspect swap status region; is an interrupted swap is being resumed?
Yes: Complete the partial swap operation; skip to step C.
- No: Proceed to step B.</p>
-<p>B. Insect boot vector; is a swap requested?
+ No: Proceed to step B.
+
+B. Inspect boot vector; is a swap requested?
Yes.
1. Is the requested image valid (integrity and security check)?
Yes.
@@ -841,14 +844,20 @@ sections describe each step of the process in more detail.</p>
a. Erase invalid image.
b. Persist failure of swap procedure to boot vector.
c. Proceed to step C.
- No: Proceed to step C.</p>
-<p>C. Boot into image in slot 0.</p>
+ No: Proceed to step C.
+
+C. Boot into image in slot 0.
+</pre></div>
+
+
<h3 id="image-swapping">Image Swapping</h3>
-<p>The boot loader swaps the contents of the two image slots for two reasons:
- * User has issued an "image test" operation; the image in slot-1 should be
- run once (state II).
- * Test image rebooted without being confirmed; the boot loader should
- revert to the original image currently in slot-1 (state III).</p>
+<p>The boot loader swaps the contents of the two image slots for two reasons:</p>
+<ul>
+<li>User has issued an "image test" operation; the image in slot-1 should be
+ run once (state II).</li>
+<li>Test image rebooted without being confirmed; the boot loader should
+ revert to the original image currently in slot-1 (state III).</li>
+</ul>
<p>If the boot vector indicates that the image in the secondary slot should be
run, the boot loader needs to copy it to the primary slot. The image currently
in the primary slot also needs to be retained in flash so that it can be used
@@ -882,11 +891,12 @@ according to the following procedure:</p>
can be written by the user at a later time. With the image trailer unwritten,
the user can test the image in slot 1 (i.e., transition to state II).</p>
<p>The particulars of step 3 vary depending on whether an image is being tested or
-reverted:
- * test:
- o Write slot0.copy_done = 1
- (should now be in state III)</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">* revert:
+reverted:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">* test:
+ o Write slot0.copy_done = 1
+ (should now be in state III)
+
+* revert:
o Write slot0.magic = BOOT_MAGIC
o Write slot0.copy_done = 1
o Write slot0.image_ok = 1
@@ -899,9 +909,9 @@ reverted:
the middle of an image swap operation. The swap status region consists of a
series of single-byte records. These records are written independently, and
therefore must be padded according to the minimum write size imposed by the
-flash hardware. In the below figure, a min-write-size of 1 is assumed for
+flash hardware. In the below figure, a <code>min-write-size</code> of 1 is assumed for
simplicity. The structure of the swap status region is illustrated below. In
-this figure, a min-write-size of 1 is assumed for simplicity.</p>
+this figure, a <code>min-write-size</code> of 1 is assumed for simplicity.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
@@ -931,11 +941,14 @@ sectors, the flash layout is not compatible with this boot loader. Finally,
reverse the list of indices such that the list starts with index 127 and ends
with 0. The swap status region is a representation of this reversed list.</p>
<p>During a swap operation, each sector index transitions through four separate
-states:
- 0. slot 0: image 0, slot 1: image 1, scratch: N/A
- 1. slot 0: image 0, slot 1: N/A, scratch: image 1 (1->s, erase 1)
- 2. slot 0: N/A, slot 1: image 0, scratch: image 1 (0->1, erase 0)
- 3. slot 0: image 1, slot 1: image 0, scratch: N/A (s->0)</p>
+states:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">0. slot 0: image 0, slot 1: image 1, scratch: N/A
+1. slot 0: image 0, slot 1: N/A, scratch: image 1 (1->s, erase 1)
+2. slot 0: N/A, slot 1: image 0, scratch: image 1 (0->1, erase 0)
+3. slot 0: image 1, slot 1: image 0, scratch: N/A (s->0)
+</pre></div>
+
+
<p>Each time a sector index transitions to a new state, the boot loader writes a
record to the swap status region. Logically, the boot loader only needs one
record per sector index to keep track of the current swap state. However, due
@@ -954,7 +967,7 @@ state 3 | 0x01 | 0x02 | 0x03
<p>The swap status region can accommodate 128 sector indices. Hence, the size of
-the region, in bytes, is 128 * min-write-size * 3. The number 128 is chosen
+the region, in bytes, is <code>128 * min-write-size * 3</code>. The number 128 is chosen
somewhat arbitrarily and will likely be made configurable. The only
requirement for the index count is that is is great enough to account for a
maximum-sized image (i.e., at least as great as the total sector count in an
@@ -1024,12 +1037,14 @@ it had just been started.</p>
primary slot. If the boot loader doesn't perform an image swap, then it
doesn't perform an integrity check.</p>
<p>During the integrity check, the boot loader verifies the following aspects of
-an image:
- * 32-bit magic number must be correct (0x96f3b83c).
- * Image must contain a SHA256 TLV.
- * Calculated SHA256 must matche SHA256 TLV contents.
- * Image <em>may</em> contain a signature TLV. If it does, its contents must be
- verifiable using a key embedded in the boot loader.</p>
+an image:</p>
+<ul>
+<li>32-bit magic number must be correct (0x96f3b83c).</li>
+<li>Image must contain a SHA256 TLV.</li>
+<li>Calculated SHA256 must matche SHA256 TLV contents.</li>
+<li>Image <em>may</em> contain a signature TLV. If it does, its contents must be
+ verifiable using a key embedded in the boot loader.</li>
+</ul>
<h3 id="image-signing-and-verification">Image Signing and Verification</h3>
<p>As indicated above, the final step of the integrity check is signature
verification. The boot loader can have one or more public keys embedded in it
@@ -1039,7 +1054,7 @@ The image signature TLV indicates the index of the key that is has been signed
with. The boot loader uses this index to identify the corresponding public
key.</p>
<p>For information on embedding public keys in the boot loader, as well as
-producing signed images, see: boot/bootutil/signed_images.md </p>
+producing signed images, see: boot/bootutil/signed_images.md</p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/modules/console/console/index.html
----------------------------------------------------------------------
diff --git a/develop/os/modules/console/console/index.html b/develop/os/modules/console/console/index.html
index 19669a7..03a0e16 100644
--- a/develop/os/modules/console/console/index.html
+++ b/develop/os/modules/console/console/index.html
@@ -549,18 +549,13 @@ application. A user typically inputs text from a keyboard and reads the OS outp
monitor. The text are sent as a sequence of characters between the user and the OS. </p>
<p>Support is currently available for console access via the serial port on the hardware board.</p>
<h3 id="description">Description</h3>
-<p>In the Mynewt OS, the console library comes in two versions:</p>
+<p>In the Mynewt OS, the console library comes in three versions:</p>
<ul>
-<li>
-<p>The <code>sys/console/full</code> package implements the complete console functionality and API.</p>
-</li>
-<li>
-<p>The <code>sys/console/stub</code> package implements stubs for the API.</p>
-</li>
+<li>The <code>sys/console/full</code> package implements the complete console functionality and API.</li>
+<li>The <code>sys/console/stub</code> package implements stubs for the API.</li>
+<li>The <code>sys/console/minimal</code> package implements minimal console functionality of reading from and writing to console. It implements the <code>console_read()</code> and <code>console_write()</code> functions and stubs for all the other console functions.</li>
</ul>
-<p>Both packages export the <code>console</code> API, and any package that uses
-the console API must list <code>console</code> as a requirement. For example, the shell package defines the following <code>pkg.yml</code>
-file:</p>
+<p>All the packages export the <code>console</code> API, and any package that uses the console API must list <code>console</code> as a requirement its <code>pkg.yml</code> file: </p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">pkg.name: sys/shell
pkg.deps:
- kernel/os
@@ -572,9 +567,11 @@ pkg.req_apis:
</pre></div>
-<p>The project <code>pkg.yml</code> file specifies the version of the console package to use.
-A project that requires the full console capability must list the <code>sys/console/full</code> package as a dependency
-in its <code>pkg.yml</code> file.</p>
+<p><br>
+The project <code>pkg.yml</code> file also specifies the version of the console package to use.</p>
+<p><br></p>
+<h4 id="using-the-full-console-package">Using the Full Console Package</h4>
+<p>A project that requires the full console capability must list the <code>sys/console/full</code> package as a dependency in its <code>pkg.yml</code> file.</p>
<p>An example is the <code>slinky</code> application. It requires the full console capability and has the following
<code>pkg.yml</code> file: </p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">pkg.name: apps/slinky
@@ -592,22 +589,51 @@ pkg.deps:
</pre></div>
-<p>On the other hand, a project may not have a physical console (e.g. a UART port to connect a terminal to)
-but may have a dependency on a package that has console capability. In this case, you use
-the console stub API and list the <code>sys/console/stub</code> package as a dependency in its <code>pkg.yml</code> file. </p>
-<p>An example is the bootloader project where we want to keep the size of the image small. It includes
+<p><br></p>
+<h4 id="using-the-stub-console-package">Using the Stub Console Package</h4>
+<p>A project that uses console stub API must list the <code>sys/console/stub</code> package as a dependency in its <code>pkg.yml</code> file.</p>
+<p>Examples of when a project would use the console stubs might be:</p>
+<ul>
+<li>A project may not have a physical console (e.g. a UART port to connect a terminal to)
+but may have a dependency on a package that has console capability. </li>
+<li>A bootloader project where we want to keep the size of the image small. It includes
the <code>kernel/os</code> package that can print out messages on a console (e.g. if there is a hard fault).
However, we do not want to use any console I/O capability in this particular bootloader project to
-keep the size small. The project uses the console stub API and has the following <code>pkg.yml</code> file: </p>
+keep the size small. </li>
+</ul>
+<p>The project would use the console stub API and has the following <code>pkg.yml</code> file: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">pkg.name: apps/boot
+pkg.deps:
+ - boot/bootutil
+ - kernel/os
+ - sys/console/stub
+</pre></div>
+
+
+<p><br></p>
+<h4 id="using-the-minimal-console-package">Using the Minimal Console Package</h4>
+<p>There might be projects that need to read and write data on a serial connection but do not need the full console capability. An example might be a project that supports serial image upgrade but does not need full newtmgr capability. The project would use the console minimal API and has the following <code>pkg.yml</code> file: </p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">pkg.name: apps/boot
+pkg.type: app
+pkg.description: Boot loader application.
+pkg.author: "Apache Mynewt <dev@mynewt.incubator.apache.org>"
+pkg.homepage: "http://mynewt.apache.org/"
+pkg.keywords:
+ - loader
+
pkg.deps:
- boot/bootutil
- kernel/os
- sys/console/stub
+
+pkg.deps.BOOT_SERIAL.OVERWRITE:
+ - sys/console/minimal
+ - boot/boot_serial
</pre></div>
-<p>Console has 2 modes for transmit; <em>blocking mode</em> and <em>non-blocking mode</em>. Usually the <em>non-blocking mode</em> is the
+<p><br>
+Console has 2 modes for transmit; <em>blocking mode</em> and <em>non-blocking mode</em>. Usually the <em>non-blocking mode</em> is the
active one; the output buffer is drained by getting TX completion interrupts from hardware, and more data is added
based on these interrupts.</p>
<p><em>Blocking mode</em> is used when we don't want TX completion interrupts. It is used when system crashes, and we still
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/modules/console/console_read/index.html
----------------------------------------------------------------------
diff --git a/develop/os/modules/console/console_read/index.html b/develop/os/modules/console/console_read/index.html
index 8a0f57f..7a079da 100644
--- a/develop/os/modules/console/console_read/index.html
+++ b/develop/os/modules/console/console_read/index.html
@@ -606,7 +606,7 @@
</div>
<h2 id="console_read"><font color="#F2853F" style="font-size:24pt"> console_read </font></h2>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #A90D91">int</span> <span style="color: #000000">console_read</span>(<span style="color: #A90D91">char</span> <span style="color: #000000">*str</span>, <span style="color: #A90D91">int</span> <span style="color: #000000">cnt</span>)
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #A90D91">int</span> <span style="color: #000000">console_read</span>(<span style="color: #A90D91">char</span> <span style="color: #000000">*str</span>, <span style="color: #A90D91">int</span> <span style="color: #000000">cnt</span>, <span style="color: #A90D91">int</span> <span style="color: #000000">*newline</span>)
</pre></div>
@@ -629,6 +629,10 @@ separate lines; once it encounters a newline character, it replaces that with en
<td><code>cnt</code></td>
<td>Maximum number of characters to copy.</td>
</tr>
+<tr>
+<td><code>newline</code></td>
+<td>Pointer to an integer variable that is set to 1 when an newline character is received and set to 0 otherwise.</td>
+</tr>
</tbody>
</table>
<h4 id="returned-values">Returned values</h4>
@@ -641,12 +645,13 @@ available, or if the first received character was '\n'.</p>
<span style="color: #A90D91">struct</span> <span style="color: #000000">os_event</span> <span style="color: #000000">*ev</span>;
<span style="color: #A90D91">char</span> <span style="color: #000000">rx_msg</span>[<span style="color: #1C01CE">128</span>];
<span style="color: #A90D91">int</span> <span style="color: #000000">rx_len</span>;
+ <span style="color: #A90D91">int</span> <span style="color: #000000">newline</span>;
<span style="color: #A90D91">while</span> (<span style="color: #1C01CE">1</span>) {
<span style="color: #000000">ev</span> <span style="color: #000000">=</span> <span style="color: #000000">os_eventq_get</span>(<span style="color: #000000">&task1_evq</span>);
<span style="color: #000000">assert</span>(<span style="color: #000000">ev</span>);
<span style="color: #A90D91">if</span> (<span style="color: #000000">ev->ev_type</span> <span style="color: #000000">==</span> <span style="color: #000000">CONS_EV_TYPE</span>) {
- <span style="color: #000000">rx_len</span> <span style="color: #000000">=</span> <span style="color: #000000">console_read</span>(<span style="color: #000000">rx_msg</span>, <span style="color: #A90D91">sizeof</span>(<span style="color: #000000">rx_msg</span>));
+ <span style="color: #000000">rx_len</span> <span style="color: #000000">=</span> <span style="color: #000000">console_read</span>(<span style="color: #000000">rx_msg</span>, <span style="color: #A90D91">sizeof</span>(<span style="color: #000000">rx_msg</span>), <span style="color: #000000">&newline</span>);
<span style="color: #A90D91">if</span> (<span style="color: #000000">rx_len</span>) {
<span style="color: #A90D91">if</span> (<span style="color: #000000">!strncmp</span>(<span style="color: #000000">rx_msg</span>, <span style="color: #C41A16">"reset"</span>, <span style="color: #000000">rx_len</span>)) {
<span style="color: #000000">assert</span>(<span style="color: #1C01CE">0</span>);
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/STM32F303/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/STM32F303/index.html b/develop/os/tutorials/STM32F303/index.html
index 02d9003..28c8948 100644
--- a/develop/os/tutorials/STM32F303/index.html
+++ b/develop/os/tutorials/STM32F303/index.html
@@ -232,14 +232,14 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
<ul>
+
+
<li >
<a href="../arduino_zero/">Blinky on Arduino Zero</a>
@@ -331,8 +331,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -340,7 +343,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -348,7 +351,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -356,20 +359,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -377,7 +375,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -385,7 +383,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -393,18 +391,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -412,15 +407,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -536,7 +534,7 @@
- <li>» <a href="../arduino_zero/">Project Blinky</a></li>
+ <li>» <a href="../blinky/">Project Blinky</a></li>
@@ -716,7 +714,7 @@ $ newt -v load stmf3_blinky
<p><br></p>
<h3 id="want-more">Want more?</h3>
<p>Want to make your board do something a little more exciting with the LEDs? Then try making the modifications to the Blinky app to make it a <a href="../pin-wheel-mods/">pin-wheel app</a> and you can light all the LEDs in a pin-wheel fashion.</p>
-<p>We have more fun tutorials for you to get your hands dirty. Be bold and try other Blinky-like <a href="../nRF52/">tutorials</a> or try enabling additional functionality such as <a href="../project-target-slinky/">remote comms</a> on the current board.</p>
+<p>We have more fun tutorials for you to get your hands dirty. Be bold and try other Blinky-like <a href="../nRF52/">tutorials</a> or try enabling additional functionality such as <a href="../project-slinky/">remote comms</a> on the current board.</p>
<p>If you see anything missing or want to send us feedback, please do so by signing up for appropriate mailing lists on our <a href="../../../community/">Community Page</a>.</p>
<p>Keep on hacking and blinking!</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/add_newtmgr/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/add_newtmgr/index.html b/develop/os/tutorials/add_newtmgr/index.html
index aef9601..c2666a2 100644
--- a/develop/os/tutorials/add_newtmgr/index.html
+++ b/develop/os/tutorials/add_newtmgr/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,7 +264,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -271,36 +272,31 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
- <li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <li class="active">
+ <a href="./">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
- <li class="active">
- <a href="./">Enable Newt Manager in any app</a>
+ <li >
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -308,7 +304,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,18 +312,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -696,9 +692,9 @@ your device has limited flash memory and cannot support Over-The-Air (OTA) firmw
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../project-stm32-slinky/>
+ <a href=../eddystone/>
<span class="fa fa-arrow-left"></span>
- Previous: Slinky on STM32 board
+ Previous: BLE Eddystone
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/add_shell/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/add_shell/index.html b/develop/os/tutorials/add_shell/index.html
index cfe597e..764f1e1 100644
--- a/develop/os/tutorials/add_shell/index.html
+++ b/develop/os/tutorials/add_shell/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,7 +264,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -271,7 +272,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -279,20 +280,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li class="active">
+ <a href="./">Enable the OS Shell and Console</a>
</li>
@@ -300,15 +296,15 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
- <li class="active">
- <a href="./">Enable the OS Shell and Console</a>
+ <li >
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,18 +312,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -602,8 +598,8 @@ prompt on
</li>
<li class="pull-right">
- <a href=../bletiny_project/>
- Next: BLE app to check stats via console
+ <a href=../tasks_lesson/>
+ Next: Tasks and Priority Management
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/air_quality_ble/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/air_quality_ble/index.html b/develop/os/tutorials/air_quality_ble/index.html
index 5460676..6505425 100644
--- a/develop/os/tutorials/air_quality_ble/index.html
+++ b/develop/os/tutorials/air_quality_ble/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,7 +264,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -271,7 +272,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -279,20 +280,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -300,7 +296,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -308,7 +304,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,18 +312,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/air_quality_sensor/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/air_quality_sensor/index.html b/develop/os/tutorials/air_quality_sensor/index.html
index 876db13..22a8817 100644
--- a/develop/os/tutorials/air_quality_sensor/index.html
+++ b/develop/os/tutorials/air_quality_sensor/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,7 +264,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -271,7 +272,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -279,20 +280,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -300,7 +296,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -308,7 +304,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,18 +312,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/arduino_zero/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/arduino_zero/index.html b/develop/os/tutorials/arduino_zero/index.html
index 6029eff..4c7eeb8 100644
--- a/develop/os/tutorials/arduino_zero/index.html
+++ b/develop/os/tutorials/arduino_zero/index.html
@@ -232,14 +232,14 @@
- <li><a href="
- ./
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
<ul>
+
+
<li class="active">
<a href="./">Blinky on Arduino Zero</a>
@@ -317,8 +317,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -326,7 +329,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -334,7 +337,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -342,20 +345,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -363,7 +361,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -371,7 +369,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -379,18 +377,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -398,15 +393,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -526,7 +524,7 @@
- <li>» Project Blinky</li>
+ <li>» <a href="../blinky/">Project Blinky</a></li>
@@ -539,19 +537,12 @@
</div>
<h2 id="blinky-your-hello-world-on-arduino-zero">Blinky, your "Hello World!", on Arduino Zero</h2>
-<p>Learn how to use packages from a default application repository of Mynewt to build your first <em>Hello World</em> application (Blinky) on a target board. Once built using the <em>newt</em> tool, this application will blink the LED lights on the target board.</p>
-<p>This tutorial describes how to run Mynewt OS on Arduino Zero. Follow these simple steps and your board will be blinking in no time!</p>
+<p>This tutorial shows you how to create, build and run the Blinky application on an Arduino Zero board.</p>
<h3 id="prerequisites">Prerequisites</h3>
-<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
<ul>
+<li>Meet the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
<li>Have an Arduino Zero board.<br />
Note: There are many flavors of Arduino. Make sure you are using an Arduino Zero. See below for the versions of Arduino Zero that are compatible with this tutorial.</li>
-<li>Have Internet connectivity to fetch remote Mynewt components.</li>
-<li>Have a computer to build a Mynewt application and connect to the board over USB.</li>
-<li>Have a Micro-USB cable to connect the board and the computer.</li>
-<li>Install the Newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
-<li>Create a project space (directory structure) and populated it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.</li>
-<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section. </li>
</ul>
<p>This tutorial uses the Arduino Zero Pro board. The tutorial has been tested on the following three Arduino Zero boards - Zero, M0 Pro, and Zero-Pro.</p>
<p><img src="https://www.arduino.cc/en/uploads/Main/Zero_Usb_Ports.jpg" alt="Drawing" style="width: 390px;"/>
@@ -848,17 +839,8 @@ Continuing.
<p>If you want the image to run without the debugger connected, simply quit the
debugger and restart the board. The image you programmed will come up and run on
the Arduino on the next boot! </p>
-<p><br></p>
-<h3 id="watch-the-led-blink">Watch the LED Blink</h3>
-<p>Congratulations! You have created an Mynewt application running on the
-Arduino Zero. The LED right next to the power LED should be blinking. It is toggled
-by one task running on the Mynewt OS. </p>
-<p>We have more fun tutorials for you to get your hands dirty. Be bold and try other
-Blinky-like <a href="../nRF52/">tutorials</a> or try enabling additional functionality
-such as <a href="../project-target-slinky/">remote comms</a> on the current board.</p>
-<p>If you see anything missing or want to send us feedback, please do so by signing up for
-appropriate mailing lists on our <a href="../../../community/">Community Page</a>.</p>
-<p>Keep on hacking and blinking!</p>
+<p><br>
+You should see the LED blink!</p>
<div class="row">
@@ -868,9 +850,9 @@ appropriate mailing lists on our <a href="../../../community/">Community Page</a
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../tutorials/>
+ <a href=../blinky/>
<span class="fa fa-arrow-left"></span>
- Previous: Tutorials
+ Previous: Project Blinky
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/blehci_project/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/blehci_project/index.html b/develop/os/tutorials/blehci_project/index.html
index 8e9844d..a973afc 100644
--- a/develop/os/tutorials/blehci_project/index.html
+++ b/develop/os/tutorials/blehci_project/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,7 +264,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -271,7 +272,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -279,20 +280,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -300,7 +296,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -308,7 +304,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,18 +312,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -493,18 +489,15 @@ support native compiling to build the project this tutorial creates. </li>
</ul>
<p><br></p>
<h3 id="create-a-project">Create a project</h3>
-<p>Use the Newt tool to create a new project directory containing a skeletal Mynewt framework. Change into the newly created directory. Make sure the downloaded version is 0.9.0 or later.</p>
+<p>Use the Newt tool to create a new project directory containing a skeletal Mynewt framework. Change into the newly created directory. </p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt new blehciproj
Downloading project skeleton from apache/incubator-mynewt-blinky...
Installing skeleton in blehciproj ...
Project blehciproj successfully created.
$ cd mblehciproj
-$ newt install -v
+$ newt install
apache-mynewt-core
-Downloading repository description for apache-mynewt-core... success!
-...
-apache-mynewt-core successfully installed version 0.9.0-none
</pre></div>
@@ -548,13 +541,14 @@ $ newt target set myble2 build_profile=optimized
<p>Then build the two targets.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt build nrf52_boot
<snip>
-App successfully built: ./bin/nrf52_boot/apps/boot/boot.elf
+Linking ~/dev/blehciproj/bin/targets/nrf52_boot/app/apps/boot/boot.elf
+Target successfully built: targets/nrf52_boot
+
$ newt build myble2
-Compiling hci_common.c
-Compiling util.c
-Archiving nimble.a
-Compiling os.c
<snip>
+Linking ~/dev/blehciproj/bin/targets/myble2/app/apps/blehci/blehci.elf
+Target successfully built: targets/myble2
+$
</pre></div>
@@ -562,15 +556,25 @@ Compiling os.c
<h3 id="create-the-app-image">Create the app image</h3>
<p>Generate a signed application image for the <code>myble2</code> target. The version number is arbitrary.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt create-image myble2 1.0.0
-App image succesfully generated: ./bin/makerbeacon/apps/bletiny/bletiny.img
-Build manifest: ./bin/makerbeacon/apps/bletiny/manifest.json
+App image succesfully generated: ~/dev/blehciproj/bin/targets/myble2/app/apps/bletiny/bletiny.img
</pre></div>
<p><br></p>
-<h3 id="load-the-image">Load the image</h3>
+<h3 id="load-the-bootloader-and-the-application-image">Load the bootloader and the application image</h3>
<p>Make sure the USB connector is in place and the power LED on the board is lit. Use the Power ON/OFF switch to reset the board after loading the image.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt -v load myble
+<p>Load the bootloader:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load nrf52_boot
+Loading bootloader
+$
+</pre></div>
+
+
+<p><br>
+Load the application image:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load myble2
+Loading app image into slot 1
+$
</pre></div>
@@ -635,9 +639,9 @@ eir_len 23
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../eddystone/>
+ <a href=../bleprph/bleprph-app/>
<span class="fa fa-arrow-left"></span>
- Previous: BLE Eddystone
+ Previous: BLE Peripheral App
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/bleprph/bleprph-adv/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/bleprph/bleprph-adv/index.html b/develop/os/tutorials/bleprph/bleprph-adv/index.html
index ce1114e..688efbf 100644
--- a/develop/os/tutorials/bleprph/bleprph-adv/index.html
+++ b/develop/os/tutorials/bleprph/bleprph-adv/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,19 @@
+
+
+ <li ><a href="../../project-slinky/">Project Slinky for Remote Comms</a>
+
+
+ </li>
+
+
+
+
+
<li >
- <a href="../../tasks_lesson/">Tasks and Priority Management</a>
+ <a href="../../ibeacon/">BLE iBeacon</a>
</li>
@@ -263,7 +272,7 @@
<li >
- <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../../eddystone/">BLE Eddystone</a>
</li>
@@ -271,7 +280,7 @@
<li >
- <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
@@ -279,20 +288,15 @@
<li >
- <a href="../../event_queue/">Events and Event Queues</a>
+ <a href="../../add_shell/">Enable the OS Shell and Console</a>
</li>
-
-
- <li><a href="
- ../../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -300,7 +304,7 @@
<li >
- <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -308,7 +312,15 @@
<li >
- <a href="../../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../event_queue/">Events and Event Queues</a>
</li>
@@ -381,22 +393,6 @@
<li >
- <a href="../../ibeacon/">BLE iBeacon</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../../eddystone/">BLE Eddystone</a>
- </li>
-
-
-
-
-
- <li >
<a href="../../blehci_project/">BLE HCI interface</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/bleprph/bleprph-app/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/bleprph/bleprph-app/index.html b/develop/os/tutorials/bleprph/bleprph-app/index.html
index 97b571a..220651a 100644
--- a/develop/os/tutorials/bleprph/bleprph-app/index.html
+++ b/develop/os/tutorials/bleprph/bleprph-app/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,19 @@
+
+
+ <li ><a href="../../project-slinky/">Project Slinky for Remote Comms</a>
+
+
+ </li>
+
+
+
+
+
<li >
- <a href="../../tasks_lesson/">Tasks and Priority Management</a>
+ <a href="../../ibeacon/">BLE iBeacon</a>
</li>
@@ -263,7 +272,7 @@
<li >
- <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../../eddystone/">BLE Eddystone</a>
</li>
@@ -271,7 +280,7 @@
<li >
- <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
@@ -279,20 +288,15 @@
<li >
- <a href="../../event_queue/">Events and Event Queues</a>
+ <a href="../../add_shell/">Enable the OS Shell and Console</a>
</li>
-
-
- <li><a href="
- ../../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -300,7 +304,7 @@
<li >
- <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -308,7 +312,15 @@
<li >
- <a href="../../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../event_queue/">Events and Event Queues</a>
</li>
@@ -381,22 +393,6 @@
<li >
- <a href="../../ibeacon/">BLE iBeacon</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../../eddystone/">BLE Eddystone</a>
- </li>
-
-
-
-
-
- <li >
<a href="../../blehci_project/">BLE HCI interface</a>
</li>
@@ -610,8 +606,8 @@ happen on the device as well.</p>
</li>
<li class="pull-right">
- <a href=../../ibeacon/>
- Next: BLE iBeacon
+ <a href=../../blehci_project/>
+ Next: BLE HCI interface
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/bleprph/bleprph-chr-access/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/bleprph/bleprph-chr-access/index.html b/develop/os/tutorials/bleprph/bleprph-chr-access/index.html
index 37dc1ea..0461c35 100644
--- a/develop/os/tutorials/bleprph/bleprph-chr-access/index.html
+++ b/develop/os/tutorials/bleprph/bleprph-chr-access/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,19 @@
+
+
+ <li ><a href="../../project-slinky/">Project Slinky for Remote Comms</a>
+
+
+ </li>
+
+
+
+
+
<li >
- <a href="../../tasks_lesson/">Tasks and Priority Management</a>
+ <a href="../../ibeacon/">BLE iBeacon</a>
</li>
@@ -263,7 +272,7 @@
<li >
- <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../../eddystone/">BLE Eddystone</a>
</li>
@@ -271,7 +280,7 @@
<li >
- <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
@@ -279,20 +288,15 @@
<li >
- <a href="../../event_queue/">Events and Event Queues</a>
+ <a href="../../add_shell/">Enable the OS Shell and Console</a>
</li>
-
-
- <li><a href="
- ../../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -300,7 +304,7 @@
<li >
- <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -308,7 +312,15 @@
<li >
- <a href="../../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../event_queue/">Events and Event Queues</a>
</li>
@@ -381,22 +393,6 @@
<li >
- <a href="../../ibeacon/">BLE iBeacon</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../../eddystone/">BLE Eddystone</a>
- </li>
-
-
-
-
-
- <li >
<a href="../../blehci_project/">BLE HCI interface</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/bleprph/bleprph-gap-event/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/bleprph/bleprph-gap-event/index.html b/develop/os/tutorials/bleprph/bleprph-gap-event/index.html
index fd9b3b7..f8dbe91 100644
--- a/develop/os/tutorials/bleprph/bleprph-gap-event/index.html
+++ b/develop/os/tutorials/bleprph/bleprph-gap-event/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,19 @@
+
+
+ <li ><a href="../../project-slinky/">Project Slinky for Remote Comms</a>
+
+
+ </li>
+
+
+
+
+
<li >
- <a href="../../tasks_lesson/">Tasks and Priority Management</a>
+ <a href="../../ibeacon/">BLE iBeacon</a>
</li>
@@ -263,7 +272,7 @@
<li >
- <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../../eddystone/">BLE Eddystone</a>
</li>
@@ -271,7 +280,7 @@
<li >
- <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
@@ -279,20 +288,15 @@
<li >
- <a href="../../event_queue/">Events and Event Queues</a>
+ <a href="../../add_shell/">Enable the OS Shell and Console</a>
</li>
-
-
- <li><a href="
- ../../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -300,7 +304,7 @@
<li >
- <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -308,7 +312,15 @@
<li >
- <a href="../../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../event_queue/">Events and Event Queues</a>
</li>
@@ -381,22 +393,6 @@
<li >
- <a href="../../ibeacon/">BLE iBeacon</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../../eddystone/">BLE Eddystone</a>
- </li>
-
-
-
-
-
- <li >
<a href="../../blehci_project/">BLE HCI interface</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/bleprph/bleprph-intro/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/bleprph/bleprph-intro/index.html b/develop/os/tutorials/bleprph/bleprph-intro/index.html
index 141640a..7ff4d3e 100644
--- a/develop/os/tutorials/bleprph/bleprph-intro/index.html
+++ b/develop/os/tutorials/bleprph/bleprph-intro/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,19 @@
+
+
+ <li ><a href="../../project-slinky/">Project Slinky for Remote Comms</a>
+
+
+ </li>
+
+
+
+
+
<li >
- <a href="../../tasks_lesson/">Tasks and Priority Management</a>
+ <a href="../../ibeacon/">BLE iBeacon</a>
</li>
@@ -263,7 +272,7 @@
<li >
- <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../../eddystone/">BLE Eddystone</a>
</li>
@@ -271,7 +280,7 @@
<li >
- <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
@@ -279,20 +288,15 @@
<li >
- <a href="../../event_queue/">Events and Event Queues</a>
+ <a href="../../add_shell/">Enable the OS Shell and Console</a>
</li>
-
-
- <li><a href="
- ../../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -300,7 +304,7 @@
<li >
- <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -308,7 +312,15 @@
<li >
- <a href="../../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../event_queue/">Events and Event Queues</a>
</li>
@@ -381,22 +393,6 @@
<li >
- <a href="../../ibeacon/">BLE iBeacon</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../../eddystone/">BLE Eddystone</a>
- </li>
-
-
-
-
-
- <li >
<a href="../../blehci_project/">BLE HCI interface</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/develop/os/tutorials/bleprph/bleprph-svc-reg/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/bleprph/bleprph-svc-reg/index.html b/develop/os/tutorials/bleprph/bleprph-svc-reg/index.html
index 6535a13..af4fe01 100644
--- a/develop/os/tutorials/bleprph/bleprph-svc-reg/index.html
+++ b/develop/os/tutorials/bleprph/bleprph-svc-reg/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,19 @@
+
+
+ <li ><a href="../../project-slinky/">Project Slinky for Remote Comms</a>
+
+
+ </li>
+
+
+
+
+
<li >
- <a href="../../tasks_lesson/">Tasks and Priority Management</a>
+ <a href="../../ibeacon/">BLE iBeacon</a>
</li>
@@ -263,7 +272,7 @@
<li >
- <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../../eddystone/">BLE Eddystone</a>
</li>
@@ -271,7 +280,7 @@
<li >
- <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
@@ -279,20 +288,15 @@
<li >
- <a href="../../event_queue/">Events and Event Queues</a>
+ <a href="../../add_shell/">Enable the OS Shell and Console</a>
</li>
-
-
- <li><a href="
- ../../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -300,7 +304,7 @@
<li >
- <a href="../../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -308,7 +312,15 @@
<li >
- <a href="../../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../../unit_test/">Write a Test Suite for a Package</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../event_queue/">Events and Event Queues</a>
</li>
@@ -381,22 +393,6 @@
<li >
- <a href="../../ibeacon/">BLE iBeacon</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../../eddystone/">BLE Eddystone</a>
- </li>
-
-
-
-
-
- <li >
<a href="../../blehci_project/">BLE HCI interface</a>
</li>
[03/11] incubator-mynewt-site git commit: Updated Blinky and Slinky
tutorials with intro summaries,
remove legacy feature references in the tutorials
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/bletiny_project/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/bletiny_project/index.html b/latest/os/tutorials/bletiny_project/index.html
index 1e5528c..682396a 100644
--- a/latest/os/tutorials/bletiny_project/index.html
+++ b/latest/os/tutorials/bletiny_project/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,7 +264,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -271,7 +272,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -279,20 +280,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -300,7 +296,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -308,42 +304,42 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
- <li class="active">
- <a href="./">BLE app to check stats via console</a>
+ <li >
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
- <li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <li class="active">
+ <a href="./">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -475,11 +471,11 @@
</div>
</div>
- <h2 id="check-stats-on-a-ble-device">Check stats on a BLE device</h2>
+ <h2 id="check-stats-for-a-ble-application-the-nrf52-board">Check stats for a BLE Application the NRF52 Board</h2>
<p><br></p>
<p>This tutorial explains how to run an example BLE app on a board and command it to scan and spew some stats. The stats will be seen over a serial port, not a BLE wireless connection.</p>
<p><br></p>
-<h3 id="pre-requisites">Pre-Requisites</h3>
+<h3 id="prerequisites">Prerequisites</h3>
<ul>
<li>Ensure you have installed <a href="../../../newt/install/newt_mac/">newt</a> and that the
newt command is in your system path. </li>
@@ -493,17 +489,13 @@ support native compiling to build the project this tutorial creates. </li>
<p><br></p>
<h3 id="create-a-project">Create a project</h3>
<p>Use the Newt tool to create a new project directory containing a skeletal Mynewt framework. Change into the newly created directory.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt new myapp1
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt new myproj
Downloading project skeleton from apache/incubator-mynewt-blinky...
-Installing skeleton in myapp1...
-Project myapp1 successfully created.
-$ cd myapp1
-
-$ newt install -v
-apache-mynewt-core
-Downloading repository description for apache-mynewt-core... success!
-...
-apache-mynewt-core successfully installed version 0.7.9-none
+Installing skeleton in myproj...
+Project myproj successfully created.
+$ cd myproj
+
+$ newt install
</pre></div>
@@ -555,7 +547,6 @@ targets/myble
app=@apache-mynewt-core/apps/bletiny
bsp=@apache-mynewt-core/hw/bsp/nrf52dk
build_profile=optimized
- cflags=-DSTATS_NAME_ENABLE
targets/nrf52_boot
app=@apache-mynewt-core/apps/boot
bsp=@apache-mynewt-core/hw/bsp/nrf52dk
@@ -578,24 +569,49 @@ syscfg.vals:
<p>The first configuration value turns on the Shell Task, and we'll need this to get to the shell. The next 2 enable the names for the various stats, and then turns on the stats CLI option.</p>
<h3 id="build-targets">Build targets</h3>
<p>Then build the two targets.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt build nrf52_boot
-<snip>
-App successfully built: ./bin/nrf52_boot/apps/boot/boot.elf
-$ newt build myble
-Compiling hci_common.c
-Compiling util.c
-Archiving nimble.a
-Compiling os.c
-<snip>
+<p>Run the <code>newt build nrf52_boot</code> command to build the bootloader:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">Building target targets/nrf52_boot
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/loader.c
+Compiling repos/apache-mynewt-core/apps/boot/src/boot.c
+
+Archiving sys_sysinit.a
+Archiving util_mem.a
+Linking ~/myproj/bin/targets/nrf52_boot/app/apps/boot/boot.elf
+Target successfully built: targets/nrf52_boot
+</pre></div>
+
+
+<p><br>
+Run the <code>newt build myble</code> command to build the bletiny application:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> newt build myble
+Building target targets/myble
+Compiling repos/apache-mynewt-core/encoding/base64/src/base64.c
+Compiling repos/apache-mynewt-core/encoding/base64/src/hex.c
+Compiling repos/apache-mynewt-core/hw/bsp/nrf52dk/src/hal_bsp.c
+Compiling repos/apache-mynewt-core/apps/bletiny/src/parse.c
+Compiling repos/apache-mynewt-core/apps/bletiny/src/misc.c
+Compiling repos/apache-mynewt-core/apps/bletiny/src/gatt_svr.c
+Compiling repos/apache-mynewt-core/apps/bletiny/src/cmd.c
+Compiling repos/apache-mynewt-core/apps/bletiny/src/main.c
+
+Archiving util_mem.a
+Linking ~/dev/myproj/bin/targets/myble/app/apps/bletiny/bletiny.elf
+Target successfully built: targets/myble
</pre></div>
<p><br></p>
<h3 id="create-the-app-image">Create the app image</h3>
-<p>Generate a signed application image for the <code>myble</code> target. The version number is arbitrary.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt create-image myble 1.0.0
-App image succesfully generated: ./bin/makerbeacon/apps/bletiny/bletiny.img
-Build manifest: ./bin/makerbeacon/apps/bletiny/manifest.json
+<p>Run the <code>newt create-image myble 1.0.0</code> command to generate a signed application image for the <code>myble</code> target. The version number is arbitrary.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt create-image myble 1.0.0
+Compiling bin/targets/myble/generated/src/myble-sysinit-app.c
+Archiving myble-sysinit-app.a
+Linking ~/dev/myproj/bin/targets/myble/app/apps/bletiny/bletiny.elf
+App image succesfully generated: ~/dev/myproj/bin/targets/myble/app/apps/bletiny/bletiny.img
</pre></div>
@@ -614,7 +630,7 @@ If you haven't done so already, make sure you're familiar with the <a href="../.
section. </p>
<p><br></p>
<p>You may use any terminal emulation program to communicate with the board. This tutorial shows a Minicom set up. </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ minicom -D /dev/tty.usbserial-AJ03HAQQ -b 115200
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ minicom -D /dev/tty.usbserial-1a12 -b 115200
</pre></div>
@@ -623,15 +639,15 @@ section. </p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">Welcome to minicom 2.7
OPTIONS:
-Compiled on Nov 24 2015, 16:14:21.
-Port /dev/tty.usbserial-AJ03HAQQ, 09:57:17
+Compiled on Mar 18 2016, 04:59:47.
+Port /dev/tty.usbserial-1a12, 21:24:09
Press Meta-Z for help on special keys
<span style="background-color: #ffffcc">?
-</span>4754:Commands:
-4754: echo ? prompt tasks mempools date
-4756: b
+</span>7471:Commands:
+7471: stat echo ? prompt ticks tasks
+7474: mempools date b
</pre></div>
@@ -651,90 +667,102 @@ This is just a counter kept by the MCU.</p>
<p><strong>Note</strong>: If you want to have a shell prompt by default, simply add the line: <code>CONSOLE_PROMPT: 1</code> to your <code>syscfg.yml</code> file and it will be turned on by default.</p>
<p><br></p>
<p>Try the <code>tasks</code> command. </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="background-color: #ffffcc">27365: > tasks
-</span>Tasks:
-28330: idle (prio: 255, tid: 0, lcheck: 0, ncheck: 0, flags: 0x0, ssize: 64, susage: 34, cswcnt: 233, tot_run_time: 28330ms)
-28333: ble_ll (prio: 0, tid: 1, lcheck: 0, ncheck: 0, flags: 0x0, ssize: 80, susage: 60, cswcnt: 11, tot_run_time: 0ms)
-28336: shell (prio: 1, tid: 2, lcheck: 0, ncheck: 0, flags: 0x0, ssize: 512, susage: 115, cswcnt: 18, tot_run_time: 0ms)
-28339: bletiny (prio: 1, tid: 3, lcheck: 0, ncheck: 0, flags: 0x0, ssize: 512, susage: 138, cswcnt: 456, tot_run_time: 0ms)
-28342: >
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="background-color: #ffffcc">> tasks
+</span>Tasks:
+46682: task pri tid runtime csw stksz stkuse lcheck ncheck fg
+46684: idle 255 0 46683 99 64 31 0 0 0
+46686: main 127 1 1 29 512 156 0 0 0
+46688: ble_ll 0 2 0 12 80 58 0 0 0
+46691: >
</pre></div>
<p><br></p>
<p>Try specifying a BLE related stat, for example <code>ble_ll</code>. You should see some HCI (Host Controller Interface) command counts. </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="background-color: #ffffcc">241133: > stat ble_ll
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="background-color: #ffffcc">113136: > stat ble_ll
</span>hci_cmds: 11
-241888:hci_cmd_errs: 0
-241888:hci_events_sent: 11
-241890:bad_ll_state: 0
-241890:bad_acl_hdr: 0
-241891:no_bufs: 0
-241891:rx_adv_pdu_crc_ok: 0
-241892:rx_adv_pdu_crc_err: 0
-241893:rx_adv_bytes_crc_ok: 0
-241894:rx_adv_bytes_crc_err: 0
-241895:rx_data_pdu_crc_ok: 0
-241895:rx_data_pdu_crc_err: 0
-<snip>
+155545:hci_cmd_errs: 0
+155545:hci_events_sent: 11
+155547:bad_ll_state: 0
+155547:bad_acl_hdr: 0
+155548:no_bufs: 0
+155548:rx_adv_pdu_crc_ok: 0
+155549:rx_adv_pdu_crc_err: 0
+155550:rx_adv_bytes_crc_ok: 0
+155551:rx_adv_bytes_crc_err: 0
+155552:rx_data_pdu_crc_ok: 0
+
+ ...
+
+155564:scan_req_txf: 0
+155565:scan_req_txg: 0
+155565:scan_rsp_txg: 0
+155566: >
</pre></div>
<p><br></p>
-<p>For a more exciting output, try scanning your surroundings for BLE adverstisements. The HCI command shown below specifies a scan duration in ms, sets discovery mode to general (as opposed to limited), the filter to no-whitelist, and type of scan to passive. You should see some scan data flying by!</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="background-color: #ffffcc">139088: > b scan dur=10000 disc=gen filt=no_wl type=passive
-</span>...
-146055:received advertisement; event_type=0 addr_type=1 addr=6b:aa:49:b7:46:e6 length_data=24 rssi=-42 data=0x02:0x01:0x1a:0x14:0xff:0x4c:0x00:0x01:0x00:0x00:0x00:0x00:0x04:0x00:0x00:0x00:0x00:0x00:0x00:0x00:0x00:0x00:0x00:0x00 fields:
-146061: flags=0x1a
-146062: mfg_data=0x4c:0x00:0x01:0x00:0x00:0x00:0x00:0x04:0x00:0x00:0x00:0x00:0x00:0x00:0x00:0x00:0x00:0x00:0x00
-146065:
-146065:received advertisement; event_type=0 addr_type=0 addr=ac:bc:32:ac:4f:e4 length_data=11 rssi=-36 data=0x02:0x01:0x06:0x07:0xff:0x4c:0x00:0x10:0x02:0x0b:0x00 fields:
-146069: flags=0x06
-146070: mfg_data=0x4c:0x00:0x10:0x02:0x0b:0x00
-146071:
-146072:scanning finished
-...
-<snip>
+<p>For a more exciting output, try scanning your surroundings for BLE advertisements. The HCI command shown below specifies a scan duration in ms, scan to passive, and no duplicates. You should see some scan data flying by!</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="background-color: #ffffcc">b scan dur=10000 passive=1 nodups=1
+</span>37266:[ts=291140616ssb, mod=4 level=1] GAP procedure initiated: discovery; own_as
+
+37641:
+38256:received advertisement; event_type=0 rssi=-48 addr_type=1 addr=59:cc:3d:a3:
+38261: flags=0x1a:
+38261: General discoverable mode
+38262: uuids16(complete)=0x1802
+38263: name(complete)=Find Me
+38264:
+38551:scanning finished
</pre></div>
<p><br></p>
<p>If you're still not seeing any output from the device, try running the debugger and see if you are seeing the program execute properly. </p>
<p><br></p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt debug myble
-Debugging ./bin/myble/apps/bletiny/bletiny.elf
-GNU gdb (GNU Tools for ARM Embedded Processors) 7.6.0.20140731-cvs
-Copyright (C) 2013 Free Software Foundation, Inc.
-
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt debug myble
+[~/dev/myproj/repos/apache-mynewt-core/hw/bsp/nrf52dk/nrf52dk_debug.sh ~/dev/myproj/repos/apache-mynewt-core/hw/bsp/nrf52dk ~/dev/wanda/dev/myproj/bin/targets/myble/app/apps/bletiny/bletiny]
+~/dev/myproj/repos/apache-mynewt-core/hw/scripts/common.sh: line 38: [: =: unary operator expected
+Debugging ~/dev/myproj/bin/targets/myble/app/apps/bletiny/bletiny.elf
+GNU gdb (GNU Tools for ARM Embedded Processors) 7.8.0.20150604-cvs
+Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=x86_64-apple-darwin10 --target=arm-none-eabi".
+Type "show configuration" for configuration details.
For bug reporting instructions, please see:
-<http://www.gnu.org/software/gdb/bugs/>...
-Reading symbols from ./bin/myble/apps/bletiny/bletiny.elf...done.
-0x00002f08 in ?? ()
+<http://www.gnu.org/software/gdb/bugs/>.
+Find the GDB manual and other documentation resources online at:
+<http://www.gnu.org/software/gdb/documentation/>.
+For help, type "help".
+Type "apropos word" to search for commands related to "word"...
+Reading symbols from ~/dev/myproj/bin/targets/myble/app/apps/bletiny/bletiny.elf...done.
+os_tick_idle (ticks=1920)
+ at repos/apache-mynewt-core/hw/mcu/nordic/nrf52xxx/src/hal_os_tick.c:200
+200 if (ticks > 0) {
(gdb) monitor reset
Resetting target
(gdb) c
Continuing.
^C
Program received signal SIGTRAP, Trace/breakpoint trap.
-os_tick_idle (ticks=1000) at hal_os_tick.c:117
-117 if (ticks > 0) {
+os_tick_idle (ticks=1907)
+ at repos/apache-mynewt-core/hw/mcu/nordic/nrf52xxx/src/hal_os_tick.c:200
+200 if (ticks > 0) {
(gdb) p g_os_time
-$1 = 37991
+$1 = 13
(gdb) c
Continuing.
^C
Program received signal SIGTRAP, Trace/breakpoint trap.
-os_tick_idle (ticks=1000) at hal_os_tick.c:117
-117 if (ticks > 0) {
+os_tick_idle (ticks=1920)
+ at repos/apache-mynewt-core/hw/mcu/nordic/nrf52xxx/src/hal_os_tick.c:200
+200 if (ticks > 0) {
(gdb) p g_os_time
-$2 = 51888
-(gdb) c
-Continuing.
+$2 = 6611
+(gdb)
</pre></div>
@@ -749,9 +777,9 @@ Continuing.
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../add_shell/>
+ <a href=../event_queue/>
<span class="fa fa-arrow-left"></span>
- Previous: Enable the OS Shell and Console
+ Previous: Events and Event Queues
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/blinky/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/blinky/index.html b/latest/os/tutorials/blinky/index.html
new file mode 100644
index 0000000..233c2c3
--- /dev/null
+++ b/latest/os/tutorials/blinky/index.html
@@ -0,0 +1,634 @@
+<!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/os/tutorials/blinky/"> -->
+ <link rel="shortcut icon" href="../../../img/favicon.ico">
+
+ <title>toc - 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="toc">
+
+
+ <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</a> released (March 22, 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="../../introduction/">Mynewt Documentation</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../../get_started/get_started/">Basic Setup</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../get_started/vocabulary/">Concepts</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../tutorials/">Tutorials</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li class="active"><a href="./">Project Blinky</a>
+
+
+ <ul>
+
+
+
+
+
+ <li >
+ <a href="../arduino_zero/">Blinky on Arduino Zero</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../blinky_primo/">Blinky on Arduino Primo</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../olimex/">Blinky on Olimex</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../STM32F303/">Blinky on STM32F303</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../nRF52/">Blinky on nRF52</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../rbnano2/">Blinky on RedBear Nano 2</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../blinky_console/">Add Console and Shell to Blinky</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../repo/add_repos/">Work with repositories</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../ibeacon/">BLE iBeacon</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../eddystone/">BLE Eddystone</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../blehci_project/">BLE HCI interface</a>
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../air_quality_sensor/
+">Air-quality Sensor project</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../nrf52_adc/">Add an Analog Sensor</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../os_user_guide/">OS User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../../network/ble/ble_intro/
+">BLE User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../newt/newt_intro/">Newt Tool Guide</a>
+
+
+ </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="../tutorials/">Tutorials</a></li>
+
+
+
+ <li>» Project Blinky</li>
+
+
+
+
+
+ </ul>
+</div>
+ </div>
+
+ <h2 id="blinky-your-hello-world-on-a-target-board">Blinky, your "Hello World!" on a Target Board</h2>
+<p>The set of Blinky tutorials show you how to create, build, and run a "Hello World" application that blinks a LED on the various target boards that Mynewt supports. The tutorials use the same Blinky application from the <a href="../../../os/get_started/project_create">Creating Your First Project</a> tutorial. </p>
+<h3 id="objective">Objective</h3>
+<p>Learn how to use packages from a default application repository of Mynewt to build your first <em>Hello World</em> application (Blinky) on a target board. Once built using the <em>newt</em> tool, this application will blink a LED light on the target board.</p>
+<h3 id="available-tutorials">Available Tutorials</h3>
+<p>Tutorials are available for the following boards:</p>
+<ul>
+<li><a href="../arduino_zero/">Blinky on an Arduino Zero</a></li>
+<li><a href="../blinky_primo/">Blinky on an Arduino Primo</a></li>
+<li><a href="../olimex/">Blinky on an Olimex</a></li>
+<li><a href="../nRF52/">Blinky on a nRF52</a></li>
+<li><a href="../rbnano2/">Blinky on a RedBear Nano 2</a></li>
+</ul>
+<p>We also have a tutorial that shows you how to add <a href="../blinky_console/">Console and Shell to the Blinky Application</a>.
+<br></p>
+<h3 id="prerequisites">Prerequisites</h3>
+<p>Ensure that you meet the following prerequisites before continuing with one of the tutorials. </p>
+<ul>
+<li>Have Internet connectivity to fetch remote Mynewt components.</li>
+<li>Have a computer to build a Mynewt application and connect to the board over USB.</li>
+<li>Have a Micro-USB cable to connect the board and the computer.</li>
+<li>Install the Newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
+<li>Install either the Jlink or OpenOCD debugger.</li>
+<li>Create a project space (directory structure) and populate it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.</li>
+<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section.
+<br></li>
+</ul>
+<h3 id="overview-of-steps">Overview of Steps</h3>
+<p>These are the general steps to create, load and run the Blinky application on your board:</p>
+<ul>
+<li>Create a project.</li>
+<li>Define the bootloader and Blinky application targets for the board.</li>
+<li>Build the bootloader target.</li>
+<li>Build the Blinky application target and create an application image.</li>
+<li>Connect to the board.</li>
+<li>Load the bootloader onto the board.</li>
+<li>Load the Blinky application image onto the board.</li>
+<li>See the LED on your board blink.</li>
+</ul>
+<p><br></p>
+<p>After you try the Blinky application on your boards, checkout out other tutorials to enable additional functionality such as <a href="../project-slinky/">remote comms</a> on the current board. If you have BLE (Bluetooth Low Energy) chip (e.g. nRF52) on your board, you can try turning it into an <a href="../ibeacon/">iBeacon</a> or <a href="../eddystone/">Eddystone Beacon</a>! </p>
+<p>If you see anything missing or want to send us feedback, please sign up for
+appropriate mailing lists on our <a href="../../../community/">Community Page</a>.</p>
+
+ <div class="row">
+
+
+
+
+<ul class="nav nav-pills" style="margin-bottom: 10px">
+ <li>
+
+ <a href=../tutorials/>
+ <span class="fa fa-arrow-left"></span>
+ Previous: Tutorials
+ </a>
+
+ </li>
+ <li class="pull-right">
+
+ <a href=../arduino_zero/>
+ Next: Blinky on Arduino Zero
+ <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/40899401/latest/os/tutorials/blinky_console/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/blinky_console/index.html b/latest/os/tutorials/blinky_console/index.html
index 61cfd8d..814234e 100644
--- a/latest/os/tutorials/blinky_console/index.html
+++ b/latest/os/tutorials/blinky_console/index.html
@@ -232,14 +232,14 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
<ul>
+
+
<li >
<a href="../arduino_zero/">Blinky on Arduino Zero</a>
@@ -317,8 +317,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -326,7 +329,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -334,7 +337,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -342,20 +345,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -363,7 +361,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -371,7 +369,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -379,18 +377,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -398,15 +393,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -526,7 +524,7 @@
- <li>» <a href="../arduino_zero/">Project Blinky</a></li>
+ <li>» <a href="../blinky/">Project Blinky</a></li>
@@ -539,12 +537,12 @@
</div>
<h2 id="enabling-the-console-and-shell-for-blinky">Enabling The Console and Shell for Blinky</h2>
-<p><br></p>
-<p>This tutorial explains how to add the Console and Shell task to the blinky application so that you can interact with it over a serial line connection.</p>
-<p><br></p>
+<p>This tutorial shows you how to add the Console and Shell to the Blinky application and interact with it over a serial line connection.
+<br></p>
<h3 id="prerequisites">Prerequisites</h3>
<ul>
<li>Work through one of the Blinky Tutorials to create and build a Blinky application for one of the boards.</li>
+<li>Have a <a href="../../get_started/serial_access/">serial setup</a>.</li>
</ul>
<p><br></p>
<h3 id="use-an-existing-project">Use an Existing Project</h3>
@@ -576,13 +574,13 @@ the shell and console connectivity. You can use blinky on a different board.</p>
<p><br></p>
<h3 id="use-the-os-default-event-queue-to-process-blinky-timer-and-shell-events">Use the OS Default Event Queue to Process Blinky Timer and Shell Events</h3>
-<p>Mynewt creates a default task that executes the application <code>main()</code> function. It also creates an OS default event queue that packages can use to queue their events. Shell uses the OS default event queue for Shell events, and <code>main()</code> can process the events in the context of the default task. </p>
+<p>Mynewt creates a main task that executes the application <code>main()</code> function. It also creates an OS default event queue that packages can use to queue their events. Shell uses the OS default event queue for Shell events, and <code>main()</code> can process the events in the context of the main task. </p>
<p>Blinky's main.c is very simple. It only has a <code>main()</code> function that executes an infinite loop to toggle the LED and sleep for one second. We will modify blinky:</p>
<ul>
<li>To use os_callout to generate a timer event every one second instead of sleeping. The timer events are added to the OS default event queue.</li>
<li>To process events from the OS default event queue inside the infinite loop in <code>main()</code>.</li>
</ul>
-<p>This allows the default task to process both Shell events and the timer events to toggle the LED from the OS default event queue.</p>
+<p>This allows the main task to process both Shell events and the timer events to toggle the LED from the OS default event queue.</p>
<p><br></p>
<h3 id="modify-mainc">Modify main.c</h3>
<p>Initialize a os_callout timer and move the toggle code from the while loop in <code>main()</code> to the event callback function. Add the following code above the <code>main()</code> function:</p>
@@ -678,7 +676,7 @@ Loading app image into slot 1
Tutorial for more information on setting up your serial communication.</p>
<p><br></p>
<h3 id="communicate-with-the-application">Communicate with the Application</h3>
-<p>Once you have a connection set up, run <code>minicom -D /dev/tty.usbmodem<port> -b 115200</code> to connect to the application console.</p>
+<p>Once you have a connection set up, run <code>minicom -D /dev/tty.usbserial<port> -b 115200</code> to connect to the application console.</p>
<p>To test and make sure that the Shell is running, first just hit <return>:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">3534: >
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/blinky_primo/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/blinky_primo/index.html b/latest/os/tutorials/blinky_primo/index.html
index aefc9f3..4ebd268 100644
--- a/latest/os/tutorials/blinky_primo/index.html
+++ b/latest/os/tutorials/blinky_primo/index.html
@@ -232,14 +232,14 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
<ul>
+
+
<li >
<a href="../arduino_zero/">Blinky on Arduino Zero</a>
@@ -317,8 +317,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -326,7 +329,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -334,7 +337,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -342,20 +345,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -363,7 +361,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -371,7 +369,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -379,18 +377,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -398,15 +393,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -526,7 +524,7 @@
- <li>» <a href="../arduino_zero/">Project Blinky</a></li>
+ <li>» <a href="../blinky/">Project Blinky</a></li>
@@ -539,23 +537,14 @@
</div>
<h2 id="blinky-your-hello-world-on-arduino-primo">Blinky, your "Hello World!", on Arduino Primo</h2>
-<p><br></p>
-<h3 id="objective">Objective</h3>
-<p>Learn how to use packages from a default application repository of Mynewt to build your first <em>Hello World</em> application (Blinky) on a target board. Once built using the <em>newt</em> tool, this application will blink the LED lights on the target board.</p>
-<p>Create a project with a simple app that blinks an LED on the Arduino Primo board. Download the application to the target and watch it blink!</p>
-<p>Note that the Mynewt OS will run on the nRF52 chip in the Arduino Primo board. However, the board support package for the Arduino Primo is different from the nRF52 dev kit board support package.</p>
-<p><br></p>
+<p>This tutorial shows you how to create, build, and run the Blinky application on an Arduino Primo board.</p>
+<p>Note that the Mynewt OS will run on the nRF52 chip in the Arduino Primo board. However, the board support package for the Arduino Primo is different from the nRF52 dev kit board support package.
+<br></p>
<h3 id="prerequisites">Prerequisites</h3>
-<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
<ul>
-<li>Have an Arduino Primo</li>
-<li>Have Internet connectivity to fetch remote Mynewt components.</li>
-<li>Have a computer to build a Mynewt application and connect to the` board over USB.</li>
-<li>Have a Micro-USB cable to connect the board and the computer.</li>
-<li>Install the Newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
-<li>Create a project space (directory structure) and populated it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.</li>
-<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section.</li>
-<li>Install a debugger - choose one of the two options below. Option 1 requires additional hardware but very easy to set up. Option 2 is free software but not as simple as Option 1.</li>
+<li>Meet the the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
+<li>Have an Arduino Primo board.</li>
+<li>Install a debugger choose one of the two options below: Option 1 requires additional hardware but very easy to set up. </li>
</ul>
<p><br></p>
<h5 id="option-1">Option 1</h5>
@@ -580,7 +569,6 @@ For bug reports, read
<p>You can now use openocd to upload to Arduino Primo board via the USB port itself.</p>
-<p><br></p>
<h3 id="create-a-project">Create a Project</h3>
<p>Create a new project if you do not have an existing one. You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already created a project.</p>
<p>Run the following commands to create a new project:</p>
@@ -761,12 +749,6 @@ warning: Source file is more recent than executable.
<p><br></p>
-<h3 id="conclusion">Conclusion</h3>
-<p>You have created, setup, compiled, loaded, and ran your first mynewt application
-for an Arduino Primo board.</p>
-<p>We have more fun tutorials for you to get your hands dirty. Be bold and work on the OS with tutorials on <a href="../unit_test/">writing a test suite</a> or try enabling additional functionality such as <a href="../project-target-slinky/">remote comms</a> or <a href="../bletiny_project/">Bluetooth Low Energy</a> on your current board.</p>
-<p>If you see anything missing or want to send us feedback, please do so by signing up for appropriate mailing lists on our <a href="../../../community/">Community Page</a>.</p>
-<p>Keep on hacking and blinking!</p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/eddystone/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/eddystone/index.html b/latest/os/tutorials/eddystone/index.html
index 8553e86..609929b 100644
--- a/latest/os/tutorials/eddystone/index.html
+++ b/latest/os/tutorials/eddystone/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,15 +264,15 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
- <li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <li class="active">
+ <a href="./">BLE Eddystone</a>
</li>
@@ -279,20 +280,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -300,7 +296,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -308,7 +304,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,18 +312,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li class="active">
- <a href="./">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -694,8 +690,8 @@ your Eddystone-aware devices.</p>
</li>
<li class="pull-right">
- <a href=../blehci_project/>
- Next: BLE HCI interface
+ <a href=../add_newtmgr/>
+ Next: Enable Newt Manager in any app
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/event_queue/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/event_queue/index.html b/latest/os/tutorials/event_queue/index.html
index 755090e..1e930ba 100644
--- a/latest/os/tutorials/event_queue/index.html
+++ b/latest/os/tutorials/event_queue/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,7 +264,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -271,28 +272,23 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
- <li class="active">
- <a href="./">Events and Event Queues</a>
+ <li >
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -300,7 +296,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -308,7 +304,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,18 +312,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li class="active">
+ <a href="./">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -947,8 +943,8 @@ Implement the <code>my_interrupt_ev_cb()</code> callback function to process an
</li>
<li class="pull-right">
- <a href=../project-slinky/>
- Next: Slinky on sim device
+ <a href=../bletiny_project/>
+ Next: BLE app to check stats via console
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/ibeacon/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/ibeacon/index.html b/latest/os/tutorials/ibeacon/index.html
index 3b87ec4..206eae1 100644
--- a/latest/os/tutorials/ibeacon/index.html
+++ b/latest/os/tutorials/ibeacon/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,16 +252,19 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
- <li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <li class="active">
+ <a href="./">BLE iBeacon</a>
</li>
@@ -271,7 +272,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -279,20 +280,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -300,7 +296,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -308,7 +304,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,34 +312,34 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
- <li class="active">
- <a href="./">BLE iBeacon</a>
+ <li >
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -641,9 +637,9 @@ your iBeacon-aware devices.</p>
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../bleprph/bleprph-app/>
+ <a href=../project-stm32-slinky/>
<span class="fa fa-arrow-left"></span>
- Previous: BLE Peripheral App
+ Previous: Slinky on Olimex
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/nRF52/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/nRF52/index.html b/latest/os/tutorials/nRF52/index.html
index b46e18a..c978f55 100644
--- a/latest/os/tutorials/nRF52/index.html
+++ b/latest/os/tutorials/nRF52/index.html
@@ -232,14 +232,14 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
<ul>
+
+
<li >
<a href="../arduino_zero/">Blinky on Arduino Zero</a>
@@ -317,8 +317,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -326,7 +329,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -334,7 +337,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -342,20 +345,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -363,7 +361,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -371,7 +369,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -379,18 +377,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -398,15 +393,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -526,7 +524,7 @@
- <li>» <a href="../arduino_zero/">Project Blinky</a></li>
+ <li>» <a href="../blinky/">Project Blinky</a></li>
@@ -539,27 +537,18 @@
</div>
<h2 id="blinky-your-hello-world-on-nrf52">Blinky, your "Hello World!", on nRF52</h2>
-<p><br></p>
-<h3 id="objective">Objective</h3>
-<p>Learn how to use packages from a default application repository of Mynewt to build your first <em>Hello World</em> application (Blinky) on a target board. Once built using the <em>newt</em> tool, this application will blink the LED lights on the target board.</p>
-<p>Create a project with a simple application that blinks an LED on the nRF52 board from Nordic Semiconductors. Download the application to the target and watch it blink!</p>
+<p>This tutorial shows you how to create, build, and run the Blinky application on the nRF52 board.
+<br></p>
<p>Note that there are several versions of the nRF52 in the market. The boards tested with this tutorial are listed under "Prerequisites".</p>
<p><br></p>
<h3 id="prerequisites">Prerequisites</h3>
-<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
<ul>
+<li>Meet the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
<li>Have a nRF52 Development Kit (one of the following)<ul>
<li>Dev Kit from Nordic - PCA 10040</li>
<li>Eval Kit from Rigado - BMD-300-EVAL-ES</li>
</ul>
</li>
-<li>Have Internet connectivity to fetch remote Mynewt components.</li>
-<li>Have a computer to build a Mynewt application and connect to the board over USB.</li>
-<li>Have a Micro-USB cable to connect the board and the computer.</li>
-<li>Install the Newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
-<li>Install the <a href="https://www.segger.com/jlink-software.html">Segger JLINK package</a> to load your project on the board.</li>
-<li>Create a project space (directory structure) and populated it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.</li>
-<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section.</li>
</ul>
<p>This tutorial uses the Nordic nRF52-DK board.</p>
<h3 id="create-a-project">Create a Project</h3>
@@ -718,13 +707,6 @@ Erasing done.
J-Link>exit
$
</pre></div>
-
-
-<h3 id="conclusion">Conclusion</h3>
-<p>You have created, setup, compiled, loaded, and ran your first mynewt application for an nrf52 board.</p>
-<p>We have more fun tutorials for you to get your hands dirty. Be bold and work on the OS with tutorials on <a href="../unit_test/">writing a test suite</a> or try enabling additional functionality such as <a href="../project-target-slinky/">remote comms</a> or <a href="../bletiny_project/">Bluetooth Low Energy</a> on your current board.</p>
-<p>If you see anything missing or want to send us feedback, please do so by signing up for appropriate mailing lists on our <a href="../../../community/">Community Page</a>.</p>
-<p>Keep on hacking and blinking!</p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/nrf52_adc/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/nrf52_adc/index.html b/latest/os/tutorials/nrf52_adc/index.html
index 40ffd7f..cdba618 100644
--- a/latest/os/tutorials/nrf52_adc/index.html
+++ b/latest/os/tutorials/nrf52_adc/index.html
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,8 +252,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -263,7 +264,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -271,7 +272,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -279,20 +280,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -300,7 +296,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -308,7 +304,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -316,18 +312,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -335,15 +328,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -530,12 +526,12 @@ project.repositories:
#
repository.apache-mynewt-core:
type: github
- vers: 0-dev
+ vers: 1-dev
user: apache
repo: incubator-mynewt-core
<span style="background-color: #ffffcc">repository.mynewt_nordic:
</span><span style="background-color: #ffffcc"> type: github
-</span><span style="background-color: #ffffcc"> vers: 0-latest
+</span><span style="background-color: #ffffcc"> vers: 1-latest
</span><span style="background-color: #ffffcc"> user: runtimeinc
</span><span style="background-color: #ffffcc"> repo: mynewt_nordic
</span></pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/olimex/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/olimex/index.html b/latest/os/tutorials/olimex/index.html
index 6988ac5..7ceb4d2 100644
--- a/latest/os/tutorials/olimex/index.html
+++ b/latest/os/tutorials/olimex/index.html
@@ -232,14 +232,14 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
<ul>
+
+
<li >
<a href="../arduino_zero/">Blinky on Arduino Zero</a>
@@ -317,8 +317,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -326,7 +329,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -334,7 +337,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -342,20 +345,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -363,7 +361,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -371,7 +369,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -379,18 +377,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -398,15 +393,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -526,7 +524,7 @@
- <li>» <a href="../arduino_zero/">Project Blinky</a></li>
+ <li>» <a href="../blinky/">Project Blinky</a></li>
@@ -539,24 +537,16 @@
</div>
<h2 id="blinky-your-hello-world-on-olimex">Blinky, your "Hello World!", on Olimex</h2>
-<h3 id="objective">Objective</h3>
-<p>Learn how to use packages from a default application repository of Mynewt to build your first <em>Hello World</em> application (Blinky) on a target board. Once built using the <em>newt</em> tool, this application will blink the LED lights on the target board. Fun stuff!</p>
-<p>This tutorial shows you how to create a blinky application for the Olimex board. It also shows you how to load the application onto the board's flash memory and run the application.</p>
-<p><br></p>
+<p>This tutorial shows you how to create, build, and run the Blinky application on an Olimex STM32-E407 board.
+<br></p>
<h3 id="prerequisites">Prerequisites</h3>
-<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
<ul>
+<li>Meet the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
<li>Have a STM32-E407 development board from Olimex. </li>
<li>Have a ARM-USB-TINY-H connector with JTAG interface for debugging ARM microcontrollers (comes with the ribbon cable to hook up to the board)</li>
-<li>Have Internet connectivity to fetch remote Mynewt components.</li>
-<li>Have a computer to build a Mynewt application and connect to the board over USB.</li>
-<li>Have a USB A-B type cable to connect the debugger to your computer.</li>
-<li>Have a USB Micro-A cable to connect your computer to the board.</li>
-<li>Install the Newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
-<li>Create a project space (directory structure) and populated it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.</li>
-<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section.</li>
+<li>Have a USB A-B type cable to connect the debugger to your computer.
+<br></li>
</ul>
-<p><br></p>
<h3 id="create-a-project">Create a Project</h3>
<p>Create a new project if you do not have an existing one. You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already created a project.</p>
<p>Run the following commands to create a new project:</p>
@@ -740,13 +730,6 @@ Let's double check that it is indeed booting from flash and making the LED blink
(0x08000020: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
(gdb) monitor flash info 0
</pre></div>
-
-
-<h3 id="conclusion">Conclusion</h3>
-<p>Congratulations! You have now tried out a project on actual hardware. If this is your first time to embedded systems, this must feel like the best hands-on and low-level "Hello World" program ever.</p>
-<p>Good, we have more fun tutorials for you to get your hands dirty. Be bold and try other Blinky-like <a href="../nRF52/">tutorials</a> or try enabling additional functionality such as <a href="../project-target-slinky/">remote comms</a> on the current board.</p>
-<p>If you see anything missing or want to send us feedback, please do so by signing up for appropriate mailing lists on our <a href="../../../community/">Community Page</a>.</p>
-<p>Keep on hacking and blinking!</p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/pin-wheel-mods/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/pin-wheel-mods/index.html b/latest/os/tutorials/pin-wheel-mods/index.html
index fd0d41c..886cad9 100644
--- a/latest/os/tutorials/pin-wheel-mods/index.html
+++ b/latest/os/tutorials/pin-wheel-mods/index.html
@@ -232,14 +232,14 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
<ul>
+
+
<li >
<a href="../arduino_zero/">Blinky on Arduino Zero</a>
@@ -331,8 +331,11 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
</li>
@@ -340,7 +343,7 @@
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -348,7 +351,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -356,20 +359,15 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -377,7 +375,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -385,7 +383,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -393,18 +391,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -412,15 +407,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -536,7 +534,7 @@
- <li>» <a href="../arduino_zero/">Project Blinky</a></li>
+ <li>» <a href="../blinky/">Project Blinky</a></li>
[02/11] incubator-mynewt-site git commit: Updated Blinky and Slinky
tutorials with intro summaries,
remove legacy feature references in the tutorials
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/project-nrf52-slinky/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/project-nrf52-slinky/index.html b/latest/os/tutorials/project-nrf52-slinky/index.html
new file mode 100644
index 0000000..9c1cb88
--- /dev/null
+++ b/latest/os/tutorials/project-nrf52-slinky/index.html
@@ -0,0 +1,742 @@
+<!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/os/tutorials/project-nrf52-slinky/"> -->
+ <link rel="shortcut icon" href="../../../img/favicon.ico">
+
+ <title>Slinky on Nordic nRF52 - 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="Slinky on Nordic nRF52">
+
+
+ <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</a> released (March 22, 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="../../introduction/">Mynewt Documentation</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../../get_started/get_started/">Basic Setup</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../get_started/vocabulary/">Concepts</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../tutorials/">Tutorials</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../blinky/">Project Blinky</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../repo/add_repos/">Work with repositories</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
+ <ul>
+
+
+
+
+
+ <li >
+ <a href="../project-sim-slinky/">Slinky on sim device</a>
+ </li>
+
+
+
+
+
+ <li class="active">
+ <a href="./">Slinky on Nordic nRF52</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../project-stm32-slinky/">Slinky on Olimex</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../ibeacon/">BLE iBeacon</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../eddystone/">BLE Eddystone</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../blehci_project/">BLE HCI interface</a>
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../air_quality_sensor/
+">Air-quality Sensor project</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../nrf52_adc/">Add an Analog Sensor</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../os_user_guide/">OS User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../../network/ble/ble_intro/
+">BLE User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../newt/newt_intro/">Newt Tool Guide</a>
+
+
+ </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="../tutorials/">Tutorials</a></li>
+
+
+
+ <li>» <a href="../project-slinky/">Project Slinky for Remote Comms</a></li>
+
+
+
+ <li>» Slinky on Nordic nRF52</li>
+
+
+
+ </ul>
+</div>
+ </div>
+
+ <h2 id="project-slinky-using-the-nordic-nrf52-board">Project Slinky using the Nordic nRF52 Board</h2>
+<p>This tutorial shows you how to create, build and run the Slinky application and communicate with newtmgr for a Nordic nRF52 board.</p>
+<h3 id="prerequisites">Prerequisites</h3>
+<ul>
+<li>Meet the prerequisites listed in <a href="../project-slinky/">Project Slinky</a>. </li>
+<li>Have a Nordic nRF52-DK board. </li>
+</ul>
+<h3 id="create-a-new-project">Create a New Project</h3>
+<p>Create a new project if you do not have an existing one. You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already have a project created or completed the <a href="../project-slinky/">Sim Slinky</a> tutorial. </p>
+<p>Run the following commands to create a new project. We name the project <code>slinky</code>. </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt new slinky
+Downloading project skeleton from apache/incubator-mynewt-blinky...
+...
+Installing skeleton in slink...
+Project slinky successfully created
+$ cd slinky
+$newt install
+apache-mynewt-core
+</pre></div>
+
+
+<p><br></p>
+<h3 id="create-the-targets"><a name="create_targets"></a> Create the Targets</h3>
+<p>Create two targets for the nRF52-DK board - one for the bootloader and one for the Slinky application.</p>
+<p>Run the following <code>newt target</code> commands, from your project directory, to create a bootloader target. We name the target <code>nrf52_boot</code>.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create nrf52_boot
+$ newt target set nrf52_boot bsp=@apache-mynewt-core/hw/bsp/nrf52dk
+$ newt target set nrf52_boot build_profile=optimized
+$ newt target set nrf52_boot app=@apache-mynewt-core/apps/boot
+</pre></div>
+
+
+<p><br>
+Run the following <code>newt target</code> commands to create a target for the Slinky application. We name the target <code>nrf52_slinky</code>.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create nrf52_slinky
+$ newt target set nrf52_slinky bsp=@apache-mynewt-core/hw/bsp/nrf52dk
+$ newt target set nrf52_slinky build_profile=debug
+$ newt target set nrf52_slinky app=@apache-mynewt-core/apps/slinky
+</pre></div>
+
+
+<p><br></p>
+<h3 id="build-the-targets">Build the Targets</h3>
+<p>Run the <code>newt build nrf52_boot</code> command to build the bootloader:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt build nrf52-boot
+Building target targets/nrf52_boot
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c
+Compiling repos/apache-mynewt-core/crypto/mbedtls/src/aes.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/loader.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c
+Compiling repos/apache-mynewt-core/apps/boot/src/boot.c
+ ...
+
+Archiving sys_mfg.a
+Archiving sys_sysinit.a
+Archiving util_mem.a
+Linking ~/dev/slinky/bin/targets/nrf52_boot/app/apps/boot/boot.elf
+Target successfully built: targets/nrf52_boot
+</pre></div>
+
+
+<p><br></p>
+<p>Run the <code>newt build nrf52_slinky</code> command to build the Slinky application:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt build nrf52_slinky
+Building target targets/nrf52_slinky
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c
+Compiling repos/apache-mynewt-core/boot/split/src/split.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/loader.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c
+Compiling repos/apache-mynewt-core/boot/split/src/split_config.c
+Compiling repos/apache-mynewt-core/crypto/mbedtls/src/aesni.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c
+Compiling repos/apache-mynewt-core/crypto/mbedtls/src/aes.c
+Compiling repos/apache-mynewt-core/apps/slinky/src/main.c
+
+ ...
+
+Archiving util_mem.a
+Linking ~/dev/slinky/bin/targets/nrf52_slinky/app/apps/slinky/slinky.elf
+Target successfully built: targets/nrf52_slinky
+</pre></div>
+
+
+<p><br></p>
+<h3 id="sign-and-create-the-slinky-application-image">Sign and Create the Slinky Application Image</h3>
+<p>Run the <code>newt create-image nrf52_slinky 1.0.0</code> command to create and sign the application image. You may assign an arbitrary version (e.g. 1.0.0) to the image.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt create-image nrf52_slinky 1.0.0
+App image succesfully generated: ~/dev/slinky/bin/targets/nrf52_slinky/app/apps/slinky/slinky.img
+$
+</pre></div>
+
+
+<p><br></p>
+<h3 id="connect-to-the-board">Connect to the Board</h3>
+<ul>
+<li>Connect a micro-USB cable from your computer to the micro-USB port on the nRF52-DK board.</li>
+<li>Turn the power on the board to ON. You should see the green LED light up on the board.</li>
+</ul>
+<p><br></p>
+<h3 id="load-the-bootloader-and-the-slinky-application-image">Load the Bootloader and the Slinky Application Image</h3>
+<p>Run the <code>newt load nrf52_boot</code> command to load the bootloader onto the board:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load nrf52_boot
+Loading bootloader
+$
+</pre></div>
+
+
+<p><br>
+Run the <code>newt load nrf52_slinky</code> command to load the Slinky application image onto the board:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load nrf52_slinky
+Loading app image into slot 1
+$
+</pre></div>
+
+
+<p><br></p>
+<h3 id="connect-newtmgr-with-the-board-using-a-serial-connection">Connect Newtmgr with the Board using a Serial Connection</h3>
+<p>Set up a serial connection from your computer to the nRF52-DK board (See <a href="../../get_started/serial_access/">Serial Port Setup</a>). </p>
+<p>Locate the port, in the /dev directory on your computer, that the serial connection uses. It should be of the type <code>tty.usbserial-<some identifier></code>.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ ls /dev/tty*usbserial*
+/dev/tty.usbserial-1d11
+$
+</pre></div>
+
+
+<p><br>
+Setup a newtmgr connection profile for the serial port. For our example, the port is <code>/dev/tty.usbserial-1d11</code>. </p>
+<p>Run the <code>newtmgr conn add</code> command to define a newtmgr connection profile for the serial port. We name the connection profile <code>nrf52serial</code>. You will need to replace the <code>connstring</code> with the specific port for your serial connection. </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr conn add nrf52serial type=serial connstring=/dev/tty.usbserial-1d11
+Connection profile nrf52serial successfully added
+$
+</pre></div>
+
+
+<p><br>
+You can run the <code>newt conn show</code> command to see all the newtmgr connection profiles:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr conn show
+Connection profiles:
+ nrf52serial: type=serial, connstring='/dev/tty.usbserial-1d11'
+ sim1: type=serial, connstring='/dev/ttys012'
+$
+</pre></div>
+
+
+<p><br></p>
+<h3 id="use-newtmgr-to-query-the-board">Use Newtmgr to Query the Board</h3>
+<p>Run some newtmgr commands to query and receive responses back from the board (See the <a href="../newtmgr/overview">Newt Manager Guide</a> for more information on the newtmgr commands). </p>
+<p>Run the <code>newtmgr echo hello -c nrf52serial</code> command. This is the simplest command that requests the board to echo back the text. </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr echo hello -c nrf52serial
+hello
+$
+</pre></div>
+
+
+<p><br>
+Run the <code>newtmgr image list -c nrf52serial</code> command to list the images on the board:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr image list -c nrf52serial
+Images:
+ slot=0
+ version: 1.0.0
+ bootable: true
+ flags: active confirmed
+ hash: f411a55d7a5f54eb8880d380bf47521d8c41ed77fd0a7bd5373b0ae87ddabd42
+Split status: N/A
+$
+</pre></div>
+
+
+<p><br>
+Run the <code>newtmgr taskstats -c nrf52serial</code> command to display the task statistics on the board:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr taskstats -c nrf52serial
+Return Code = 0
+ task pri tid runtime csw stksz stkuse last_checkin next_checkin
+ task1 8 2 0 1751 192 110 0 0
+ task2 9 3 0 1751 64 31 0 0
+ idle 255 0 224081 2068 64 32 0 0
+ main 127 1 3 29 1024 365 0 0
+$
+</pre></div>
+
+ <div class="row">
+
+
+
+
+<ul class="nav nav-pills" style="margin-bottom: 10px">
+ <li>
+
+ <a href=../project-sim-slinky/>
+ <span class="fa fa-arrow-left"></span>
+ Previous: Slinky on sim device
+ </a>
+
+ </li>
+ <li class="pull-right">
+
+ <a href=../project-stm32-slinky/>
+ Next: Slinky on Olimex
+ <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/40899401/latest/os/tutorials/project-sim-slinky/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/project-sim-slinky/index.html b/latest/os/tutorials/project-sim-slinky/index.html
new file mode 100644
index 0000000..0701e46
--- /dev/null
+++ b/latest/os/tutorials/project-sim-slinky/index.html
@@ -0,0 +1,653 @@
+<!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/os/tutorials/project-sim-slinky/"> -->
+ <link rel="shortcut icon" href="../../../img/favicon.ico">
+
+ <title>Slinky on sim device - 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="Slinky on sim device">
+
+
+ <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</a> released (March 22, 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="../../introduction/">Mynewt Documentation</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../../get_started/get_started/">Basic Setup</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../get_started/vocabulary/">Concepts</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../tutorials/">Tutorials</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../blinky/">Project Blinky</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../repo/add_repos/">Work with repositories</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
+ <ul>
+
+
+
+
+
+ <li class="active">
+ <a href="./">Slinky on sim device</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../project-nrf52-slinky/">Slinky on Nordic nRF52</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../project-stm32-slinky/">Slinky on Olimex</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../ibeacon/">BLE iBeacon</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../eddystone/">BLE Eddystone</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../blehci_project/">BLE HCI interface</a>
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../air_quality_sensor/
+">Air-quality Sensor project</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../nrf52_adc/">Add an Analog Sensor</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../os_user_guide/">OS User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../../network/ble/ble_intro/
+">BLE User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../newt/newt_intro/">Newt Tool Guide</a>
+
+
+ </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="../tutorials/">Tutorials</a></li>
+
+
+
+ <li>» <a href="../project-slinky/">Project Slinky for Remote Comms</a></li>
+
+
+
+ <li>» Slinky on sim device</li>
+
+
+
+ </ul>
+</div>
+ </div>
+
+ <h2 id="project-sim-slinky">Project Sim Slinky</h2>
+<p>This tutorial shows you how to create, build and run the Slinky application and communicate with newtmgr for a simulated device.</p>
+<p><br></p>
+<h3 id="prerequisites">Prerequisites</h3>
+<p>Meet the prerequisites listed in <a href="../project-slinky/">Project Slinky</a>.</p>
+<h3 id="creating-a-new-project">Creating a new project</h3>
+<p>Instructions for creating a project are located in the <a href="../../get_started/project_create/">Basic Setup</a> section of the <a href="../../introduction/">Mynewt Documentation</a></p>
+<p>We will list only the steps here for brevity. We will name the project <code>slinky</code>.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt new slinky
+Downloading project skeleton from apache/incubator-mynewt-blinky...
+...
+Installing skeleton in slink...
+Project slinky successfully created
+$ cd slinky
+$newt install
+apache-mynewt-core
+</pre></div>
+
+
+<h3 id="setting-up-your-target-build">Setting up your target build</h3>
+<p>Create a target for <code>slinky</code> using the native bsp. We will list only the steps and suppress the tool output here for brevity.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newt target create sim_slinky
+ $ newt target set sim_slinky bsp=@apache-mynewt-core/hw/bsp/native
+ $ newt target set sim_slinky build_profile=debug
+ $ newt target set sim_slinky app=@apache-mynewt-core/apps/slinky
+</pre></div>
+
+
+<h3 id="building-your-target">Building Your target</h3>
+<p>To build your target, use <code>newt build</code>. When complete, an executable file
+is created.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newt build sim_slinky
+ Building target targets/sim_slinky
+ Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c
+ Compiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c
+ Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c
+ Compiling repos/apache-mynewt-core/boot/split/src/split.c
+ Compiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c
+ Compiling repos/apache-mynewt-core/boot/bootutil/src/loader.c
+ Compiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c
+ Compiling repos/apache-mynewt-core/crypto/mbedtls/src/aesni.c
+ Compiling repos/apache-mynewt-core/crypto/mbedtls/src/aes.c
+ Compiling repos/apache-mynewt-core/boot/split/src/split_config.c
+ Compiling repos/apache-mynewt-core/apps/slinky/src/main.c
+
+ ...
+
+ Archiving util_crc.a
+ Archiving util_mem.a
+ Linking ~/dev/slinky/bin/targets/sim_slinky/app/apps/slinky/slinky.elf
+ Target successfully built: targets/sim_slinky
+</pre></div>
+
+
+<h3 id="run-the-target">Run the target</h3>
+<p>Run the executable you have build for the simulated environment. The serial port name on which the simulated target is connected is shown in the output when mynewt slinky starts.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ ~/dev/slinky/bin/targets/sim_slinky/app/apps/slinky/slinky.elf
+ uart0 at /dev/ttys005
+</pre></div>
+
+
+<p><br></p>
+<p>In this example, the slinky app opened up a com port <code>/dev/ttys005</code> for communications with newtmgr. </p>
+<p><strong>NOTE:</strong> This application will block. You will need to open a new console (or execute this in another console) to continue the tutorial.*</p>
+<p><br></p>
+<h3 id="setting-up-a-connection-profile">Setting up a connection profile</h3>
+<p>You will now set up a connection profile using <code>newtmgr</code> for the serial port connection and start communicating with the simulated remote device.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newtmgr conn add sim1 type=serial connstring=/dev/ttys005
+ Connection profile sim1 successfully added
+ $ newtmgr conn show
+ Connection profiles:
+ sim1: type=serial, connstring='/dev/ttys005'
+</pre></div>
+
+
+<h3 id="executing-newtmgr-commands-with-the-target">Executing newtmgr commands with the target</h3>
+<p>You can now use connection profile <code>sim1</code> to talk to the running sim_slinky.
+As an example, we will query the running mynewt OS for the usage of its
+memory pools. </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newtmgr -c sim1 mpstats
+ Return Code = 0
+ name blksz cnt free min
+ msys_1 292 12 10 10
+</pre></div>
+
+
+<p>As a test command, you can send an arbitrary string to the target and it
+will echo that string back in a response to newtmgr.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newtmgr -c sim1 echo "Hello Mynewt"
+ Hello Mynewt
+</pre></div>
+
+
+<p>In addition to these, you can also examine running tasks, statistics,
+logs, image status (not on sim), and configuration.</p>
+
+ <div class="row">
+
+
+
+
+<ul class="nav nav-pills" style="margin-bottom: 10px">
+ <li>
+
+ <a href=../project-slinky/>
+ <span class="fa fa-arrow-left"></span>
+ Previous: Project Slinky for Remote Comms
+ </a>
+
+ </li>
+ <li class="pull-right">
+
+ <a href=../project-nrf52-slinky/>
+ Next: Slinky on Nordic nRF52
+ <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/40899401/latest/os/tutorials/project-slinky/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/project-slinky/index.html b/latest/os/tutorials/project-slinky/index.html
index e444ef7..8ae237f 100644
--- a/latest/os/tutorials/project-slinky/index.html
+++ b/latest/os/tutorials/project-slinky/index.html
@@ -10,7 +10,7 @@
<link rel="canonical" href="http://mynewt.apache.org/os/tutorials/project-slinky/"> -->
<link rel="shortcut icon" href="../../../img/favicon.ico">
- <title>Slinky on sim device - Apache Mynewt</title>
+ <title>toc - Apache Mynewt</title>
<link href="../../../css/bootstrap-3.0.3.min.css" rel="stylesheet">
<link rel="stylesheet" href="../../../css/highlight.css">
@@ -41,7 +41,7 @@
</head>
- <body class="Slinky on sim device">
+ <body class="toc">
<div class="container">
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,16 +252,19 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
- </li>
-
+
+
+ <li class="active"><a href="./">Project Slinky for Remote Comms</a>
+
+
+ <ul>
+
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../project-sim-slinky/">Slinky on sim device</a>
</li>
@@ -271,7 +272,7 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../project-nrf52-slinky/">Slinky on Nordic nRF52</a>
</li>
@@ -279,26 +280,21 @@
<li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <a href="../project-stm32-slinky/">Slinky on Olimex</a>
</li>
-
-
-
-
- <li><a href="
- ./
-">Project Slinky for remote comms</a>
-
+ </ul>
- <ul>
+ </li>
+
+
- <li class="active">
- <a href="./">Slinky on sim device</a>
+ <li >
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -306,7 +302,7 @@
<li >
- <a href="../project-target-slinky/">Slinky on Nordic nRF52 board</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
@@ -314,13 +310,15 @@
<li >
- <a href="../project-stm32-slinky/">Slinky on STM32 board</a>
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
- </ul>
-
+
+
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -328,7 +326,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -336,7 +334,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -344,18 +342,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -363,15 +358,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -491,134 +489,50 @@
- <li>» Project Slinky for remote comms</li>
+ <li>» Project Slinky for Remote Comms</li>
- <li>» Slinky on sim device</li>
-
</ul>
</div>
</div>
- <h2 id="project-sim-slinky">Project Sim Slinky</h2>
-<p><br></p>
-<p>The goal of the project is to use a sample app called "Slinky" included in the Mynewt repository to enable remote communications with a device running the Mynewt OS. The protocol for remote communications is called newt manager (newtmgr). In this tutorial we will create a target for a simulated device and define it with the sample app "Slinky". </p>
-<p>If you have an existing project using a target that does not use the Slinky app and you wish to add newtmgt functonality to it, check out the tutorial titled <a href="../add_newtmgr/">Enable newtmgr in any app</a>. </p>
-<p><br></p>
+ <h2 id="project-slinky">Project Slinky</h2>
+<p>The goal of the project is to use a sample application called "Slinky" included in the Mynewt repository to enable remote communications with a device running the Mynewt OS. The protocol for remote communications is called newt manager (newtmgr). </p>
+<p>If you have an existing project using a target that does not use the Slinky application and you wish to add newtmgr functionality to it, check out the tutorial titled <a href="../add_newtmgr/">Enable newtmgr in any app</a>. </p>
+<h3 id="available-tutorials">Available Tutorials</h3>
+<p>Tutorials are available for the following boards:</p>
+<ul>
+<li><a href="../../../os/tutorials/project-sim-slinky">Slinky on a simulated device</a>.</li>
+<li><a href="../../../os/tutorials/project-nrf52-slinky">Slinky on a nRF52</a>.</li>
+<li><a href="../../../os/tutorials/project-stm32-slinky">Slinky on an Olimex</a>.
+<br></li>
+</ul>
<h3 id="prerequisites">Prerequisites</h3>
-<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
+<p>Ensure that you meet the following prerequisites before continuing with this tutorial:</p>
<ul>
<li>Have Internet connectivity to fetch remote Mynewt components.</li>
-<li>Have a computer to build a Mynewt application.</li>
+<li>Have a computer to build a Mynewt application and connect to the board over USB.</li>
+<li>Have a Micro-USB cable to connect the board and the computer.</li>
+<li>Have a <a href="../../get_started/serial_access/">serial port setup</a>.</li>
<li>Install the newt tool and the toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
<li>Install the <a href="../../../newtmgr/installing/">newtmgr tool</a>.</li>
<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section.</li>
+<li>Create a project space (directory structure) and populated it with the core code repository (apache-mynewt-core) or kn
+ow how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.</li>
</ul>
-<h3 id="overview-of-steps">Overview of steps</h3>
+<h3 id="overview-of-steps">Overview of Steps</h3>
<ul>
-<li>Install dependencies</li>
-<li>Define a target using the newt tool</li>
-<li>Build executables for the targets using the newt tool</li>
-<li>Set up serial connection with the targets </li>
-<li>Create a connection profile using the newtmgr tool</li>
-<li>Use the newtmgr tool to communicate with the targets</li>
+<li>Install dependencies.</li>
+<li>Define the bootloader and Slinky application target for the target board.</li>
+<li>Build the bootloader target.</li>
+<li>Build the Slinky application target and create an application image.</li>
+<li>Set a up serial connection with the targets.</li>
+<li>Create a connection profile using the newtmgr tool.</li>
+<li>Use the newtmgr tool to communicate with the targets.</li>
</ul>
-<h3 id="creating-a-new-project">Creating a new project</h3>
-<p>Instructions for creating a project are located in the <a href="../../get_started/project_create/">Basic Setup</a> section of the <a href="../../introduction/">Mynewt Documentation</a></p>
-<p>We will list only the steps here for brevity. We will name the project
-<code>slinky</code>.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newt new slinky
- Downloading project skeleton from apache/incubator-mynewt-blinky...
- ...
- Installing skeleton in slink...
- Project slink successfully created
- $ cd slinky
- $ newt install -v
- Downloading repository description for apache-mynewt-core... success!
- ...
- Repos successfully installed
-</pre></div>
-
-
-<h3 id="setting-up-your-target-build">Setting up your target build</h3>
-<p>Create a target for <code>slinky</code> using the native bsp. We will list only the steps and suppress the tool output here for brevity.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newt target create sim_slinky
- $ newt target set sim_slinky bsp=@apache-mynewt-core/hw/bsp/native
- $ newt target set sim_slinky build_profile=debug
- $ newt target set sim_slinky app=@apache-mynewt-core/apps/slinky
-</pre></div>
-
-
-<h3 id="building-your-target">Building Your target</h3>
-<p>To build your target, use <code>newt build</code>. When complete, an executable file
-is created.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newt build sim_slinky
- Building target targets/sim_slinky
- Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c
- Compiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c
- Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c
- Compiling repos/apache-mynewt-core/boot/split/src/split.c
- Compiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c
- Compiling repos/apache-mynewt-core/boot/bootutil/src/loader.c
- Compiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c
- Compiling repos/apache-mynewt-core/crypto/mbedtls/src/aesni.c
- Compiling repos/apache-mynewt-core/crypto/mbedtls/src/aes.c
- Compiling repos/apache-mynewt-core/boot/split/src/split_config.c
- Compiling repos/apache-mynewt-core/apps/slinky/src/main.c
-
- ...
-
- Archiving util_crc.a
- Archiving util_mem.a
- Linking ~/dev/slinky/bin/targets/sim_slinky/app/apps/slinky/slinky.elf
- Target successfully built: targets/sim_slinky
-</pre></div>
-
-
-<h3 id="run-the-target">Run the target</h3>
-<p>Run the executable you have build for the simulated environment. The serial port name on which the simulated target is connected is shown in the output when mynewt slinky starts.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ ~/dev/slinky/bin/targets/sim_slinky/app/apps/slinky/slinky.elf
- uart0 at /dev/ttys005
-</pre></div>
-
-
-<p><br></p>
-<p>In this example, the slinky app opened up a com port <code>/dev/ttys005</code> for communications with newtmgr. </p>
-<p><strong>NOTE:</strong> This application will block. You will need to open a new console (or execute this in another console) to continue the tutorial.*</p>
-<p><br></p>
-<h3 id="setting-up-a-connection-profile">Setting up a connection profile</h3>
-<p>You will now set up a connection profile using <code>newtmgr</code> for the serial port connection and start communicating with the simulated remote device.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newtmgr conn add sim1 type=serial connstring=/dev/ttys005
- Connection profile sim1 successfully added
- $ newtmgr conn show
- Connection profiles:
- sim1: type=serial, connstring='/dev/ttys005'
-</pre></div>
-
-
-<h3 id="executing-newtmgr-commands-with-the-target">Executing newtmgr commands with the target</h3>
-<p>You can now use connection profile <code>sim1</code> to talk to the running sim_slinky.
-As an example, we will query the running mynewt OS for the usage of its
-memory pools. </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newtmgr -c sim1 mpstats
- Return Code = 0
- name blksz cnt free min
- msys_1 292 12 10 10
-</pre></div>
-
-
-<p>As a test command, you can send an arbitrary string to the target and it
-will echo that string back in a response to newtmgr.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newtmgr -c sim1 echo "Hello Mynewt"
- Hello Mynewt
-</pre></div>
-
-
-<p>In addition to these, you can also examine running tasks, statistics,
-logs, image status (not on sim), and configuration.</p>
<div class="row">
@@ -628,16 +542,16 @@ logs, image status (not on sim), and configuration.</p>
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../event_queue/>
+ <a href=../repo/private_repo/>
<span class="fa fa-arrow-left"></span>
- Previous: Events and Event Queues
+ Previous: Access a private Repo
</a>
</li>
<li class="pull-right">
- <a href=../project-target-slinky/>
- Next: Slinky on Nordic nRF52 board
+ <a href=../project-sim-slinky/>
+ Next: Slinky on sim device
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/project-stm32-slinky/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/project-stm32-slinky/index.html b/latest/os/tutorials/project-stm32-slinky/index.html
index d00e7f3..50003cb 100644
--- a/latest/os/tutorials/project-stm32-slinky/index.html
+++ b/latest/os/tutorials/project-stm32-slinky/index.html
@@ -10,7 +10,7 @@
<link rel="canonical" href="http://mynewt.apache.org/os/tutorials/project-stm32-slinky/"> -->
<link rel="shortcut icon" href="../../../img/favicon.ico">
- <title>Slinky on STM32 board - Apache Mynewt</title>
+ <title>Slinky on Olimex - Apache Mynewt</title>
<link href="../../../css/bootstrap-3.0.3.min.css" rel="stylesheet">
<link rel="stylesheet" href="../../../css/highlight.css">
@@ -41,7 +41,7 @@
</head>
- <body class="Slinky on STM32 board">
+ <body class="Slinky on Olimex">
<div class="container">
@@ -232,9 +232,7 @@
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
+ <li ><a href="../blinky/">Project Blinky</a>
</li>
@@ -254,16 +252,19 @@
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
- </li>
-
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
+ <ul>
+
<li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ <a href="../project-sim-slinky/">Slinky on sim device</a>
</li>
@@ -271,34 +272,29 @@
<li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
+ <a href="../project-nrf52-slinky/">Slinky on Nordic nRF52</a>
</li>
- <li >
- <a href="../event_queue/">Events and Event Queues</a>
+ <li class="active">
+ <a href="./">Slinky on Olimex</a>
</li>
-
-
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
+ </ul>
- <ul>
+ </li>
+
+
<li >
- <a href="../project-slinky/">Slinky on sim device</a>
+ <a href="../ibeacon/">BLE iBeacon</a>
</li>
@@ -306,21 +302,23 @@
<li >
- <a href="../project-target-slinky/">Slinky on Nordic nRF52 board</a>
+ <a href="../eddystone/">BLE Eddystone</a>
</li>
- <li class="active">
- <a href="./">Slinky on STM32 board</a>
+ <li >
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
</li>
- </ul>
-
+
+
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
</li>
@@ -328,7 +326,7 @@
<li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
</li>
@@ -336,7 +334,7 @@
<li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
</li>
@@ -344,18 +342,15 @@
<li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
</li>
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
</li>
@@ -363,15 +358,18 @@
<li >
- <a href="../ibeacon/">BLE iBeacon</a>
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
</li>
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
</li>
@@ -491,11 +489,11 @@
- <li>» <a href="../project-slinky/">Project Slinky for remote comms</a></li>
+ <li>» <a href="../project-slinky/">Project Slinky for Remote Comms</a></li>
- <li>» Slinky on STM32 board</li>
+ <li>» Slinky on Olimex</li>
@@ -503,32 +501,16 @@
</div>
</div>
- <h2 id="project-slinky-using-stm32-board">Project Slinky Using STM32 Board</h2>
-<p>The goal of the project is to enable and demonstrate remote communications with the Mynewt OS via newt manager (newtmgr) by leveraging a sample app "Slinky" included under the /apps directory in the repository. In this project we will define a target for the STM32-E407 board and assign the app "Slinky" to it.</p>
-<p>If you have an existing project that has a different application and you wish to add newtmgr functionality to it, check out the <a href="../add_newtmgr/">Enable newtmgr in any app</a> tutorial.</p>
-<p><br></p>
+ <h2 id="project-slinky-using-olimex-board">Project Slinky Using Olimex Board</h2>
+<p>This tutorial shows you how to create, build and run the Slinky application and communicate with newtmgr for an Olimex STM-E407 board.
+<br></p>
<h3 id="prerequisites">Prerequisites</h3>
-<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
<ul>
+<li>Meet the prerequisites listed in <a href="../project-slinky/">Project Slinky</a>.</li>
<li>Have a STM32-E407 development board from Olimex. </li>
<li>Have a ARM-USB-TINY-H connector with JTAG interface for debugging ARM microcontrollers (comes with the ribbon cable to hook up to the board)</li>
+<li>Have a USB A-B type cable to connect the debugger to your computer. </li>
<li>Have a USB to TTL Serial Cable with female wiring harness.</li>
-<li>Have a USB Micro-A cable to connect your computer to the board.</li>
-<li>Have Internet connectivity to fetch remote Mynewt components.</li>
-<li>Have a computer to build a Mynewt application and connect to the board over USB.</li>
-<li>Install the newt tool and the toolchains (See Basic Setup).</li>
-<li>Install the newtmgr tool.</li>
-<li>Create a project space (directory structure) and populated it with the core code repository (apache-mynewt-core) or know how to as explained in Creating Your First Project.</li>
-<li>Read the Mynewt OS Concepts section.</li>
-</ul>
-<h3 id="overview-of-steps">Overview of Steps</h3>
-<ul>
-<li>Install dependencies</li>
-<li>Define a target using the newt tool</li>
-<li>Build executables for the targets using the newt tool</li>
-<li>Set up serial connection with the targets</li>
-<li>Create a connection profile using the newtmgr tool</li>
-<li>Use the newtmgr tool to communicate with the targets</li>
</ul>
<h3 id="create-a-new-project">Create a New Project</h3>
<p>Create a new project if you do not have an existing one. You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already have a project created or completed the <a href="../project-slinky/">Sim Slinky</a> tutorial.</p>
@@ -727,16 +709,16 @@ $
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../project-target-slinky/>
+ <a href=../project-nrf52-slinky/>
<span class="fa fa-arrow-left"></span>
- Previous: Slinky on Nordic nRF52 board
+ Previous: Slinky on Nordic nRF52
</a>
</li>
<li class="pull-right">
- <a href=../add_newtmgr/>
- Next: Enable Newt Manager in any app
+ <a href=../ibeacon/>
+ Next: BLE iBeacon
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/40899401/latest/os/tutorials/project-target-slinky/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/project-target-slinky/index.html b/latest/os/tutorials/project-target-slinky/index.html
deleted file mode 100644
index 6c65af9..0000000
--- a/latest/os/tutorials/project-target-slinky/index.html
+++ /dev/null
@@ -1,763 +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/os/tutorials/project-target-slinky/"> -->
- <link rel="shortcut icon" href="../../../img/favicon.ico">
-
- <title>Slinky on Nordic nRF52 board - 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="Slinky on Nordic nRF52 board">
-
-
- <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</a> released (March 22, 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="../../introduction/">Mynewt Documentation</a>
-
-
- <ul>
-
-
-
-
-
-
-
- <li ><a href="../../get_started/get_started/">Basic Setup</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../../get_started/vocabulary/">Concepts</a>
- </li>
-
-
-
-
-
-
-
- <li ><a href="../tutorials/">Tutorials</a>
-
-
- <ul>
-
-
-
-
-
-
-
- <li><a href="
- ../arduino_zero/
-">Project Blinky</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../repo/add_repos/">Work with repositories</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../event_queue/">Events and Event Queues</a>
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../project-slinky/
-">Project Slinky for remote comms</a>
-
-
- <ul>
-
-
-
- <li >
- <a href="../project-slinky/">Slinky on sim device</a>
- </li>
-
-
-
-
-
- <li class="active">
- <a href="./">Slinky on Nordic nRF52 board</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../project-stm32-slinky/">Slinky on STM32 board</a>
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
- <li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
- </li>
-
-
-
-
-
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../ibeacon/">BLE iBeacon</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../blehci_project/">BLE HCI interface</a>
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../air_quality_sensor/
-">Air-quality Sensor project</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../nrf52_adc/">Add an Analog Sensor</a>
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../os_user_guide/">OS User Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../../../network/ble/ble_intro/
-">BLE User Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../../newt/newt_intro/">Newt Tool Guide</a>
-
-
- </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="../tutorials/">Tutorials</a></li>
-
-
-
- <li>» <a href="../project-slinky/">Project Slinky for remote comms</a></li>
-
-
-
- <li>» Slinky on Nordic nRF52 board</li>
-
-
-
- </ul>
-</div>
- </div>
-
- <h2 id="project-slinky-using-the-nordic-nrf52-board">Project Slinky using the Nordic nRF52 Board</h2>
-<p><br></p>
-<p>The goal of this tutorial is to enable and demonstrate remote communications with a Mynewt application running on a device via newt manager (newtmgr). It uses the "Slinky" sample application that is included in the apache-mynewt-core/apps directory and the Nordic nRF52-DK board.</p>
-<p>If you have an existing project that has a different application and you wish to add newtmgr functionality to it, check out the <a href="../add_newtmgr/">Enable newtmgr in any app</a> tutorial.</p>
-<h3 id="prerequisites">Prerequisites</h3>
-<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
-<ul>
-<li>Have a Nordic nRF52-DK board. </li>
-<li>Have Internet connectivity to fetch remote Mynewt components.</li>
-<li>Have a computer to build a Mynewt application and connect to the board over USB.</li>
-<li>Have a Micro-USB cable to connect the board and the computer.</li>
-<li>Have a <a href="../../get_started/serial_access/">Serial Port Setup</a>. </li>
-<li>Install the newt tool and the toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
-<li>Install the <a href="../../../newtmgr/installing/">newtmgr tool</a>. </li>
-<li>Create a project space (directory structure) and populated it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.</li>
-<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section.</li>
-</ul>
-<h3 id="overview-of-steps">Overview of Steps</h3>
-<ul>
-<li>Install dependencies</li>
-<li>Define targets using the newt tool</li>
-<li>Build executables for the targets using the newt tool</li>
-<li>Set up serial connection with the targets</li>
-<li>Create a connection profile using the newtmgr tool</li>
-<li>Use the newtmgr tool to communicate with the targets</li>
-</ul>
-<h3 id="create-a-new-project">Create a New Project</h3>
-<p>Create a new project if you do not have an existing one. You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already have a project created or completed the <a href="../project-slinky/">Sim Slinky</a> tutorial. </p>
-<p>Run the following commands to create a new project. We name the project <code>slinky</code>. </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt new slinky
-Downloading project skeleton from apache/incubator-mynewt-blinky...
-...
-Installing skeleton in slink...
-Project slinky successfully created
-$ cd slinky
-$newt install
-apache-mynewt-core
-</pre></div>
-
-
-<p><br></p>
-<h3 id="create-the-targets"><a name="create_targets"></a> Create the Targets</h3>
-<p>Create two targets for the nRF52-DK board - one for the bootloader and one for the Slinky application.</p>
-<p>Run the following <code>newt target</code> commands, from your project directory, to create a bootloader target. We name the target <code>nrf52_boot</code>.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create nrf52_boot
-$ newt target set nrf52_boot bsp=@apache-mynewt-core/hw/bsp/nrf52dk
-$ newt target set nrf52_boot build_profile=optimized
-$ newt target set nrf52_boot app=@apache-mynewt-core/apps/boot
-</pre></div>
-
-
-<p><br>
-Run the following <code>newt target</code> commands to create a target for the Slinky application. We name the target <code>nrf52_slinky</code>.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create nrf52_slinky
-$ newt target set nrf52_slinky bsp=@apache-mynewt-core/hw/bsp/nrf52dk
-$ newt target set nrf52_slinky build_profile=debug
-$ newt target set nrf52_slinky app=@apache-mynewt-core/apps/slinky
-</pre></div>
-
-
-<p><br></p>
-<h3 id="build-the-targets">Build the Targets</h3>
-<p>Run the <code>newt build nrf52_boot</code> command to build the bootloader:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt build nrf52-boot
-Building target targets/nrf52_boot
-Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c
-Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c
-Compiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c
-Compiling repos/apache-mynewt-core/crypto/mbedtls/src/aes.c
-Compiling repos/apache-mynewt-core/boot/bootutil/src/loader.c
-Compiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c
-Compiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c
-Compiling repos/apache-mynewt-core/apps/boot/src/boot.c
- ...
-
-Archiving sys_mfg.a
-Archiving sys_sysinit.a
-Archiving util_mem.a
-Linking ~/dev/slinky/bin/targets/nrf52_boot/app/apps/boot/boot.elf
-Target successfully built: targets/nrf52_boot
-</pre></div>
-
-
-<p><br></p>
-<p>Run the <code>newt build nrf52_slinky</code> command to build the Slinky application:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt build nrf52_slinky
-Building target targets/nrf52_slinky
-Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c
-Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c
-Compiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c
-Compiling repos/apache-mynewt-core/boot/split/src/split.c
-Compiling repos/apache-mynewt-core/boot/bootutil/src/loader.c
-Compiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c
-Compiling repos/apache-mynewt-core/boot/split/src/split_config.c
-Compiling repos/apache-mynewt-core/crypto/mbedtls/src/aesni.c
-Compiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c
-Compiling repos/apache-mynewt-core/crypto/mbedtls/src/aes.c
-Compiling repos/apache-mynewt-core/apps/slinky/src/main.c
-
- ...
-
-Archiving util_mem.a
-Linking ~/dev/slinky/bin/targets/nrf52_slinky/app/apps/slinky/slinky.elf
-Target successfully built: targets/nrf52_slinky
-</pre></div>
-
-
-<p><br></p>
-<h3 id="sign-and-create-the-slinky-application-image">Sign and Create the Slinky Application Image</h3>
-<p>Run the <code>newt create-image nrf52_slinky 1.0.0</code> command to create and sign the application image. You may assign an arbitrary version (e.g. 1.0.0) to the image.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt create-image nrf52_slinky 1.0.0
-App image succesfully generated: ~/dev/slinky/bin/targets/nrf52_slinky/app/apps/slinky/slinky.img
-$
-</pre></div>
-
-
-<p><br></p>
-<h3 id="connect-to-the-board">Connect to the Board</h3>
-<ul>
-<li>Connect a micro-USB cable from your computer to the micro-USB port on the nRF52-DK board.</li>
-<li>Turn the power on the board to ON. You should see the green LED light up on the board.</li>
-</ul>
-<p><br></p>
-<h3 id="load-the-bootloader-and-the-slinky-application-image">Load the Bootloader and the Slinky Application Image</h3>
-<p>Run the <code>newt load nrf52_boot</code> command to load the bootloader onto the board:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load nrf52_boot
-Loading bootloader
-$
-</pre></div>
-
-
-<p><br>
-Run the <code>newt load nrf52_slinky</code> command to load the Slinky application image onto the board:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load nrf52_slinky
-Loading app image into slot 1
-$
-</pre></div>
-
-
-<p><br></p>
-<h3 id="connect-newtmgr-with-the-board-using-a-serial-connection">Connect Newtmgr with the Board using a Serial Connection</h3>
-<p>Set up a serial connection from your computer to the nRF52-DK board (See <a href="../../get_started/serial_access/">Serial Port Setup</a>). </p>
-<p>Locate the port, in the /dev directory on your computer, that the serial connection uses. It should be of the type <code>tty.usbserial-<some identifier></code>.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ ls /dev/tty*usbserial*
-/dev/tty.usbserial-1d11
-$
-</pre></div>
-
-
-<p><br>
-Setup a newtmgr connection profile for the serial port. For our example, the port is <code>/dev/tty.usbserial-1d11</code>. </p>
-<p>Run the <code>newtmgr conn add</code> command to define a newtmgr connection profile for the serial port. We name the connection profile <code>nrf52serial</code>. You will need to replace the <code>connstring</code> with the specific port for your serial connection. </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr conn add nrf52serial type=serial connstring=/dev/tty.usbserial-1d11
-Connection profile nrf52serial successfully added
-$
-</pre></div>
-
-
-<p><br>
-You can run the <code>newt conn show</code> command to see all the newtmgr connection profiles:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr conn show
-Connection profiles:
- nrf52serial: type=serial, connstring='/dev/tty.usbserial-1d11'
- sim1: type=serial, connstring='/dev/ttys012'
-$
-</pre></div>
-
-
-<p><br></p>
-<h3 id="use-newtmgr-to-query-the-board">Use Newtmgr to Query the Board</h3>
-<p>Run some newtmgr commands to query and receive responses back from the board (See the <a href="../newtmgr/overview">Newt Manager Guide</a> for more information on the newtmgr commands). </p>
-<p>Run the <code>newtmgr echo hello -c nrf52serial</code> command. This is the simplest command that requests the board to echo back the text. </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr echo hello -c nrf52serial
-hello
-$
-</pre></div>
-
-
-<p><br>
-Run the <code>newtmgr image list -c nrf52serial</code> command to list the images on the board:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr image list -c nrf52serial
-Images:
- slot=0
- version: 1.0.0
- bootable: true
- flags: active confirmed
- hash: f411a55d7a5f54eb8880d380bf47521d8c41ed77fd0a7bd5373b0ae87ddabd42
-Split status: N/A
-$
-</pre></div>
-
-
-<p><br>
-Run the <code>newtmgr taskstats -c nrf52serial</code> command to display the task statistics on the board:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newtmgr taskstats -c nrf52serial
-Return Code = 0
- task pri tid runtime csw stksz stkuse last_checkin next_checkin
- task1 8 2 0 1751 192 110 0 0
- task2 9 3 0 1751 64 31 0 0
- idle 255 0 224081 2068 64 32 0 0
- main 127 1 3 29 1024 365 0 0
-$
-</pre></div>
-
- <div class="row">
-
-
-
-
-<ul class="nav nav-pills" style="margin-bottom: 10px">
- <li>
-
- <a href=../project-slinky/>
- <span class="fa fa-arrow-left"></span>
- Previous: Slinky on sim device
- </a>
-
- </li>
- <li class="pull-right">
-
- <a href=../project-stm32-slinky/>
- Next: Slinky on STM32 board
- <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