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:31 UTC
[1/7] incubator-mynewt-site git commit: Added functions in task,
mempool, context switch
Repository: incubator-mynewt-site
Updated Branches:
refs/heads/asf-site 7d514c155 -> 6b7450f63
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/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 6152acf..5cad4fc 100644
--- a/latest/os/get_started/project_create/index.html
+++ b/latest/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/latest/os/get_started/serial_access/index.html
----------------------------------------------------------------------
diff --git a/latest/os/get_started/serial_access/index.html b/latest/os/get_started/serial_access/index.html
index 284120b..84f01a2 100644
--- a/latest/os/get_started/serial_access/index.html
+++ b/latest/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/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 c61ba5a..c472ff4 100644
--- a/latest/os/modules/bootloader/bootloader/index.html
+++ b/latest/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/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 c0320a1..1b0ca8d 100644
--- a/latest/os/tutorials/add_newtmgr/index.html
+++ b/latest/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/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 db79882..88f0ce3 100644
--- a/latest/os/tutorials/arduino_zero/index.html
+++ b/latest/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/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 ec721f2..c07ceae 100644
--- a/latest/os/tutorials/blinky_primo/index.html
+++ b/latest/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/latest/os/tutorials/nRF52/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/nRF52/index.html b/latest/os/tutorials/nRF52/index.html
index fe879f9..653adc9 100644
--- a/latest/os/tutorials/nRF52/index.html
+++ b/latest/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/latest/os/tutorials/olimex/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/olimex/index.html b/latest/os/tutorials/olimex/index.html
index 47acbfa..2442556 100644
--- a/latest/os/tutorials/olimex/index.html
+++ b/latest/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/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 1c9bb8a..f21fa32 100644
--- a/latest/os/tutorials/project-slinky/index.html
+++ b/latest/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/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
index d378dc2..f7c88aa 100644
--- a/latest/os/tutorials/project-target-slinky/index.html
+++ b/latest/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/latest/sitemap.xml
----------------------------------------------------------------------
diff --git a/latest/sitemap.xml b/latest/sitemap.xml
index 5bf7961..1c69dde 100644
--- a/latest/sitemap.xml
+++ b/latest/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>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/sitemap.xml
----------------------------------------------------------------------
diff --git a/sitemap.xml b/sitemap.xml
index 7c5d2e1..7379b52 100644
--- a/sitemap.xml
+++ b/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,13 +13,13 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/pages/securitybullets/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -28,7 +28,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -36,7 +36,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -44,7 +44,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -52,7 +52,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -60,7 +60,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -68,7 +68,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -77,7 +77,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -89,7 +89,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>
@@ -129,13 +129,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>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/v0_9_0/sitemap.xml
----------------------------------------------------------------------
diff --git a/v0_9_0/sitemap.xml b/v0_9_0/sitemap.xml
index 7c5d2e1..7379b52 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-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,13 +13,13 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/pages/securitybullets/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -28,7 +28,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -36,7 +36,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -44,7 +44,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -52,7 +52,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -60,7 +60,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -68,7 +68,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -77,7 +77,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-03-24</lastmod>
+ <lastmod>2017-03-26</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -89,7 +89,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>
@@ -129,13 +129,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>
[2/7] incubator-mynewt-site git commit: Added functions in task,
mempool, context switch
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/context_switch/context_switch/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/context_switch/context_switch/index.html b/latest/os/core_os/context_switch/context_switch/index.html
index fd5b2cb..b3c0e17 100644
--- a/latest/os/core_os/context_switch/context_switch/index.html
+++ b/latest/os/core_os/context_switch/context_switch/index.html
@@ -738,6 +738,10 @@
<td>Inform scheduler that OS time has moved forward.</td>
</tr>
<tr>
+<td><a href="../os_sched_remove/">os_sched_remove</a></td>
+<td>Stops a task and removes it from all the OS task lists.</td>
+</tr>
+<tr>
<td><a href="../os_sched_resort/">os_sched_resort</a></td>
<td>Inform scheduler that the priority of the given task has changed and the <em>ready to run</em> list should be re-sorted.</td>
</tr>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/context_switch/os_arch_ctx_sw/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/context_switch/os_arch_ctx_sw/index.html b/latest/os/core_os/context_switch/os_arch_ctx_sw/index.html
index 796ed97..c62d3b6 100644
--- a/latest/os/core_os/context_switch/os_arch_ctx_sw/index.html
+++ b/latest/os/core_os/context_switch/os_arch_ctx_sw/index.html
@@ -344,6 +344,14 @@
<li >
+ <a href="../os_sched_remove/">os_sched_remove</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_sched_resort/">os_sched_resort</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/context_switch/os_sched/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/context_switch/os_sched/index.html b/latest/os/core_os/context_switch/os_sched/index.html
index 82f2cc2..024fb24 100644
--- a/latest/os/core_os/context_switch/os_sched/index.html
+++ b/latest/os/core_os/context_switch/os_sched/index.html
@@ -344,6 +344,14 @@
<li >
+ <a href="../os_sched_remove/">os_sched_remove</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_sched_resort/">os_sched_resort</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/context_switch/os_sched_ctx_sw_hook/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/context_switch/os_sched_ctx_sw_hook/index.html b/latest/os/core_os/context_switch/os_sched_ctx_sw_hook/index.html
index 52602f9..310bc85 100644
--- a/latest/os/core_os/context_switch/os_sched_ctx_sw_hook/index.html
+++ b/latest/os/core_os/context_switch/os_sched_ctx_sw_hook/index.html
@@ -344,6 +344,14 @@
<li >
+ <a href="../os_sched_remove/">os_sched_remove</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_sched_resort/">os_sched_resort</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/context_switch/os_sched_get_current_task/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/context_switch/os_sched_get_current_task/index.html b/latest/os/core_os/context_switch/os_sched_get_current_task/index.html
index 8746b65..31cc446 100644
--- a/latest/os/core_os/context_switch/os_sched_get_current_task/index.html
+++ b/latest/os/core_os/context_switch/os_sched_get_current_task/index.html
@@ -344,6 +344,14 @@
<li >
+ <a href="../os_sched_remove/">os_sched_remove</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_sched_resort/">os_sched_resort</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/context_switch/os_sched_insert/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/context_switch/os_sched_insert/index.html b/latest/os/core_os/context_switch/os_sched_insert/index.html
index 2643af2..a87e002 100644
--- a/latest/os/core_os/context_switch/os_sched_insert/index.html
+++ b/latest/os/core_os/context_switch/os_sched_insert/index.html
@@ -344,6 +344,14 @@
<li >
+ <a href="../os_sched_remove/">os_sched_remove</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_sched_resort/">os_sched_resort</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/context_switch/os_sched_next_task/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/context_switch/os_sched_next_task/index.html b/latest/os/core_os/context_switch/os_sched_next_task/index.html
index 5904d06..232bff0 100644
--- a/latest/os/core_os/context_switch/os_sched_next_task/index.html
+++ b/latest/os/core_os/context_switch/os_sched_next_task/index.html
@@ -344,6 +344,14 @@
<li >
+ <a href="../os_sched_remove/">os_sched_remove</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_sched_resort/">os_sched_resort</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/context_switch/os_sched_os_timer_exp/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/context_switch/os_sched_os_timer_exp/index.html b/latest/os/core_os/context_switch/os_sched_os_timer_exp/index.html
index afd1371..940b423 100644
--- a/latest/os/core_os/context_switch/os_sched_os_timer_exp/index.html
+++ b/latest/os/core_os/context_switch/os_sched_os_timer_exp/index.html
@@ -344,6 +344,14 @@
<li >
+ <a href="../os_sched_remove/">os_sched_remove</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_sched_resort/">os_sched_resort</a>
</li>
@@ -822,8 +830,8 @@
</li>
<li class="pull-right">
- <a href=../os_sched_resort/>
- Next: os_sched_resort
+ <a href=../os_sched_remove/>
+ Next: os_sched_remove
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/context_switch/os_sched_remove/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/context_switch/os_sched_remove/index.html b/latest/os/core_os/context_switch/os_sched_remove/index.html
new file mode 100644
index 0000000..6746063
--- /dev/null
+++ b/latest/os/core_os/context_switch/os_sched_remove/index.html
@@ -0,0 +1,895 @@
+<!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/core_os/context_switch/os_sched_remove/"> -->
+ <link rel="shortcut icon" href="../../../../img/favicon.ico">
+
+ <title>os_sched_remove - 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="os_sched_remove">
+
+
+ <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/">Tutorials</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../os_user_guide/">OS User Guide</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../../mynewt_os/">OS Core</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../os_started/
+">Functions</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../context_switch/">Scheduler</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li><a href="
+ ../os_sched/
+">Functions</a>
+
+
+ <ul>
+
+
+
+ <li >
+ <a href="../os_sched/">os_sched</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_arch_ctx_sw/">os_arch_ctx_sw</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_sched_ctx_sw_hook/">os_sched_ctx_sw_hook</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_sched_get_current_task/">os_sched_get_current_task</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_sched_insert/">os_sched_insert</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_sched_next_task/">os_sched_next_task</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_sched_os_timer_exp/">os_sched_os_timer_exp</a>
+ </li>
+
+
+
+
+
+ <li class="active">
+ <a href="./">os_sched_remove</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_sched_resort/">os_sched_resort</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_sched_set_current_task/">os_sched_set_current_task</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_sched_sleep/">os_sched_sleep</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_sched_wakeup/">os_sched_wakeup</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../time/os_time/">Time</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../task/task/">Tasks</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../event_queue/event_queue/">Event Queues</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../semaphore/semaphore/">Semaphores</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../mutex/mutex/">Mutexes</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../memory_pool/memory_pool/">Memory Pools</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../heap/heap/">Heap</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+
+
+ ../../mbuf/mbuf/
+
+">Memory Buffers</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../sanity/sanity/">Sanity</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../callout/callout/">Callouts</a>
+
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../porting/port_os/">Porting to your Platform</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/console/console/">Console</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/shell/shell/">Shell</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/split/split/">Split Images</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/bootloader/bootloader/">Bootloader</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+
+
+ ../../../modules/fs/fs/fs/
+
+">File System</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/hal/hal/">Hardware Abstraction Layer</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/drivers/driver/">Drivers</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/testutil/testutil/">Test Utilities</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/devmgmt/newtmgr/">Device Management with Newt Manager</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/imgmgr/imgmgr/">Image Manager</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../../modules/baselibc/">Baselibc library</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/json/json/">JSON</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/fcb/fcb/">Flash Circular Buffer</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/stats/stats/">Stats</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/logs/logs/">Logs</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/sysinitconfig/sysinitconfig/">System Configuration And Initialization</a>
+
+
+ </li>
+
+
+
+ </ul>
+
+ </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="../context_switch/">Scheduler</a></li>
+
+
+
+ <li>» <a href="../os_sched/">Functions</a></li>
+
+
+
+ <li>» os_sched_remove</li>
+
+
+
+ </ul>
+</div>
+ </div>
+
+ <h2 id="os_sched_remove"><font color="#F2853F" style="font-size:24pt"> os_sched_remove </font></h2>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #A90D91">int</span> <span style="color: #000000">os_sched_remove</span>(<span style="color: #A90D91">struct</span> <span style="color: #000000">os_task</span> <span style="color: #000000">*t</span>)
+</pre></div>
+
+
+<p>Stops and removes task <code>t</code>.</p>
+<p>The function removes the task from the <code>g_os_task_list</code> task list. It also removes the task from one of the following task list:</p>
+<ul>
+<li><code>g_os_run_list</code> if the task is in the Ready state.</li>
+<li><code>g_os_sleep_list</code> if the task is in the Sleep state.</li>
+</ul>
+<h4 id="arguments">Arguments</h4>
+<table>
+<thead>
+<tr>
+<th>Arguments</th>
+<th>Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td><code>t</code></td>
+<td>Pointer to the <code>os_task</code> structure for the task to be removed.</td>
+</tr>
+</tbody>
+</table>
+<h4 id="returned-values">Returned values</h4>
+<p>OS_OK - The task is removed successfully.</p>
+<h4 id="notes">Notes</h4>
+<p>This function must be called with all interrupts disabled.</p>
+<h4 id="example">Example</h4>
+<p>The <code>os_task_remove</code> function calls the <code>os_sched_remove</code> function to remove a task:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #A90D91">int</span>
+<span style="color: #000000">os_task_remove</span>(<span style="color: #A90D91">struct</span> <span style="color: #000000">os_task</span> <span style="color: #000000">*t</span>)
+{
+ <span style="color: #A90D91">int</span> <span style="color: #000000">rc</span>;
+ <span style="color: #A90D91">os_sr_t</span> <span style="color: #000000">sr</span>;
+
+ <span style="color: #177500">/* Add error checking code to ensure task can removed. */</span>
+
+
+ <span style="color: #177500">/* Call os_sched_remove to remove the task. */</span>
+ <span style="color: #000000">OS_ENTER_CRITICAL</span>(<span style="color: #000000">sr</span>);
+ <span style="color: #000000">rc</span> <span style="color: #000000">=</span> <span style="color: #000000">os_sched_remove</span>(<span style="color: #000000">t</span>);
+ <span style="color: #000000">OS_EXIT_CRITICAL</span>(<span style="color: #000000">sr</span>);
+ <span style="color: #A90D91">return</span> <span style="color: #000000">rc</span>;
+}
+</pre></div>
+
+ <div class="row">
+
+
+
+
+<ul class="nav nav-pills" style="margin-bottom: 10px">
+ <li>
+
+ <a href=../os_sched_os_timer_exp/>
+ <span class="fa fa-arrow-left"></span>
+ Previous: os_sched_os_timer_exp
+ </a>
+
+ </li>
+ <li class="pull-right">
+
+ <a href=../os_sched_resort/>
+ Next: os_sched_resort
+ <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/6b7450f6/latest/os/core_os/context_switch/os_sched_resort/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/context_switch/os_sched_resort/index.html b/latest/os/core_os/context_switch/os_sched_resort/index.html
index f48c116..0247a7e 100644
--- a/latest/os/core_os/context_switch/os_sched_resort/index.html
+++ b/latest/os/core_os/context_switch/os_sched_resort/index.html
@@ -343,6 +343,14 @@
+ <li >
+ <a href="../os_sched_remove/">os_sched_remove</a>
+ </li>
+
+
+
+
+
<li class="active">
<a href="./">os_sched_resort</a>
</li>
@@ -830,9 +838,9 @@
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../os_sched_os_timer_exp/>
+ <a href=../os_sched_remove/>
<span class="fa fa-arrow-left"></span>
- Previous: os_sched_os_timer_exp
+ Previous: os_sched_remove
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/context_switch/os_sched_set_current_task/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/context_switch/os_sched_set_current_task/index.html b/latest/os/core_os/context_switch/os_sched_set_current_task/index.html
index 95c51be..e146136 100644
--- a/latest/os/core_os/context_switch/os_sched_set_current_task/index.html
+++ b/latest/os/core_os/context_switch/os_sched_set_current_task/index.html
@@ -344,6 +344,14 @@
<li >
+ <a href="../os_sched_remove/">os_sched_remove</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_sched_resort/">os_sched_resort</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/context_switch/os_sched_sleep/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/context_switch/os_sched_sleep/index.html b/latest/os/core_os/context_switch/os_sched_sleep/index.html
index 194ca49..68257d5 100644
--- a/latest/os/core_os/context_switch/os_sched_sleep/index.html
+++ b/latest/os/core_os/context_switch/os_sched_sleep/index.html
@@ -344,6 +344,14 @@
<li >
+ <a href="../os_sched_remove/">os_sched_remove</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_sched_resort/">os_sched_resort</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/context_switch/os_sched_wakeup/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/context_switch/os_sched_wakeup/index.html b/latest/os/core_os/context_switch/os_sched_wakeup/index.html
index 3db9621..da28616 100644
--- a/latest/os/core_os/context_switch/os_sched_wakeup/index.html
+++ b/latest/os/core_os/context_switch/os_sched_wakeup/index.html
@@ -344,6 +344,14 @@
<li >
+ <a href="../os_sched_remove/">os_sched_remove</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_sched_resort/">os_sched_resort</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/event_queue/event_queue/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/event_queue/event_queue/index.html b/latest/os/core_os/event_queue/event_queue/index.html
index 91aa44b..95739f3 100644
--- a/latest/os/core_os/event_queue/event_queue/index.html
+++ b/latest/os/core_os/event_queue/event_queue/index.html
@@ -839,9 +839,9 @@ The <code>os_eventq</code> structure defines an event queue and has the followin
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../../task/os_task_init/>
+ <a href=../../task/os_task_remove/>
<span class="fa fa-arrow-left"></span>
- Previous: os_task_init
+ Previous: os_task_remove
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/memory_pool/OS_MEMPOOL_BYTES/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/memory_pool/OS_MEMPOOL_BYTES/index.html b/latest/os/core_os/memory_pool/OS_MEMPOOL_BYTES/index.html
index f888c8e..017e5ba 100644
--- a/latest/os/core_os/memory_pool/OS_MEMPOOL_BYTES/index.html
+++ b/latest/os/core_os/memory_pool/OS_MEMPOOL_BYTES/index.html
@@ -362,6 +362,14 @@
<li >
+ <a href="../os_mempool_info_get_next/">os_mempool_info_get_next</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_mempool_init/">os_mempool_init</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/memory_pool/OS_MEMPOOL_SIZE/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/memory_pool/OS_MEMPOOL_SIZE/index.html b/latest/os/core_os/memory_pool/OS_MEMPOOL_SIZE/index.html
index 03ccf46..1d47c32 100644
--- a/latest/os/core_os/memory_pool/OS_MEMPOOL_SIZE/index.html
+++ b/latest/os/core_os/memory_pool/OS_MEMPOOL_SIZE/index.html
@@ -362,6 +362,14 @@
<li >
+ <a href="../os_mempool_info_get_next/">os_mempool_info_get_next</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_mempool_init/">os_mempool_init</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/memory_pool/memory_pool/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/memory_pool/memory_pool/index.html b/latest/os/core_os/memory_pool/memory_pool/index.html
index 218d5ca..48ea96d 100644
--- a/latest/os/core_os/memory_pool/memory_pool/index.html
+++ b/latest/os/core_os/memory_pool/memory_pool/index.html
@@ -723,11 +723,20 @@ Once the memory pool has been initialized the developer can allocate memory bloc
<span style="color: #A90D91">int</span> <span style="color: #000000">mp_block_size</span>;
<span style="color: #A90D91">int</span> <span style="color: #000000">mp_num_blocks</span>;
<span style="color: #A90D91">int</span> <span style="color: #000000">mp_num_free</span>;
+ <span style="color: #A90D91">int</span> <span style="color: #000000">mp_min_free</span>;
<span style="color: #A90D91">uint32_t</span> <span style="color: #000000">mp_membuf_addr</span>;
<span style="color: #000000">STAILQ_ENTRY</span>(<span style="color: #000000">os_mempool</span>) <span style="color: #000000">mp_list</span>;
<span style="color: #000000">SLIST_HEAD</span>(,<span style="color: #000000">os_memblock</span>);
<span style="color: #A90D91">char</span> <span style="color: #000000">*name</span>;
};
+
+<span style="color: #A90D91">struct</span> <span style="color: #000000">os_mempool_info</span> {
+ <span style="color: #A90D91">int</span> <span style="color: #000000">omi_block_size</span>;
+ <span style="color: #A90D91">int</span> <span style="color: #000000">omi_num_blocks</span>;
+ <span style="color: #A90D91">int</span> <span style="color: #000000">omi_num_free</span>;
+ <span style="color: #A90D91">int</span> <span style="color: #000000">omi_min_free</span>;
+ <span style="color: #A90D91">char</span> <span style="color: #000000">omi_name</span>[<span style="color: #000000">OS_MEMPOOL_INFO_NAME_LEN</span>];
+};
</pre></div>
@@ -753,6 +762,10 @@ Once the memory pool has been initialized the developer can allocate memory bloc
<td>Number of free blocks left</td>
</tr>
<tr>
+<td>mp_min_free</td>
+<td>Lowest number of free blocks seen</td>
+</tr>
+<tr>
<td>mp_membuf_addr</td>
<td>The address of the memory block. This is used to check that a valid memory block is being freed.</td>
</tr>
@@ -793,6 +806,10 @@ Once the memory pool has been initialized the developer can allocate memory bloc
<td>Releases previously allocated element back to the pool.</td>
</tr>
<tr>
+<td><a href="../os_mempool_info_get_next">os_mempool_info_get_next</a></td>
+<td>Retrieves memory pool information for the next memory pool.</td>
+</tr>
+<tr>
<td><a href="../OS_MEMPOOL_BYTES">OS_MEMPOOL_BYTES</a></td>
<td>Calculates how many bytes of memory is used by n number of elements, when individual element size is blksize bytes.</td>
</tr>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/memory_pool/os_memblock_get/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/memory_pool/os_memblock_get/index.html b/latest/os/core_os/memory_pool/os_memblock_get/index.html
index 14e8be4..9024615 100644
--- a/latest/os/core_os/memory_pool/os_memblock_get/index.html
+++ b/latest/os/core_os/memory_pool/os_memblock_get/index.html
@@ -362,6 +362,14 @@
<li >
+ <a href="../os_mempool_info_get_next/">os_mempool_info_get_next</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_mempool_init/">os_mempool_init</a>
</li>
@@ -785,8 +793,8 @@
</li>
<li class="pull-right">
- <a href=../os_mempool_init/>
- Next: os_mempool_init
+ <a href=../os_mempool_info_get_next/>
+ Next: os_mempool_info_get_next
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/memory_pool/os_memblock_put/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/memory_pool/os_memblock_put/index.html b/latest/os/core_os/memory_pool/os_memblock_put/index.html
index 2f0c348..c690a2f 100644
--- a/latest/os/core_os/memory_pool/os_memblock_put/index.html
+++ b/latest/os/core_os/memory_pool/os_memblock_put/index.html
@@ -362,6 +362,14 @@
<li >
+ <a href="../os_mempool_info_get_next/">os_mempool_info_get_next</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_mempool_init/">os_mempool_init</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/memory_pool/os_mempool_info_get_next/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/memory_pool/os_mempool_info_get_next/index.html b/latest/os/core_os/memory_pool/os_mempool_info_get_next/index.html
new file mode 100644
index 0000000..6ad5342
--- /dev/null
+++ b/latest/os/core_os/memory_pool/os_mempool_info_get_next/index.html
@@ -0,0 +1,879 @@
+<!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/core_os/memory_pool/os_mempool_info_get_next/"> -->
+ <link rel="shortcut icon" href="../../../../img/favicon.ico">
+
+ <title>os_mempool_info_get_next - 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="os_mempool_info_get_next">
+
+
+ <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/">Tutorials</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../os_user_guide/">OS User Guide</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../../mynewt_os/">OS Core</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../os_started/
+">Functions</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../context_switch/context_switch/">Scheduler</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../time/os_time/">Time</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../task/task/">Tasks</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../event_queue/event_queue/">Event Queues</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../semaphore/semaphore/">Semaphores</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../mutex/mutex/">Mutexes</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../memory_pool/">Memory Pools</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li><a href="
+ ../os_memblock_get/
+">Functions/Macros</a>
+
+
+ <ul>
+
+
+
+ <li >
+ <a href="../os_memblock_get/">os_memblock_get</a>
+ </li>
+
+
+
+
+
+ <li class="active">
+ <a href="./">os_mempool_info_get_next</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_mempool_init/">os_mempool_init</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_memblock_put/">os_memblock_put</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../OS_MEMPOOL_BYTES/">OS_MEMPOOL_BYTES</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../OS_MEMPOOL_SIZE/">OS_MEMPOOL_SIZE</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../heap/heap/">Heap</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+
+
+ ../../mbuf/mbuf/
+
+">Memory Buffers</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../sanity/sanity/">Sanity</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../callout/callout/">Callouts</a>
+
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../porting/port_os/">Porting to your Platform</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/console/console/">Console</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/shell/shell/">Shell</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/split/split/">Split Images</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/bootloader/bootloader/">Bootloader</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+
+
+ ../../../modules/fs/fs/fs/
+
+">File System</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/hal/hal/">Hardware Abstraction Layer</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/drivers/driver/">Drivers</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/testutil/testutil/">Test Utilities</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/devmgmt/newtmgr/">Device Management with Newt Manager</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/imgmgr/imgmgr/">Image Manager</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../../modules/baselibc/">Baselibc library</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/json/json/">JSON</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/fcb/fcb/">Flash Circular Buffer</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/stats/stats/">Stats</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/logs/logs/">Logs</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/sysinitconfig/sysinitconfig/">System Configuration And Initialization</a>
+
+
+ </li>
+
+
+
+ </ul>
+
+ </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="../memory_pool/">Memory Pools</a></li>
+
+
+
+ <li>» <a href="../os_memblock_get/">Functions/Macros</a></li>
+
+
+
+ <li>» os_mempool_info_get_next</li>
+
+
+
+ </ul>
+</div>
+ </div>
+
+ <h2 id="os_mempool_info_get_next"><font color="F2853F" style="font-size:24pt"> os_mempool_info_get_next</font></h2>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #A90D91">struct</span> <span style="color: #000000">os_mempool</span> <span style="color: #000000">*</span> <span style="color: #000000">os_mempool_info_get_next</span>(<span style="color: #A90D91">struct</span> <span style="color: #000000">os_mempool</span> <span style="color: #000000">*mp</span>, <span style="color: #A90D91">struct</span> <span style="color: #000000">os_mempool_info</span> <span style="color: #000000">*omi</span>)
+</pre></div>
+
+
+<p>Populates the os_mempool_info structure pointed to by <code>omi</code> with memory pool information.
+The value of <code>mp</code> specifies the memory pool information to populate. If <code>mp</code> is <strong>NULL</strong>, it populates the information for the first memory pool on the memory pool list. If <code>mp</code> is not NULL, it populates the information for the next memory pool after <code>mp</code>. </p>
+<p><br></p>
+<h4 id="arguments">Arguments</h4>
+<table>
+<thead>
+<tr>
+<th>Arguments</th>
+<th>Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td><code>mp</code></td>
+<td>Pointer to the memory pool in the memory pool list from the previous <code>os_mempool_info_get_next</code> function call. The next memory pool after <code>mp</code> is populated. If <code>mp</code> is NULL, the first memory pool on the memory pool list is populated.</td>
+</tr>
+<tr>
+<td><code>omi</code></td>
+<td>Pointer to <code>os_mempool_info</code> structure where memory information will be stored.</td>
+</tr>
+</tbody>
+</table>
+<p><br></p>
+<h4 id="returned-values">Returned values</h4>
+<ul>
+<li>
+<p>A pointer to the memory pool structure that was used to populate the memory pool information structure. </p>
+</li>
+<li>
+<p>NULL indicates <code>mp</code> is the last memory pool on the list and <code>omi</code> is not populated with memory pool information.</p>
+</li>
+</ul>
+<p><br></p>
+<h4 id="example">Example</h4>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #000000">shell_os_mpool_display_cmd</span>(<span style="color: #A90D91">int</span> <span style="color: #000000">argc</span>, <span style="color: #A90D91">char</span> <span style="color: #000000">**argv</span>)
+{
+ <span style="color: #A90D91">struct</span> <span style="color: #000000">os_mempool</span> <span style="color: #000000">*mp</span>;
+ <span style="color: #A90D91">struct</span> <span style="color: #000000">os_mempool_info</span> <span style="color: #000000">omi</span>;
+ <span style="color: #A90D91">char</span> <span style="color: #000000">*name</span>;
+
+ <span style="color: #000000">name</span> <span style="color: #000000">=</span> <span style="color: #A90D91">NULL</span>;
+ <span style="color: #000000">found</span> <span style="color: #000000">=</span> <span style="color: #1C01CE">0</span>;
+
+ <span style="color: #A90D91">if</span> (<span style="color: #000000">argc</span> <span style="color: #000000">></span> <span style="color: #1C01CE">1</span> <span style="color: #000000">&&</span> <span style="color: #000000">strcmp</span>(<span style="color: #000000">argv</span>[<span style="color: #1C01CE">1</span>], <span style="color: #C41A16">""</span>)) {
+ <span style="color: #000000">name</span> <span style="color: #000000">=</span> <span style="color: #000000">argv</span>[<span style="color: #1C01CE">1</span>];
+ }
+ <span style="color: #000000">console_printf</span>(<span style="color: #C41A16">"Mempools: \n"</span>);
+ <span style="color: #000000">mp</span> <span style="color: #000000">=</span> <span style="color: #A90D91">NULL</span>;
+ <span style="color: #000000">console_printf</span>(<span style="color: #C41A16">"%32s %5s %4s %4s %4s\n"</span>, <span style="color: #C41A16">"name"</span>, <span style="color: #C41A16">"blksz"</span>, <span style="color: #C41A16">"cnt"</span>, <span style="color: #C41A16">"free"</span>,
+ <span style="color: #C41A16">"min"</span>);
+ <span style="color: #A90D91">while</span> (<span style="color: #1C01CE">1</span>) {
+ <span style="color: #000000">mp</span> <span style="color: #000000">=</span> <span style="color: #000000">o</span>{<span style="color: #000000">_mempool_info_get_next</span>(<span style="color: #000000">mp</span>, <span style="color: #000000">&omi</span>);
+ <span style="color: #A90D91">if</span> (<span style="color: #000000">mp</span> <span style="color: #000000">==</span> <span style="color: #A90D91">NULL</span>) {
+ <span style="color: #A90D91">break</span>;
+ }
+ <span style="color: #A90D91">if</span> (<span style="color: #000000">name</span>) {
+ <span style="color: #A90D91">if</span> (<span style="color: #000000">strcmp</span>(<span style="color: #000000">name</span>, <span style="color: #000000">omi</span>.<span style="color: #000000">omi_name</span>)) {
+ <span style="color: #A90D91">continue</span>;
+ } <span style="color: #A90D91">else</span> {
+ <span style="color: #000000">found</span> <span style="color: #000000">=</span> <span style="color: #1C01CE">1</span>;
+ }
+ }
+
+ <span style="color: #000000">console_printf</span>(<span style="color: #C41A16">"%32s %5d %4d %4d %4d\n"</span>, <span style="color: #000000">omi</span>.<span style="color: #000000">omi_name</span>,
+ <span style="color: #000000">omi</span>.<span style="color: #000000">omi_block_size</span>, <span style="color: #000000">omi</span>.<span style="color: #000000">omi_num_blocks</span>,
+ <span style="color: #000000">omi</span>.<span style="color: #000000">omi_num_free</span>, <span style="color: #000000">omi</span>.<span style="color: #000000">omi_min_free</span>);
+ }
+
+ <span style="color: #A90D91">if</span> (<span style="color: #000000">name</span> <span style="color: #000000">&&</span> <span style="color: #000000">!found</span>) {
+ <span style="color: #000000">console_printf</span>(<span style="color: #C41A16">"Couldn't find a memory pool with name %s\n"</span>,
+ <span style="color: #000000">name</span>);
+ }
+ <span style="color: #A90D91">return</span> (<span style="color: #1C01CE">0</span>);
+}
+</pre></div>
+
+ <div class="row">
+
+
+
+
+<ul class="nav nav-pills" style="margin-bottom: 10px">
+ <li>
+
+ <a href=../os_memblock_get/>
+ <span class="fa fa-arrow-left"></span>
+ Previous: os_memblock_get
+ </a>
+
+ </li>
+ <li class="pull-right">
+
+ <a href=../os_mempool_init/>
+ Next: os_mempool_init
+ <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/6b7450f6/latest/os/core_os/memory_pool/os_mempool_init/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/memory_pool/os_mempool_init/index.html b/latest/os/core_os/memory_pool/os_mempool_init/index.html
index 3291e97..007bb10 100644
--- a/latest/os/core_os/memory_pool/os_mempool_init/index.html
+++ b/latest/os/core_os/memory_pool/os_mempool_init/index.html
@@ -361,6 +361,14 @@
+ <li >
+ <a href="../os_mempool_info_get_next/">os_mempool_info_get_next</a>
+ </li>
+
+
+
+
+
<li class="active">
<a href="./">os_mempool_init</a>
</li>
@@ -802,9 +810,9 @@
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../os_memblock_get/>
+ <a href=../os_mempool_info_get_next/>
<span class="fa fa-arrow-left"></span>
- Previous: os_memblock_get
+ Previous: os_mempool_info_get_next
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/task/os_task_count/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/task/os_task_count/index.html b/latest/os/core_os/task/os_task_count/index.html
index 29af7d9..f8ce60d 100644
--- a/latest/os/core_os/task/os_task_count/index.html
+++ b/latest/os/core_os/task/os_task_count/index.html
@@ -331,6 +331,14 @@
+
+
+ <li >
+ <a href="../os_task_remove/">os_task_remove</a>
+ </li>
+
+
+
</ul>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/task/os_task_info_get_next/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/task/os_task_info_get_next/index.html b/latest/os/core_os/task/os_task_info_get_next/index.html
index d3a9faa..5b68a22 100644
--- a/latest/os/core_os/task/os_task_info_get_next/index.html
+++ b/latest/os/core_os/task/os_task_info_get_next/index.html
@@ -331,6 +331,14 @@
+
+
+ <li >
+ <a href="../os_task_remove/">os_task_remove</a>
+ </li>
+
+
+
</ul>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/task/os_task_init/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/task/os_task_init/index.html b/latest/os/core_os/task/os_task_init/index.html
index 6d5d872..882747c 100644
--- a/latest/os/core_os/task/os_task_init/index.html
+++ b/latest/os/core_os/task/os_task_init/index.html
@@ -331,6 +331,14 @@
+
+
+ <li >
+ <a href="../os_task_remove/">os_task_remove</a>
+ </li>
+
+
+
</ul>
</li>
@@ -803,8 +811,8 @@ tasks.</p>
</li>
<li class="pull-right">
- <a href=../../event_queue/event_queue/>
- Next: Event Queues
+ <a href=../os_task_remove/>
+ Next: os_task_remove
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/os/core_os/task/os_task_remove/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/task/os_task_remove/index.html b/latest/os/core_os/task/os_task_remove/index.html
new file mode 100644
index 0000000..16a9ae1
--- /dev/null
+++ b/latest/os/core_os/task/os_task_remove/index.html
@@ -0,0 +1,831 @@
+<!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/core_os/task/os_task_remove/"> -->
+ <link rel="shortcut icon" href="../../../../img/favicon.ico">
+
+ <title>os_task_remove - 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="os_task_remove">
+
+
+ <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/">Tutorials</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../os_user_guide/">OS User Guide</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../../mynewt_os/">OS Core</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../os_started/
+">Functions</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../context_switch/context_switch/">Scheduler</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../time/os_time/">Time</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../task/">Tasks</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li><a href="
+ ../os_task_count/
+">Functions</a>
+
+
+ <ul>
+
+
+
+ <li >
+ <a href="../os_task_count/">os_task_count</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_task_info_get_next/">os_task_info_get_next</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_task_init/">os_task_init</a>
+ </li>
+
+
+
+
+
+ <li class="active">
+ <a href="./">os_task_remove</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../event_queue/event_queue/">Event Queues</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../semaphore/semaphore/">Semaphores</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../mutex/mutex/">Mutexes</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../memory_pool/memory_pool/">Memory Pools</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../heap/heap/">Heap</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+
+
+ ../../mbuf/mbuf/
+
+">Memory Buffers</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../sanity/sanity/">Sanity</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../callout/callout/">Callouts</a>
+
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../porting/port_os/">Porting to your Platform</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/console/console/">Console</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/shell/shell/">Shell</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/split/split/">Split Images</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/bootloader/bootloader/">Bootloader</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+
+
+ ../../../modules/fs/fs/fs/
+
+">File System</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/hal/hal/">Hardware Abstraction Layer</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/drivers/driver/">Drivers</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/testutil/testutil/">Test Utilities</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/devmgmt/newtmgr/">Device Management with Newt Manager</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/imgmgr/imgmgr/">Image Manager</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../../modules/baselibc/">Baselibc library</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/json/json/">JSON</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/fcb/fcb/">Flash Circular Buffer</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/stats/stats/">Stats</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/logs/logs/">Logs</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/sysinitconfig/sysinitconfig/">System Configuration And Initialization</a>
+
+
+ </li>
+
+
+
+ </ul>
+
+ </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="../task/">Tasks</a></li>
+
+
+
+ <li>» <a href="../os_task_count/">Functions</a></li>
+
+
+
+ <li>» os_task_remove</li>
+
+
+
+ </ul>
+</div>
+ </div>
+
+ <h2 id="os_task_remove"><font color="F2853F" style="font-size:24pt"> os_task_remove</font></h2>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #A90D91">int</span> <span style="color: #000000">os_task_remove</span>(<span style="color: #A90D91">struct</span> <span style="color: #000000">os_task</span> <span style="color: #000000">*t</span>)
+</pre></div>
+
+
+<p>Removes a task, <code>t</code>, from the task list. A task cannot be removed when it is in one of the following states:</p>
+<ul>
+<li>It is running - a task cannot remove itself.</li>
+<li>It has not been initialized.</li>
+<li>It is holding a lock on a semphore or mutex.</li>
+<li>It is suspended waiting on a lock (semaphore or mutex) or for an event on an event queue.</li>
+</ul>
+<p><br></p>
+<h4 id="arguments">Arguments</h4>
+<table>
+<thead>
+<tr>
+<th>Arguments</th>
+<th>Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td><code>t</code></td>
+<td>Pointer to the <code>os_task</code> structure for the task to be removed</td>
+</tr>
+</tbody>
+</table>
+<p><br></p>
+<h4 id="returned-values">Returned values</h4>
+<p><code>OS_OK</code>: Task <code>t</code> is removed sucessfully.
+<br><code>OS_INVALID_PARM</code>: Task <code>t</code> is the calling task. A task cannot remove itself.
+<br><code>OS_NOT_STARTED</code>: Task <code>t</code> is not initialized.
+<br><code>OS_EBUSY</code>: Task <code>t</code> is either holding a lock or suspended waiting on lock on event.
+<br></p>
+<h4 id="example">Example</h4>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #A90D91">struct</span> <span style="color: #000000">os_task</span> <span style="color: #000000">worker_task</span>;
+
+<span style="color: #A90D91">int</span>
+<span style="color: #000000">remove_my_worker_task</span>(<span style="color: #A90D91">void</span>)
+{
+ <span style="color: #177500">/* Add error checking code to ensure task can removed. */</span>
+
+ <span style="color: #177500">/* Call os_task_remove to remove the worker task */</span>
+ <span style="color: #000000">rc</span> <span style="color: #000000">=</span> <span style="color: #000000">os_task_remove</span>(<span style="color: #000000">&worker_task</span>);
+ <span style="color: #A90D91">return</span> <span style="color: #000000">rc</span>;
+}
+</pre></div>
+
+ <div class="row">
+
+
+
+
+<ul class="nav nav-pills" style="margin-bottom: 10px">
+ <li>
+
+ <a href=../os_task_init/>
+ <span class="fa fa-arrow-left"></span>
+ Previous: os_task_init
+ </a>
+
+ </li>
+ <li class="pull-right">
+
+ <a href=../../event_queue/event_queue/>
+ Next: Event Queues
+ <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/6b7450f6/latest/os/core_os/task/task/index.html
----------------------------------------------------------------------
diff --git a/latest/os/core_os/task/task/index.html b/latest/os/core_os/task/task/index.html
index 6ab76a6..5fd2c6f 100644
--- a/latest/os/core_os/task/task/index.html
+++ b/latest/os/core_os/task/task/index.html
@@ -1016,6 +1016,10 @@ task simply toggles an LED at a one second interval.</p>
<td><a href="../os_task_info_get_next/">os_task_info_get_next</a></td>
<td>Populates the os task info structure given with task information.</td>
</tr>
+<tr>
+<td><a href="../os_task_remove/">os_task_remove</a></td>
+<td>Removes a task from the task list.</td>
+</tr>
</tbody>
</table>
[6/7] incubator-mynewt-site git commit: Added functions in task,
mempool, context switch
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/mkdocs/search_index.json
----------------------------------------------------------------------
diff --git a/develop/mkdocs/search_index.json b/develop/mkdocs/search_index.json
index 957c469..665dde5 100644
--- a/develop/mkdocs/search_index.json
+++ b/develop/mkdocs/search_index.json
@@ -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: 0-latest\n user: apache\n repo: incubator-mynewt-core\n\n\n\n\n\nChanging to 0-dev will put you on the develop branch. \nThe Develop Branch may not be stable and \nyou 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
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.\n\n\n$ tree -L 2 repos/apache-mynewt-core/\nrepos/apache-mynewt-core/\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 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 ffs2native\n\u2502\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 \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 \u2514\u2500\u2500 split\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 \u2514\u2500\u2500 sim\n\u251c\u2500\u2500 crypto\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mbedtls\n\u2502\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\u00a
0 \u251c\u2500\u2500 json\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 tinycbor\n\u251c\u2500\u2500 fs\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\u2500\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\u2500\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 \u251c\u2500\u2500
testreport\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\n87 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\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\nsnip\n\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 a
djusted 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\n...lots of compiling and testing...\n...about 2 minutes later ...\nCompiling mn_sock_test.c\nArchiving mn_socket.a\nLinking test_mn_socket\nExecuting test: /Users/dsimmons/myproj/bin/unittest/sys/mn_socket/test_mn_socket\nPassed 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]\nAll tests passe
d\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 main.c\nArchiving blinky.a\nCompiling hal_bsp.c\nCompiling os_bsp.c\nCompiling sbrk.c\nArchiving native.a\nCompiling flash_map.c\n\nsnip\n\nLinking blinky.elf\nApp successfully built: ~/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\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 \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!",
"title": "Create Your First Project"
},
{
@@ -372,22 +372,22 @@
},
{
"location": "/os/get_started/project_create/#newt-new",
- "text": "Choose a project name. For this tutorial we will call this project myproj .\nEnter the newt new myproj command. $ newt new myproj\nDownloading project skeleton from apache/incubator-mynewt-blinky...\nInstalling skeleton in myproj...\nProject myproj successfully created. Newt populates this new project with a base skeleton of a new Apache Mynewt \nproject. It has the following structure. Note : If you do not have tree , install it by running brew install tree . $ 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 The Newt tool has installed the base files for a project comprising the following: The file project.yml 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. The file apps/blinky/pkg.yml contains the description of your application\nand its package dependencies. A target directory containing my_blinky_sim , a target descriptor used to\nbuild a version of myproj. Use newt target show to see available build \ntargets. A non-buildable target called unittest . This is used internally by newt and is not a formal build target. NOTE: The actual code and pack
age files are not installed \n(except the template for main.c ). See the next step for installing the packages. NOTE: 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. repository.apache-mynewt-core:\n type: github\n vers: 0-latest\n user: apache\n repo: incubator-mynewt-core Changing to 0-dev will put you on the develop branch. The Develop Branch may not be stable and \nyou may encounter bugs or other problems.",
+ "text": "Choose a project name. For this tutorial we will call this project myproj .\nEnter the newt new myproj command. $ newt new myproj\nDownloading project skeleton from apache/incubator-mynewt-blinky...\nInstalling skeleton in myproj...\nProject myproj successfully created. Newt populates this new project with a base skeleton of a new Apache Mynewt \nproject. It has the following structure. Note : If you do not have tree , install it by running brew install tree . $ 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 The Newt tool has installed the base files for a project comprising the following: The file project.yml 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. The file apps/blinky/pkg.yml contains the description of your application\nand its package dependencies. A target directory containing my_blinky_sim , a target descriptor used to\nbuild a version of myproj. Use newt target show to see available build \ntargets. A non-buildable target called unittest . This is used internally by newt and is not a formal build target. NOTE: The actual code and pack
age files are not installed \n(except the template for main.c ). See the next step for installing the packages. NOTE: 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. repository.apache-mynewt-core:\n type: github\n vers: 1-latest\n user: apache\n repo: incubator-mynewt-core Changing to 1-dev will put you on the develop branch. The Develop Branch may not be stable and you may encounter bugs or other problems.",
"title": "Newt New"
},
{
"location": "/os/get_started/project_create/#newt-install",
- "text": "Once 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 newt install command will\nfetch this repository. $ newt install\napache-mynewt-core NOTE: apache-mynewt-core may take a while to download. To see progress,\nuse the -v (verbose) option to install. Once newt install has successfully finished, the contents of apache-mynewt-core 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. $ tree -L 2 repos/apache-mynewt-core/\nrepos/apache-mynewt-core/\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\u2
500\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 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 ffs2native\n\u2502\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 \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 \u2514\u2500\u
2500 split\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 \u2514\u2500\u2500 sim\n\u251c\u2500\u2500 crypto\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mbedtls\n\u2502\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 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 \u25
1c\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\u2500\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\u2500\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 \u251c\u2500\u2500 testreport\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\n87 directories, 9 files As you can see, the core of the Apache Mynewt operating system has been brought \ninto your local directory.",
+ "text": "Once 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 newt install command will\nfetch this repository. $ newt install\napache-mynewt-core NOTE: apache-mynewt-core may take a while to download. To see progress,\nuse the -v (verbose) option to install. Once newt install has successfully finished, the contents of apache-mynewt-core 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. $ 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\u25
1c\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\u2502\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\u00
a0\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\u2502\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\u
00a0\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\u2500\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\u250
0\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\u2500\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 As you can see, the core of the Apache Mynewt operating system has been brought \ninto your local directory.",
"title": "Newt Install"
},
{
"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 snip 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 configuration 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 uni
nstall 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\n...lots of compiling and testing...\n...about 2 minutes later ...\nCompiling mn_sock_test.c\nArchiving mn_socket.a\nLinking test_mn_socket\nExecuting test: /Users/dsimmons/myproj/bin/unittest/sys/mn_socket/test_mn_socket\nPassed 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]\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 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",
"title": "Test the project's packages"
},
{
"location": "/os/get_started/project_create/#build-the-project",
- "text": "To build and run your new application, simply issue the following command: $ newt build my_blinky_sim \nBuilding target targets/my_blinky_sim\nCompiling main.c\nArchiving blinky.a\nCompiling hal_bsp.c\nCompiling os_bsp.c\nCompiling sbrk.c\nArchiving native.a\nCompiling flash_map.c snip \nLinking blinky.elf\nApp successfully built: ~/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf",
+ "text": "To build and run your new application, simply issue the following command: $ 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",
"title": "Build the Project"
},
{
@@ -402,7 +402,7 @@
},
{
"location": "/os/get_started/serial_access/",
- "text": "Using the Serial Port with Mynewt OS\n\n\nSome of the projects and tutorials here will allow you to use a serial port\nto interact with your Mynewt project. While most modern PCs and laptops\nno longer have a true serial port, almost all can use their USB ports\nas serial ports. \n\n\nThis will show you how to connect to some of the development boards\nwe use via a serial port. \n\n\nThe development boards covered here are:\n\n\n\n\nNordic Semiconductor NRF52dk\n\n\nArduino M0 Pro\n\n\n\n\nIn order to communicate with these boards you will also need a USB\n--\nSerial\nconverted. We'll be using the \nAdaFruit FT232H Breakout Board\n for\nthis, but almost any similar board should work just as well. You will also\nneed Minicom or a similar Serial communications application. We'll show you how\nto use the \nscreen\n command built in to Mac OS X, but later tutorials will\nalso show Minicom setup.\n\n\nSo let's get started!\n\n\n\n\nSetup FT232H\n\n\nThis is a great b
oard because it's so easy to set up, and it can do Serial UART,\nSPI, I2C and GPIO as well. There's full documentation on the board \nhere\n\n but we're only covering the wiring for the Serial UART. \n\n\nStart by connecting a jumper wire to Pin D0. This will be the UART Tx pin, \nwhich we'll then connect to the Rx pin on the Development Board.\n\n\nNext connect a jumper wire to pin D1. This will be the UART Rx pin,\nwhich we'll connect to the Tx pin on the development board.\n\n\nFinally connect a jumper wire to the GND pin.\n\n\nIt should look like this:\n\n\n\n\n\n\nSetup Nordic Semiconductor NRF52DK\n\n\nOn the NRF52DK developer kit board, the Rx pin is P0.08, so you'll attach your\njumper wire from the Tx pin (D0) of the FT232H board here.\n\n\nThe TX Pin is pin P0.08, so you'll attache the jumper wire from the Rx Pin (D1)\non the FT232H board here. \n\n\nFinally, the GND wire should go to the GND Pin on the NRF52DK. When you're\ndone, your wiring should look like this:\n\n\n \
n\n\n\n\nSetup Arduino M0 Pro\n\n\nOn the Arduino M0 Pro, the Tx and Rx pins are clearly labeled as such, as is the GND\npin. Just make sure you wire Rx from the FT232H to TX on the M0 Pro, and vice-versa.\n\n\nYour Arduino M0 Pro should look like this:\n\n\n\n\n\n\nSetup Serial Communications\n\n\nAs mentioned earlier, we'll be using the built in \nscreen\n command for this, but we'll still \nneed to know which serial port to connect to. So, before plugging in the FT232H Board, \ncheck to see what USB devices are already connected:\n\n\n$ ls -la /dev/*usb*\n0 crw-rw-rw- 1 root wheel 20, 63 Nov 23 11:13 /dev/cu.usbmodem401322\n0 crw-rw-rw- 1 root wheel 20, 62 Nov 23 11:13 /dev/tty.usbmodem401322\n$\n\n\n\n\n\nNow, plug in the FT232H board, and run that command again:\n\n\n$ ls -la /dev/*usb*\n0 crw-rw-rw- 1 root wheel 20, 63 Nov 23 11:13 /dev/cu.usbmodem401322\n0 crw-rw-rw- 1 root wheel 20, 65 Nov 23 11:26 /dev/cu.usbserial-0020124\n0 crw-rw-rw- 1 root wheel
20, 62 Nov 23 11:13 /dev/tty.usbmodem401322\n0 crw-rw-rw- 1 root wheel 20, 64 Nov 23 11:26 /dev/tty.usbserial-0020124\n$\n\n\n\n\n\nSo the FT232H is connected to \n/dev/tty.usbserial-0020124\n (The number after tty.usbserial\nwill be different on your machine.)\n\n\nSo let's connect to it:\n\n\n$ screen /dev/tty.usbserial-0020124 115200\n\n\n\n\n\nTo exit out of \nscreen\n you'll type \ncontrol-A\n followed by \ncontrol-\\\n and you'll\nbe back to a terminal prompt.\n\n\nIf you'd like to use Minicom:\n\n\n$ minicom -D /dev/tty.usbserial-0020124\n\n\n\n\n\nWelcome to minicom 2.7\n\n\nOPTIONS: \nCompiled on Nov 24 2015, 16:14:21.\nPort /dev/tty.usbserial-0020124, 09:57:17\n\n\nPress Meta-Z for help on special keys\n```\n\n\n\n\nIf there's no Mynewt app running, or the Mynewt app doesn't have the Shell and Console\nenabled, you won't see anything there, but you can always refer back to this page\nfrom later tutorials if you need to.\n\n\nNow that you know how to communicate with
your mynewt application, let's move on to\ncreating one!",
+ "text": "Using the Serial Port with Mynewt OS\n\n\nSome of the projects and tutorials here will allow you to use a serial port\nto interact with your Mynewt project. While most modern PCs and laptops\nno longer have a true serial port, almost all can use their USB ports\nas serial ports. \n\n\nThis will show you how to connect to some of the development boards\nwe use via a serial port. \n\n\nThe development boards covered here are:\n\n\n\n\nNordic Semiconductor NRF52dk\n\n\nArduino M0 Pro\n\n\n\n\nIn order to communicate with these boards you will also need a USB\n--\nSerial\nconverted. We'll be using the \nAdaFruit FT232H Breakout Board\n for\nthis, but almost any similar board should work just as well. You will also\nneed Minicom or a similar Serial communications application. We'll show you how\nto use the \nscreen\n command built in to Mac OS X, but later tutorials will\nalso show Minicom setup.\n\n\nSo let's get started!\n\n\n\n\nSetup FT232H\n\n\nThis is a great b
oard because it's so easy to set up, and it can do Serial UART,\nSPI, I2C and GPIO as well. There's full documentation on the board \nhere\n\n but we're only covering the wiring for the Serial UART. \n\n\nStart by connecting a jumper wire to Pin D0. This will be the UART Tx pin, \nwhich we'll then connect to the Rx pin on the Development Board.\n\n\nNext connect a jumper wire to pin D1. This will be the UART Rx pin,\nwhich we'll connect to the Tx pin on the development board.\n\n\nFinally connect a jumper wire to the GND pin.\n\n\nIt should look like this:\n\n\n\n\n\n\nSetup Nordic Semiconductor NRF52DK\n\n\nOn the NRF52DK developer kit board, the Rx pin is P0.08, so you'll attach your\njumper wire from the Tx pin (D0) of the FT232H board here.\n\n\nThe TX Pin is pin P0.06, so you'll attache the jumper wire from the Rx Pin (D1)\non the FT232H board here. \n\n\nFinally, the GND wire should go to the GND Pin on the NRF52DK. When you're\ndone, your wiring should look like this:\n\n\n \
n\n\n\n\nSetup Arduino M0 Pro\n\n\nOn the Arduino M0 Pro, the Tx and Rx pins are clearly labeled as such, as is the GND\npin. Just make sure you wire Rx from the FT232H to TX on the M0 Pro, and vice-versa.\n\n\nYour Arduino M0 Pro should look like this:\n\n\n\n\n\n\nSetup Serial Communications\n\n\nAs mentioned earlier, we'll be using the built in \nscreen\n command for this, but we'll still \nneed to know which serial port to connect to. So, before plugging in the FT232H Board, \ncheck to see what USB devices are already connected:\n\n\n$ ls -la /dev/*usb*\n0 crw-rw-rw- 1 root wheel 20, 63 Nov 23 11:13 /dev/cu.usbmodem401322\n0 crw-rw-rw- 1 root wheel 20, 62 Nov 23 11:13 /dev/tty.usbmodem401322\n$\n\n\n\n\n\nNow, plug in the FT232H board, and run that command again:\n\n\n$ ls -la /dev/*usb*\n0 crw-rw-rw- 1 root wheel 20, 63 Nov 23 11:13 /dev/cu.usbmodem401322\n0 crw-rw-rw- 1 root wheel 20, 65 Nov 23 11:26 /dev/cu.usbserial-0020124\n0 crw-rw-rw- 1 root wheel
20, 62 Nov 23 11:13 /dev/tty.usbmodem401322\n0 crw-rw-rw- 1 root wheel 20, 64 Nov 23 11:26 /dev/tty.usbserial-0020124\n$\n\n\n\n\n\nSo the FT232H is connected to \n/dev/tty.usbserial-0020124\n (The number after tty.usbserial\nwill be different on your machine.)\n\n\nSo let's connect to it:\n\n\n$ screen /dev/tty.usbserial-0020124 115200\n\n\n\n\n\nTo exit out of \nscreen\n you'll type \ncontrol-A\n followed by \ncontrol-\\\n and you'll\nbe back to a terminal prompt.\n\n\nIf you'd like to use Minicom:\n\n\n$ minicom -D /dev/tty.usbserial-0020124\n\n\n\n\n\nWelcome to minicom 2.7\n\n\nOPTIONS: \nCompiled on Nov 24 2015, 16:14:21.\nPort /dev/tty.usbserial-0020124, 09:57:17\n\n\nPress Meta-Z for help on special keys\n```\n\n\n\n\nIf there's no Mynewt app running, or the Mynewt app doesn't have the Shell and Console\nenabled, you won't see anything there, but you can always refer back to this page\nfrom later tutorials if you need to.\n\n\nNow that you know how to communicate with
your mynewt application, let's move on to\ncreating one!",
"title": "Serial Port Setup"
},
{
@@ -417,7 +417,7 @@
},
{
"location": "/os/get_started/serial_access/#setup-nordic-semiconductor-nrf52dk",
- "text": "On the NRF52DK developer kit board, the Rx pin is P0.08, so you'll attach your\njumper wire from the Tx pin (D0) of the FT232H board here. The TX Pin is pin P0.08, so you'll attache the jumper wire from the Rx Pin (D1)\non the FT232H board here. Finally, the GND wire should go to the GND Pin on the NRF52DK. When you're\ndone, your wiring should look like this:",
+ "text": "On the NRF52DK developer kit board, the Rx pin is P0.08, so you'll attach your\njumper wire from the Tx pin (D0) of the FT232H board here. The TX Pin is pin P0.06, so you'll attache the jumper wire from the Rx Pin (D1)\non the FT232H board here. Finally, the GND wire should go to the GND Pin on the NRF52DK. When you're\ndone, your wiring should look like this:",
"title": "Setup Nordic Semiconductor NRF52DK"
},
{
@@ -482,7 +482,7 @@
},
{
"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 Micro-USB cable to connect the board and the computer.\n\n\nHave a computer to build a Mynewt application and connect to your board over U
SB.\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 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 successfully created.\n $ cd myproj\n $ n
ewt 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\nproject.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\n\nCreate a Target for the Bootloader\n\n\nYou need to create two targets, one for the bootloader and one
for the Blinky application.\n\n\n\nRun the following \nnewt target\n commands, from your project directory (ex. ~/dev/myproj), to create a bootloader target for the Arduino Zero Pro board. 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 a Arduino Zero Pro board, replace \nBSP_ARDUINO_ZERO_PRO\n with \nBSP_ARDUINO_ZERO\n in the last \nne
wt target set\n command.\n\n\nThese commands perform the following:\n\n\n\n\nCreate a target named \narduino_boot\n for the Arduino Zero Bootloader. \n\n\nSet the application for the \narduino_boot\n target to the default Apache Mynewt\n bootloader (\n@apache-mynewt-core/apps/boot\n)\n\n\nSet the board support package for the target to\n \n@mynewt_arduino_zero/hw/bsp/arduino_zero\n. This is a reference to the downloaded\n Arduino Zero support from Github.\n\n\nUse the \"optimized\" build profile for the \narduino_boot\n target. This\n instructs Newt to generate smaller and more efficient code for this target.\n This setting is necessary due to the bootloader's strict size constraints.\n\n\nSets the system configuration setting for Board Support Package to support the Arduino Zero Pro. \n\n\n\n\nSee the \nConcepts\n section for more information on setting options.\n\n\n\nCreate a Target for the Blinky Application\n\n\nRun the following \nnewt target\n commands to cr
eate your Blinky application target. We name the application target \narduino_blinky\n.\n\n\n$ newt target create arduino_blinky\nTarget targets/arduino_blinky successfully created\n$ newt target set arduino_blinky app=apps/blinky\nTarget targets/arduino_blinky successfully set target.app to apps/blinky\n$ newt target set arduino_blinky bsp=@mynewt_arduino_zero/hw/bsp/arduino_zero\nTarget targets/arduino_blinky successfully set target.bsp to @mynewt_arduino_zero/hw/bsp/arduino_zero\n$ newt target set arduino_blinky build_profile=debug\nTarget targets/arduino_blinky successfully set target.build_profile to debug\n$ newt target set arduino_blinky 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 a Arduino Zero Pro board, replace \nBSP_ARDUINO_ZERO_PRO\n with \nBSP_ARDUINO_ZERO\n in the last \nnewt target set\n command.\n\n\n\n\nBuild the Bootloader\n\n\nRun
the \nnewt build arduino_boot\n command to build a bootloader for your arduino board:\n\n\n$ newt build arduino_boot\nBuilding target targets/arduino_boot\nCompiling bin/targets/arduino_boot/generated/src/arduino_boot-sysinit-app.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c\nCompiling bin/targets/arduino_boot/generated/src/arduino_boot-sysflash.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c\nCompiling repos/apache-mynewt-core/apps/boot/src/boot.c\nCompiling repos/apache-mynewt-core/crypto/mbedtls/src/arc4.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/loader.c\nCompiling repos/apache-mynewt-core/crypto/mbedtls/src/aes.c\n\n ....\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bi
n/targets/arduino_boot/app/apps/boot/boot.elf\nTarget successfully built: targets/arduino_boot\n\n\n\n\n\n\n\nBuild the Blinky Application\n\n\nRun the \nnewt build arduino_blinky\n command to build your Blinky application image:\n\n\n$ newt build arduino_blinky\nBuilding target targets/arduino_blinky\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c\nCompiling apps/blinky/src/main.c\nCompiling repos/mynewt_arduino_zero/hw/mcu/atmel/samd21xx/src/sam0/drivers/i2s/i2s.c\nCompiling repos/mynewt_arduino_zero/hw/bsp/arduino_zero/src/hal_bsp.c\nCompiling repos/mynewt_arduino_zero/hw/mcu/atmel/samd21xx/src/sam0/drivers/i2s/i2s_callback.c\nCompiling repos/mynewt_arduino_zero/hw/mcu/atmel/samd21xx/src/sam0/drivers/nvm/nvm.c\n\n ...\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.elf\nTarget successfully built: targets/arduino_blinky\n\n\n\n\n\n\n\nConnect to the Board\n\n\nConnect your
computer to the Arduino Zero (from now on we'll call this the\ntarget) with a Micro-USB cable through the Programming Port as shown below.\nMynewt will load the image onto the board and debug the target through this port. You should see a\nlittle green LED come on. That means the board has power.\n\n\nNo external debugger is required. The Arduino Zero comes with an internal\ndebugger that can be accessed by Mynewt.\n\n\nThe images below show the Arduino Zero Programming Port.\n\n\n\n\n\n\n\n\nLoad the Bootloader onto the Board\n\n\nRun the \nnewt load arduino_boot\n command to load the bootloader onto your board:\n\n\n$ newt load arduino_boot\nLoading bootloader\n$\n\n\n\n\n\nThe bootloader is loaded onto your board succesfully when the \nnewt load\n command returns to the command prompt with no messages. You can proceed to load and run your Blinky application image (See \nRun the Blinky Application\n).\n\n\nIf the \nnewt load\n command outputs the following error messages, you wi
ll need to erase your board.\n\n\n$ newt load arduino_boot -v\nLoading bootloader\nError: Downloading ~/dev/arduino_zero/bin/targets/arduino_boot/app/apps/boot/boot.elf.bin to 0x0\nOpen On-Chip Debugger 0.9.0 (2015-11-15-05:39)\nLicensed under GNU GPL v2\nFor bug reports, read\n http://openocd.org/doc/doxygen/bugs.html\nInfo : only one transport option; autoselect \nswd\n\nadapter speed: 500 kHz\nadapter_nsrst_delay: 100\ncortex_m reset_config sysresetreq\nInfo : CMSIS-DAP: SWD Supported\nInfo : CMSIS-DAP: JTAG Supported\nInfo : CMSIS-DAP: Interface Initialised (SWD)\nInfo : CMSIS-DAP: FW Version = 01.1F.0118\nInfo : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 1 TDO = 1 nTRST = 0 nRESET = 1\nInfo : CMSIS-DAP: Interface ready\nInfo : clock speed 500 kHz\nInfo : SWD IDCODE 0x0bc11477\nInfo : at91samd21g18.cpu: hardware has 4 breakpoints, 2 watchpoints\nError: Target not halted\n\n\n\n\n\n\nTo erase your board, start a debug session and enter the highlighted commands at the \n(gdb)\n prompts
:\n\n\n$ newt debug arduino_blinky\n(gdb) mon at91samd chip-erase\nchip erased\nchip erased\n(gdb) x/32wx 0\n0x0: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x10: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x20: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x30: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x40: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x50: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x60: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x70: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n(gdb) q\n\n\n\n\n\n\nRun the \nnewt load arduino_boot\n command again after erasing the board. \n\n\n Reminder if you are using Docker: \n When working with actual hardware, remember that each board has an ID. If you swap boards and do not refresh the USB Device Filter on the VirtualBox UI, the ID might be stale and the Docker instance may not be able to see the board correctly. For example, you may see an error message like \nError: un
able to find CMSIS-DAP device\n when you try to load or run an image on the board. In that case, you need to click on the USB link in VirtualBox UI, remove the existing USB Device Filter (e.g. \"Atmel Corp. EDBG CMSIS-DAP[0101]\") by clicking on the \"Removes selected USB filter\" button, and add a new filter by clicking on the \"Adds new USB filter\" button.\n\n\n\n\nRun the Blinky Application\n\n\nAfter you load the bootloader successfully onto your board, you can load and run the Blinky application. \n\n\nRun the \nnewt run arduino_blinky 0.0.0\n 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. \n\n\n$ newt run arduino_blinky 0.0.0\nApp image succesfully generated: ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.img\nLoading app image into slot 1\n[~/dev/myproj/repos/mynewt_arduino_zero/hw/bsp/arduino_zero/arduino_zero_debug.sh ~/dev/myproj/repos/mynewt_arduin
o_zero/hw/bsp/arduino_zero ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky]\nOpen On-Chip Debugger 0.9.0 (2015-11-15-13:10)\nLicensed under GNU GPL v2\nFor bug reports, read\nhttp://openocd.org/doc/doxygen/bugs.html\nInfo : only one transport option; autoselect \nswd\n\nadapter speed: 500 kHz\nadapter_nsrst_delay: 100\ncortex_m reset_config sysresetreq\nInfo : CMSIS-DAP: SWD Supported\nInfo : CMSIS-DAP: JTAG Supported\nInfo : CMSIS-DAP: Interface Initialised (SWD)\nInfo : CMSIS-DAP: FW Version = 01.1F.0118\nInfo : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 1 TDO = 1 nTRST = 0 nRESET = 1\nInfo : CMSIS-DAP: Interface ready\nInfo : clock speed 500 kHz\nInfo : SWD IDCODE 0x0bc11477\nInfo : at91samd21g18.cpu: hardware has 4 breakpoints, 2 watchpoints\ntarget state: halted\ntarget halted due to debug-request, current mode: Thread \nxPSR: 0x21000000 pc: 0x0000fca6 psp: 0x20002408\nGNU gdb (GNU Tools for ARM Embedded Processors) 7.8.0.20150604-cvs\nCopyright (C) 2014 Free Software Fo
undation, Inc.\nLicense GPLv3+: GNU GPL version 3 or later \nhttp://gnu.org/licenses/gpl.html\n\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law. Type \nshow copying\n\nand \nshow warranty\n for details.\nThis GDB was configured as \n--host=x86_64-apple-darwin10 --target=arm-none-eabi\n.\nType \nshow configuration\n for configuration details.\nFor bug reporting instructions, please see:\n\nhttp://www.gnu.org/software/gdb/bugs/\n.\nFind the GDB manual and other documentation resources online at:\n\nhttp://www.gnu.org/software/gdb/documentation/\n.\nFor help, type \nhelp\n.\nType \napropos word\n to search for commands related to \nword\n...\nReading symbols from ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.elf...(no debugging symbols found)...done.\nInfo : accepting \ngdb\n connection on tcp/3333\nInfo : SAMD MCU: SAMD21G18A (256KB Flash, 32KB RAM)\n0x0000fca6 in os_tick_idle ()\ntarget state:
halted\ntarget halted due to debug-request, current mode: Thread \nxPSR: 0x21000000 pc: 0x000000b8 msp: 0x20008000\ntarget state: halted\ntarget halted due to debug-request, current mode: Thread \nxPSR: 0x21000000 pc: 0x000000b8 msp: 0x20008000\n(gdb) r\nThe \nremote\n target does not support \nrun\n. Try \nhelp target\n or \ncontinue\n.\n(gdb) c\nContinuing.\n\n\n\n\n\n\n\nNOTE:\n 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.\n\n\nIf you want the image to run without the debugger connected, simply quit the\ndebugger and restart the board. The image you programmed will come up and run on \nthe Arduino on the next boot! \n\n\n\n\nWatch the LED Blink\n\n\nCongratulations! You have created an Mynewt application running on the\nArduino Zero. The LED right next to the power LED should be blinking. It is toggled \nby one task running on the Mynewt OS.
\n\n\nWe have more fun tutorials for you to get your hands dirty. Be bold and try other \nBlinky-like \ntutorials\n or try enabling additional functionality \nsuch as \nremote comms\n on the current board.\n\n\nIf you see anything missing or want to send us feedback, please do so by signing up for \nappropriate mailing lists on our \nCommunity Page\n.\n\n\nKeep on hacking and blinking!",
+ "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 M0 Pro board, replace \nBSP_ARDUINO_ZERO_PRO\n with \nBSP_ARDUINO_ZERO\n in the last \
nnewt target set\n command.\n\n\nThese commands perform the following:\n\n\n\n\nCreate a target named \narduino_boot\n for the Arduino Zero Bootloader. \n\n\nSet the application for the \narduino_boot\n target to the default Apache Mynewt\n bootloader (\n@apache-mynewt-core/apps/boot\n)\n\n\nSet the board support package for the target to\n \n@mynewt_arduino_zero/hw/bsp/arduino_zero\n. This is a reference to the downloaded\n Arduino Zero support from Github.\n\n\nUse the \"optimized\" build profile for the \narduino_boot\n target. This\n instructs Newt to generate smaller and more efficient code for this target.\n This setting is necessary due to the bootloader's strict size constraints.\n\n\nSets the system configuration setting for Board Support Package to support the Arduino Zero Pro. \n\n\n\n\nSee the \nConcepts\n section for more information on setting options.\n\n\n\nCreate a Target for the Blinky Application\n\n\nRun the following \nnewt target\n commands to
create the Blinky application target. We name the application target \narduino_blinky\n.\n\n\n$ newt target create arduino_blinky\nTarget targets/arduino_blinky successfully created\n$ newt target set arduino_blinky app=apps/blinky\nTarget targets/arduino_blinky successfully set target.app to apps/blinky\n$ newt target set arduino_blinky bsp=@mynewt_arduino_zero/hw/bsp/arduino_zero\nTarget targets/arduino_blinky successfully set target.bsp to @mynewt_arduino_zero/hw/bsp/arduino_zero\n$ newt target set arduino_blinky build_profile=debug\nTarget targets/arduino_blinky successfully set target.build_profile to debug\n$ newt target set arduino_blinky 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 a Arduino Zero Pro board, replace \nBSP_ARDUINO_ZERO_PRO\n with \nBSP_ARDUINO_ZERO\n in the last \nnewt target set\n command.\n\n\n\n\nBuild the Bootloader\n\n\nRu
n the \nnewt build arduino_boot\n command to build the bootloader:\n\n\n$ newt build arduino_boot\nBuilding target targets/arduino_boot\nCompiling bin/targets/arduino_boot/generated/src/arduino_boot-sysinit-app.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c\nCompiling bin/targets/arduino_boot/generated/src/arduino_boot-sysflash.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c\nCompiling repos/apache-mynewt-core/apps/boot/src/boot.c\nCompiling repos/apache-mynewt-core/crypto/mbedtls/src/arc4.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/loader.c\nCompiling repos/apache-mynewt-core/crypto/mbedtls/src/aes.c\n\n ....\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bin/targets/arduino_b
oot/app/apps/boot/boot.elf\nTarget successfully built: targets/arduino_boot\n\n\n\n\n\n\n\nBuild the Blinky Application\n\n\nRun the \nnewt build arduino_blinky\n command to build the Blinky application image:\n\n\n$ newt build arduino_blinky\nBuilding target targets/arduino_blinky\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c\nCompiling apps/blinky/src/main.c\nCompiling repos/mynewt_arduino_zero/hw/mcu/atmel/samd21xx/src/sam0/drivers/i2s/i2s.c\nCompiling repos/mynewt_arduino_zero/hw/bsp/arduino_zero/src/hal_bsp.c\nCompiling repos/mynewt_arduino_zero/hw/mcu/atmel/samd21xx/src/sam0/drivers/i2s/i2s_callback.c\nCompiling repos/mynewt_arduino_zero/hw/mcu/atmel/samd21xx/src/sam0/drivers/nvm/nvm.c\n\n ...\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.elf\nTarget successfully built: targets/arduino_blinky\n\n\n\n\n\n\n\nConnect to the Board\n\n\nConnect your computer to the Ardu
ino Zero (from now on we'll call this the\ntarget) with a Micro-USB cable through the Programming Port as shown below.\nMynewt will load the image onto the board and debug the target through this port. You should see a\ngreen LED come on that indicates the board has power.\n\n\nNo external debugger is required. The Arduino Zero comes with an internal\ndebugger that can be accessed by Mynewt.\n\n\nThe images below show the Arduino Zero Programming Port.\n\n\n\n\n\n\n\n\nLoad the Bootloader onto the Board\n\n\nRun the \nnewt load arduino_boot\n command to load the bootloader onto the board:\n\n\n$ newt load arduino_boot\nLoading bootloader\n$\n\n\n\n\n\nThe bootloader is loaded onto your board succesfully when the \nnewt load\n command returns to the command prompt after the \nLoading bootloader\n status message. You can proceed to load and run your Blinky application image (See \nRun the Blinky Application\n).\n\n\nIf the \nnewt load\n command outputs the following error messages,
you will need to erase the board.\n\n\n$ newt load arduino_boot -v\nLoading bootloader\nError: Downloading ~/dev/myproj/bin/targets/arduino_boot/app/apps/boot/boot.elf.bin to 0x0\nOpen On-Chip Debugger 0.9.0 (2015-11-15-05:39)\nLicensed under GNU GPL v2\nFor bug reports, read\n http://openocd.org/doc/doxygen/bugs.html\nInfo : only one transport option; autoselect \nswd\n\nadapter speed: 500 kHz\nadapter_nsrst_delay: 100\ncortex_m reset_config sysresetreq\nInfo : CMSIS-DAP: SWD Supported\nInfo : CMSIS-DAP: JTAG Supported\nInfo : CMSIS-DAP: Interface Initialised (SWD)\nInfo : CMSIS-DAP: FW Version = 01.1F.0118\nInfo : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 1 TDO = 1 nTRST = 0 nRESET = 1\nInfo : CMSIS-DAP: Interface ready\nInfo : clock speed 500 kHz\nInfo : SWD IDCODE 0x0bc11477\nInfo : at91samd21g18.cpu: hardware has 4 breakpoints, 2 watchpoints\nError: Target not halted\n\n\n\n\n\n\nTo erase your board, start a debug session and enter the highlighted commands at the \n(gdb)\n prompts
:\n\n\n$ newt debug arduino_blinky\n(gdb) mon at91samd chip-erase\nchip erased\nchip erased\n(gdb) x/32wx 0\n0x0: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x10: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x20: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x30: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x40: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x50: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x60: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x70: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n(gdb) q\n\n\n\n\n\n\nRun the \nnewt load arduino_boot\n command again after erasing the board. \n\n\n Reminder if you are using Docker: \n When working with actual hardware, remember that each board has an ID. If you swap boards and do not refresh the USB Device Filter on the VirtualBox UI, the ID might be stale and the Docker instance may not be able to see the board correctly. For example, you may see an error message like \nError: un
able to find CMSIS-DAP device\n when you try to load or run an image on the board. In that case, you need to click on the USB link in VirtualBox UI, remove the existing USB Device Filter (e.g. \"Atmel Corp. EDBG CMSIS-DAP[0101]\") by clicking on the \"Removes selected USB filter\" button, and add a new filter by clicking on the \"Adds new USB filter\" button.\n\n\n\n\nRun the Blinky Application\n\n\nAfter you load the bootloader successfully onto your board, you can load and run the Blinky application. \n\n\nRun the \nnewt run arduino_blinky 1.0.0\n 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. \n\n\n$ newt run arduino_blinky 1.0.0\nApp image succesfully generated: ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.img\nLoading app image into slot 1\n[~/dev/myproj/repos/mynewt_arduino_zero/hw/bsp/arduino_zero/arduino_zero_debug.sh ~/dev/myproj/repos/mynewt_arduin
o_zero/hw/bsp/arduino_zero ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky]\nOpen On-Chip Debugger 0.9.0 (2015-11-15-13:10)\nLicensed under GNU GPL v2\nFor bug reports, read\nhttp://openocd.org/doc/doxygen/bugs.html\nInfo : only one transport option; autoselect \nswd\n\nadapter speed: 500 kHz\nadapter_nsrst_delay: 100\ncortex_m reset_config sysresetreq\nInfo : CMSIS-DAP: SWD Supported\nInfo : CMSIS-DAP: JTAG Supported\nInfo : CMSIS-DAP: Interface Initialised (SWD)\nInfo : CMSIS-DAP: FW Version = 01.1F.0118\nInfo : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 1 TDO = 1 nTRST = 0 nRESET = 1\nInfo : CMSIS-DAP: Interface ready\nInfo : clock speed 500 kHz\nInfo : SWD IDCODE 0x0bc11477\nInfo : at91samd21g18.cpu: hardware has 4 breakpoints, 2 watchpoints\ntarget state: halted\ntarget halted due to debug-request, current mode: Thread \nxPSR: 0x21000000 pc: 0x0000fca6 psp: 0x20002408\nGNU gdb (GNU Tools for ARM Embedded Processors) 7.8.0.20150604-cvs\nCopyright (C) 2014 Free Software Fo
undation, Inc.\nLicense GPLv3+: GNU GPL version 3 or later \nhttp://gnu.org/licenses/gpl.html\n\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law. Type \nshow copying\n\nand \nshow warranty\n for details.\nThis GDB was configured as \n--host=x86_64-apple-darwin10 --target=arm-none-eabi\n.\nType \nshow configuration\n for configuration details.\nFor bug reporting instructions, please see:\n\nhttp://www.gnu.org/software/gdb/bugs/\n.\nFind the GDB manual and other documentation resources online at:\n\nhttp://www.gnu.org/software/gdb/documentation/\n.\nFor help, type \nhelp\n.\nType \napropos word\n to search for commands related to \nword\n...\nReading symbols from ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.elf...(no debugging symbols found)...done.\nInfo : accepting \ngdb\n connection on tcp/3333\nInfo : SAMD MCU: SAMD21G18A (256KB Flash, 32KB RAM)\n0x0000fca6 in os_tick_idle ()\ntarget state:
halted\ntarget halted due to debug-request, current mode: Thread \nxPSR: 0x21000000 pc: 0x000000b8 msp: 0x20008000\ntarget state: halted\
<TRUNCATED>
[5/7] incubator-mynewt-site git commit: Added functions in task,
mempool, context switch
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/context_switch/context_switch/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/context_switch/context_switch/index.html b/develop/os/core_os/context_switch/context_switch/index.html
index f918a88..a8fe4a3 100644
--- a/develop/os/core_os/context_switch/context_switch/index.html
+++ b/develop/os/core_os/context_switch/context_switch/index.html
@@ -738,6 +738,10 @@
<td>Inform scheduler that OS time has moved forward.</td>
</tr>
<tr>
+<td><a href="../os_sched_remove/">os_sched_remove</a></td>
+<td>Stops a task and removes it from all the OS task lists.</td>
+</tr>
+<tr>
<td><a href="../os_sched_resort/">os_sched_resort</a></td>
<td>Inform scheduler that the priority of the given task has changed and the <em>ready to run</em> list should be re-sorted.</td>
</tr>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/context_switch/os_arch_ctx_sw/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/context_switch/os_arch_ctx_sw/index.html b/develop/os/core_os/context_switch/os_arch_ctx_sw/index.html
index 1d5aee8..0dd1d77 100644
--- a/develop/os/core_os/context_switch/os_arch_ctx_sw/index.html
+++ b/develop/os/core_os/context_switch/os_arch_ctx_sw/index.html
@@ -344,6 +344,14 @@
<li >
+ <a href="../os_sched_remove/">os_sched_remove</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_sched_resort/">os_sched_resort</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/context_switch/os_sched/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/context_switch/os_sched/index.html b/develop/os/core_os/context_switch/os_sched/index.html
index 7e2e288..e0b7b05 100644
--- a/develop/os/core_os/context_switch/os_sched/index.html
+++ b/develop/os/core_os/context_switch/os_sched/index.html
@@ -344,6 +344,14 @@
<li >
+ <a href="../os_sched_remove/">os_sched_remove</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_sched_resort/">os_sched_resort</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/context_switch/os_sched_ctx_sw_hook/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/context_switch/os_sched_ctx_sw_hook/index.html b/develop/os/core_os/context_switch/os_sched_ctx_sw_hook/index.html
index c57d0c9..d17d5c3 100644
--- a/develop/os/core_os/context_switch/os_sched_ctx_sw_hook/index.html
+++ b/develop/os/core_os/context_switch/os_sched_ctx_sw_hook/index.html
@@ -344,6 +344,14 @@
<li >
+ <a href="../os_sched_remove/">os_sched_remove</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_sched_resort/">os_sched_resort</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/context_switch/os_sched_get_current_task/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/context_switch/os_sched_get_current_task/index.html b/develop/os/core_os/context_switch/os_sched_get_current_task/index.html
index 4bac204..62b53f5 100644
--- a/develop/os/core_os/context_switch/os_sched_get_current_task/index.html
+++ b/develop/os/core_os/context_switch/os_sched_get_current_task/index.html
@@ -344,6 +344,14 @@
<li >
+ <a href="../os_sched_remove/">os_sched_remove</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_sched_resort/">os_sched_resort</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/context_switch/os_sched_insert/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/context_switch/os_sched_insert/index.html b/develop/os/core_os/context_switch/os_sched_insert/index.html
index 9b5c20e..0cf0488 100644
--- a/develop/os/core_os/context_switch/os_sched_insert/index.html
+++ b/develop/os/core_os/context_switch/os_sched_insert/index.html
@@ -344,6 +344,14 @@
<li >
+ <a href="../os_sched_remove/">os_sched_remove</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_sched_resort/">os_sched_resort</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/context_switch/os_sched_next_task/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/context_switch/os_sched_next_task/index.html b/develop/os/core_os/context_switch/os_sched_next_task/index.html
index 3c507dd..af16f1a 100644
--- a/develop/os/core_os/context_switch/os_sched_next_task/index.html
+++ b/develop/os/core_os/context_switch/os_sched_next_task/index.html
@@ -344,6 +344,14 @@
<li >
+ <a href="../os_sched_remove/">os_sched_remove</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_sched_resort/">os_sched_resort</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/context_switch/os_sched_os_timer_exp/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/context_switch/os_sched_os_timer_exp/index.html b/develop/os/core_os/context_switch/os_sched_os_timer_exp/index.html
index 4b9541b..340d430 100644
--- a/develop/os/core_os/context_switch/os_sched_os_timer_exp/index.html
+++ b/develop/os/core_os/context_switch/os_sched_os_timer_exp/index.html
@@ -344,6 +344,14 @@
<li >
+ <a href="../os_sched_remove/">os_sched_remove</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_sched_resort/">os_sched_resort</a>
</li>
@@ -822,8 +830,8 @@
</li>
<li class="pull-right">
- <a href=../os_sched_resort/>
- Next: os_sched_resort
+ <a href=../os_sched_remove/>
+ Next: os_sched_remove
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/context_switch/os_sched_remove/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/context_switch/os_sched_remove/index.html b/develop/os/core_os/context_switch/os_sched_remove/index.html
new file mode 100644
index 0000000..830f865
--- /dev/null
+++ b/develop/os/core_os/context_switch/os_sched_remove/index.html
@@ -0,0 +1,895 @@
+<!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/core_os/context_switch/os_sched_remove/"> -->
+ <link rel="shortcut icon" href="../../../../img/favicon.ico">
+
+ <title>os_sched_remove - 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="os_sched_remove">
+
+
+ <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/">Tutorials</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../os_user_guide/">OS User Guide</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../../mynewt_os/">OS Core</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../os_started/
+">Functions</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../context_switch/">Scheduler</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li><a href="
+ ../os_sched/
+">Functions</a>
+
+
+ <ul>
+
+
+
+ <li >
+ <a href="../os_sched/">os_sched</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_arch_ctx_sw/">os_arch_ctx_sw</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_sched_ctx_sw_hook/">os_sched_ctx_sw_hook</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_sched_get_current_task/">os_sched_get_current_task</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_sched_insert/">os_sched_insert</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_sched_next_task/">os_sched_next_task</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_sched_os_timer_exp/">os_sched_os_timer_exp</a>
+ </li>
+
+
+
+
+
+ <li class="active">
+ <a href="./">os_sched_remove</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_sched_resort/">os_sched_resort</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_sched_set_current_task/">os_sched_set_current_task</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_sched_sleep/">os_sched_sleep</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_sched_wakeup/">os_sched_wakeup</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../time/os_time/">Time</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../task/task/">Tasks</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../event_queue/event_queue/">Event Queues</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../semaphore/semaphore/">Semaphores</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../mutex/mutex/">Mutexes</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../memory_pool/memory_pool/">Memory Pools</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../heap/heap/">Heap</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+
+
+ ../../mbuf/mbuf/
+
+">Memory Buffers</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../sanity/sanity/">Sanity</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../callout/callout/">Callouts</a>
+
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../porting/port_os/">Porting to your Platform</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/console/console/">Console</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/shell/shell/">Shell</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/split/split/">Split Images</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/bootloader/bootloader/">Bootloader</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+
+
+ ../../../modules/fs/fs/fs/
+
+">File System</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/hal/hal/">Hardware Abstraction Layer</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/drivers/driver/">Drivers</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/testutil/testutil/">Test Utilities</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/devmgmt/newtmgr/">Device Management with Newt Manager</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/imgmgr/imgmgr/">Image Manager</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../../modules/baselibc/">Baselibc library</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/json/json/">JSON</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/fcb/fcb/">Flash Circular Buffer</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/stats/stats/">Stats</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/logs/logs/">Logs</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/sysinitconfig/sysinitconfig/">System Configuration And Initialization</a>
+
+
+ </li>
+
+
+
+ </ul>
+
+ </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="../context_switch/">Scheduler</a></li>
+
+
+
+ <li>» <a href="../os_sched/">Functions</a></li>
+
+
+
+ <li>» os_sched_remove</li>
+
+
+
+ </ul>
+</div>
+ </div>
+
+ <h2 id="os_sched_remove"><font color="#F2853F" style="font-size:24pt"> os_sched_remove </font></h2>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #A90D91">int</span> <span style="color: #000000">os_sched_remove</span>(<span style="color: #A90D91">struct</span> <span style="color: #000000">os_task</span> <span style="color: #000000">*t</span>)
+</pre></div>
+
+
+<p>Stops and removes task <code>t</code>.</p>
+<p>The function removes the task from the <code>g_os_task_list</code> task list. It also removes the task from one of the following task list:</p>
+<ul>
+<li><code>g_os_run_list</code> if the task is in the Ready state.</li>
+<li><code>g_os_sleep_list</code> if the task is in the Sleep state.</li>
+</ul>
+<h4 id="arguments">Arguments</h4>
+<table>
+<thead>
+<tr>
+<th>Arguments</th>
+<th>Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td><code>t</code></td>
+<td>Pointer to the <code>os_task</code> structure for the task to be removed.</td>
+</tr>
+</tbody>
+</table>
+<h4 id="returned-values">Returned values</h4>
+<p>OS_OK - The task is removed successfully.</p>
+<h4 id="notes">Notes</h4>
+<p>This function must be called with all interrupts disabled.</p>
+<h4 id="example">Example</h4>
+<p>The <code>os_task_remove</code> function calls the <code>os_sched_remove</code> function to remove a task:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #A90D91">int</span>
+<span style="color: #000000">os_task_remove</span>(<span style="color: #A90D91">struct</span> <span style="color: #000000">os_task</span> <span style="color: #000000">*t</span>)
+{
+ <span style="color: #A90D91">int</span> <span style="color: #000000">rc</span>;
+ <span style="color: #A90D91">os_sr_t</span> <span style="color: #000000">sr</span>;
+
+ <span style="color: #177500">/* Add error checking code to ensure task can removed. */</span>
+
+
+ <span style="color: #177500">/* Call os_sched_remove to remove the task. */</span>
+ <span style="color: #000000">OS_ENTER_CRITICAL</span>(<span style="color: #000000">sr</span>);
+ <span style="color: #000000">rc</span> <span style="color: #000000">=</span> <span style="color: #000000">os_sched_remove</span>(<span style="color: #000000">t</span>);
+ <span style="color: #000000">OS_EXIT_CRITICAL</span>(<span style="color: #000000">sr</span>);
+ <span style="color: #A90D91">return</span> <span style="color: #000000">rc</span>;
+}
+</pre></div>
+
+ <div class="row">
+
+
+
+
+<ul class="nav nav-pills" style="margin-bottom: 10px">
+ <li>
+
+ <a href=../os_sched_os_timer_exp/>
+ <span class="fa fa-arrow-left"></span>
+ Previous: os_sched_os_timer_exp
+ </a>
+
+ </li>
+ <li class="pull-right">
+
+ <a href=../os_sched_resort/>
+ Next: os_sched_resort
+ <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/6b7450f6/develop/os/core_os/context_switch/os_sched_resort/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/context_switch/os_sched_resort/index.html b/develop/os/core_os/context_switch/os_sched_resort/index.html
index 3c7286b..d9edadf 100644
--- a/develop/os/core_os/context_switch/os_sched_resort/index.html
+++ b/develop/os/core_os/context_switch/os_sched_resort/index.html
@@ -343,6 +343,14 @@
+ <li >
+ <a href="../os_sched_remove/">os_sched_remove</a>
+ </li>
+
+
+
+
+
<li class="active">
<a href="./">os_sched_resort</a>
</li>
@@ -830,9 +838,9 @@
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../os_sched_os_timer_exp/>
+ <a href=../os_sched_remove/>
<span class="fa fa-arrow-left"></span>
- Previous: os_sched_os_timer_exp
+ Previous: os_sched_remove
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/context_switch/os_sched_set_current_task/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/context_switch/os_sched_set_current_task/index.html b/develop/os/core_os/context_switch/os_sched_set_current_task/index.html
index 7e42cb2..818dbc2 100644
--- a/develop/os/core_os/context_switch/os_sched_set_current_task/index.html
+++ b/develop/os/core_os/context_switch/os_sched_set_current_task/index.html
@@ -344,6 +344,14 @@
<li >
+ <a href="../os_sched_remove/">os_sched_remove</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_sched_resort/">os_sched_resort</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/context_switch/os_sched_sleep/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/context_switch/os_sched_sleep/index.html b/develop/os/core_os/context_switch/os_sched_sleep/index.html
index b99b6ba..ce39273 100644
--- a/develop/os/core_os/context_switch/os_sched_sleep/index.html
+++ b/develop/os/core_os/context_switch/os_sched_sleep/index.html
@@ -344,6 +344,14 @@
<li >
+ <a href="../os_sched_remove/">os_sched_remove</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_sched_resort/">os_sched_resort</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/context_switch/os_sched_wakeup/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/context_switch/os_sched_wakeup/index.html b/develop/os/core_os/context_switch/os_sched_wakeup/index.html
index 315452a..3238b43 100644
--- a/develop/os/core_os/context_switch/os_sched_wakeup/index.html
+++ b/develop/os/core_os/context_switch/os_sched_wakeup/index.html
@@ -344,6 +344,14 @@
<li >
+ <a href="../os_sched_remove/">os_sched_remove</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_sched_resort/">os_sched_resort</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/event_queue/event_queue/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/event_queue/event_queue/index.html b/develop/os/core_os/event_queue/event_queue/index.html
index c174396..a090d3d 100644
--- a/develop/os/core_os/event_queue/event_queue/index.html
+++ b/develop/os/core_os/event_queue/event_queue/index.html
@@ -839,9 +839,9 @@ The <code>os_eventq</code> structure defines an event queue and has the followin
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../../task/os_task_init/>
+ <a href=../../task/os_task_remove/>
<span class="fa fa-arrow-left"></span>
- Previous: os_task_init
+ Previous: os_task_remove
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/memory_pool/OS_MEMPOOL_BYTES/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/memory_pool/OS_MEMPOOL_BYTES/index.html b/develop/os/core_os/memory_pool/OS_MEMPOOL_BYTES/index.html
index fafc106..e5a2bc7 100644
--- a/develop/os/core_os/memory_pool/OS_MEMPOOL_BYTES/index.html
+++ b/develop/os/core_os/memory_pool/OS_MEMPOOL_BYTES/index.html
@@ -362,6 +362,14 @@
<li >
+ <a href="../os_mempool_info_get_next/">os_mempool_info_get_next</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_mempool_init/">os_mempool_init</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/memory_pool/OS_MEMPOOL_SIZE/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/memory_pool/OS_MEMPOOL_SIZE/index.html b/develop/os/core_os/memory_pool/OS_MEMPOOL_SIZE/index.html
index 37edec0..501842e 100644
--- a/develop/os/core_os/memory_pool/OS_MEMPOOL_SIZE/index.html
+++ b/develop/os/core_os/memory_pool/OS_MEMPOOL_SIZE/index.html
@@ -362,6 +362,14 @@
<li >
+ <a href="../os_mempool_info_get_next/">os_mempool_info_get_next</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_mempool_init/">os_mempool_init</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/memory_pool/memory_pool/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/memory_pool/memory_pool/index.html b/develop/os/core_os/memory_pool/memory_pool/index.html
index b76d8eb..17daad3 100644
--- a/develop/os/core_os/memory_pool/memory_pool/index.html
+++ b/develop/os/core_os/memory_pool/memory_pool/index.html
@@ -723,11 +723,20 @@ Once the memory pool has been initialized the developer can allocate memory bloc
<span style="color: #A90D91">int</span> <span style="color: #000000">mp_block_size</span>;
<span style="color: #A90D91">int</span> <span style="color: #000000">mp_num_blocks</span>;
<span style="color: #A90D91">int</span> <span style="color: #000000">mp_num_free</span>;
+ <span style="color: #A90D91">int</span> <span style="color: #000000">mp_min_free</span>;
<span style="color: #A90D91">uint32_t</span> <span style="color: #000000">mp_membuf_addr</span>;
<span style="color: #000000">STAILQ_ENTRY</span>(<span style="color: #000000">os_mempool</span>) <span style="color: #000000">mp_list</span>;
<span style="color: #000000">SLIST_HEAD</span>(,<span style="color: #000000">os_memblock</span>);
<span style="color: #A90D91">char</span> <span style="color: #000000">*name</span>;
};
+
+<span style="color: #A90D91">struct</span> <span style="color: #000000">os_mempool_info</span> {
+ <span style="color: #A90D91">int</span> <span style="color: #000000">omi_block_size</span>;
+ <span style="color: #A90D91">int</span> <span style="color: #000000">omi_num_blocks</span>;
+ <span style="color: #A90D91">int</span> <span style="color: #000000">omi_num_free</span>;
+ <span style="color: #A90D91">int</span> <span style="color: #000000">omi_min_free</span>;
+ <span style="color: #A90D91">char</span> <span style="color: #000000">omi_name</span>[<span style="color: #000000">OS_MEMPOOL_INFO_NAME_LEN</span>];
+};
</pre></div>
@@ -753,6 +762,10 @@ Once the memory pool has been initialized the developer can allocate memory bloc
<td>Number of free blocks left</td>
</tr>
<tr>
+<td>mp_min_free</td>
+<td>Lowest number of free blocks seen</td>
+</tr>
+<tr>
<td>mp_membuf_addr</td>
<td>The address of the memory block. This is used to check that a valid memory block is being freed.</td>
</tr>
@@ -793,6 +806,10 @@ Once the memory pool has been initialized the developer can allocate memory bloc
<td>Releases previously allocated element back to the pool.</td>
</tr>
<tr>
+<td><a href="../os_mempool_info_get_next">os_mempool_info_get_next</a></td>
+<td>Retrieves memory pool information for the next memory pool.</td>
+</tr>
+<tr>
<td><a href="../OS_MEMPOOL_BYTES">OS_MEMPOOL_BYTES</a></td>
<td>Calculates how many bytes of memory is used by n number of elements, when individual element size is blksize bytes.</td>
</tr>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/memory_pool/os_memblock_get/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/memory_pool/os_memblock_get/index.html b/develop/os/core_os/memory_pool/os_memblock_get/index.html
index c775e00..bf3106b 100644
--- a/develop/os/core_os/memory_pool/os_memblock_get/index.html
+++ b/develop/os/core_os/memory_pool/os_memblock_get/index.html
@@ -362,6 +362,14 @@
<li >
+ <a href="../os_mempool_info_get_next/">os_mempool_info_get_next</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_mempool_init/">os_mempool_init</a>
</li>
@@ -785,8 +793,8 @@
</li>
<li class="pull-right">
- <a href=../os_mempool_init/>
- Next: os_mempool_init
+ <a href=../os_mempool_info_get_next/>
+ Next: os_mempool_info_get_next
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/memory_pool/os_memblock_put/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/memory_pool/os_memblock_put/index.html b/develop/os/core_os/memory_pool/os_memblock_put/index.html
index d1a5af7..bcc6239 100644
--- a/develop/os/core_os/memory_pool/os_memblock_put/index.html
+++ b/develop/os/core_os/memory_pool/os_memblock_put/index.html
@@ -362,6 +362,14 @@
<li >
+ <a href="../os_mempool_info_get_next/">os_mempool_info_get_next</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../os_mempool_init/">os_mempool_init</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/memory_pool/os_mempool_info_get_next/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/memory_pool/os_mempool_info_get_next/index.html b/develop/os/core_os/memory_pool/os_mempool_info_get_next/index.html
new file mode 100644
index 0000000..69aab0b
--- /dev/null
+++ b/develop/os/core_os/memory_pool/os_mempool_info_get_next/index.html
@@ -0,0 +1,879 @@
+<!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/core_os/memory_pool/os_mempool_info_get_next/"> -->
+ <link rel="shortcut icon" href="../../../../img/favicon.ico">
+
+ <title>os_mempool_info_get_next - 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="os_mempool_info_get_next">
+
+
+ <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/">Tutorials</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../os_user_guide/">OS User Guide</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../../mynewt_os/">OS Core</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../os_started/
+">Functions</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../context_switch/context_switch/">Scheduler</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../time/os_time/">Time</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../task/task/">Tasks</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../event_queue/event_queue/">Event Queues</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../semaphore/semaphore/">Semaphores</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../mutex/mutex/">Mutexes</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../memory_pool/">Memory Pools</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li><a href="
+ ../os_memblock_get/
+">Functions/Macros</a>
+
+
+ <ul>
+
+
+
+ <li >
+ <a href="../os_memblock_get/">os_memblock_get</a>
+ </li>
+
+
+
+
+
+ <li class="active">
+ <a href="./">os_mempool_info_get_next</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_mempool_init/">os_mempool_init</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_memblock_put/">os_memblock_put</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../OS_MEMPOOL_BYTES/">OS_MEMPOOL_BYTES</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../OS_MEMPOOL_SIZE/">OS_MEMPOOL_SIZE</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../heap/heap/">Heap</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+
+
+ ../../mbuf/mbuf/
+
+">Memory Buffers</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../sanity/sanity/">Sanity</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../callout/callout/">Callouts</a>
+
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../porting/port_os/">Porting to your Platform</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/console/console/">Console</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/shell/shell/">Shell</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/split/split/">Split Images</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/bootloader/bootloader/">Bootloader</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+
+
+ ../../../modules/fs/fs/fs/
+
+">File System</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/hal/hal/">Hardware Abstraction Layer</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/drivers/driver/">Drivers</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/testutil/testutil/">Test Utilities</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/devmgmt/newtmgr/">Device Management with Newt Manager</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/imgmgr/imgmgr/">Image Manager</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../../modules/baselibc/">Baselibc library</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/json/json/">JSON</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/fcb/fcb/">Flash Circular Buffer</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/stats/stats/">Stats</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/logs/logs/">Logs</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/sysinitconfig/sysinitconfig/">System Configuration And Initialization</a>
+
+
+ </li>
+
+
+
+ </ul>
+
+ </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="../memory_pool/">Memory Pools</a></li>
+
+
+
+ <li>» <a href="../os_memblock_get/">Functions/Macros</a></li>
+
+
+
+ <li>» os_mempool_info_get_next</li>
+
+
+
+ </ul>
+</div>
+ </div>
+
+ <h2 id="os_mempool_info_get_next"><font color="F2853F" style="font-size:24pt"> os_mempool_info_get_next</font></h2>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #A90D91">struct</span> <span style="color: #000000">os_mempool</span> <span style="color: #000000">*</span> <span style="color: #000000">os_mempool_info_get_next</span>(<span style="color: #A90D91">struct</span> <span style="color: #000000">os_mempool</span> <span style="color: #000000">*mp</span>, <span style="color: #A90D91">struct</span> <span style="color: #000000">os_mempool_info</span> <span style="color: #000000">*omi</span>)
+</pre></div>
+
+
+<p>Populates the os_mempool_info structure pointed to by <code>omi</code> with memory pool information.
+The value of <code>mp</code> specifies the memory pool information to populate. If <code>mp</code> is <strong>NULL</strong>, it populates the information for the first memory pool on the memory pool list. If <code>mp</code> is not NULL, it populates the information for the next memory pool after <code>mp</code>. </p>
+<p><br></p>
+<h4 id="arguments">Arguments</h4>
+<table>
+<thead>
+<tr>
+<th>Arguments</th>
+<th>Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td><code>mp</code></td>
+<td>Pointer to the memory pool in the memory pool list from the previous <code>os_mempool_info_get_next</code> function call. The next memory pool after <code>mp</code> is populated. If <code>mp</code> is NULL, the first memory pool on the memory pool list is populated.</td>
+</tr>
+<tr>
+<td><code>omi</code></td>
+<td>Pointer to <code>os_mempool_info</code> structure where memory information will be stored.</td>
+</tr>
+</tbody>
+</table>
+<p><br></p>
+<h4 id="returned-values">Returned values</h4>
+<ul>
+<li>
+<p>A pointer to the memory pool structure that was used to populate the memory pool information structure. </p>
+</li>
+<li>
+<p>NULL indicates <code>mp</code> is the last memory pool on the list and <code>omi</code> is not populated with memory pool information.</p>
+</li>
+</ul>
+<p><br></p>
+<h4 id="example">Example</h4>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #000000">shell_os_mpool_display_cmd</span>(<span style="color: #A90D91">int</span> <span style="color: #000000">argc</span>, <span style="color: #A90D91">char</span> <span style="color: #000000">**argv</span>)
+{
+ <span style="color: #A90D91">struct</span> <span style="color: #000000">os_mempool</span> <span style="color: #000000">*mp</span>;
+ <span style="color: #A90D91">struct</span> <span style="color: #000000">os_mempool_info</span> <span style="color: #000000">omi</span>;
+ <span style="color: #A90D91">char</span> <span style="color: #000000">*name</span>;
+
+ <span style="color: #000000">name</span> <span style="color: #000000">=</span> <span style="color: #A90D91">NULL</span>;
+ <span style="color: #000000">found</span> <span style="color: #000000">=</span> <span style="color: #1C01CE">0</span>;
+
+ <span style="color: #A90D91">if</span> (<span style="color: #000000">argc</span> <span style="color: #000000">></span> <span style="color: #1C01CE">1</span> <span style="color: #000000">&&</span> <span style="color: #000000">strcmp</span>(<span style="color: #000000">argv</span>[<span style="color: #1C01CE">1</span>], <span style="color: #C41A16">""</span>)) {
+ <span style="color: #000000">name</span> <span style="color: #000000">=</span> <span style="color: #000000">argv</span>[<span style="color: #1C01CE">1</span>];
+ }
+ <span style="color: #000000">console_printf</span>(<span style="color: #C41A16">"Mempools: \n"</span>);
+ <span style="color: #000000">mp</span> <span style="color: #000000">=</span> <span style="color: #A90D91">NULL</span>;
+ <span style="color: #000000">console_printf</span>(<span style="color: #C41A16">"%32s %5s %4s %4s %4s\n"</span>, <span style="color: #C41A16">"name"</span>, <span style="color: #C41A16">"blksz"</span>, <span style="color: #C41A16">"cnt"</span>, <span style="color: #C41A16">"free"</span>,
+ <span style="color: #C41A16">"min"</span>);
+ <span style="color: #A90D91">while</span> (<span style="color: #1C01CE">1</span>) {
+ <span style="color: #000000">mp</span> <span style="color: #000000">=</span> <span style="color: #000000">o</span>{<span style="color: #000000">_mempool_info_get_next</span>(<span style="color: #000000">mp</span>, <span style="color: #000000">&omi</span>);
+ <span style="color: #A90D91">if</span> (<span style="color: #000000">mp</span> <span style="color: #000000">==</span> <span style="color: #A90D91">NULL</span>) {
+ <span style="color: #A90D91">break</span>;
+ }
+ <span style="color: #A90D91">if</span> (<span style="color: #000000">name</span>) {
+ <span style="color: #A90D91">if</span> (<span style="color: #000000">strcmp</span>(<span style="color: #000000">name</span>, <span style="color: #000000">omi</span>.<span style="color: #000000">omi_name</span>)) {
+ <span style="color: #A90D91">continue</span>;
+ } <span style="color: #A90D91">else</span> {
+ <span style="color: #000000">found</span> <span style="color: #000000">=</span> <span style="color: #1C01CE">1</span>;
+ }
+ }
+
+ <span style="color: #000000">console_printf</span>(<span style="color: #C41A16">"%32s %5d %4d %4d %4d\n"</span>, <span style="color: #000000">omi</span>.<span style="color: #000000">omi_name</span>,
+ <span style="color: #000000">omi</span>.<span style="color: #000000">omi_block_size</span>, <span style="color: #000000">omi</span>.<span style="color: #000000">omi_num_blocks</span>,
+ <span style="color: #000000">omi</span>.<span style="color: #000000">omi_num_free</span>, <span style="color: #000000">omi</span>.<span style="color: #000000">omi_min_free</span>);
+ }
+
+ <span style="color: #A90D91">if</span> (<span style="color: #000000">name</span> <span style="color: #000000">&&</span> <span style="color: #000000">!found</span>) {
+ <span style="color: #000000">console_printf</span>(<span style="color: #C41A16">"Couldn't find a memory pool with name %s\n"</span>,
+ <span style="color: #000000">name</span>);
+ }
+ <span style="color: #A90D91">return</span> (<span style="color: #1C01CE">0</span>);
+}
+</pre></div>
+
+ <div class="row">
+
+
+
+
+<ul class="nav nav-pills" style="margin-bottom: 10px">
+ <li>
+
+ <a href=../os_memblock_get/>
+ <span class="fa fa-arrow-left"></span>
+ Previous: os_memblock_get
+ </a>
+
+ </li>
+ <li class="pull-right">
+
+ <a href=../os_mempool_init/>
+ Next: os_mempool_init
+ <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/6b7450f6/develop/os/core_os/memory_pool/os_mempool_init/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/memory_pool/os_mempool_init/index.html b/develop/os/core_os/memory_pool/os_mempool_init/index.html
index bfdb2ec..e039fb3 100644
--- a/develop/os/core_os/memory_pool/os_mempool_init/index.html
+++ b/develop/os/core_os/memory_pool/os_mempool_init/index.html
@@ -361,6 +361,14 @@
+ <li >
+ <a href="../os_mempool_info_get_next/">os_mempool_info_get_next</a>
+ </li>
+
+
+
+
+
<li class="active">
<a href="./">os_mempool_init</a>
</li>
@@ -802,9 +810,9 @@
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../os_memblock_get/>
+ <a href=../os_mempool_info_get_next/>
<span class="fa fa-arrow-left"></span>
- Previous: os_memblock_get
+ Previous: os_mempool_info_get_next
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/task/os_task_count/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/task/os_task_count/index.html b/develop/os/core_os/task/os_task_count/index.html
index b65d6e1..50d1061 100644
--- a/develop/os/core_os/task/os_task_count/index.html
+++ b/develop/os/core_os/task/os_task_count/index.html
@@ -331,6 +331,14 @@
+
+
+ <li >
+ <a href="../os_task_remove/">os_task_remove</a>
+ </li>
+
+
+
</ul>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/task/os_task_info_get_next/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/task/os_task_info_get_next/index.html b/develop/os/core_os/task/os_task_info_get_next/index.html
index d1e9712..e411a47 100644
--- a/develop/os/core_os/task/os_task_info_get_next/index.html
+++ b/develop/os/core_os/task/os_task_info_get_next/index.html
@@ -331,6 +331,14 @@
+
+
+ <li >
+ <a href="../os_task_remove/">os_task_remove</a>
+ </li>
+
+
+
</ul>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/task/os_task_init/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/task/os_task_init/index.html b/develop/os/core_os/task/os_task_init/index.html
index 26036da..89bda77 100644
--- a/develop/os/core_os/task/os_task_init/index.html
+++ b/develop/os/core_os/task/os_task_init/index.html
@@ -331,6 +331,14 @@
+
+
+ <li >
+ <a href="../os_task_remove/">os_task_remove</a>
+ </li>
+
+
+
</ul>
</li>
@@ -803,8 +811,8 @@ tasks.</p>
</li>
<li class="pull-right">
- <a href=../../event_queue/event_queue/>
- Next: Event Queues
+ <a href=../os_task_remove/>
+ Next: os_task_remove
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/develop/os/core_os/task/os_task_remove/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/task/os_task_remove/index.html b/develop/os/core_os/task/os_task_remove/index.html
new file mode 100644
index 0000000..bdace0b
--- /dev/null
+++ b/develop/os/core_os/task/os_task_remove/index.html
@@ -0,0 +1,831 @@
+<!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/core_os/task/os_task_remove/"> -->
+ <link rel="shortcut icon" href="../../../../img/favicon.ico">
+
+ <title>os_task_remove - 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="os_task_remove">
+
+
+ <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/">Tutorials</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../os_user_guide/">OS User Guide</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../../mynewt_os/">OS Core</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../os_started/
+">Functions</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../context_switch/context_switch/">Scheduler</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../time/os_time/">Time</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../task/">Tasks</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li><a href="
+ ../os_task_count/
+">Functions</a>
+
+
+ <ul>
+
+
+
+ <li >
+ <a href="../os_task_count/">os_task_count</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_task_info_get_next/">os_task_info_get_next</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../os_task_init/">os_task_init</a>
+ </li>
+
+
+
+
+
+ <li class="active">
+ <a href="./">os_task_remove</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../event_queue/event_queue/">Event Queues</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../semaphore/semaphore/">Semaphores</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../mutex/mutex/">Mutexes</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../memory_pool/memory_pool/">Memory Pools</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../heap/heap/">Heap</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+
+
+ ../../mbuf/mbuf/
+
+">Memory Buffers</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../sanity/sanity/">Sanity</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../callout/callout/">Callouts</a>
+
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../porting/port_os/">Porting to your Platform</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/console/console/">Console</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/shell/shell/">Shell</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/split/split/">Split Images</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/bootloader/bootloader/">Bootloader</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+
+
+ ../../../modules/fs/fs/fs/
+
+">File System</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/hal/hal/">Hardware Abstraction Layer</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/drivers/driver/">Drivers</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/testutil/testutil/">Test Utilities</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/devmgmt/newtmgr/">Device Management with Newt Manager</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/imgmgr/imgmgr/">Image Manager</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../../modules/baselibc/">Baselibc library</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/json/json/">JSON</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/fcb/fcb/">Flash Circular Buffer</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/stats/stats/">Stats</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/logs/logs/">Logs</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../modules/sysinitconfig/sysinitconfig/">System Configuration And Initialization</a>
+
+
+ </li>
+
+
+
+ </ul>
+
+ </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="../task/">Tasks</a></li>
+
+
+
+ <li>» <a href="../os_task_count/">Functions</a></li>
+
+
+
+ <li>» os_task_remove</li>
+
+
+
+ </ul>
+</div>
+ </div>
+
+ <h2 id="os_task_remove"><font color="F2853F" style="font-size:24pt"> os_task_remove</font></h2>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #A90D91">int</span> <span style="color: #000000">os_task_remove</span>(<span style="color: #A90D91">struct</span> <span style="color: #000000">os_task</span> <span style="color: #000000">*t</span>)
+</pre></div>
+
+
+<p>Removes a task, <code>t</code>, from the task list. A task cannot be removed when it is in one of the following states:</p>
+<ul>
+<li>It is running - a task cannot remove itself.</li>
+<li>It has not been initialized.</li>
+<li>It is holding a lock on a semphore or mutex.</li>
+<li>It is suspended waiting on a lock (semaphore or mutex) or for an event on an event queue.</li>
+</ul>
+<p><br></p>
+<h4 id="arguments">Arguments</h4>
+<table>
+<thead>
+<tr>
+<th>Arguments</th>
+<th>Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td><code>t</code></td>
+<td>Pointer to the <code>os_task</code> structure for the task to be removed</td>
+</tr>
+</tbody>
+</table>
+<p><br></p>
+<h4 id="returned-values">Returned values</h4>
+<p><code>OS_OK</code>: Task <code>t</code> is removed sucessfully.
+<br><code>OS_INVALID_PARM</code>: Task <code>t</code> is the calling task. A task cannot remove itself.
+<br><code>OS_NOT_STARTED</code>: Task <code>t</code> is not initialized.
+<br><code>OS_EBUSY</code>: Task <code>t</code> is either holding a lock or suspended waiting on lock on event.
+<br></p>
+<h4 id="example">Example</h4>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="color: #A90D91">struct</span> <span style="color: #000000">os_task</span> <span style="color: #000000">worker_task</span>;
+
+<span style="color: #A90D91">int</span>
+<span style="color: #000000">remove_my_worker_task</span>(<span style="color: #A90D91">void</span>)
+{
+ <span style="color: #177500">/* Add error checking code to ensure task can removed. */</span>
+
+ <span style="color: #177500">/* Call os_task_remove to remove the worker task */</span>
+ <span style="color: #000000">rc</span> <span style="color: #000000">=</span> <span style="color: #000000">os_task_remove</span>(<span style="color: #000000">&worker_task</span>);
+ <span style="color: #A90D91">return</span> <span style="color: #000000">rc</span>;
+}
+</pre></div>
+
+ <div class="row">
+
+
+
+
+<ul class="nav nav-pills" style="margin-bottom: 10px">
+ <li>
+
+ <a href=../os_task_init/>
+ <span class="fa fa-arrow-left"></span>
+ Previous: os_task_init
+ </a>
+
+ </li>
+ <li class="pull-right">
+
+ <a href=../../event_queue/event_queue/>
+ Next: Event Queues
+ <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/6b7450f6/develop/os/core_os/task/task/index.html
----------------------------------------------------------------------
diff --git a/develop/os/core_os/task/task/index.html b/develop/os/core_os/task/task/index.html
index 59d0605..41b73b5 100644
--- a/develop/os/core_os/task/task/index.html
+++ b/develop/os/core_os/task/task/index.html
@@ -1016,6 +1016,10 @@ task simply toggles an LED at a one second interval.</p>
<td><a href="../os_task_info_get_next/">os_task_info_get_next</a></td>
<td>Populates the os task info structure given with task information.</td>
</tr>
+<tr>
+<td><a href="../os_task_remove/">os_task_remove</a></td>
+<td>Removes a task from the task list.</td>
+</tr>
</tbody>
</table>
[4/7] incubator-mynewt-site git commit: Added functions in task,
mempool, context switch
Posted by ad...@apache.org.
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>
[7/7] incubator-mynewt-site git commit: Added functions in task,
mempool, context switch
Posted by ad...@apache.org.
Added functions in task, mempool, context switch
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/6b7450f6
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/6b7450f6
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/6b7450f6
Branch: refs/heads/asf-site
Commit: 6b7450f63cc3a32610b607c11f390a0df3de9e8a
Parents: 7d514c1
Author: aditihilbert <ad...@runtime.io>
Authored: Sun Mar 26 23:41:18 2017 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Sun Mar 26 23:41:18 2017 -0700
----------------------------------------------------------------------
develop/mkdocs/search_index.json | 226 +++--
.../context_switch/context_switch/index.html | 4 +
.../context_switch/os_arch_ctx_sw/index.html | 8 +
.../core_os/context_switch/os_sched/index.html | 8 +
.../os_sched_ctx_sw_hook/index.html | 8 +
.../os_sched_get_current_task/index.html | 8 +
.../context_switch/os_sched_insert/index.html | 8 +
.../os_sched_next_task/index.html | 8 +
.../os_sched_os_timer_exp/index.html | 12 +-
.../context_switch/os_sched_remove/index.html | 895 +++++++++++++++++++
.../context_switch/os_sched_resort/index.html | 12 +-
.../os_sched_set_current_task/index.html | 8 +
.../context_switch/os_sched_sleep/index.html | 8 +
.../context_switch/os_sched_wakeup/index.html | 8 +
.../core_os/event_queue/event_queue/index.html | 4 +-
.../memory_pool/OS_MEMPOOL_BYTES/index.html | 8 +
.../memory_pool/OS_MEMPOOL_SIZE/index.html | 8 +
.../core_os/memory_pool/memory_pool/index.html | 17 +
.../memory_pool/os_memblock_get/index.html | 12 +-
.../memory_pool/os_memblock_put/index.html | 8 +
.../os_mempool_info_get_next/index.html | 879 ++++++++++++++++++
.../memory_pool/os_mempool_init/index.html | 12 +-
.../os/core_os/task/os_task_count/index.html | 8 +
.../task/os_task_info_get_next/index.html | 8 +
develop/os/core_os/task/os_task_init/index.html | 12 +-
.../os/core_os/task/os_task_remove/index.html | 831 +++++++++++++++++
develop/os/core_os/task/task/index.html | 4 +
.../os/get_started/project_create/index.html | 90 +-
develop/os/get_started/serial_access/index.html | 2 +-
.../os/modules/bootloader/bootloader/index.html | 10 +-
develop/os/tutorials/add_newtmgr/index.html | 2 +-
develop/os/tutorials/arduino_zero/index.html | 37 +-
develop/os/tutorials/blinky_primo/index.html | 34 +-
develop/os/tutorials/nRF52/index.html | 27 +-
develop/os/tutorials/olimex/index.html | 18 +-
develop/os/tutorials/project-slinky/index.html | 4 +-
.../tutorials/project-target-slinky/index.html | 273 +++---
develop/sitemap.xml | 24 +-
latest/mkdocs/search_index.json | 226 +++--
.../context_switch/context_switch/index.html | 4 +
.../context_switch/os_arch_ctx_sw/index.html | 8 +
.../core_os/context_switch/os_sched/index.html | 8 +
.../os_sched_ctx_sw_hook/index.html | 8 +
.../os_sched_get_current_task/index.html | 8 +
.../context_switch/os_sched_insert/index.html | 8 +
.../os_sched_next_task/index.html | 8 +
.../os_sched_os_timer_exp/index.html | 12 +-
.../context_switch/os_sched_remove/index.html | 895 +++++++++++++++++++
.../context_switch/os_sched_resort/index.html | 12 +-
.../os_sched_set_current_task/index.html | 8 +
.../context_switch/os_sched_sleep/index.html | 8 +
.../context_switch/os_sched_wakeup/index.html | 8 +
.../core_os/event_queue/event_queue/index.html | 4 +-
.../memory_pool/OS_MEMPOOL_BYTES/index.html | 8 +
.../memory_pool/OS_MEMPOOL_SIZE/index.html | 8 +
.../core_os/memory_pool/memory_pool/index.html | 17 +
.../memory_pool/os_memblock_get/index.html | 12 +-
.../memory_pool/os_memblock_put/index.html | 8 +
.../os_mempool_info_get_next/index.html | 879 ++++++++++++++++++
.../memory_pool/os_mempool_init/index.html | 12 +-
latest/os/core_os/task/os_task_count/index.html | 8 +
.../task/os_task_info_get_next/index.html | 8 +
latest/os/core_os/task/os_task_init/index.html | 12 +-
.../os/core_os/task/os_task_remove/index.html | 831 +++++++++++++++++
latest/os/core_os/task/task/index.html | 4 +
latest/os/get_started/project_create/index.html | 90 +-
latest/os/get_started/serial_access/index.html | 2 +-
.../os/modules/bootloader/bootloader/index.html | 10 +-
latest/os/tutorials/add_newtmgr/index.html | 2 +-
latest/os/tutorials/arduino_zero/index.html | 37 +-
latest/os/tutorials/blinky_primo/index.html | 34 +-
latest/os/tutorials/nRF52/index.html | 27 +-
latest/os/tutorials/olimex/index.html | 18 +-
latest/os/tutorials/project-slinky/index.html | 4 +-
.../tutorials/project-target-slinky/index.html | 273 +++---
latest/sitemap.xml | 24 +-
sitemap.xml | 26 +-
v0_9_0/sitemap.xml | 26 +-
78 files changed, 6514 insertions(+), 644 deletions(-)
----------------------------------------------------------------------
[3/7] incubator-mynewt-site git commit: Added functions in task,
mempool, context switch
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/6b7450f6/latest/mkdocs/search_index.json
----------------------------------------------------------------------
diff --git a/latest/mkdocs/search_index.json b/latest/mkdocs/search_index.json
index 957c469..665dde5 100644
--- a/latest/mkdocs/search_index.json
+++ b/latest/mkdocs/search_index.json
@@ -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: 0-latest\n user: apache\n repo: incubator-mynewt-core\n\n\n\n\n\nChanging to 0-dev will put you on the develop branch. \nThe Develop Branch may not be stable and \nyou 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
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.\n\n\n$ tree -L 2 repos/apache-mynewt-core/\nrepos/apache-mynewt-core/\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 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 ffs2native\n\u2502\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 \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 \u2514\u2500\u2500 split\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 \u2514\u2500\u2500 sim\n\u251c\u2500\u2500 crypto\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mbedtls\n\u2502\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\u00a
0 \u251c\u2500\u2500 json\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 tinycbor\n\u251c\u2500\u2500 fs\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\u2500\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\u2500\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 \u251c\u2500\u2500
testreport\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\n87 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\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\nsnip\n\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 a
djusted 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\n...lots of compiling and testing...\n...about 2 minutes later ...\nCompiling mn_sock_test.c\nArchiving mn_socket.a\nLinking test_mn_socket\nExecuting test: /Users/dsimmons/myproj/bin/unittest/sys/mn_socket/test_mn_socket\nPassed 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]\nAll tests passe
d\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 main.c\nArchiving blinky.a\nCompiling hal_bsp.c\nCompiling os_bsp.c\nCompiling sbrk.c\nArchiving native.a\nCompiling flash_map.c\n\nsnip\n\nLinking blinky.elf\nApp successfully built: ~/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\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 \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!",
"title": "Create Your First Project"
},
{
@@ -372,22 +372,22 @@
},
{
"location": "/os/get_started/project_create/#newt-new",
- "text": "Choose a project name. For this tutorial we will call this project myproj .\nEnter the newt new myproj command. $ newt new myproj\nDownloading project skeleton from apache/incubator-mynewt-blinky...\nInstalling skeleton in myproj...\nProject myproj successfully created. Newt populates this new project with a base skeleton of a new Apache Mynewt \nproject. It has the following structure. Note : If you do not have tree , install it by running brew install tree . $ 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 The Newt tool has installed the base files for a project comprising the following: The file project.yml 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. The file apps/blinky/pkg.yml contains the description of your application\nand its package dependencies. A target directory containing my_blinky_sim , a target descriptor used to\nbuild a version of myproj. Use newt target show to see available build \ntargets. A non-buildable target called unittest . This is used internally by newt and is not a formal build target. NOTE: The actual code and pack
age files are not installed \n(except the template for main.c ). See the next step for installing the packages. NOTE: 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. repository.apache-mynewt-core:\n type: github\n vers: 0-latest\n user: apache\n repo: incubator-mynewt-core Changing to 0-dev will put you on the develop branch. The Develop Branch may not be stable and \nyou may encounter bugs or other problems.",
+ "text": "Choose a project name. For this tutorial we will call this project myproj .\nEnter the newt new myproj command. $ newt new myproj\nDownloading project skeleton from apache/incubator-mynewt-blinky...\nInstalling skeleton in myproj...\nProject myproj successfully created. Newt populates this new project with a base skeleton of a new Apache Mynewt \nproject. It has the following structure. Note : If you do not have tree , install it by running brew install tree . $ 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 The Newt tool has installed the base files for a project comprising the following: The file project.yml 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. The file apps/blinky/pkg.yml contains the description of your application\nand its package dependencies. A target directory containing my_blinky_sim , a target descriptor used to\nbuild a version of myproj. Use newt target show to see available build \ntargets. A non-buildable target called unittest . This is used internally by newt and is not a formal build target. NOTE: The actual code and pack
age files are not installed \n(except the template for main.c ). See the next step for installing the packages. NOTE: 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. repository.apache-mynewt-core:\n type: github\n vers: 1-latest\n user: apache\n repo: incubator-mynewt-core Changing to 1-dev will put you on the develop branch. The Develop Branch may not be stable and you may encounter bugs or other problems.",
"title": "Newt New"
},
{
"location": "/os/get_started/project_create/#newt-install",
- "text": "Once 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 newt install command will\nfetch this repository. $ newt install\napache-mynewt-core NOTE: apache-mynewt-core may take a while to download. To see progress,\nuse the -v (verbose) option to install. Once newt install has successfully finished, the contents of apache-mynewt-core 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. $ tree -L 2 repos/apache-mynewt-core/\nrepos/apache-mynewt-core/\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\u2
500\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 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 ffs2native\n\u2502\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 \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 \u2514\u2500\u
2500 split\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 \u2514\u2500\u2500 sim\n\u251c\u2500\u2500 crypto\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 mbedtls\n\u2502\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 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 \u25
1c\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\u2500\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\u2500\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 \u251c\u2500\u2500 testreport\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\n87 directories, 9 files As you can see, the core of the Apache Mynewt operating system has been brought \ninto your local directory.",
+ "text": "Once 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 newt install command will\nfetch this repository. $ newt install\napache-mynewt-core NOTE: apache-mynewt-core may take a while to download. To see progress,\nuse the -v (verbose) option to install. Once newt install has successfully finished, the contents of apache-mynewt-core 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. $ 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\u25
1c\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\u2502\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\u00
a0\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\u2502\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\u
00a0\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\u2500\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\u250
0\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\u2500\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 As you can see, the core of the Apache Mynewt operating system has been brought \ninto your local directory.",
"title": "Newt Install"
},
{
"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 snip 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 configuration 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 uni
nstall 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\n...lots of compiling and testing...\n...about 2 minutes later ...\nCompiling mn_sock_test.c\nArchiving mn_socket.a\nLinking test_mn_socket\nExecuting test: /Users/dsimmons/myproj/bin/unittest/sys/mn_socket/test_mn_socket\nPassed 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]\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 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",
"title": "Test the project's packages"
},
{
"location": "/os/get_started/project_create/#build-the-project",
- "text": "To build and run your new application, simply issue the following command: $ newt build my_blinky_sim \nBuilding target targets/my_blinky_sim\nCompiling main.c\nArchiving blinky.a\nCompiling hal_bsp.c\nCompiling os_bsp.c\nCompiling sbrk.c\nArchiving native.a\nCompiling flash_map.c snip \nLinking blinky.elf\nApp successfully built: ~/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf",
+ "text": "To build and run your new application, simply issue the following command: $ 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",
"title": "Build the Project"
},
{
@@ -402,7 +402,7 @@
},
{
"location": "/os/get_started/serial_access/",
- "text": "Using the Serial Port with Mynewt OS\n\n\nSome of the projects and tutorials here will allow you to use a serial port\nto interact with your Mynewt project. While most modern PCs and laptops\nno longer have a true serial port, almost all can use their USB ports\nas serial ports. \n\n\nThis will show you how to connect to some of the development boards\nwe use via a serial port. \n\n\nThe development boards covered here are:\n\n\n\n\nNordic Semiconductor NRF52dk\n\n\nArduino M0 Pro\n\n\n\n\nIn order to communicate with these boards you will also need a USB\n--\nSerial\nconverted. We'll be using the \nAdaFruit FT232H Breakout Board\n for\nthis, but almost any similar board should work just as well. You will also\nneed Minicom or a similar Serial communications application. We'll show you how\nto use the \nscreen\n command built in to Mac OS X, but later tutorials will\nalso show Minicom setup.\n\n\nSo let's get started!\n\n\n\n\nSetup FT232H\n\n\nThis is a great b
oard because it's so easy to set up, and it can do Serial UART,\nSPI, I2C and GPIO as well. There's full documentation on the board \nhere\n\n but we're only covering the wiring for the Serial UART. \n\n\nStart by connecting a jumper wire to Pin D0. This will be the UART Tx pin, \nwhich we'll then connect to the Rx pin on the Development Board.\n\n\nNext connect a jumper wire to pin D1. This will be the UART Rx pin,\nwhich we'll connect to the Tx pin on the development board.\n\n\nFinally connect a jumper wire to the GND pin.\n\n\nIt should look like this:\n\n\n\n\n\n\nSetup Nordic Semiconductor NRF52DK\n\n\nOn the NRF52DK developer kit board, the Rx pin is P0.08, so you'll attach your\njumper wire from the Tx pin (D0) of the FT232H board here.\n\n\nThe TX Pin is pin P0.08, so you'll attache the jumper wire from the Rx Pin (D1)\non the FT232H board here. \n\n\nFinally, the GND wire should go to the GND Pin on the NRF52DK. When you're\ndone, your wiring should look like this:\n\n\n \
n\n\n\n\nSetup Arduino M0 Pro\n\n\nOn the Arduino M0 Pro, the Tx and Rx pins are clearly labeled as such, as is the GND\npin. Just make sure you wire Rx from the FT232H to TX on the M0 Pro, and vice-versa.\n\n\nYour Arduino M0 Pro should look like this:\n\n\n\n\n\n\nSetup Serial Communications\n\n\nAs mentioned earlier, we'll be using the built in \nscreen\n command for this, but we'll still \nneed to know which serial port to connect to. So, before plugging in the FT232H Board, \ncheck to see what USB devices are already connected:\n\n\n$ ls -la /dev/*usb*\n0 crw-rw-rw- 1 root wheel 20, 63 Nov 23 11:13 /dev/cu.usbmodem401322\n0 crw-rw-rw- 1 root wheel 20, 62 Nov 23 11:13 /dev/tty.usbmodem401322\n$\n\n\n\n\n\nNow, plug in the FT232H board, and run that command again:\n\n\n$ ls -la /dev/*usb*\n0 crw-rw-rw- 1 root wheel 20, 63 Nov 23 11:13 /dev/cu.usbmodem401322\n0 crw-rw-rw- 1 root wheel 20, 65 Nov 23 11:26 /dev/cu.usbserial-0020124\n0 crw-rw-rw- 1 root wheel
20, 62 Nov 23 11:13 /dev/tty.usbmodem401322\n0 crw-rw-rw- 1 root wheel 20, 64 Nov 23 11:26 /dev/tty.usbserial-0020124\n$\n\n\n\n\n\nSo the FT232H is connected to \n/dev/tty.usbserial-0020124\n (The number after tty.usbserial\nwill be different on your machine.)\n\n\nSo let's connect to it:\n\n\n$ screen /dev/tty.usbserial-0020124 115200\n\n\n\n\n\nTo exit out of \nscreen\n you'll type \ncontrol-A\n followed by \ncontrol-\\\n and you'll\nbe back to a terminal prompt.\n\n\nIf you'd like to use Minicom:\n\n\n$ minicom -D /dev/tty.usbserial-0020124\n\n\n\n\n\nWelcome to minicom 2.7\n\n\nOPTIONS: \nCompiled on Nov 24 2015, 16:14:21.\nPort /dev/tty.usbserial-0020124, 09:57:17\n\n\nPress Meta-Z for help on special keys\n```\n\n\n\n\nIf there's no Mynewt app running, or the Mynewt app doesn't have the Shell and Console\nenabled, you won't see anything there, but you can always refer back to this page\nfrom later tutorials if you need to.\n\n\nNow that you know how to communicate with
your mynewt application, let's move on to\ncreating one!",
+ "text": "Using the Serial Port with Mynewt OS\n\n\nSome of the projects and tutorials here will allow you to use a serial port\nto interact with your Mynewt project. While most modern PCs and laptops\nno longer have a true serial port, almost all can use their USB ports\nas serial ports. \n\n\nThis will show you how to connect to some of the development boards\nwe use via a serial port. \n\n\nThe development boards covered here are:\n\n\n\n\nNordic Semiconductor NRF52dk\n\n\nArduino M0 Pro\n\n\n\n\nIn order to communicate with these boards you will also need a USB\n--\nSerial\nconverted. We'll be using the \nAdaFruit FT232H Breakout Board\n for\nthis, but almost any similar board should work just as well. You will also\nneed Minicom or a similar Serial communications application. We'll show you how\nto use the \nscreen\n command built in to Mac OS X, but later tutorials will\nalso show Minicom setup.\n\n\nSo let's get started!\n\n\n\n\nSetup FT232H\n\n\nThis is a great b
oard because it's so easy to set up, and it can do Serial UART,\nSPI, I2C and GPIO as well. There's full documentation on the board \nhere\n\n but we're only covering the wiring for the Serial UART. \n\n\nStart by connecting a jumper wire to Pin D0. This will be the UART Tx pin, \nwhich we'll then connect to the Rx pin on the Development Board.\n\n\nNext connect a jumper wire to pin D1. This will be the UART Rx pin,\nwhich we'll connect to the Tx pin on the development board.\n\n\nFinally connect a jumper wire to the GND pin.\n\n\nIt should look like this:\n\n\n\n\n\n\nSetup Nordic Semiconductor NRF52DK\n\n\nOn the NRF52DK developer kit board, the Rx pin is P0.08, so you'll attach your\njumper wire from the Tx pin (D0) of the FT232H board here.\n\n\nThe TX Pin is pin P0.06, so you'll attache the jumper wire from the Rx Pin (D1)\non the FT232H board here. \n\n\nFinally, the GND wire should go to the GND Pin on the NRF52DK. When you're\ndone, your wiring should look like this:\n\n\n \
n\n\n\n\nSetup Arduino M0 Pro\n\n\nOn the Arduino M0 Pro, the Tx and Rx pins are clearly labeled as such, as is the GND\npin. Just make sure you wire Rx from the FT232H to TX on the M0 Pro, and vice-versa.\n\n\nYour Arduino M0 Pro should look like this:\n\n\n\n\n\n\nSetup Serial Communications\n\n\nAs mentioned earlier, we'll be using the built in \nscreen\n command for this, but we'll still \nneed to know which serial port to connect to. So, before plugging in the FT232H Board, \ncheck to see what USB devices are already connected:\n\n\n$ ls -la /dev/*usb*\n0 crw-rw-rw- 1 root wheel 20, 63 Nov 23 11:13 /dev/cu.usbmodem401322\n0 crw-rw-rw- 1 root wheel 20, 62 Nov 23 11:13 /dev/tty.usbmodem401322\n$\n\n\n\n\n\nNow, plug in the FT232H board, and run that command again:\n\n\n$ ls -la /dev/*usb*\n0 crw-rw-rw- 1 root wheel 20, 63 Nov 23 11:13 /dev/cu.usbmodem401322\n0 crw-rw-rw- 1 root wheel 20, 65 Nov 23 11:26 /dev/cu.usbserial-0020124\n0 crw-rw-rw- 1 root wheel
20, 62 Nov 23 11:13 /dev/tty.usbmodem401322\n0 crw-rw-rw- 1 root wheel 20, 64 Nov 23 11:26 /dev/tty.usbserial-0020124\n$\n\n\n\n\n\nSo the FT232H is connected to \n/dev/tty.usbserial-0020124\n (The number after tty.usbserial\nwill be different on your machine.)\n\n\nSo let's connect to it:\n\n\n$ screen /dev/tty.usbserial-0020124 115200\n\n\n\n\n\nTo exit out of \nscreen\n you'll type \ncontrol-A\n followed by \ncontrol-\\\n and you'll\nbe back to a terminal prompt.\n\n\nIf you'd like to use Minicom:\n\n\n$ minicom -D /dev/tty.usbserial-0020124\n\n\n\n\n\nWelcome to minicom 2.7\n\n\nOPTIONS: \nCompiled on Nov 24 2015, 16:14:21.\nPort /dev/tty.usbserial-0020124, 09:57:17\n\n\nPress Meta-Z for help on special keys\n```\n\n\n\n\nIf there's no Mynewt app running, or the Mynewt app doesn't have the Shell and Console\nenabled, you won't see anything there, but you can always refer back to this page\nfrom later tutorials if you need to.\n\n\nNow that you know how to communicate with
your mynewt application, let's move on to\ncreating one!",
"title": "Serial Port Setup"
},
{
@@ -417,7 +417,7 @@
},
{
"location": "/os/get_started/serial_access/#setup-nordic-semiconductor-nrf52dk",
- "text": "On the NRF52DK developer kit board, the Rx pin is P0.08, so you'll attach your\njumper wire from the Tx pin (D0) of the FT232H board here. The TX Pin is pin P0.08, so you'll attache the jumper wire from the Rx Pin (D1)\non the FT232H board here. Finally, the GND wire should go to the GND Pin on the NRF52DK. When you're\ndone, your wiring should look like this:",
+ "text": "On the NRF52DK developer kit board, the Rx pin is P0.08, so you'll attach your\njumper wire from the Tx pin (D0) of the FT232H board here. The TX Pin is pin P0.06, so you'll attache the jumper wire from the Rx Pin (D1)\non the FT232H board here. Finally, the GND wire should go to the GND Pin on the NRF52DK. When you're\ndone, your wiring should look like this:",
"title": "Setup Nordic Semiconductor NRF52DK"
},
{
@@ -482,7 +482,7 @@
},
{
"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 Micro-USB cable to connect the board and the computer.\n\n\nHave a computer to build a Mynewt application and connect to your board over U
SB.\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 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 successfully created.\n $ cd myproj\n $ n
ewt 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\nproject.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\n\nCreate a Target for the Bootloader\n\n\nYou need to create two targets, one for the bootloader and one
for the Blinky application.\n\n\n\nRun the following \nnewt target\n commands, from your project directory (ex. ~/dev/myproj), to create a bootloader target for the Arduino Zero Pro board. 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 a Arduino Zero Pro board, replace \nBSP_ARDUINO_ZERO_PRO\n with \nBSP_ARDUINO_ZERO\n in the last \nne
wt target set\n command.\n\n\nThese commands perform the following:\n\n\n\n\nCreate a target named \narduino_boot\n for the Arduino Zero Bootloader. \n\n\nSet the application for the \narduino_boot\n target to the default Apache Mynewt\n bootloader (\n@apache-mynewt-core/apps/boot\n)\n\n\nSet the board support package for the target to\n \n@mynewt_arduino_zero/hw/bsp/arduino_zero\n. This is a reference to the downloaded\n Arduino Zero support from Github.\n\n\nUse the \"optimized\" build profile for the \narduino_boot\n target. This\n instructs Newt to generate smaller and more efficient code for this target.\n This setting is necessary due to the bootloader's strict size constraints.\n\n\nSets the system configuration setting for Board Support Package to support the Arduino Zero Pro. \n\n\n\n\nSee the \nConcepts\n section for more information on setting options.\n\n\n\nCreate a Target for the Blinky Application\n\n\nRun the following \nnewt target\n commands to cr
eate your Blinky application target. We name the application target \narduino_blinky\n.\n\n\n$ newt target create arduino_blinky\nTarget targets/arduino_blinky successfully created\n$ newt target set arduino_blinky app=apps/blinky\nTarget targets/arduino_blinky successfully set target.app to apps/blinky\n$ newt target set arduino_blinky bsp=@mynewt_arduino_zero/hw/bsp/arduino_zero\nTarget targets/arduino_blinky successfully set target.bsp to @mynewt_arduino_zero/hw/bsp/arduino_zero\n$ newt target set arduino_blinky build_profile=debug\nTarget targets/arduino_blinky successfully set target.build_profile to debug\n$ newt target set arduino_blinky 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 a Arduino Zero Pro board, replace \nBSP_ARDUINO_ZERO_PRO\n with \nBSP_ARDUINO_ZERO\n in the last \nnewt target set\n command.\n\n\n\n\nBuild the Bootloader\n\n\nRun
the \nnewt build arduino_boot\n command to build a bootloader for your arduino board:\n\n\n$ newt build arduino_boot\nBuilding target targets/arduino_boot\nCompiling bin/targets/arduino_boot/generated/src/arduino_boot-sysinit-app.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c\nCompiling bin/targets/arduino_boot/generated/src/arduino_boot-sysflash.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c\nCompiling repos/apache-mynewt-core/apps/boot/src/boot.c\nCompiling repos/apache-mynewt-core/crypto/mbedtls/src/arc4.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/loader.c\nCompiling repos/apache-mynewt-core/crypto/mbedtls/src/aes.c\n\n ....\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bi
n/targets/arduino_boot/app/apps/boot/boot.elf\nTarget successfully built: targets/arduino_boot\n\n\n\n\n\n\n\nBuild the Blinky Application\n\n\nRun the \nnewt build arduino_blinky\n command to build your Blinky application image:\n\n\n$ newt build arduino_blinky\nBuilding target targets/arduino_blinky\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c\nCompiling apps/blinky/src/main.c\nCompiling repos/mynewt_arduino_zero/hw/mcu/atmel/samd21xx/src/sam0/drivers/i2s/i2s.c\nCompiling repos/mynewt_arduino_zero/hw/bsp/arduino_zero/src/hal_bsp.c\nCompiling repos/mynewt_arduino_zero/hw/mcu/atmel/samd21xx/src/sam0/drivers/i2s/i2s_callback.c\nCompiling repos/mynewt_arduino_zero/hw/mcu/atmel/samd21xx/src/sam0/drivers/nvm/nvm.c\n\n ...\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.elf\nTarget successfully built: targets/arduino_blinky\n\n\n\n\n\n\n\nConnect to the Board\n\n\nConnect your
computer to the Arduino Zero (from now on we'll call this the\ntarget) with a Micro-USB cable through the Programming Port as shown below.\nMynewt will load the image onto the board and debug the target through this port. You should see a\nlittle green LED come on. That means the board has power.\n\n\nNo external debugger is required. The Arduino Zero comes with an internal\ndebugger that can be accessed by Mynewt.\n\n\nThe images below show the Arduino Zero Programming Port.\n\n\n\n\n\n\n\n\nLoad the Bootloader onto the Board\n\n\nRun the \nnewt load arduino_boot\n command to load the bootloader onto your board:\n\n\n$ newt load arduino_boot\nLoading bootloader\n$\n\n\n\n\n\nThe bootloader is loaded onto your board succesfully when the \nnewt load\n command returns to the command prompt with no messages. You can proceed to load and run your Blinky application image (See \nRun the Blinky Application\n).\n\n\nIf the \nnewt load\n command outputs the following error messages, you wi
ll need to erase your board.\n\n\n$ newt load arduino_boot -v\nLoading bootloader\nError: Downloading ~/dev/arduino_zero/bin/targets/arduino_boot/app/apps/boot/boot.elf.bin to 0x0\nOpen On-Chip Debugger 0.9.0 (2015-11-15-05:39)\nLicensed under GNU GPL v2\nFor bug reports, read\n http://openocd.org/doc/doxygen/bugs.html\nInfo : only one transport option; autoselect \nswd\n\nadapter speed: 500 kHz\nadapter_nsrst_delay: 100\ncortex_m reset_config sysresetreq\nInfo : CMSIS-DAP: SWD Supported\nInfo : CMSIS-DAP: JTAG Supported\nInfo : CMSIS-DAP: Interface Initialised (SWD)\nInfo : CMSIS-DAP: FW Version = 01.1F.0118\nInfo : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 1 TDO = 1 nTRST = 0 nRESET = 1\nInfo : CMSIS-DAP: Interface ready\nInfo : clock speed 500 kHz\nInfo : SWD IDCODE 0x0bc11477\nInfo : at91samd21g18.cpu: hardware has 4 breakpoints, 2 watchpoints\nError: Target not halted\n\n\n\n\n\n\nTo erase your board, start a debug session and enter the highlighted commands at the \n(gdb)\n prompts
:\n\n\n$ newt debug arduino_blinky\n(gdb) mon at91samd chip-erase\nchip erased\nchip erased\n(gdb) x/32wx 0\n0x0: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x10: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x20: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x30: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x40: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x50: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x60: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x70: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n(gdb) q\n\n\n\n\n\n\nRun the \nnewt load arduino_boot\n command again after erasing the board. \n\n\n Reminder if you are using Docker: \n When working with actual hardware, remember that each board has an ID. If you swap boards and do not refresh the USB Device Filter on the VirtualBox UI, the ID might be stale and the Docker instance may not be able to see the board correctly. For example, you may see an error message like \nError: un
able to find CMSIS-DAP device\n when you try to load or run an image on the board. In that case, you need to click on the USB link in VirtualBox UI, remove the existing USB Device Filter (e.g. \"Atmel Corp. EDBG CMSIS-DAP[0101]\") by clicking on the \"Removes selected USB filter\" button, and add a new filter by clicking on the \"Adds new USB filter\" button.\n\n\n\n\nRun the Blinky Application\n\n\nAfter you load the bootloader successfully onto your board, you can load and run the Blinky application. \n\n\nRun the \nnewt run arduino_blinky 0.0.0\n 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. \n\n\n$ newt run arduino_blinky 0.0.0\nApp image succesfully generated: ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.img\nLoading app image into slot 1\n[~/dev/myproj/repos/mynewt_arduino_zero/hw/bsp/arduino_zero/arduino_zero_debug.sh ~/dev/myproj/repos/mynewt_arduin
o_zero/hw/bsp/arduino_zero ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky]\nOpen On-Chip Debugger 0.9.0 (2015-11-15-13:10)\nLicensed under GNU GPL v2\nFor bug reports, read\nhttp://openocd.org/doc/doxygen/bugs.html\nInfo : only one transport option; autoselect \nswd\n\nadapter speed: 500 kHz\nadapter_nsrst_delay: 100\ncortex_m reset_config sysresetreq\nInfo : CMSIS-DAP: SWD Supported\nInfo : CMSIS-DAP: JTAG Supported\nInfo : CMSIS-DAP: Interface Initialised (SWD)\nInfo : CMSIS-DAP: FW Version = 01.1F.0118\nInfo : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 1 TDO = 1 nTRST = 0 nRESET = 1\nInfo : CMSIS-DAP: Interface ready\nInfo : clock speed 500 kHz\nInfo : SWD IDCODE 0x0bc11477\nInfo : at91samd21g18.cpu: hardware has 4 breakpoints, 2 watchpoints\ntarget state: halted\ntarget halted due to debug-request, current mode: Thread \nxPSR: 0x21000000 pc: 0x0000fca6 psp: 0x20002408\nGNU gdb (GNU Tools for ARM Embedded Processors) 7.8.0.20150604-cvs\nCopyright (C) 2014 Free Software Fo
undation, Inc.\nLicense GPLv3+: GNU GPL version 3 or later \nhttp://gnu.org/licenses/gpl.html\n\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law. Type \nshow copying\n\nand \nshow warranty\n for details.\nThis GDB was configured as \n--host=x86_64-apple-darwin10 --target=arm-none-eabi\n.\nType \nshow configuration\n for configuration details.\nFor bug reporting instructions, please see:\n\nhttp://www.gnu.org/software/gdb/bugs/\n.\nFind the GDB manual and other documentation resources online at:\n\nhttp://www.gnu.org/software/gdb/documentation/\n.\nFor help, type \nhelp\n.\nType \napropos word\n to search for commands related to \nword\n...\nReading symbols from ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.elf...(no debugging symbols found)...done.\nInfo : accepting \ngdb\n connection on tcp/3333\nInfo : SAMD MCU: SAMD21G18A (256KB Flash, 32KB RAM)\n0x0000fca6 in os_tick_idle ()\ntarget state:
halted\ntarget halted due to debug-request, current mode: Thread \nxPSR: 0x21000000 pc: 0x000000b8 msp: 0x20008000\ntarget state: halted\ntarget halted due to debug-request, current mode: Thread \nxPSR: 0x21000000 pc: 0x000000b8 msp: 0x20008000\n(gdb) r\nThe \nremote\n target does not support \nrun\n. Try \nhelp target\n or \ncontinue\n.\n(gdb) c\nContinuing.\n\n\n\n\n\n\n\nNOTE:\n 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.\n\n\nIf you want the image to run without the debugger connected, simply quit the\ndebugger and restart the board. The image you programmed will come up and run on \nthe Arduino on the next boot! \n\n\n\n\nWatch the LED Blink\n\n\nCongratulations! You have created an Mynewt application running on the\nArduino Zero. The LED right next to the power LED should be blinking. It is toggled \nby one task running on the Mynewt OS.
\n\n\nWe have more fun tutorials for you to get your hands dirty. Be bold and try other \nBlinky-like \ntutorials\n or try enabling additional functionality \nsuch as \nremote comms\n on the current board.\n\n\nIf you see anything missing or want to send us feedback, please do so by signing up for \nappropriate mailing lists on our \nCommunity Page\n.\n\n\nKeep on hacking and blinking!",
+ "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 M0 Pro board, replace \nBSP_ARDUINO_ZERO_PRO\n with \nBSP_ARDUINO_ZERO\n in the last \
nnewt target set\n command.\n\n\nThese commands perform the following:\n\n\n\n\nCreate a target named \narduino_boot\n for the Arduino Zero Bootloader. \n\n\nSet the application for the \narduino_boot\n target to the default Apache Mynewt\n bootloader (\n@apache-mynewt-core/apps/boot\n)\n\n\nSet the board support package for the target to\n \n@mynewt_arduino_zero/hw/bsp/arduino_zero\n. This is a reference to the downloaded\n Arduino Zero support from Github.\n\n\nUse the \"optimized\" build profile for the \narduino_boot\n target. This\n instructs Newt to generate smaller and more efficient code for this target.\n This setting is necessary due to the bootloader's strict size constraints.\n\n\nSets the system configuration setting for Board Support Package to support the Arduino Zero Pro. \n\n\n\n\nSee the \nConcepts\n section for more information on setting options.\n\n\n\nCreate a Target for the Blinky Application\n\n\nRun the following \nnewt target\n commands to
create the Blinky application target. We name the application target \narduino_blinky\n.\n\n\n$ newt target create arduino_blinky\nTarget targets/arduino_blinky successfully created\n$ newt target set arduino_blinky app=apps/blinky\nTarget targets/arduino_blinky successfully set target.app to apps/blinky\n$ newt target set arduino_blinky bsp=@mynewt_arduino_zero/hw/bsp/arduino_zero\nTarget targets/arduino_blinky successfully set target.bsp to @mynewt_arduino_zero/hw/bsp/arduino_zero\n$ newt target set arduino_blinky build_profile=debug\nTarget targets/arduino_blinky successfully set target.build_profile to debug\n$ newt target set arduino_blinky 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 a Arduino Zero Pro board, replace \nBSP_ARDUINO_ZERO_PRO\n with \nBSP_ARDUINO_ZERO\n in the last \nnewt target set\n command.\n\n\n\n\nBuild the Bootloader\n\n\nRu
n the \nnewt build arduino_boot\n command to build the bootloader:\n\n\n$ newt build arduino_boot\nBuilding target targets/arduino_boot\nCompiling bin/targets/arduino_boot/generated/src/arduino_boot-sysinit-app.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c\nCompiling bin/targets/arduino_boot/generated/src/arduino_boot-sysflash.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c\nCompiling repos/apache-mynewt-core/apps/boot/src/boot.c\nCompiling repos/apache-mynewt-core/crypto/mbedtls/src/arc4.c\nCompiling repos/apache-mynewt-core/boot/bootutil/src/loader.c\nCompiling repos/apache-mynewt-core/crypto/mbedtls/src/aes.c\n\n ....\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bin/targets/arduino_b
oot/app/apps/boot/boot.elf\nTarget successfully built: targets/arduino_boot\n\n\n\n\n\n\n\nBuild the Blinky Application\n\n\nRun the \nnewt build arduino_blinky\n command to build the Blinky application image:\n\n\n$ newt build arduino_blinky\nBuilding target targets/arduino_blinky\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c\nCompiling apps/blinky/src/main.c\nCompiling repos/mynewt_arduino_zero/hw/mcu/atmel/samd21xx/src/sam0/drivers/i2s/i2s.c\nCompiling repos/mynewt_arduino_zero/hw/bsp/arduino_zero/src/hal_bsp.c\nCompiling repos/mynewt_arduino_zero/hw/mcu/atmel/samd21xx/src/sam0/drivers/i2s/i2s_callback.c\nCompiling repos/mynewt_arduino_zero/hw/mcu/atmel/samd21xx/src/sam0/drivers/nvm/nvm.c\n\n ...\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.elf\nTarget successfully built: targets/arduino_blinky\n\n\n\n\n\n\n\nConnect to the Board\n\n\nConnect your computer to the Ardu
ino Zero (from now on we'll call this the\ntarget) with a Micro-USB cable through the Programming Port as shown below.\nMynewt will load the image onto the board and debug the target through this port. You should see a\ngreen LED come on that indicates the board has power.\n\n\nNo external debugger is required. The Arduino Zero comes with an internal\ndebugger that can be accessed by Mynewt.\n\n\nThe images below show the Arduino Zero Programming Port.\n\n\n\n\n\n\n\n\nLoad the Bootloader onto the Board\n\n\nRun the \nnewt load arduino_boot\n command to load the bootloader onto the board:\n\n\n$ newt load arduino_boot\nLoading bootloader\n$\n\n\n\n\n\nThe bootloader is loaded onto your board succesfully when the \nnewt load\n command returns to the command prompt after the \nLoading bootloader\n status message. You can proceed to load and run your Blinky application image (See \nRun the Blinky Application\n).\n\n\nIf the \nnewt load\n command outputs the following error messages,
you will need to erase the board.\n\n\n$ newt load arduino_boot -v\nLoading bootloader\nError: Downloading ~/dev/myproj/bin/targets/arduino_boot/app/apps/boot/boot.elf.bin to 0x0\nOpen On-Chip Debugger 0.9.0 (2015-11-15-05:39)\nLicensed under GNU GPL v2\nFor bug reports, read\n http://openocd.org/doc/doxygen/bugs.html\nInfo : only one transport option; autoselect \nswd\n\nadapter speed: 500 kHz\nadapter_nsrst_delay: 100\ncortex_m reset_config sysresetreq\nInfo : CMSIS-DAP: SWD Supported\nInfo : CMSIS-DAP: JTAG Supported\nInfo : CMSIS-DAP: Interface Initialised (SWD)\nInfo : CMSIS-DAP: FW Version = 01.1F.0118\nInfo : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 1 TDO = 1 nTRST = 0 nRESET = 1\nInfo : CMSIS-DAP: Interface ready\nInfo : clock speed 500 kHz\nInfo : SWD IDCODE 0x0bc11477\nInfo : at91samd21g18.cpu: hardware has 4 breakpoints, 2 watchpoints\nError: Target not halted\n\n\n\n\n\n\nTo erase your board, start a debug session and enter the highlighted commands at the \n(gdb)\n prompts
:\n\n\n$ newt debug arduino_blinky\n(gdb) mon at91samd chip-erase\nchip erased\nchip erased\n(gdb) x/32wx 0\n0x0: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x10: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x20: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x30: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x40: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x50: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x60: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n0x70: 0xffffffff 0xffffffff 0xffffffff 0xffffffff\n(gdb) q\n\n\n\n\n\n\nRun the \nnewt load arduino_boot\n command again after erasing the board. \n\n\n Reminder if you are using Docker: \n When working with actual hardware, remember that each board has an ID. If you swap boards and do not refresh the USB Device Filter on the VirtualBox UI, the ID might be stale and the Docker instance may not be able to see the board correctly. For example, you may see an error message like \nError: un
able to find CMSIS-DAP device\n when you try to load or run an image on the board. In that case, you need to click on the USB link in VirtualBox UI, remove the existing USB Device Filter (e.g. \"Atmel Corp. EDBG CMSIS-DAP[0101]\") by clicking on the \"Removes selected USB filter\" button, and add a new filter by clicking on the \"Adds new USB filter\" button.\n\n\n\n\nRun the Blinky Application\n\n\nAfter you load the bootloader successfully onto your board, you can load and run the Blinky application. \n\n\nRun the \nnewt run arduino_blinky 1.0.0\n 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. \n\n\n$ newt run arduino_blinky 1.0.0\nApp image succesfully generated: ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.img\nLoading app image into slot 1\n[~/dev/myproj/repos/mynewt_arduino_zero/hw/bsp/arduino_zero/arduino_zero_debug.sh ~/dev/myproj/repos/mynewt_arduin
o_zero/hw/bsp/arduino_zero ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky]\nOpen On-Chip Debugger 0.9.0 (2015-11-15-13:10)\nLicensed under GNU GPL v2\nFor bug reports, read\nhttp://openocd.org/doc/doxygen/bugs.html\nInfo : only one transport option; autoselect \nswd\n\nadapter speed: 500 kHz\nadapter_nsrst_delay: 100\ncortex_m reset_config sysresetreq\nInfo : CMSIS-DAP: SWD Supported\nInfo : CMSIS-DAP: JTAG Supported\nInfo : CMSIS-DAP: Interface Initialised (SWD)\nInfo : CMSIS-DAP: FW Version = 01.1F.0118\nInfo : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 1 TDO = 1 nTRST = 0 nRESET = 1\nInfo : CMSIS-DAP: Interface ready\nInfo : clock speed 500 kHz\nInfo : SWD IDCODE 0x0bc11477\nInfo : at91samd21g18.cpu: hardware has 4 breakpoints, 2 watchpoints\ntarget state: halted\ntarget halted due to debug-request, current mode: Thread \nxPSR: 0x21000000 pc: 0x0000fca6 psp: 0x20002408\nGNU gdb (GNU Tools for ARM Embedded Processors) 7.8.0.20150604-cvs\nCopyright (C) 2014 Free Software Fo
undation, Inc.\nLicense GPLv3+: GNU GPL version 3 or later \nhttp://gnu.org/licenses/gpl.html\n\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law. Type \nshow copying\n\nand \nshow warranty\n for details.\nThis GDB was configured as \n--host=x86_64-apple-darwin10 --target=arm-none-eabi\n.\nType \nshow configuration\n for configuration details.\nFor bug reporting instructions, please see:\n\nhttp://www.gnu.org/software/gdb/bugs/\n.\nFind the GDB manual and other documentation resources online at:\n\nhttp://www.gnu.org/software/gdb/documentation/\n.\nFor help, type \nhelp\n.\nType \napropos word\n to search for commands related to \nword\n...\nReading symbols from ~/dev/myproj/bin/targets/arduino_blinky/app/apps/blinky/blinky.elf...(no debugging symbols found)...done.\nInfo : accepting \ngdb\n connection on tcp/3333\nInfo : SAMD MCU: SAMD21G18A (256KB Flash, 32KB RAM)\n0x0000fca6 in os_tick_idle ()\ntarget state:
halted\ntarget halted due to debug-request, current mode: Thread \nxPSR: 0x21000000 pc: 0x000000b8 msp: 0x20008000\ntarget state: halted\ntarg
<TRUNCATED>