You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by ad...@apache.org on 2017/03/27 06:41:34 UTC
[4/7] incubator-mynewt-site git commit: Added functions in task,
mempool, context switch
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/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 049df01..2f5038e 100644
--- a/develop/os/get_started/project_create/index.html
+++ b/develop/os/get_started/project_create/index.html
@@ -436,14 +436,13 @@ code for newt. If you need to use a different branch, you can set this in the pr
file. </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>
-<p>Changing to 0-dev will put you on the develop branch. <strong>The Develop Branch may not be stable and
-you may encounter bugs or other problems.</strong></p>
+<p>Changing to 1-dev will put you on the develop branch. <strong>The Develop Branch may not be stable and you may encounter bugs or other problems.</strong></p>
<p><br></p>
<h3 id="newt-install">Newt Install</h3>
<p>Once you've switched into your new project's directory, the next step is to fetch
@@ -460,7 +459,7 @@ use the <em>-v</em> (verbose) option to install. </p>
<p><br></p>
<p>Once <em>newt install</em> has successfully finished, the contents of <em>apache-mynewt-core</em> will have been downloaded into your local directory. You can view 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.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ tree -L 2 repos/apache-mynewt-core/
-repos/apache-mynewt-core/
+
repos/apache-mynewt-core/
\u251c\u2500\u2500 CODING_STANDARDS.md
\u251c\u2500\u2500 DISCLAIMER
@@ -473,10 +472,12 @@ repos/apache-mynewt-core/
\u2502�� \u251c\u2500\u2500 blehci
\u2502�� \u251c\u2500\u2500 bleprph
\u2502�� \u251c\u2500\u2500 bleprph_oic
+\u2502�� \u251c\u2500\u2500 blesplit
\u2502�� \u251c\u2500\u2500 bletest
\u2502�� \u251c\u2500\u2500 bletiny
\u2502�� \u251c\u2500\u2500 bleuart
\u2502�� \u251c\u2500\u2500 boot
+\u2502�� \u251c\u2500\u2500 fat2native
\u2502�� \u251c\u2500\u2500 ffs2native
\u2502�� \u251c\u2500\u2500 ocf_sample
\u2502�� \u251c\u2500\u2500 slinky
@@ -484,16 +485,20 @@ repos/apache-mynewt-core/
\u2502�� \u251c\u2500\u2500 spitest
\u2502�� \u251c\u2500\u2500 splitty
\u2502�� \u251c\u2500\u2500 test
+\u2502�� \u251c\u2500\u2500 testbench
\u2502�� \u2514\u2500\u2500 timtest
\u251c\u2500\u2500 boot
\u2502�� \u251c\u2500\u2500 boot_serial
\u2502�� \u251c\u2500\u2500 bootutil
-\u2502�� \u2514\u2500\u2500 split
+\u2502�� \u251c\u2500\u2500 split
+\u2502�� \u2514\u2500\u2500 split_app
\u251c\u2500\u2500 compiler
\u2502�� \u251c\u2500\u2500 arm-none-eabi-m0
\u2502�� \u251c\u2500\u2500 arm-none-eabi-m4
\u2502�� \u251c\u2500\u2500 gdbmacros
-\u2502�� \u2514\u2500\u2500 sim
+\u2502�� \u251c\u2500\u2500 mips
+\u2502�� \u251c\u2500\u2500 sim
+\u2502�� \u2514\u2500\u2500 sim-mips
\u251c\u2500\u2500 crypto
\u2502�� \u251c\u2500\u2500 mbedtls
\u2502�� \u2514\u2500\u2500 tinycrypt
@@ -505,6 +510,8 @@ repos/apache-mynewt-core/
\u2502�� \u251c\u2500\u2500 json
\u2502�� \u2514\u2500\u2500 tinycbor
\u251c\u2500\u2500 fs
+\u2502�� \u251c\u2500\u2500 disk
+\u2502�� \u251c\u2500\u2500 fatfs
\u2502�� \u251c\u2500\u2500 fcb
\u2502�� \u251c\u2500\u2500 fs
\u2502�� \u2514\u2500\u2500 nffs
@@ -550,7 +557,6 @@ repos/apache-mynewt-core/
\u2502�� \u251c\u2500\u2500 crash_test
\u2502�� \u251c\u2500\u2500 flash_test
\u2502�� \u251c\u2500\u2500 runtest
-\u2502�� \u251c\u2500\u2500 testreport
\u2502�� \u2514\u2500\u2500 testutil
\u251c\u2500\u2500 time
\u2502�� \u2514\u2500\u2500 datetime
@@ -559,7 +565,7 @@ repos/apache-mynewt-core/
\u251c\u2500\u2500 crc
\u2514\u2500\u2500 mem
-87 directories, 9 files
+94 directories, 9 files
</pre></div>
@@ -574,7 +580,30 @@ Compiling bootutil_misc.c
Compiling image_ec.c
Compiling image_rsa.c
Compiling image_validate.c
-<snip>
+
+ ...
+
+Linking ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf
+Executing test: ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf
+Testing package @apache-mynewt-core/sys/config/test-nffs
+Compiling repos/apache-mynewt-core/encoding/base64/src/hex.c
+Compiling repos/apache-mynewt-core/fs/fs/src/fs_cli.c
+Compiling repos/apache-mynewt-core/fs/fs/src/fs_dirent.c
+Compiling repos/apache-mynewt-core/fs/fs/src/fs_mkdir.c
+Compiling repos/apache-mynewt-core/fs/fs/src/fs_mount.c
+Compiling repos/apache-mynewt-core/encoding/base64/src/base64.c
+Compiling repos/apache-mynewt-core/fs/fs/src/fs_file.c
+Compiling repos/apache-mynewt-core/fs/disk/src/disk.c
+Compiling repos/apache-mynewt-core/fs/fs/src/fs_nmgr.c
+Compiling repos/apache-mynewt-core/fs/fs/src/fsutil.c
+Compiling repos/apache-mynewt-core/fs/nffs/src/nffs.c
+
+ ...
+
+Linking ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf
+Executing test: ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf
+Passed tests: [sys/config/test-fcb sys/config/test-nffs]
+All tests passed
</pre></div>
@@ -588,13 +617,19 @@ $ brew link gcc-5
<p><br></p>
<p>To test all the packages in a project, specify <code>all</code> instead of the package name.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt test all
+Testing package @apache-mynewt-core/boot/boot_serial/test
+Compiling repos/apache-mynewt-core/boot/boot_serial/test/src/boot_test.c
+Compiling repos/apache-mynewt-core/boot/boot_serial/test/src/testcases/boot_serial_setup.c
+
+ ...
+
+Linking ~/dev/myproj/bin/targets/unittest/boot_boot_serial_test/app/boot/boot_serial/test/boot_boot_serial_test.elf
+
...lots of compiling and testing...
-...about 2 minutes later ...
-Compiling mn_sock_test.c
-Archiving mn_socket.a
-Linking test_mn_socket
-Executing test: /Users/dsimmons/myproj/bin/unittest/sys/mn_socket/test_mn_socket
-Passed tests: [libs/json libs/util libs/mbedtls net/nimble/host hw/hal libs/bootutil sys/log sys/config sys/fcb fs/nffs libs/os libs/boot_serial sys/mn_socket]
+
+Linking ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf
+Executing test: ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf
+Passed 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]
All tests passed
</pre></div>
@@ -604,16 +639,21 @@ All tests passed
<p>To build and run your new application, simply issue the following command:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt build my_blinky_sim
Building target targets/my_blinky_sim
-Compiling main.c
-Archiving blinky.a
-Compiling hal_bsp.c
-Compiling os_bsp.c
-Compiling sbrk.c
-Archiving native.a
-Compiling flash_map.c
-<snip>
-Linking blinky.elf
-App successfully built: ~/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf
+Compiling repos/apache-mynewt-core/hw/hal/src/hal_common.c
+Compiling repos/apache-mynewt-core/hw/drivers/uart/src/uart.c
+Compiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c
+Compiling repos/apache-mynewt-core/hw/bsp/native/src/hal_bsp.c
+Compiling repos/apache-mynewt-core/hw/drivers/uart/uart_hal/src/uart_hal.c
+Compiling apps/blinky/src/main.c
+
+ ...
+
+
+Archiving sys_mfg.a
+Archiving sys_sysinit.a
+Archiving util_mem.a
+Linking ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf
+Target successfully built: targets/my_blinky_sim
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/get_started/serial_access/index.html
----------------------------------------------------------------------
diff --git a/develop/os/get_started/serial_access/index.html b/develop/os/get_started/serial_access/index.html
index abeb89a..9af8a51 100644
--- a/develop/os/get_started/serial_access/index.html
+++ b/develop/os/get_started/serial_access/index.html
@@ -396,7 +396,7 @@ which we'll connect to the Tx pin on the development board.</p>
<h2 id="setup-nordic-semiconductor-nrf52dk">Setup Nordic Semiconductor NRF52DK</h2>
<p>On the NRF52DK developer kit board, the Rx pin is P0.08, so you'll attach your
jumper wire from the Tx pin (D0) of the FT232H board here.</p>
-<p>The TX Pin is pin P0.08, so you'll attache the jumper wire from the Rx Pin (D1)
+<p>The TX Pin is pin P0.06, so you'll attache the jumper wire from the Rx Pin (D1)
on the FT232H board here. </p>
<p>Finally, the GND wire should go to the GND Pin on the NRF52DK. When you're
done, your wiring should look like this:</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/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 5ffd528..bc0dcc9 100644
--- a/develop/os/modules/bootloader/bootloader/index.html
+++ b/develop/os/modules/bootloader/bootloader/index.html
@@ -755,15 +755,7 @@ 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=d< bok@bok.net
-35d33
-< ericmanganaro@gmail.com
-42d39
-< tam@proxy.co
-55d51
-< nathan@natb1.com
-110d105
-< rvs@apache.orgone; 0xff=not done).</p>
+complete (0x01=done, 0xff=not done).</p>
</li>
<li>
<p>Image OK: A single byte indicating whether the image in this slot has been
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/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 f74224a..071be1e 100644
--- a/develop/os/tutorials/add_newtmgr/index.html
+++ b/develop/os/tutorials/add_newtmgr/index.html
@@ -698,7 +698,7 @@ your device has limited flash memory and cannot support Over-The-Air (OTA) firmw
<a href=../project-target-slinky/>
<span class="fa fa-arrow-left"></span>
- Previous: Slinky on STM32 board
+ Previous: Slinky on Nordic nRF52 board
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/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 588f1c7..30dde87 100644
--- a/develop/os/tutorials/arduino_zero/index.html
+++ b/develop/os/tutorials/arduino_zero/index.html
@@ -547,13 +547,13 @@
<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>Have a computer to build a Mynewt application and connect to your 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>This tutorial has been tested on the following three Arduino Zero boards - Zero, M0 Pro, and Zero-Pro.</p>
+<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;"/>
<img src="http://www.arduino.org/images/products/Arduino-M0Pro-flat.jpg" alt="Drawing" style="width: 310px;"/>
<img src="http://www.arduino.org//images/products/ArduinoZeroPro-flat-org.jpg" alt="Drawing" style="width: 310px;"/></p>
@@ -607,7 +607,7 @@ repository.apache-mynewt-core:
<p><br>
-Install the project dependencies using the <code>newt install</code> command (You can specify <code>-v</code> for verbose output):</p>
+Install the project dependencies using the <code>newt install</code> command (you can specify <code>-v</code> for verbose output):</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt install
apache-mynewt-core
mynewt_arduino_zero
@@ -617,11 +617,10 @@ $
<p><br></p>
<p><strong>NOTE:</strong> If there has been a new release of a repo used in your project since you last installed it, the <code>1-latest</code> version for the repo in the <code>project.yml</code> 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 <code>newt upgrade</code> to overwrite the existing files with the latest codebase.</p>
-<p><br></p>
-<h3 id="create-a-target-for-the-bootloader">Create a Target for the Bootloader</h3>
-<p>You need to create two targets, one for the bootloader and one for the Blinky application.<br />
+<p><br>
+You need to create two targets for the Arduino Zero Pro board, one for the bootloader and one for the Blinky application.<br />
<br>
-Run the following <code>newt target</code> commands, from your project directory (ex. ~/dev/myproj), to create a bootloader target for the Arduino Zero Pro board. We name the target <code>arduino_boot</code>.</p>
+Run the following <code>newt target</code> commands, from your project directory, to create a bootloader target. We name the target <code>arduino_boot</code>.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create arduino_boot
$ newt target set arduino_boot bsp=@mynewt_arduino_zero/hw/bsp/arduino_zero
Target targets/arduino_boot successfully created
@@ -635,7 +634,7 @@ $
</pre></div>
-<p><strong>Note:</strong> If you have an Arduino Zero instead of a Arduino Zero Pro board, replace <code>BSP_ARDUINO_ZERO_PRO</code> with <code>BSP_ARDUINO_ZERO</code> in the last <code>newt target set</code> command.</p>
+<p><strong>Note:</strong> If you have an Arduino Zero instead of an Arduino Zero Pro or Arduino M0 Pro board, replace <code>BSP_ARDUINO_ZERO_PRO</code> with <code>BSP_ARDUINO_ZERO</code> in the last <code>newt target set</code> command.</p>
<p>These commands perform the following:</p>
<ul>
<li>Create a target named <code>arduino_boot</code> for the Arduino Zero Bootloader. </li>
@@ -652,7 +651,7 @@ $
<p>See the <a href="../../get_started/vocabulary/">Concepts</a> section for more information on setting options.
<br></p>
<h3 id="create-a-target-for-the-blinky-application">Create a Target for the Blinky Application</h3>
-<p>Run the following <code>newt target</code> commands to create your Blinky application target. We name the application target <code>arduino_blinky</code>.</p>
+<p>Run the following <code>newt target</code> commands to create the Blinky application target. We name the application target <code>arduino_blinky</code>.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create arduino_blinky
Target targets/arduino_blinky successfully created
$ newt target set arduino_blinky app=apps/blinky
@@ -670,7 +669,7 @@ $
<p><strong>Note:</strong> If you have an Arduino Zero instead of a Arduino Zero Pro board, replace <code>BSP_ARDUINO_ZERO_PRO</code> with <code>BSP_ARDUINO_ZERO</code> in the last <code>newt target set</code> command.</p>
<p><br></p>
<h3 id="build-the-bootloader">Build the Bootloader</h3>
-<p>Run the <code>newt build arduino_boot</code> command to build a bootloader for your arduino board:</p>
+<p>Run the <code>newt build arduino_boot</code> command to build the bootloader:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt build arduino_boot
Building target targets/arduino_boot
Compiling bin/targets/arduino_boot/generated/src/arduino_boot-sysinit-app.c
@@ -697,7 +696,7 @@ Target successfully built: targets/arduino_boot
<p><br></p>
<h3 id="build-the-blinky-application">Build the Blinky Application</h3>
-<p>Run the <code>newt build arduino_blinky</code> command to build your Blinky application image:</p>
+<p>Run the <code>newt build arduino_blinky</code> command to build the Blinky application image:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt build arduino_blinky
Building target targets/arduino_blinky
Compiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c
@@ -722,7 +721,7 @@ Target successfully built: targets/arduino_blinky
<p>Connect your computer to the Arduino Zero (from now on we'll call this the
target) with a Micro-USB cable through the Programming Port as shown below.
Mynewt will load the image onto the board and debug the target through this port. You should see a
-little green LED come on. That means the board has power.</p>
+green LED come on that indicates the board has power.</p>
<p>No external debugger is required. The Arduino Zero comes with an internal
debugger that can be accessed by Mynewt.</p>
<p>The images below show the Arduino Zero Programming Port.</p>
@@ -730,18 +729,18 @@ debugger that can be accessed by Mynewt.</p>
<img src="http://www.arduino.org//images/products/ArduinoZeroPro-flat-org.jpg" alt="Drawing" style="width: 330px;"/></p>
<p><br></p>
<h3 id="load-the-bootloader-onto-the-board">Load the Bootloader onto the Board</h3>
-<p>Run the <code>newt load arduino_boot</code> command to load the bootloader onto your board:</p>
+<p>Run the <code>newt load arduino_boot</code> command to load the bootloader onto the board:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load arduino_boot
Loading bootloader
$
</pre></div>
-<p>The bootloader is loaded onto your board succesfully when the <code>newt load</code> command returns to the command prompt with no messages. You can proceed to load and run your Blinky application image (See <a href="#runimage">Run the Blinky Application</a>).</p>
-<p>If the <code>newt load</code> command outputs the following error messages, you will need to erase your board.</p>
+<p>The bootloader is loaded onto your board succesfully when the <code>newt load</code> command returns to the command prompt after the <code>Loading bootloader</code> status message. You can proceed to load and run your Blinky application image (See <a href="#runimage">Run the Blinky Application</a>).</p>
+<p>If the <code>newt load</code> command outputs the following error messages, you will need to erase the board.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load arduino_boot -v
Loading bootloader
-Error: Downloading ~/dev/arduino_zero/bin/targets/arduino_boot/app/apps/boot/boot.elf.bin to 0x0
+Error: Downloading ~/dev/myproj/bin/targets/arduino_boot/app/apps/boot/boot.elf.bin to 0x0
Open On-Chip Debugger 0.9.0 (2015-11-15-05:39)
Licensed under GNU GPL v2
For bug reports, read
@@ -788,8 +787,8 @@ Run the <code>newt load arduino_boot</code> command again after erasing the boar
<p><br></p>
<h3 id="run-the-blinky-application"><a name="runimage"></a>Run the Blinky Application</h3>
<p>After you load the bootloader successfully onto your board, you can load and run the Blinky application. </p>
-<p>Run the <code>newt run arduino_blinky 0.0.0</code> command to build the arduino_blinky target (if necessary), create an image with verison 0.0.0, load the image onto the board, and start a debugger session. </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt run arduino_blinky 0.0.0
+<p>Run the <code>newt run arduino_blinky 1.0.0</code> command to build the arduino_blinky target (if necessary), create an image with version 1.0.0, load the image onto the board, and start a debugger session. </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt run arduino_blinky 1.0.0
App image succesfully generated: ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.img
Loading app image into slot 1
[~/dev/myproj/repos/mynewt_arduino_zero/hw/bsp/arduino_zero/arduino_zero_debug.sh ~/dev/myproj/repos/mynewt_arduino_zero/hw/bsp/arduino_zero ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky]
@@ -845,7 +844,7 @@ Continuing.
<p><br></p>
-<p><strong>NOTE:</strong> The 0.0.0 is the version number to assign to the images. If you are not providing remote upgrade, and are just developing locally, you can provide 0.0.0 for every image version.</p>
+<p><strong>NOTE:</strong> The 1.0.0 is the version number to assign to the image. You may assign an arbitrary version number. If you are not providing remote upgrade, and are just developing locally, you can provide 1.0.0 for every image version.</p>
<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>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/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 5e779e3..272f6e5 100644
--- a/develop/os/tutorials/blinky_primo/index.html
+++ b/develop/os/tutorials/blinky_primo/index.html
@@ -550,12 +550,12 @@
<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>Have a computer to build a Mynewt application and connect to your 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>
-<li>Debugger - choose one of the two options below. Option 1 requires additional hardware but very easy to set up. Option 2 is free software install but not as simple as Option 1.</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 install but not as simple as Option 1.</li>
</ul>
<p><br></p>
<h5 id="option-1">Option 1</h5>
@@ -564,9 +564,7 @@
<li><a href="https://www.segger.com/jlink-adapters.html#CM_9pin">J-Link 9 pin Cortex-M Adapter</a> that allows JTAG, SWD and SWO connections between J-Link and Cortex M based target hardware systems</li>
</ul>
<h5 id="option-2">Option 2</h5>
-<ul>
-<li>No additional hardware is required but a version of OpenOCD 0.10.0 that is currently in development needs to be installed. A patch for the nRF52 has been applied to the OpenOCD code in development and a tarball has been made available for download <a href="../downloads/openocd-wnrf52.tgz">here</a>. Untar it. From the top of the directory tree ("openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4"), build it using the following configuration:</li>
-</ul>
+<p>No additional hardware is required but a version of OpenOCD 0.10.0 that is currently in development needs to be installed. A patch for the nRF52 has been applied to the OpenOCD code in development and a tarball has been made available for download <a href="../downloads/openocd-wnrf52.tgz">here</a>. Untar it. From the top of the directory tree ("openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4"), build it using the following configuration:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$./configure --enable-cmsis-dap --enable-openjtag_ftdi --enable-jlink --enable-stlink
</pre></div>
@@ -614,14 +612,14 @@ $ go install
<p><br></p>
<h3 id="create-the-targets"><a name="create_targets"></a>Create the Targets</h3>
<p>Create two targets for the Arduino Primo board - one for the bootloader and one for the Blinky application.</p>
-<p>Run the following <code>newt target</code> commands to create a bootloader target. We name the target <code>primo_boot</code>:</p>
+<p>Run the following <code>newt target</code> commands, from your project directory, to create a bootloader target. We name the target <code>primo_boot</code>.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create primo_boot
$ newt target set primo_boot app=@apache-mynewt-core/apps/boot bsp=@apache-mynewt-core/hw/bsp/arduino_primo_nrf52 build_profile=optimized
</pre></div>
<p><br>
-Run the following <code>newt target</code> commands to create a target for your Blinky application. We name the target <code>primoblinky</code>:</p>
+Run the following <code>newt target</code> commands to create a target for the Blinky application. We name the target <code>primoblinky</code>.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create primoblinky
$ newt target set primoblinky app=apps/blinky bsp=@apache-mynewt-core/hw/bsp/arduino_primo_nrf52 build_profile=debug
</pre></div>
@@ -629,13 +627,13 @@ $ newt target set primoblinky app=apps/blinky bsp=@apache-mynewt-core/hw/bsp/ard
<p><br>
If you are using openocd, run the following <code>newt target set</code> commands:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target set primoblinky syscfg=OPENCD_DEBUG=1
-$ newt target set primo_boot syscfg=OPENCD_DEBUG=1
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target set primoblinky syscfg=OPENOCD_DEBUG=1
+$ newt target set primo_boot syscfg=OPENOCD_DEBUG=1
</pre></div>
<p><br>
-You can run the <code>newt target show</code> command to verify your target settings:</p>
+You can run the <code>newt target show</code> command to verify the target settings:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target show
targets/my_blinky_sim
app=apps/blinky
@@ -707,12 +705,14 @@ App image succesfully generated: ~/dev/myproj/bin/targets/primoblinky/app/apps/b
<p><br></p>
<h3 id="connect-to-the-board">Connect to the Board</h3>
-<p>Connect the Segger J-Link debug probe to the JTAG port on the Primo board using the Jlink 9-pin adapter and cable. Note that there are two JTAG ports on the board. Use the one nearest to the reset button as shown in the picture. Also use a micro USB 2.0 cable to connect the Primo board to one of your laptop's USB host ports.</p>
+<ul>
+<li>Connect a micro USB cable to the Arduino Primo board and to your computer's USB port.</li>
+<li>If you are using the Segger J-Link debug probe, connect the debug probe to the JTAG port on the Primo board using the Jlink 9-pin adapter and cable. Note that there are two JTAG ports on the board. Use the one nearest to the reset button as shown in the picture. </li>
+</ul>
<p><img alt="J-Link debug probe to Arduino" src="../pics/primo-jlink.jpg" title="Connecting J-Link debug probe to Arduino Primo" /></p>
-<p><br></p>
-<p><strong>Note:</strong> If you are going the OpenOCD route, you do not need to attach this connector. </p>
+<p><strong>Note:</strong> If you are using the OpenOCD debugger, you do not need to attach this connector. </p>
<h3 id="load-the-bootloader-and-the-blinky-application-image">Load the Bootloader and the Blinky Application Image</h3>
-<p>Run the <code>newt load primo_boot</code> command to load the bootloader onto your board:</p>
+<p>Run the <code>newt load primo_boot</code> command to load the bootloader onto the board:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load primo_boot
Loading bootloader
$
@@ -720,15 +720,15 @@ $
<p><br>
-Run the <code>newt load primoblinky</code> command to load Blinky application image onto your board.</p>
+Run the <code>newt load primoblinky</code> command to load the Blinky application image onto the board.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load primoblinky
Loading app image into slot 1
$
</pre></div>
-<p>You should see the LED on your board blink!</p>
-<p>Note: If the LED does not blink, try resetting your board.</p>
+<p>You should see the LED on the board blink!</p>
+<p>Note: If the LED does not blink, try resetting the board.</p>
<p><br></p>
<p><strong>Note:</strong> If you want to erase the flash and load the image again, you can use JLinkExe to issue an <code>erase</code> command.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ JLinkExe -device nRF52 -speed 4000 -if SWD
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/tutorials/nRF52/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/nRF52/index.html b/develop/os/tutorials/nRF52/index.html
index e0c361e..407cd90 100644
--- a/develop/os/tutorials/nRF52/index.html
+++ b/develop/os/tutorials/nRF52/index.html
@@ -543,9 +543,9 @@
<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 nRF52 board from Nordic Semiconductors. Download the application to the target and watch it blink!</p>
-<p>Note that there are several versions of the nRF52 in the market. The boards tested with this tutorial are listed under "Hardware needed" below.</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="prerequistes">Prerequistes</h3>
+<h3 id="prerequisites">Prerequisites</h3>
<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
<ul>
<li>Have a nRF52 Development Kit (one of the following)<ul>
@@ -554,13 +554,14 @@
</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>Have computer to build a Mynewt application and connect to your 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><br></p>
+<p>This tutorial uses the Nordic nRF52-DK board.
+<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 have a project created. </p>
<p>Run the following commands to create a new project:</p>
@@ -580,9 +581,9 @@
<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 Blinky application.</p>
-<p>Run the following <code>newt target</code> commands, from your project directory (~/dev/myproj), to create a bootloader target. We name the target <code>nrf52_boot</code>:</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>
<p><font color="#F2853F">
-Note: For this tutorial, we are using the nRF52-DK board. You must specify the correct bsp for the board you are using. </font> </p>
+Note: This tutorial uses the Nordic nRF52-DK board. You must specify the correct bsp for the board you are using. </font> </p>
<ul>
<li>For the Nordic Dev Kit choose @apache-mynewt-core/hw/bsp/nrf52dk instead (in the highlighted lines)</li>
<li>For the Rigado Eval Kit choose @apache-mynewt-core/hw/bsp/bmd300eval instead (in the highlighted lines)</li>
@@ -595,7 +596,7 @@ $ newt target set nrf52_boot app=@apache-mynewt-core/apps/boot
<p><br>
-Run the following <code>newt target</code> commands to create a target for your Blinky application. We name the target <code>nrf52_blinky</code>:</p>
+Run the following <code>newt target</code> commands to create a target for the Blinky application. We name the target <code>nrf52_blinky</code>.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create nrf52_blinky
$ newt target set nrf52_blinky app=apps/blinky
<span style="background-color: #ffffcc">$ newt target set nrf52_blinky bsp=@apache-mynewt-core/hw/bsp/nrf52dk
@@ -604,7 +605,7 @@ $ newt target set nrf52_blinky app=apps/blinky
<p><br>
-You can run the <code>newt target show</code> command to verify your target settings:</p>
+You can run the <code>newt target show</code> command to verify the target settings:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target show
targets/nrf52_blinky
app=apps/blinky
@@ -673,11 +674,11 @@ App image succesfully generated: ~/dev/myproj/bin/targets/nrf52_blinky/app/apps/
<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 your nRF52-DK board.</li>
+<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>
<h3 id="load-the-bootloader-and-the-blinky-application-image">Load the Bootloader and the Blinky Application Image</h3>
-<p>Run the <code>newt load nrf52_boot</code> command to load the bootloader onto your board: </p>
+<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
$
@@ -685,13 +686,13 @@ $
<p><br>
-Run the <code>newt load nrf52_blinky</code> command to load Blinky application image onto your board.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt -v load nrf52_blinky
+Run the <code>newt load nrf52_blinky</code> command to load the Blinky application image onto the board.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load nrf52_blinky
Loading app image into slot 1
</pre></div>
-<p>You should see the LED1 on your board blink!</p>
+<p>You should see the LED1 on the board blink!</p>
<p>Note: If the LED does not blink, try resetting your board.</p>
<p><br></p>
<p><strong>Note:</strong> If you want to erase the flash and load the image again, you can use JLinkExe to issue an <code>erase</code> command.</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/tutorials/olimex/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/olimex/index.html b/develop/os/tutorials/olimex/index.html
index f07fa3d..b6dddcc 100644
--- a/develop/os/tutorials/olimex/index.html
+++ b/develop/os/tutorials/olimex/index.html
@@ -548,9 +548,9 @@
<ul>
<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 USB A-B type cable to connect the debugger to your personal computer.</li>
<li>Have Internet connectivity to fetch remote Mynewt components.</li>
-<li>Have a computer to build a Mynewt application and connect to your board over USB.</li>
+<li>Have a computer to build a Mynewt application and connect to the board over USB.</li>
+<li>Have USB A-B type cable to connect the debugger to your 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>
@@ -577,7 +577,7 @@
<p><br></p>
<h3 id="create-the-targets"><a name="create_targets"></a>Create the Targets</h3>
<p>Create two targets for the Olimex board - one for the bootloader and one for the Blinky application.</p>
-<p>Run the following <code>newt target</code> commands to create a bootloader target. We name the target <code>boot_olimex</code>:</p>
+<p>Run the following <code>newt target</code> commands, from your project directory, to create a bootloader target. We name the target <code>boot_olimex</code>.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create boot_olimex
$ newt target set boot_olimex build_profile=optimized
$ newt target set boot_olimex app=@apache-mynewt-core/apps/boot
@@ -586,7 +586,7 @@ $ newt target set boot_olimex bsp=@apache-mynewt-core/hw/bsp/olimex_stm32-e407_d
<p><br>
-Run the following <code>newt target</code> commands to create a target for your Blinky application. We name the target <code>olimex_blinky</code>:</p>
+Run the following <code>newt target</code> commands to create a target for the Blinky application. We name the target <code>olimex_blinky</code>.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create olimex_blinky
$ newt target set olimex_blinky build_profile=debug
$ newt target set olimex_blinky bsp=@apache-mynewt-core/hw/bsp/olimex_stm32-e407_devboard
@@ -596,7 +596,7 @@ $ newt target set olimex_blinky app=apps/blinky
<p><br></p>
<h3 id="build-the-bootloader">Build the Bootloader</h3>
-<p>Run the <code>newt build boot_olimex</code> command to build the boot loader image:</p>
+<p>Run the <code>newt build boot_olimex</code> command to build the bootloader:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt build boot_olimex
Building target targets/boot_olimex
Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c
@@ -644,7 +644,7 @@ Target successfully built: targets/olimex_blinky
<p><br></p>
<h3 id="sign-and-create-the-blinky-application-image">Sign and Create the Blinky Application Image</h3>
-<p>Run the <code>newt create-image olimex_blinky 1.0.0</code> command to sign and create an image file for your blinky application. You may assign an arbitrary version (e.g. 1.0.0) number.</p>
+<p>Run the <code>newt create-image olimex_blinky 1.0.0</code> command to sign and create an image file for the blinky application. You may assign an arbitrary version (e.g. 1.0.0) number.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt create-image olimex_blinky 1.0.0
App image succesfully generated: ~/dev/myproj/bin/targets/olimex_blinky/app/apps/blinky/blinky.img
</pre></div>
@@ -652,7 +652,7 @@ App image succesfully generated: ~/dev/myproj/bin/targets/olimex_blinky/app/apps
<p><br></p>
<h3 id="connect-to-the-board">Connect to the Board</h3>
-<p>Configure your board to bootload from flash memory and to use the JTAG/SWD for the power source. Refer to the following diagrams to locate the boot jumpers and power input select jumpers on your board.
+<p>Configure the board to bootload from flash memory and to use the JTAG/SWD for the power source. Refer to the following diagrams to locate the boot jumpers and power input select jumpers on the board.
<br></p>
<p align="center">
<img src="../pics/STM32-E407_top_small.jpg"></img>
@@ -667,13 +667,13 @@ App image succesfully generated: ~/dev/myproj/bin/targets/olimex_blinky/app/apps
<strong>Note:</strong> The markings on the board may not always be accurate, and you should always refer to the manual for the correct positioning. </p>
</li>
<li>
-<p>Locate the <strong>Power Input Select</strong> jumpers on the lower left corner of the board. Set the Power Select jumpers to position 3 and 4 to use the JTAG/SWD for the power source. If you would like to use a different power source, refer to [OLIMEZ STM32-E407] user manual](https://www.olimex.com/Products/ARM/ST/STM32-E407/resources/STM32-E407.pdf) to pin specificiation.</p>
+<p>Locate the <strong>Power Input Select</strong> jumpers on the lower left corner of the board. Set the Power Select jumpers to position 3 and 4 to use the JTAG/SWD for the power source. If you would like to use a different power source, refer to the <a href="https://www.olimex.com/Products/ARM/ST/STM32-E407/resources/STM32-E407.pdf">OLIMEX STM32-E407 user manual</a> for pin specifications.</p>
</li>
<li>
<p>Connect the JTAG connector to the JTAG/SWD interface on the board. </p>
</li>
<li>
-<p>Connect the USB A-B cable to the ARM-USB-TINY-H connector and your personal computer. </p>
+<p>Connect the USB A-B cable to the ARM-USB-TINY-H connector and your computer.</p>
</li>
<li>
<p>Check that the red PWR LED lights up.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/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 8674d78..360ae92 100644
--- a/develop/os/tutorials/project-slinky/index.html
+++ b/develop/os/tutorials/project-slinky/index.html
@@ -306,7 +306,7 @@
<li >
- <a href="../project-target-slinky/">Slinky on STM32 board</a>
+ <a href="../project-target-slinky/">Slinky on Nordic nRF52 board</a>
</li>
@@ -633,7 +633,7 @@ logs, image status (not on sim), and configuration.</p>
<li class="pull-right">
<a href=../project-target-slinky/>
- Next: Slinky on STM32 board
+ Next: Slinky on Nordic nRF52 board
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/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
index 3bbf2d8..9f622db 100644
--- a/develop/os/tutorials/project-target-slinky/index.html
+++ b/develop/os/tutorials/project-target-slinky/index.html
@@ -10,7 +10,7 @@
<link rel="canonical" href="http://mynewt.apache.org/os/tutorials/project-target-slinky/"> -->
<link rel="shortcut icon" href="../../../img/favicon.ico">
- <title>Slinky on STM32 board - Apache Mynewt</title>
+ <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">
@@ -41,7 +41,7 @@
</head>
- <body class="Slinky on STM32 board">
+ <body class="Slinky on Nordic nRF52 board">
<div class="container">
@@ -306,7 +306,7 @@
<li class="active">
- <a href="./">Slinky on STM32 board</a>
+ <a href="./">Slinky on Nordic nRF52 board</a>
</li>
@@ -487,7 +487,7 @@
- <li>» Slinky on STM32 board</li>
+ <li>» Slinky on Nordic nRF52 board</li>
@@ -495,167 +495,208 @@
</div>
</div>
- <h2 id="project-slinky-using-stm32-board">Project Slinky using STM32 board</h2>
+ <h2 id="project-slinky-using-the-nordic-nrf52-board">Project Slinky using the Nordic nRF52 Board</h2>
<p><br></p>
-<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 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>
-<h3 id="what-you-need">What you need</h3>
-<ol>
-<li>STM32-E407 development board from Olimex. You can order it from <a href="http://www.mouser.com/search/ProductDetail.aspx?R=0virtualkey0virtualkeySTM32-E407">http://www.mouser.com</a>, <a href="http://www.digikey.com/product-detail/en/STM32-E407/1188-1093-ND/3726951">http://www.digikey.com</a>, and other places.</li>
-<li>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>USB A-B type cable to connect the debugger to your personal computer</li>
-<li>A USB to TTL Serial Cable with female wiring harness. An example is <a href="http://www.amazon.com/JBtek�-WINDOWS-Supported-Raspberry-Programming/dp/B00QT7LQ88/ref=lp_464404_1_9?s=pc&ie=UTF8&qid=1454631303&sr=1-9">http://www.amazon.com/JBtek�-WINDOWS-Supported-Raspberry-Programming/dp/B00QT7LQ88/ref=lp_464404_1_9?s=pc&ie=UTF8&qid=1454631303&sr=1-9</a></li>
-<li>Personal Computer</li>
-</ol>
-<p>The instructions assume the user is using a Bourne-compatible shell (e.g. bash or zsh) on your computer. The given instructions have been tested with the following releases of operating systems:</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>Mac: OS X Yosemite Version 10.10.5</li>
+<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>
+<h3 id="overview-of-steps">Overview of Steps</h3>
<ul>
<li>Install dependencies</li>
-<li>Define a target using the newt tool</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="install-newt">Install newt</h3>
-<p>If you have not already installed <code>newt</code>, see the
-<a href="../../get_started/get_started/">newt installation instructions</a> and ensure newt is installed an in your path.</p>
-<h3 id="install-newtmgr">Install newtmgr</h3>
-<p>If you have not already installed <code>newtmgr</code>, see the
-<a href="../../../newtmgr/installing/">newtmgr installation instructions</a> and ensure newtmgr is installed an in your path.</p>
-<h3 id="create-a-new-project">Create 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>If you already completed <a href="../project-slinky/">Sim Slinky</a> you can skip this step.</p>
-<p>We will list only the steps here for brevity. We will name the project
-<code>slinky</code>.</p>
+<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 slink successfully created
+Project slinky successfully created
$ cd slinky
-$newt install -v
-Downloading repository description for apache-mynewt-core... success!
-...
-Repos successfully installed
+$newt install
+apache-mynewt-core
</pre></div>
<p><br></p>
-<h3 id="set-up-your-target-builds">Set up your target builds</h3>
-<p>Create a target for <code>stm32_slinky</code> using the native BSP. The Newt tool output is suppressed below for brevity.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create stm32_slinky
-$ newt target set stm32_slinky bsp=@apache-mynewt-core/hw/bsp/olimex_stm32-e407_devboard
-$ newt target set stm32_slinky build_profile=debug
-$ newt target set stm32_slinky app=@apache-mynewt-core/apps/slinky
+<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>Create a second target for <code>stm32_bootloader</code> to build a bootloader to boot
-the <code>stm32_slinky</code> image. The tool output is suppressed below for brevity.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create stm32_bootloader
-$ newt target set stm32_bootloader bsp=@apache-mynewt-core/hw/bsp/olimex_stm32-e407_devboard
-$ newt target set stm32_bootloader build_profile=optimized
-$ newt target set stm32_bootloader target.app=@apache-mynewt-core/apps/boot
+<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-targets">Build Targets</h3>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt build stm32_slinky
-Compiling main.c
-...
-Linking slinky.elf
-App successfully built: ~/dev/slinky/bin/stm32_slinky/apps/slinky/slinky.elf
+<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>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">newt build stm32_bootloader
-Compiling crc16.c
-...
-Linking boot.elf
-App successfully built: ~/slinky/bin/stm32_bootloader/apps/boot/boot.elf
+<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>For the main image, you need to create an image using newt create-image.
-Give this image some arbitrary version number "1.2.3".</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt create-image stm32_slinky 1.2.3
-App image successfully generated: /Users/paulfdietrich/dev/slinky/bin/stm32_slinky/apps/slinky/slinky.img
-Build manifest: /Users/paulfdietrich/dev/slinky/bin/stm32_slinky/apps/slinky/manifest.json
+<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="using-newtmgr-with-a-remote-target">Using newtmgr with a remote target</h3>
+<h3 id="connect-to-the-board">Connect to the Board</h3>
<ul>
-<li>
-<p>First make sure the USB A-B type cable is connected to the ARM-USB-TINY-H debugger connector on the Olimex board.</p>
-<p>Next go the to project directory and download the slinky project image to the flash of the Olimex board.</p>
-</li>
+<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>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt load stm32_bootloader
-$ newt load stm32_slinky
+<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>You can now disconnect the debugging cable from the board. You should see the green LED blinking. If not, try powercycling the board.</p>
-<p><br></p>
-<ul>
-<li>
-<p>Now you have to set up the serial connection from your computer to the Olimex board. Locate the PC6/USART6_TX (pin#3), PC7/USART6_RX (pin#4), and GND (pin#2) of the UEXT connector on the Olimex board. More information on the UEXT connector can be found at <a href="https://www.olimex.com/Products/Modules/UEXT/">https://www.olimex.com/Products/Modules/UEXT/</a>. The schematic of the board can be found at <a href="https://www.olimex.com/Products/ARM/ST/STM32-E407/resources/STM32-E407_sch.pdf">https://www.olimex.com/Products/ARM/ST/STM32-E407/resources/STM32-E407_sch.pdf</a> for reference.</p>
-<p><img alt="Alt Layout - Serial Connection" src="../pics/serial_conn.png" /></p>
-<ul>
-<li>Connect the female RX pin of the USB-TTL serial cable to the TX of the UEXT connector on the board.</li>
-<li>Connect the female TX pin of the USB-TTL serial cable to the RX of the UEXT connector on the board.</li>
-<li>Connect the GND pin of the USB-TTL serial cable to the GND of the UEXT connector on the board.</li>
-</ul>
-</li>
-</ul>
-<p><br></p>
-<ul>
-<li>Locate the serial connection established in the /dev directory of your computer. It should be of the type <code>tty.usbserial-<some identifier></code>.</li>
-</ul>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ ls /dev/tty.usbserial-AJ03HAQQ
- /dev/tty.usbserial-AJ03HAQQ
+<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>
-<ul>
-<li>You now have to define a connection profile using newtmgr. You can give it any name you want. The example below shows the connection profile being named as the very imaginative <code>olimex01</code>.</li>
-</ul>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ pwd
- /Users/<user>/dev/project/slinky
- $ newtmgr conn add olimex01 type=serial connstring=/dev/tty.usbserial-AJ03HAQQ
- Connection profile olimex01 successfully added
- $ newtmgr conn show
- Connection profiles:
- sim1: type=serial, connstring='/dev/ttys007'
- olimex01: type=serial, connstring='/dev/tty.usbserial-AJ03HAQQ'
+<h3 id="connect-newtmgr-with-the-board-using-a-serial-connection">Connect Newtmgr with the Board using a Serial Connection</h3>
+<p>Set up 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>
-<ul>
-<li>Now go ahead and query the Olimex board to get responses back. The simplest command is the <code>echo</code> command to ask it to respond with the text you send it.</li>
-</ul>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newtmgr echo -c olimex01 hello
- {"r": "hello"}
- $ newtmgr image -c olimex01 list
- Images:
- 0 : 1.2.3
- $ newtmgr -c olimex01 taskstats
- Return Code = 0
- newtmgr (prio=4 tid=2 runtime=0 cswcnt=12 stksize=512 stkusage=255 last_checkin=0 next_checkin=0)
- task1 (prio=1 tid=3 runtime=0 cswcnt=299 stksize=128 stkusage=33 last_checkin=0 next_checkin=0)
- task2 (prio=2 tid=4 runtime=0 cswcnt=300 stksize=128 stkusage=31 last_checkin=0 next_checkin=0)
- idle (prio=255 tid=0 runtime=299916 cswcnt=313 stksize=32 stkusage=18 last_checkin=0 next_checkin=0)
- shell (prio=3 tid=1 runtime=1 cswcnt=20 stksize=384 stkusage=60 last_checkin=0 next_checkin=0)
+<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">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/sitemap.xml
----------------------------------------------------------------------
diff --git a/develop/sitemap.xml b/develop/sitemap.xml
index 5bf7961..1c69dde 100644
--- a/develop/sitemap.xml
+++ b/develop/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,7 +13,7 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -22,7 +22,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -30,7 +30,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -38,7 +38,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -46,7 +46,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -54,7 +54,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -62,7 +62,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -71,7 +71,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -83,7 +83,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -123,13 +123,13 @@
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>