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/05/05 22:31:07 UTC
[1/7] incubator-mynewt-site git commit: changed runtimeinc to
runtimeco in docs, updated install instructions for linux ,
blinky for stm32F4-discovery
Repository: incubator-mynewt-site
Updated Branches:
refs/heads/asf-site 26592f06f -> ea2670d63
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/sitemap.xml
----------------------------------------------------------------------
diff --git a/latest/sitemap.xml b/latest/sitemap.xml
index b635405..bdc2916 100644
--- a/latest/sitemap.xml
+++ b/latest/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,7 +13,7 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -22,7 +22,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -30,7 +30,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -38,7 +38,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -46,7 +46,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -54,7 +54,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -62,7 +62,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -71,7 +71,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -83,7 +83,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -123,19 +123,19 @@
<url>
<loc>http://mynewt.apache.org/faq/go_env/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/os/tutorials/pics/stm32f4_disc.jpg
----------------------------------------------------------------------
diff --git a/os/tutorials/pics/stm32f4_disc.jpg b/os/tutorials/pics/stm32f4_disc.jpg
new file mode 100755
index 0000000..cbed05f
Binary files /dev/null and b/os/tutorials/pics/stm32f4_disc.jpg differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/sitemap.xml
----------------------------------------------------------------------
diff --git a/sitemap.xml b/sitemap.xml
index 650f503..345840d 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,13 +13,13 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/pages/securitybullets/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -28,7 +28,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -36,7 +36,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -44,7 +44,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -52,7 +52,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -60,7 +60,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -68,7 +68,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -77,7 +77,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -89,7 +89,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -129,13 +129,13 @@
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/v0_9_0/os/tutorials/pics/stm32f4_disc.jpg
----------------------------------------------------------------------
diff --git a/v0_9_0/os/tutorials/pics/stm32f4_disc.jpg b/v0_9_0/os/tutorials/pics/stm32f4_disc.jpg
new file mode 100755
index 0000000..cbed05f
Binary files /dev/null and b/v0_9_0/os/tutorials/pics/stm32f4_disc.jpg differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/v0_9_0/sitemap.xml
----------------------------------------------------------------------
diff --git a/v0_9_0/sitemap.xml b/v0_9_0/sitemap.xml
index 650f503..345840d 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-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,13 +13,13 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/pages/securitybullets/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -28,7 +28,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -36,7 +36,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -44,7 +44,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -52,7 +52,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -60,7 +60,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -68,7 +68,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -77,7 +77,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -89,7 +89,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -129,13 +129,13 @@
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
[2/7] incubator-mynewt-site git commit: changed runtimeinc to
runtimeco in docs, updated install instructions for linux ,
blinky for stm32F4-discovery
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/newt/install/newt_linux/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/install/newt_linux/index.html b/latest/newt/install/newt_linux/index.html
index ed4c63e..d177b3f 100644
--- a/latest/newt/install/newt_linux/index.html
+++ b/latest/newt/install/newt_linux/index.html
@@ -213,7 +213,7 @@
- <li ><a href="../../../os/get_started/native_tools/">Native install Option</a>
+ <li ><a href="../../../os/get_started/native_install_intro/">Native Install Option</a>
<ul>
@@ -239,6 +239,14 @@
<li >
+ <a href="../../../os/get_started/native_tools/">Install Native Toolchain</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../../../os/get_started/cross_tools/">Install Cross Tools for ARM</a>
</li>
@@ -379,7 +387,7 @@
- <li>» <a href="../../../os/get_started/native_tools/">Native install Option</a></li>
+ <li>» <a href="../../../os/get_started/native_install_intro/">Native Install Option</a></li>
@@ -392,13 +400,13 @@
</div>
<h2 id="installing-newt-on-linux">Installing Newt on Linux</h2>
-<p>You can install the latest stable release (1.0.0) of newt from a Debian binary package (amd64) or from a Debian source package. This page shows you how to:</p>
+<p>You can install the latest stable release (1.0.0) of the newt tool from a Debian binary package (amd64) or from a Debian source package. This page shows you how to:</p>
<ol>
<li>Set up your computer to retrieve Debian packages from the runtimeco debian package repository.</li>
<li>Install the latest stable release version of newt from a Debian binary package. </li>
<li>Install the latest stable release version of newt from a Debian source package.</li>
</ol>
-<p>If you are running on an amd64 platform, we recommend that you install from the binary package.</p>
+<p>If you are installing on an amd64 platform, we recommend that you install from the binary package.</p>
<p><strong>Note:</strong> See <a href="../../../faq/go_env">Setting Up an Go Environment to Contribute to Newt and Newtmgr Tools</a> if you want to: </p>
<ul>
<li>Use the newt tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.</li>
@@ -406,55 +414,50 @@
</ul>
<p><br></p>
<h3 id="setting-up-your-computer-to-get-packages-from-runtimeco">Setting Up Your Computer to Get Packages from runtimeco</h3>
-<p>The newt Debian packages are stored in a private repository on <strong>https://github/runtimeco/debian-mynewt</strong>. </p>
-<p><strong>Note:</strong> You will only need to perform these steps only once on your computer.
-The following steps must be performed on your computer:</p>
+<p>The newt Debian packages are stored in a private repository on <strong>https://github/runtimeco/debian-mynewt</strong>. The following steps must be performed on your computer to retreive packages from the repository:</p>
+<p><strong>Note:</strong> You only need to perform this setup once on your computer.</p>
<ol>
-<li>Add the <code>apt-transport-https</code> package to use HTTPS to retrieve packages. </li>
+<li>Install the <code>apt-transport-https</code> package to use HTTPS to retrieve packages. </li>
<li>Download the public key for the runtimeco debian repository and import the key into the apt keychain.</li>
<li>Add the repository for the binary and source packages to the apt source list.</li>
</ol>
<p><br>
-Add the apt-transport-https package:</p>
+Install the apt-transport-https package:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get update
$sudo apt-get install apt-transport-https
</pre></div>
<p><br></p>
-<p>Download the public key for the runtimeco apt repo (<strong>Note:</strong> There is <code>-</code> after the add):</p>
+<p>Download the public key for the runtimeco apt repo (<strong>Note:</strong> There is a <code>-</code> after <code>apt-key add</code>):</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -
</pre></div>
<p><br></p>
-<p>Add the repository for the binary and source packages to the apt source list:</p>
+<p>Add the repository for the binary and source packages to the <code>mynewt.list</code> apt source list file.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo -s
[sudo] password for <user>:
root$ cat > /etc/apt/sources.list.d/mynewt.list <<EOF
deb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
deb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
EOF
+root$exit
</pre></div>
+<p><strong>Note:</strong> Do not forget to exit the root shell.</p>
<p><br>
-Check the content of the file:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">root$more /etc/apt/sources.list.d//mynewt.list
+Verify the content of the source list file:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$more /etc/apt/sources.list.d/mynewt.list
deb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
deb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
</pre></div>
<p><br> </p>
-<p>Exit the root shell:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">root$exit
-</pre></div>
-
-
-<p><br></p>
<h3 id="installing-the-latest-release-of-newt-from-a-binary-package">Installing the Latest Release of Newt from a Binary Package</h3>
-<p>For Linux amd64 platform, you can install the latest stable version (1.0.0) of newt from the newt Debian binary package:</p>
+<p>For Linux amd64 platforms, you can install the latest stable version (1.0.0) of newt from the newt Debian binary package:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get update
$sudo apt-get install newt
Reading package lists... Done
@@ -474,7 +477,7 @@ See <a href="#check">Checking the Installed Version of Newt</a> to verify that y
<p><br></p>
<h3 id="installing-the-latest-stable-release-of-newt-from-a-source-package">Installing the Latest Stable Release of Newt from a Source Package</h3>
<p>If you are running Linux on a different architecture, you can install the Debian source package for the latest stable release (1.0.0) of newt. The installation of the source package builds the newt binary and creates a Debian binary package that you then install.</p>
-<p><strong>Note</strong>: Newt version 1.0.0 has been tested on Linux amd64 platform. Version 1.0.0 does not build on the 32 bit platform but have been fixed for the next release.</p>
+<p><strong>Note</strong>: Newt version 1.0.0 has been tested on Linux amd64 platforms. Version 1.0.0 does not build on 32 bit platforms but have been fixed for the next release.</p>
<p><br></p>
<h4 id="installing-go-17">Installing Go 1.7</h4>
<p>You need Go version 1.7 or higher to build Newt version 1.0.0. Currently, the latest Go version that Ubuntu installs is 1.6. Run <code>go version</code> to check if you have Go 1.7 installed. </p>
@@ -522,9 +525,10 @@ W: Can't drop privileges for downloading as file 'newt_1.0.0-1.dsc'
</pre></div>
-<p><strong>Note:</strong> You can ignore the "Permission denied: warning message at the end of the command.</p>
+<p><strong>Note:</strong> You can ignore the "Permission denied" warning message at the end of the command.</p>
<p><br>
Install the newt binary package that is created from the source package:</p>
+<p><strong>Note:</strong> The file name for the binary package has the format: newt_1.0.0-1_<strong>arch</strong>.deb, where <strong>arch</strong> is a value that identifies your host architecture. </p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo dpkg -i newt_1.0.0-1_amd64.deb
Selecting previously unselected package newt.
(Reading database ... 252969 files and directories currently installed.)
@@ -547,7 +551,7 @@ Apache Newt (incubating) version: 1.0.0
</pre></div>
-<p><strong>Note:</strong> If you previously built newt from source and the output of <code>which newt</code> shows "$GOPATH/bin/newt", you will need to move "$GOPATH/bin" after "/usr/bin" in your $PATH and export your $PATH.</p>
+<p><strong>Note:</strong> If you previously built newt from source and the output of <code>which newt</code> shows "$GOPATH/bin/newt", you will need to move "$GOPATH/bin" after "/usr/bin" for your PATH environment variable and export it. </p>
<p><br>
Get information about newt:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt
@@ -621,8 +625,8 @@ Use "newt [command] --help" for more information about a command.
</li>
<li class="pull-right">
- <a href=../../../os/get_started/cross_tools/>
- Next: Install Cross Tools for ARM
+ <a href=../../../os/get_started/native_tools/>
+ Next: Install Native Toolchain
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/newt/install/newt_mac/index.html
----------------------------------------------------------------------
diff --git a/latest/newt/install/newt_mac/index.html b/latest/newt/install/newt_mac/index.html
index 4855bbb..e21390b 100644
--- a/latest/newt/install/newt_mac/index.html
+++ b/latest/newt/install/newt_mac/index.html
@@ -213,7 +213,7 @@
- <li ><a href="../../../os/get_started/native_tools/">Native install Option</a>
+ <li ><a href="../../../os/get_started/native_install_intro/">Native Install Option</a>
<ul>
@@ -239,6 +239,14 @@
<li >
+ <a href="../../../os/get_started/native_tools/">Install Native Toolchain</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../../../os/get_started/cross_tools/">Install Cross Tools for ARM</a>
</li>
@@ -379,7 +387,7 @@
- <li>» <a href="../../../os/get_started/native_tools/">Native install Option</a></li>
+ <li>» <a href="../../../os/get_started/native_install_intro/">Native Install Option</a></li>
@@ -550,9 +558,9 @@ Apache Newt (incubating) version: 1.0.0
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../../../os/get_started/native_tools/>
+ <a href=../../../os/get_started/native_install_intro/>
<span class="fa fa-arrow-left"></span>
- Previous: Native install Option
+ Previous: Native Install Option
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/newtmgr/install_linux/index.html
----------------------------------------------------------------------
diff --git a/latest/newtmgr/install_linux/index.html b/latest/newtmgr/install_linux/index.html
index a06f3fe..76e6b2a 100644
--- a/latest/newtmgr/install_linux/index.html
+++ b/latest/newtmgr/install_linux/index.html
@@ -373,7 +373,7 @@
</div>
<h2 id="installing-newtmgr-on-linux">Installing Newtmgr on Linux</h2>
-<p>You can install the latest stable release (1.0.0) of newtmgr from a Debian binary package (amd64) or from a Debian source package. This page shows you how to:</p>
+<p>You can install the latest stable release (1.0.0) of the newtmgr tool from a Debian binary package (amd64) or from a Debian source package. This page shows you how to:</p>
<ol>
<li>
<p>Set up your computer to retrieve Debian packages from the runtimeco debian package repository. </p>
@@ -384,7 +384,7 @@
</li>
<li>Install the latest stable release version of newtmgr from a Debian source package.</li>
</ol>
-<p>If you are running on an amd64 platform, we recommend that you install from the binary package.</p>
+<p>If you are installing on an amd64 platform, we recommend that you install from the binary package.</p>
<p><strong>Note:</strong> See <a href="../../faq/go_env">Setting Up an Go Environment to Contribute to Newt and Newtmgr Tools</a> if you want to: </p>
<ul>
<li>Use the newtmgr tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.</li>
@@ -392,55 +392,50 @@
</ul>
<p><br></p>
<h3 id="setting-up-your-computer-to-get-packages-from-runtimeco">Setting Up Your Computer to Get Packages from runtimeco</h3>
-<p>The newtmgr Debian packages are stored in a private repository on <strong>https://github/runtimeco/debian-mynewt</strong>. </p>
-<p><strong>Note</strong>: You will only need to perform these steps once on your computer. You can skip this step if you already set up your computer to access the runtimeco debian repository when you installed the newt tool. </p>
-<p>The following steps must be performed on your computer:</p>
+<p>The newtmgr Debian packages are stored in a private repository on <strong>https://github/runtimeco/debian-mynewt</strong>. You must set up the following on your computer to retreive packages from the repository:</p>
+<p><strong>Note</strong>: You only need to perform this setup once on your computer and you may have already done so when you installed the newt tool. </p>
<ol>
-<li>Add the <code>apt-transport-https</code> package to use HTTPS to retrieve packages. </li>
+<li>Install the <code>apt-transport-https</code> package to use HTTPS to retrieve packages. </li>
<li>Download the public key for the runtimeco debian repository and import the key into the apt keychain.</li>
<li>Add the repository for the binary and source packages to the apt source list.</li>
</ol>
<p><br>
-Add the apt-transport-https package:</p>
+Install the apt-transport-https package:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get update
$sudo apt-get install apt-transport-https
</pre></div>
<p><br></p>
-<p>Download the public key for the runtimeco apt repo (<strong>Note:</strong> There is <code>-</code> after the add):</p>
+<p>Download the public key for the runtimeco apt repo (<strong>Note:</strong> There is a <code>-</code> after <code>apt-key add</code>):</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -
</pre></div>
<p><br></p>
-<p>Add the repository for the binary and source packages to the apt source list:</p>
+<p>Add the repository for the binary and source packages to the <code>mynewt.list</code> apt source list file.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo -s
[sudo] password for <user>:
root$ cat > /etc/apt/sources.list.d/mynewt.list <<EOF
deb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
deb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
EOF
+root$exit
</pre></div>
+<p><strong>Note:</strong> Do not forget to exit the root shell.</p>
<p><br>
-Check the content of the file:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">root$more /etc/apt/sources.list.d//mynewt.list
+Verify the content of the source list file:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$more /etc/apt/sources.list.d/mynewt.list
deb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
deb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
</pre></div>
<p><br> </p>
-<p>Exit the root shell:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">root$exit
-</pre></div>
-
-
-<p><br></p>
<h3 id="installing-the-latest-release-of-newtmgr-from-a-binary-package">Installing the Latest Release of Newtmgr from a Binary Package</h3>
-<p>For Linux amd64 platform, you can install the latest stable version (1.0.0) of newtmgr from the newtmgr Debian binary package:</p>
+<p>For Linux amd64 platforms, you can install the latest stable version (1.0.0) of newtmgr from the newtmgr Debian binary package:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get update
$sudo apt-get install newtmgr
Reading package lists... Done
@@ -464,7 +459,7 @@ See <a href="#check">Checking the Installed Version of Newtmgr</a> to verify tha
<p><br></p>
<h3 id="installing-the-latest-stable-release-of-newtmgr-from-a-source-package">Installing the Latest Stable Release of Newtmgr from a Source Package</h3>
<p>If you are running Linux on a different architecture, you can install the Debian source package for the latest stable release (1.0.0) of newtmgr. The installation of the source package builds the newtmgr binary and creates a Debian binary package that you then install.</p>
-<p><strong>Note</strong>: Newtmgr version 1.0.0 has been tested on Linux amd64 platform. </p>
+<p><strong>Note</strong>: Newtmgr version 1.0.0 has been tested on Linux amd64 platforms. </p>
<p><br></p>
<h4 id="installing-go-17">Installing Go 1.7</h4>
<p>You need Go version 1.7 or higher to build Newtmgr version 1.0.0. Currently, the latest Go version that Ubuntu installs is 1.6. Run <code>go version</code> to check if you have Go 1.7 installed. </p>
@@ -506,12 +501,20 @@ dpkg-deb: building package 'newtmgr' in '../newtmgr_1.0.0-1_amd64.de
dpkg-genchanges: info: binary-only upload (no source code included)
dpkg-source --after-build newtmgr-1.0.0
dpkg-buildpackage: info: binary-only upload (no source included)
+W: Can't drop privileges for downloading as file 'newtmgr_1.0.0-1.dsc' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
</pre></div>
+<p><strong>Note:</strong> You can ignore the "Permission denied" warning message at the end of the command.</p>
<p><br>
Install the newtmgr binary package that is created from the source package:</p>
+<p><strong>Note:</strong> The file name for the binary package has the format: newtmgr_1.0.0-1_<strong>arch</strong>.deb, where <strong>arch</strong> is a value that identifies your host architecture.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo dpkg -i newtmgr_1.0.0-1_amd64.deb
+Selecting previously unselected package newtmgr.
+(Reading database ... 215099 files and directories currently installed.)
+Preparing to unpack newtmgr_1.0.0-1_amd64.deb ...
+Unpacking newtmgr (1.0.0-1) ...
+Setting up newtmgr (1.0.0-1) ...
</pre></div>
@@ -526,7 +529,7 @@ $which newtmgr
</pre></div>
-<p><strong>Note:</strong> If you previously built newtmgr from source and the output of <code>which newtmgr</code> shows "$GOPATH/bin/newtmgr", you will need to move "$GOPATH/bin" after "/usr/bin" in your $PATH and export your $PATH.</p>
+<p><strong>Note:</strong> If you previously built newtmgr from source and the output of <code>which newtmgr</code> shows "$GOPATH/bin/newtmgr", you will need to move "$GOPATH/bin" after "/usr/bin" for your PATH environment variable and export it.</p>
<p><br>
Get information about newtmgr:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newtmgr
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/os/get_started/cross_tools/index.html
----------------------------------------------------------------------
diff --git a/latest/os/get_started/cross_tools/index.html b/latest/os/get_started/cross_tools/index.html
index 85ec703..39323b4 100644
--- a/latest/os/get_started/cross_tools/index.html
+++ b/latest/os/get_started/cross_tools/index.html
@@ -213,7 +213,7 @@
- <li ><a href="../native_tools/">Native install Option</a>
+ <li ><a href="../native_install_intro/">Native Install Option</a>
<ul>
@@ -238,6 +238,14 @@
+ <li >
+ <a href="../native_tools/">Install Native Toolchain</a>
+ </li>
+
+
+
+
+
<li class="active">
<a href="./">Install Cross Tools for ARM</a>
</li>
@@ -379,7 +387,7 @@
- <li>» <a href="../native_tools/">Native install Option</a></li>
+ <li>» <a href="../native_install_intro/">Native Install Option</a></li>
@@ -525,9 +533,9 @@ http://openocd.org/doc/doxygen/bugs.html
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../../../newt/install/newt_linux/>
+ <a href=../native_tools/>
<span class="fa fa-arrow-left"></span>
- Previous: Install Newt on Linux
+ Previous: Install Native Toolchain
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/os/get_started/docker/index.html
----------------------------------------------------------------------
diff --git a/latest/os/get_started/docker/index.html b/latest/os/get_started/docker/index.html
index f5cbfbf..43aae96 100644
--- a/latest/os/get_started/docker/index.html
+++ b/latest/os/get_started/docker/index.html
@@ -213,7 +213,7 @@
- <li ><a href="../native_tools/">Native install Option</a>
+ <li ><a href="../native_install_intro/">Native Install Option</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/os/get_started/get_started/index.html
----------------------------------------------------------------------
diff --git a/latest/os/get_started/get_started/index.html b/latest/os/get_started/get_started/index.html
index 96eca2f..d94d437 100644
--- a/latest/os/get_started/get_started/index.html
+++ b/latest/os/get_started/get_started/index.html
@@ -213,7 +213,7 @@
- <li ><a href="../native_tools/">Native install Option</a>
+ <li ><a href="../native_install_intro/">Native Install Option</a>
</li>
@@ -391,8 +391,8 @@
</li>
<li class="pull-right">
- <a href=../native_tools/>
- Next: Native install Option
+ <a href=../native_install_intro/>
+ Next: Native Install Option
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/os/get_started/native_install_intro/index.html
----------------------------------------------------------------------
diff --git a/latest/os/get_started/native_install_intro/index.html b/latest/os/get_started/native_install_intro/index.html
new file mode 100644
index 0000000..4f42d5a
--- /dev/null
+++ b/latest/os/get_started/native_install_intro/index.html
@@ -0,0 +1,476 @@
+<!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/get_started/native_install_intro/"> -->
+ <link rel="shortcut icon" href="../../../img/favicon.ico">
+
+ <title>toc - Apache Mynewt</title>
+
+ <link href="../../../css/bootstrap-3.0.3.min.css" rel="stylesheet">
+ <link rel="stylesheet" href="../../../css/highlight.css">
+ <link href="../../../css/base.css" rel="stylesheet">
+ <link href="../../../css/custom.css" rel="stylesheet">
+ <link href="../../../css/v2.css" rel="stylesheet">
+ <link href="https://fonts.googleapis.com/css?family=Lato" rel="stylesheet">
+ <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css">
+ <link href="../../../extra.css" rel="stylesheet">
+
+ <!-- HTML5 shim and Respond.js IE8 support of HTML5 elements and media queries -->
+ <!--[if lt IE 9]>
+ <script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script>
+ <script src="https://oss.maxcdn.com/libs/respond.js/1.3.0/respond.min.js"></script>
+ <![endif]-->
+
+
+ <script>
+ (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
+ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
+ m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
+ })(window,document,'script','//www.google-analytics.com/analytics.js','ga');
+
+ ga('create', 'UA-72162311-1', 'auto');
+ ga('send', 'pageview');
+ </script>
+
+ </head>
+
+
+ <body class="toc">
+
+
+ <div class="container">
+ <div class="row v2-main-banner">
+ <a class="logo-cell" href="/">
+ <img class="logo" src="/img/logo.png">
+ </a>
+ <div class="tagline-cell">
+ <h4 class="tagline">An OS to build, deploy and securely manage billions of devices</h4>
+ </div>
+ <div class="news-cell">
+ <div class="well">
+ <h4>Latest News:</h4> <a href="/download">Apache Mynewt 1.0.0</a> released (March 22, 2017)
+ </div>
+ </div>
+ </div>
+</div>
+
+
+
+
+
+
+
+
+<nav id="navbar" class="navbar navbar-inverse affix-top" data-spy="affix" data-offset-top="150" role="navigation">
+ <div class="container">
+ <!-- Collapsed navigation -->
+ <div class="navbar-header">
+ <!-- Expander button -->
+ <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
+ <span class="sr-only">Toggle navigation</span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ </button>
+
+ </div>
+
+ <!-- Expanded navigation -->
+ <div class="navbar-collapse collapse">
+ <!-- Main navigation -->
+ <ul class="nav navbar-nav navbar-right">
+ <li
+ class=""
+>
+ <a href="/"><i class="fa fa-home" style="font-size: larger;"></i></a>
+ </li>
+ <li
+ class="important"
+>
+ <a href="/quick-start/">Quick Start</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/about/">About</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/talks/">Talks</a>
+ </li>
+ <li
+ class="active"
+>
+ <a href="/latest/os/introduction">Documentation</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/download/">Download</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/community/">Community</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/events/">Events</a>
+ </li>
+ </ul>
+
+ <!-- Search, Navigation and Repo links -->
+ <ul class="nav navbar-nav navbar-right">
+
+ </ul>
+ </div>
+ </div>
+</nav>
+
+
+
+ <div class="container">
+
+ <div class="row">
+ <div class="col-md-3 v2-sidebar sidebar-container"><div id="docSidebar" class="hidden-print" role="complementary">
+ <div class="top">
+ <div role="search">
+ <form id="rtd-search-form" class="wy-form" action="../../../search.html" method="get">
+ <div class="form-group">
+ <input type="text" name="q" class="form-control" placeholder="Search documentation" />
+ </div>
+ </form>
+ </div>
+ </div>
+ <ul class="toc-nav">
+ <li class="doc-version">
+<select class="form-control" onchange="if (this.value) window.location.href=this.value">
+
+ <option
+ value="/develop/os/introduction"
+ selected="selected"
+ >
+ Version: develop (latest)
+ </option>
+
+ <option
+ value="/v0_9_0/os/introduction"
+
+ >
+ Version: 0.9.0
+ </option>
+
+</select>
+</li>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ <li ><a href="../../introduction/">Mynewt Documentation</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../get_started/">Basic Setup</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li class="active"><a href="./">Native Install Option</a>
+
+
+ <ul>
+
+
+
+
+
+ <li >
+ <a href="../../../newt/install/newt_mac/">Install Newt on Mac</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../../newt/install/newt_linux/">Install Newt on Linux</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../native_tools/">Install Native Toolchain</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../cross_tools/">Install Cross Tools for ARM</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../docker/">Docker Container Option</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../project_create/">Create Your First Project</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../serial_access/">Serial Port Setup</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../vocabulary/">Concepts</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../tutorials/tutorials/">Tutorials</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../os_user_guide/">OS User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../../network/ble/ble_intro/
+">BLE User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../newt/newt_intro/">Newt Tool Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../newtmgr/overview/">Newt Manager Guide</a>
+
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../../faq/go_env/
+">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="../get_started/">Basic Setup</a></li>
+
+
+
+ <li>» Native Install Option</li>
+
+
+
+
+
+ </ul>
+</div>
+ </div>
+
+ <h1 id="native-installation">Native Installation</h1>
+<p>This section shows you how to install tools on Mac OS and Linux platforms to develop, build, run, and debug Mynewt OS applications. You can build Mynewt OS applications to run as a native application on your computer or to run on your target board. These tools include:</p>
+<ul>
+<li>
+<p>Newt tool - Tool to create, build, load, and debug a mynewt target.</p>
+<ul>
+<li>See <a href="../../../newt/install/newt_mac/">Installing the Newt Tool on Mac OS</a> to install on Mac OS.</li>
+<li>See <a href="../../../newt/install/newt_linux/">Installing the Newt Tool on Linux</a> to install on Linux.</li>
+</ul>
+</li>
+</ul>
+<p><br></p>
+<ul>
+<li>
+<p>Native toolchain - Native toolchain to build and run Mynewt OS as a native application on your computer.
+ (See <a href="/os/get_started/native_install.md">Installing Native Toolchain</a>). </p>
+</li>
+<li>
+<p>Cross toolchain for ARM - Cross toolchain for ARM to build and run a Mynewt OS application on a target board
+ (See <a href="../cross_tools/">Installing Cross Tools for ARMs</a>).</p>
+</li>
+</ul>
+
+ <div class="row">
+
+
+
+
+<ul class="nav nav-pills" style="margin-bottom: 10px">
+ <li>
+
+ <a href=../get_started/>
+ <span class="fa fa-arrow-left"></span>
+ Previous: Basic Setup
+ </a>
+
+ </li>
+ <li class="pull-right">
+
+ <a href=../../../newt/install/newt_mac/>
+ Next: Install Newt on Mac
+ <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/ea2670d6/latest/os/get_started/native_tools/index.html
----------------------------------------------------------------------
diff --git a/latest/os/get_started/native_tools/index.html b/latest/os/get_started/native_tools/index.html
index 8c957f0..1fe3b02 100644
--- a/latest/os/get_started/native_tools/index.html
+++ b/latest/os/get_started/native_tools/index.html
@@ -10,7 +10,7 @@
<link rel="canonical" href="http://mynewt.apache.org/os/get_started/native_tools/"> -->
<link rel="shortcut icon" href="../../../img/favicon.ico">
- <title>toc - Apache Mynewt</title>
+ <title>Install Native Toolchain - 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="toc">
+ <body class="Install Native Toolchain">
<div class="container">
@@ -213,7 +213,7 @@
- <li class="active"><a href="./">Native install Option</a>
+ <li ><a href="../native_install_intro/">Native Install Option</a>
<ul>
@@ -238,6 +238,14 @@
+ <li class="active">
+ <a href="./">Install Native Toolchain</a>
+ </li>
+
+
+
+
+
<li >
<a href="../cross_tools/">Install Cross Tools for ARM</a>
</li>
@@ -379,10 +387,12 @@
- <li>» Native install Option</li>
+ <li>» <a href="../native_install_intro/">Native Install Option</a></li>
+ <li>» Install Native Toolchain</li>
+
</ul>
@@ -497,7 +507,7 @@ Setting up gdb (7.7.1-0ubuntu5~14.04.2) ...
<p><br></p>
-<p>At this point you have installed all the necessary software to build and test code on a simluator running on your Mac or Linux. Proceed to the <a href="../project_create/">Create Your First Project</a> section.</p>
+<p>At this point you have installed all the necessary software to build and run your first project on a simluator on your Mac OS or Linux computer. You may proceed to the <a href="../project_create/">Create Your First Project</a> section or continue to the next section and install the cross tools for ARM.</p>
<div class="row">
@@ -507,16 +517,16 @@ Setting up gdb (7.7.1-0ubuntu5~14.04.2) ...
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../get_started/>
+ <a href=../../../newt/install/newt_linux/>
<span class="fa fa-arrow-left"></span>
- Previous: Basic Setup
+ Previous: Install Newt on Linux
</a>
</li>
<li class="pull-right">
- <a href=../../../newt/install/newt_mac/>
- Next: Install Newt on Mac
+ <a href=../cross_tools/>
+ Next: Install Cross Tools for ARM
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/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 4098295..c989cab 100644
--- a/latest/os/get_started/project_create/index.html
+++ b/latest/os/get_started/project_create/index.html
@@ -213,7 +213,7 @@
- <li ><a href="../native_tools/">Native install Option</a>
+ <li ><a href="../native_install_intro/">Native Install Option</a>
</li>
@@ -364,16 +364,15 @@
<h2 id="create-your-first-mynewt-project">Create Your First Mynewt Project</h2>
<p>This page shows how to create a Mynewt Project using the <code>newt</code> command-line tool.</p>
<p><br></p>
-<h3 id="pre-requisites">Pre-Requisites</h3>
+<h3 id="prerequisites">Prerequisites</h3>
<ul>
-<li>Newt:<ul>
+<li>Have Internet connectivity to fetch remote Mynewt components.</li>
+<li>Install Newt:<ul>
+<li>If you have taken the native install route, see the installation instructions for <a href="../../../newt/install/newt_mac/">Mac OS</a> or for <a href="../../../newt/install/newt_linux/">Linux</a>. </li>
<li>If you have taken the Docker route, you have already installed Newt.</li>
-<li>If you have taken the native install route, you have to ensure that you have installed the Newt tool following the instructions for <a href="../../../newt/install/newt_mac/">Mac</a> or <a href="../../../newt/install/newt_linux/">Linux</a> as appropriate, and that the <code>newt</code> command is in your system path. </li>
</ul>
</li>
-<li>You must have Internet connectivity to fetch remote Mynewt components.</li>
-<li>You must <a href="../native_tools/">install the compiler tools</a> to
-support native compiling to build the project this tutorial creates. </li>
+<li>Install the <a href="../native_tools/">native toolchain</a> to compile and build a Mynewt native application. </li>
</ul>
<p><br></p>
<h3 id="newt-new">Newt New</h3>
@@ -389,7 +388,7 @@ Project myproj successfully created.
<p><br></p>
<p>Newt populates this new project with a base skeleton of a new Apache Mynewt
project. It has the following structure. </p>
-<p><strong>Note</strong>: If you do not have <code>tree</code>, install it by running <code>brew install tree</code>.</p>
+<p><strong>Note</strong>: If you do not have <code>tree</code>, run <code>brew install tree</code> to install on Mac OS or run <code>sudo apt-get install tree</code> to install on Linux.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ cd myproj
$ tree
.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/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 219e805..b827b90 100644
--- a/latest/os/get_started/serial_access/index.html
+++ b/latest/os/get_started/serial_access/index.html
@@ -213,7 +213,7 @@
- <li ><a href="../native_tools/">Native install Option</a>
+ <li ><a href="../native_install_intro/">Native Install Option</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/os/modules/drivers/driver/index.html
----------------------------------------------------------------------
diff --git a/latest/os/modules/drivers/driver/index.html b/latest/os/modules/drivers/driver/index.html
index 25b6d25..79e8706 100644
--- a/latest/os/modules/drivers/driver/index.html
+++ b/latest/os/modules/drivers/driver/index.html
@@ -573,7 +573,7 @@
<p>Device drivers should have a consistent structure and unified interface whenever possible. For example, we have a top-level package, “adc”, which contains the interface for all ADC drivers, and then we have the individual implementation of the driver itself. The following source files point to this:</p>
<ul>
<li>high-level ADC API: <code>hw/drivers/adc/include/adc/adc.h</code> </li>
-<li>implementation of ADC for STM32F4: <code>hw/drivers/adc/adc_stm32f4/src/adc_stm32f4.c</code> (As of the 1.0.0-beta release, ADC for nRF51 and nRF52 are available at an external <a href="https://github.com/runtimeinc/mynewt_nordic/tree/master/hw/drivers/adc">repo</a>. They are expected to be pulled into the core repo on Apache Mynewt after the license terms are clarified.). The only exported call in this example is <code>int stm32f4_adc_dev_init(struct os_dev *, void *)</code> which is passed as a function pointer to <code>os_dev_create()</code> in <code>hal_bsp.c</code>, when the adc device is created.</li>
+<li>implementation of ADC for STM32F4: <code>hw/drivers/adc/adc_stm32f4/src/adc_stm32f4.c</code> (As of the 1.0.0-beta release, ADC for nRF51 and nRF52 are available at an external <a href="https://github.com/runtimeco/mynewt_nordic/tree/master/hw/drivers/adc">repo</a>. They are expected to be pulled into the core repo on Apache Mynewt after the license terms are clarified.). The only exported call in this example is <code>int stm32f4_adc_dev_init(struct os_dev *, void *)</code> which is passed as a function pointer to <code>os_dev_create()</code> in <code>hal_bsp.c</code>, when the adc device is created.</li>
</ul>
</li>
<li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/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 5999c2e..ff989cb 100644
--- a/latest/os/tutorials/add_newtmgr/index.html
+++ b/latest/os/tutorials/add_newtmgr/index.html
@@ -490,12 +490,10 @@ to customize your application.</p>
<h3 id="prerequisites">Prerequisites</h3>
<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
<ul>
-<li>Install the <a href="../../../newt/install/newt_mac/">newt tool</a>. </li>
-<li>Install the <a href="../../../newtmgr/install_mac/">newtmgr tool</a>.</li>
<li>Have Internet connectivity to fetch remote Mynewt components.</li>
-<li>Install the <a href="../../get_started/native_tools/">compiler tools</a> to
-support native compiling to build the project this tutorial creates. </li>
<li>Have a cable to establish a serial USB connection between the board and the laptop.</li>
+<li>Install the newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
+<li>Install the <a href="../../../newtmgr/install_mac/">newtmgr tool</a>.</li>
</ul>
<p><br></p>
<h3 id="use-an-existing-project">Use an Existing Project</h3>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/os/tutorials/add_shell/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/add_shell/index.html b/latest/os/tutorials/add_shell/index.html
index 711ac27..361ff1f 100644
--- a/latest/os/tutorials/add_shell/index.html
+++ b/latest/os/tutorials/add_shell/index.html
@@ -476,16 +476,13 @@
<p>This tutorial explains how to add the Console and Shell task to a project so that you
can interact with your project over a serial line connection.</p>
<p><br></p>
-<h3 id="pre-requisites">Pre-Requisites</h3>
+<h3 id="prerequisites">Prerequisites</h3>
+<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
<ul>
-<li>Ensure you have installed <a href="../../../newt/install/newt_mac/">newt</a> and that the
-newt command is in your system path. </li>
-<li>You must have Internet connectivity to fetch remote Mynewt components.</li>
-<li>You must <a href="../../get_started/native_tools/">install the compiler tools</a> to
-support native compiling to build the project this tutorial creates. </li>
-<li>You must install the <a href="https://www.segger.com/jlink-software.html">Segger JLINK package</a> to
-load your project on the board.</li>
-<li>Cable to establish a serial USB connection between the board and the laptop</li>
+<li>Have Internet connectivity to fetch remote Mynewt components. </li>
+<li>Have a cable to establish a serial USB connection between the board and the laptop</li>
+<li>Install the newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
+<li>Install the <a href="https://www.segger.com/jlink-software.html">Segger JLINK package</a> to load your project on the board.</li>
</ul>
<p><br></p>
<h3 id="use-an-existing-project">Use an existing project</h3>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/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 ca09ea1..26f0dec 100644
--- a/latest/os/tutorials/arduino_zero/index.html
+++ b/latest/os/tutorials/arduino_zero/index.html
@@ -282,6 +282,14 @@
<li >
+ <a href="../blinky_stm32f4disc/">Blinky on STM32F4-Discovery</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../blinky_console/">Add Console and Shell to Blinky</a>
</li>
@@ -559,7 +567,7 @@ Note: There are many flavors of Arduino. Make sure you are using an Arduino Zero
<p><br></p>
<h3 id="fetch-external-packages"><a name="fetchexternal"></a> Fetch External Packages</h3>
<p>Mynewt uses source code provided directly from the chip manufacturer for
-low 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.</p>
+low 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.</p>
<p>To fetch the package with MCU support for Atmel SAMD21 for Arduino Zero from the Runtime git repository, you need to add
the repository to the <code>project.yml</code> file in your base project directory.</p>
<p>Here is an example <code>project.yml</code> file with the Arduino Zero repository
@@ -581,7 +589,7 @@ repository.apache-mynewt-core:
<span style="background-color: #ffffcc">repository.mynewt_arduino_zero:
</span><span style="background-color: #ffffcc"> type: github
</span><span style="background-color: #ffffcc"> vers: 1-latest
-</span><span style="background-color: #ffffcc"> user: runtimeinc
+</span><span style="background-color: #ffffcc"> user: runtimeco
</span><span style="background-color: #ffffcc"> repo: mynewt_arduino_zero
</span>$
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/os/tutorials/blehci_project/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/blehci_project/index.html b/latest/os/tutorials/blehci_project/index.html
index 179dbff..69a5708 100644
--- a/latest/os/tutorials/blehci_project/index.html
+++ b/latest/os/tutorials/blehci_project/index.html
@@ -476,20 +476,18 @@
<p>This tutorial explains how to use the example application <code>blehci</code> included in the NimBLE stack to talk to the Mynewt NimBLE controller via the Host Controller Interface. You may build the Mynewt image using a laptop running any OS of your choice - Mac, Linux, or Windows.</p>
<p>The host used in this specific example is the BlueZ Bluetooth stack. Since BlueZ is a Bluetooth stack for Linux kernel-based family of operating system, the tutorial expects a computer running Linux OS and with BlueZ installed to talk to the board with the Mynewt image.</p>
<p><br></p>
-<h3 id="pre-requisites">Pre-Requisites</h3>
+<h3 id="prerequisites">Prerequisites</h3>
+<p>Ensure that you meet the following prerequisites before continuing with one of the tutorials.</p>
<ul>
-<li>Ensure you have installed <a href="../../../newt/install/newt_mac/">newt</a> and that the
-newt command is in your system path. </li>
-<li>You must have Internet connectivity to fetch remote Mynewt components.</li>
-<li>If you are not using the Docker container for newt and other tools, you must <a href="../../get_started/native_tools/">install the compiler tools</a> to
-support native compiling to build the project this tutorial creates. </li>
-<li>You have a board with BLE radio that is supported by Mynewt. We will use an nRF52 Dev board in this tutorial.</li>
-<li>USB TTL Serial Cable that supports hardware flow control such as ones found at <a href="http://www.ftdichip.com/Products/Cables/USBTTLSerial.htm">http://www.ftdichip.com/Products/Cables/USBTTLSerial.htm</a> to establish a serial USB connection between the board and the laptop.</li>
-<li>You have installed a BLE host such as BlueZ on a Linux machine to talk to the nrf52 board running Mynewt. Use <code>sudo apt-get install bluez</code> to install it on your Linux machine. </li>
+<li>Have Internet connectivity to fetch remote Mynewt components.</li>
+<li>Have a board with BLE radio that is supported by Mynewt. We will use an nRF52 Dev board in this tutorial.</li>
+<li>Have a USB TTL Serial Cable that supports hardware flow control such as ones found at <a href="http://www.ftdichip.com/Products/Cables/USBTTLSerial.htm">http://www.ftdichip.com/Products/Cables/USBTTLSerial.htm</a> to establish a serial USB connection between the board and the laptop.</li>
+<li>Install the newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
+<li>Install a BLE host such as BlueZ on a Linux machine to talk to the nrf52 board running Mynewt. Use <code>sudo apt-get install bluez</code> to install it on your Linux machine. </li>
</ul>
<p><br></p>
<h3 id="create-a-project">Create a project</h3>
-<p>Use the Newt tool to create a new project directory containing a skeletal Mynewt framework. Change into the newly created directory. </p>
+<p>Use the newt tool to create a new project directory containing a skeletal Mynewt framework. Change into the newly created directory. </p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt new blehciproj
Downloading project skeleton from apache/incubator-mynewt-blinky...
Installing skeleton in blehciproj ...
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/os/tutorials/bletiny_project/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/bletiny_project/index.html b/latest/os/tutorials/bletiny_project/index.html
index a9197de..5b7dcdf 100644
--- a/latest/os/tutorials/bletiny_project/index.html
+++ b/latest/os/tutorials/bletiny_project/index.html
@@ -476,19 +476,17 @@
<p>This tutorial explains how to run an example BLE app on a board and command it to scan and spew some stats. The stats will be seen over a serial port, not a BLE wireless connection.</p>
<p><br></p>
<h3 id="prerequisites">Prerequisites</h3>
+<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
<ul>
-<li>Ensure you have installed <a href="../../../newt/install/newt_mac/">newt</a> and that the
-newt command is in your system path. </li>
-<li>You must have Internet connectivity to fetch remote Mynewt components.</li>
-<li>You must <a href="../../get_started/native_tools/">install the compiler tools</a> to
-support native compiling to build the project this tutorial creates. </li>
-<li>You must install the <a href="https://www.segger.com/jlink-software.html">Segger JLINK package</a> to load your project on the board.</li>
-<li>You have a board with BLE radio that is supported by Mynewt. We will use an nRF52 Dev board in this tutorial.</li>
-<li>Cable to establish a serial USB connection between the board and the laptop</li>
+<li>Have Internet connectivity to fetch remote Mynewt components.</li>
+<li>Have a board with BLE radio that is supported by Mynewt. We will use an nRF52 Dev board in this tutorial.</li>
+<li>Have a cable to establish a serial USB connection between the board and the laptop</li>
+<li>Install the newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
+<li>Install the <a href="https://www.segger.com/jlink-software.html">Segger JLINK package</a> to load your project on the board.</li>
</ul>
<p><br></p>
<h3 id="create-a-project">Create a project</h3>
-<p>Use the Newt tool to create a new project directory containing a skeletal Mynewt framework. Change into the newly created directory.</p>
+<p>Use the newt tool to create a new project directory containing a skeletal Mynewt framework. Change into the newly created directory.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt new myproj
Downloading project skeleton from apache/incubator-mynewt-blinky...
Installing skeleton in myproj...
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/os/tutorials/blinky/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/blinky/index.html b/latest/os/tutorials/blinky/index.html
index 9f77141..1bb740c 100644
--- a/latest/os/tutorials/blinky/index.html
+++ b/latest/os/tutorials/blinky/index.html
@@ -282,6 +282,14 @@
<li >
+ <a href="../blinky_stm32f4disc/">Blinky on STM32F4-Discovery</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../blinky_console/">Add Console and Shell to Blinky</a>
</li>
@@ -535,6 +543,7 @@
<li><a href="../olimex/">Blinky on an Olimex</a></li>
<li><a href="../nRF52/">Blinky on a nRF52</a></li>
<li><a href="../rbnano2/">Blinky on a RedBear Nano 2</a></li>
+<li><a href="../blinky_stm32f4disc/">Blinky on a STM32F4-Discovery</a></li>
</ul>
<p>We also have a tutorial that shows you how to add <a href="../blinky_console/">Console and Shell to the Blinky Application</a>.
<br></p>
@@ -544,7 +553,7 @@
<li>Have Internet connectivity to fetch remote Mynewt components.</li>
<li>Have a computer to build a Mynewt application and connect to the board over USB.</li>
<li>Have a Micro-USB cable to connect the board and the computer.</li>
-<li>Install the Newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
+<li>Install the newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section. </li>
<li>Create a project space (directory structure) and populate it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.
<br></li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/os/tutorials/blinky_console/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/blinky_console/index.html b/latest/os/tutorials/blinky_console/index.html
index f8067ad..05494c0 100644
--- a/latest/os/tutorials/blinky_console/index.html
+++ b/latest/os/tutorials/blinky_console/index.html
@@ -281,6 +281,14 @@
+ <li >
+ <a href="../blinky_stm32f4disc/">Blinky on STM32F4-Discovery</a>
+ </li>
+
+
+
+
+
<li class="active">
<a href="./">Add Console and Shell to Blinky</a>
</li>
@@ -697,9 +705,9 @@ prompt on
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../rbnano2/>
+ <a href=../blinky_stm32f4disc/>
<span class="fa fa-arrow-left"></span>
- Previous: Blinky on RedBear Nano 2
+ Previous: Blinky on STM32F4-Discovery
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/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 bd384e6..daa57f8 100644
--- a/latest/os/tutorials/blinky_primo/index.html
+++ b/latest/os/tutorials/blinky_primo/index.html
@@ -282,6 +282,14 @@
<li >
+ <a href="../blinky_stm32f4disc/">Blinky on STM32F4-Discovery</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../blinky_console/">Add Console and Shell to Blinky</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/os/tutorials/blinky_stm32f4disc/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/blinky_stm32f4disc/index.html b/latest/os/tutorials/blinky_stm32f4disc/index.html
new file mode 100644
index 0000000..a922d73
--- /dev/null
+++ b/latest/os/tutorials/blinky_stm32f4disc/index.html
@@ -0,0 +1,770 @@
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <meta charset="utf-8">
+ <meta http-equiv="X-UA-Compatible" content="IE=edge">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+
+ <!-- This is broken by doc revisioning.
+ <link rel="canonical" href="http://mynewt.apache.org/os/tutorials/blinky_stm32f4disc/"> -->
+ <link rel="shortcut icon" href="../../../img/favicon.ico">
+
+ <title>Blinky on STM32F4-Discovery - 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="Blinky on STM32F4-Discovery">
+
+
+ <div class="container">
+ <div class="row v2-main-banner">
+ <a class="logo-cell" href="/">
+ <img class="logo" src="/img/logo.png">
+ </a>
+ <div class="tagline-cell">
+ <h4 class="tagline">An OS to build, deploy and securely manage billions of devices</h4>
+ </div>
+ <div class="news-cell">
+ <div class="well">
+ <h4>Latest News:</h4> <a href="/download">Apache Mynewt 1.0.0</a> released (March 22, 2017)
+ </div>
+ </div>
+ </div>
+</div>
+
+
+
+
+
+
+
+
+<nav id="navbar" class="navbar navbar-inverse affix-top" data-spy="affix" data-offset-top="150" role="navigation">
+ <div class="container">
+ <!-- Collapsed navigation -->
+ <div class="navbar-header">
+ <!-- Expander button -->
+ <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
+ <span class="sr-only">Toggle navigation</span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ </button>
+
+ </div>
+
+ <!-- Expanded navigation -->
+ <div class="navbar-collapse collapse">
+ <!-- Main navigation -->
+ <ul class="nav navbar-nav navbar-right">
+ <li
+ class=""
+>
+ <a href="/"><i class="fa fa-home" style="font-size: larger;"></i></a>
+ </li>
+ <li
+ class="important"
+>
+ <a href="/quick-start/">Quick Start</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/about/">About</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/talks/">Talks</a>
+ </li>
+ <li
+ class="active"
+>
+ <a href="/latest/os/introduction">Documentation</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/download/">Download</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/community/">Community</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/events/">Events</a>
+ </li>
+ </ul>
+
+ <!-- Search, Navigation and Repo links -->
+ <ul class="nav navbar-nav navbar-right">
+
+ </ul>
+ </div>
+ </div>
+</nav>
+
+
+
+ <div class="container">
+
+ <div class="row">
+ <div class="col-md-3 v2-sidebar sidebar-container"><div id="docSidebar" class="hidden-print" role="complementary">
+ <div class="top">
+ <div role="search">
+ <form id="rtd-search-form" class="wy-form" action="../../../search.html" method="get">
+ <div class="form-group">
+ <input type="text" name="q" class="form-control" placeholder="Search documentation" />
+ </div>
+ </form>
+ </div>
+ </div>
+ <ul class="toc-nav">
+ <li class="doc-version">
+<select class="form-control" onchange="if (this.value) window.location.href=this.value">
+
+ <option
+ value="/develop/os/introduction"
+ selected="selected"
+ >
+ Version: develop (latest)
+ </option>
+
+ <option
+ value="/v0_9_0/os/introduction"
+
+ >
+ Version: 0.9.0
+ </option>
+
+</select>
+</li>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ <li ><a href="../../introduction/">Mynewt Documentation</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../../get_started/get_started/">Basic Setup</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../get_started/vocabulary/">Concepts</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../tutorials/">Tutorials</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../blinky/">Project Blinky</a>
+
+
+ <ul>
+
+
+
+
+
+ <li >
+ <a href="../arduino_zero/">Blinky on Arduino Zero</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../blinky_primo/">Blinky on Arduino Primo</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../olimex/">Blinky on Olimex</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../nRF52/">Blinky on nRF52</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../rbnano2/">Blinky on RedBear Nano 2</a>
+ </li>
+
+
+
+
+
+ <li class="active">
+ <a href="./">Blinky on STM32F4-Discovery</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../blinky_console/">Add Console and Shell to Blinky</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../repo/add_repos/">Work with repositories</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../ibeacon/">BLE iBeacon</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../eddystone/">BLE Eddystone</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../blehci_project/">BLE HCI interface</a>
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../air_quality_sensor/
+">Air-quality Sensor project</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../nrf52_adc/">Add an Analog Sensor</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../os_user_guide/">OS User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../../network/ble/ble_intro/
+">BLE User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../newt/newt_intro/">Newt Tool Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../newtmgr/overview/">Newt Manager Guide</a>
+
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../../faq/go_env/
+">Appendix</a>
+
+
+ </li>
+
+
+
+ </ul>
+</div></div>
+
+ <div class="col-md-9" role="main">
+ <div class="doc-header">
+ <div role="navigation" aria-label="breadcrumbs navigation">
+ <ul class="wy-breadcrumbs pull-right">
+ <li><a href="/latest/os/introduction">Docs</a></li>
+
+
+
+ <li>» <a href="../tutorials/">Tutorials</a></li>
+
+
+
+ <li>» <a href="../blinky/">Project Blinky</a></li>
+
+
+
+ <li>» Blinky on STM32F4-Discovery</li>
+
+
+
+ </ul>
+</div>
+ </div>
+
+ <h2 id="blinky-your-hello-world-on-stm32f4-discovery">Blinky, your "Hello World!", on STM32F4-Discovery</h2>
+<p>This tutorial shows you how to create, build, and run the Blinky application on the STM32F4-Discovery board.
+<br></p>
+<p><br></p>
+<h3 id="prerequisites">Prerequisites</h3>
+<ul>
+<li>Meet the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
+<li>Have a STM32F4-Discovery board.</li>
+<li>Have a USB type A to Mini-B cable. </li>
+<li>Install a patched version of OpenOCD 0.10.0 described in <a href="../os/get_started/cross_tools/">Install OpenOCD</a>. </li>
+</ul>
+<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>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ mkdir ~/dev
+ $ cd ~/dev
+ $ newt new myproj
+ Downloading project skeleton from apache/incubator-mynewt-blinky...
+ Installing skeleton in myproj...
+ Project myproj successfully created.
+ $ cd myproj
+ $ newt install
+ apache-mynewt-core
+ $
+</pre></div>
+
+
+<p><br></p>
+<h3 id="create-the-targets"><a name="create_targets"></a>Create the Targets</h3>
+<p>Create two targets for the STM32F4-Discovery 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, to create a bootloader target. We name the target <code>stm32f4disc_boot</code>:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create stm32f4disc_boot
+$ newt target set stm32f4disc_boot app=@apache-mynewt-core/apps/boot
+$ newt target set stm32f4disc_boot bsp=@apache-mynewt-core/hw/bsp/stm32f4discovery
+$ newt target set stm32f4disc_boot build_profile=optimized
+</pre></div>
+
+
+<p><br>
+Run the following <code>newt target</code> commands to create a target for the Blinky application. We name the target <code>stm32f4disc_blinky</code>:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create stm32f4disc_blinky
+$ newt target set stm32f4disc_blinky app=apps/blinky
+$ newt target set stm32f4disc_blinky bsp=@apache-mynewt-core/hw/bsp/stm32f4discovery
+$ newt target set stm32f4disc_blinky build_profile=debug
+</pre></div>
+
+
+<p><br>
+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
+ bsp=@apache-mynewt-core/hw/bsp/native
+ build_profile=debug
+targets/stm32f4disc_blinky
+ app=apps/blinky
+ bsp=@apache-mynewt-core/hw/bsp/stm32f4discovery
+ build_profile=debug
+targets/stm32f4disc_boot
+ app=@apache-mynewt-core/apps/boot
+ bsp=@apache-mynewt-core/hw/bsp/stm32f4discovery
+ build_profile=optimized
+</pre></div>
+
+
+<p><br></p>
+<h3 id="build-the-target-executables">Build the Target Executables</h3>
+<p>Run the <code>newt build stm32f4disc_boot</code> command to build the bootloader:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt build stm32f4disc_boot
+Building target targets/stm32f4disc_boot
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c
+Compiling repos/apache-mynewt-core/apps/boot/src/boot.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/loader.c
+ ...
+
+Archiving sys_flash_map.a
+Archiving sys_mfg.a
+Archiving sys_sysinit.a
+Archiving util_mem.a
+Linking ~/dev/myproj/bin/targets/stm32f4disc_boot/app/apps/boot/boot.elf
+Target successfully built: targets/stm32f4disc_boot
+</pre></div>
+
+
+<p><br>
+Run the <code>newt build stm32f4disc_blinky</code> command to build the Blinky application:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt build stm32f4disc_blinky
+Building target targets/stm32f4disc_blinky
+Compiling apps/blinky/src/main.c
+Compiling repos/apache-mynewt-core/hw/bsp/stm32f4discovery/src/sbrk.c
+Compiling repos/apache-mynewt-core/hw/bsp/stm32f4discovery/src/system_stm32f4xx.c
+Compiling repos/apache-mynewt-core/hw/bsp/stm32f4discovery/src/hal_bsp.c
+Assembling repos/apache-mynewt-core/hw/bsp/stm32f4discovery/src/arch/cortex_m4/startup_STM32F40x.s
+Compiling repos/apache-mynewt-core/hw/cmsis-core/src/cmsis_nvic.c
+Compiling repos/apache-mynewt-core/hw/drivers/uart/src/uart.c
+Compiling repos/apache-mynewt-core/hw/drivers/uart/uart_hal/src/uart_hal.c
+Compiling repos/apache-mynewt-core/hw/hal/src/hal_common.c
+Compiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c
+
+ ...
+
+Archiving sys_sysinit.a
+Archiving util_mem.a
+Linking ~/dev/myproj/bin/targets/stm32f4disc_blinky/app/apps/blinky/blinky.elf
+Target successfully built: targets/stm32f4disc_blinky
+</pre></div>
+
+
+<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 stm32f4disc_blinky 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 stm32f4disc_blinky 1.0.0
+App image succesfully generated: ~/dev/myproj/bin/targets/stm32f4disc_blinky/app/apps/blinky/blinky.img
+</pre></div>
+
+
+<p><br></p>
+<h3 id="connect-to-the-board">Connect to the Board</h3>
+<p>Connect a USB type A to Mini-B cable from your computer to the port the board indicated on the diagram: </p>
+<p><br>
+<br>
+<img alt="stm32f4-discovery" src="../pics/stm32f4_disc.jpg" title="Connecting computer to stm32f4disc" /></p>
+<p><br></p>
+<p>You should see the small PWR red LED light up.</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 stm32f4disc_boot</code> command to load the bootloader onto the board: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt load stm32f4disc_boot
+Loading bootloader
+</pre></div>
+
+
+<p><br>
+Run the <code>newt load stm32f4disc_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 stm32f4disc_blinky
+Loading app image into slot 1
+</pre></div>
+
+
+<p>You should see the small green LD4 LED 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, start a debug session, and enter <code>mon stm32f2x mass_erase 0</code> at the gdb prompt:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt debug stm32f4disc_blinky
+[~/dev/myproj/repos/apache-mynewt-core/hw/bsp/stm32f4discovery/stm32f4discovery_debug.sh ~/dev/myproj/repos/apache-mynewt-core/hw/bsp/stm32f4discovery ~/dev/myproj/bin/targets/stm32f4disc_blinky/app/apps/blinky/blinky]
+Open On-Chip Debugger 0.10.0
+Licensed under GNU GPL v2
+For bug reports, read
+ http://openocd.org/doc/doxygen/bugs.html
+Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
+adapter speed: 2000 kHz
+adapter_nsrst_delay: 100
+none separate
+Info : Unable to match requested speed 2000 kHz, using 1800 kHz
+Info : Unable to match requested speed 2000 kHz, using 1800 kHz
+Info : clock speed 1800 kHz
+Info : STLINK v2 JTAG v25 API v2 SWIM v14 VID 0x0483 PID 0x374B
+Info : using stlink api v2
+Info : Target voltage: 2.881129
+Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints
+target halted due to debug-request, current mode: Thread
+
+ ...
+
+Reading symbols from ~/dev/myproj/bin/targets/stm32f4disc_blinky/app/apps/blinky/blinky.elf...done.
+target halted due to debug-request, current mode: Thread
+xPSR: 0x41000000 pc: 0x08021e90 psp: 0x20002290
+Info : accepting 'gdb' connection on tcp/3333
+Info : device id = 0x10076413
+Info : flash size = 1024kbytes
+0x08021e90 in __WFI () at repos/apache-mynewt-core/hw/cmsis-core/src/ext/core_cmInstr.h:342
+342 __ASM volatile ("wfi");
+(gdb) mon stm32f2x mass_erase 0
+stm32x mass erase complete
+stm32x mass erase complete
+(gdb)
+</pre></div>
+
+ <div class="row">
+
+
+
+
+<ul class="nav nav-pills" style="margin-bottom: 10px">
+ <li>
+
+ <a href=../rbnano2/>
+ <span class="fa fa-arrow-left"></span>
+ Previous: Blinky on RedBear Nano 2
+ </a>
+
+ </li>
+ <li class="pull-right">
+
+ <a href=../blinky_console/>
+ Next: Add Console and Shell to Blinky
+ <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/ea2670d6/latest/os/tutorials/nRF52/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/nRF52/index.html b/latest/os/tutorials/nRF52/index.html
index 43b4566..d69043a 100644
--- a/latest/os/tutorials/nRF52/index.html
+++ b/latest/os/tutorials/nRF52/index.html
@@ -282,6 +282,14 @@
<li >
+ <a href="../blinky_stm32f4disc/">Blinky on STM32F4-Discovery</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../blinky_console/">Add Console and Shell to Blinky</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/os/tutorials/nrf52_adc/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/nrf52_adc/index.html b/latest/os/tutorials/nrf52_adc/index.html
index b2c8ef1..6bbebcf 100644
--- a/latest/os/tutorials/nrf52_adc/index.html
+++ b/latest/os/tutorials/nrf52_adc/index.html
@@ -532,7 +532,7 @@ repository.apache-mynewt-core:
<span style="background-color: #ffffcc">repository.mynewt_nordic:
</span><span style="background-color: #ffffcc"> type: github
</span><span style="background-color: #ffffcc"> vers: 1-latest
-</span><span style="background-color: #ffffcc"> user: runtimeinc
+</span><span style="background-color: #ffffcc"> user: runtimeco
</span><span style="background-color: #ffffcc"> repo: mynewt_nordic
</span></pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/os/tutorials/olimex/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/olimex/index.html b/latest/os/tutorials/olimex/index.html
index e769619..a51abf4 100644
--- a/latest/os/tutorials/olimex/index.html
+++ b/latest/os/tutorials/olimex/index.html
@@ -282,6 +282,14 @@
<li >
+ <a href="../blinky_stm32f4disc/">Blinky on STM32F4-Discovery</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../blinky_console/">Add Console and Shell to Blinky</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/os/tutorials/pics/stm32f4_disc.jpg
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/pics/stm32f4_disc.jpg b/latest/os/tutorials/pics/stm32f4_disc.jpg
new file mode 100755
index 0000000..cbed05f
Binary files /dev/null and b/latest/os/tutorials/pics/stm32f4_disc.jpg differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/os/tutorials/rbnano2/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/rbnano2/index.html b/latest/os/tutorials/rbnano2/index.html
index e6e0fa9..672112a 100644
--- a/latest/os/tutorials/rbnano2/index.html
+++ b/latest/os/tutorials/rbnano2/index.html
@@ -282,6 +282,14 @@
<li >
+ <a href="../blinky_stm32f4disc/">Blinky on STM32F4-Discovery</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../blinky_console/">Add Console and Shell to Blinky</a>
</li>
@@ -699,8 +707,8 @@ Loading app image into slot 1
</li>
<li class="pull-right">
- <a href=../blinky_console/>
- Next: Add Console and Shell to Blinky
+ <a href=../blinky_stm32f4disc/>
+ Next: Blinky on STM32F4-Discovery
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/os/tutorials/repo/add_repos/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/repo/add_repos/index.html b/latest/os/tutorials/repo/add_repos/index.html
index 82b24df..ec6fce2 100644
--- a/latest/os/tutorials/repo/add_repos/index.html
+++ b/latest/os/tutorials/repo/add_repos/index.html
@@ -628,7 +628,7 @@ repository.apache-Mynewt-core:
repository.Mynewt_arduino_zero:
type: github
vers: 1-latest
- user: runtimeinc
+ user: runtimeco
repo: Mynewt_arduino_zero
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/os/tutorials/wi-fi_on_arduino/index.html
----------------------------------------------------------------------
diff --git a/latest/os/tutorials/wi-fi_on_arduino/index.html b/latest/os/tutorials/wi-fi_on_arduino/index.html
index ed8d7f8..691611d 100644
--- a/latest/os/tutorials/wi-fi_on_arduino/index.html
+++ b/latest/os/tutorials/wi-fi_on_arduino/index.html
@@ -541,7 +541,7 @@ repository.apache-mynewt-core:
<span style="background-color: #ffffcc">repository.mynewt_arduino_zero:
</span><span style="background-color: #ffffcc"> type: github
</span><span style="background-color: #ffffcc"> vers: 1-latest
-</span><span style="background-color: #ffffcc"> user: runtimeinc
+</span><span style="background-color: #ffffcc"> user: runtimeco
</span><span style="background-color: #ffffcc"> repo: mynewt_arduino_zero
</span>$
</pre></div>
[4/7] incubator-mynewt-site git commit: changed runtimeinc to
runtimeco in docs, updated install instructions for linux ,
blinky for stm32F4-discovery
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/sitemap.xml
----------------------------------------------------------------------
diff --git a/develop/sitemap.xml b/develop/sitemap.xml
index b635405..bdc2916 100644
--- a/develop/sitemap.xml
+++ b/develop/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>http://mynewt.apache.org/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -13,7 +13,7 @@
<url>
<loc>http://mynewt.apache.org/pages/ble/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -22,7 +22,7 @@
<url>
<loc>http://mynewt.apache.org/quick-start/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -30,7 +30,7 @@
<url>
<loc>http://mynewt.apache.org/about/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -38,7 +38,7 @@
<url>
<loc>http://mynewt.apache.org/talks/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -46,7 +46,7 @@
<url>
<loc>http://mynewt.apache.org/download/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -54,7 +54,7 @@
<url>
<loc>http://mynewt.apache.org/community/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -62,7 +62,7 @@
<url>
<loc>http://mynewt.apache.org/events/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -71,7 +71,7 @@
<url>
<loc>http://mynewt.apache.org/os/introduction/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -83,7 +83,7 @@
<url>
<loc>http://mynewt.apache.org/os/get_started/vocabulary/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
@@ -123,19 +123,19 @@
<url>
<loc>http://mynewt.apache.org/faq/go_env/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/how_to_edit_docs/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>http://mynewt.apache.org/faq/answers/</loc>
- <lastmod>2017-04-25</lastmod>
+ <lastmod>2017-05-05</lastmod>
<changefreq>daily</changefreq>
</url>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/faq/go_env/index.html
----------------------------------------------------------------------
diff --git a/latest/faq/go_env/index.html b/latest/faq/go_env/index.html
index 36d3bd2..079529b 100644
--- a/latest/faq/go_env/index.html
+++ b/latest/faq/go_env/index.html
@@ -409,7 +409,7 @@ nothing to commit, working directory clean
Check that the newtmgr binary is installed and you are using the one from <strong>$GOPATH/bin</strong>:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ls $GOPATH/bin/newtmgr
~/dev/go/bin/newtmgr
-$which newt
+$which newtmgr
~/dev/go/bin/newtmgr
</pre></div>
[3/7] incubator-mynewt-site git commit: changed runtimeinc to
runtimeco in docs, updated install instructions for linux ,
blinky for stm32F4-discovery
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/latest/mkdocs/search_index.json
----------------------------------------------------------------------
diff --git a/latest/mkdocs/search_index.json b/latest/mkdocs/search_index.json
index 4de7a25..808a034 100644
--- a/latest/mkdocs/search_index.json
+++ b/latest/mkdocs/search_index.json
@@ -146,49 +146,14 @@
"title": "Quick Start"
},
{
- "location": "/os/get_started/native_tools/",
- "text": "Installing Native Mynewt Tools\n\n\nThis page shows how to install tools for native Mynewt targets (simulated targets on your laptop/computer) without using a Docker container. In other words, it allows you to run Mynewt OS as a native application on your Mac or Linux machine to simulate a target and use the Newt tool running natively on your machine to manage the simulated target. It also allows you to run the test suites for all packages not requiring HW support. You may choose to do this instead of using the build toolchain and Newt tool available in a Docker container.\n\n\nThis page provides guidance for MAC and Linux. See the relevant sections below.\n\n\n\n\nSet up toolchain for Mac\n\n\nInstall Brew\n\n\nIf you have not already installed Homebrew from the \n\nnewt\n tutorials pages\n, install it. \n\n\n\n\nInstall gcc/libc\n\n\nOS X ships with a C compiler called Clang. To build applications for the Mynewt simulator with, a different compiler is used as
default: gcc.\n\n\n$ brew install gcc\n...\n...\n==\n Summary\n\ud83c\udf7a /usr/local/Cellar/gcc/5.2.0: 1353 files, 248M\n\n\n\n\n\n\n\nCheck the gcc version you have installed (either using brew or previously installed). The brew-installed version can be checked using \nbrew list gcc\n. The default compiler.yml configuration file in Mynewt expects version 5.x for Mac users, so if the installed version is 6.x and you wish to continue with this newer version, modify the \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n file to change the default \ngcc-5\n defined there to \ngcc-6\n. In other words, replace the lines shown highlighted below:\n\n\n# OS X.\n\ncompiler.path.cc.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.as.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.objdump.DARWIN.OVERWRITE: \ngobjdump\n\ncompiler.path.objsize.DARWIN.OVERWRITE: \nobjsize\n\ncompiler.path.objcopy.DARWIN.OVERWRITE: \ngobjcopy\n\n\n\n\n\n\nwith the following:\n\n\ncompiler.p
ath.cc.DARWIN.OVERWRITE: \ngcc-6\n\ncompiler.path.as.DARWIN.OVERWRITE: \ngcc-6\u201d\n\n\n\n\n\n\n\nIn case you wish to use Clang, you can change your \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n to use Clang. Delete the gcc-5 DARWIN.OVERWRITE lines highlighted below.\n\n\n# OS X.\n\ncompiler.path.cc.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.as.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.objdump.DARWIN.OVERWRITE: \ngobjdump\n\ncompiler.path.objsize.DARWIN.OVERWRITE: \nobjsize\n\ncompiler.path.objcopy.DARWIN.OVERWRITE: \ngobjcopy\n\n\n\n\n\n\n\n\nNOTE:\n Both the newer gcc 6.x and Clang report a few warnings but they can be ignored.\n\n\n\n\nFURTHER NOTE:\n Mynewt developers mostly use gcc 5.x for sim builds; so it may take a little while to fix issues reported by the newer compiler. One option is to \ndisable warnings\n. To do that, remove the \n-Werror\n flag as an option for the compiler in the \nmynewt-src-directory\n/repos/apache-mynewt-core
/compiler/sim/compiler.yml\n file as shown below. \n\n\ncompiler.flags.base: \n\n\n -m32 -Wall -ggdb\n\n\n\n\n\nYou may alternatively choose to \nspecify the precise warnings to ignore\n depending on the error thrown by the compiler. For example, if you see a \n[-Werror=misleading-indentation]\n error while building the sim image, add \n-Wno-misleading-indentation]\n as a compiler flag in the same line from the \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n file.\n\n\ncompiler.flags.base: \n\n\n -m32 -Wall -Werror -ggdb -Wno-misleading-indentation\n\n\n\n\n\nA third option is to simply \ndowngrade to gcc 5.x\n.\n\n\n\n\nInstall gdb\n\n\n$ brew install gdb\n...\n...\n==\n Summary\n\ud83c\udf7a /usr/local/Cellar/gdb/7.10.1: XXX files,YYM\n\n\n\n\n\n\n\nNOTE:\n When running a program with gdb, you may need to sign your gdb\nexecutable. \nThis page\n\nshows a recipe for gdb signing. Alternately you can skip this step and\ncontinue without the abili
ty to debug your mynewt application on your PC.*\n\n\n\n\nSet up toolchain for Linux\n\n\nThe below procedure can be used to set up a Debian-based Linux system (e.g.,\nUbuntu). If you are running a different Linux distribution, you will need to\nsubstitute invocations of \napt-get\n in the below steps with the package manager\nthat your distro uses.\n\n\n\n\nInstall gcc/libc that will produce 32-bit executables:\n\n\n$ sudo apt-get install gcc-multilib libc6-i386\n\n\n\n\n\n\n\nInstall gdb\n\n\n$ sudo apt-get install gdb\n\nReading package lists... Done\nBuilding dependency tree \nReading state information... Done\nSuggested packages:\n gdb-doc gdbserver\nThe following NEW packages will be installed:\n gdb\n...\nProcessing triggers for man-db (2.6.7.1-1ubuntu1) ...\nSetting up gdb (7.7.1-0ubuntu5~14.04.2) ...\n\n\n\n\n\n\n\nAt this point you have installed all the necessary software to build and test code on a simluator running on your Mac or Linux. Proceed to the \nCreate
Your First Project\n section.",
+ "location": "/os/get_started/native_install_intro/",
+ "text": "Native Installation\n\n\nThis section shows you how to install tools on Mac OS and Linux platforms to develop, build, run, and debug Mynewt OS applications. You can build Mynewt OS applications to run as a native application on your computer or to run on your target board. These tools include:\n\n\n\n\n\n\nNewt tool - Tool to create, build, load, and debug a mynewt target.\n\n\n\n\nSee \nInstalling the Newt Tool on Mac OS\n to install on Mac OS.\n\n\nSee \nInstalling the Newt Tool on Linux\n to install on Linux.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nNative toolchain - Native toolchain to build and run Mynewt OS as a native application on your computer.\n (See \nInstalling Native Toolchain\n). \n\n\n\n\n\n\nCross toolchain for ARM - Cross toolchain for ARM to build and run a Mynewt OS application on a target board\n (See \nInstalling Cross Tools for ARMs\n).",
"title": "toc"
},
{
- "location": "/os/get_started/native_tools/#installing-native-mynewt-tools",
- "text": "This page shows how to install tools for native Mynewt targets (simulated targets on your laptop/computer) without using a Docker container. In other words, it allows you to run Mynewt OS as a native application on your Mac or Linux machine to simulate a target and use the Newt tool running natively on your machine to manage the simulated target. It also allows you to run the test suites for all packages not requiring HW support. You may choose to do this instead of using the build toolchain and Newt tool available in a Docker container. This page provides guidance for MAC and Linux. See the relevant sections below.",
- "title": "Installing Native Mynewt Tools"
- },
- {
- "location": "/os/get_started/native_tools/#set-up-toolchain-for-mac",
- "text": "",
- "title": "Set up toolchain for Mac"
- },
- {
- "location": "/os/get_started/native_tools/#install-brew",
- "text": "If you have not already installed Homebrew from the newt tutorials pages , install it.",
- "title": "Install Brew"
- },
- {
- "location": "/os/get_started/native_tools/#install-gcclibc",
- "text": "OS X ships with a C compiler called Clang. To build applications for the Mynewt simulator with, a different compiler is used as default: gcc. $ brew install gcc\n...\n...\n== Summary\n\ud83c\udf7a /usr/local/Cellar/gcc/5.2.0: 1353 files, 248M Check the gcc version you have installed (either using brew or previously installed). The brew-installed version can be checked using brew list gcc . The default compiler.yml configuration file in Mynewt expects version 5.x for Mac users, so if the installed version is 6.x and you wish to continue with this newer version, modify the mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml file to change the default gcc-5 defined there to gcc-6 . In other words, replace the lines shown highlighted below: # OS X. compiler.path.cc.DARWIN.OVERWRITE: gcc-5 compiler.path.as.DARWIN.OVERWRITE: gcc-5 compiler.path.objdump.DARWIN.OVERWRITE: gobjdump \ncompiler.path.objsize.DARWIN.OVERWRITE: objsize
\ncompiler.path.objcopy.DARWIN.OVERWRITE: gobjcopy with the following: compiler.path.cc.DARWIN.OVERWRITE: gcc-6 \ncompiler.path.as.DARWIN.OVERWRITE: gcc-6\u201d In case you wish to use Clang, you can change your mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml to use Clang. Delete the gcc-5 DARWIN.OVERWRITE lines highlighted below. # OS X. compiler.path.cc.DARWIN.OVERWRITE: gcc-5 compiler.path.as.DARWIN.OVERWRITE: gcc-5 compiler.path.objdump.DARWIN.OVERWRITE: gobjdump \ncompiler.path.objsize.DARWIN.OVERWRITE: objsize \ncompiler.path.objcopy.DARWIN.OVERWRITE: gobjcopy NOTE: Both the newer gcc 6.x and Clang report a few warnings but they can be ignored. FURTHER NOTE: Mynewt developers mostly use gcc 5.x for sim builds; so it may take a little while to fix issues reported by the newer compiler. One option is to disable warnings . To do that, remove the -Werror flag as an option for the compiler in the mynewt-src-directory /repos/apa
che-mynewt-core/compiler/sim/compiler.yml file as shown below. compiler.flags.base: -m32 -Wall -ggdb You may alternatively choose to specify the precise warnings to ignore depending on the error thrown by the compiler. For example, if you see a [-Werror=misleading-indentation] error while building the sim image, add -Wno-misleading-indentation] as a compiler flag in the same line from the mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml file. compiler.flags.base: -m32 -Wall -Werror -ggdb -Wno-misleading-indentation A third option is to simply downgrade to gcc 5.x .",
- "title": "Install gcc/libc"
- },
- {
- "location": "/os/get_started/native_tools/#install-gdb",
- "text": "$ brew install gdb\n...\n...\n== Summary\n\ud83c\udf7a /usr/local/Cellar/gdb/7.10.1: XXX files,YYM NOTE: When running a program with gdb, you may need to sign your gdb\nexecutable. This page \nshows a recipe for gdb signing. Alternately you can skip this step and\ncontinue without the ability to debug your mynewt application on your PC.*",
- "title": "Install gdb"
- },
- {
- "location": "/os/get_started/native_tools/#set-up-toolchain-for-linux",
- "text": "The below procedure can be used to set up a Debian-based Linux system (e.g.,\nUbuntu). If you are running a different Linux distribution, you will need to\nsubstitute invocations of apt-get in the below steps with the package manager\nthat your distro uses.",
- "title": "Set up toolchain for Linux"
- },
- {
- "location": "/os/get_started/native_tools/#install-gcclibc-that-will-produce-32-bit-executables",
- "text": "$ sudo apt-get install gcc-multilib libc6-i386",
- "title": "Install gcc/libc that will produce 32-bit executables:"
- },
- {
- "location": "/os/get_started/native_tools/#install-gdb_1",
- "text": "$ sudo apt-get install gdb\n\nReading package lists... Done\nBuilding dependency tree \nReading state information... Done\nSuggested packages:\n gdb-doc gdbserver\nThe following NEW packages will be installed:\n gdb\n...\nProcessing triggers for man-db (2.6.7.1-1ubuntu1) ...\nSetting up gdb (7.7.1-0ubuntu5~14.04.2) ... At this point you have installed all the necessary software to build and test code on a simluator running on your Mac or Linux. Proceed to the Create Your First Project section.",
- "title": "Install gdb"
+ "location": "/os/get_started/native_install_intro/#native-installation",
+ "text": "This section shows you how to install tools on Mac OS and Linux platforms to develop, build, run, and debug Mynewt OS applications. You can build Mynewt OS applications to run as a native application on your computer or to run on your target board. These tools include: Newt tool - Tool to create, build, load, and debug a mynewt target. See Installing the Newt Tool on Mac OS to install on Mac OS. See Installing the Newt Tool on Linux to install on Linux. Native toolchain - Native toolchain to build and run Mynewt OS as a native application on your computer.\n (See Installing Native Toolchain ). Cross toolchain for ARM - Cross toolchain for ARM to build and run a Mynewt OS application on a target board\n (See Installing Cross Tools for ARMs ).",
+ "title": "Native Installation"
},
{
"location": "/newt/install/newt_mac/",
@@ -222,27 +187,27 @@
},
{
"location": "/newt/install/newt_linux/",
- "text": "Installing Newt on Linux\n\n\nYou can install the latest stable release (1.0.0) of newt from a Debian binary package (amd64) or from a Debian source package. This page shows you how to:\n\n\n\n\nSet up your computer to retrieve Debian packages from the runtimeco debian package repository.\n\n\nInstall the latest stable release version of newt from a Debian binary package. \n\n\nInstall the latest stable release version of newt from a Debian source package.\n\n\n\n\nIf you are running on an amd64 platform, we recommend that you install from the binary package.\n\n\nNote:\n See \nSetting Up an Go Environment to Contribute to Newt and Newtmgr Tools\n if you want to: \n\n\n\n\nUse the newt tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.\n\n\nContribute to the newt tool. \n\n\n\n\n\n\nSetting Up Your Computer to Get Packages from runtimeco\n\n\nThe newt Debian pac
kages are stored in a private repository on \nhttps://github/runtimeco/debian-mynewt\n. \n\n\nNote:\n You will only need to perform these steps only once on your computer.\nThe following steps must be performed on your computer:\n\n\n\n\nAdd the \napt-transport-https\n package to use HTTPS to retrieve packages. \n\n\nDownload the public key for the runtimeco debian repository and import the key into the apt keychain.\n\n\nAdd the repository for the binary and source packages to the apt source list.\n\n\n\n\n\nAdd the apt-transport-https package:\n\n\n$sudo apt-get update\n$sudo apt-get install apt-transport-https\n\n\n\n\n\n\n\nDownload the public key for the runtimeco apt repo (\nNote:\n There is \n-\n after the add):\n\n\nwget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -\n\n\n\n\n\n\n\nAdd the repository for the binary and source packages to the apt source list:\n\n\n$sudo -s\n[sudo] password for \nuser\n:\nroot$ cat \
n /etc/apt/sources.list.d/mynewt.list \nEOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\nEOF\n\n\n\n\n\n\nCheck the content of the file:\n\n\nroot$more /etc/apt/sources.list.d//mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\n\n\n\n\n\n \n\n\nExit the root shell:\n\n\nroot$exit\n\n\n\n\n\n\n\nInstalling the Latest Release of Newt from a Binary Package\n\n\nFor Linux amd64 platform, you can install the latest stable version (1.0.0) of newt from the newt Debian binary package:\n\n\n$sudo apt-get update\n$sudo apt-get install newt\nReading package lists... Done\nBuilding dependency tree \nReading state information... Done\n\n ...\n\nPreparing to unpack .../newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSettin
g up newt (1.0.0-1) ...\n\n\n\n\n\n\nSee \nChecking the Installed Version of Newt\n to verify that you are using the installed version of newt.\n\n\n\n\nInstalling the Latest Stable Release of Newt from a Source Package\n\n\nIf you are running Linux on a different architecture, you can install the Debian source package for the latest stable release (1.0.0) of newt. The installation of the source package builds the newt binary and creates a Debian binary package that you then install.\n\n\nNote\n: Newt version 1.0.0 has been tested on Linux amd64 platform. Version 1.0.0 does not build on the 32 bit platform but have been fixed for the next release.\n\n\n\n\nInstalling Go 1.7\n\n\nYou need Go version 1.7 or higher to build Newt version 1.0.0. Currently, the latest Go version that Ubuntu installs is 1.6. Run \ngo version\n to check if you have Go 1.7 installed. \n\n\n\n\nInstall Go version 1.7:\n\n\n$sudo apt-get install golang-1.7-go\nReading package lists... Done\n ...\nUnpacki
ng golang-1.7-go (1.7.1-2ubuntu1) ...\nSetting up golang-1.7-go (1.7.1-2ubuntu1) ...\n$\n$sudo ln -sf ../lib/go-1.7/bin/go /usr/bin/go\n$go version\ngo version go1.7.1 linux/amd64\n\n\n\n\n\nYou can also download version 1.7 from \nhttps://golang.org/dl/\n. \n\n\n\n\nInstalling from the Source Package\n\n\nCreate a directory and change into the directory, download the source package, and build a binary package from the source package:\n\n\nmkdir newt_source\n$cd newt_source\n$sudo apt-get --build source newt\n[sudo] password for \nuser\n: \nReading package lists... Done\nNeed to get 1,866 kB of source archives.\nGet:1 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (dsc) [795 B]\nGet:2 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (tar) [1,864 kB]\nGet:3 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (diff) [2,000 B]\nFetched 1,866 kB in 1s (1,222 kB/s)\nd
pkg-source: warning: extracting unsigned source package (newt_1.0.0-1.dsc)\ndpkg-source: info: extracting newt in newt-1.0.0\ndpkg-source: info: unpacking newt_1.0.0.orig.tar.gz\ndpkg-source: info: unpacking newt_1.0.0-1.debian.tar.xz\n\n ...\n\ndpkg-deb: building package \nnewt\n in \n../newt_1.0.0-1_amd64.deb\n.\n dpkg-genchanges --build=any,all \n../newt_1.0.0-1_amd64.changes\ndpkg-genchanges: info: binary-only upload (no source code included)\n dpkg-source --after-build newt-1.0.0\ndpkg-buildpackage: info: binary-only upload (no source included)\nW: Can\nt drop privileges for downloading as file \nnewt_1.0.0-1.dsc\n couldn\nt be accessed by user \n_apt\n. - pkgAcquire::Run (13: Permission denied)\n\n\n\n\n\nNote:\n You can ignore the \"Permission denied: warning message at the end of the command.\n\n\n\nInstall the newt binary package that is created from the source package:\n\n\n$sudo dpkg -i newt_1.0.0-1_amd64.deb \nSelecting previously unselected package newt.\n(Rea
ding database ... 252969 files and directories currently installed.)\nPreparing to unpack newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.0-1) ...\n\n\n\n\n\n\n\n Checking the Installed Version of Newt\n\n\nAfter you have installed newt from either a Debian binary or source package, check that you are using the installed version of newt from \n/usr/bin\n. \n\n\nCheck the modification time of the binary and the newt tool that you are using:\n\n\n$ls -l /usr/bin/newt\n-rwxr-xr-x 1 root root 6919280 Apr 22 10:09 /usr/bin/newt\n$which newt\n/usr/bin/newt\n$newt version\nApache Newt (incubating) version: 1.0.0\n\n\n\n\n\nNote:\n If you previously built newt from source and the output of \nwhich newt\n shows \"$GOPATH/bin/newt\", you will need to move \"$GOPATH/bin\" after \"/usr/bin\" in your $PATH and export your $PATH.\n\n\n\nGet information about newt:\n\n\n$newt\nNewt allows you to create your own embedded application based on the Mynewt\noperating syst
em. Newt provides both build and package management in a single\ntool, which allows you to compose an embedded application, and set of\nprojects, and then build the necessary artifacts from those projects. For more\ninformation on the Mynewt operating system, please visit\nhttps://mynewt.apache.org/.\n\nPlease use the newt help command, and specify the name of the command you want\nhelp for, for help on how to use a specific command\n\nUsage:\n newt [flags]\n newt [command]\n\nExamples:\n newt\n newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\nAvailable Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image
commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing comm
ands\n\nUse \nnewt [command] --help\n for more information about a command.",
+ "text": "Installing Newt on Linux\n\n\nYou can install the latest stable release (1.0.0) of the newt tool from a Debian binary package (amd64) or from a Debian source package. This page shows you how to:\n\n\n\n\nSet up your computer to retrieve Debian packages from the runtimeco debian package repository.\n\n\nInstall the latest stable release version of newt from a Debian binary package. \n\n\nInstall the latest stable release version of newt from a Debian source package.\n\n\n\n\nIf you are installing on an amd64 platform, we recommend that you install from the binary package.\n\n\nNote:\n See \nSetting Up an Go Environment to Contribute to Newt and Newtmgr Tools\n if you want to: \n\n\n\n\nUse the newt tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.\n\n\nContribute to the newt tool. \n\n\n\n\n\n\nSetting Up Your Computer to Get Packages from runtimeco\n\n\nThe new
t Debian packages are stored in a private repository on \nhttps://github/runtimeco/debian-mynewt\n. The following steps must be performed on your computer to retreive packages from the repository:\n\n\nNote:\n You only need to perform this setup once on your computer.\n\n\n\n\nInstall the \napt-transport-https\n package to use HTTPS to retrieve packages. \n\n\nDownload the public key for the runtimeco debian repository and import the key into the apt keychain.\n\n\nAdd the repository for the binary and source packages to the apt source list.\n\n\n\n\n\nInstall the apt-transport-https package:\n\n\n$sudo apt-get update\n$sudo apt-get install apt-transport-https\n\n\n\n\n\n\n\nDownload the public key for the runtimeco apt repo (\nNote:\n There is a \n-\n after \napt-key add\n):\n\n\nwget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -\n\n\n\n\n\n\n\nAdd the repository for the binary and source packages to the \nmynewt.list\
n apt source list file.\n\n\n$sudo -s\n[sudo] password for \nuser\n:\nroot$ cat \n /etc/apt/sources.list.d/mynewt.list \nEOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\nEOF\nroot$exit\n\n\n\n\n\nNote:\n Do not forget to exit the root shell.\n\n\n\nVerify the content of the source list file:\n\n\n$more /etc/apt/sources.list.d/mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\n\n\n\n\n\n \n\n\nInstalling the Latest Release of Newt from a Binary Package\n\n\nFor Linux amd64 platforms, you can install the latest stable version (1.0.0) of newt from the newt Debian binary package:\n\n\n$sudo apt-get update\n$sudo apt-get install newt\nReading package lists... Done\nBuilding dependency tree \nReading state information... Done\n\n
...\n\nPreparing to unpack .../newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.0-1) ...\n\n\n\n\n\n\nSee \nChecking the Installed Version of Newt\n to verify that you are using the installed version of newt.\n\n\n\n\nInstalling the Latest Stable Release of Newt from a Source Package\n\n\nIf you are running Linux on a different architecture, you can install the Debian source package for the latest stable release (1.0.0) of newt. The installation of the source package builds the newt binary and creates a Debian binary package that you then install.\n\n\nNote\n: Newt version 1.0.0 has been tested on Linux amd64 platforms. Version 1.0.0 does not build on 32 bit platforms but have been fixed for the next release.\n\n\n\n\nInstalling Go 1.7\n\n\nYou need Go version 1.7 or higher to build Newt version 1.0.0. Currently, the latest Go version that Ubuntu installs is 1.6. Run \ngo version\n to check if you have Go 1.7 installed. \n\n\n\n\nInstall Go vers
ion 1.7:\n\n\n$sudo apt-get install golang-1.7-go\nReading package lists... Done\n ...\nUnpacking golang-1.7-go (1.7.1-2ubuntu1) ...\nSetting up golang-1.7-go (1.7.1-2ubuntu1) ...\n$\n$sudo ln -sf ../lib/go-1.7/bin/go /usr/bin/go\n$go version\ngo version go1.7.1 linux/amd64\n\n\n\n\n\nYou can also download version 1.7 from \nhttps://golang.org/dl/\n. \n\n\n\n\nInstalling from the Source Package\n\n\nCreate a directory and change into the directory, download the source package, and build a binary package from the source package:\n\n\nmkdir newt_source\n$cd newt_source\n$sudo apt-get --build source newt\n[sudo] password for \nuser\n: \nReading package lists... Done\nNeed to get 1,866 kB of source archives.\nGet:1 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (dsc) [795 B]\nGet:2 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (tar) [1,864 kB]\nGet:3 https://raw.githubusercontent.com/runtimeco/deb
ian-mynewt/master latest/main newt 1.0.0-1 (diff) [2,000 B]\nFetched 1,866 kB in 1s (1,222 kB/s)\ndpkg-source: warning: extracting unsigned source package (newt_1.0.0-1.dsc)\ndpkg-source: info: extracting newt in newt-1.0.0\ndpkg-source: info: unpacking newt_1.0.0.orig.tar.gz\ndpkg-source: info: unpacking newt_1.0.0-1.debian.tar.xz\n\n ...\n\ndpkg-deb: building package \nnewt\n in \n../newt_1.0.0-1_amd64.deb\n.\n dpkg-genchanges --build=any,all \n../newt_1.0.0-1_amd64.changes\ndpkg-genchanges: info: binary-only upload (no source code included)\n dpkg-source --after-build newt-1.0.0\ndpkg-buildpackage: info: binary-only upload (no source included)\nW: Can\nt drop privileges for downloading as file \nnewt_1.0.0-1.dsc\n couldn\nt be accessed by user \n_apt\n. - pkgAcquire::Run (13: Permission denied)\n\n\n\n\n\nNote:\n You can ignore the \"Permission denied\" warning message at the end of the command.\n\n\n\nInstall the newt binary package that is created from the source pack
age:\n\n\nNote:\n The file name for the binary package has the format: newt_1.0.0-1_\narch\n.deb, where \narch\n is a value that identifies your host architecture. \n\n\n$sudo dpkg -i newt_1.0.0-1_amd64.deb \nSelecting previously unselected package newt.\n(Reading database ... 252969 files and directories currently installed.)\nPreparing to unpack newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.0-1) ...\n\n\n\n\n\n\n\n Checking the Installed Version of Newt\n\n\nAfter you have installed newt from either a Debian binary or source package, check that you are using the installed version of newt from \n/usr/bin\n. \n\n\nCheck the modification time of the binary and the newt tool that you are using:\n\n\n$ls -l /usr/bin/newt\n-rwxr-xr-x 1 root root 6919280 Apr 22 10:09 /usr/bin/newt\n$which newt\n/usr/bin/newt\n$newt version\nApache Newt (incubating) version: 1.0.0\n\n\n\n\n\nNote:\n If you previously built newt from source and the output of \nwhich newt\
n shows \"$GOPATH/bin/newt\", you will need to move \"$GOPATH/bin\" after \"/usr/bin\" for your PATH environment variable and export it. \n\n\n\nGet information about newt:\n\n\n$newt\nNewt allows you to create your own embedded application based on the Mynewt\noperating system. Newt provides both build and package management in a single\ntool, which allows you to compose an embedded application, and set of\nprojects, and then build the necessary artifacts from those projects. For more\ninformation on the Mynewt operating system, please visit\nhttps://mynewt.apache.org/.\n\nPlease use the newt help command, and specify the name of the command you want\nhelp for, for help on how to use a specific command\n\nUsage:\n newt [flags]\n newt [command]\n\nExamples:\n newt\n newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\nAvailable Commands:\n build Build one or more targets\n clean Delete build artifacts for one o
r more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string
Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse \nnewt [command] --help\n for more information about a command.",
"title": "Install Newt on Linux"
},
{
"location": "/newt/install/newt_linux/#installing-newt-on-linux",
- "text": "You can install the latest stable release (1.0.0) of newt from a Debian binary package (amd64) or from a Debian source package. This page shows you how to: Set up your computer to retrieve Debian packages from the runtimeco debian package repository. Install the latest stable release version of newt from a Debian binary package. Install the latest stable release version of newt from a Debian source package. If you are running on an amd64 platform, we recommend that you install from the binary package. Note: See Setting Up an Go Environment to Contribute to Newt and Newtmgr Tools if you want to: Use the newt tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version. Contribute to the newt tool.",
+ "text": "You can install the latest stable release (1.0.0) of the newt tool from a Debian binary package (amd64) or from a Debian source package. This page shows you how to: Set up your computer to retrieve Debian packages from the runtimeco debian package repository. Install the latest stable release version of newt from a Debian binary package. Install the latest stable release version of newt from a Debian source package. If you are installing on an amd64 platform, we recommend that you install from the binary package. Note: See Setting Up an Go Environment to Contribute to Newt and Newtmgr Tools if you want to: Use the newt tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version. Contribute to the newt tool.",
"title": "Installing Newt on Linux"
},
{
"location": "/newt/install/newt_linux/#setting-up-your-computer-to-get-packages-from-runtimeco",
- "text": "The newt Debian packages are stored in a private repository on https://github/runtimeco/debian-mynewt . Note: You will only need to perform these steps only once on your computer.\nThe following steps must be performed on your computer: Add the apt-transport-https package to use HTTPS to retrieve packages. Download the public key for the runtimeco debian repository and import the key into the apt keychain. Add the repository for the binary and source packages to the apt source list. \nAdd the apt-transport-https package: $sudo apt-get update\n$sudo apt-get install apt-transport-https Download the public key for the runtimeco apt repo ( Note: There is - after the add): wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add - Add the repository for the binary and source packages to the apt source list: $sudo -s\n[sudo] password for user :\nroot$ cat /etc/apt/sources.list.d/mynewt.lis
t EOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\nEOF \nCheck the content of the file: root$more /etc/apt/sources.list.d//mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main Exit the root shell: root$exit",
+ "text": "The newt Debian packages are stored in a private repository on https://github/runtimeco/debian-mynewt . The following steps must be performed on your computer to retreive packages from the repository: Note: You only need to perform this setup once on your computer. Install the apt-transport-https package to use HTTPS to retrieve packages. Download the public key for the runtimeco debian repository and import the key into the apt keychain. Add the repository for the binary and source packages to the apt source list. \nInstall the apt-transport-https package: $sudo apt-get update\n$sudo apt-get install apt-transport-https Download the public key for the runtimeco apt repo ( Note: There is a - after apt-key add ): wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add - Add the repository for the binary and source packages to the mynewt.list apt source list file. $sudo -s\n[sudo] pas
sword for user :\nroot$ cat /etc/apt/sources.list.d/mynewt.list EOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\nEOF\nroot$exit Note: Do not forget to exit the root shell. \nVerify the content of the source list file: $more /etc/apt/sources.list.d/mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main",
"title": "Setting Up Your Computer to Get Packages from runtimeco"
},
{
"location": "/newt/install/newt_linux/#installing-the-latest-release-of-newt-from-a-binary-package",
- "text": "For Linux amd64 platform, you can install the latest stable version (1.0.0) of newt from the newt Debian binary package: $sudo apt-get update\n$sudo apt-get install newt\nReading package lists... Done\nBuilding dependency tree \nReading state information... Done\n\n ...\n\nPreparing to unpack .../newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.0-1) ... \nSee Checking the Installed Version of Newt to verify that you are using the installed version of newt.",
+ "text": "For Linux amd64 platforms, you can install the latest stable version (1.0.0) of newt from the newt Debian binary package: $sudo apt-get update\n$sudo apt-get install newt\nReading package lists... Done\nBuilding dependency tree \nReading state information... Done\n\n ...\n\nPreparing to unpack .../newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.0-1) ... \nSee Checking the Installed Version of Newt to verify that you are using the installed version of newt.",
"title": "Installing the Latest Release of Newt from a Binary Package"
},
{
"location": "/newt/install/newt_linux/#installing-the-latest-stable-release-of-newt-from-a-source-package",
- "text": "If you are running Linux on a different architecture, you can install the Debian source package for the latest stable release (1.0.0) of newt. The installation of the source package builds the newt binary and creates a Debian binary package that you then install. Note : Newt version 1.0.0 has been tested on Linux amd64 platform. Version 1.0.0 does not build on the 32 bit platform but have been fixed for the next release.",
+ "text": "If you are running Linux on a different architecture, you can install the Debian source package for the latest stable release (1.0.0) of newt. The installation of the source package builds the newt binary and creates a Debian binary package that you then install. Note : Newt version 1.0.0 has been tested on Linux amd64 platforms. Version 1.0.0 does not build on 32 bit platforms but have been fixed for the next release.",
"title": "Installing the Latest Stable Release of Newt from a Source Package"
},
{
@@ -252,10 +217,55 @@
},
{
"location": "/newt/install/newt_linux/#installing-from-the-source-package",
- "text": "Create a directory and change into the directory, download the source package, and build a binary package from the source package: mkdir newt_source\n$cd newt_source\n$sudo apt-get --build source newt\n[sudo] password for user : \nReading package lists... Done\nNeed to get 1,866 kB of source archives.\nGet:1 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (dsc) [795 B]\nGet:2 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (tar) [1,864 kB]\nGet:3 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (diff) [2,000 B]\nFetched 1,866 kB in 1s (1,222 kB/s)\ndpkg-source: warning: extracting unsigned source package (newt_1.0.0-1.dsc)\ndpkg-source: info: extracting newt in newt-1.0.0\ndpkg-source: info: unpacking newt_1.0.0.orig.tar.gz\ndpkg-source: info: unpacking newt_1.0.0-1.debian.tar.xz\n\n ...\n\ndpkg-deb: building package newt in
../newt_1.0.0-1_amd64.deb .\n dpkg-genchanges --build=any,all ../newt_1.0.0-1_amd64.changes\ndpkg-genchanges: info: binary-only upload (no source code included)\n dpkg-source --after-build newt-1.0.0\ndpkg-buildpackage: info: binary-only upload (no source included)\nW: Can t drop privileges for downloading as file newt_1.0.0-1.dsc couldn t be accessed by user _apt . - pkgAcquire::Run (13: Permission denied) Note: You can ignore the \"Permission denied: warning message at the end of the command. \nInstall the newt binary package that is created from the source package: $sudo dpkg -i newt_1.0.0-1_amd64.deb \nSelecting previously unselected package newt.\n(Reading database ... 252969 files and directories currently installed.)\nPreparing to unpack newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.0-1) ...",
+ "text": "Create a directory and change into the directory, download the source package, and build a binary package from the source package: mkdir newt_source\n$cd newt_source\n$sudo apt-get --build source newt\n[sudo] password for user : \nReading package lists... Done\nNeed to get 1,866 kB of source archives.\nGet:1 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (dsc) [795 B]\nGet:2 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (tar) [1,864 kB]\nGet:3 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (diff) [2,000 B]\nFetched 1,866 kB in 1s (1,222 kB/s)\ndpkg-source: warning: extracting unsigned source package (newt_1.0.0-1.dsc)\ndpkg-source: info: extracting newt in newt-1.0.0\ndpkg-source: info: unpacking newt_1.0.0.orig.tar.gz\ndpkg-source: info: unpacking newt_1.0.0-1.debian.tar.xz\n\n ...\n\ndpkg-deb: building package newt in
../newt_1.0.0-1_amd64.deb .\n dpkg-genchanges --build=any,all ../newt_1.0.0-1_amd64.changes\ndpkg-genchanges: info: binary-only upload (no source code included)\n dpkg-source --after-build newt-1.0.0\ndpkg-buildpackage: info: binary-only upload (no source included)\nW: Can t drop privileges for downloading as file newt_1.0.0-1.dsc couldn t be accessed by user _apt . - pkgAcquire::Run (13: Permission denied) Note: You can ignore the \"Permission denied\" warning message at the end of the command. \nInstall the newt binary package that is created from the source package: Note: The file name for the binary package has the format: newt_1.0.0-1_ arch .deb, where arch is a value that identifies your host architecture. $sudo dpkg -i newt_1.0.0-1_amd64.deb \nSelecting previously unselected package newt.\n(Reading database ... 252969 files and directories currently installed.)\nPreparing to unpack newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.
0-1) ...",
"title": "Installing from the Source Package"
},
{
+ "location": "/os/get_started/native_tools/",
+ "text": "Installing Native Mynewt Tools\n\n\nThis page shows how to install tools for native Mynewt targets (simulated targets on your laptop/computer) without using a Docker container. In other words, it allows you to run Mynewt OS as a native application on your Mac or Linux machine to simulate a target and use the Newt tool running natively on your machine to manage the simulated target. It also allows you to run the test suites for all packages not requiring HW support. You may choose to do this instead of using the build toolchain and Newt tool available in a Docker container.\n\n\nThis page provides guidance for MAC and Linux. See the relevant sections below.\n\n\n\n\nSet up toolchain for Mac\n\n\nInstall Brew\n\n\nIf you have not already installed Homebrew from the \n\nnewt\n tutorials pages\n, install it. \n\n\n\n\nInstall gcc/libc\n\n\nOS X ships with a C compiler called Clang. To build applications for the Mynewt simulator with, a different compiler is used as
default: gcc.\n\n\n$ brew install gcc\n...\n...\n==\n Summary\n\ud83c\udf7a /usr/local/Cellar/gcc/5.2.0: 1353 files, 248M\n\n\n\n\n\n\n\nCheck the gcc version you have installed (either using brew or previously installed). The brew-installed version can be checked using \nbrew list gcc\n. The default compiler.yml configuration file in Mynewt expects version 5.x for Mac users, so if the installed version is 6.x and you wish to continue with this newer version, modify the \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n file to change the default \ngcc-5\n defined there to \ngcc-6\n. In other words, replace the lines shown highlighted below:\n\n\n# OS X.\n\ncompiler.path.cc.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.as.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.objdump.DARWIN.OVERWRITE: \ngobjdump\n\ncompiler.path.objsize.DARWIN.OVERWRITE: \nobjsize\n\ncompiler.path.objcopy.DARWIN.OVERWRITE: \ngobjcopy\n\n\n\n\n\n\nwith the following:\n\n\ncompiler.p
ath.cc.DARWIN.OVERWRITE: \ngcc-6\n\ncompiler.path.as.DARWIN.OVERWRITE: \ngcc-6\u201d\n\n\n\n\n\n\n\nIn case you wish to use Clang, you can change your \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n to use Clang. Delete the gcc-5 DARWIN.OVERWRITE lines highlighted below.\n\n\n# OS X.\n\ncompiler.path.cc.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.as.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.objdump.DARWIN.OVERWRITE: \ngobjdump\n\ncompiler.path.objsize.DARWIN.OVERWRITE: \nobjsize\n\ncompiler.path.objcopy.DARWIN.OVERWRITE: \ngobjcopy\n\n\n\n\n\n\n\n\nNOTE:\n Both the newer gcc 6.x and Clang report a few warnings but they can be ignored.\n\n\n\n\nFURTHER NOTE:\n Mynewt developers mostly use gcc 5.x for sim builds; so it may take a little while to fix issues reported by the newer compiler. One option is to \ndisable warnings\n. To do that, remove the \n-Werror\n flag as an option for the compiler in the \nmynewt-src-directory\n/repos/apache-mynewt-core
/compiler/sim/compiler.yml\n file as shown below. \n\n\ncompiler.flags.base: \n\n\n -m32 -Wall -ggdb\n\n\n\n\n\nYou may alternatively choose to \nspecify the precise warnings to ignore\n depending on the error thrown by the compiler. For example, if you see a \n[-Werror=misleading-indentation]\n error while building the sim image, add \n-Wno-misleading-indentation]\n as a compiler flag in the same line from the \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n file.\n\n\ncompiler.flags.base: \n\n\n -m32 -Wall -Werror -ggdb -Wno-misleading-indentation\n\n\n\n\n\nA third option is to simply \ndowngrade to gcc 5.x\n.\n\n\n\n\nInstall gdb\n\n\n$ brew install gdb\n...\n...\n==\n Summary\n\ud83c\udf7a /usr/local/Cellar/gdb/7.10.1: XXX files,YYM\n\n\n\n\n\n\n\nNOTE:\n When running a program with gdb, you may need to sign your gdb\nexecutable. \nThis page\n\nshows a recipe for gdb signing. Alternately you can skip this step and\ncontinue without the abili
ty to debug your mynewt application on your PC.*\n\n\n\n\nSet up toolchain for Linux\n\n\nThe below procedure can be used to set up a Debian-based Linux system (e.g.,\nUbuntu). If you are running a different Linux distribution, you will need to\nsubstitute invocations of \napt-get\n in the below steps with the package manager\nthat your distro uses.\n\n\n\n\nInstall gcc/libc that will produce 32-bit executables:\n\n\n$ sudo apt-get install gcc-multilib libc6-i386\n\n\n\n\n\n\n\nInstall gdb\n\n\n$ sudo apt-get install gdb\n\nReading package lists... Done\nBuilding dependency tree \nReading state information... Done\nSuggested packages:\n gdb-doc gdbserver\nThe following NEW packages will be installed:\n gdb\n...\nProcessing triggers for man-db (2.6.7.1-1ubuntu1) ...\nSetting up gdb (7.7.1-0ubuntu5~14.04.2) ...\n\n\n\n\n\n\n\nAt this point you have installed all the necessary software to build and run your first project on a simluator on your Mac OS or Linux computer. You may
proceed to the \nCreate Your First Project\n section or continue to the next section and install the cross tools for ARM.",
+ "title": "Install Native Toolchain"
+ },
+ {
+ "location": "/os/get_started/native_tools/#installing-native-mynewt-tools",
+ "text": "This page shows how to install tools for native Mynewt targets (simulated targets on your laptop/computer) without using a Docker container. In other words, it allows you to run Mynewt OS as a native application on your Mac or Linux machine to simulate a target and use the Newt tool running natively on your machine to manage the simulated target. It also allows you to run the test suites for all packages not requiring HW support. You may choose to do this instead of using the build toolchain and Newt tool available in a Docker container. This page provides guidance for MAC and Linux. See the relevant sections below.",
+ "title": "Installing Native Mynewt Tools"
+ },
+ {
+ "location": "/os/get_started/native_tools/#set-up-toolchain-for-mac",
+ "text": "",
+ "title": "Set up toolchain for Mac"
+ },
+ {
+ "location": "/os/get_started/native_tools/#install-brew",
+ "text": "If you have not already installed Homebrew from the newt tutorials pages , install it.",
+ "title": "Install Brew"
+ },
+ {
+ "location": "/os/get_started/native_tools/#install-gcclibc",
+ "text": "OS X ships with a C compiler called Clang. To build applications for the Mynewt simulator with, a different compiler is used as default: gcc. $ brew install gcc\n...\n...\n== Summary\n\ud83c\udf7a /usr/local/Cellar/gcc/5.2.0: 1353 files, 248M Check the gcc version you have installed (either using brew or previously installed). The brew-installed version can be checked using brew list gcc . The default compiler.yml configuration file in Mynewt expects version 5.x for Mac users, so if the installed version is 6.x and you wish to continue with this newer version, modify the mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml file to change the default gcc-5 defined there to gcc-6 . In other words, replace the lines shown highlighted below: # OS X. compiler.path.cc.DARWIN.OVERWRITE: gcc-5 compiler.path.as.DARWIN.OVERWRITE: gcc-5 compiler.path.objdump.DARWIN.OVERWRITE: gobjdump \ncompiler.path.objsize.DARWIN.OVERWRITE: objsize
\ncompiler.path.objcopy.DARWIN.OVERWRITE: gobjcopy with the following: compiler.path.cc.DARWIN.OVERWRITE: gcc-6 \ncompiler.path.as.DARWIN.OVERWRITE: gcc-6\u201d In case you wish to use Clang, you can change your mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml to use Clang. Delete the gcc-5 DARWIN.OVERWRITE lines highlighted below. # OS X. compiler.path.cc.DARWIN.OVERWRITE: gcc-5 compiler.path.as.DARWIN.OVERWRITE: gcc-5 compiler.path.objdump.DARWIN.OVERWRITE: gobjdump \ncompiler.path.objsize.DARWIN.OVERWRITE: objsize \ncompiler.path.objcopy.DARWIN.OVERWRITE: gobjcopy NOTE: Both the newer gcc 6.x and Clang report a few warnings but they can be ignored. FURTHER NOTE: Mynewt developers mostly use gcc 5.x for sim builds; so it may take a little while to fix issues reported by the newer compiler. One option is to disable warnings . To do that, remove the -Werror flag as an option for the compiler in the mynewt-src-directory /repos/apa
che-mynewt-core/compiler/sim/compiler.yml file as shown below. compiler.flags.base: -m32 -Wall -ggdb You may alternatively choose to specify the precise warnings to ignore depending on the error thrown by the compiler. For example, if you see a [-Werror=misleading-indentation] error while building the sim image, add -Wno-misleading-indentation] as a compiler flag in the same line from the mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml file. compiler.flags.base: -m32 -Wall -Werror -ggdb -Wno-misleading-indentation A third option is to simply downgrade to gcc 5.x .",
+ "title": "Install gcc/libc"
+ },
+ {
+ "location": "/os/get_started/native_tools/#install-gdb",
+ "text": "$ brew install gdb\n...\n...\n== Summary\n\ud83c\udf7a /usr/local/Cellar/gdb/7.10.1: XXX files,YYM NOTE: When running a program with gdb, you may need to sign your gdb\nexecutable. This page \nshows a recipe for gdb signing. Alternately you can skip this step and\ncontinue without the ability to debug your mynewt application on your PC.*",
+ "title": "Install gdb"
+ },
+ {
+ "location": "/os/get_started/native_tools/#set-up-toolchain-for-linux",
+ "text": "The below procedure can be used to set up a Debian-based Linux system (e.g.,\nUbuntu). If you are running a different Linux distribution, you will need to\nsubstitute invocations of apt-get in the below steps with the package manager\nthat your distro uses.",
+ "title": "Set up toolchain for Linux"
+ },
+ {
+ "location": "/os/get_started/native_tools/#install-gcclibc-that-will-produce-32-bit-executables",
+ "text": "$ sudo apt-get install gcc-multilib libc6-i386",
+ "title": "Install gcc/libc that will produce 32-bit executables:"
+ },
+ {
+ "location": "/os/get_started/native_tools/#install-gdb_1",
+ "text": "$ sudo apt-get install gdb\n\nReading package lists... Done\nBuilding dependency tree \nReading state information... Done\nSuggested packages:\n gdb-doc gdbserver\nThe following NEW packages will be installed:\n gdb\n...\nProcessing triggers for man-db (2.6.7.1-1ubuntu1) ...\nSetting up gdb (7.7.1-0ubuntu5~14.04.2) ... At this point you have installed all the necessary software to build and run your first project on a simluator on your Mac OS or Linux computer. You may proceed to the Create Your First Project section or continue to the next section and install the cross tools for ARM.",
+ "title": "Install gdb"
+ },
+ {
"location": "/os/get_started/cross_tools/",
"text": "Installing Cross Tools for ARM\n\n\nThis page shows how to install tools on your laptop/computer to use for direct communication (e.g. for debugging) with some ARM based HW platforms running Apache Mynewt. It shows you how to install the following tools for Mac OS X and Linux:\n\n\n\n\nARM Cross toolchain\n\n\nDebugger to load and debug your device\n\n\n\n\n\n\nInstall ARM Cross Toolchain\n\n\nInstall ARM Toolchain For Mac OS X\n\n\nInstall the PX4 Toolchain and check the version installed. ARM maintains a\npre-built GNU toolchain with a GCC source branch targeted at Embedded ARM\nProcessors, namely Cortex-R/Cortex-M processor families. After installing,\nensure that the symbolic link installed by Homebrew points to the correct\nversion of the debugger.\n\n\n$ brew tap PX4/homebrew-px4\n$ brew update\n$ brew install gcc-arm-none-eabi-49\n$ arm-none-eabi-gcc --version \narm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 4.9.3 20150529 (release) [ARM/embe
dded-4_9-branch revision 224288]\nCopyright (C) 2014 Free Software Foundation, Inc.\nThis is free software; see the source for copying conditions. There is NO\nwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.\n$ ls -al /usr/local/bin/arm-none-eabi-gdb\nlrwxr-xr-x 1 aditihilbert admin 69 Sep 22 17:16 /usr/local/bin/arm-none-eabi-gdb -\n /usr/local/Cellar/gcc-arm-none-eabi-49/20150609/bin/arm-none-eabi-gdb\n\n\n\n\n\nNote:\n If no version is specified, brew will install the latest version\navailable. Mynewt OS will eventually work with multiple versions available,\nincluding the latest releases. However, at present we have tested only with\nthis version and recommend it for getting started. \n\n\n\n\nInstall ARM Toolchain For Linux\n\n\nOn a Debian-based Linux distribution, gcc 4.9.3 for ARM can be installed with\napt-get as documented below. The steps are explained in depth at\n\nhttps://launchpad.net/~team-gcc-arm-embedded/+archive/ubuntu/ppa\n.\n\n\n$
sudo apt-get remove binutils-arm-none-eabi gcc-arm-none-eabi \n$ sudo add-apt-repository ppa:team-gcc-arm-embedded/ppa\n$ sudo apt-get update \n$ sudo apt-get install gcc-arm-none-eabi\n$ sudo apt-get install gdb-arm-none-eabi\n\n\n\n\n\n\n\nInstall Debugger\n\n\nMynewt uses, depending on the board, either the OpenOCD or SEGGER J-Link debugger. \n\n\nInstall OpenOCD\n\n\nOpenOCD (Open On-Chip Debugger) is open-source software that allows your\ncomputer to interface with the JTAG debug connector on a variety of boards. A\nJTAG connection lets you debug and test embedded target devices. For more on\nOpenOCD go to \nhttp://openocd.org\n.\n\n\nOpenOCD version 0.10.0 with nrf52 support is required. A binary for this version is available to download for Mac OS and Linux.\n\n\n\n\nInstall OpenOCD on Mac OS\n\n\nStep 1: Download the \nbinary tarball for Mac OS\n.\n\n\nStep 2: Change to the root directory: \n\n\n$cd / \n\n\n\n\n\n\nStep 3: Untar the tarball and install into \n /usr/local/
bin\n. You will need to replace \n ~/Downloads \n with the directory that the tarball is downloaded to. \n\n\nsudo tar -xf ~/Downloads/openocd-bin-0.10.0-MacOS.tgz ` \n\n\n\n\n\n\nStep 4: Check the OpenOCD version you are using: \n\n\n$which openocd\n/usr/local/bin/openocd\n$openocd -v\nOpen On-Chip Debugger 0.10.0\nLicensed under GNU GPL v2\nFor bug reports, read\nhttp://openocd.org/doc/doxygen/bugs.html\n\n\n\n\n\nYou should see version: \n0.10.0\n. \n\n\n\n\nInstall OpenOCD on Linux\n\n\nStep 1: Download the \nbinary tarball for Linux\n\n\nStep 2: Change to the root directory: \n\n\n$cd / \n\n\n\n\n\n\nStep 3: Untar the tarball and install into \n /usr/local/bin\n. You will need to replace \n ~/Downloads \n with the directory that the tarball is downloaded to. \n\n\n Note:\n You must specify the -p option for the tar command.\n\n\n$sudo tar -xpf ~/Downloads/openocd-bin-0.10.0-Linux.tgz\n\n\n\n\n\n\nStep 4: Check the OpenOCD version you are using: \n\n\n$which openocd\n/usr/lo
cal/bin/openocd\n$openocd -v\nOpen On-Chip Debugger 0.10.0\nLicensed under GNU GPL v2\nFor bug reports, read\nhttp://openocd.org/doc/doxygen/bugs.html\n\n\n\n\n\nYou should see version: \n0.10.0\n. \n\n\nIf you see any of these error messages:\n\n\n\n\n\n\nopenocd: error while loading shared libraries: libhidapi-hidraw.so.0: cannot open shared object file: No such file or directory\n\n\n\n\n\n\nopenocd: error while loading shared libraries: libusb-1.0.so.0: cannot open shared object file: No such file or directory \n\n\n\n\n\n\nrun the following command to install the libraries: \n\n\n$sudo apt-get install libhidapi-dev:i386\n\n\n\n\n\n\n\nInstall SEGGAR J-Link\n\n\nYou can download and install Segger J-LINK Software and documentation pack from \nSEGGER\n.",
"title": "Install Cross Tools for ARM"
@@ -352,7 +362,7 @@
},
{
"location": "/os/get_started/project_create/",
- "text": "Create Your First Mynewt Project\n\n\nThis page shows how to create a Mynewt Project using the \nnewt\n command-line tool.\n\n\n\n\nPre-Requisites\n\n\n\n\nNewt:\n\n\nIf you have taken the Docker route, you have already installed Newt.\n\n\nIf you have taken the native install route, you have to ensure that you have installed the Newt tool following the instructions for \nMac\n or \nLinux\n as appropriate, and that the \nnewt\n command is in your system path. \n\n\n\n\n\n\nYou must have Internet connectivity to fetch remote Mynewt components.\n\n\nYou must \ninstall the compiler tools\n to \nsupport native compiling to build the project this tutorial creates. \n\n\n\n\n\n\nNewt New\n\n\nChoose a project name. For this tutorial we will call this project \nmyproj\n.\nEnter the \nnewt new myproj\n command. \n\n\n$ newt new myproj\nDownloading project skeleton from apache/incubator-mynewt-blinky...\nInstalling skeleton in myproj...\nProject myproj successfully crea
ted.\n\n\n\n\n\n\n\nNewt populates this new project with a base skeleton of a new Apache Mynewt \nproject. It has the following structure. \n\n\nNote\n: If you do not have \ntree\n, install it by running \nbrew install tree\n.\n\n\n$ cd myproj\n$ tree \n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\u2500\u2500 README.md\n\u251c\u2500\u2500 apps\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 pkg.yml\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 src\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 main.c\n\u251c\u2500\u2500 project.yml\n\u2514\u2500\u2500 targets\n \u251c\u2500\u2500 my_blinky_sim\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 pkg.yml\n \u2502\u00a0\u00a0 \u2514\u2500\u2500 target.yml\n \u2514\u2500\u2500 unittest\n \u251c\u2500\u2500 pkg.yml\n \u2514\u2500\u2500 target.yml\n\n6 directories, 11 files\n\n\n\n\n\n\n\nThe Newt tool has installed the base files for a
project comprising the following:\n\n\n\n\nThe file \nproject.yml\n contains the repository list that the project uses to fetch\nits packages. Your project is a collection of repositories. In this case, the project just\ncomprises the core mynewt repository. Later you will add more repositories\nto include other mynewt components.\n\n\nThe file \napps/blinky/pkg.yml\n contains the description of your application\nand its package dependencies.\n\n\nA \ntarget\n directory containing \nmy_blinky_sim\n, a target descriptor used to\nbuild a version of myproj. Use \nnewt target show\n to see available build \ntargets.\n\n\nA non-buildable target called \nunittest\n. This is used internally by \nnewt\n and is not a formal build target.\n\n\n\n\nNOTE:\n The actual code and package files are not installed \n(except the template for \nmain.c\n). See the next step for installing the packages.\n\n\nNOTE:\n By default newt uses the code in the master branch. This is the latest stable\ncode
for newt. If you need to use a different branch, you can set this in the project.yml\nfile. \n\n\nrepository.apache-mynewt-core:\n type: github\n vers: 1-latest\n user: apache\n repo: incubator-mynewt-core\n\n\n\n\n\nChanging to 0-dev will put you on the latest master branch. \nThis 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 vi
ew 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\u250
2\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\u250
2\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\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\u25
00\u2500 stats\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 sysinit\n\u251c\u2500\u2500 targets\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 unittest\n\u251c\u2500\u2500 test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 crash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 flash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 runtest\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 testutil\n\u251c\u2500\u2500 time\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 datetime\n\u2514\u2500\u2500 util\n \u251c\u2500\u2500 cbmem\n \u251c\u2500\u2500 crc\n \u2514\u2500\u2500 mem\n\n94 directories, 9 files\n\n\n\n\n\nAs you can see, the core of the Apache Mynewt operating system has been brought \ninto your local directory. \n\n\n\n\nTest the project's packages\n\n\nYou have already built your first basic project. You can ask Newt to execute the unit tests in a package. For example, to test the \nsys/config\n package in the \napache-mynewt-core\n repo, call newt as shown below.\n\n\n$ newt test @apache-mynewt-core/sys/config\n
Testing 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/ap
ache-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 u
ninstall gcc-6\n$ brew link gcc-5\n\n\n\n\n\n\n\nTo test all the packages in a project, specify \nall\n instead of the package name.\n\n\n$ newt test all\nTesting package @apache-mynewt-core/boot/boot_serial/test\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/boot_test.c\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/testcases/boot_serial_setup.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/boot_boot_serial_test/app/boot/boot_serial/test/boot_boot_serial_test.elf\n\n...lots of compiling and testing...\n\nLinking ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nPassed tests: [boot/boot_serial/test boot/bootutil/test crypto/mbedtls/test encoding/base64/test encoding/cborattr/test encoding/json/test fs/fcb/test fs/nffs/test kernel/os/test net/ip/mn_socket/test net/nimble/host/test net/oic/test sys/
config/test-fcb sys/config/test-nffs sys/flash_map/test sys/log/full/test util/cbmem/test]\nAll tests passed\n\n\n\n\n\n\n\nBuild the Project\n\n\nTo build and run your new application, simply issue the following command:\n\n\n$ newt build my_blinky_sim \nBuilding target targets/my_blinky_sim\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_common.c\nCompiling repos/apache-mynewt-core/hw/drivers/uart/src/uart.c\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c\nCompiling repos/apache-mynewt-core/hw/bsp/native/src/hal_bsp.c\nCompiling repos/apache-mynewt-core/hw/drivers/uart/uart_hal/src/uart_hal.c\nCompiling apps/blinky/src/main.c\n\n ...\n\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nTarget successfully built: targets/my_blinky_sim\n\n\n\n\n\n\n\nRun the Project\n\n\nYou can run the simulated version of your project and see the simulated LED\nblink. If you are using ne
wt docker, use \nnewt run\n to run the simulated binary.\n\n\n$ newt run my_blinky_sim\nLoading app image into slot 1\n ...\nDebugging ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\n ...\nReading symbols from /bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf...done.\n(gdb)\n\n\n\n\n\nType \nr\n at the \n(gdb)\n prompt to run the project. You will see an output indicating that the hal_gpio pin is toggling between 1 and 0 in a simulated blink.\n\n\nIf you natively install the toolchain, you can either use \nnewt run\n or call the binary directly. Generally, \nnewt run\n is the expected way to call things.\n\n\n$ ./bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nhal_gpio set pin 1 to 0\n\n\n\n\n\n\n\nComplete\n\n\nCongratulations, you have created your first project! The blinky application\nis not terribly exciting when it is run in the simulator, as there is no LED to\nblink. Apache Mynewt has a lot more functionality than just running simulated\
napplications. It provides all the features you'll need to cross-compile your\napplication, run it on real hardware and develop a full featured application.\n\n\nIf you're interested in learning more, a good next step is to dig in to one of\nthe \ntutorials\n and get a Mynewt project running on real hardware.\n\n\nHappy Hacking!",
+ "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\nPrerequisites\n\n\n\n\nHave Internet connectivity to fetch remote Mynewt components.\n\n\nInstall Newt:\n\n\nIf you have taken the native install route, see the installation instructions for \nMac OS\n or for \nLinux\n. \n\n\nIf you have taken the Docker route, you have already installed Newt.\n\n\n\n\n\n\nInstall the \nnative toolchain\n to compile and build a Mynewt native application. \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 created.\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, run \nbrew install tree\n to install on Mac OS or run \nsudo apt-get install tree\n to install on Linux.\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 rep
ository 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 0-dev will put you on the latest master branch. \nThis 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 view them by issuing the following commands in the base directory of the new project. T
he 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\u2502\u00a0\u00a0 \u251c\u2500\u2500 ocf_sample\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 sl
inky\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\u2502\u00a0\u00a0 \u2514\u2500\u2500 tinycrypt\n\u251c\u2500\u2500 docs\n\u2502\u00a0\u00
a0 \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\u2500\u2500 baselibc\n\u251c\u2500\u2500 mgmt\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 imgmg
r\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 tar
gets\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 unittest\n\u251c\u2500\u2500 test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 crash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 flash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 runtest\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 testutil\n\u251c\u2500\u2500 time\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 datetime\n\u2514\u2500\u2500 util\n \u251c\u2500\u2500 cbmem\n \u251c\u2500\u2500 crc\n \u2514\u2500\u2500 mem\n\n94 directories, 9 files\n\n\n\n\n\nAs you can see, the core of the Apache Mynewt operating system has been brought \ninto your local directory. \n\n\n\n\nTest the project's packages\n\n\nYou have already built your first basic project. You can ask Newt to execute the unit tests in a package. For example, to test the \nsys/config\n package in the \napache-mynewt-core\n repo, call newt as shown below.\n\n\n$ newt test @apache-mynewt-core/sys/config\nTesting package @apache-mynewt-core/sys/config/test-fcb\nCompiling bootutil_misc.c\nC
ompiling image_ec.c\nCompiling image_rsa.c\nCompiling image_validate.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nTesting package @apache-mynewt-core/sys/config/test-nffs\nCompiling repos/apache-mynewt-core/encoding/base64/src/hex.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_cli.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_dirent.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_mkdir.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_mount.c\nCompiling repos/apache-mynewt-core/encoding/base64/src/base64.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_file.c\nCompiling repos/apache-mynewt-core/fs/disk/src/disk.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_nmgr.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fsutil.c\nCompiling repos/apache-mynewt-core/fs/nffs/src/n
ffs.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nPassed tests: [sys/config/test-fcb sys/config/test-nffs]\nAll tests passed\n\n\n\n\n\nNOTE:\n If you've installed the latest gcc using homebrew on your Mac, you will likely be running gcc-6. Make sure you have adjusted the compiler.yml configuration to reflect that as noted in \nNative Install Option\n. You can choose to downgrade to gcc-5 in order to use the default gcc compiler configuration for MyNewt.\n\n\nNOTE:\n If you are running the standard gcc for 64-bit machines, it does not support 32-bit. In that case you will see compilation errors. You need to install multiboot gcc (e.g. gcc-multilib if you running on a 64-bit Ubuntu).\n\n\n$ brew uninstall gcc-6\n$ brew link gcc-5\n\n\n\n\n\n\n\nTo test all the packages in a projec
t, specify \nall\n instead of the package name.\n\n\n$ newt test all\nTesting package @apache-mynewt-core/boot/boot_serial/test\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/boot_test.c\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/testcases/boot_serial_setup.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/boot_boot_serial_test/app/boot/boot_serial/test/boot_boot_serial_test.elf\n\n...lots of compiling and testing...\n\nLinking ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nPassed tests: [boot/boot_serial/test boot/bootutil/test crypto/mbedtls/test encoding/base64/test encoding/cborattr/test encoding/json/test fs/fcb/test fs/nffs/test kernel/os/test net/ip/mn_socket/test net/nimble/host/test net/oic/test sys/config/test-fcb sys/config/test-nffs sys/flash_map/test sys/log/full/test util/cbmem/
test]\nAll tests passed\n\n\n\n\n\n\n\nBuild the Project\n\n\nTo build and run your new application, simply issue the following command:\n\n\n$ newt build my_blinky_sim \nBuilding target targets/my_blinky_sim\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_common.c\nCompiling repos/apache-mynewt-core/hw/drivers/uart/src/uart.c\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c\nCompiling repos/apache-mynewt-core/hw/bsp/native/src/hal_bsp.c\nCompiling repos/apache-mynewt-core/hw/drivers/uart/uart_hal/src/uart_hal.c\nCompiling apps/blinky/src/main.c\n\n ...\n\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nTarget successfully built: targets/my_blinky_sim\n\n\n\n\n\n\n\nRun the Project\n\n\nYou can run the simulated version of your project and see the simulated LED\nblink. If you are using newt docker, use \nnewt run\n to run the simulated binary.\n\n\n$ newt run my_blinky_si
m\nLoading app image into slot 1\n ...\nDebugging ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\n ...\nReading symbols from /bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf...done.\n(gdb)\n\n\n\n\n\nType \nr\n at the \n(gdb)\n prompt to run the project. You will see an output indicating that the hal_gpio pin is toggling between 1 and 0 in a simulated blink.\n\n\nIf you natively install the toolchain, you can either use \nnewt run\n or call the binary directly. Generally, \nnewt run\n is the expected way to call things.\n\n\n$ ./bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nhal_gpio set pin 1 to 0\n\n\n\n\n\n\n\nComplete\n\n\nCongratulations, you have created your first project! The blinky application\nis not terribly exciting when it is run in the simulator, as there is no LED to\nblink. Apache Mynewt has a lot more functionality than just running simulated\napplications. It provides all the features you'll need to cross-compile your\nappli
cation, 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"
},
{
@@ -361,13 +371,13 @@
"title": "Create Your First Mynewt Project"
},
{
- "location": "/os/get_started/project_create/#pre-requisites",
- "text": "Newt: If you have taken the Docker route, you have already installed Newt. If you have taken the native install route, you have to ensure that you have installed the Newt tool following the instructions for Mac or Linux as appropriate, and that the newt command is in your system path. You must have Internet connectivity to fetch remote Mynewt components. You must install the compiler tools to \nsupport native compiling to build the project this tutorial creates.",
- "title": "Pre-Requisites"
+ "location": "/os/get_started/project_create/#prerequisites",
+ "text": "Have Internet connectivity to fetch remote Mynewt components. Install Newt: If you have taken the native install route, see the installation instructions for Mac OS or for Linux . If you have taken the Docker route, you have already installed Newt. Install the native too
<TRUNCATED>
[6/7] incubator-mynewt-site git commit: changed runtimeinc to
runtimeco in docs, updated install instructions for linux ,
blinky for stm32F4-discovery
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/mkdocs/search_index.json
----------------------------------------------------------------------
diff --git a/develop/mkdocs/search_index.json b/develop/mkdocs/search_index.json
index 4de7a25..808a034 100644
--- a/develop/mkdocs/search_index.json
+++ b/develop/mkdocs/search_index.json
@@ -146,49 +146,14 @@
"title": "Quick Start"
},
{
- "location": "/os/get_started/native_tools/",
- "text": "Installing Native Mynewt Tools\n\n\nThis page shows how to install tools for native Mynewt targets (simulated targets on your laptop/computer) without using a Docker container. In other words, it allows you to run Mynewt OS as a native application on your Mac or Linux machine to simulate a target and use the Newt tool running natively on your machine to manage the simulated target. It also allows you to run the test suites for all packages not requiring HW support. You may choose to do this instead of using the build toolchain and Newt tool available in a Docker container.\n\n\nThis page provides guidance for MAC and Linux. See the relevant sections below.\n\n\n\n\nSet up toolchain for Mac\n\n\nInstall Brew\n\n\nIf you have not already installed Homebrew from the \n\nnewt\n tutorials pages\n, install it. \n\n\n\n\nInstall gcc/libc\n\n\nOS X ships with a C compiler called Clang. To build applications for the Mynewt simulator with, a different compiler is used as
default: gcc.\n\n\n$ brew install gcc\n...\n...\n==\n Summary\n\ud83c\udf7a /usr/local/Cellar/gcc/5.2.0: 1353 files, 248M\n\n\n\n\n\n\n\nCheck the gcc version you have installed (either using brew or previously installed). The brew-installed version can be checked using \nbrew list gcc\n. The default compiler.yml configuration file in Mynewt expects version 5.x for Mac users, so if the installed version is 6.x and you wish to continue with this newer version, modify the \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n file to change the default \ngcc-5\n defined there to \ngcc-6\n. In other words, replace the lines shown highlighted below:\n\n\n# OS X.\n\ncompiler.path.cc.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.as.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.objdump.DARWIN.OVERWRITE: \ngobjdump\n\ncompiler.path.objsize.DARWIN.OVERWRITE: \nobjsize\n\ncompiler.path.objcopy.DARWIN.OVERWRITE: \ngobjcopy\n\n\n\n\n\n\nwith the following:\n\n\ncompiler.p
ath.cc.DARWIN.OVERWRITE: \ngcc-6\n\ncompiler.path.as.DARWIN.OVERWRITE: \ngcc-6\u201d\n\n\n\n\n\n\n\nIn case you wish to use Clang, you can change your \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n to use Clang. Delete the gcc-5 DARWIN.OVERWRITE lines highlighted below.\n\n\n# OS X.\n\ncompiler.path.cc.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.as.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.objdump.DARWIN.OVERWRITE: \ngobjdump\n\ncompiler.path.objsize.DARWIN.OVERWRITE: \nobjsize\n\ncompiler.path.objcopy.DARWIN.OVERWRITE: \ngobjcopy\n\n\n\n\n\n\n\n\nNOTE:\n Both the newer gcc 6.x and Clang report a few warnings but they can be ignored.\n\n\n\n\nFURTHER NOTE:\n Mynewt developers mostly use gcc 5.x for sim builds; so it may take a little while to fix issues reported by the newer compiler. One option is to \ndisable warnings\n. To do that, remove the \n-Werror\n flag as an option for the compiler in the \nmynewt-src-directory\n/repos/apache-mynewt-core
/compiler/sim/compiler.yml\n file as shown below. \n\n\ncompiler.flags.base: \n\n\n -m32 -Wall -ggdb\n\n\n\n\n\nYou may alternatively choose to \nspecify the precise warnings to ignore\n depending on the error thrown by the compiler. For example, if you see a \n[-Werror=misleading-indentation]\n error while building the sim image, add \n-Wno-misleading-indentation]\n as a compiler flag in the same line from the \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n file.\n\n\ncompiler.flags.base: \n\n\n -m32 -Wall -Werror -ggdb -Wno-misleading-indentation\n\n\n\n\n\nA third option is to simply \ndowngrade to gcc 5.x\n.\n\n\n\n\nInstall gdb\n\n\n$ brew install gdb\n...\n...\n==\n Summary\n\ud83c\udf7a /usr/local/Cellar/gdb/7.10.1: XXX files,YYM\n\n\n\n\n\n\n\nNOTE:\n When running a program with gdb, you may need to sign your gdb\nexecutable. \nThis page\n\nshows a recipe for gdb signing. Alternately you can skip this step and\ncontinue without the abili
ty to debug your mynewt application on your PC.*\n\n\n\n\nSet up toolchain for Linux\n\n\nThe below procedure can be used to set up a Debian-based Linux system (e.g.,\nUbuntu). If you are running a different Linux distribution, you will need to\nsubstitute invocations of \napt-get\n in the below steps with the package manager\nthat your distro uses.\n\n\n\n\nInstall gcc/libc that will produce 32-bit executables:\n\n\n$ sudo apt-get install gcc-multilib libc6-i386\n\n\n\n\n\n\n\nInstall gdb\n\n\n$ sudo apt-get install gdb\n\nReading package lists... Done\nBuilding dependency tree \nReading state information... Done\nSuggested packages:\n gdb-doc gdbserver\nThe following NEW packages will be installed:\n gdb\n...\nProcessing triggers for man-db (2.6.7.1-1ubuntu1) ...\nSetting up gdb (7.7.1-0ubuntu5~14.04.2) ...\n\n\n\n\n\n\n\nAt this point you have installed all the necessary software to build and test code on a simluator running on your Mac or Linux. Proceed to the \nCreate
Your First Project\n section.",
+ "location": "/os/get_started/native_install_intro/",
+ "text": "Native Installation\n\n\nThis section shows you how to install tools on Mac OS and Linux platforms to develop, build, run, and debug Mynewt OS applications. You can build Mynewt OS applications to run as a native application on your computer or to run on your target board. These tools include:\n\n\n\n\n\n\nNewt tool - Tool to create, build, load, and debug a mynewt target.\n\n\n\n\nSee \nInstalling the Newt Tool on Mac OS\n to install on Mac OS.\n\n\nSee \nInstalling the Newt Tool on Linux\n to install on Linux.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nNative toolchain - Native toolchain to build and run Mynewt OS as a native application on your computer.\n (See \nInstalling Native Toolchain\n). \n\n\n\n\n\n\nCross toolchain for ARM - Cross toolchain for ARM to build and run a Mynewt OS application on a target board\n (See \nInstalling Cross Tools for ARMs\n).",
"title": "toc"
},
{
- "location": "/os/get_started/native_tools/#installing-native-mynewt-tools",
- "text": "This page shows how to install tools for native Mynewt targets (simulated targets on your laptop/computer) without using a Docker container. In other words, it allows you to run Mynewt OS as a native application on your Mac or Linux machine to simulate a target and use the Newt tool running natively on your machine to manage the simulated target. It also allows you to run the test suites for all packages not requiring HW support. You may choose to do this instead of using the build toolchain and Newt tool available in a Docker container. This page provides guidance for MAC and Linux. See the relevant sections below.",
- "title": "Installing Native Mynewt Tools"
- },
- {
- "location": "/os/get_started/native_tools/#set-up-toolchain-for-mac",
- "text": "",
- "title": "Set up toolchain for Mac"
- },
- {
- "location": "/os/get_started/native_tools/#install-brew",
- "text": "If you have not already installed Homebrew from the newt tutorials pages , install it.",
- "title": "Install Brew"
- },
- {
- "location": "/os/get_started/native_tools/#install-gcclibc",
- "text": "OS X ships with a C compiler called Clang. To build applications for the Mynewt simulator with, a different compiler is used as default: gcc. $ brew install gcc\n...\n...\n== Summary\n\ud83c\udf7a /usr/local/Cellar/gcc/5.2.0: 1353 files, 248M Check the gcc version you have installed (either using brew or previously installed). The brew-installed version can be checked using brew list gcc . The default compiler.yml configuration file in Mynewt expects version 5.x for Mac users, so if the installed version is 6.x and you wish to continue with this newer version, modify the mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml file to change the default gcc-5 defined there to gcc-6 . In other words, replace the lines shown highlighted below: # OS X. compiler.path.cc.DARWIN.OVERWRITE: gcc-5 compiler.path.as.DARWIN.OVERWRITE: gcc-5 compiler.path.objdump.DARWIN.OVERWRITE: gobjdump \ncompiler.path.objsize.DARWIN.OVERWRITE: objsize
\ncompiler.path.objcopy.DARWIN.OVERWRITE: gobjcopy with the following: compiler.path.cc.DARWIN.OVERWRITE: gcc-6 \ncompiler.path.as.DARWIN.OVERWRITE: gcc-6\u201d In case you wish to use Clang, you can change your mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml to use Clang. Delete the gcc-5 DARWIN.OVERWRITE lines highlighted below. # OS X. compiler.path.cc.DARWIN.OVERWRITE: gcc-5 compiler.path.as.DARWIN.OVERWRITE: gcc-5 compiler.path.objdump.DARWIN.OVERWRITE: gobjdump \ncompiler.path.objsize.DARWIN.OVERWRITE: objsize \ncompiler.path.objcopy.DARWIN.OVERWRITE: gobjcopy NOTE: Both the newer gcc 6.x and Clang report a few warnings but they can be ignored. FURTHER NOTE: Mynewt developers mostly use gcc 5.x for sim builds; so it may take a little while to fix issues reported by the newer compiler. One option is to disable warnings . To do that, remove the -Werror flag as an option for the compiler in the mynewt-src-directory /repos/apa
che-mynewt-core/compiler/sim/compiler.yml file as shown below. compiler.flags.base: -m32 -Wall -ggdb You may alternatively choose to specify the precise warnings to ignore depending on the error thrown by the compiler. For example, if you see a [-Werror=misleading-indentation] error while building the sim image, add -Wno-misleading-indentation] as a compiler flag in the same line from the mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml file. compiler.flags.base: -m32 -Wall -Werror -ggdb -Wno-misleading-indentation A third option is to simply downgrade to gcc 5.x .",
- "title": "Install gcc/libc"
- },
- {
- "location": "/os/get_started/native_tools/#install-gdb",
- "text": "$ brew install gdb\n...\n...\n== Summary\n\ud83c\udf7a /usr/local/Cellar/gdb/7.10.1: XXX files,YYM NOTE: When running a program with gdb, you may need to sign your gdb\nexecutable. This page \nshows a recipe for gdb signing. Alternately you can skip this step and\ncontinue without the ability to debug your mynewt application on your PC.*",
- "title": "Install gdb"
- },
- {
- "location": "/os/get_started/native_tools/#set-up-toolchain-for-linux",
- "text": "The below procedure can be used to set up a Debian-based Linux system (e.g.,\nUbuntu). If you are running a different Linux distribution, you will need to\nsubstitute invocations of apt-get in the below steps with the package manager\nthat your distro uses.",
- "title": "Set up toolchain for Linux"
- },
- {
- "location": "/os/get_started/native_tools/#install-gcclibc-that-will-produce-32-bit-executables",
- "text": "$ sudo apt-get install gcc-multilib libc6-i386",
- "title": "Install gcc/libc that will produce 32-bit executables:"
- },
- {
- "location": "/os/get_started/native_tools/#install-gdb_1",
- "text": "$ sudo apt-get install gdb\n\nReading package lists... Done\nBuilding dependency tree \nReading state information... Done\nSuggested packages:\n gdb-doc gdbserver\nThe following NEW packages will be installed:\n gdb\n...\nProcessing triggers for man-db (2.6.7.1-1ubuntu1) ...\nSetting up gdb (7.7.1-0ubuntu5~14.04.2) ... At this point you have installed all the necessary software to build and test code on a simluator running on your Mac or Linux. Proceed to the Create Your First Project section.",
- "title": "Install gdb"
+ "location": "/os/get_started/native_install_intro/#native-installation",
+ "text": "This section shows you how to install tools on Mac OS and Linux platforms to develop, build, run, and debug Mynewt OS applications. You can build Mynewt OS applications to run as a native application on your computer or to run on your target board. These tools include: Newt tool - Tool to create, build, load, and debug a mynewt target. See Installing the Newt Tool on Mac OS to install on Mac OS. See Installing the Newt Tool on Linux to install on Linux. Native toolchain - Native toolchain to build and run Mynewt OS as a native application on your computer.\n (See Installing Native Toolchain ). Cross toolchain for ARM - Cross toolchain for ARM to build and run a Mynewt OS application on a target board\n (See Installing Cross Tools for ARMs ).",
+ "title": "Native Installation"
},
{
"location": "/newt/install/newt_mac/",
@@ -222,27 +187,27 @@
},
{
"location": "/newt/install/newt_linux/",
- "text": "Installing Newt on Linux\n\n\nYou can install the latest stable release (1.0.0) of newt from a Debian binary package (amd64) or from a Debian source package. This page shows you how to:\n\n\n\n\nSet up your computer to retrieve Debian packages from the runtimeco debian package repository.\n\n\nInstall the latest stable release version of newt from a Debian binary package. \n\n\nInstall the latest stable release version of newt from a Debian source package.\n\n\n\n\nIf you are running on an amd64 platform, we recommend that you install from the binary package.\n\n\nNote:\n See \nSetting Up an Go Environment to Contribute to Newt and Newtmgr Tools\n if you want to: \n\n\n\n\nUse the newt tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.\n\n\nContribute to the newt tool. \n\n\n\n\n\n\nSetting Up Your Computer to Get Packages from runtimeco\n\n\nThe newt Debian pac
kages are stored in a private repository on \nhttps://github/runtimeco/debian-mynewt\n. \n\n\nNote:\n You will only need to perform these steps only once on your computer.\nThe following steps must be performed on your computer:\n\n\n\n\nAdd the \napt-transport-https\n package to use HTTPS to retrieve packages. \n\n\nDownload the public key for the runtimeco debian repository and import the key into the apt keychain.\n\n\nAdd the repository for the binary and source packages to the apt source list.\n\n\n\n\n\nAdd the apt-transport-https package:\n\n\n$sudo apt-get update\n$sudo apt-get install apt-transport-https\n\n\n\n\n\n\n\nDownload the public key for the runtimeco apt repo (\nNote:\n There is \n-\n after the add):\n\n\nwget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -\n\n\n\n\n\n\n\nAdd the repository for the binary and source packages to the apt source list:\n\n\n$sudo -s\n[sudo] password for \nuser\n:\nroot$ cat \
n /etc/apt/sources.list.d/mynewt.list \nEOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\nEOF\n\n\n\n\n\n\nCheck the content of the file:\n\n\nroot$more /etc/apt/sources.list.d//mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\n\n\n\n\n\n \n\n\nExit the root shell:\n\n\nroot$exit\n\n\n\n\n\n\n\nInstalling the Latest Release of Newt from a Binary Package\n\n\nFor Linux amd64 platform, you can install the latest stable version (1.0.0) of newt from the newt Debian binary package:\n\n\n$sudo apt-get update\n$sudo apt-get install newt\nReading package lists... Done\nBuilding dependency tree \nReading state information... Done\n\n ...\n\nPreparing to unpack .../newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSettin
g up newt (1.0.0-1) ...\n\n\n\n\n\n\nSee \nChecking the Installed Version of Newt\n to verify that you are using the installed version of newt.\n\n\n\n\nInstalling the Latest Stable Release of Newt from a Source Package\n\n\nIf you are running Linux on a different architecture, you can install the Debian source package for the latest stable release (1.0.0) of newt. The installation of the source package builds the newt binary and creates a Debian binary package that you then install.\n\n\nNote\n: Newt version 1.0.0 has been tested on Linux amd64 platform. Version 1.0.0 does not build on the 32 bit platform but have been fixed for the next release.\n\n\n\n\nInstalling Go 1.7\n\n\nYou need Go version 1.7 or higher to build Newt version 1.0.0. Currently, the latest Go version that Ubuntu installs is 1.6. Run \ngo version\n to check if you have Go 1.7 installed. \n\n\n\n\nInstall Go version 1.7:\n\n\n$sudo apt-get install golang-1.7-go\nReading package lists... Done\n ...\nUnpacki
ng golang-1.7-go (1.7.1-2ubuntu1) ...\nSetting up golang-1.7-go (1.7.1-2ubuntu1) ...\n$\n$sudo ln -sf ../lib/go-1.7/bin/go /usr/bin/go\n$go version\ngo version go1.7.1 linux/amd64\n\n\n\n\n\nYou can also download version 1.7 from \nhttps://golang.org/dl/\n. \n\n\n\n\nInstalling from the Source Package\n\n\nCreate a directory and change into the directory, download the source package, and build a binary package from the source package:\n\n\nmkdir newt_source\n$cd newt_source\n$sudo apt-get --build source newt\n[sudo] password for \nuser\n: \nReading package lists... Done\nNeed to get 1,866 kB of source archives.\nGet:1 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (dsc) [795 B]\nGet:2 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (tar) [1,864 kB]\nGet:3 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (diff) [2,000 B]\nFetched 1,866 kB in 1s (1,222 kB/s)\nd
pkg-source: warning: extracting unsigned source package (newt_1.0.0-1.dsc)\ndpkg-source: info: extracting newt in newt-1.0.0\ndpkg-source: info: unpacking newt_1.0.0.orig.tar.gz\ndpkg-source: info: unpacking newt_1.0.0-1.debian.tar.xz\n\n ...\n\ndpkg-deb: building package \nnewt\n in \n../newt_1.0.0-1_amd64.deb\n.\n dpkg-genchanges --build=any,all \n../newt_1.0.0-1_amd64.changes\ndpkg-genchanges: info: binary-only upload (no source code included)\n dpkg-source --after-build newt-1.0.0\ndpkg-buildpackage: info: binary-only upload (no source included)\nW: Can\nt drop privileges for downloading as file \nnewt_1.0.0-1.dsc\n couldn\nt be accessed by user \n_apt\n. - pkgAcquire::Run (13: Permission denied)\n\n\n\n\n\nNote:\n You can ignore the \"Permission denied: warning message at the end of the command.\n\n\n\nInstall the newt binary package that is created from the source package:\n\n\n$sudo dpkg -i newt_1.0.0-1_amd64.deb \nSelecting previously unselected package newt.\n(Rea
ding database ... 252969 files and directories currently installed.)\nPreparing to unpack newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.0-1) ...\n\n\n\n\n\n\n\n Checking the Installed Version of Newt\n\n\nAfter you have installed newt from either a Debian binary or source package, check that you are using the installed version of newt from \n/usr/bin\n. \n\n\nCheck the modification time of the binary and the newt tool that you are using:\n\n\n$ls -l /usr/bin/newt\n-rwxr-xr-x 1 root root 6919280 Apr 22 10:09 /usr/bin/newt\n$which newt\n/usr/bin/newt\n$newt version\nApache Newt (incubating) version: 1.0.0\n\n\n\n\n\nNote:\n If you previously built newt from source and the output of \nwhich newt\n shows \"$GOPATH/bin/newt\", you will need to move \"$GOPATH/bin\" after \"/usr/bin\" in your $PATH and export your $PATH.\n\n\n\nGet information about newt:\n\n\n$newt\nNewt allows you to create your own embedded application based on the Mynewt\noperating syst
em. Newt provides both build and package management in a single\ntool, which allows you to compose an embedded application, and set of\nprojects, and then build the necessary artifacts from those projects. For more\ninformation on the Mynewt operating system, please visit\nhttps://mynewt.apache.org/.\n\nPlease use the newt help command, and specify the name of the command you want\nhelp for, for help on how to use a specific command\n\nUsage:\n newt [flags]\n newt [command]\n\nExamples:\n newt\n newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\nAvailable Commands:\n build Build one or more targets\n clean Delete build artifacts for one or more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image
commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing comm
ands\n\nUse \nnewt [command] --help\n for more information about a command.",
+ "text": "Installing Newt on Linux\n\n\nYou can install the latest stable release (1.0.0) of the newt tool from a Debian binary package (amd64) or from a Debian source package. This page shows you how to:\n\n\n\n\nSet up your computer to retrieve Debian packages from the runtimeco debian package repository.\n\n\nInstall the latest stable release version of newt from a Debian binary package. \n\n\nInstall the latest stable release version of newt from a Debian source package.\n\n\n\n\nIf you are installing on an amd64 platform, we recommend that you install from the binary package.\n\n\nNote:\n See \nSetting Up an Go Environment to Contribute to Newt and Newtmgr Tools\n if you want to: \n\n\n\n\nUse the newt tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.\n\n\nContribute to the newt tool. \n\n\n\n\n\n\nSetting Up Your Computer to Get Packages from runtimeco\n\n\nThe new
t Debian packages are stored in a private repository on \nhttps://github/runtimeco/debian-mynewt\n. The following steps must be performed on your computer to retreive packages from the repository:\n\n\nNote:\n You only need to perform this setup once on your computer.\n\n\n\n\nInstall the \napt-transport-https\n package to use HTTPS to retrieve packages. \n\n\nDownload the public key for the runtimeco debian repository and import the key into the apt keychain.\n\n\nAdd the repository for the binary and source packages to the apt source list.\n\n\n\n\n\nInstall the apt-transport-https package:\n\n\n$sudo apt-get update\n$sudo apt-get install apt-transport-https\n\n\n\n\n\n\n\nDownload the public key for the runtimeco apt repo (\nNote:\n There is a \n-\n after \napt-key add\n):\n\n\nwget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -\n\n\n\n\n\n\n\nAdd the repository for the binary and source packages to the \nmynewt.list\
n apt source list file.\n\n\n$sudo -s\n[sudo] password for \nuser\n:\nroot$ cat \n /etc/apt/sources.list.d/mynewt.list \nEOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\nEOF\nroot$exit\n\n\n\n\n\nNote:\n Do not forget to exit the root shell.\n\n\n\nVerify the content of the source list file:\n\n\n$more /etc/apt/sources.list.d/mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\n\n\n\n\n\n \n\n\nInstalling the Latest Release of Newt from a Binary Package\n\n\nFor Linux amd64 platforms, you can install the latest stable version (1.0.0) of newt from the newt Debian binary package:\n\n\n$sudo apt-get update\n$sudo apt-get install newt\nReading package lists... Done\nBuilding dependency tree \nReading state information... Done\n\n
...\n\nPreparing to unpack .../newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.0-1) ...\n\n\n\n\n\n\nSee \nChecking the Installed Version of Newt\n to verify that you are using the installed version of newt.\n\n\n\n\nInstalling the Latest Stable Release of Newt from a Source Package\n\n\nIf you are running Linux on a different architecture, you can install the Debian source package for the latest stable release (1.0.0) of newt. The installation of the source package builds the newt binary and creates a Debian binary package that you then install.\n\n\nNote\n: Newt version 1.0.0 has been tested on Linux amd64 platforms. Version 1.0.0 does not build on 32 bit platforms but have been fixed for the next release.\n\n\n\n\nInstalling Go 1.7\n\n\nYou need Go version 1.7 or higher to build Newt version 1.0.0. Currently, the latest Go version that Ubuntu installs is 1.6. Run \ngo version\n to check if you have Go 1.7 installed. \n\n\n\n\nInstall Go vers
ion 1.7:\n\n\n$sudo apt-get install golang-1.7-go\nReading package lists... Done\n ...\nUnpacking golang-1.7-go (1.7.1-2ubuntu1) ...\nSetting up golang-1.7-go (1.7.1-2ubuntu1) ...\n$\n$sudo ln -sf ../lib/go-1.7/bin/go /usr/bin/go\n$go version\ngo version go1.7.1 linux/amd64\n\n\n\n\n\nYou can also download version 1.7 from \nhttps://golang.org/dl/\n. \n\n\n\n\nInstalling from the Source Package\n\n\nCreate a directory and change into the directory, download the source package, and build a binary package from the source package:\n\n\nmkdir newt_source\n$cd newt_source\n$sudo apt-get --build source newt\n[sudo] password for \nuser\n: \nReading package lists... Done\nNeed to get 1,866 kB of source archives.\nGet:1 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (dsc) [795 B]\nGet:2 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (tar) [1,864 kB]\nGet:3 https://raw.githubusercontent.com/runtimeco/deb
ian-mynewt/master latest/main newt 1.0.0-1 (diff) [2,000 B]\nFetched 1,866 kB in 1s (1,222 kB/s)\ndpkg-source: warning: extracting unsigned source package (newt_1.0.0-1.dsc)\ndpkg-source: info: extracting newt in newt-1.0.0\ndpkg-source: info: unpacking newt_1.0.0.orig.tar.gz\ndpkg-source: info: unpacking newt_1.0.0-1.debian.tar.xz\n\n ...\n\ndpkg-deb: building package \nnewt\n in \n../newt_1.0.0-1_amd64.deb\n.\n dpkg-genchanges --build=any,all \n../newt_1.0.0-1_amd64.changes\ndpkg-genchanges: info: binary-only upload (no source code included)\n dpkg-source --after-build newt-1.0.0\ndpkg-buildpackage: info: binary-only upload (no source included)\nW: Can\nt drop privileges for downloading as file \nnewt_1.0.0-1.dsc\n couldn\nt be accessed by user \n_apt\n. - pkgAcquire::Run (13: Permission denied)\n\n\n\n\n\nNote:\n You can ignore the \"Permission denied\" warning message at the end of the command.\n\n\n\nInstall the newt binary package that is created from the source pack
age:\n\n\nNote:\n The file name for the binary package has the format: newt_1.0.0-1_\narch\n.deb, where \narch\n is a value that identifies your host architecture. \n\n\n$sudo dpkg -i newt_1.0.0-1_amd64.deb \nSelecting previously unselected package newt.\n(Reading database ... 252969 files and directories currently installed.)\nPreparing to unpack newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.0-1) ...\n\n\n\n\n\n\n\n Checking the Installed Version of Newt\n\n\nAfter you have installed newt from either a Debian binary or source package, check that you are using the installed version of newt from \n/usr/bin\n. \n\n\nCheck the modification time of the binary and the newt tool that you are using:\n\n\n$ls -l /usr/bin/newt\n-rwxr-xr-x 1 root root 6919280 Apr 22 10:09 /usr/bin/newt\n$which newt\n/usr/bin/newt\n$newt version\nApache Newt (incubating) version: 1.0.0\n\n\n\n\n\nNote:\n If you previously built newt from source and the output of \nwhich newt\
n shows \"$GOPATH/bin/newt\", you will need to move \"$GOPATH/bin\" after \"/usr/bin\" for your PATH environment variable and export it. \n\n\n\nGet information about newt:\n\n\n$newt\nNewt allows you to create your own embedded application based on the Mynewt\noperating system. Newt provides both build and package management in a single\ntool, which allows you to compose an embedded application, and set of\nprojects, and then build the necessary artifacts from those projects. For more\ninformation on the Mynewt operating system, please visit\nhttps://mynewt.apache.org/.\n\nPlease use the newt help command, and specify the name of the command you want\nhelp for, for help on how to use a specific command\n\nUsage:\n newt [flags]\n newt [command]\n\nExamples:\n newt\n newt help [\ncommand-name\n]\n For help on \ncommand-name\n. If not specified, print this message.\n\nAvailable Commands:\n build Build one or more targets\n clean Delete build artifacts for one o
r more targets\n create-image Add image header to target binary\n debug Open debugger session to target\n info Show project info\n install Install project dependencies\n load Load built target to board\n mfg Manufacturing flash image commands\n new Create a new project\n pkg Create and manage packages in the current workspace\n run build/create-image/download/debug \ntarget\n\n size Size of target components\n sync Synchronize project dependencies\n target Commands to create, delete, configure, and query targets\n test Executes unit tests for one or more packages\n upgrade Upgrade project dependencies\n vals Display valid values for the specified element type(s)\n version Display the Newt version number\n\nFlags:\n -h, --help Help for newt commands\n -j, --jobs int Number of concurrent build jobs (default 8)\n -l, --loglevel string
Log level (default \nWARN\n)\n -o, --outfile string Filename to tee output to\n -q, --quiet Be quiet; only display error output\n -s, --silent Be silent; don\nt output anything\n -v, --verbose Enable verbose output when executing commands\n\nUse \nnewt [command] --help\n for more information about a command.",
"title": "Install Newt on Linux"
},
{
"location": "/newt/install/newt_linux/#installing-newt-on-linux",
- "text": "You can install the latest stable release (1.0.0) of newt from a Debian binary package (amd64) or from a Debian source package. This page shows you how to: Set up your computer to retrieve Debian packages from the runtimeco debian package repository. Install the latest stable release version of newt from a Debian binary package. Install the latest stable release version of newt from a Debian source package. If you are running on an amd64 platform, we recommend that you install from the binary package. Note: See Setting Up an Go Environment to Contribute to Newt and Newtmgr Tools if you want to: Use the newt tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version. Contribute to the newt tool.",
+ "text": "You can install the latest stable release (1.0.0) of the newt tool from a Debian binary package (amd64) or from a Debian source package. This page shows you how to: Set up your computer to retrieve Debian packages from the runtimeco debian package repository. Install the latest stable release version of newt from a Debian binary package. Install the latest stable release version of newt from a Debian source package. If you are installing on an amd64 platform, we recommend that you install from the binary package. Note: See Setting Up an Go Environment to Contribute to Newt and Newtmgr Tools if you want to: Use the newt tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version. Contribute to the newt tool.",
"title": "Installing Newt on Linux"
},
{
"location": "/newt/install/newt_linux/#setting-up-your-computer-to-get-packages-from-runtimeco",
- "text": "The newt Debian packages are stored in a private repository on https://github/runtimeco/debian-mynewt . Note: You will only need to perform these steps only once on your computer.\nThe following steps must be performed on your computer: Add the apt-transport-https package to use HTTPS to retrieve packages. Download the public key for the runtimeco debian repository and import the key into the apt keychain. Add the repository for the binary and source packages to the apt source list. \nAdd the apt-transport-https package: $sudo apt-get update\n$sudo apt-get install apt-transport-https Download the public key for the runtimeco apt repo ( Note: There is - after the add): wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add - Add the repository for the binary and source packages to the apt source list: $sudo -s\n[sudo] password for user :\nroot$ cat /etc/apt/sources.list.d/mynewt.lis
t EOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\nEOF \nCheck the content of the file: root$more /etc/apt/sources.list.d//mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main Exit the root shell: root$exit",
+ "text": "The newt Debian packages are stored in a private repository on https://github/runtimeco/debian-mynewt . The following steps must be performed on your computer to retreive packages from the repository: Note: You only need to perform this setup once on your computer. Install the apt-transport-https package to use HTTPS to retrieve packages. Download the public key for the runtimeco debian repository and import the key into the apt keychain. Add the repository for the binary and source packages to the apt source list. \nInstall the apt-transport-https package: $sudo apt-get update\n$sudo apt-get install apt-transport-https Download the public key for the runtimeco apt repo ( Note: There is a - after apt-key add ): wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add - Add the repository for the binary and source packages to the mynewt.list apt source list file. $sudo -s\n[sudo] pas
sword for user :\nroot$ cat /etc/apt/sources.list.d/mynewt.list EOF\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\nEOF\nroot$exit Note: Do not forget to exit the root shell. \nVerify the content of the source list file: $more /etc/apt/sources.list.d/mynewt.list\ndeb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main\ndeb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main",
"title": "Setting Up Your Computer to Get Packages from runtimeco"
},
{
"location": "/newt/install/newt_linux/#installing-the-latest-release-of-newt-from-a-binary-package",
- "text": "For Linux amd64 platform, you can install the latest stable version (1.0.0) of newt from the newt Debian binary package: $sudo apt-get update\n$sudo apt-get install newt\nReading package lists... Done\nBuilding dependency tree \nReading state information... Done\n\n ...\n\nPreparing to unpack .../newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.0-1) ... \nSee Checking the Installed Version of Newt to verify that you are using the installed version of newt.",
+ "text": "For Linux amd64 platforms, you can install the latest stable version (1.0.0) of newt from the newt Debian binary package: $sudo apt-get update\n$sudo apt-get install newt\nReading package lists... Done\nBuilding dependency tree \nReading state information... Done\n\n ...\n\nPreparing to unpack .../newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.0-1) ... \nSee Checking the Installed Version of Newt to verify that you are using the installed version of newt.",
"title": "Installing the Latest Release of Newt from a Binary Package"
},
{
"location": "/newt/install/newt_linux/#installing-the-latest-stable-release-of-newt-from-a-source-package",
- "text": "If you are running Linux on a different architecture, you can install the Debian source package for the latest stable release (1.0.0) of newt. The installation of the source package builds the newt binary and creates a Debian binary package that you then install. Note : Newt version 1.0.0 has been tested on Linux amd64 platform. Version 1.0.0 does not build on the 32 bit platform but have been fixed for the next release.",
+ "text": "If you are running Linux on a different architecture, you can install the Debian source package for the latest stable release (1.0.0) of newt. The installation of the source package builds the newt binary and creates a Debian binary package that you then install. Note : Newt version 1.0.0 has been tested on Linux amd64 platforms. Version 1.0.0 does not build on 32 bit platforms but have been fixed for the next release.",
"title": "Installing the Latest Stable Release of Newt from a Source Package"
},
{
@@ -252,10 +217,55 @@
},
{
"location": "/newt/install/newt_linux/#installing-from-the-source-package",
- "text": "Create a directory and change into the directory, download the source package, and build a binary package from the source package: mkdir newt_source\n$cd newt_source\n$sudo apt-get --build source newt\n[sudo] password for user : \nReading package lists... Done\nNeed to get 1,866 kB of source archives.\nGet:1 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (dsc) [795 B]\nGet:2 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (tar) [1,864 kB]\nGet:3 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (diff) [2,000 B]\nFetched 1,866 kB in 1s (1,222 kB/s)\ndpkg-source: warning: extracting unsigned source package (newt_1.0.0-1.dsc)\ndpkg-source: info: extracting newt in newt-1.0.0\ndpkg-source: info: unpacking newt_1.0.0.orig.tar.gz\ndpkg-source: info: unpacking newt_1.0.0-1.debian.tar.xz\n\n ...\n\ndpkg-deb: building package newt in
../newt_1.0.0-1_amd64.deb .\n dpkg-genchanges --build=any,all ../newt_1.0.0-1_amd64.changes\ndpkg-genchanges: info: binary-only upload (no source code included)\n dpkg-source --after-build newt-1.0.0\ndpkg-buildpackage: info: binary-only upload (no source included)\nW: Can t drop privileges for downloading as file newt_1.0.0-1.dsc couldn t be accessed by user _apt . - pkgAcquire::Run (13: Permission denied) Note: You can ignore the \"Permission denied: warning message at the end of the command. \nInstall the newt binary package that is created from the source package: $sudo dpkg -i newt_1.0.0-1_amd64.deb \nSelecting previously unselected package newt.\n(Reading database ... 252969 files and directories currently installed.)\nPreparing to unpack newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.0-1) ...",
+ "text": "Create a directory and change into the directory, download the source package, and build a binary package from the source package: mkdir newt_source\n$cd newt_source\n$sudo apt-get --build source newt\n[sudo] password for user : \nReading package lists... Done\nNeed to get 1,866 kB of source archives.\nGet:1 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (dsc) [795 B]\nGet:2 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (tar) [1,864 kB]\nGet:3 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (diff) [2,000 B]\nFetched 1,866 kB in 1s (1,222 kB/s)\ndpkg-source: warning: extracting unsigned source package (newt_1.0.0-1.dsc)\ndpkg-source: info: extracting newt in newt-1.0.0\ndpkg-source: info: unpacking newt_1.0.0.orig.tar.gz\ndpkg-source: info: unpacking newt_1.0.0-1.debian.tar.xz\n\n ...\n\ndpkg-deb: building package newt in
../newt_1.0.0-1_amd64.deb .\n dpkg-genchanges --build=any,all ../newt_1.0.0-1_amd64.changes\ndpkg-genchanges: info: binary-only upload (no source code included)\n dpkg-source --after-build newt-1.0.0\ndpkg-buildpackage: info: binary-only upload (no source included)\nW: Can t drop privileges for downloading as file newt_1.0.0-1.dsc couldn t be accessed by user _apt . - pkgAcquire::Run (13: Permission denied) Note: You can ignore the \"Permission denied\" warning message at the end of the command. \nInstall the newt binary package that is created from the source package: Note: The file name for the binary package has the format: newt_1.0.0-1_ arch .deb, where arch is a value that identifies your host architecture. $sudo dpkg -i newt_1.0.0-1_amd64.deb \nSelecting previously unselected package newt.\n(Reading database ... 252969 files and directories currently installed.)\nPreparing to unpack newt_1.0.0-1_amd64.deb ...\nUnpacking newt (1.0.0-1) ...\nSetting up newt (1.0.
0-1) ...",
"title": "Installing from the Source Package"
},
{
+ "location": "/os/get_started/native_tools/",
+ "text": "Installing Native Mynewt Tools\n\n\nThis page shows how to install tools for native Mynewt targets (simulated targets on your laptop/computer) without using a Docker container. In other words, it allows you to run Mynewt OS as a native application on your Mac or Linux machine to simulate a target and use the Newt tool running natively on your machine to manage the simulated target. It also allows you to run the test suites for all packages not requiring HW support. You may choose to do this instead of using the build toolchain and Newt tool available in a Docker container.\n\n\nThis page provides guidance for MAC and Linux. See the relevant sections below.\n\n\n\n\nSet up toolchain for Mac\n\n\nInstall Brew\n\n\nIf you have not already installed Homebrew from the \n\nnewt\n tutorials pages\n, install it. \n\n\n\n\nInstall gcc/libc\n\n\nOS X ships with a C compiler called Clang. To build applications for the Mynewt simulator with, a different compiler is used as
default: gcc.\n\n\n$ brew install gcc\n...\n...\n==\n Summary\n\ud83c\udf7a /usr/local/Cellar/gcc/5.2.0: 1353 files, 248M\n\n\n\n\n\n\n\nCheck the gcc version you have installed (either using brew or previously installed). The brew-installed version can be checked using \nbrew list gcc\n. The default compiler.yml configuration file in Mynewt expects version 5.x for Mac users, so if the installed version is 6.x and you wish to continue with this newer version, modify the \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n file to change the default \ngcc-5\n defined there to \ngcc-6\n. In other words, replace the lines shown highlighted below:\n\n\n# OS X.\n\ncompiler.path.cc.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.as.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.objdump.DARWIN.OVERWRITE: \ngobjdump\n\ncompiler.path.objsize.DARWIN.OVERWRITE: \nobjsize\n\ncompiler.path.objcopy.DARWIN.OVERWRITE: \ngobjcopy\n\n\n\n\n\n\nwith the following:\n\n\ncompiler.p
ath.cc.DARWIN.OVERWRITE: \ngcc-6\n\ncompiler.path.as.DARWIN.OVERWRITE: \ngcc-6\u201d\n\n\n\n\n\n\n\nIn case you wish to use Clang, you can change your \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n to use Clang. Delete the gcc-5 DARWIN.OVERWRITE lines highlighted below.\n\n\n# OS X.\n\ncompiler.path.cc.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.as.DARWIN.OVERWRITE: \ngcc-5\n\n\ncompiler.path.objdump.DARWIN.OVERWRITE: \ngobjdump\n\ncompiler.path.objsize.DARWIN.OVERWRITE: \nobjsize\n\ncompiler.path.objcopy.DARWIN.OVERWRITE: \ngobjcopy\n\n\n\n\n\n\n\n\nNOTE:\n Both the newer gcc 6.x and Clang report a few warnings but they can be ignored.\n\n\n\n\nFURTHER NOTE:\n Mynewt developers mostly use gcc 5.x for sim builds; so it may take a little while to fix issues reported by the newer compiler. One option is to \ndisable warnings\n. To do that, remove the \n-Werror\n flag as an option for the compiler in the \nmynewt-src-directory\n/repos/apache-mynewt-core
/compiler/sim/compiler.yml\n file as shown below. \n\n\ncompiler.flags.base: \n\n\n -m32 -Wall -ggdb\n\n\n\n\n\nYou may alternatively choose to \nspecify the precise warnings to ignore\n depending on the error thrown by the compiler. For example, if you see a \n[-Werror=misleading-indentation]\n error while building the sim image, add \n-Wno-misleading-indentation]\n as a compiler flag in the same line from the \nmynewt-src-directory\n/repos/apache-mynewt-core/compiler/sim/compiler.yml\n file.\n\n\ncompiler.flags.base: \n\n\n -m32 -Wall -Werror -ggdb -Wno-misleading-indentation\n\n\n\n\n\nA third option is to simply \ndowngrade to gcc 5.x\n.\n\n\n\n\nInstall gdb\n\n\n$ brew install gdb\n...\n...\n==\n Summary\n\ud83c\udf7a /usr/local/Cellar/gdb/7.10.1: XXX files,YYM\n\n\n\n\n\n\n\nNOTE:\n When running a program with gdb, you may need to sign your gdb\nexecutable. \nThis page\n\nshows a recipe for gdb signing. Alternately you can skip this step and\ncontinue without the abili
ty to debug your mynewt application on your PC.*\n\n\n\n\nSet up toolchain for Linux\n\n\nThe below procedure can be used to set up a Debian-based Linux system (e.g.,\nUbuntu). If you are running a different Linux distribution, you will need to\nsubstitute invocations of \napt-get\n in the below steps with the package manager\nthat your distro uses.\n\n\n\n\nInstall gcc/libc that will produce 32-bit executables:\n\n\n$ sudo apt-get install gcc-multilib libc6-i386\n\n\n\n\n\n\n\nInstall gdb\n\n\n$ sudo apt-get install gdb\n\nReading package lists... Done\nBuilding dependency tree \nReading state information... Done\nSuggested packages:\n gdb-doc gdbserver\nThe following NEW packages will be installed:\n gdb\n...\nProcessing triggers for man-db (2.6.7.1-1ubuntu1) ...\nSetting up gdb (7.7.1-0ubuntu5~14.04.2) ...\n\n\n\n\n\n\n\nAt this point you have installed all the necessary software to build and run your first project on a simluator on your Mac OS or Linux computer. You may
proceed to the \nCreate Your First Project\n section or continue to the next section and install the cross tools for ARM.",
+ "title": "Install Native Toolchain"
+ },
+ {
+ "location": "/os/get_started/native_tools/#installing-native-mynewt-tools",
+ "text": "This page shows how to install tools for native Mynewt targets (simulated targets on your laptop/computer) without using a Docker container. In other words, it allows you to run Mynewt OS as a native application on your Mac or Linux machine to simulate a target and use the Newt tool running natively on your machine to manage the simulated target. It also allows you to run the test suites for all packages not requiring HW support. You may choose to do this instead of using the build toolchain and Newt tool available in a Docker container. This page provides guidance for MAC and Linux. See the relevant sections below.",
+ "title": "Installing Native Mynewt Tools"
+ },
+ {
+ "location": "/os/get_started/native_tools/#set-up-toolchain-for-mac",
+ "text": "",
+ "title": "Set up toolchain for Mac"
+ },
+ {
+ "location": "/os/get_started/native_tools/#install-brew",
+ "text": "If you have not already installed Homebrew from the newt tutorials pages , install it.",
+ "title": "Install Brew"
+ },
+ {
+ "location": "/os/get_started/native_tools/#install-gcclibc",
+ "text": "OS X ships with a C compiler called Clang. To build applications for the Mynewt simulator with, a different compiler is used as default: gcc. $ brew install gcc\n...\n...\n== Summary\n\ud83c\udf7a /usr/local/Cellar/gcc/5.2.0: 1353 files, 248M Check the gcc version you have installed (either using brew or previously installed). The brew-installed version can be checked using brew list gcc . The default compiler.yml configuration file in Mynewt expects version 5.x for Mac users, so if the installed version is 6.x and you wish to continue with this newer version, modify the mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml file to change the default gcc-5 defined there to gcc-6 . In other words, replace the lines shown highlighted below: # OS X. compiler.path.cc.DARWIN.OVERWRITE: gcc-5 compiler.path.as.DARWIN.OVERWRITE: gcc-5 compiler.path.objdump.DARWIN.OVERWRITE: gobjdump \ncompiler.path.objsize.DARWIN.OVERWRITE: objsize
\ncompiler.path.objcopy.DARWIN.OVERWRITE: gobjcopy with the following: compiler.path.cc.DARWIN.OVERWRITE: gcc-6 \ncompiler.path.as.DARWIN.OVERWRITE: gcc-6\u201d In case you wish to use Clang, you can change your mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml to use Clang. Delete the gcc-5 DARWIN.OVERWRITE lines highlighted below. # OS X. compiler.path.cc.DARWIN.OVERWRITE: gcc-5 compiler.path.as.DARWIN.OVERWRITE: gcc-5 compiler.path.objdump.DARWIN.OVERWRITE: gobjdump \ncompiler.path.objsize.DARWIN.OVERWRITE: objsize \ncompiler.path.objcopy.DARWIN.OVERWRITE: gobjcopy NOTE: Both the newer gcc 6.x and Clang report a few warnings but they can be ignored. FURTHER NOTE: Mynewt developers mostly use gcc 5.x for sim builds; so it may take a little while to fix issues reported by the newer compiler. One option is to disable warnings . To do that, remove the -Werror flag as an option for the compiler in the mynewt-src-directory /repos/apa
che-mynewt-core/compiler/sim/compiler.yml file as shown below. compiler.flags.base: -m32 -Wall -ggdb You may alternatively choose to specify the precise warnings to ignore depending on the error thrown by the compiler. For example, if you see a [-Werror=misleading-indentation] error while building the sim image, add -Wno-misleading-indentation] as a compiler flag in the same line from the mynewt-src-directory /repos/apache-mynewt-core/compiler/sim/compiler.yml file. compiler.flags.base: -m32 -Wall -Werror -ggdb -Wno-misleading-indentation A third option is to simply downgrade to gcc 5.x .",
+ "title": "Install gcc/libc"
+ },
+ {
+ "location": "/os/get_started/native_tools/#install-gdb",
+ "text": "$ brew install gdb\n...\n...\n== Summary\n\ud83c\udf7a /usr/local/Cellar/gdb/7.10.1: XXX files,YYM NOTE: When running a program with gdb, you may need to sign your gdb\nexecutable. This page \nshows a recipe for gdb signing. Alternately you can skip this step and\ncontinue without the ability to debug your mynewt application on your PC.*",
+ "title": "Install gdb"
+ },
+ {
+ "location": "/os/get_started/native_tools/#set-up-toolchain-for-linux",
+ "text": "The below procedure can be used to set up a Debian-based Linux system (e.g.,\nUbuntu). If you are running a different Linux distribution, you will need to\nsubstitute invocations of apt-get in the below steps with the package manager\nthat your distro uses.",
+ "title": "Set up toolchain for Linux"
+ },
+ {
+ "location": "/os/get_started/native_tools/#install-gcclibc-that-will-produce-32-bit-executables",
+ "text": "$ sudo apt-get install gcc-multilib libc6-i386",
+ "title": "Install gcc/libc that will produce 32-bit executables:"
+ },
+ {
+ "location": "/os/get_started/native_tools/#install-gdb_1",
+ "text": "$ sudo apt-get install gdb\n\nReading package lists... Done\nBuilding dependency tree \nReading state information... Done\nSuggested packages:\n gdb-doc gdbserver\nThe following NEW packages will be installed:\n gdb\n...\nProcessing triggers for man-db (2.6.7.1-1ubuntu1) ...\nSetting up gdb (7.7.1-0ubuntu5~14.04.2) ... At this point you have installed all the necessary software to build and run your first project on a simluator on your Mac OS or Linux computer. You may proceed to the Create Your First Project section or continue to the next section and install the cross tools for ARM.",
+ "title": "Install gdb"
+ },
+ {
"location": "/os/get_started/cross_tools/",
"text": "Installing Cross Tools for ARM\n\n\nThis page shows how to install tools on your laptop/computer to use for direct communication (e.g. for debugging) with some ARM based HW platforms running Apache Mynewt. It shows you how to install the following tools for Mac OS X and Linux:\n\n\n\n\nARM Cross toolchain\n\n\nDebugger to load and debug your device\n\n\n\n\n\n\nInstall ARM Cross Toolchain\n\n\nInstall ARM Toolchain For Mac OS X\n\n\nInstall the PX4 Toolchain and check the version installed. ARM maintains a\npre-built GNU toolchain with a GCC source branch targeted at Embedded ARM\nProcessors, namely Cortex-R/Cortex-M processor families. After installing,\nensure that the symbolic link installed by Homebrew points to the correct\nversion of the debugger.\n\n\n$ brew tap PX4/homebrew-px4\n$ brew update\n$ brew install gcc-arm-none-eabi-49\n$ arm-none-eabi-gcc --version \narm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 4.9.3 20150529 (release) [ARM/embe
dded-4_9-branch revision 224288]\nCopyright (C) 2014 Free Software Foundation, Inc.\nThis is free software; see the source for copying conditions. There is NO\nwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.\n$ ls -al /usr/local/bin/arm-none-eabi-gdb\nlrwxr-xr-x 1 aditihilbert admin 69 Sep 22 17:16 /usr/local/bin/arm-none-eabi-gdb -\n /usr/local/Cellar/gcc-arm-none-eabi-49/20150609/bin/arm-none-eabi-gdb\n\n\n\n\n\nNote:\n If no version is specified, brew will install the latest version\navailable. Mynewt OS will eventually work with multiple versions available,\nincluding the latest releases. However, at present we have tested only with\nthis version and recommend it for getting started. \n\n\n\n\nInstall ARM Toolchain For Linux\n\n\nOn a Debian-based Linux distribution, gcc 4.9.3 for ARM can be installed with\napt-get as documented below. The steps are explained in depth at\n\nhttps://launchpad.net/~team-gcc-arm-embedded/+archive/ubuntu/ppa\n.\n\n\n$
sudo apt-get remove binutils-arm-none-eabi gcc-arm-none-eabi \n$ sudo add-apt-repository ppa:team-gcc-arm-embedded/ppa\n$ sudo apt-get update \n$ sudo apt-get install gcc-arm-none-eabi\n$ sudo apt-get install gdb-arm-none-eabi\n\n\n\n\n\n\n\nInstall Debugger\n\n\nMynewt uses, depending on the board, either the OpenOCD or SEGGER J-Link debugger. \n\n\nInstall OpenOCD\n\n\nOpenOCD (Open On-Chip Debugger) is open-source software that allows your\ncomputer to interface with the JTAG debug connector on a variety of boards. A\nJTAG connection lets you debug and test embedded target devices. For more on\nOpenOCD go to \nhttp://openocd.org\n.\n\n\nOpenOCD version 0.10.0 with nrf52 support is required. A binary for this version is available to download for Mac OS and Linux.\n\n\n\n\nInstall OpenOCD on Mac OS\n\n\nStep 1: Download the \nbinary tarball for Mac OS\n.\n\n\nStep 2: Change to the root directory: \n\n\n$cd / \n\n\n\n\n\n\nStep 3: Untar the tarball and install into \n /usr/local/
bin\n. You will need to replace \n ~/Downloads \n with the directory that the tarball is downloaded to. \n\n\nsudo tar -xf ~/Downloads/openocd-bin-0.10.0-MacOS.tgz ` \n\n\n\n\n\n\nStep 4: Check the OpenOCD version you are using: \n\n\n$which openocd\n/usr/local/bin/openocd\n$openocd -v\nOpen On-Chip Debugger 0.10.0\nLicensed under GNU GPL v2\nFor bug reports, read\nhttp://openocd.org/doc/doxygen/bugs.html\n\n\n\n\n\nYou should see version: \n0.10.0\n. \n\n\n\n\nInstall OpenOCD on Linux\n\n\nStep 1: Download the \nbinary tarball for Linux\n\n\nStep 2: Change to the root directory: \n\n\n$cd / \n\n\n\n\n\n\nStep 3: Untar the tarball and install into \n /usr/local/bin\n. You will need to replace \n ~/Downloads \n with the directory that the tarball is downloaded to. \n\n\n Note:\n You must specify the -p option for the tar command.\n\n\n$sudo tar -xpf ~/Downloads/openocd-bin-0.10.0-Linux.tgz\n\n\n\n\n\n\nStep 4: Check the OpenOCD version you are using: \n\n\n$which openocd\n/usr/lo
cal/bin/openocd\n$openocd -v\nOpen On-Chip Debugger 0.10.0\nLicensed under GNU GPL v2\nFor bug reports, read\nhttp://openocd.org/doc/doxygen/bugs.html\n\n\n\n\n\nYou should see version: \n0.10.0\n. \n\n\nIf you see any of these error messages:\n\n\n\n\n\n\nopenocd: error while loading shared libraries: libhidapi-hidraw.so.0: cannot open shared object file: No such file or directory\n\n\n\n\n\n\nopenocd: error while loading shared libraries: libusb-1.0.so.0: cannot open shared object file: No such file or directory \n\n\n\n\n\n\nrun the following command to install the libraries: \n\n\n$sudo apt-get install libhidapi-dev:i386\n\n\n\n\n\n\n\nInstall SEGGAR J-Link\n\n\nYou can download and install Segger J-LINK Software and documentation pack from \nSEGGER\n.",
"title": "Install Cross Tools for ARM"
@@ -352,7 +362,7 @@
},
{
"location": "/os/get_started/project_create/",
- "text": "Create Your First Mynewt Project\n\n\nThis page shows how to create a Mynewt Project using the \nnewt\n command-line tool.\n\n\n\n\nPre-Requisites\n\n\n\n\nNewt:\n\n\nIf you have taken the Docker route, you have already installed Newt.\n\n\nIf you have taken the native install route, you have to ensure that you have installed the Newt tool following the instructions for \nMac\n or \nLinux\n as appropriate, and that the \nnewt\n command is in your system path. \n\n\n\n\n\n\nYou must have Internet connectivity to fetch remote Mynewt components.\n\n\nYou must \ninstall the compiler tools\n to \nsupport native compiling to build the project this tutorial creates. \n\n\n\n\n\n\nNewt New\n\n\nChoose a project name. For this tutorial we will call this project \nmyproj\n.\nEnter the \nnewt new myproj\n command. \n\n\n$ newt new myproj\nDownloading project skeleton from apache/incubator-mynewt-blinky...\nInstalling skeleton in myproj...\nProject myproj successfully crea
ted.\n\n\n\n\n\n\n\nNewt populates this new project with a base skeleton of a new Apache Mynewt \nproject. It has the following structure. \n\n\nNote\n: If you do not have \ntree\n, install it by running \nbrew install tree\n.\n\n\n$ cd myproj\n$ tree \n.\n\u251c\u2500\u2500 DISCLAIMER\n\u251c\u2500\u2500 LICENSE\n\u251c\u2500\u2500 NOTICE\n\u251c\u2500\u2500 README.md\n\u251c\u2500\u2500 apps\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 blinky\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 pkg.yml\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 src\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 main.c\n\u251c\u2500\u2500 project.yml\n\u2514\u2500\u2500 targets\n \u251c\u2500\u2500 my_blinky_sim\n \u2502\u00a0\u00a0 \u251c\u2500\u2500 pkg.yml\n \u2502\u00a0\u00a0 \u2514\u2500\u2500 target.yml\n \u2514\u2500\u2500 unittest\n \u251c\u2500\u2500 pkg.yml\n \u2514\u2500\u2500 target.yml\n\n6 directories, 11 files\n\n\n\n\n\n\n\nThe Newt tool has installed the base files for a
project comprising the following:\n\n\n\n\nThe file \nproject.yml\n contains the repository list that the project uses to fetch\nits packages. Your project is a collection of repositories. In this case, the project just\ncomprises the core mynewt repository. Later you will add more repositories\nto include other mynewt components.\n\n\nThe file \napps/blinky/pkg.yml\n contains the description of your application\nand its package dependencies.\n\n\nA \ntarget\n directory containing \nmy_blinky_sim\n, a target descriptor used to\nbuild a version of myproj. Use \nnewt target show\n to see available build \ntargets.\n\n\nA non-buildable target called \nunittest\n. This is used internally by \nnewt\n and is not a formal build target.\n\n\n\n\nNOTE:\n The actual code and package files are not installed \n(except the template for \nmain.c\n). See the next step for installing the packages.\n\n\nNOTE:\n By default newt uses the code in the master branch. This is the latest stable\ncode
for newt. If you need to use a different branch, you can set this in the project.yml\nfile. \n\n\nrepository.apache-mynewt-core:\n type: github\n vers: 1-latest\n user: apache\n repo: incubator-mynewt-core\n\n\n\n\n\nChanging to 0-dev will put you on the latest master branch. \nThis 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 vi
ew 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\u250
2\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\u250
2\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\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\u25
00\u2500 stats\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 sysinit\n\u251c\u2500\u2500 targets\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 unittest\n\u251c\u2500\u2500 test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 crash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 flash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 runtest\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 testutil\n\u251c\u2500\u2500 time\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 datetime\n\u2514\u2500\u2500 util\n \u251c\u2500\u2500 cbmem\n \u251c\u2500\u2500 crc\n \u2514\u2500\u2500 mem\n\n94 directories, 9 files\n\n\n\n\n\nAs you can see, the core of the Apache Mynewt operating system has been brought \ninto your local directory. \n\n\n\n\nTest the project's packages\n\n\nYou have already built your first basic project. You can ask Newt to execute the unit tests in a package. For example, to test the \nsys/config\n package in the \napache-mynewt-core\n repo, call newt as shown below.\n\n\n$ newt test @apache-mynewt-core/sys/config\n
Testing 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/ap
ache-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 u
ninstall gcc-6\n$ brew link gcc-5\n\n\n\n\n\n\n\nTo test all the packages in a project, specify \nall\n instead of the package name.\n\n\n$ newt test all\nTesting package @apache-mynewt-core/boot/boot_serial/test\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/boot_test.c\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/testcases/boot_serial_setup.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/boot_boot_serial_test/app/boot/boot_serial/test/boot_boot_serial_test.elf\n\n...lots of compiling and testing...\n\nLinking ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nPassed tests: [boot/boot_serial/test boot/bootutil/test crypto/mbedtls/test encoding/base64/test encoding/cborattr/test encoding/json/test fs/fcb/test fs/nffs/test kernel/os/test net/ip/mn_socket/test net/nimble/host/test net/oic/test sys/
config/test-fcb sys/config/test-nffs sys/flash_map/test sys/log/full/test util/cbmem/test]\nAll tests passed\n\n\n\n\n\n\n\nBuild the Project\n\n\nTo build and run your new application, simply issue the following command:\n\n\n$ newt build my_blinky_sim \nBuilding target targets/my_blinky_sim\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_common.c\nCompiling repos/apache-mynewt-core/hw/drivers/uart/src/uart.c\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c\nCompiling repos/apache-mynewt-core/hw/bsp/native/src/hal_bsp.c\nCompiling repos/apache-mynewt-core/hw/drivers/uart/uart_hal/src/uart_hal.c\nCompiling apps/blinky/src/main.c\n\n ...\n\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nTarget successfully built: targets/my_blinky_sim\n\n\n\n\n\n\n\nRun the Project\n\n\nYou can run the simulated version of your project and see the simulated LED\nblink. If you are using ne
wt docker, use \nnewt run\n to run the simulated binary.\n\n\n$ newt run my_blinky_sim\nLoading app image into slot 1\n ...\nDebugging ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\n ...\nReading symbols from /bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf...done.\n(gdb)\n\n\n\n\n\nType \nr\n at the \n(gdb)\n prompt to run the project. You will see an output indicating that the hal_gpio pin is toggling between 1 and 0 in a simulated blink.\n\n\nIf you natively install the toolchain, you can either use \nnewt run\n or call the binary directly. Generally, \nnewt run\n is the expected way to call things.\n\n\n$ ./bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nhal_gpio set pin 1 to 0\n\n\n\n\n\n\n\nComplete\n\n\nCongratulations, you have created your first project! The blinky application\nis not terribly exciting when it is run in the simulator, as there is no LED to\nblink. Apache Mynewt has a lot more functionality than just running simulated\
napplications. It provides all the features you'll need to cross-compile your\napplication, run it on real hardware and develop a full featured application.\n\n\nIf you're interested in learning more, a good next step is to dig in to one of\nthe \ntutorials\n and get a Mynewt project running on real hardware.\n\n\nHappy Hacking!",
+ "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\nPrerequisites\n\n\n\n\nHave Internet connectivity to fetch remote Mynewt components.\n\n\nInstall Newt:\n\n\nIf you have taken the native install route, see the installation instructions for \nMac OS\n or for \nLinux\n. \n\n\nIf you have taken the Docker route, you have already installed Newt.\n\n\n\n\n\n\nInstall the \nnative toolchain\n to compile and build a Mynewt native application. \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 created.\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, run \nbrew install tree\n to install on Mac OS or run \nsudo apt-get install tree\n to install on Linux.\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 rep
ository 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 0-dev will put you on the latest master branch. \nThis 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 view them by issuing the following commands in the base directory of the new project. T
he 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\u2502\u00a0\u00a0 \u251c\u2500\u2500 ocf_sample\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 sl
inky\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\u2502\u00a0\u00a0 \u2514\u2500\u2500 tinycrypt\n\u251c\u2500\u2500 docs\n\u2502\u00a0\u00
a0 \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\u2500\u2500 baselibc\n\u251c\u2500\u2500 mgmt\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 imgmg
r\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 tar
gets\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 unittest\n\u251c\u2500\u2500 test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 crash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 flash_test\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 runtest\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 testutil\n\u251c\u2500\u2500 time\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 datetime\n\u2514\u2500\u2500 util\n \u251c\u2500\u2500 cbmem\n \u251c\u2500\u2500 crc\n \u2514\u2500\u2500 mem\n\n94 directories, 9 files\n\n\n\n\n\nAs you can see, the core of the Apache Mynewt operating system has been brought \ninto your local directory. \n\n\n\n\nTest the project's packages\n\n\nYou have already built your first basic project. You can ask Newt to execute the unit tests in a package. For example, to test the \nsys/config\n package in the \napache-mynewt-core\n repo, call newt as shown below.\n\n\n$ newt test @apache-mynewt-core/sys/config\nTesting package @apache-mynewt-core/sys/config/test-fcb\nCompiling bootutil_misc.c\nC
ompiling image_ec.c\nCompiling image_rsa.c\nCompiling image_validate.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-fcb/app/sys/config/test-fcb/sys_config_test-fcb.elf\nTesting package @apache-mynewt-core/sys/config/test-nffs\nCompiling repos/apache-mynewt-core/encoding/base64/src/hex.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_cli.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_dirent.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_mkdir.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_mount.c\nCompiling repos/apache-mynewt-core/encoding/base64/src/base64.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_file.c\nCompiling repos/apache-mynewt-core/fs/disk/src/disk.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fs_nmgr.c\nCompiling repos/apache-mynewt-core/fs/fs/src/fsutil.c\nCompiling repos/apache-mynewt-core/fs/nffs/src/n
ffs.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/sys_config_test-nffs/app/sys/config/test-nffs/sys_config_test-nffs.elf\nPassed tests: [sys/config/test-fcb sys/config/test-nffs]\nAll tests passed\n\n\n\n\n\nNOTE:\n If you've installed the latest gcc using homebrew on your Mac, you will likely be running gcc-6. Make sure you have adjusted the compiler.yml configuration to reflect that as noted in \nNative Install Option\n. You can choose to downgrade to gcc-5 in order to use the default gcc compiler configuration for MyNewt.\n\n\nNOTE:\n If you are running the standard gcc for 64-bit machines, it does not support 32-bit. In that case you will see compilation errors. You need to install multiboot gcc (e.g. gcc-multilib if you running on a 64-bit Ubuntu).\n\n\n$ brew uninstall gcc-6\n$ brew link gcc-5\n\n\n\n\n\n\n\nTo test all the packages in a projec
t, specify \nall\n instead of the package name.\n\n\n$ newt test all\nTesting package @apache-mynewt-core/boot/boot_serial/test\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/boot_test.c\nCompiling repos/apache-mynewt-core/boot/boot_serial/test/src/testcases/boot_serial_setup.c\n\n ...\n\nLinking ~/dev/myproj/bin/targets/unittest/boot_boot_serial_test/app/boot/boot_serial/test/boot_boot_serial_test.elf\n\n...lots of compiling and testing...\n\nLinking ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nExecuting test: ~/dev/myproj/bin/targets/unittest/util_cbmem_test/app/util/cbmem/test/util_cbmem_test.elf\nPassed tests: [boot/boot_serial/test boot/bootutil/test crypto/mbedtls/test encoding/base64/test encoding/cborattr/test encoding/json/test fs/fcb/test fs/nffs/test kernel/os/test net/ip/mn_socket/test net/nimble/host/test net/oic/test sys/config/test-fcb sys/config/test-nffs sys/flash_map/test sys/log/full/test util/cbmem/
test]\nAll tests passed\n\n\n\n\n\n\n\nBuild the Project\n\n\nTo build and run your new application, simply issue the following command:\n\n\n$ newt build my_blinky_sim \nBuilding target targets/my_blinky_sim\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_common.c\nCompiling repos/apache-mynewt-core/hw/drivers/uart/src/uart.c\nCompiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c\nCompiling repos/apache-mynewt-core/hw/bsp/native/src/hal_bsp.c\nCompiling repos/apache-mynewt-core/hw/drivers/uart/uart_hal/src/uart_hal.c\nCompiling apps/blinky/src/main.c\n\n ...\n\n\nArchiving sys_mfg.a\nArchiving sys_sysinit.a\nArchiving util_mem.a\nLinking ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nTarget successfully built: targets/my_blinky_sim\n\n\n\n\n\n\n\nRun the Project\n\n\nYou can run the simulated version of your project and see the simulated LED\nblink. If you are using newt docker, use \nnewt run\n to run the simulated binary.\n\n\n$ newt run my_blinky_si
m\nLoading app image into slot 1\n ...\nDebugging ~/dev/myproj/bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\n ...\nReading symbols from /bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf...done.\n(gdb)\n\n\n\n\n\nType \nr\n at the \n(gdb)\n prompt to run the project. You will see an output indicating that the hal_gpio pin is toggling between 1 and 0 in a simulated blink.\n\n\nIf you natively install the toolchain, you can either use \nnewt run\n or call the binary directly. Generally, \nnewt run\n is the expected way to call things.\n\n\n$ ./bin/targets/my_blinky_sim/app/apps/blinky/blinky.elf\nhal_gpio set pin 1 to 0\n\n\n\n\n\n\n\nComplete\n\n\nCongratulations, you have created your first project! The blinky application\nis not terribly exciting when it is run in the simulator, as there is no LED to\nblink. Apache Mynewt has a lot more functionality than just running simulated\napplications. It provides all the features you'll need to cross-compile your\nappli
cation, 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"
},
{
@@ -361,13 +371,13 @@
"title": "Create Your First Mynewt Project"
},
{
- "location": "/os/get_started/project_create/#pre-requisites",
- "text": "Newt: If you have taken the Docker route, you have already installed Newt. If you have taken the native install route, you have to ensure that you have installed the Newt tool following the instructions for Mac or Linux as appropriate, and that the newt command is in your system path. You must have Internet connectivity to fetch remote Mynewt components. You must install the compiler tools to \nsupport native compiling to build the project this tutorial creates.",
- "title": "Pre-Requisites"
+ "location": "/os/get_started/project_create/#prerequisites",
+ "text": "Have Internet connectivity to fetch remote Mynewt components. Install Newt: If you have taken the native install route, see the installation instructions for Mac OS or for Linux . If you have taken the Docker route, you have already installed Newt. Install the nativ
<TRUNCATED>
[5/7] incubator-mynewt-site git commit: changed runtimeinc to
runtimeco in docs, updated install instructions for linux ,
blinky for stm32F4-discovery
Posted by ad...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/newt/install/newt_linux/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/install/newt_linux/index.html b/develop/newt/install/newt_linux/index.html
index cbdbbd4..9e5bd62 100644
--- a/develop/newt/install/newt_linux/index.html
+++ b/develop/newt/install/newt_linux/index.html
@@ -213,7 +213,7 @@
- <li ><a href="../../../os/get_started/native_tools/">Native install Option</a>
+ <li ><a href="../../../os/get_started/native_install_intro/">Native Install Option</a>
<ul>
@@ -239,6 +239,14 @@
<li >
+ <a href="../../../os/get_started/native_tools/">Install Native Toolchain</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../../../os/get_started/cross_tools/">Install Cross Tools for ARM</a>
</li>
@@ -379,7 +387,7 @@
- <li>» <a href="../../../os/get_started/native_tools/">Native install Option</a></li>
+ <li>» <a href="../../../os/get_started/native_install_intro/">Native Install Option</a></li>
@@ -392,13 +400,13 @@
</div>
<h2 id="installing-newt-on-linux">Installing Newt on Linux</h2>
-<p>You can install the latest stable release (1.0.0) of newt from a Debian binary package (amd64) or from a Debian source package. This page shows you how to:</p>
+<p>You can install the latest stable release (1.0.0) of the newt tool from a Debian binary package (amd64) or from a Debian source package. This page shows you how to:</p>
<ol>
<li>Set up your computer to retrieve Debian packages from the runtimeco debian package repository.</li>
<li>Install the latest stable release version of newt from a Debian binary package. </li>
<li>Install the latest stable release version of newt from a Debian source package.</li>
</ol>
-<p>If you are running on an amd64 platform, we recommend that you install from the binary package.</p>
+<p>If you are installing on an amd64 platform, we recommend that you install from the binary package.</p>
<p><strong>Note:</strong> See <a href="../../../faq/go_env">Setting Up an Go Environment to Contribute to Newt and Newtmgr Tools</a> if you want to: </p>
<ul>
<li>Use the newt tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.</li>
@@ -406,55 +414,50 @@
</ul>
<p><br></p>
<h3 id="setting-up-your-computer-to-get-packages-from-runtimeco">Setting Up Your Computer to Get Packages from runtimeco</h3>
-<p>The newt Debian packages are stored in a private repository on <strong>https://github/runtimeco/debian-mynewt</strong>. </p>
-<p><strong>Note:</strong> You will only need to perform these steps only once on your computer.
-The following steps must be performed on your computer:</p>
+<p>The newt Debian packages are stored in a private repository on <strong>https://github/runtimeco/debian-mynewt</strong>. The following steps must be performed on your computer to retreive packages from the repository:</p>
+<p><strong>Note:</strong> You only need to perform this setup once on your computer.</p>
<ol>
-<li>Add the <code>apt-transport-https</code> package to use HTTPS to retrieve packages. </li>
+<li>Install the <code>apt-transport-https</code> package to use HTTPS to retrieve packages. </li>
<li>Download the public key for the runtimeco debian repository and import the key into the apt keychain.</li>
<li>Add the repository for the binary and source packages to the apt source list.</li>
</ol>
<p><br>
-Add the apt-transport-https package:</p>
+Install the apt-transport-https package:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get update
$sudo apt-get install apt-transport-https
</pre></div>
<p><br></p>
-<p>Download the public key for the runtimeco apt repo (<strong>Note:</strong> There is <code>-</code> after the add):</p>
+<p>Download the public key for the runtimeco apt repo (<strong>Note:</strong> There is a <code>-</code> after <code>apt-key add</code>):</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -
</pre></div>
<p><br></p>
-<p>Add the repository for the binary and source packages to the apt source list:</p>
+<p>Add the repository for the binary and source packages to the <code>mynewt.list</code> apt source list file.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo -s
[sudo] password for <user>:
root$ cat > /etc/apt/sources.list.d/mynewt.list <<EOF
deb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
deb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
EOF
+root$exit
</pre></div>
+<p><strong>Note:</strong> Do not forget to exit the root shell.</p>
<p><br>
-Check the content of the file:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">root$more /etc/apt/sources.list.d//mynewt.list
+Verify the content of the source list file:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$more /etc/apt/sources.list.d/mynewt.list
deb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
deb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
</pre></div>
<p><br> </p>
-<p>Exit the root shell:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">root$exit
-</pre></div>
-
-
-<p><br></p>
<h3 id="installing-the-latest-release-of-newt-from-a-binary-package">Installing the Latest Release of Newt from a Binary Package</h3>
-<p>For Linux amd64 platform, you can install the latest stable version (1.0.0) of newt from the newt Debian binary package:</p>
+<p>For Linux amd64 platforms, you can install the latest stable version (1.0.0) of newt from the newt Debian binary package:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get update
$sudo apt-get install newt
Reading package lists... Done
@@ -474,7 +477,7 @@ See <a href="#check">Checking the Installed Version of Newt</a> to verify that y
<p><br></p>
<h3 id="installing-the-latest-stable-release-of-newt-from-a-source-package">Installing the Latest Stable Release of Newt from a Source Package</h3>
<p>If you are running Linux on a different architecture, you can install the Debian source package for the latest stable release (1.0.0) of newt. The installation of the source package builds the newt binary and creates a Debian binary package that you then install.</p>
-<p><strong>Note</strong>: Newt version 1.0.0 has been tested on Linux amd64 platform. Version 1.0.0 does not build on the 32 bit platform but have been fixed for the next release.</p>
+<p><strong>Note</strong>: Newt version 1.0.0 has been tested on Linux amd64 platforms. Version 1.0.0 does not build on 32 bit platforms but have been fixed for the next release.</p>
<p><br></p>
<h4 id="installing-go-17">Installing Go 1.7</h4>
<p>You need Go version 1.7 or higher to build Newt version 1.0.0. Currently, the latest Go version that Ubuntu installs is 1.6. Run <code>go version</code> to check if you have Go 1.7 installed. </p>
@@ -522,9 +525,10 @@ W: Can't drop privileges for downloading as file 'newt_1.0.0-1.dsc'
</pre></div>
-<p><strong>Note:</strong> You can ignore the "Permission denied: warning message at the end of the command.</p>
+<p><strong>Note:</strong> You can ignore the "Permission denied" warning message at the end of the command.</p>
<p><br>
Install the newt binary package that is created from the source package:</p>
+<p><strong>Note:</strong> The file name for the binary package has the format: newt_1.0.0-1_<strong>arch</strong>.deb, where <strong>arch</strong> is a value that identifies your host architecture. </p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo dpkg -i newt_1.0.0-1_amd64.deb
Selecting previously unselected package newt.
(Reading database ... 252969 files and directories currently installed.)
@@ -547,7 +551,7 @@ Apache Newt (incubating) version: 1.0.0
</pre></div>
-<p><strong>Note:</strong> If you previously built newt from source and the output of <code>which newt</code> shows "$GOPATH/bin/newt", you will need to move "$GOPATH/bin" after "/usr/bin" in your $PATH and export your $PATH.</p>
+<p><strong>Note:</strong> If you previously built newt from source and the output of <code>which newt</code> shows "$GOPATH/bin/newt", you will need to move "$GOPATH/bin" after "/usr/bin" for your PATH environment variable and export it. </p>
<p><br>
Get information about newt:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt
@@ -621,8 +625,8 @@ Use "newt [command] --help" for more information about a command.
</li>
<li class="pull-right">
- <a href=../../../os/get_started/cross_tools/>
- Next: Install Cross Tools for ARM
+ <a href=../../../os/get_started/native_tools/>
+ Next: Install Native Toolchain
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/newt/install/newt_mac/index.html
----------------------------------------------------------------------
diff --git a/develop/newt/install/newt_mac/index.html b/develop/newt/install/newt_mac/index.html
index 7f93f5f..dc66d91 100644
--- a/develop/newt/install/newt_mac/index.html
+++ b/develop/newt/install/newt_mac/index.html
@@ -213,7 +213,7 @@
- <li ><a href="../../../os/get_started/native_tools/">Native install Option</a>
+ <li ><a href="../../../os/get_started/native_install_intro/">Native Install Option</a>
<ul>
@@ -239,6 +239,14 @@
<li >
+ <a href="../../../os/get_started/native_tools/">Install Native Toolchain</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../../../os/get_started/cross_tools/">Install Cross Tools for ARM</a>
</li>
@@ -379,7 +387,7 @@
- <li>» <a href="../../../os/get_started/native_tools/">Native install Option</a></li>
+ <li>» <a href="../../../os/get_started/native_install_intro/">Native Install Option</a></li>
@@ -550,9 +558,9 @@ Apache Newt (incubating) version: 1.0.0
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../../../os/get_started/native_tools/>
+ <a href=../../../os/get_started/native_install_intro/>
<span class="fa fa-arrow-left"></span>
- Previous: Native install Option
+ Previous: Native Install Option
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/newtmgr/install_linux/index.html
----------------------------------------------------------------------
diff --git a/develop/newtmgr/install_linux/index.html b/develop/newtmgr/install_linux/index.html
index c191e51..d955629 100644
--- a/develop/newtmgr/install_linux/index.html
+++ b/develop/newtmgr/install_linux/index.html
@@ -373,7 +373,7 @@
</div>
<h2 id="installing-newtmgr-on-linux">Installing Newtmgr on Linux</h2>
-<p>You can install the latest stable release (1.0.0) of newtmgr from a Debian binary package (amd64) or from a Debian source package. This page shows you how to:</p>
+<p>You can install the latest stable release (1.0.0) of the newtmgr tool from a Debian binary package (amd64) or from a Debian source package. This page shows you how to:</p>
<ol>
<li>
<p>Set up your computer to retrieve Debian packages from the runtimeco debian package repository. </p>
@@ -384,7 +384,7 @@
</li>
<li>Install the latest stable release version of newtmgr from a Debian source package.</li>
</ol>
-<p>If you are running on an amd64 platform, we recommend that you install from the binary package.</p>
+<p>If you are installing on an amd64 platform, we recommend that you install from the binary package.</p>
<p><strong>Note:</strong> See <a href="../../faq/go_env">Setting Up an Go Environment to Contribute to Newt and Newtmgr Tools</a> if you want to: </p>
<ul>
<li>Use the newtmgr tool with the latest updates from the master branch. The master branch may be unstable and we recommend that you use the latest stable release version.</li>
@@ -392,55 +392,50 @@
</ul>
<p><br></p>
<h3 id="setting-up-your-computer-to-get-packages-from-runtimeco">Setting Up Your Computer to Get Packages from runtimeco</h3>
-<p>The newtmgr Debian packages are stored in a private repository on <strong>https://github/runtimeco/debian-mynewt</strong>. </p>
-<p><strong>Note</strong>: You will only need to perform these steps once on your computer. You can skip this step if you already set up your computer to access the runtimeco debian repository when you installed the newt tool. </p>
-<p>The following steps must be performed on your computer:</p>
+<p>The newtmgr Debian packages are stored in a private repository on <strong>https://github/runtimeco/debian-mynewt</strong>. You must set up the following on your computer to retreive packages from the repository:</p>
+<p><strong>Note</strong>: You only need to perform this setup once on your computer and you may have already done so when you installed the newt tool. </p>
<ol>
-<li>Add the <code>apt-transport-https</code> package to use HTTPS to retrieve packages. </li>
+<li>Install the <code>apt-transport-https</code> package to use HTTPS to retrieve packages. </li>
<li>Download the public key for the runtimeco debian repository and import the key into the apt keychain.</li>
<li>Add the repository for the binary and source packages to the apt source list.</li>
</ol>
<p><br>
-Add the apt-transport-https package:</p>
+Install the apt-transport-https package:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get update
$sudo apt-get install apt-transport-https
</pre></div>
<p><br></p>
-<p>Download the public key for the runtimeco apt repo (<strong>Note:</strong> There is <code>-</code> after the add):</p>
+<p>Download the public key for the runtimeco apt repo (<strong>Note:</strong> There is a <code>-</code> after <code>apt-key add</code>):</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -
</pre></div>
<p><br></p>
-<p>Add the repository for the binary and source packages to the apt source list:</p>
+<p>Add the repository for the binary and source packages to the <code>mynewt.list</code> apt source list file.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo -s
[sudo] password for <user>:
root$ cat > /etc/apt/sources.list.d/mynewt.list <<EOF
deb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
deb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
EOF
+root$exit
</pre></div>
+<p><strong>Note:</strong> Do not forget to exit the root shell.</p>
<p><br>
-Check the content of the file:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">root$more /etc/apt/sources.list.d//mynewt.list
+Verify the content of the source list file:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$more /etc/apt/sources.list.d/mynewt.list
deb https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
deb-src https://raw.githubusercontent.com/runtimeco/debian-package/master latest main
</pre></div>
<p><br> </p>
-<p>Exit the root shell:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">root$exit
-</pre></div>
-
-
-<p><br></p>
<h3 id="installing-the-latest-release-of-newtmgr-from-a-binary-package">Installing the Latest Release of Newtmgr from a Binary Package</h3>
-<p>For Linux amd64 platform, you can install the latest stable version (1.0.0) of newtmgr from the newtmgr Debian binary package:</p>
+<p>For Linux amd64 platforms, you can install the latest stable version (1.0.0) of newtmgr from the newtmgr Debian binary package:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get update
$sudo apt-get install newtmgr
Reading package lists... Done
@@ -464,7 +459,7 @@ See <a href="#check">Checking the Installed Version of Newtmgr</a> to verify tha
<p><br></p>
<h3 id="installing-the-latest-stable-release-of-newtmgr-from-a-source-package">Installing the Latest Stable Release of Newtmgr from a Source Package</h3>
<p>If you are running Linux on a different architecture, you can install the Debian source package for the latest stable release (1.0.0) of newtmgr. The installation of the source package builds the newtmgr binary and creates a Debian binary package that you then install.</p>
-<p><strong>Note</strong>: Newtmgr version 1.0.0 has been tested on Linux amd64 platform. </p>
+<p><strong>Note</strong>: Newtmgr version 1.0.0 has been tested on Linux amd64 platforms. </p>
<p><br></p>
<h4 id="installing-go-17">Installing Go 1.7</h4>
<p>You need Go version 1.7 or higher to build Newtmgr version 1.0.0. Currently, the latest Go version that Ubuntu installs is 1.6. Run <code>go version</code> to check if you have Go 1.7 installed. </p>
@@ -506,12 +501,20 @@ dpkg-deb: building package 'newtmgr' in '../newtmgr_1.0.0-1_amd64.de
dpkg-genchanges: info: binary-only upload (no source code included)
dpkg-source --after-build newtmgr-1.0.0
dpkg-buildpackage: info: binary-only upload (no source included)
+W: Can't drop privileges for downloading as file 'newtmgr_1.0.0-1.dsc' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
</pre></div>
+<p><strong>Note:</strong> You can ignore the "Permission denied" warning message at the end of the command.</p>
<p><br>
Install the newtmgr binary package that is created from the source package:</p>
+<p><strong>Note:</strong> The file name for the binary package has the format: newtmgr_1.0.0-1_<strong>arch</strong>.deb, where <strong>arch</strong> is a value that identifies your host architecture.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo dpkg -i newtmgr_1.0.0-1_amd64.deb
+Selecting previously unselected package newtmgr.
+(Reading database ... 215099 files and directories currently installed.)
+Preparing to unpack newtmgr_1.0.0-1_amd64.deb ...
+Unpacking newtmgr (1.0.0-1) ...
+Setting up newtmgr (1.0.0-1) ...
</pre></div>
@@ -526,7 +529,7 @@ $which newtmgr
</pre></div>
-<p><strong>Note:</strong> If you previously built newtmgr from source and the output of <code>which newtmgr</code> shows "$GOPATH/bin/newtmgr", you will need to move "$GOPATH/bin" after "/usr/bin" in your $PATH and export your $PATH.</p>
+<p><strong>Note:</strong> If you previously built newtmgr from source and the output of <code>which newtmgr</code> shows "$GOPATH/bin/newtmgr", you will need to move "$GOPATH/bin" after "/usr/bin" for your PATH environment variable and export it.</p>
<p><br>
Get information about newtmgr:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newtmgr
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/os/get_started/cross_tools/index.html
----------------------------------------------------------------------
diff --git a/develop/os/get_started/cross_tools/index.html b/develop/os/get_started/cross_tools/index.html
index 6398a54..05f0dba 100644
--- a/develop/os/get_started/cross_tools/index.html
+++ b/develop/os/get_started/cross_tools/index.html
@@ -213,7 +213,7 @@
- <li ><a href="../native_tools/">Native install Option</a>
+ <li ><a href="../native_install_intro/">Native Install Option</a>
<ul>
@@ -238,6 +238,14 @@
+ <li >
+ <a href="../native_tools/">Install Native Toolchain</a>
+ </li>
+
+
+
+
+
<li class="active">
<a href="./">Install Cross Tools for ARM</a>
</li>
@@ -379,7 +387,7 @@
- <li>» <a href="../native_tools/">Native install Option</a></li>
+ <li>» <a href="../native_install_intro/">Native Install Option</a></li>
@@ -525,9 +533,9 @@ http://openocd.org/doc/doxygen/bugs.html
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../../../newt/install/newt_linux/>
+ <a href=../native_tools/>
<span class="fa fa-arrow-left"></span>
- Previous: Install Newt on Linux
+ Previous: Install Native Toolchain
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/os/get_started/docker/index.html
----------------------------------------------------------------------
diff --git a/develop/os/get_started/docker/index.html b/develop/os/get_started/docker/index.html
index efb3ea4..83cd079 100644
--- a/develop/os/get_started/docker/index.html
+++ b/develop/os/get_started/docker/index.html
@@ -213,7 +213,7 @@
- <li ><a href="../native_tools/">Native install Option</a>
+ <li ><a href="../native_install_intro/">Native Install Option</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/os/get_started/get_started/index.html
----------------------------------------------------------------------
diff --git a/develop/os/get_started/get_started/index.html b/develop/os/get_started/get_started/index.html
index 9b8332e..997790a 100644
--- a/develop/os/get_started/get_started/index.html
+++ b/develop/os/get_started/get_started/index.html
@@ -213,7 +213,7 @@
- <li ><a href="../native_tools/">Native install Option</a>
+ <li ><a href="../native_install_intro/">Native Install Option</a>
</li>
@@ -391,8 +391,8 @@
</li>
<li class="pull-right">
- <a href=../native_tools/>
- Next: Native install Option
+ <a href=../native_install_intro/>
+ Next: Native Install Option
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/os/get_started/native_install_intro/index.html
----------------------------------------------------------------------
diff --git a/develop/os/get_started/native_install_intro/index.html b/develop/os/get_started/native_install_intro/index.html
new file mode 100644
index 0000000..e8df52f
--- /dev/null
+++ b/develop/os/get_started/native_install_intro/index.html
@@ -0,0 +1,476 @@
+<!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/get_started/native_install_intro/"> -->
+ <link rel="shortcut icon" href="../../../img/favicon.ico">
+
+ <title>toc - Apache Mynewt</title>
+
+ <link href="../../../css/bootstrap-3.0.3.min.css" rel="stylesheet">
+ <link rel="stylesheet" href="../../../css/highlight.css">
+ <link href="../../../css/base.css" rel="stylesheet">
+ <link href="../../../css/custom.css" rel="stylesheet">
+ <link href="../../../css/v2.css" rel="stylesheet">
+ <link href="https://fonts.googleapis.com/css?family=Lato" rel="stylesheet">
+ <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css">
+ <link href="../../../extra.css" rel="stylesheet">
+
+ <!-- HTML5 shim and Respond.js IE8 support of HTML5 elements and media queries -->
+ <!--[if lt IE 9]>
+ <script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script>
+ <script src="https://oss.maxcdn.com/libs/respond.js/1.3.0/respond.min.js"></script>
+ <![endif]-->
+
+
+ <script>
+ (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
+ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
+ m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
+ })(window,document,'script','//www.google-analytics.com/analytics.js','ga');
+
+ ga('create', 'UA-72162311-1', 'auto');
+ ga('send', 'pageview');
+ </script>
+
+ </head>
+
+
+ <body class="toc">
+
+
+ <div class="container">
+ <div class="row v2-main-banner">
+ <a class="logo-cell" href="/">
+ <img class="logo" src="/img/logo.png">
+ </a>
+ <div class="tagline-cell">
+ <h4 class="tagline">An OS to build, deploy and securely manage billions of devices</h4>
+ </div>
+ <div class="news-cell">
+ <div class="well">
+ <h4>Latest News:</h4> <a href="/download">Apache Mynewt 1.0.0</a> released (March 22, 2017)
+ </div>
+ </div>
+ </div>
+</div>
+
+
+
+
+
+
+
+
+<nav id="navbar" class="navbar navbar-inverse affix-top" data-spy="affix" data-offset-top="150" role="navigation">
+ <div class="container">
+ <!-- Collapsed navigation -->
+ <div class="navbar-header">
+ <!-- Expander button -->
+ <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
+ <span class="sr-only">Toggle navigation</span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ </button>
+
+ </div>
+
+ <!-- Expanded navigation -->
+ <div class="navbar-collapse collapse">
+ <!-- Main navigation -->
+ <ul class="nav navbar-nav navbar-right">
+ <li
+ class=""
+>
+ <a href="/"><i class="fa fa-home" style="font-size: larger;"></i></a>
+ </li>
+ <li
+ class="important"
+>
+ <a href="/quick-start/">Quick Start</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/about/">About</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/talks/">Talks</a>
+ </li>
+ <li
+ class="active"
+>
+ <a href="/latest/os/introduction">Documentation</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/download/">Download</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/community/">Community</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/events/">Events</a>
+ </li>
+ </ul>
+
+ <!-- Search, Navigation and Repo links -->
+ <ul class="nav navbar-nav navbar-right">
+
+ </ul>
+ </div>
+ </div>
+</nav>
+
+
+
+ <div class="container">
+
+ <div class="row">
+ <div class="col-md-3 v2-sidebar sidebar-container"><div id="docSidebar" class="hidden-print" role="complementary">
+ <div class="top">
+ <div role="search">
+ <form id="rtd-search-form" class="wy-form" action="../../../search.html" method="get">
+ <div class="form-group">
+ <input type="text" name="q" class="form-control" placeholder="Search documentation" />
+ </div>
+ </form>
+ </div>
+ </div>
+ <ul class="toc-nav">
+ <li class="doc-version">
+<select class="form-control" onchange="if (this.value) window.location.href=this.value">
+
+ <option
+ value="/develop/os/introduction"
+ selected="selected"
+ >
+ Version: develop (latest)
+ </option>
+
+ <option
+ value="/v0_9_0/os/introduction"
+
+ >
+ Version: 0.9.0
+ </option>
+
+</select>
+</li>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ <li ><a href="../../introduction/">Mynewt Documentation</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../get_started/">Basic Setup</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li class="active"><a href="./">Native Install Option</a>
+
+
+ <ul>
+
+
+
+
+
+ <li >
+ <a href="../../../newt/install/newt_mac/">Install Newt on Mac</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../../newt/install/newt_linux/">Install Newt on Linux</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../native_tools/">Install Native Toolchain</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../cross_tools/">Install Cross Tools for ARM</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../docker/">Docker Container Option</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../project_create/">Create Your First Project</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../serial_access/">Serial Port Setup</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../vocabulary/">Concepts</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../tutorials/tutorials/">Tutorials</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../os_user_guide/">OS User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../../network/ble/ble_intro/
+">BLE User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../newt/newt_intro/">Newt Tool Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../newtmgr/overview/">Newt Manager Guide</a>
+
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../../faq/go_env/
+">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="../get_started/">Basic Setup</a></li>
+
+
+
+ <li>» Native Install Option</li>
+
+
+
+
+
+ </ul>
+</div>
+ </div>
+
+ <h1 id="native-installation">Native Installation</h1>
+<p>This section shows you how to install tools on Mac OS and Linux platforms to develop, build, run, and debug Mynewt OS applications. You can build Mynewt OS applications to run as a native application on your computer or to run on your target board. These tools include:</p>
+<ul>
+<li>
+<p>Newt tool - Tool to create, build, load, and debug a mynewt target.</p>
+<ul>
+<li>See <a href="../../../newt/install/newt_mac/">Installing the Newt Tool on Mac OS</a> to install on Mac OS.</li>
+<li>See <a href="../../../newt/install/newt_linux/">Installing the Newt Tool on Linux</a> to install on Linux.</li>
+</ul>
+</li>
+</ul>
+<p><br></p>
+<ul>
+<li>
+<p>Native toolchain - Native toolchain to build and run Mynewt OS as a native application on your computer.
+ (See <a href="/os/get_started/native_install.md">Installing Native Toolchain</a>). </p>
+</li>
+<li>
+<p>Cross toolchain for ARM - Cross toolchain for ARM to build and run a Mynewt OS application on a target board
+ (See <a href="../cross_tools/">Installing Cross Tools for ARMs</a>).</p>
+</li>
+</ul>
+
+ <div class="row">
+
+
+
+
+<ul class="nav nav-pills" style="margin-bottom: 10px">
+ <li>
+
+ <a href=../get_started/>
+ <span class="fa fa-arrow-left"></span>
+ Previous: Basic Setup
+ </a>
+
+ </li>
+ <li class="pull-right">
+
+ <a href=../../../newt/install/newt_mac/>
+ Next: Install Newt on Mac
+ <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/ea2670d6/develop/os/get_started/native_tools/index.html
----------------------------------------------------------------------
diff --git a/develop/os/get_started/native_tools/index.html b/develop/os/get_started/native_tools/index.html
index 2e4082a..d69ab06 100644
--- a/develop/os/get_started/native_tools/index.html
+++ b/develop/os/get_started/native_tools/index.html
@@ -10,7 +10,7 @@
<link rel="canonical" href="http://mynewt.apache.org/os/get_started/native_tools/"> -->
<link rel="shortcut icon" href="../../../img/favicon.ico">
- <title>toc - Apache Mynewt</title>
+ <title>Install Native Toolchain - 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="toc">
+ <body class="Install Native Toolchain">
<div class="container">
@@ -213,7 +213,7 @@
- <li class="active"><a href="./">Native install Option</a>
+ <li ><a href="../native_install_intro/">Native Install Option</a>
<ul>
@@ -238,6 +238,14 @@
+ <li class="active">
+ <a href="./">Install Native Toolchain</a>
+ </li>
+
+
+
+
+
<li >
<a href="../cross_tools/">Install Cross Tools for ARM</a>
</li>
@@ -379,10 +387,12 @@
- <li>» Native install Option</li>
+ <li>» <a href="../native_install_intro/">Native Install Option</a></li>
+ <li>» Install Native Toolchain</li>
+
</ul>
@@ -497,7 +507,7 @@ Setting up gdb (7.7.1-0ubuntu5~14.04.2) ...
<p><br></p>
-<p>At this point you have installed all the necessary software to build and test code on a simluator running on your Mac or Linux. Proceed to the <a href="../project_create/">Create Your First Project</a> section.</p>
+<p>At this point you have installed all the necessary software to build and run your first project on a simluator on your Mac OS or Linux computer. You may proceed to the <a href="../project_create/">Create Your First Project</a> section or continue to the next section and install the cross tools for ARM.</p>
<div class="row">
@@ -507,16 +517,16 @@ Setting up gdb (7.7.1-0ubuntu5~14.04.2) ...
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../get_started/>
+ <a href=../../../newt/install/newt_linux/>
<span class="fa fa-arrow-left"></span>
- Previous: Basic Setup
+ Previous: Install Newt on Linux
</a>
</li>
<li class="pull-right">
- <a href=../../../newt/install/newt_mac/>
- Next: Install Newt on Mac
+ <a href=../cross_tools/>
+ Next: Install Cross Tools for ARM
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/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 c932da5..ee89474 100644
--- a/develop/os/get_started/project_create/index.html
+++ b/develop/os/get_started/project_create/index.html
@@ -213,7 +213,7 @@
- <li ><a href="../native_tools/">Native install Option</a>
+ <li ><a href="../native_install_intro/">Native Install Option</a>
</li>
@@ -364,16 +364,15 @@
<h2 id="create-your-first-mynewt-project">Create Your First Mynewt Project</h2>
<p>This page shows how to create a Mynewt Project using the <code>newt</code> command-line tool.</p>
<p><br></p>
-<h3 id="pre-requisites">Pre-Requisites</h3>
+<h3 id="prerequisites">Prerequisites</h3>
<ul>
-<li>Newt:<ul>
+<li>Have Internet connectivity to fetch remote Mynewt components.</li>
+<li>Install Newt:<ul>
+<li>If you have taken the native install route, see the installation instructions for <a href="../../../newt/install/newt_mac/">Mac OS</a> or for <a href="../../../newt/install/newt_linux/">Linux</a>. </li>
<li>If you have taken the Docker route, you have already installed Newt.</li>
-<li>If you have taken the native install route, you have to ensure that you have installed the Newt tool following the instructions for <a href="../../../newt/install/newt_mac/">Mac</a> or <a href="../../../newt/install/newt_linux/">Linux</a> as appropriate, and that the <code>newt</code> command is in your system path. </li>
</ul>
</li>
-<li>You must have Internet connectivity to fetch remote Mynewt components.</li>
-<li>You must <a href="../native_tools/">install the compiler tools</a> to
-support native compiling to build the project this tutorial creates. </li>
+<li>Install the <a href="../native_tools/">native toolchain</a> to compile and build a Mynewt native application. </li>
</ul>
<p><br></p>
<h3 id="newt-new">Newt New</h3>
@@ -389,7 +388,7 @@ Project myproj successfully created.
<p><br></p>
<p>Newt populates this new project with a base skeleton of a new Apache Mynewt
project. It has the following structure. </p>
-<p><strong>Note</strong>: If you do not have <code>tree</code>, install it by running <code>brew install tree</code>.</p>
+<p><strong>Note</strong>: If you do not have <code>tree</code>, run <code>brew install tree</code> to install on Mac OS or run <code>sudo apt-get install tree</code> to install on Linux.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ cd myproj
$ tree
.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/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 09ccfd8..ade0b64 100644
--- a/develop/os/get_started/serial_access/index.html
+++ b/develop/os/get_started/serial_access/index.html
@@ -213,7 +213,7 @@
- <li ><a href="../native_tools/">Native install Option</a>
+ <li ><a href="../native_install_intro/">Native Install Option</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/os/modules/drivers/driver/index.html
----------------------------------------------------------------------
diff --git a/develop/os/modules/drivers/driver/index.html b/develop/os/modules/drivers/driver/index.html
index 265adb8..a59faa5 100644
--- a/develop/os/modules/drivers/driver/index.html
+++ b/develop/os/modules/drivers/driver/index.html
@@ -573,7 +573,7 @@
<p>Device drivers should have a consistent structure and unified interface whenever possible. For example, we have a top-level package, “adc”, which contains the interface for all ADC drivers, and then we have the individual implementation of the driver itself. The following source files point to this:</p>
<ul>
<li>high-level ADC API: <code>hw/drivers/adc/include/adc/adc.h</code> </li>
-<li>implementation of ADC for STM32F4: <code>hw/drivers/adc/adc_stm32f4/src/adc_stm32f4.c</code> (As of the 1.0.0-beta release, ADC for nRF51 and nRF52 are available at an external <a href="https://github.com/runtimeinc/mynewt_nordic/tree/master/hw/drivers/adc">repo</a>. They are expected to be pulled into the core repo on Apache Mynewt after the license terms are clarified.). The only exported call in this example is <code>int stm32f4_adc_dev_init(struct os_dev *, void *)</code> which is passed as a function pointer to <code>os_dev_create()</code> in <code>hal_bsp.c</code>, when the adc device is created.</li>
+<li>implementation of ADC for STM32F4: <code>hw/drivers/adc/adc_stm32f4/src/adc_stm32f4.c</code> (As of the 1.0.0-beta release, ADC for nRF51 and nRF52 are available at an external <a href="https://github.com/runtimeco/mynewt_nordic/tree/master/hw/drivers/adc">repo</a>. They are expected to be pulled into the core repo on Apache Mynewt after the license terms are clarified.). The only exported call in this example is <code>int stm32f4_adc_dev_init(struct os_dev *, void *)</code> which is passed as a function pointer to <code>os_dev_create()</code> in <code>hal_bsp.c</code>, when the adc device is created.</li>
</ul>
</li>
<li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/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 689a114..ccebf5b 100644
--- a/develop/os/tutorials/add_newtmgr/index.html
+++ b/develop/os/tutorials/add_newtmgr/index.html
@@ -490,12 +490,10 @@ to customize your application.</p>
<h3 id="prerequisites">Prerequisites</h3>
<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
<ul>
-<li>Install the <a href="../../../newt/install/newt_mac/">newt tool</a>. </li>
-<li>Install the <a href="../../../newtmgr/install_mac/">newtmgr tool</a>.</li>
<li>Have Internet connectivity to fetch remote Mynewt components.</li>
-<li>Install the <a href="../../get_started/native_tools/">compiler tools</a> to
-support native compiling to build the project this tutorial creates. </li>
<li>Have a cable to establish a serial USB connection between the board and the laptop.</li>
+<li>Install the newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
+<li>Install the <a href="../../../newtmgr/install_mac/">newtmgr tool</a>.</li>
</ul>
<p><br></p>
<h3 id="use-an-existing-project">Use an Existing Project</h3>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/os/tutorials/add_shell/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/add_shell/index.html b/develop/os/tutorials/add_shell/index.html
index e5d907f..8b14c3e 100644
--- a/develop/os/tutorials/add_shell/index.html
+++ b/develop/os/tutorials/add_shell/index.html
@@ -476,16 +476,13 @@
<p>This tutorial explains how to add the Console and Shell task to a project so that you
can interact with your project over a serial line connection.</p>
<p><br></p>
-<h3 id="pre-requisites">Pre-Requisites</h3>
+<h3 id="prerequisites">Prerequisites</h3>
+<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
<ul>
-<li>Ensure you have installed <a href="../../../newt/install/newt_mac/">newt</a> and that the
-newt command is in your system path. </li>
-<li>You must have Internet connectivity to fetch remote Mynewt components.</li>
-<li>You must <a href="../../get_started/native_tools/">install the compiler tools</a> to
-support native compiling to build the project this tutorial creates. </li>
-<li>You must install the <a href="https://www.segger.com/jlink-software.html">Segger JLINK package</a> to
-load your project on the board.</li>
-<li>Cable to establish a serial USB connection between the board and the laptop</li>
+<li>Have Internet connectivity to fetch remote Mynewt components. </li>
+<li>Have a cable to establish a serial USB connection between the board and the laptop</li>
+<li>Install the newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
+<li>Install the <a href="https://www.segger.com/jlink-software.html">Segger JLINK package</a> to load your project on the board.</li>
</ul>
<p><br></p>
<h3 id="use-an-existing-project">Use an existing project</h3>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/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 41b0eb3..7b2bc85 100644
--- a/develop/os/tutorials/arduino_zero/index.html
+++ b/develop/os/tutorials/arduino_zero/index.html
@@ -282,6 +282,14 @@
<li >
+ <a href="../blinky_stm32f4disc/">Blinky on STM32F4-Discovery</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../blinky_console/">Add Console and Shell to Blinky</a>
</li>
@@ -559,7 +567,7 @@ Note: There are many flavors of Arduino. Make sure you are using an Arduino Zero
<p><br></p>
<h3 id="fetch-external-packages"><a name="fetchexternal"></a> Fetch External Packages</h3>
<p>Mynewt uses source code provided directly from the chip manufacturer for
-low 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.</p>
+low 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.</p>
<p>To fetch the package with MCU support for Atmel SAMD21 for Arduino Zero from the Runtime git repository, you need to add
the repository to the <code>project.yml</code> file in your base project directory.</p>
<p>Here is an example <code>project.yml</code> file with the Arduino Zero repository
@@ -581,7 +589,7 @@ repository.apache-mynewt-core:
<span style="background-color: #ffffcc">repository.mynewt_arduino_zero:
</span><span style="background-color: #ffffcc"> type: github
</span><span style="background-color: #ffffcc"> vers: 1-latest
-</span><span style="background-color: #ffffcc"> user: runtimeinc
+</span><span style="background-color: #ffffcc"> user: runtimeco
</span><span style="background-color: #ffffcc"> repo: mynewt_arduino_zero
</span>$
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/os/tutorials/blehci_project/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/blehci_project/index.html b/develop/os/tutorials/blehci_project/index.html
index 06932ac..2fdbcb0 100644
--- a/develop/os/tutorials/blehci_project/index.html
+++ b/develop/os/tutorials/blehci_project/index.html
@@ -476,20 +476,18 @@
<p>This tutorial explains how to use the example application <code>blehci</code> included in the NimBLE stack to talk to the Mynewt NimBLE controller via the Host Controller Interface. You may build the Mynewt image using a laptop running any OS of your choice - Mac, Linux, or Windows.</p>
<p>The host used in this specific example is the BlueZ Bluetooth stack. Since BlueZ is a Bluetooth stack for Linux kernel-based family of operating system, the tutorial expects a computer running Linux OS and with BlueZ installed to talk to the board with the Mynewt image.</p>
<p><br></p>
-<h3 id="pre-requisites">Pre-Requisites</h3>
+<h3 id="prerequisites">Prerequisites</h3>
+<p>Ensure that you meet the following prerequisites before continuing with one of the tutorials.</p>
<ul>
-<li>Ensure you have installed <a href="../../../newt/install/newt_mac/">newt</a> and that the
-newt command is in your system path. </li>
-<li>You must have Internet connectivity to fetch remote Mynewt components.</li>
-<li>If you are not using the Docker container for newt and other tools, you must <a href="../../get_started/native_tools/">install the compiler tools</a> to
-support native compiling to build the project this tutorial creates. </li>
-<li>You have a board with BLE radio that is supported by Mynewt. We will use an nRF52 Dev board in this tutorial.</li>
-<li>USB TTL Serial Cable that supports hardware flow control such as ones found at <a href="http://www.ftdichip.com/Products/Cables/USBTTLSerial.htm">http://www.ftdichip.com/Products/Cables/USBTTLSerial.htm</a> to establish a serial USB connection between the board and the laptop.</li>
-<li>You have installed a BLE host such as BlueZ on a Linux machine to talk to the nrf52 board running Mynewt. Use <code>sudo apt-get install bluez</code> to install it on your Linux machine. </li>
+<li>Have Internet connectivity to fetch remote Mynewt components.</li>
+<li>Have a board with BLE radio that is supported by Mynewt. We will use an nRF52 Dev board in this tutorial.</li>
+<li>Have a USB TTL Serial Cable that supports hardware flow control such as ones found at <a href="http://www.ftdichip.com/Products/Cables/USBTTLSerial.htm">http://www.ftdichip.com/Products/Cables/USBTTLSerial.htm</a> to establish a serial USB connection between the board and the laptop.</li>
+<li>Install the newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
+<li>Install a BLE host such as BlueZ on a Linux machine to talk to the nrf52 board running Mynewt. Use <code>sudo apt-get install bluez</code> to install it on your Linux machine. </li>
</ul>
<p><br></p>
<h3 id="create-a-project">Create a project</h3>
-<p>Use the Newt tool to create a new project directory containing a skeletal Mynewt framework. Change into the newly created directory. </p>
+<p>Use the newt tool to create a new project directory containing a skeletal Mynewt framework. Change into the newly created directory. </p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt new blehciproj
Downloading project skeleton from apache/incubator-mynewt-blinky...
Installing skeleton in blehciproj ...
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/os/tutorials/bletiny_project/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/bletiny_project/index.html b/develop/os/tutorials/bletiny_project/index.html
index 0e52dcf..94b4bf7 100644
--- a/develop/os/tutorials/bletiny_project/index.html
+++ b/develop/os/tutorials/bletiny_project/index.html
@@ -476,19 +476,17 @@
<p>This tutorial explains how to run an example BLE app on a board and command it to scan and spew some stats. The stats will be seen over a serial port, not a BLE wireless connection.</p>
<p><br></p>
<h3 id="prerequisites">Prerequisites</h3>
+<p>Ensure that you have met the following prerequisites before continuing with this tutorial:</p>
<ul>
-<li>Ensure you have installed <a href="../../../newt/install/newt_mac/">newt</a> and that the
-newt command is in your system path. </li>
-<li>You must have Internet connectivity to fetch remote Mynewt components.</li>
-<li>You must <a href="../../get_started/native_tools/">install the compiler tools</a> to
-support native compiling to build the project this tutorial creates. </li>
-<li>You must install the <a href="https://www.segger.com/jlink-software.html">Segger JLINK package</a> to load your project on the board.</li>
-<li>You have a board with BLE radio that is supported by Mynewt. We will use an nRF52 Dev board in this tutorial.</li>
-<li>Cable to establish a serial USB connection between the board and the laptop</li>
+<li>Have Internet connectivity to fetch remote Mynewt components.</li>
+<li>Have a board with BLE radio that is supported by Mynewt. We will use an nRF52 Dev board in this tutorial.</li>
+<li>Have a cable to establish a serial USB connection between the board and the laptop</li>
+<li>Install the newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
+<li>Install the <a href="https://www.segger.com/jlink-software.html">Segger JLINK package</a> to load your project on the board.</li>
</ul>
<p><br></p>
<h3 id="create-a-project">Create a project</h3>
-<p>Use the Newt tool to create a new project directory containing a skeletal Mynewt framework. Change into the newly created directory.</p>
+<p>Use the newt tool to create a new project directory containing a skeletal Mynewt framework. Change into the newly created directory.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt new myproj
Downloading project skeleton from apache/incubator-mynewt-blinky...
Installing skeleton in myproj...
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/os/tutorials/blinky/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/blinky/index.html b/develop/os/tutorials/blinky/index.html
index bfc9c0e..7565297 100644
--- a/develop/os/tutorials/blinky/index.html
+++ b/develop/os/tutorials/blinky/index.html
@@ -282,6 +282,14 @@
<li >
+ <a href="../blinky_stm32f4disc/">Blinky on STM32F4-Discovery</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../blinky_console/">Add Console and Shell to Blinky</a>
</li>
@@ -535,6 +543,7 @@
<li><a href="../olimex/">Blinky on an Olimex</a></li>
<li><a href="../nRF52/">Blinky on a nRF52</a></li>
<li><a href="../rbnano2/">Blinky on a RedBear Nano 2</a></li>
+<li><a href="../blinky_stm32f4disc/">Blinky on a STM32F4-Discovery</a></li>
</ul>
<p>We also have a tutorial that shows you how to add <a href="../blinky_console/">Console and Shell to the Blinky Application</a>.
<br></p>
@@ -544,7 +553,7 @@
<li>Have Internet connectivity to fetch remote Mynewt components.</li>
<li>Have a computer to build a Mynewt application and connect to the board over USB.</li>
<li>Have a Micro-USB cable to connect the board and the computer.</li>
-<li>Install the Newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
+<li>Install the newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section. </li>
<li>Create a project space (directory structure) and populate it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.
<br></li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/os/tutorials/blinky_console/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/blinky_console/index.html b/develop/os/tutorials/blinky_console/index.html
index 4761d6b..516ddb3 100644
--- a/develop/os/tutorials/blinky_console/index.html
+++ b/develop/os/tutorials/blinky_console/index.html
@@ -281,6 +281,14 @@
+ <li >
+ <a href="../blinky_stm32f4disc/">Blinky on STM32F4-Discovery</a>
+ </li>
+
+
+
+
+
<li class="active">
<a href="./">Add Console and Shell to Blinky</a>
</li>
@@ -697,9 +705,9 @@ prompt on
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../rbnano2/>
+ <a href=../blinky_stm32f4disc/>
<span class="fa fa-arrow-left"></span>
- Previous: Blinky on RedBear Nano 2
+ Previous: Blinky on STM32F4-Discovery
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/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 6e9b84a..a0e803b 100644
--- a/develop/os/tutorials/blinky_primo/index.html
+++ b/develop/os/tutorials/blinky_primo/index.html
@@ -282,6 +282,14 @@
<li >
+ <a href="../blinky_stm32f4disc/">Blinky on STM32F4-Discovery</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../blinky_console/">Add Console and Shell to Blinky</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/os/tutorials/blinky_stm32f4disc/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/blinky_stm32f4disc/index.html b/develop/os/tutorials/blinky_stm32f4disc/index.html
new file mode 100644
index 0000000..3cf584b
--- /dev/null
+++ b/develop/os/tutorials/blinky_stm32f4disc/index.html
@@ -0,0 +1,770 @@
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <meta charset="utf-8">
+ <meta http-equiv="X-UA-Compatible" content="IE=edge">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+
+ <!-- This is broken by doc revisioning.
+ <link rel="canonical" href="http://mynewt.apache.org/os/tutorials/blinky_stm32f4disc/"> -->
+ <link rel="shortcut icon" href="../../../img/favicon.ico">
+
+ <title>Blinky on STM32F4-Discovery - 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="Blinky on STM32F4-Discovery">
+
+
+ <div class="container">
+ <div class="row v2-main-banner">
+ <a class="logo-cell" href="/">
+ <img class="logo" src="/img/logo.png">
+ </a>
+ <div class="tagline-cell">
+ <h4 class="tagline">An OS to build, deploy and securely manage billions of devices</h4>
+ </div>
+ <div class="news-cell">
+ <div class="well">
+ <h4>Latest News:</h4> <a href="/download">Apache Mynewt 1.0.0</a> released (March 22, 2017)
+ </div>
+ </div>
+ </div>
+</div>
+
+
+
+
+
+
+
+
+<nav id="navbar" class="navbar navbar-inverse affix-top" data-spy="affix" data-offset-top="150" role="navigation">
+ <div class="container">
+ <!-- Collapsed navigation -->
+ <div class="navbar-header">
+ <!-- Expander button -->
+ <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
+ <span class="sr-only">Toggle navigation</span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ </button>
+
+ </div>
+
+ <!-- Expanded navigation -->
+ <div class="navbar-collapse collapse">
+ <!-- Main navigation -->
+ <ul class="nav navbar-nav navbar-right">
+ <li
+ class=""
+>
+ <a href="/"><i class="fa fa-home" style="font-size: larger;"></i></a>
+ </li>
+ <li
+ class="important"
+>
+ <a href="/quick-start/">Quick Start</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/about/">About</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/talks/">Talks</a>
+ </li>
+ <li
+ class="active"
+>
+ <a href="/latest/os/introduction">Documentation</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/download/">Download</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/community/">Community</a>
+ </li>
+ <li
+ class=""
+>
+ <a href="/events/">Events</a>
+ </li>
+ </ul>
+
+ <!-- Search, Navigation and Repo links -->
+ <ul class="nav navbar-nav navbar-right">
+
+ </ul>
+ </div>
+ </div>
+</nav>
+
+
+
+ <div class="container">
+
+ <div class="row">
+ <div class="col-md-3 v2-sidebar sidebar-container"><div id="docSidebar" class="hidden-print" role="complementary">
+ <div class="top">
+ <div role="search">
+ <form id="rtd-search-form" class="wy-form" action="../../../search.html" method="get">
+ <div class="form-group">
+ <input type="text" name="q" class="form-control" placeholder="Search documentation" />
+ </div>
+ </form>
+ </div>
+ </div>
+ <ul class="toc-nav">
+ <li class="doc-version">
+<select class="form-control" onchange="if (this.value) window.location.href=this.value">
+
+ <option
+ value="/develop/os/introduction"
+ selected="selected"
+ >
+ Version: develop (latest)
+ </option>
+
+ <option
+ value="/v0_9_0/os/introduction"
+
+ >
+ Version: 0.9.0
+ </option>
+
+</select>
+</li>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ <li ><a href="../../introduction/">Mynewt Documentation</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../../get_started/get_started/">Basic Setup</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../../get_started/vocabulary/">Concepts</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../tutorials/">Tutorials</a>
+
+
+ <ul>
+
+
+
+
+
+
+
+ <li ><a href="../blinky/">Project Blinky</a>
+
+
+ <ul>
+
+
+
+
+
+ <li >
+ <a href="../arduino_zero/">Blinky on Arduino Zero</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../blinky_primo/">Blinky on Arduino Primo</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../olimex/">Blinky on Olimex</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../nRF52/">Blinky on nRF52</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../rbnano2/">Blinky on RedBear Nano 2</a>
+ </li>
+
+
+
+
+
+ <li class="active">
+ <a href="./">Blinky on STM32F4-Discovery</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../blinky_console/">Add Console and Shell to Blinky</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../repo/add_repos/">Work with repositories</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../ibeacon/">BLE iBeacon</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../eddystone/">BLE Eddystone</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../add_shell/">Enable the OS Shell and Console</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../tasks_lesson/">Tasks and Priority Management</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../unit_test/">Write a Test Suite for a Package</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../event_queue/">Events and Event Queues</a>
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../bletiny_project/">BLE app to check stats via console</a>
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../blehci_project/">BLE HCI interface</a>
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../air_quality_sensor/
+">Air-quality Sensor project</a>
+
+
+ </li>
+
+
+
+
+
+ <li >
+ <a href="../nrf52_adc/">Add an Analog Sensor</a>
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../os_user_guide/">OS User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../../network/ble/ble_intro/
+">BLE User Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../newt/newt_intro/">Newt Tool Guide</a>
+
+
+ </li>
+
+
+
+
+
+
+
+ <li ><a href="../../../newtmgr/overview/">Newt Manager Guide</a>
+
+
+ </li>
+
+
+
+ </ul>
+
+ </li>
+
+
+
+
+
+
+
+ <li><a href="
+ ../../../faq/go_env/
+">Appendix</a>
+
+
+ </li>
+
+
+
+ </ul>
+</div></div>
+
+ <div class="col-md-9" role="main">
+ <div class="doc-header">
+ <div role="navigation" aria-label="breadcrumbs navigation">
+ <ul class="wy-breadcrumbs pull-right">
+ <li><a href="/develop/os/introduction">Docs</a></li>
+
+
+
+ <li>» <a href="../tutorials/">Tutorials</a></li>
+
+
+
+ <li>» <a href="../blinky/">Project Blinky</a></li>
+
+
+
+ <li>» Blinky on STM32F4-Discovery</li>
+
+
+
+ </ul>
+</div>
+ </div>
+
+ <h2 id="blinky-your-hello-world-on-stm32f4-discovery">Blinky, your "Hello World!", on STM32F4-Discovery</h2>
+<p>This tutorial shows you how to create, build, and run the Blinky application on the STM32F4-Discovery board.
+<br></p>
+<p><br></p>
+<h3 id="prerequisites">Prerequisites</h3>
+<ul>
+<li>Meet the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
+<li>Have a STM32F4-Discovery board.</li>
+<li>Have a USB type A to Mini-B cable. </li>
+<li>Install a patched version of OpenOCD 0.10.0 described in <a href="../os/get_started/cross_tools/">Install OpenOCD</a>. </li>
+</ul>
+<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>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ mkdir ~/dev
+ $ cd ~/dev
+ $ newt new myproj
+ Downloading project skeleton from apache/incubator-mynewt-blinky...
+ Installing skeleton in myproj...
+ Project myproj successfully created.
+ $ cd myproj
+ $ newt install
+ apache-mynewt-core
+ $
+</pre></div>
+
+
+<p><br></p>
+<h3 id="create-the-targets"><a name="create_targets"></a>Create the Targets</h3>
+<p>Create two targets for the STM32F4-Discovery 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, to create a bootloader target. We name the target <code>stm32f4disc_boot</code>:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create stm32f4disc_boot
+$ newt target set stm32f4disc_boot app=@apache-mynewt-core/apps/boot
+$ newt target set stm32f4disc_boot bsp=@apache-mynewt-core/hw/bsp/stm32f4discovery
+$ newt target set stm32f4disc_boot build_profile=optimized
+</pre></div>
+
+
+<p><br>
+Run the following <code>newt target</code> commands to create a target for the Blinky application. We name the target <code>stm32f4disc_blinky</code>:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create stm32f4disc_blinky
+$ newt target set stm32f4disc_blinky app=apps/blinky
+$ newt target set stm32f4disc_blinky bsp=@apache-mynewt-core/hw/bsp/stm32f4discovery
+$ newt target set stm32f4disc_blinky build_profile=debug
+</pre></div>
+
+
+<p><br>
+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
+ bsp=@apache-mynewt-core/hw/bsp/native
+ build_profile=debug
+targets/stm32f4disc_blinky
+ app=apps/blinky
+ bsp=@apache-mynewt-core/hw/bsp/stm32f4discovery
+ build_profile=debug
+targets/stm32f4disc_boot
+ app=@apache-mynewt-core/apps/boot
+ bsp=@apache-mynewt-core/hw/bsp/stm32f4discovery
+ build_profile=optimized
+</pre></div>
+
+
+<p><br></p>
+<h3 id="build-the-target-executables">Build the Target Executables</h3>
+<p>Run the <code>newt build stm32f4disc_boot</code> command to build the bootloader:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt build stm32f4disc_boot
+Building target targets/stm32f4disc_boot
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_ec256.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/bootutil_misc.c
+Compiling repos/apache-mynewt-core/apps/boot/src/boot.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_rsa.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/image_validate.c
+Compiling repos/apache-mynewt-core/boot/bootutil/src/loader.c
+ ...
+
+Archiving sys_flash_map.a
+Archiving sys_mfg.a
+Archiving sys_sysinit.a
+Archiving util_mem.a
+Linking ~/dev/myproj/bin/targets/stm32f4disc_boot/app/apps/boot/boot.elf
+Target successfully built: targets/stm32f4disc_boot
+</pre></div>
+
+
+<p><br>
+Run the <code>newt build stm32f4disc_blinky</code> command to build the Blinky application:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt build stm32f4disc_blinky
+Building target targets/stm32f4disc_blinky
+Compiling apps/blinky/src/main.c
+Compiling repos/apache-mynewt-core/hw/bsp/stm32f4discovery/src/sbrk.c
+Compiling repos/apache-mynewt-core/hw/bsp/stm32f4discovery/src/system_stm32f4xx.c
+Compiling repos/apache-mynewt-core/hw/bsp/stm32f4discovery/src/hal_bsp.c
+Assembling repos/apache-mynewt-core/hw/bsp/stm32f4discovery/src/arch/cortex_m4/startup_STM32F40x.s
+Compiling repos/apache-mynewt-core/hw/cmsis-core/src/cmsis_nvic.c
+Compiling repos/apache-mynewt-core/hw/drivers/uart/src/uart.c
+Compiling repos/apache-mynewt-core/hw/drivers/uart/uart_hal/src/uart_hal.c
+Compiling repos/apache-mynewt-core/hw/hal/src/hal_common.c
+Compiling repos/apache-mynewt-core/hw/hal/src/hal_flash.c
+
+ ...
+
+Archiving sys_sysinit.a
+Archiving util_mem.a
+Linking ~/dev/myproj/bin/targets/stm32f4disc_blinky/app/apps/blinky/blinky.elf
+Target successfully built: targets/stm32f4disc_blinky
+</pre></div>
+
+
+<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 stm32f4disc_blinky 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 stm32f4disc_blinky 1.0.0
+App image succesfully generated: ~/dev/myproj/bin/targets/stm32f4disc_blinky/app/apps/blinky/blinky.img
+</pre></div>
+
+
+<p><br></p>
+<h3 id="connect-to-the-board">Connect to the Board</h3>
+<p>Connect a USB type A to Mini-B cable from your computer to the port the board indicated on the diagram: </p>
+<p><br>
+<br>
+<img alt="stm32f4-discovery" src="../pics/stm32f4_disc.jpg" title="Connecting computer to stm32f4disc" /></p>
+<p><br></p>
+<p>You should see the small PWR red LED light up.</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 stm32f4disc_boot</code> command to load the bootloader onto the board: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt load stm32f4disc_boot
+Loading bootloader
+</pre></div>
+
+
+<p><br>
+Run the <code>newt load stm32f4disc_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 stm32f4disc_blinky
+Loading app image into slot 1
+</pre></div>
+
+
+<p>You should see the small green LD4 LED 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, start a debug session, and enter <code>mon stm32f2x mass_erase 0</code> at the gdb prompt:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt debug stm32f4disc_blinky
+[~/dev/myproj/repos/apache-mynewt-core/hw/bsp/stm32f4discovery/stm32f4discovery_debug.sh ~/dev/myproj/repos/apache-mynewt-core/hw/bsp/stm32f4discovery ~/dev/myproj/bin/targets/stm32f4disc_blinky/app/apps/blinky/blinky]
+Open On-Chip Debugger 0.10.0
+Licensed under GNU GPL v2
+For bug reports, read
+ http://openocd.org/doc/doxygen/bugs.html
+Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
+adapter speed: 2000 kHz
+adapter_nsrst_delay: 100
+none separate
+Info : Unable to match requested speed 2000 kHz, using 1800 kHz
+Info : Unable to match requested speed 2000 kHz, using 1800 kHz
+Info : clock speed 1800 kHz
+Info : STLINK v2 JTAG v25 API v2 SWIM v14 VID 0x0483 PID 0x374B
+Info : using stlink api v2
+Info : Target voltage: 2.881129
+Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints
+target halted due to debug-request, current mode: Thread
+
+ ...
+
+Reading symbols from ~/dev/myproj/bin/targets/stm32f4disc_blinky/app/apps/blinky/blinky.elf...done.
+target halted due to debug-request, current mode: Thread
+xPSR: 0x41000000 pc: 0x08021e90 psp: 0x20002290
+Info : accepting 'gdb' connection on tcp/3333
+Info : device id = 0x10076413
+Info : flash size = 1024kbytes
+0x08021e90 in __WFI () at repos/apache-mynewt-core/hw/cmsis-core/src/ext/core_cmInstr.h:342
+342 __ASM volatile ("wfi");
+(gdb) mon stm32f2x mass_erase 0
+stm32x mass erase complete
+stm32x mass erase complete
+(gdb)
+</pre></div>
+
+ <div class="row">
+
+
+
+
+<ul class="nav nav-pills" style="margin-bottom: 10px">
+ <li>
+
+ <a href=../rbnano2/>
+ <span class="fa fa-arrow-left"></span>
+ Previous: Blinky on RedBear Nano 2
+ </a>
+
+ </li>
+ <li class="pull-right">
+
+ <a href=../blinky_console/>
+ Next: Add Console and Shell to Blinky
+ <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/ea2670d6/develop/os/tutorials/nRF52/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/nRF52/index.html b/develop/os/tutorials/nRF52/index.html
index 36fbb3c..2e95c97 100644
--- a/develop/os/tutorials/nRF52/index.html
+++ b/develop/os/tutorials/nRF52/index.html
@@ -282,6 +282,14 @@
<li >
+ <a href="../blinky_stm32f4disc/">Blinky on STM32F4-Discovery</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../blinky_console/">Add Console and Shell to Blinky</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/os/tutorials/nrf52_adc/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/nrf52_adc/index.html b/develop/os/tutorials/nrf52_adc/index.html
index 933f8f4..dd6cec4 100644
--- a/develop/os/tutorials/nrf52_adc/index.html
+++ b/develop/os/tutorials/nrf52_adc/index.html
@@ -532,7 +532,7 @@ repository.apache-mynewt-core:
<span style="background-color: #ffffcc">repository.mynewt_nordic:
</span><span style="background-color: #ffffcc"> type: github
</span><span style="background-color: #ffffcc"> vers: 1-latest
-</span><span style="background-color: #ffffcc"> user: runtimeinc
+</span><span style="background-color: #ffffcc"> user: runtimeco
</span><span style="background-color: #ffffcc"> repo: mynewt_nordic
</span></pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/os/tutorials/olimex/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/olimex/index.html b/develop/os/tutorials/olimex/index.html
index 0780b13..82ba948 100644
--- a/develop/os/tutorials/olimex/index.html
+++ b/develop/os/tutorials/olimex/index.html
@@ -282,6 +282,14 @@
<li >
+ <a href="../blinky_stm32f4disc/">Blinky on STM32F4-Discovery</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../blinky_console/">Add Console and Shell to Blinky</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/os/tutorials/pics/stm32f4_disc.jpg
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/pics/stm32f4_disc.jpg b/develop/os/tutorials/pics/stm32f4_disc.jpg
new file mode 100755
index 0000000..cbed05f
Binary files /dev/null and b/develop/os/tutorials/pics/stm32f4_disc.jpg differ
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/os/tutorials/rbnano2/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/rbnano2/index.html b/develop/os/tutorials/rbnano2/index.html
index af1959e..bbe63a4 100644
--- a/develop/os/tutorials/rbnano2/index.html
+++ b/develop/os/tutorials/rbnano2/index.html
@@ -282,6 +282,14 @@
<li >
+ <a href="../blinky_stm32f4disc/">Blinky on STM32F4-Discovery</a>
+ </li>
+
+
+
+
+
+ <li >
<a href="../blinky_console/">Add Console and Shell to Blinky</a>
</li>
@@ -699,8 +707,8 @@ Loading app image into slot 1
</li>
<li class="pull-right">
- <a href=../blinky_console/>
- Next: Add Console and Shell to Blinky
+ <a href=../blinky_stm32f4disc/>
+ Next: Blinky on STM32F4-Discovery
<span class="fa fa-arrow-right"></span>
</a>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/os/tutorials/repo/add_repos/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/repo/add_repos/index.html b/develop/os/tutorials/repo/add_repos/index.html
index 1d6b1bc..fa259b1 100644
--- a/develop/os/tutorials/repo/add_repos/index.html
+++ b/develop/os/tutorials/repo/add_repos/index.html
@@ -628,7 +628,7 @@ repository.apache-Mynewt-core:
repository.Mynewt_arduino_zero:
type: github
vers: 1-latest
- user: runtimeinc
+ user: runtimeco
repo: Mynewt_arduino_zero
</pre></div>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/os/tutorials/wi-fi_on_arduino/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/wi-fi_on_arduino/index.html b/develop/os/tutorials/wi-fi_on_arduino/index.html
index 25f25a9..6e66832 100644
--- a/develop/os/tutorials/wi-fi_on_arduino/index.html
+++ b/develop/os/tutorials/wi-fi_on_arduino/index.html
@@ -541,7 +541,7 @@ repository.apache-mynewt-core:
<span style="background-color: #ffffcc">repository.mynewt_arduino_zero:
</span><span style="background-color: #ffffcc"> type: github
</span><span style="background-color: #ffffcc"> vers: 1-latest
-</span><span style="background-color: #ffffcc"> user: runtimeinc
+</span><span style="background-color: #ffffcc"> user: runtimeco
</span><span style="background-color: #ffffcc"> repo: mynewt_arduino_zero
</span>$
</pre></div>
[7/7] incubator-mynewt-site git commit: changed runtimeinc to
runtimeco in docs, updated install instructions for linux ,
blinky for stm32F4-discovery
Posted by ad...@apache.org.
changed runtimeinc to runtimeco in docs, updated install instructions for linux , blinky for stm32F4-discovery
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/ea2670d6
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/ea2670d6
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/ea2670d6
Branch: refs/heads/asf-site
Commit: ea2670d630c65bb26c755ae5a46ffa3d9e2c35f7
Parents: 26592f0
Author: aditihilbert <ad...@runtime.io>
Authored: Fri May 5 15:30:53 2017 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Fri May 5 15:30:53 2017 -0700
----------------------------------------------------------------------
develop/faq/go_env/index.html | 2 +-
develop/mkdocs/search_index.json | 214 ++++--
develop/newt/install/newt_linux/index.html | 54 +-
develop/newt/install/newt_mac/index.html | 16 +-
develop/newtmgr/install_linux/index.html | 43 +-
develop/os/get_started/cross_tools/index.html | 16 +-
develop/os/get_started/docker/index.html | 2 +-
develop/os/get_started/get_started/index.html | 6 +-
.../get_started/native_install_intro/index.html | 476 ++++++++++++
develop/os/get_started/native_tools/index.html | 28 +-
.../os/get_started/project_create/index.html | 15 +-
develop/os/get_started/serial_access/index.html | 2 +-
develop/os/modules/drivers/driver/index.html | 2 +-
develop/os/tutorials/add_newtmgr/index.html | 6 +-
develop/os/tutorials/add_shell/index.html | 15 +-
develop/os/tutorials/arduino_zero/index.html | 12 +-
develop/os/tutorials/blehci_project/index.html | 18 +-
develop/os/tutorials/bletiny_project/index.html | 16 +-
develop/os/tutorials/blinky/index.html | 11 +-
develop/os/tutorials/blinky_console/index.html | 12 +-
develop/os/tutorials/blinky_primo/index.html | 8 +
.../os/tutorials/blinky_stm32f4disc/index.html | 770 +++++++++++++++++++
develop/os/tutorials/nRF52/index.html | 8 +
develop/os/tutorials/nrf52_adc/index.html | 2 +-
develop/os/tutorials/olimex/index.html | 8 +
develop/os/tutorials/pics/stm32f4_disc.jpg | Bin 0 -> 40575 bytes
develop/os/tutorials/rbnano2/index.html | 12 +-
develop/os/tutorials/repo/add_repos/index.html | 2 +-
.../os/tutorials/wi-fi_on_arduino/index.html | 2 +-
develop/sitemap.xml | 26 +-
latest/faq/go_env/index.html | 2 +-
latest/mkdocs/search_index.json | 214 ++++--
latest/newt/install/newt_linux/index.html | 54 +-
latest/newt/install/newt_mac/index.html | 16 +-
latest/newtmgr/install_linux/index.html | 43 +-
latest/os/get_started/cross_tools/index.html | 16 +-
latest/os/get_started/docker/index.html | 2 +-
latest/os/get_started/get_started/index.html | 6 +-
.../get_started/native_install_intro/index.html | 476 ++++++++++++
latest/os/get_started/native_tools/index.html | 28 +-
latest/os/get_started/project_create/index.html | 15 +-
latest/os/get_started/serial_access/index.html | 2 +-
latest/os/modules/drivers/driver/index.html | 2 +-
latest/os/tutorials/add_newtmgr/index.html | 6 +-
latest/os/tutorials/add_shell/index.html | 15 +-
latest/os/tutorials/arduino_zero/index.html | 12 +-
latest/os/tutorials/blehci_project/index.html | 18 +-
latest/os/tutorials/bletiny_project/index.html | 16 +-
latest/os/tutorials/blinky/index.html | 11 +-
latest/os/tutorials/blinky_console/index.html | 12 +-
latest/os/tutorials/blinky_primo/index.html | 8 +
.../os/tutorials/blinky_stm32f4disc/index.html | 770 +++++++++++++++++++
latest/os/tutorials/nRF52/index.html | 8 +
latest/os/tutorials/nrf52_adc/index.html | 2 +-
latest/os/tutorials/olimex/index.html | 8 +
latest/os/tutorials/pics/stm32f4_disc.jpg | Bin 0 -> 40575 bytes
latest/os/tutorials/rbnano2/index.html | 12 +-
latest/os/tutorials/repo/add_repos/index.html | 2 +-
latest/os/tutorials/wi-fi_on_arduino/index.html | 2 +-
latest/sitemap.xml | 26 +-
os/tutorials/pics/stm32f4_disc.jpg | Bin 0 -> 40575 bytes
sitemap.xml | 26 +-
v0_9_0/os/tutorials/pics/stm32f4_disc.jpg | Bin 0 -> 40575 bytes
v0_9_0/sitemap.xml | 26 +-
64 files changed, 3206 insertions(+), 454 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ea2670d6/develop/faq/go_env/index.html
----------------------------------------------------------------------
diff --git a/develop/faq/go_env/index.html b/develop/faq/go_env/index.html
index f897a6f..0b74b23 100644
--- a/develop/faq/go_env/index.html
+++ b/develop/faq/go_env/index.html
@@ -409,7 +409,7 @@ nothing to commit, working directory clean
Check that the newtmgr binary is installed and you are using the one from <strong>$GOPATH/bin</strong>:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ls $GOPATH/bin/newtmgr
~/dev/go/bin/newtmgr
-$which newt
+$which newtmgr
~/dev/go/bin/newtmgr
</pre></div>