You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by ad...@apache.org on 2017/04/26 00:31:38 UTC
[5/7] incubator-mynewt-site git commit: Updates to installation on
Linux and Mac, removal of references to develop branch on website
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/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 df1b621..cbdbbd4 100644
--- a/develop/newt/install/newt_linux/index.html
+++ b/develop/newt/install/newt_linux/index.html
@@ -391,181 +391,218 @@
</div>
</div>
- <h2 id="install-newt-tool-on-linux">Install newt tool on Linux</h2>
+ <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>
+<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><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>
+<li>Contribute to the newt tool. </li>
+</ul>
<p><br></p>
-<h3 id="getting-your-linux-box-ready">Getting your Linux box Ready</h3>
-<p>If you want to build the <em>newt</em> tool from its source code, follow the following steps:</p>
-<h4 id="1-install-git-libcurl">1. Install git, libcurl</h4>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ sudo apt-get install git
- $ sudo apt-get install libcurl4-gnutls-dev
+<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>
+<ol>
+<li>Add 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>
+<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><strong>NOTE:</strong> On 64-bit host, you may also need to install gcc-multilib, if you encounter compilation errors related to 'sys/cdefs.h'</p>
<p><br></p>
-<h4 id="2-install-go-the-programming-language">2. Install Go, the programming language</h4>
-<ul>
-<li>
-<p>Go language environment dictates a directory structure. Known in Go parlance as a workspace, it must contain three sibling directories with the directory names src, pkg and bin, as explained below. </p>
-<ul>
-<li>
-<p>src contains Go source files organized into packages (one package per directory),</p>
-</li>
-<li>
-<p>pkg contains package objects, and</p>
-</li>
-<li>
-<p>bin contains executable commands.</p>
-</li>
-</ul>
-<p>The GOPATH environment variable specifies the location of your workspace. To setup this workspace environment, create a 'dev' directory and then a 'go' directory under it. Set the GOPATH environment variable to this directory where you will soon clone the <em>newt</em> tool repository.</p>
-</li>
-</ul>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ cd $HOME
- $ mkdir -p dev/go
- $ cd dev/go
- $ export GOPATH=`pwd`
+<p>Download the public key for the runtimeco apt repo (<strong>Note:</strong> There is <code>-</code> after the add):</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>(Note that you need to add export statements to ~/.bash_profile to export variables permanently. Don't forget to source the file for the change to go into effect.)</p>
<p><br></p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ vi ~/.bash_profile
- $ source ~/.bash_profile
+<p>Add the repository for the binary and source packages to the apt source list:</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
+</pre></div>
+
+
+<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
+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>
-<ul>
-<li>
-<p>Next, install Go. When installed, Go offers you as a developer a language environment (to compile Go code), construct Go packages (to assemble Go packages) and import Go code (from github). In the next step, you will use the Go commands to import <em>newt</em> repo into your local Go environment.</p>
-<p><strong>Note</strong>: The Newt tool requires Go version 1.7 or later. Currently, the latest Go version that Ubuntu installs is 1.6. You can run <code>apt-get install golang-1.7-go</code> to install version 1.7. You can also download version 1.7 from <a href="https://golang.org/dl/">https://golang.org/dl/</a>. </p>
-</li>
-</ul>
+<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>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get update
+$sudo apt-get install newt
+Reading package lists... Done
+Building dependency tree
+Reading state information... Done
+
+ ...
+
+Preparing to unpack .../newt_1.0.0-1_amd64.deb ...
+Unpacking newt (1.0.0-1) ...
+Setting up newt (1.0.0-1) ...
+</pre></div>
+
+
+<p><br>
+See <a href="#check">Checking the Installed Version of Newt</a> to verify that you are using the installed version of newt.</p>
+<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><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>
+<p><br></p>
+<p>Install Go version 1.7:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get install golang-1.7-go
Reading package lists... Done
...
Unpacking golang-1.7-go (1.7.1-2ubuntu1) ...
Setting up golang-1.7-go (1.7.1-2ubuntu1) ...
$
-$sudo ln -s /usr/lib/go-1.7/bin/go /usr/bin/go
+$sudo ln -sf ../lib/go-1.7/bin/go /usr/bin/go
$go version
go version go1.7.1 linux/amd64
</pre></div>
-<p><br> </p>
-<h4 id="3-create-local-repository">3. Create local repository</h4>
-<ul>
-<li>Use Go commands to copy the directory (currently the ASF incubator directory). Be patient as it may take a minute or two. Check the directories installed.</li>
-</ul>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ go get mynewt.apache.org/newt/...
-</pre></div>
-
-
+<p>You can also download version 1.7 from <a href="https://golang.org/dl/">https://golang.org/dl/</a>. </p>
<p><br></p>
-<ul>
-<li>Check that newt.go is in place.</li>
-</ul>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ ls $GOPATH/src/mynewt.apache.org/newt
- DISCLAIMER NOTICE newt newtvm viper
- LICENSE README.md newtmgr util yaml
+<h4 id="installing-from-the-source-package">Installing from the Source Package</h4>
+<p>Create a directory and change into the directory, download the source package, and build a binary package from the source package:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">mkdir newt_source
+$cd newt_source
+$sudo apt-get --build source newt
+[sudo] password for <user>:
+Reading package lists... Done
+Need to get 1,866 kB of source archives.
+Get:1 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (dsc) [795 B]
+Get:2 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (tar) [1,864 kB]
+Get:3 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newt 1.0.0-1 (diff) [2,000 B]
+Fetched 1,866 kB in 1s (1,222 kB/s)
+dpkg-source: warning: extracting unsigned source package (newt_1.0.0-1.dsc)
+dpkg-source: info: extracting newt in newt-1.0.0
+dpkg-source: info: unpacking newt_1.0.0.orig.tar.gz
+dpkg-source: info: unpacking newt_1.0.0-1.debian.tar.xz
+
+ ...
+
+dpkg-deb: building package 'newt' in '../newt_1.0.0-1_amd64.deb'.
+ dpkg-genchanges --build=any,all >../newt_1.0.0-1_amd64.changes
+dpkg-genchanges: info: binary-only upload (no source code included)
+ dpkg-source --after-build newt-1.0.0
+dpkg-buildpackage: info: binary-only upload (no source included)
+W: 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)
</pre></div>
-<p><br></p>
-<h4 id="4-build-the-newt-tool">4. Build the Newt tool</h4>
-<ul>
-<li>Use Go to run the newt.go program to build the <em>newt</em> tool. The command <code>go install</code> compiles and writes the resulting executable to an output file named <code>newt</code>, which is then installed, along with its dependencies, in $GOPATH/bin. If you get errors it is likely because of path resolution issues. Try <code>go build</code> followed by <code>go install</code> in that case.</li>
-</ul>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ cd $GOPATH/src/mynewt.apache.org/newt/newt
- $ go install
- $ ls "$GOPATH"/bin/
- newt newtmgr newtvm
+<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>
+<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.)
+Preparing to unpack newt_1.0.0-1_amd64.deb ...
+Unpacking newt (1.0.0-1) ...
+Setting up newt (1.0.0-1) ...
</pre></div>
<p><br></p>
-<ul>
-<li>At this point, you can try using <em>newt</em>. For example, check for the version number by typing 'newt version'. See all the possible commands available to a user of newt by typing 'newt -h'.</li>
-</ul>
-<p>(Note: If you are going to be modifying the <em>newt</em> often and going to be compile the program every time you call it, you will want to store the command in a variable in your .bash_profile. So type in <code>export newt="go run $GOPATH/mynewt.apache.org/newt/newt/newt.go"</code> in your .bash_profile and execute it by calling <code>$newt</code> at the prompt instead of <code>newt</code>. Essentially, <code>$newt</code> calls <code>go run</code> which runs the compiled binary directly without producing an executable. Don't forget to reload the updated bash profile by typing <code>source ~/.bash_profile</code> at the prompt! )</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ newt version
- Newt version: 1.0
- $ newt -h
- Newt allows you to create your own embedded application based on the Mynewt
- operating system. Newt provides both build and package management in a single
- tool, which allows you to compose an embedded application, and set of
- projects, and then build the necessary artifacts from those projects. For more
- information on the Mynewt operating system, please visit
- https://mynewt.apache.org/.
-
- Please use the newt help command, and specify the name of the command you want
- help for, for help on how to use a specific command
-
- Usage:
- newt [flags]
- newt [command]
-
- Examples:
- newt
- newt help [<command-name>]
- For help on <command-name>. If not specified, print this message.
-
- Available Commands:
- build Build one or more targets
- clean Delete build artifacts for one or more targets
- create-image Add image header to target binary
- debug Open debugger session to target
- info Show project info
- install Install project dependencies
- load Load built target to board
- mfg Manufacturing flash image commands
- new Create a new project
- pkg Create and manage packages in the current workspace
- run build/create-image/download/debug <target>
- size Size of target components
- sync Synchronize project dependencies
- target Commands to create, delete, configure, and query targets
- test Executes unit tests for one or more packages
- upgrade Upgrade project dependencies
- vals Display valid values for the specified element type(s)
- version Display the Newt version number
-
- Flags:
- -h, --help Help for newt commands
- -j, --jobs int Number of concurrent build jobs (default 8)
- -l, --loglevel string Log level (default "WARN")
- -o, --outfile string Filename to tee output to
- -q, --quiet Be quiet; only display error output
- -s, --silent Be silent; don't output anything
- -v, --verbose Enable verbose output when executing commands
-
- Use "newt [command] --help" for more information about a comma
+<h3 id="checking-the-installed-version-of-newt"><a name="check"></a> Checking the Installed Version of Newt</h3>
+<p>After you have installed newt from either a Debian binary or source package, check that you are using the installed version of newt from <strong>/usr/bin</strong>. </p>
+<p>Check the modification time of the binary and the newt tool that you are using:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ls -l /usr/bin/newt
+-rwxr-xr-x 1 root root 6919280 Apr 22 10:09 /usr/bin/newt
+$which newt
+/usr/bin/newt
+$newt version
+Apache Newt (incubating) version: 1.0.0
</pre></div>
-<p><br></p>
-<h4 id="5-updating-the-newt-tool">5. Updating the Newt tool</h4>
-<ul>
-<li>You will update the newt tool in the same place as you initially installed the newt tool.</li>
-<li>Start by updating the git repository of the newt tool (you can change to a different branch using git checkout [branch] if you need to)</li>
-<li>Then update each of the tools newt, newtmgr and newtvm as needed</li>
-</ul>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"> $ cd $GOPATH/src/mynewt.apache.org/newt
- $ git pull
- $ cd newt
- $ go install
- $ cd ../newtmgr
- $ go install
- $ cd ../newtvm
- $ go install
- $ ls "$GOPATH"/bin/
- newt newtmgr newtvm
+<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><br>
+Get information about newt:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newt
+Newt allows you to create your own embedded application based on the Mynewt
+operating system. Newt provides both build and package management in a single
+tool, which allows you to compose an embedded application, and set of
+projects, and then build the necessary artifacts from those projects. For more
+information on the Mynewt operating system, please visit
+https://mynewt.apache.org/.
+
+Please use the newt help command, and specify the name of the command you want
+help for, for help on how to use a specific command
+
+Usage:
+ newt [flags]
+ newt [command]
+
+Examples:
+ newt
+ newt help [<command-name>]
+ For help on <command-name>. If not specified, print this message.
+
+Available Commands:
+ build Build one or more targets
+ clean Delete build artifacts for one or more targets
+ create-image Add image header to target binary
+ debug Open debugger session to target
+ info Show project info
+ install Install project dependencies
+ load Load built target to board
+ mfg Manufacturing flash image commands
+ new Create a new project
+ pkg Create and manage packages in the current workspace
+ run build/create-image/download/debug <target>
+ size Size of target components
+ sync Synchronize project dependencies
+ target Commands to create, delete, configure, and query targets
+ test Executes unit tests for one or more packages
+ upgrade Upgrade project dependencies
+ vals Display valid values for the specified element type(s)
+ version Display the Newt version number
+
+Flags:
+ -h, --help Help for newt commands
+ -j, --jobs int Number of concurrent build jobs (default 8)
+ -l, --loglevel string Log level (default "WARN")
+ -o, --outfile string Filename to tee output to
+ -q, --quiet Be quiet; only display error output
+ -s, --silent Be silent; don't output anything
+ -v, --verbose Enable verbose output when executing commands
+
+Use "newt [command] --help" for more information about a command.
</pre></div>
-<p>That should have updated your newt, newtmgr and newtvm to the latest versions based on the git repository you used.</p>
<p><br></p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/newtmgr/install_linux/index.html
----------------------------------------------------------------------
diff --git a/develop/newtmgr/install_linux/index.html b/develop/newtmgr/install_linux/index.html
index c5bb466..c191e51 100644
--- a/develop/newtmgr/install_linux/index.html
+++ b/develop/newtmgr/install_linux/index.html
@@ -372,59 +372,197 @@
</div>
</div>
- <h1 id="installing-newtmgr-on-linux">Installing Newtmgr on Linux</h1>
-<p>This page shows you how to install newtmgr from source code on Linux.</p>
-<h3 id="install-go-golang">Install Go (golang)</h3>
-<p>Install Go if it is not installed. The Newtmgr tool version 1.0.0 requires Go version 1.7 or later. Currently, the latest Go version that Ubuntu installs is
-1.6. You can run <code>apt-get install golang-1.7-go</code> to install version 1.7. You can also download version 1.7 from <a href="https://golang.org/dl/">https:/
-/golang.org/dl/</a>.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"><span style="background-color: #ffffcc">$sudo apt-get install golang-1.7-go
-</span>Reading package lists... Done
+ <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>
+<ol>
+<li>
+<p>Set up your computer to retrieve Debian packages from the runtimeco debian package repository. </p>
+<p><strong>Note:</strong> 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>
+</li>
+<li>
+<p>Install the latest stable release version of newtmgr from a Debian binary package. </p>
+</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><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>
+<li>Contribute to the newtmgr tool. </li>
+</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>
+<ol>
+<li>Add 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>
+<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>
+<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>
+<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
+</pre></div>
+
+
+<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
+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>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get update
+$sudo apt-get install newtmgr
+Reading package lists... Done
+Building dependency tree
+Reading state information... Done
+The following NEW packages will be installed:
+ newtmgr
+0 upgraded, 1 newly installed, 0 to remove and 204 not upgraded.
+Need to get 0 B/2,312 kB of archives.
+After this operation, 11.5 MB of additional disk space will be used.
+Selecting previously unselected package newtmgr.
+(Reading database ... 211647 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>
+
+
+<p><br>
+See <a href="#check">Checking the Installed Version of Newtmgr</a> to verify that you are using the installed version of newtmgr.</p>
+<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><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>
+<p><br></p>
+<p>Install Go version 1.7:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get install golang-1.7-go
+Reading package lists... Done
...
Unpacking golang-1.7-go (1.7.1-2ubuntu1) ...
Setting up golang-1.7-go (1.7.1-2ubuntu1) ...
$
-<span style="background-color: #ffffcc">$sudo ln -sf ../lib/go-1.7/bin/go /usr/bin/go
-</span>$go version
+$sudo ln -sf ../lib/go-1.7/bin/go /usr/bin/go
+$go version
go version go1.7.1 linux/amd64
</pre></div>
+<p>You can also download version 1.7 from <a href="https://golang.org/dl/">https://golang.org/dl/</a>. </p>
<p><br></p>
-<p>To use go, you must set a <code>$GOPATH</code> variable in your environment. This tells
-go where to put all the packages it downloads, builds and runs.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ mkdir $HOME/dev
-$ export GOPATH=$HOME/dev/Go
+<h4 id="installing-from-the-source-package">Installing from the Source Package</h4>
+<p>Create a directory and change into the directory, download the source package, and build a binary package from the source package:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">mkdir newtmgr_source
+$cd newtmgr_source
+$sudo apt-get --build source newtmgr
+[sudo] password for <user>:
+
+sudo apt-get --build source newtmgr
+Reading package lists... Done
+Need to get 1,867 kB of source archives.
+Get:1 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newtmgr 1.0.0-1 (dsc) [822 B]
+Get:2 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newtmgr 1.0.0-1 (tar) [1,864 kB]
+Get:3 https://raw.githubusercontent.com/runtimeco/debian-mynewt/master latest/main newtmgr 1.0.0-1 (diff) [2,372 B]
+Fetched 1,867 kB in 1s (1,767 kB/s)
+
+ ...
+
+dpkg-deb: building package 'newtmgr' in '../newtmgr_1.0.0-1_amd64.deb'.
+ dpkg-genchanges --build=any,all >../newtmgr_1.0.0-1_amd64.changes
+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)
</pre></div>
-<p><br></p>
-<p>Its best to add this to your <code>.profile</code> so its set automatically for your
-environment. </p>
-<p><br></p>
-<h3 id="download-the-newtmgr-source">Download the newtmgr source</h3>
-<p>You will first download the source code for newt.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">go get mynewt.apache.org/newt/...
+<p><br>
+Install the newtmgr binary package that is created from the source package:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo dpkg -i newtmgr_1.0.0-1_amd64.deb
</pre></div>
<p><br></p>
-<h3 id="building-newtmgr">Building newtmgr</h3>
-<p>Change into the directory where the newmgr tool was downloaded and
-install the newtmgr tool</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$cd $GOPATH/src/mynewt.apache.org/newt/newtmgr
-$go install
-$ls $GOPATH/bin
-... newtmgr ...
+<h3 id="checking-the-installed-version-of-newtmgr"><a name="check"></a> Checking the Installed Version of Newtmgr</h3>
+<p>After you have installed newtmgr from either a Debian binary or source package, check that you are using the installed version of newtmgr from <strong>/usr/bin</strong>. </p>
+<p>Check the modification time of the binary and the newtmgr tool that you are using:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ls -l /usr/bin/newtmgr
+-rwxr-xr-x 1 root root 11473328 Apr 25 10:10 /usr/bin/newtmgr
+$which newtmgr
+/usr/bin/newtmgr
</pre></div>
-<p><br></p>
-<p><strong>Note:</strong> If the <code>go install</code> command results in errors indicating some package
-cannot be found, do a <code>go get</code> to download all the third-party files needed
-from github.com and then run <code>go install</code> again. </p>
-<h3 id="add-to-your-path">Add to your Path</h3>
-<p>Add your <code>$GOPATH/bin</code> directory to 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" in your $PATH and export your $PATH.</p>
+<p><br>
+Get information about newtmgr:</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$newtmgr
+Newtmgr helps you manage remote devices running the Mynewt OS
+
+Usage:
+ newtmgr [flags]
+ newtmgr [command]
+
+Available Commands:
+ config Read or write a config value on a device
+ conn Manage newtmgr connection profiles
+ crash Send a crash command to a device
+ datetime Manage datetime on a device
+ echo Send data to a device and display the echoed back data
+ fs Access files on a device
+ image Manage images on a device
+ log Manage logs on a device
+ mpstats Read memory pool statistics from a device
+ reset Send reset request to a device
+ run Run test procedures on a device
+ stat Read statistics from a device
+ taskstats Read task statistics from a device
+
+Flags:
+ -c, --conn string connection profile to use
+ -h, --help Help for newtmgr commands
+ -l, --loglevel string log level to use (default "info")
+ -t, --trace print all bytes transmitted and received
+
+Use "newtmgr [command] --help" for more information about a command.
+</pre></div>
+
+
+<p>```
+<br></p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/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 d4adb46..6398a54 100644
--- a/develop/os/get_started/cross_tools/index.html
+++ b/develop/os/get_started/cross_tools/index.html
@@ -392,11 +392,14 @@
</div>
<h1 id="installing-cross-tools-for-arm">Installing Cross Tools for ARM</h1>
-<p>This 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. You will also have to use the Newt tool installed to run natively on your machine. You may choose to do this instead of using the build toolchain and Newt tool available in a Docker container.</p>
-<p>This page provides guidance for installing the tools directly on your MAC and Linux machine. See the relevant sections below.</p>
+<p>This 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:</p>
+<ul>
+<li>ARM Cross toolchain</li>
+<li>Debugger to load and debug your device</li>
+</ul>
<p><br></p>
-<h2 id="install-arm-cross-tools-in-mac-os-x">Install ARM Cross tools in Mac OS X</h2>
-<h3 id="install-tool-chain">Install Tool Chain</h3>
+<h2 id="install-arm-cross-toolchain">Install ARM Cross Toolchain</h2>
+<h3 id="install-arm-toolchain-for-mac-os-x">Install ARM Toolchain For Mac OS X</h3>
<p>Install the PX4 Toolchain and check the version installed. ARM maintains a
pre-built GNU toolchain with a GCC source branch targeted at Embedded ARM
Processors, namely Cortex-R/Cortex-M processor families. After installing,
@@ -420,22 +423,7 @@ available. Mynewt OS will eventually work with multiple versions available,
including the latest releases. However, at present we have tested only with
this version and recommend it for getting started. </p>
<p><br></p>
-<h3 id="install-openocd">Install OpenOCD</h3>
-<p>OpenOCD (Open On-Chip Debugger) is open-source software that allows your
-computer to interface with the JTAG debug connector on a variety of boards. A
-JTAG connection lets you debug and test embedded target devices. For more on
-OpenOCD go to <a href="http://openocd.org">http://openocd.org</a>.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ brew install open-ocd
-$ which openocd
-/usr/local/bin/openocd
-$ ls -l $(which openocd)
-lrwxr-xr-x 1 <user> admin 36 Sep 17 16:22 /usr/local/bin/openocd -> ../Cellar/open-ocd/0.9.0/bin/openocd
-</pre></div>
-
-
-<p><br></p>
-<h2 id="install-arm-cross-arm-tools-for-linux">Install ARM cross arm tools for Linux</h2>
-<h3 id="install-tool-chain_1">Install Tool Chain</h3>
+<h3 id="install-arm-toolchain-for-linux">Install ARM Toolchain For Linux</h3>
<p>On a Debian-based Linux distribution, gcc 4.9.3 for ARM can be installed with
apt-get as documented below. The steps are explained in depth at
<a href="https://launchpad.net/~team-gcc-arm-embedded/+archive/ubuntu/ppa">https://launchpad.net/~team-gcc-arm-embedded/+archive/ubuntu/ppa</a>.</p>
@@ -448,20 +436,86 @@ $ sudo apt-get install gdb-arm-none-eabi
<p><br></p>
-<h3 id="install-openocd_1">Install OpenOCD</h3>
+<h2 id="install-debugger">Install Debugger</h2>
+<p>Mynewt uses, depending on the board, either the OpenOCD or SEGGER J-Link debugger. </p>
+<h3 id="install-openocd">Install OpenOCD</h3>
<p>OpenOCD (Open On-Chip Debugger) is open-source software that allows your
computer to interface with the JTAG debug connector on a variety of boards. A
JTAG connection lets you debug and test embedded target devices. For more on
OpenOCD go to <a href="http://openocd.org">http://openocd.org</a>.</p>
-<p>If you are running Ubuntu 15.x, then you are in luck and you can simply run: </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ sudo apt-get install openocd
+<p>OpenOCD version 0.10.0 with nrf52 support is required. A binary for this version is available to download for Mac OS and Linux.</p>
+<p><br></p>
+<h4 id="install-openocd-on-mac-os">Install OpenOCD on Mac OS</h4>
+<p>Step 1: Download the <a href="https://github.com/runtimeco/openocd-binaries/raw/master/openocd-bin-0.10.0-MacOS.tgz">binary tarball for Mac OS</a>.</p>
+<p>Step 2: Change to the root directory: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$cd /
+</pre></div>
+
+
+<p><br>
+Step 3: Untar the tarball and install into <strong> /usr/local/bin</strong>. You will need to replace <strong> ~/Downloads </strong> with the directory that the tarball is downloaded to. </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">sudo tar -xf ~/Downloads/openocd-bin-0.10.0-MacOS.tgz `
+</pre></div>
+
+
+<p><br>
+Step 4: Check the OpenOCD version you are using: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$which openocd
+/usr/local/bin/openocd
+$openocd -v
+Open On-Chip Debugger 0.10.0
+Licensed under GNU GPL v2
+For bug reports, read
+http://openocd.org/doc/doxygen/bugs.html
+</pre></div>
+
+
+<p>You should see version: <strong>0.10.0</strong>. </p>
+<p><br></p>
+<h4 id="install-openocd-on-linux">Install OpenOCD on Linux</h4>
+<p>Step 1: Download the <a href="https://github.com/runtimeco/openocd-binaries/raw/master/openocd-bin-0.10.0-Linux.tgz">binary tarball for Linux</a></p>
+<p>Step 2: Change to the root directory: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$cd /
</pre></div>
-<p>For this project, you should download the openocd 0.8.0 package from
-<a href="https://launchpad.net/ubuntu/vivid/+source/openocd">https://launchpad.net/ubuntu/vivid/+source/openocd</a>.
-The direct link to the amd64 build is
-<a href="http://launchpadlibrarian.net/188260097/openocd_0.8.0-4_amd64.deb">http://launchpadlibrarian.net/188260097/openocd_0.8.0-4_amd64.deb</a>. </p>
+<p><br>
+Step 3: Untar the tarball and install into <strong> /usr/local/bin</strong>. You will need to replace <strong> ~/Downloads </strong> with the directory that the tarball is downloaded to. </p>
+<p><strong> Note:</strong> You must specify the -p option for the tar command.</p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo tar -xpf ~/Downloads/openocd-bin-0.10.0-Linux.tgz
+</pre></div>
+
+
+<p><br>
+Step 4: Check the OpenOCD version you are using: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$which openocd
+/usr/local/bin/openocd
+$openocd -v
+Open On-Chip Debugger 0.10.0
+Licensed under GNU GPL v2
+For bug reports, read
+http://openocd.org/doc/doxygen/bugs.html
+</pre></div>
+
+
+<p>You should see version: <strong>0.10.0</strong>. </p>
+<p>If you see any of these error messages:</p>
+<ul>
+<li>
+<p>openocd: error while loading shared libraries: libhidapi-hidraw.so.0: cannot open shared object file: No such file or directory</p>
+</li>
+<li>
+<p>openocd: error while loading shared libraries: libusb-1.0.so.0: cannot open shared object file: No such file or directory </p>
+</li>
+</ul>
+<p>run the following command to install the libraries: </p>
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$sudo apt-get install libhidapi-dev:i386
+</pre></div>
+
+
+<p><br></p>
+<h3 id="install-seggar-j-link">Install SEGGAR J-Link</h3>
+<p>You can download and install Segger J-LINK Software and documentation pack from <a href="https://www.segger.com/jlink-software.html">SEGGER</a>. </p>
<div class="row">
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/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 596404f..9b8332e 100644
--- a/develop/os/get_started/get_started/index.html
+++ b/develop/os/get_started/get_started/index.html
@@ -361,13 +361,12 @@
<h2 id="quick-start">Quick Start</h2>
<p>If you are curious about Mynewt and want to get a quick feel for the project, you've come to the right place. We have two options for you:</p>
+<p><br>
+<strong>Option 1 (Recommended)</strong> allows you to install the Newt tool, instances of the Mynewt OS (for simulated targets), and toolchains for developing embedded software (e.g. GNU toolchain) natively on your laptop or computer. We have tried to make the process easy. For example, for the Mac OS we created brew formulas. </p>
+<p>We recommend this option if you are familiar with such environments or are concerned about performance on your machine. Follow the instructions to <a href="../native_tools/">install native tools</a> and <a href="../cross_tools/">install cross tools for ARM</a> if you prefer this option.</p>
<p><br></p>
-<p><strong>Option 1</strong> is an easy, self-contained way to get up and running with Mynewt - but has limitations! The Newt tool and build toolchains are all available in a single <a href="../docker/">All-in-one Docker Container</a> that you can install on your laptop or computer.</p>
-<p>However, this is not a long-term option since support is not likely for all features useful or critical to embedded systems development. For example, USB device mapping available in the Docker toolkit (used in this Option 1) is no longer available in the new Docker releases. The Docker option is also typically slower than the native install option. </p>
-<p><span style="color:red"> Therefore, the recommended option is Option 2 below. </span></p>
-<p><br></p>
-<p><strong>Option 2 (Recommended)</strong> allows you to install the Newt tool, instances of the Mynewt OS (for simulated targets), and toolchains for developing embedded software (e.g. GNU toolchain) natively on your laptop or computer. We have tried to make the process easy. For example, for the Mac OS we created brew formulas. </p>
-<p>You want this option if you are familiar with such environments or are concerned about performance on your machine. Follow the instructions to <a href="../native_tools/">install native tools</a> and <a href="../cross_tools/">install cross tools for ARM</a> if you prefer this option.</p>
+<p><strong>Option 2</strong> is an easy, self-contained way to get up and running with Mynewt - but has limitations! The Newt tool and build toolchains are all available in a single <a href="../docker/">All-in-one Docker Container</a> that you can install on your laptop or computer.</p>
+<p>However, this is not a long-term option since support is not likely for all features useful or critical to embedded systems development. For example, USB device mapping available in the Docker toolkit is no longer available in the new Docker releases. The Docker option is also typically slower than the native install option. </p>
<p><br></p>
<p>You can then proceed with the instructions on how to
* <a href="../project_create/">Create Your First Project</a> - on simulated hardware.</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/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 0a6e774..2e4082a 100644
--- a/develop/os/get_started/native_tools/index.html
+++ b/develop/os/get_started/native_tools/index.html
@@ -411,8 +411,8 @@
<p><br></p>
<p>Check the gcc version you have installed (either using brew or previously installed). The brew-installed version can be checked using <code>brew list gcc</code>. 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 <code><mynewt-src-directory>/repos/apache-mynewt-core/compiler/sim/compiler.yml</code> file to change the default <code>gcc-5</code> defined there to <code>gcc-6</code>. In other words, replace the lines shown highlighted below:</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"># OS X.
-<span style="background-color: #ffffcc">compiler.path.cc.DARWIN.OVERWRITE: "/usr/local/bin/gcc-5"
-</span><span style="background-color: #ffffcc">compiler.path.as.DARWIN.OVERWRITE: "/usr/local/bin/gcc-5 -x assembler-with-cpp"
+<span style="background-color: #ffffcc">compiler.path.cc.DARWIN.OVERWRITE: "gcc-5"
+</span><span style="background-color: #ffffcc">compiler.path.as.DARWIN.OVERWRITE: "gcc-5"
</span>compiler.path.objdump.DARWIN.OVERWRITE: "gobjdump"
compiler.path.objsize.DARWIN.OVERWRITE: "objsize"
compiler.path.objcopy.DARWIN.OVERWRITE: "gobjcopy"
@@ -420,16 +420,16 @@ compiler.path.objcopy.DARWIN.OVERWRITE: "gobjcopy"
<p>with the following:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">compiler.path.cc.DARWIN.OVERWRITE: "/usr/local/bin/gcc-6"
-compiler.path.as.DARWIN.OVERWRITE: "/usr/local/bin/gcc-6 -x assembler-with-cpp\u201d
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">compiler.path.cc.DARWIN.OVERWRITE: "gcc-6"
+compiler.path.as.DARWIN.OVERWRITE: "gcc-6\u201d
</pre></div>
<p><br></p>
<p>In case you wish to use Clang, you can change your <code><mynewt-src-directory>/repos/apache-mynewt-core/compiler/sim/compiler.yml</code> to use Clang. Delete the gcc-5 DARWIN.OVERWRITE lines highlighted below.</p>
<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%"># OS X.
-<span style="background-color: #ffffcc">compiler.path.cc.DARWIN.OVERWRITE: "/usr/local/bin/gcc-5"
-</span><span style="background-color: #ffffcc">compiler.path.as.DARWIN.OVERWRITE: "/usr/local/bin/gcc-5 -x assembler-with-cpp"
+<span style="background-color: #ffffcc">compiler.path.cc.DARWIN.OVERWRITE: "gcc-5"
+</span><span style="background-color: #ffffcc">compiler.path.as.DARWIN.OVERWRITE: "gcc-5"
</span>compiler.path.objdump.DARWIN.OVERWRITE: "gobjdump"
compiler.path.objsize.DARWIN.OVERWRITE: "objsize"
compiler.path.objcopy.DARWIN.OVERWRITE: "gobjcopy"
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/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 3c72674..c932da5 100644
--- a/develop/os/get_started/project_create/index.html
+++ b/develop/os/get_started/project_create/index.html
@@ -442,7 +442,7 @@ file. </p>
</pre></div>
-<p>Changing to 1-dev will put you on the develop branch. <strong>The Develop Branch may not be stable and you may encounter bugs or other problems.</strong></p>
+<p>Changing to 0-dev will put you on the latest master branch. <strong>This branch may not be stable and you may encounter bugs or other problems.</strong></p>
<p><br></p>
<h3 id="newt-install">Newt Install</h3>
<p>Once you've switched into your new project's directory, the next step is to fetch
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/get_started/vocabulary/index.html
----------------------------------------------------------------------
diff --git a/develop/os/get_started/vocabulary/index.html b/develop/os/get_started/vocabulary/index.html
index 7dee262..18e7b19 100644
--- a/develop/os/get_started/vocabulary/index.html
+++ b/develop/os/get_started/vocabulary/index.html
@@ -363,8 +363,8 @@ the <code>apache-mynewt-core</code> repository.</p>
</li>
<li>
<p><code>vers=1-latest</code>: Defines the repository version. This string will use the
-latest code in the 'Master' github branch. To use the latest version in the
-develop branch, just change it to <code>vers=1-dev</code></p>
+latest stable version in the 'Master' github branch. To use the latest version in the
+master branch, just change it to <code>vers=0-dev</code>. Note that this branch might not be stable. </p>
</li>
</ul>
<p>Repositories are versioned collections of packages. </p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/tutorials/STM32F303/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/STM32F303/index.html b/develop/os/tutorials/STM32F303/index.html
deleted file mode 100644
index 00802d0..0000000
--- a/develop/os/tutorials/STM32F303/index.html
+++ /dev/null
@@ -1,774 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
- <head>
- <meta charset="utf-8">
- <meta http-equiv="X-UA-Compatible" content="IE=edge">
- <meta name="viewport" content="width=device-width, initial-scale=1.0">
-
-
- <!-- This is broken by doc revisioning.
- <link rel="canonical" href="http://mynewt.apache.org/os/tutorials/STM32F303/"> -->
- <link rel="shortcut icon" href="../../../img/favicon.ico">
-
- <title>toc - Apache Mynewt</title>
-
- <link href="../../../css/bootstrap-3.0.3.min.css" rel="stylesheet">
- <link rel="stylesheet" href="../../../css/highlight.css">
- <link href="../../../css/base.css" rel="stylesheet">
- <link href="../../../css/custom.css" rel="stylesheet">
- <link href="../../../css/v2.css" rel="stylesheet">
- <link href="https://fonts.googleapis.com/css?family=Lato" rel="stylesheet">
- <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css">
- <link href="../../../extra.css" rel="stylesheet">
-
- <!-- HTML5 shim and Respond.js IE8 support of HTML5 elements and media queries -->
- <!--[if lt IE 9]>
- <script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script>
- <script src="https://oss.maxcdn.com/libs/respond.js/1.3.0/respond.min.js"></script>
- <![endif]-->
-
-
- <script>
- (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
- (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
- m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
- })(window,document,'script','//www.google-analytics.com/analytics.js','ga');
-
- ga('create', 'UA-72162311-1', 'auto');
- ga('send', 'pageview');
- </script>
-
- </head>
-
-
- <body class="toc">
-
-
- <div class="container">
- <div class="row v2-main-banner">
- <a class="logo-cell" href="/">
- <img class="logo" src="/img/logo.png">
- </a>
- <div class="tagline-cell">
- <h4 class="tagline">An OS to build, deploy and securely manage billions of devices</h4>
- </div>
- <div class="news-cell">
- <div class="well">
- <h4>Latest News:</h4> <a href="/download">Apache Mynewt 1.0.0</a> released (March 22, 2017)
- </div>
- </div>
- </div>
-</div>
-
-
-
-
-
-
-
-
-<nav id="navbar" class="navbar navbar-inverse affix-top" data-spy="affix" data-offset-top="150" role="navigation">
- <div class="container">
- <!-- Collapsed navigation -->
- <div class="navbar-header">
- <!-- Expander button -->
- <button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
- <span class="sr-only">Toggle navigation</span>
- <span class="icon-bar"></span>
- <span class="icon-bar"></span>
- <span class="icon-bar"></span>
- </button>
-
- </div>
-
- <!-- Expanded navigation -->
- <div class="navbar-collapse collapse">
- <!-- Main navigation -->
- <ul class="nav navbar-nav navbar-right">
- <li
- class=""
->
- <a href="/"><i class="fa fa-home" style="font-size: larger;"></i></a>
- </li>
- <li
- class="important"
->
- <a href="/quick-start/">Quick Start</a>
- </li>
- <li
- class=""
->
- <a href="/about/">About</a>
- </li>
- <li
- class=""
->
- <a href="/talks/">Talks</a>
- </li>
- <li
- class="active"
->
- <a href="/latest/os/introduction">Documentation</a>
- </li>
- <li
- class=""
->
- <a href="/download/">Download</a>
- </li>
- <li
- class=""
->
- <a href="/community/">Community</a>
- </li>
- <li
- class=""
->
- <a href="/events/">Events</a>
- </li>
- </ul>
-
- <!-- Search, Navigation and Repo links -->
- <ul class="nav navbar-nav navbar-right">
-
- </ul>
- </div>
- </div>
-</nav>
-
-
-
- <div class="container">
-
- <div class="row">
- <div class="col-md-3 v2-sidebar sidebar-container"><div id="docSidebar" class="hidden-print" role="complementary">
- <div class="top">
- <div role="search">
- <form id="rtd-search-form" class="wy-form" action="../../../search.html" method="get">
- <div class="form-group">
- <input type="text" name="q" class="form-control" placeholder="Search documentation" />
- </div>
- </form>
- </div>
- </div>
- <ul class="toc-nav">
- <li class="doc-version">
-<select class="form-control" onchange="if (this.value) window.location.href=this.value">
-
- <option
- value="/develop/os/introduction"
- selected="selected"
- >
- Version: develop (latest)
- </option>
-
- <option
- value="/v0_9_0/os/introduction"
-
- >
- Version: 0.9.0
- </option>
-
-</select>
-</li>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- <li ><a href="../../introduction/">Mynewt Documentation</a>
-
-
- <ul>
-
-
-
-
-
-
-
- <li ><a href="../../get_started/get_started/">Basic Setup</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../../get_started/vocabulary/">Concepts</a>
- </li>
-
-
-
-
-
-
-
- <li ><a href="../tutorials/">Tutorials</a>
-
-
- <ul>
-
-
-
-
-
-
-
- <li ><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 class="active"><a href="./">Blinky on STM32F303</a>
-
-
- <ul>
-
-
-
-
-
- <li >
- <a href="../pin-wheel-mods/">Pinwheel Blinky</a>
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
- <li >
- <a href="../nRF52/">Blinky on nRF52</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../rbnano2/">Blinky on RedBear Nano 2</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../blinky_console/">Add Console and Shell to Blinky</a>
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../repo/add_repos/">Work with repositories</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../project-slinky/">Project Slinky for Remote Comms</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../ibeacon/">BLE iBeacon</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../eddystone/">BLE Eddystone</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../add_newtmgr/">Enable Newt Manager in any app</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../add_shell/">Enable the OS Shell and Console</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../tasks_lesson/">Tasks and Priority Management</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../wi-fi_on_arduino/">Enable Wi-Fi on Arduino MKR1000</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../unit_test/">Write a Test Suite for a Package</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../event_queue/">Events and Event Queues</a>
- </li>
-
-
-
-
-
- <li >
- <a href="../bletiny_project/">BLE app to check stats via console</a>
- </li>
-
-
-
-
-
-
-
- <li ><a href="../bleprph/bleprph-intro/">BLE peripheral project</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../blehci_project/">BLE HCI interface</a>
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../air_quality_sensor/
-">Air-quality Sensor project</a>
-
-
- </li>
-
-
-
-
-
- <li >
- <a href="../nrf52_adc/">Add an Analog Sensor</a>
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../os_user_guide/">OS User Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../../../network/ble/ble_intro/
-">BLE User Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../../newt/newt_intro/">Newt Tool Guide</a>
-
-
- </li>
-
-
-
-
-
-
-
- <li ><a href="../../../newtmgr/overview/">Newt Manager Guide</a>
-
-
- </li>
-
-
-
- </ul>
-
- </li>
-
-
-
-
-
-
-
- <li><a href="
- ../../../faq/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="../blinky/">Project Blinky</a></li>
-
-
-
- <li>» Blinky on STM32F303</li>
-
-
-
-
-
- </ul>
-</div>
- </div>
-
- <h2 id="blinky-your-hello-world-on-stm32f303-discovery">Blinky, your "Hello World!", on STM32F303 Discovery</h2>
-<p><br></p>
-<h3 id="objective">Objective</h3>
-<p>Learn how to use packages from a default application repository of Mynewt to build your first <em>Hello World</em> application (Blinky) on a target board. Once built using the <em>newt</em> tool, this application will blink the LED lights on the target board.</p>
-<p>Create a project with a simple app that blinks an LED on the stmf303
-discovery board. In the process import some external libraries into your project. Download the application to the target and watch it blink!</p>
-<p><br></p>
-<h3 id="what-you-need">What you need</h3>
-<ul>
-<li>Discovery kit with STM32F303VC MCU</li>
-<li>Laptop running Mac OSX. </li>
-<li>It is assumed you have already installed newt tool. </li>
-<li>It is assumed you already installed native tools as described <a href="../../get_started/native_tools/">here</a></li>
-</ul>
-<p>Also, we assume that you're familiar with UNIX shells. Let's gets started!</p>
-<p><br></p>
-<h3 id="create-a-project">Create a project</h3>
-<p>Create a new project to hold your work. For a deeper understanding, you can read about project creation in
-<a href="../../get_started/project_create/">Get Started -- Creating Your First Project</a>
-or just follow the commands below.</p>
-<p>If you've already created a project from another tutorial, you can re-use
-that 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
-</pre></div>
-
-
-<p><strong>Note:</strong> Don't forget to change into the <code>myproj</code> directory.</p>
-<p><br></p>
-<h3 id="import-external-stm32f3-library-support">Import External STM32F3 Library support</h3>
-<p>The STM32F303 support for Mynewt lives in an external repository. It's
-necessary to add another repository to the project. To do this,
-edit the file <code>project.yml</code> in the root directory of your project <code>myproj</code></p>
-<p>This requires two changes to this file.</p>
-<ol>
-<li>You must define the properties of the external repository that you want
-to add</li>
-<li>You must include the repository in your project.</li>
-</ol>
-<p>Edit the file <code>project.yml</code> with your favorite editor and add the
-following repository details in the file (after the core
-repository). This gives newt the information to contact the repository
-and extract its contents. In this case, the repository is on github in
-the <code>runtimeinc</code> collection. Its name is <code>mynewt-stm32f3</code> and we will accept
-any version up to the latest. You can look at the contents <a href="https://github.com/runtimeinc/mynewt_stm32f3">here</a>.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">repository.mynewt_stm32f3:
- type: github
- vers: 0-latest
- user: runtimeinc
- repo: mynewt_stm32f3
-</pre></div>
-
-
-<p><br></p>
-<p>In the same file, add the following highlighted line to the
-<code>project.repositories</code> variable. This tells newt to download the
- repository contents into your project. </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">project.repositories:
- - apache-mynewt-core
-<span style="background-color: #ffffcc"> - mynewt_stm32f3
-</span></pre></div>
-
-
-<p><br></p>
-<h3 id="install-dependencies">Install dependencies</h3>
-<p>Now you can install this into the project using:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt install -v
-Downloading repository description for apache-mynewt-core... success!
-...
-apache-mynewt-core successfully installed version 0.9.1-none
-...
-Downloading repository description for mynewt_stm32f3... success!
-Downloading repository mynewt_stm32f3
-...
-Resolving deltas: 100% (65/65), done.
-Checking connectivity... done.
-mynewt_stm32f3 successfully installed version 0.9.0-none
-</pre></div>
-
-
-<p><br></p>
-<h3 id="create-targets">Create targets</h3>
-<p>Create two targets to build using the stmf3 board support package and the
-app blinky example from mynewt. The output of these commands are not
-shown here for brevity. </p>
-<p>The first target is the application image itself. The second
-target is the bootloader which allows you to upgrade your mynewt
-applications. </p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt target create stmf3_blinky
-$ newt target set stmf3_blinky build_profile=optimized
-$ newt target set stmf3_blinky bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
-$ newt target set stmf3_blinky app=apps/blinky
-
-$ newt target create stmf3_boot
-$ newt target set stmf3_boot app=@apache-mynewt-core/apps/boot
-$ newt target set stmf3_boot bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
-$ newt target set stmf3_boot build_profile=optimized
-
-$ newt target show
-
-targets/stmf3_blinky
- app=apps/blinky
- bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
- build_profile=optimized
-targets/stmf3_boot
- app=apps/boot
- bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
- build_profile=optimized
-</pre></div>
-
-
-<p><br></p>
-<h3 id="build-the-target-executables">Build the target executables</h3>
-<p>To build the images, use the <code>newt build</code> command below.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt build stmf3_blinky
- ...
-Archiving stm32f3discovery.a
-Linking blinky.elf
-App successfully built: ~/dev/myproj/bin/stmf3_blinky/apps/blinky/blinky.elf
-
-$ newt build stmf3_boot
-Compiling log_shell.c
-Archiving log.a
-Linking boot.elf
-App successfully built: ~/dev/myproj/bin/stmf3_boot/apps/boot/boot.elf
-</pre></div>
-
-
-<p><br></p>
-<h3 id="sign-and-create-the-blinky-application-image">Sign and create the blinky application image</h3>
-<p>You must sign and version your application image to download it using newt. Use
-the <code>newt create-image</code> command to perform this action. Here we assign this
-image an arbitrary version <code>1.2.3</code>.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt create-image stmf3_blinky 1.2.3
-App image successfully generated: ~/dev/myproj/bin/stmf3_blinky/apps/blinky/blinky.img
-Build manifest:~/dev/myproj/bin/stmf3_blinky/apps/blinky/manifest.json
-</pre></div>
-
-
-<p><br></p>
-<h3 id="configure-the-hardware">Configure the hardware</h3>
-<p>The STM32F3DISCOVERY board includes an ST-LINK/V2 embedded debug tool interface that will be used to program/debug the board. To program the MCU on the board, simply plug in the two jumpers on CN4, as shown in the picture in red. If you want to learn more about the board you will find the User Manual at <a href="http://www.st.com/st-web-ui/static/active/jp/resource/technical/document/user_manual/DM00063382.pdf">http://www.st.com/st-web-ui/static/active/jp/resource/technical/document/user_manual/DM00063382.pdf</a></p>
-<p>Just plug the USB cable into the <code>USB ST-LINK</code> port and it should power on and be ready to dowload to.</p>
-<ul>
-<li><img alt="STMdiscovery" src="../pics/STM32f3discovery_connector.png" /></li>
-</ul>
-<p><br></p>
-<h3 id="download-the-images">Download the Images</h3>
-<p>Use the <code>newt load</code> command to download the images to the target board.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ newt -v load stmf3_boot
-$ newt -v load stmf3_blinky
-</pre></div>
-
-
-<p><br></p>
-<h3 id="watch-the-led-blink">Watch the LED blink</h3>
-<p>Congratulations! You have built, downloaded, and run your first application using mynewt for the stm32f3 discovery board. One of the LEDs on the LED wheel should be blinking at 1 Hz.</p>
-<p><br></p>
-<h3 id="want-more">Want more?</h3>
-<p>Want to make your board do something a little more exciting with the LEDs? Then try making the modifications to the Blinky app to make it a <a href="../pin-wheel-mods/">pin-wheel app</a> and you can light all the LEDs in a pin-wheel fashion.</p>
-<p>We have more fun tutorials for you to get your hands dirty. Be bold and try other Blinky-like <a href="../nRF52/">tutorials</a> or try enabling additional functionality such as <a href="../project-slinky/">remote comms</a> on the current board.</p>
-<p>If you see anything missing or want to send us feedback, please do so by signing up for appropriate mailing lists on our <a href="../../../community/">Community Page</a>.</p>
-<p>Keep on hacking and blinking!</p>
-
- <div class="row">
-
-
-
-
-<ul class="nav nav-pills" style="margin-bottom: 10px">
- <li>
-
- <a href=../olimex/>
- <span class="fa fa-arrow-left"></span>
- Previous: Blinky on Olimex
- </a>
-
- </li>
- <li class="pull-right">
-
- <a href=../pin-wheel-mods/>
- Next: Pinwheel 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/45c390ea/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 9620a75..41b0eb3 100644
--- a/develop/os/tutorials/arduino_zero/index.html
+++ b/develop/os/tutorials/arduino_zero/index.html
@@ -265,17 +265,6 @@
-
-
- <li ><a href="../STM32F303/">Blinky on STM32F303</a>
-
-
- </li>
-
-
-
-
-
<li >
<a href="../nRF52/">Blinky on nRF52</a>
</li>
@@ -543,6 +532,7 @@
<li>Meet the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
<li>Have an Arduino Zero board.<br />
Note: There are many flavors of Arduino. Make sure you are using an Arduino Zero. See below for the versions of Arduino Zero that are compatible with this tutorial.</li>
+<li>Install the <a href="../../../os/get_started/cross_tools/">OpenOCD debugger</a>.</li>
</ul>
<p>This tutorial uses the Arduino Zero Pro board. The tutorial has been tested on the following three Arduino Zero boards - Zero, M0 Pro, and Zero-Pro.</p>
<p><img src="https://www.arduino.cc/en/uploads/Main/Zero_Usb_Ports.jpg" alt="Drawing" style="width: 390px;"/>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/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 de2973b..06932ac 100644
--- a/develop/os/tutorials/blehci_project/index.html
+++ b/develop/os/tutorials/blehci_project/index.html
@@ -594,13 +594,16 @@ Bluetooth monitor ver 5.37
<p><br></p>
<h3 id="attach-the-blehci-device-to-bluez">Attach the blehci device to BlueZ</h3>
<p>In a different terminal, attach the blehci device to the BlueZ daemon (substitute the correct /dev filename for ttyUSB0).</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ sudo btattach -B /dev/ttyUSB0 -S 115200
+<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ sudo btattach -B /dev/ttyUSB0 -S 1000000
Attaching BR/EDR controller to /dev/ttyUSB0
Switched line discipline from 0 to 15
Device index 1 attached
</pre></div>
+<p>The baud rate used to connect to the controller may be changed by overriding the default value of 1000000 in the <code>net/nimble/transport/uart/syscfg.yml</code>. Settings in the serial transport <code>syscfg.yml</code> file can be overridden by a higher priority package such as the application. So, for example, you may set the <code>BLE_HCI_UART_BAUD</code> to a different value in <code>apps/blehci/syscfg.yml</code>.</p>
+<p>If there is no CTS/RTS lines present in the test environment, flow control should be turned off. This can be done with
+-N option for btattach. <strong>Note:</strong> -N option came with BlueZ ver 5.44.</p>
<p><br></p>
<h3 id="start-btmgmt-to-send-commands">Start btmgmt to send commands</h3>
<p>In a third terminal, start btmgmt. This tool allows you to send commands to the blehci controller. Use the index number that shows up when you <code>btattach</code> in the previous step.</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/tutorials/blinky/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/blinky/index.html b/develop/os/tutorials/blinky/index.html
index 0493a2a..bfc9c0e 100644
--- a/develop/os/tutorials/blinky/index.html
+++ b/develop/os/tutorials/blinky/index.html
@@ -265,17 +265,6 @@
-
-
- <li ><a href="../STM32F303/">Blinky on STM32F303</a>
-
-
- </li>
-
-
-
-
-
<li >
<a href="../nRF52/">Blinky on nRF52</a>
</li>
@@ -556,9 +545,8 @@
<li>Have a computer to build a Mynewt application and connect to the board over USB.</li>
<li>Have a Micro-USB cable to connect the board and the computer.</li>
<li>Install the Newt tool and toolchains (See <a href="../../get_started/get_started/">Basic Setup</a>).</li>
-<li>Install either the Jlink or OpenOCD debugger.</li>
-<li>Create a project space (directory structure) and populate it with the core code repository (apache-mynewt-core) or know how to as explained in <a href="../../../os/get_started/project_create">Creating Your First Project</a>.</li>
-<li>Read the Mynewt OS <a href="../../get_started/vocabulary/">Concepts</a> section.
+<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>
</ul>
<h3 id="overview-of-steps">Overview of Steps</h3>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/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 2e8f957..4761d6b 100644
--- a/develop/os/tutorials/blinky_console/index.html
+++ b/develop/os/tutorials/blinky_console/index.html
@@ -265,17 +265,6 @@
-
-
- <li ><a href="../STM32F303/">Blinky on STM32F303</a>
-
-
- </li>
-
-
-
-
-
<li >
<a href="../nRF52/">Blinky on nRF52</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/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 d37552f..6e9b84a 100644
--- a/develop/os/tutorials/blinky_primo/index.html
+++ b/develop/os/tutorials/blinky_primo/index.html
@@ -265,17 +265,6 @@
-
-
- <li ><a href="../STM32F303/">Blinky on STM32F303</a>
-
-
- </li>
-
-
-
-
-
<li >
<a href="../nRF52/">Blinky on nRF52</a>
</li>
@@ -544,7 +533,7 @@
<ul>
<li>Meet the the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
<li>Have an Arduino Primo board.</li>
-<li>Install a debugger choose one of the two options below: Option 1 requires additional hardware but very easy to set up. </li>
+<li>Install a debugger. Choose one of the two options below: Option 1 requires additional hardware but very easy to set up. </li>
</ul>
<p><br></p>
<h5 id="option-1">Option 1</h5>
@@ -554,20 +543,7 @@
<li>Install the <a href="https://www.segger.com/jlink-software.html">Segger JLINK Software and documentation pack</a>. </li>
</ul>
<h5 id="option-2">Option 2</h5>
-<p>No additional hardware is required but a version of OpenOCD 0.10.0 that is currently in development needs to be installed. A patch for the nRF52 has been applied to the OpenOCD code in development and a tarball has been made available for download <a href="../downloads/openocd-wnrf52.tgz">here</a>. Untar it. From the top of the directory tree ("openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4"), build it using the following configuration:</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$./configure --enable-cmsis-dap --enable-openjtag_ftdi --enable-jlink --enable-stlink
-</pre></div>
-
-
-<p>Then run <code>make</code> and <code>sudo make install</code>. This step takes minutes, so be patient.</p>
-<div class="codehilite" style="background: #ffffff"><pre style="line-height: 125%">$ openocd -v
-Open On-Chip Debugger 0.10.0-dev-snapshot (2016-05-20-10:43)
-Licensed under GNU GPL v2
-For bug reports, read
- http://openocd.org/doc/doxygen/bugs.html
-</pre></div>
-
-
+<p>This board requires a patch version of OpenOCD 0.10.0 that is in development. See <a href="../../get_started/cross_tools/">Install OpenOCD</a> instructions to install it if you do not have this version installed.</p>
<p>You can now use openocd to upload to Arduino Primo board via the USB port itself.</p>
<h3 id="create-a-project">Create a Project</h3>
<p>Create a new project if you do not have an existing one. You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already created a project.</p>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/tutorials/nRF52/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/nRF52/index.html b/develop/os/tutorials/nRF52/index.html
index b4d86ea..36fbb3c 100644
--- a/develop/os/tutorials/nRF52/index.html
+++ b/develop/os/tutorials/nRF52/index.html
@@ -265,17 +265,6 @@
-
-
- <li ><a href="../STM32F303/">Blinky on STM32F303</a>
-
-
- </li>
-
-
-
-
-
<li class="active">
<a href="./">Blinky on nRF52</a>
</li>
@@ -549,6 +538,7 @@
<li>Eval Kit from Rigado - BMD-300-EVAL-ES</li>
</ul>
</li>
+<li>Install the <a href="https://www.segger.com/jlink-software.html">Segger JLINK Software and documentation pack</a>.</li>
</ul>
<p>This tutorial uses the Nordic nRF52-DK board.</p>
<h3 id="create-a-project">Create a Project</h3>
@@ -716,9 +706,9 @@ $
<ul class="nav nav-pills" style="margin-bottom: 10px">
<li>
- <a href=../pin-wheel-mods/>
+ <a href=../olimex/>
<span class="fa fa-arrow-left"></span>
- Previous: Pinwheel Blinky
+ Previous: Blinky on Olimex
</a>
</li>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/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 9e88c62..933f8f4 100644
--- a/develop/os/tutorials/nrf52_adc/index.html
+++ b/develop/os/tutorials/nrf52_adc/index.html
@@ -526,7 +526,7 @@ project.repositories:
#
repository.apache-mynewt-core:
type: github
- vers: 1-dev
+ vers: 1-latest
user: apache
repo: incubator-mynewt-core
<span style="background-color: #ffffcc">repository.mynewt_nordic:
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/45c390ea/develop/os/tutorials/olimex/index.html
----------------------------------------------------------------------
diff --git a/develop/os/tutorials/olimex/index.html b/develop/os/tutorials/olimex/index.html
index 9e1e071..0780b13 100644
--- a/develop/os/tutorials/olimex/index.html
+++ b/develop/os/tutorials/olimex/index.html
@@ -265,17 +265,6 @@
-
-
- <li ><a href="../STM32F303/">Blinky on STM32F303</a>
-
-
- </li>
-
-
-
-
-
<li >
<a href="../nRF52/">Blinky on nRF52</a>
</li>
@@ -544,9 +533,10 @@
<li>Meet the prerequisites listed in <a href="../blinky/">Project Blinky</a>.</li>
<li>Have a STM32-E407 development board from Olimex. </li>
<li>Have a ARM-USB-TINY-H connector with JTAG interface for debugging ARM microcontrollers (comes with the ribbon cable to hook up to the board)</li>
-<li>Have a USB A-B type cable to connect the debugger to your computer.
-<br></li>
+<li>Have a USB A-B type cable to connect the debugger to your computer.</li>
+<li>Install the <a href="../../../os/get_started/cross_tools/">OpenOCD debugger</a>.</li>
</ul>
+<p><br></p>
<h3 id="create-a-project">Create a Project</h3>
<p>Create a new project if you do not have an existing one. You can skip this step and proceed to <a href="#create_targets">create the targets</a> if you already created a project.</p>
<p>Run the following commands to create a new project:</p>
@@ -747,8 +737,8 @@ Let's double check that it is indeed booting from flash and making the LED blink
</li>
<li class="pull-right">
- <a href=../STM32F303/>
- Next: Blinky on STM32F303
+ <a href=../nRF52/>
+ Next: Blinky on nRF52
<span class="fa fa-arrow-right"></span>
</a>