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:51:12 UTC
[01/12] incubator-mynewt-site git commit: 1) Reorganized and updated
the Contributing to Newt and Newtmgr Tools section to reflect the separate
newtmgr git repo. 2) Added a note to indicate this is the setup to use if a
user running on the Linux platform
Repository: incubator-mynewt-site
Updated Branches:
refs/heads/develop 6f5c8273b -> d7a35b7b2
1) Reorganized and updated the Contributing to Newt and Newtmgr Tools section to reflect
the separate newtmgr git repo.
2) Added a note to indicate this is the setup to use if a user running on the Linux platform
wants the latest updates from master.
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/1db5d8d0
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/1db5d8d0
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/1db5d8d0
Branch: refs/heads/develop
Commit: 1db5d8d0cfa4ccb64f6973ece7ab3bf306844dc1
Parents: 6f5c827
Author: cwanda <wa...@happycity.com>
Authored: Sun Apr 23 16:21:19 2017 -0700
Committer: cwanda <wa...@happycity.com>
Committed: Sun Apr 23 16:21:19 2017 -0700
----------------------------------------------------------------------
docs/faq/go_env.md | 147 +++++++++++++++++++++++++++++++++---------------
1 file changed, 103 insertions(+), 44 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/1db5d8d0/docs/faq/go_env.md
----------------------------------------------------------------------
diff --git a/docs/faq/go_env.md b/docs/faq/go_env.md
index 8771ee1..a757420 100644
--- a/docs/faq/go_env.md
+++ b/docs/faq/go_env.md
@@ -1,22 +1,22 @@
-## Contributing to Newt and Newtmgr Tools
-Newt and Newtmgr are written in Go (golang). This guide shows you how to install Go and setup your environment if
-you would like to contribute to the newt or newtmgr tools.
+## Contributing to Newt or Newtmgr Tools
+Newt and Newtmgr are written in Go (golang). This guide shows you how to install Go and setup your environment to update and build the tools if you want to:
+
+* Contribute to newt or newtmgr features or fix bugs.
+* Build the tools with latest updates from the master branch on a Linux platform.
This guide shows you how to perform the following:
-1. Install Go on either Mac OS or Linux.
+1. Install Go on either Mac OS X or Linux. (Tasks that are specific to each platform are called out.)
2. Setup the Go environment.
-3. Download the newt and newtmgr source code.
-4. Build the newt and newtmgr tools.
-5. Update and rebuild the tools.
-
-Steps 2-5 apply to both Mac OS and Linux platforms.
+3. Download the source, build, and install the newt or newtmgr tools.
+4. Update and rebuild the tools.
-**Note:** You will also need to read and follow the instructions from [FAQ](/faq/answers/) to set up your git repos to submit changes.
+**Note:** You will also need to read and follow the instructions from the [FAQ](/faq/answers/) to set up your git repos to submit changes.
### Step 1: Installing Go
-The latest master branch of newt and newtmgr requires GO version 1.6 or higher.
+The latest master branch of newt and newtmgr requires GO version 1.6 or higher. You can skip this step and proceed to Step 2 if you already have Go version 1.6 or higher installed.
+
<br>
#### Installing Go on Mac OS X
@@ -68,13 +68,16 @@ go version go1.6.3 linux/amd64
```
<br>
###Step 2: Setting Up Your Go Environment
-Go provides an environment to compile Go code, construct Go packages, and import Go code. You will use Go commands to import the **newt** repository into your local Go environment. The Go language environment dictates a specific directory structure, or workspace in Go parlance. It must contain three sibling directories with the names **src**, **pkg** and **bin**:
+
+This section describes the Go environment and how to setup a Go workspace. If you already have a Go workspace for your other Go projects, you can skip this step and proceed to Step 3.
+
+Go provides an environment to compile Go code, construct Go packages, and import Go code. You will use Go commands to import the newt or newtmgr package repository into your local Go environment. The Go language environment dictates a specific directory structure, or workspace in Go parlance. It must contain three sibling directories with the names **src**, **pkg** and **bin**:
* src contains Go source files organized into packages (one package per directory)
* pkg contains package objects
-* bin contains executable commands.
+* bin contains the Go application executables that Go builds and installs.
-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 clone the newt repository.
+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 clone the newt and newtmgr repositories.
```no-highlight
$ cd $HOME
@@ -83,61 +86,117 @@ $ cd dev/go
$ export GOPATH=`pwd`
```
<br>
-Add the export GOPATH statement to the ~/.bash_profile file and source the file:
-
+Add the following export statements to your ~/.bash_profile file and source the file:
```no-highlight
-$ vi ~/.bash_profile
-$ source ~/.bash_profile
+export GOPATH=$HOME/dev/go
+export PATH=$GOPATH/bin:$PATH
```
+<br>
+
+###Step 3: Downloading the Source and Installing the Tools
+Newt and newtmgr are individual Go packages and have their own git repositories. You can download the source and install one or both tools.
+
+We use the `go get` command to download the source, build, and install the binary in the **$GOPATH/bin** directory.
<br>
+####Downloading and Installing the Newt Tool
+The newt Go package is **mynewt.apache.org/newt/newt** and is stored in the [Apache Mynewt newt tool repository mirrored on github](https://github.com/apache/incubator-mynewt-newt).
-###Step 3: Downloading the Source
-Use Go commands to retrieve the latest source from the newt repository (currently the ASF incubator directory). Check that the directories are installed.
+Download the newt package source and install the tool:
```no-highlight
-$ go get mynewt.apache.org/newt/...
-$ ls $GOPATH/src/mynewt.apache.org/newt
-DISCLAIMER NOTICE newt newtvm viper
-LICENSE README.md newtmgr util yaml
+$cd $GOPATH
+$go get mynewt.apache.org/newt/newt
+$cd $GOPATH/src/mynewt.apache.org/newt
+$ls
+DISCLAIMER RELEASE_NOTES.md util
+INSTALLING.md build.sh viper
+LICENSE newt yaml
+NOTICE newtmgr
+README.md newtvm
+$git status
+On branch master
+Your branch is up-to-date with 'origin/master'.
+
+nothing to commit, working directory clean
```
+<br>
+**Note:** The source code under the **newtmgr** directory is no longer used or updated. The current **newtmgr** source has its own Git repository.
<br>
+Check that the newt binary is installed and you are using the one from ** $GOPATH/bin**:
-### Step 4: Building the Newt and Newtmgr Tools
-Perform the following commands to build the tools:
```no-highlight
-$ cd $GOPATH/src/mynewt.apache.org/newt/newt
-$ go install
-$ ls $GOPATH/bin/
-newt newtmgr newtvm
+$ls $GOPATH/bin/newt
+~/dev/go/bin/newt
+$which newt
+~/dev/go/bin/newt
+$newt version
+Apache Newt (incubating) version: 1.0.0-dev
```
-
<br>
+####Downloading and Installing the Newtmgr Tool
+The newtmgr Go package is **mynewt.apache.org/newtmgr/newtmgr**. It is stored in the [Apache Mynewt newtmgr tool repository mirrored on github](https://github.com/apache/incubator-mynewt-newtmgr).
-### Step 5: Updating and Rebuilding the Tools
-Change to the directory where you initially installed the source:
+Download the newtmgr package and install the tool:
```no-highlight
-$ cd $GOPATH/src/mynewt.apache.org/newt
+$cd $GOPATH
+$go get mynewt.apache.org/newtmgr/newtmgr
+$cd $GOPATH/src/mynewt.apache.org/newtmgr
+$ls
+DISCLAIMER NOTICE newtmgr
+LICENSE README.md nmxact
+$git status
+On branch master
+Your branch is up-to-date with 'origin/master'.
+
+nothing to commit, working directory clean
```
<br>
-Pull the latest source from the repository (you can change to a different branch using git checkout [branch] if you need to)
+Check that the newtmgr binary is installed and you are using the one from **$GOPATH/bin**:
+
```no-highlight
-$ git pull
+$ls $GOPATH/bin/newtmgr
+~/dev/go/bin/newtmgr
+$which newt
+~/dev/go/bin/newtmgr
```
<br>
-Install the tools from the latest source:
+### Step 4: Updating and Rebuilding the Tools:
+This section shows you how to rebuild the newt and newtmgr tools with the latest updates from the master branch or after you have made changes in your branch.
+
+Here is the general procedure to rebuild either the newt or newtmgr tool. The only difference is the directory where you will be executing the commands from. You will need to repeat the procedure to rebuild both tools.
+
+1. Change to the directory where the local Git repository for the tool is installed.
+2. Pull the latest changes from the master branch. If you made changes you will need to rebase with **origin master** (See [FAQ](/faq/answers/)).
+3. Build and install the tool.
+
+<br>
+Change to the directory where the source for the tool is installed.
+
+For the **newt** tool:
```no-highlight
-$ cd newt
-$ go install
-$ cd ../newtmgr
-$ go install
-$ ls $GOPATH /bin/
-newt newtmgr newtvm
+$cd $GOPATH/src/mynewt.apache.org/newt/newt
```
-This should have updated your newt and newtmgr to the latest version based on the git repository you used.
+For the **newtmgr** tool:
+```no-highlight
+$cd $GOPATH/src/mynewt.apache.org/newtmgr/newtmgr
+```
+<br>
+After you change to the specific tool directory, get the latest updates from the master branch. If you made changes and need to rebase with the origin, add the `--rebase origin master` arguments to the `git pull` command:
+```no-highlight
+$git pull
+```
+
+<br>
+Build and install the tool. The updated binary will be installed in the **$GOPATH/bin** directory:
+
+```no-highlight
+$go install
+```
+You can run the `ls -l` command to check the modification time for the binary to ensure the new version is installed.
[04/12] incubator-mynewt-site git commit: Added how to install
openocd binary. Added information about installing J-Link Added the specific
debugger to install in prerequisites to blinky and slinky tutorials. Removed
STM32F303 from list of blinky tutori
Posted by ad...@apache.org.
Added how to install openocd binary.
Added information about installing J-Link
Added the specific debugger to install in prerequisites to blinky and slinky tutorials.
Removed STM32F303 from list of blinky tutorials
Project: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/commit/0c750d32
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/0c750d32
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/0c750d32
Branch: refs/heads/develop
Commit: 0c750d3210b9217b291cfa5ea881adeed1a9a2cc
Parents: 2aa8532
Author: cwanda <wa...@happycity.com>
Authored: Fri Apr 14 21:04:49 2017 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Tue Apr 25 13:03:34 2017 -0700
----------------------------------------------------------------------
docs/os/get_started/cross_tools.md | 103 +++++++++++++++++--------
docs/os/tutorials/arduino_zero.md | 1 +
docs/os/tutorials/blinky.md | 1 -
docs/os/tutorials/blinky_primo.md | 18 +----
docs/os/tutorials/nRF52.md | 1 +
docs/os/tutorials/olimex.md | 2 +
docs/os/tutorials/project-nrf52-slinky.md | 1 +
docs/os/tutorials/project-stm32-slinky.md | 1 +
docs/os/tutorials/rbnano2.md | 3 +-
mkdocs.yml | 3 -
10 files changed, 80 insertions(+), 54 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/0c750d32/docs/os/get_started/cross_tools.md
----------------------------------------------------------------------
diff --git a/docs/os/get_started/cross_tools.md b/docs/os/get_started/cross_tools.md
index b68c1e9..450952d 100644
--- a/docs/os/get_started/cross_tools.md
+++ b/docs/os/get_started/cross_tools.md
@@ -1,14 +1,15 @@
# Installing Cross Tools for ARM
-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.
+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:
-This page provides guidance for installing the tools directly on your MAC and Linux machine. See the relevant sections below.
+* ARM Cross toolchain
+* Debugger to load and debug your device
<br>
-## Install ARM Cross tools in Mac OS X
+## Install ARM Cross Toolchain
-### Install Tool Chain
+### Install ARM Toolchain For Mac OS X
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
@@ -34,27 +35,7 @@ including the latest releases. However, at present we have tested only with
this version and recommend it for getting started.
<br>
-
-### Install OpenOCD
-
-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 [http://openocd.org](http://openocd.org).
-
-```no-highlight
-$ 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
-```
-
-<br>
-
-## Install ARM cross arm tools for Linux
-
-### Install Tool Chain
+### Install ARM Toolchain For Linux
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
@@ -67,21 +48,79 @@ $ sudo apt-get update
$ sudo apt-get install gcc-arm-none-eabi
$ sudo apt-get install gdb-arm-none-eabi
```
+<br>
+## Install Debugger
+Mynewt uses, depending on the board, either the OpenOCD or SEGGER J-Link debugger.
<br>
-###Install OpenOCD
+### Install OpenOCD
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 [http://openocd.org](http://openocd.org).
-If you are running Ubuntu 15.x, then you are in luck and you can simply run:
+OpenOCD version 0.10.0-dev-snapshot that is currently in development is required. A binary for this version is available to download for Mac OS and Linux
+
+#### Install OpenOCD on Mac OS
+Step 1: Download the [binary tarball for Mac OS](https://github.com/runtimeco/openocd-binaries/raw/master/openocd-bin-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4-MacOS.tgz).
+
+Step 2: Change to the root directory:
+```no-highlight
+$cd /
+```
+Step 3: Untar the tarball and install into ** /usr/local/bin**. You will need to replace ** ~/Downloads ** with the directory that the tarball is downloaded to.
```no-highlight
-$ sudo apt-get install openocd
+sudo tar -xf ~/Downloads/openocd-bin-8*-MacOS.tgz `
```
- For this project, you should download the openocd 0.8.0 package from
-[https://launchpad.net/ubuntu/vivid/+source/openocd](https://launchpad.net/ubuntu/vivid/+source/openocd).
-The direct link to the amd64 build is
-[http://launchpadlibrarian.net/188260097/openocd_0.8.0-4_amd64.deb](http://launchpadlibrarian.net/188260097/openocd_0.8.0-4_amd64.deb).
+Step 4: Check the OpenOCD version you are using:
+
+```no-highlight
+$which openocd
+/usr/local/bin/openocd
+$openocd -v
+Open On-Chip Debugger 0.10.0-dev-snapshot (2017-04-04-14:18)
+Licensed under GNU GPL v2
+For bug reports, read
+http://openocd.org/doc/doxygen/bugs.html
+```
+#### Install OpenOCD on Linux
+
+Step 1: Download the [binary tarball for Linux 64 bits](https://github.com/runtimeco/openocd-binaries/raw/master/openocd-bin-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4-Linux.tgz).
+
+Step 2: Change to the root directory:
+```
+$cd /
+```
+
+Step 3: Untar the tarball and install into ** /usr/local/bin**. You will need to replace ** ~/Downloads ** with the directory that the tarball is downloaded to.
+
+```no-highlight
+$sudo tar --no-same-owner -xpf ~/Downloads/openocd-bin-8*-Linux.tgz
+```
+
+Step 4: Check the OpenOCD version you are using:
+
+```no-highlight
+$which openocd
+/usr/local/bin/openocd
+$openocd -v
+Open On-Chip Debugger 0.10.0-dev-snapshot (2017-04-04-14:18)
+Licensed under GNU GPL v2
+For bug reports, read
+http://openocd.org/doc/doxygen/bugs.html
+```
+You should see version: ** 0.10.0-dev-snapshot (2017-04-04-14:18) **.
+
+If you see the following error message:
+
+** openocd: error while loading shared libraries: libftdi.so.1: cannot open shared object file: No such file or directory **
+
+run the following to install the library:
+```no-highlight
+$sudo apt-get install libftdi1
+```
+<br>
+###Install SEGGAR J-Link
+You can download and install Segger J-LINK Software and documentation pack from [SEGGER](https://www.segger.com/jlink-software.html).
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/0c750d32/docs/os/tutorials/arduino_zero.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/arduino_zero.md b/docs/os/tutorials/arduino_zero.md
index dc72b5b..68499b3 100644
--- a/docs/os/tutorials/arduino_zero.md
+++ b/docs/os/tutorials/arduino_zero.md
@@ -6,6 +6,7 @@ This tutorial shows you how to create, build and run the Blinky application on a
* Meet the prerequisites listed in [Project Blinky](/os/tutorials/blinky.md).
* Have an Arduino Zero board.
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.
+* Install the [OpenOCD debugger](/os/get_started/cross_tools/).
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.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/0c750d32/docs/os/tutorials/blinky.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/blinky.md b/docs/os/tutorials/blinky.md
index 59d9ad1..a411e1e 100644
--- a/docs/os/tutorials/blinky.md
+++ b/docs/os/tutorials/blinky.md
@@ -23,7 +23,6 @@ Ensure that you meet the following prerequisites before continuing with one of t
* Have a computer to build a Mynewt application and connect to the board over USB.
* Have a Micro-USB cable to connect the board and the computer.
* Install the Newt tool and toolchains (See [Basic Setup](/os/get_started/get_started.md)).
-* Install either the Jlink or OpenOCD debugger.
* Create a project space (directory structure) and populate it with the core code repository (apache-mynewt-core) or know how to as explained in [Creating Your First Project](/os/get_started/project_create).
* Read the Mynewt OS [Concepts](/os/get_started/vocabulary.md) section.
<br>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/0c750d32/docs/os/tutorials/blinky_primo.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/blinky_primo.md b/docs/os/tutorials/blinky_primo.md
index 1193938..4eaf92d 100644
--- a/docs/os/tutorials/blinky_primo.md
+++ b/docs/os/tutorials/blinky_primo.md
@@ -8,7 +8,7 @@ Note that the Mynewt OS will run on the nRF52 chip in the Arduino Primo board. H
* Meet the the prerequisites listed in [Project Blinky](/os/tutorials/blinky.md).
* Have an Arduino Primo board.
-* Install a debugger choose one of the two options below: Option 1 requires additional hardware but very easy to set up.
+* Install a debugger. Choose one of the two options below: Option 1 requires additional hardware but very easy to set up.
<br>
##### Option 1
@@ -17,21 +17,7 @@ Note that the Mynewt OS will run on the nRF52 chip in the Arduino Primo board. H
* Install the [Segger JLINK Software and documentation pack](https://www.segger.com/jlink-software.html).
##### Option 2
-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 [here](downloads/openocd-wnrf52.tgz). Untar it. From the top of the directory tree ("openocd-code-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4"), build it using the following configuration:
-
-```
-$./configure --enable-cmsis-dap --enable-openjtag_ftdi --enable-jlink --enable-stlink
-```
-
-Then run `make` and `sudo make install`. This step takes minutes, so be patient.
-
-```
-$ 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
-```
+This board requires a patch version of OpenOCD 0.10.0 that is in development. See [Install OpenOCD](/os/get_started/cross_tools.md) instructions to install it if you do not have this version installed.
You can now use openocd to upload to Arduino Primo board via the USB port itself.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/0c750d32/docs/os/tutorials/nRF52.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/nRF52.md b/docs/os/tutorials/nRF52.md
index c62f85e..deca009 100644
--- a/docs/os/tutorials/nRF52.md
+++ b/docs/os/tutorials/nRF52.md
@@ -12,6 +12,7 @@ Note that there are several versions of the nRF52 in the market. The boards test
* Have a nRF52 Development Kit (one of the following)
* Dev Kit from Nordic - PCA 10040
* Eval Kit from Rigado - BMD-300-EVAL-ES
+* Install the [Segger JLINK Software and documentation pack](https://www.segger.com/jlink-software.html).
This tutorial uses the Nordic nRF52-DK board.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/0c750d32/docs/os/tutorials/olimex.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/olimex.md b/docs/os/tutorials/olimex.md
index 44e8b92..0233b59 100644
--- a/docs/os/tutorials/olimex.md
+++ b/docs/os/tutorials/olimex.md
@@ -8,6 +8,8 @@ This tutorial shows you how to create, build, and run the Blinky application on
* Have a STM32-E407 development board from Olimex.
* 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)
* Have a USB A-B type cable to connect the debugger to your computer.
+* Install the [OpenOCD debugger](/os/get_started/cross_tools/).
+
<br>
### Create a Project
Create a new project if you do not have an existing one. You can skip this step and proceed to [create the targets](#create_targets) if you already created a project.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/0c750d32/docs/os/tutorials/project-nrf52-slinky.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/project-nrf52-slinky.md b/docs/os/tutorials/project-nrf52-slinky.md
index dfc4c57..729d32a 100644
--- a/docs/os/tutorials/project-nrf52-slinky.md
+++ b/docs/os/tutorials/project-nrf52-slinky.md
@@ -4,6 +4,7 @@ This tutorial shows you how to create, build and run the Slinky application and
### Prerequisites
* Meet the prerequisites listed in [Project Slinky](/os/tutorials/project-slinky.md).
* Have a Nordic nRF52-DK board.
+* Install the [Segger JLINK Software and documentation pack](https://www.segger.com/jlink-software.html).
### Create a New Project
Create a new project if you do not have an existing one. You can skip this step and proceed to [create the targets](#create_targets) if you already have a project created or completed the [Sim Slinky](project-slinky.md) tutorial.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/0c750d32/docs/os/tutorials/project-stm32-slinky.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/project-stm32-slinky.md b/docs/os/tutorials/project-stm32-slinky.md
index 6ee5f3b..16387c5 100644
--- a/docs/os/tutorials/project-stm32-slinky.md
+++ b/docs/os/tutorials/project-stm32-slinky.md
@@ -8,6 +8,7 @@ This tutorial shows you how to create, build and run the Slinky application and
* 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)
* Have a USB A-B type cable to connect the debugger to your computer.
* Have a USB to TTL Serial Cable with female wiring harness.
+* Install the [OpenOCD debugger](/os/get_started/cross_tools/).
### Create a New Project
Create a new project if you do not have an existing one. You can skip this step and proceed to [create the targets](#create_targets) if you already have a project created or completed the [Sim Slinky](project-slinky.md) tutorial.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/0c750d32/docs/os/tutorials/rbnano2.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/rbnano2.md b/docs/os/tutorials/rbnano2.md
index ea0d3ad..4f93c09 100644
--- a/docs/os/tutorials/rbnano2.md
+++ b/docs/os/tutorials/rbnano2.md
@@ -7,8 +7,7 @@ This tutorial shows you how to create, build and run the Blinky application on a
* Meet the prerequisites listed in [Project Blinky](/os/tutorials/blinky.md).
* Have a RedBear Nano 2 board.
-
-**Note:** You must install a patched version of OpenOCD .10.0 (See [Debugger Option 2 in the Arduino Primo Blinky Tutorial](/os/tutorials/blinky_primo)).
+* Install a patched version of OpenOCD 0.10.0 described in [Install OpenOCD](os/get_started/cross_tools/).
### Create a Project
Create a new project if you do not have an existing one. You can skip this step and proceed to [create the targets](#create_targets) if you already have a project created.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/0c750d32/mkdocs.yml
----------------------------------------------------------------------
diff --git a/mkdocs.yml b/mkdocs.yml
index 61d89cf..8d51e74 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -33,9 +33,6 @@ pages:
- 'Blinky on Arduino Zero': 'os/tutorials/arduino_zero.md'
- 'Blinky on Arduino Primo': 'os/tutorials/blinky_primo.md'
- 'Blinky on Olimex': 'os/tutorials/olimex.md'
- - 'Blinky on STM32F303':
- - toc: 'os/tutorials/STM32F303.md'
- - 'Pinwheel Blinky': 'os/tutorials/pin-wheel-mods.md'
- 'Blinky on nRF52': 'os/tutorials/nRF52.md'
- 'Blinky on RedBear Nano 2': 'os/tutorials/rbnano2.md'
- 'Add Console and Shell to Blinky': 'os/tutorials/blinky_console.md'
[03/12] incubator-mynewt-site git commit: 1) Updated OpenOCD
installation to use 0.10.0 tarball. The linux version is a 32 bit binary. 2)
Remove stm discovery tutorial
Posted by ad...@apache.org.
1) Updated OpenOCD installation to use 0.10.0 tarball. The linux version is a 32 bit binary.
2) Remove stm discovery tutorial
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/737b215e
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/737b215e
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/737b215e
Branch: refs/heads/develop
Commit: 737b215e022ea575c5abdb65664544b8bf59a651
Parents: ef77955
Author: cwanda <wa...@happycity.com>
Authored: Tue Apr 18 21:50:40 2017 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Tue Apr 25 13:03:34 2017 -0700
----------------------------------------------------------------------
docs/os/get_started/cross_tools.md | 42 ++++++++++++++++++++-------------
docs/os/tutorials/tutorials.md | 8 +------
2 files changed, 26 insertions(+), 24 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/737b215e/docs/os/get_started/cross_tools.md
----------------------------------------------------------------------
diff --git a/docs/os/get_started/cross_tools.md b/docs/os/get_started/cross_tools.md
index 450952d..efd6f96 100644
--- a/docs/os/get_started/cross_tools.md
+++ b/docs/os/get_started/cross_tools.md
@@ -52,8 +52,6 @@ $ sudo apt-get install gdb-arm-none-eabi
## Install Debugger
Mynewt uses, depending on the board, either the OpenOCD or SEGGER J-Link debugger.
-<br>
-
### Install OpenOCD
OpenOCD (Open On-Chip Debugger) is open-source software that allows your
@@ -61,65 +59,75 @@ 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 [http://openocd.org](http://openocd.org).
-OpenOCD version 0.10.0-dev-snapshot that is currently in development is required. A binary for this version is available to download for Mac OS and Linux
+OpenOCD version 0.10.0 with nrf52 support is required. A binary for this version is available to download for Mac OS and Linux.
+<br>
#### Install OpenOCD on Mac OS
-Step 1: Download the [binary tarball for Mac OS](https://github.com/runtimeco/openocd-binaries/raw/master/openocd-bin-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4-MacOS.tgz).
+Step 1: Download the [binary tarball for Mac OS](https://github.com/runtimeco/openocd-binaries/raw/master/openocd-bin-0.10.0-MacOS.tgz).
Step 2: Change to the root directory:
```no-highlight
$cd /
```
+<br>
Step 3: Untar the tarball and install into ** /usr/local/bin**. You will need to replace ** ~/Downloads ** with the directory that the tarball is downloaded to.
```no-highlight
-sudo tar -xf ~/Downloads/openocd-bin-8*-MacOS.tgz `
+sudo tar -xf ~/Downloads/openocd-bin-0.10.0-MacOS.tgz `
```
+<br>
Step 4: Check the OpenOCD version you are using:
```no-highlight
$which openocd
/usr/local/bin/openocd
$openocd -v
-Open On-Chip Debugger 0.10.0-dev-snapshot (2017-04-04-14:18)
+Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
```
-#### Install OpenOCD on Linux
-Step 1: Download the [binary tarball for Linux 64 bits](https://github.com/runtimeco/openocd-binaries/raw/master/openocd-bin-89bf96ffe6ac66c80407af8383b9d5adc0dc35f4-Linux.tgz).
+You should see version: **0.10.0**.
+
+<br>
+#### Install OpenOCD on Linux
+Step 1: Download the [binary tarball for Linux](https://github.com/runtimeco/openocd-binaries/raw/master/openocd-bin-0.10.0-Linux.tgz)
Step 2: Change to the root directory:
```
$cd /
```
-
+<br>
Step 3: Untar the tarball and install into ** /usr/local/bin**. You will need to replace ** ~/Downloads ** with the directory that the tarball is downloaded to.
+** Note:** You must specify the -p option for the tar command.
+
```no-highlight
-$sudo tar --no-same-owner -xpf ~/Downloads/openocd-bin-8*-Linux.tgz
+$sudo tar -xpf ~/Downloads/openocd-bin-0.10.0-Linux.tgz
```
-
+<br>
Step 4: Check the OpenOCD version you are using:
```no-highlight
$which openocd
/usr/local/bin/openocd
$openocd -v
-Open On-Chip Debugger 0.10.0-dev-snapshot (2017-04-04-14:18)
+Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
```
-You should see version: ** 0.10.0-dev-snapshot (2017-04-04-14:18) **.
+You should see version: **0.10.0**.
+
+If you see any of these error messages:
-If you see the following error message:
+* openocd: error while loading shared libraries: libhidapi-hidraw.so.0: cannot open shared object file: No such file or directory
-** openocd: error while loading shared libraries: libftdi.so.1: cannot open shared object file: No such file or directory **
+* openocd: error while loading shared libraries: libusb-1.0.so.0: cannot open shared object file: No such file or directory
-run the following to install the library:
+run the following command to install the libraries:
```no-highlight
-$sudo apt-get install libftdi1
+$sudo apt-get install libhidapi-dev:i386
```
<br>
###Install SEGGAR J-Link
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/737b215e/docs/os/tutorials/tutorials.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/tutorials.md b/docs/os/tutorials/tutorials.md
index b66222e..2f16ed1 100644
--- a/docs/os/tutorials/tutorials.md
+++ b/docs/os/tutorials/tutorials.md
@@ -11,7 +11,6 @@ The full list of tutorials can be seen in the navigation bar on the left. New on
* You have installed Docker container of Newt tool and toolchains or you have installed them natively on your machine
* You have created a new project space (directory structure) and populated it with the core code repository (apache-mynewt-core) or know how to as explained in [Creating Your First Project](../get_started/project_create).
* You have at least one of the supported development boards:
- * [STM32F3 discovery kit from ST Micro](STM32F303.md)
* [Arduino Zero hardware](arduino_zero.md)
* [Olimex/STM32F407ZGT6 Cortex-M4 hardware](olimex.md)
* [nRF52 Development Kit from Nordic Semiconductor](nRF52.md)
@@ -28,13 +27,8 @@ The tutorials fall into a few broad categories. Some examples in each category a
* Making an LED blink (the "Hello World" equivalent in the electronics world)
* [Blinky on Arduino Zero hardware](arduino_zero.md)
* [Blinky on Olimex/STM32F407ZGT6 Cortex-M4 hardware](olimex.md)
- * [Blinky on STM32F3 discovery kit from ST Micro](STM32F303.md)
* [Blinky on nRF52 Development Kit from Nordic Semiconductor](nRF52.md) **Note:** This supports BLE.
-
- <br>
-
-* Tweaking available apps to customize behavior e.g. making a more exciting LED blink pattern
- * [Pinwheel Blinky on STM32F3 discovery board](pin-wheel-mods.md)
+ * [Blinky on Redbear Nano2](rbnano2.md)
<br>
[07/12] incubator-mynewt-site git commit: corrected BlueZ options in
blehci tutorial and links in slinky tutorial
Posted by ad...@apache.org.
corrected BlueZ options in blehci tutorial and links in slinky tutorial
This closes #169. This closes #173.
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/e991d47a
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/e991d47a
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/e991d47a
Branch: refs/heads/develop
Commit: e991d47aba7de4af7fd8b8db58356e100842ee91
Parents: e9cff2c
Author: aditihilbert <ad...@runtime.io>
Authored: Tue Apr 25 12:52:46 2017 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Tue Apr 25 13:34:13 2017 -0700
----------------------------------------------------------------------
docs/os/tutorials/blehci_project.md | 7 ++++++-
docs/os/tutorials/project-nrf52-slinky.md | 2 +-
2 files changed, 7 insertions(+), 2 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/e991d47a/docs/os/tutorials/blehci_project.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/blehci_project.md b/docs/os/tutorials/blehci_project.md
index 1824902..173ec66 100644
--- a/docs/os/tutorials/blehci_project.md
+++ b/docs/os/tutorials/blehci_project.md
@@ -155,12 +155,17 @@ Bluetooth monitor ver 5.37
In a different terminal, attach the blehci device to the BlueZ daemon (substitute the correct /dev filename for ttyUSB0).
```
-$ sudo btattach -B /dev/ttyUSB0 -S 115200
+$ 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
```
+The baud rate can be configured by overriding the default value of 1000000 in the `net/nimble/transport/uart/syscfg.yml`. Settings can be overriden by a higher priority package such as the application. So, for example, you may set the `BLE_HCI_UART_BAUD` to a different value in `apps/blehci/syscfg.yml`.
+
+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. **Note:** -N option came with BlueZ ver 5.44.
+
<br>
### Start btmgmt to send commands
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/e991d47a/docs/os/tutorials/project-nrf52-slinky.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/project-nrf52-slinky.md b/docs/os/tutorials/project-nrf52-slinky.md
index 729d32a..4f845fb 100644
--- a/docs/os/tutorials/project-nrf52-slinky.md
+++ b/docs/os/tutorials/project-nrf52-slinky.md
@@ -169,7 +169,7 @@ $
<br>
### Use Newtmgr to Query the Board
-Run some newtmgr commands to query and receive responses back from the board (See the [Newt Manager Guide](newtmgr/overview) for more information on the newtmgr commands).
+Run some newtmgr commands to query and receive responses back from the board (See the [Newt Manager Guide](../../newtmgr/overview) for more information on the newtmgr commands).
Run the `newtmgr echo hello -c nrf52serial` command. This is the simplest command that requests the board to echo back the text.
[10/12] incubator-mynewt-site git commit: Add -ldflags -s when
building newtmgr
Posted by ad...@apache.org.
Add -ldflags -s when building newtmgr
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/e02e2985
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/e02e2985
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/e02e2985
Branch: refs/heads/develop
Commit: e02e29852acc0c7fd4d8d834bd8d858b17d50bb1
Parents: 1db5d8d
Author: cwanda <wa...@happycity.com>
Authored: Tue Apr 25 14:22:32 2017 -0700
Committer: cwanda <wa...@happycity.com>
Committed: Tue Apr 25 14:22:32 2017 -0700
----------------------------------------------------------------------
docs/faq/go_env.md | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/e02e2985/docs/faq/go_env.md
----------------------------------------------------------------------
diff --git a/docs/faq/go_env.md b/docs/faq/go_env.md
index a757420..4b4a880 100644
--- a/docs/faq/go_env.md
+++ b/docs/faq/go_env.md
@@ -142,9 +142,11 @@ The newtmgr Go package is **mynewt.apache.org/newtmgr/newtmgr**. It is stored in
Download the newtmgr package and install the tool:
+**Note:** `-ldflags -s` must be passed to the `go get` command.
+
```no-highlight
$cd $GOPATH
-$go get mynewt.apache.org/newtmgr/newtmgr
+$go get -ldflags -s mynewt.apache.org/newtmgr/newtmgr
$cd $GOPATH/src/mynewt.apache.org/newtmgr
$ls
DISCLAIMER NOTICE newtmgr
@@ -196,6 +198,8 @@ $git pull
<br>
Build and install the tool. The updated binary will be installed in the **$GOPATH/bin** directory:
+(**Note:** `-ldflags -s` must be passed to the `go install` command if you are rebuilding newtmgr)
+
```no-highlight
$go install
```
[09/12] incubator-mynewt-site git commit: clarified baud rate config
in the blehci tutorial
Posted by ad...@apache.org.
clarified baud rate config in the blehci tutorial
This closes #174.
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/a60c6fd7
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/a60c6fd7
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/a60c6fd7
Branch: refs/heads/develop
Commit: a60c6fd78eb74ffad1a73f954a0fa6ae01eb4994
Parents: e991d47
Author: aditihilbert <ad...@runtime.io>
Authored: Tue Apr 25 13:49:43 2017 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Tue Apr 25 13:57:29 2017 -0700
----------------------------------------------------------------------
docs/os/tutorials/blehci_project.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/a60c6fd7/docs/os/tutorials/blehci_project.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/blehci_project.md b/docs/os/tutorials/blehci_project.md
index 173ec66..7bf43af 100644
--- a/docs/os/tutorials/blehci_project.md
+++ b/docs/os/tutorials/blehci_project.md
@@ -161,7 +161,7 @@ Switched line discipline from 0 to 15
Device index 1 attached
```
-The baud rate can be configured by overriding the default value of 1000000 in the `net/nimble/transport/uart/syscfg.yml`. Settings can be overriden by a higher priority package such as the application. So, for example, you may set the `BLE_HCI_UART_BAUD` to a different value in `apps/blehci/syscfg.yml`.
+The baud rate used to connect to the controller may be changed by overriding the default value of 1000000 in the `net/nimble/transport/uart/syscfg.yml`. Settings in the serial transport `syscfg.yml` file can be overridden by a higher priority package such as the application. So, for example, you may set the `BLE_HCI_UART_BAUD` to a different value in `apps/blehci/syscfg.yml`.
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. **Note:** -N option came with BlueZ ver 5.44.
[02/12] incubator-mynewt-site git commit: - Make option 1 - native
install and option 2 docker in Basic Setup.
Posted by ad...@apache.org.
- Make option 1 - native install and option 2 docker in Basic Setup.
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/e9cff2c8
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/e9cff2c8
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/e9cff2c8
Branch: refs/heads/develop
Commit: e9cff2c8944e05535d4c68df36c1d4ab49e5ac73
Parents: 737b215
Author: cwanda <wa...@happycity.com>
Authored: Thu Apr 20 16:35:32 2017 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Tue Apr 25 13:03:34 2017 -0700
----------------------------------------------------------------------
docs/os/get_started/get_started.md | 11 ++++-------
1 file changed, 4 insertions(+), 7 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/e9cff2c8/docs/os/get_started/get_started.md
----------------------------------------------------------------------
diff --git a/docs/os/get_started/get_started.md b/docs/os/get_started/get_started.md
index 86bc56e..add6d37 100644
--- a/docs/os/get_started/get_started.md
+++ b/docs/os/get_started/get_started.md
@@ -3,18 +3,15 @@
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:
<br>
+**Option 1 (Recommended)** 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.
-**Option 1** 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 [All-in-one Docker Container](docker.md) that you can install on your laptop or computer.
-
-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.
-
-<span style="color:red"> Therefore, the recommended option is Option 2 below. </span>
+We recommend this option if you are familiar with such environments or are concerned about performance on your machine. Follow the instructions to [install native tools](native_tools.md) and [install cross tools for ARM](cross_tools.md) if you prefer this option.
<br>
-**Option 2 (Recommended)** 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.
+**Option 2** 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 [All-in-one Docker Container](docker.md) that you can install on your laptop or computer.
-You want this option if you are familiar with such environments or are concerned about performance on your machine. Follow the instructions to [install native tools](native_tools.md) and [install cross tools for ARM](cross_tools.md) if you prefer this option.
+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.
<br>
[08/12] incubator-mynewt-site git commit: Documentation on how to
install newt and newtmgr from debian package
Posted by ad...@apache.org.
Documentation on how to install newt and newtmgr from debian package
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/2fa19db1
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/2fa19db1
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/2fa19db1
Branch: refs/heads/develop
Commit: 2fa19db1d48a6c96c2562e15dd4cf9614698f309
Parents: 6f5c827
Author: cwanda <wa...@happycity.com>
Authored: Tue Apr 25 13:46:40 2017 -0700
Committer: cwanda <wa...@happycity.com>
Committed: Tue Apr 25 13:46:40 2017 -0700
----------------------------------------------------------------------
docs/newt/install/newt_linux.md | 305 ++++++++++++++++++++---------------
docs/newtmgr/install_linux.md | 214 +++++++++++++++++++-----
2 files changed, 356 insertions(+), 163 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/2fa19db1/docs/newt/install/newt_linux.md
----------------------------------------------------------------------
diff --git a/docs/newt/install/newt_linux.md b/docs/newt/install/newt_linux.md
index a2c1671..5956496 100644
--- a/docs/newt/install/newt_linux.md
+++ b/docs/newt/install/newt_linux.md
@@ -1,55 +1,109 @@
-## Install newt tool on Linux
+## Installing Newt on Linux
+
+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:
+
+1. Set up your computer to retrieve Debian packages from the runtimeco debian package repository.
+2. Install the latest stable release version of newt from a Debian binary package.
+3. 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](/faq/go_env) 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.
<br>
-### Getting your Linux box Ready
+### Setting Up Your Computer to Get Packages from runtimeco
+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.
+The following steps must be performed on your computer:
-If you want to build the *newt* tool from its source code, follow the following steps:
+1. Add the `apt-transport-https` package to use HTTPS to retrieve packages.
+2. Download the public key for the runtimeco debian repository and import the key into the apt keychain.
+3. Add the repository for the binary and source packages to the apt source list.
-#### 1. Install git, libcurl
+<br>
+Add the apt-transport-https package:
+```no-highlight
+$sudo apt-get update
+$sudo apt-get install apt-transport-https
```
- $ sudo apt-get install git
- $ sudo apt-get install libcurl4-gnutls-dev
+<br>
+
+
+Download the public key for the runtimeco apt repo (**Note:** There is `-` after the add):
+
+```no-highlight
+wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -
```
+<br>
-**NOTE:** On 64-bit host, you may also need to install gcc-multilib, if you encounter compilation errors related to 'sys/cdefs.h'
+Add the repository for the binary and source packages to the apt source list:
+```no-highlight
+$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
+```
<br>
+Check the content of the file:
+
+```no-highlight
+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
+```
+<br>
-#### 2. Install Go, the programming language
+Exit the root shell:
-* 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.
+```no-highlight
+root$exit
+```
+<br>
+### Installing the Latest Release of Newt from a Binary Package
- * src contains Go source files organized into packages (one package per directory),
+For Linux amd64 platform, you can install the latest stable version (1.0.0) of newt from the newt Debian binary package:
- * pkg contains package objects, and
+```no-highlight
+$sudo apt-get update
+$sudo apt-get install newt
+Reading package lists... Done
+Building dependency tree
+Reading state information... Done
- * bin contains executable commands.
+ ...
- The GOPATH environment variable specifies the location of your workspace. To setup this workspace environment, create a 'dev' directory and then a 'go' directory under it. Set the GOPATH environment variable to this directory where you will soon clone the *newt* tool repository.
-
-```
- $ cd $HOME
- $ mkdir -p dev/go
- $ cd dev/go
- $ export GOPATH=`pwd`
+Preparing to unpack .../newt_1.0.0-1_amd64.deb ...
+Unpacking newt (1.0.0-1) ...
+Setting up newt (1.0.0-1) ...
```
- (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.)
+<br>
+See [Checking the Installed Version of Newt](#check) to verify that you are using the installed version of newt.
<br>
+### Installing the Latest Stable Release of Newt from a Source Package
-```
- $ vi ~/.bash_profile
- $ source ~/.bash_profile
-```
+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.
+
+<br>
+#### Installing Go 1.7
+
+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 `go version` to check if you have Go 1.7 installed.
<br>
-* Next, install Go. When installed, Go offers you as a developer a language environment (to compile Go code), construct Go packages (to assemble Go packages) and import Go code (from github). In the next step, you will use the Go commands to import *newt* repo into your local Go environment.
+Install Go version 1.7:
- **Note**: The Newt tool requires Go version 1.7 or later. Currently, the latest Go version that Ubuntu installs is 1.6. You can run `apt-get install golang-1.7-go` to install version 1.7. You can also download version 1.7 from [https://golang.org/dl/](https://golang.org/dl/).
-
```no-highlight
$sudo apt-get install golang-1.7-go
Reading package lists... Done
@@ -57,126 +111,123 @@ 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
```
-
-<br>
-
-#### 3. Create local repository
-
-* 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.
-
-```no-highlight
- $ go get mynewt.apache.org/newt/...
-```
+You can also download version 1.7 from [https://golang.org/dl/](https://golang.org/dl/).
<br>
+#### Installing from the Source Package
+Create a directory and change into the directory, download the source package, and build a binary package from the source package:
-* Check that newt.go is in place.
```no-highlight
- $ ls $GOPATH/src/mynewt.apache.org/newt
- DISCLAIMER NOTICE newt newtvm viper
- LICENSE README.md newtmgr util yaml
+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)
```
+**Note:** You can ignore the "Permission denied: warning message at the end of the command.
<br>
-
-#### 4. Build the Newt tool
-
-* Use Go to run the newt.go program to build the *newt* tool. The command `go install` compiles and writes the resulting executable to an output file named `newt`, which is then installed, along with its dependencies, in $GOPATH/bin. If you get errors it is likely because of path resolution issues. Try `go build` followed by `go install` in that case.
+Install the newt binary package that is created from the source package:
```no-highlight
- $ cd $GOPATH/src/mynewt.apache.org/newt/newt
- $ go install
- $ ls "$GOPATH"/bin/
- newt newtmgr newtvm
+$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) ...
```
-
<br>
+###<a name="check"></a> Checking the Installed Version of Newt
+After you have installed newt from either a Debian binary or source package, check that you are using the installed version of newt from **/usr/bin**.
-* At this point, you can try using *newt*. 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'.
+Check the modification time of the binary and the newt tool that you are using:
- (Note: If you are going to be modifying the *newt* 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 `export newt="go run $GOPATH/mynewt.apache.org/newt/newt/newt.go"` in your .bash_profile and execute it by calling `$newt` at the prompt instead of `newt`. Essentially, `$newt` calls `go run` which runs the compiled binary directly without producing an executable. Don't forget to reload the updated bash profile by typing `source ~/.bash_profile` at the prompt! )
-
```no-highlight
- $ 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
+$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
```
-<br>
-#### 5. Updating the Newt tool
-
-* You will update the newt tool in the same place as you initially installed the newt tool.
-* 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)
-* Then update each of the tools newt, newtmgr and newtvm as needed
+**Note:** If you previously built newt from source and the output of `which newt` shows "$GOPATH/bin/newt", you will need to move "$GOPATH/bin" after "/usr/bin" in your $PATH and export your $PATH.
+<br>
+Get information about newt:
```no-highlight
- $ 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
+$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.
```
-
-That should have updated your newt, newtmgr and newtvm to the latest versions based on the git repository you used.
-
<br>
-
-
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/2fa19db1/docs/newtmgr/install_linux.md
----------------------------------------------------------------------
diff --git a/docs/newtmgr/install_linux.md b/docs/newtmgr/install_linux.md
index faece9f..9badcc9 100644
--- a/docs/newtmgr/install_linux.md
+++ b/docs/newtmgr/install_linux.md
@@ -1,15 +1,118 @@
+## Installing Newtmgr on Linux
-# Installing Newtmgr on Linux
+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:
-This page shows you how to install newtmgr from source code on Linux.
+1. Set up your computer to retrieve Debian packages from the runtimeco debian package repository.
-### Install Go (golang)
+ **Note:** You can skip this step if you already set up your computer to access the runtimeco debian repository when you installed the newt tool.
-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 `apt-get install golang-1.7-go` to install version 1.7. You can also download version 1.7 from [https:/
-/golang.org/dl/](https://golang.org/dl/).
+2. Install the latest stable release version of newtmgr from a Debian binary package.
+3. Install the latest stable release version of newtmgr from a Debian source package.
-```hl_lines="1 7"
+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](/faq/go_env) if you want to:
+
+* 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.
+* Contribute to the newtmgr tool.
+
+<br>
+
+### Setting Up Your Computer to Get Packages from runtimeco
+
+The newtmgr Debian packages are stored in a private repository on **https://github/runtimeco/debian-mynewt**.
+
+**Note**: 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.
+
+The following steps must be performed on your computer:
+
+1. Add the `apt-transport-https` package to use HTTPS to retrieve packages.
+2. Download the public key for the runtimeco debian repository and import the key into the apt keychain.
+3. Add the repository for the binary and source packages to the apt source list.
+
+<br>
+Add the apt-transport-https package:
+```no-highlight
+$sudo apt-get update
+$sudo apt-get install apt-transport-https
+```
+<br>
+
+
+Download the public key for the runtimeco apt repo (**Note:** There is `-` after the add):
+
+```no-highlight
+wget -qO - https://raw.githubusercontent.com/runtimeco/debian-mynewt/master/mynewt.gpg.key | sudo apt-key add -
+```
+<br>
+
+Add the repository for the binary and source packages to the apt source list:
+
+```no-highlight
+$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
+```
+<br>
+Check the content of the file:
+
+```no-highlight
+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
+```
+<br>
+
+Exit the root shell:
+
+```no-highlight
+root$exit
+```
+<br>
+### Installing the Latest Release of Newtmgr from a Binary Package
+
+For Linux amd64 platform, you can install the latest stable version (1.0.0) of newtmgr from the newtmgr Debian binary package:
+
+```no-highlight
+$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)
+```
+<br>
+See [Checking the Installed Version of Newtmgr](#check) to verify that you are using the installed version of newtmgr.
+
+<br>
+### Installing the Latest Stable Release of Newtmgr from a Source Package
+
+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.
+
+**Note**: Newtmgr version 1.0.0 has been tested on Linux amd64 platform.
+
+<br>
+#### Installing Go 1.7
+
+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 `go version` to check if you have Go 1.7 installed.
+
+<br>
+
+Install Go version 1.7:
+
+```no-highlight
$sudo apt-get install golang-1.7-go
Reading package lists... Done
...
@@ -20,52 +123,91 @@ $sudo ln -sf ../lib/go-1.7/bin/go /usr/bin/go
$go version
go version go1.7.1 linux/amd64
```
-<br>
+You can also download version 1.7 from [https://golang.org/dl/](https://golang.org/dl/).
-To use go, you must set a `$GOPATH` variable in your environment. This tells
-go where to put all the packages it downloads, builds and runs.
+<br>
+#### Installing from the Source Package
+Create a directory and change into the directory, download the source package, and build a binary package from the source package:
```no-highlight
-$ mkdir $HOME/dev
-$ export GOPATH=$HOME/dev/Go
+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)
```
<br>
+Install the newtmgr binary package that is created from the source package:
-Its best to add this to your `.profile` so its set automatically for your
-environment.
+```no-highlight
+$sudo dpkg -i newtmgr_1.0.0-1_amd64.deb
+```
<br>
+###<a name="check"></a> Checking the Installed Version of Newtmgr
+After you have installed newtmgr from either a Debian binary or source package, check that you are using the installed version of newtmgr from **/usr/bin**.
-### Download the newtmgr source
-
-You will first download the source code for newt.
+Check the modification time of the binary and the newtmgr tool that you are using:
```no-highlight
-go get mynewt.apache.org/newt/...
+$ls -l /usr/bin/newtmgr
+-rwxr-xr-x 1 root root 11473328 Apr 25 10:10 /usr/bin/newtmgr
+$which newtmgr
+/usr/bin/newtmgr
```
-<br>
-
-### Building newtmgr
+**Note:** If you previously built newtmgr from source and the output of `which newtmgr` shows "$GOPATH/bin/newtmgr", you will need to move "$GOPATH/bin" after "/usr/bin" in your $PATH and export your $PATH.
-Change into the directory where the newmgr tool was downloaded and
-install the newtmgr tool
+<br>
+Get information about newtmgr:
```no-highlight
-$cd $GOPATH/src/mynewt.apache.org/newt/newtmgr
-$go install
-$ls $GOPATH/bin
-... newtmgr ...
+$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.
```
+```
<br>
-
-**Note:** If the `go install` command results in errors indicating some package
-cannot be found, do a `go get` to download all the third-party files needed
-from github.com and then run `go install` again.
-
-### Add to your Path
-
-Add your `$GOPATH/bin` directory to your path.
-
[05/12] incubator-mynewt-site git commit: Various Updates to fix
discrepencies 1) Add -f to ln command go 1.7 for installing newt on linux
(newt_linux.md) 2) Change develop branch to the master branch as the unstable
branch in repo docs. 3) change 0-late
Posted by ad...@apache.org.
Various Updates to fix discrepencies
1) Add -f to ln command go 1.7 for installing newt on linux (newt_linux.md)
2) Change develop branch to the master branch as the unstable branch in repo docs.
3) change 0-latest to 1-latest in nrf52_adc tutorial
4) Remove paths from "gcc" in compiler.yml file in native_tools.md
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/2aa85321
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/2aa85321
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/2aa85321
Branch: refs/heads/develop
Commit: 2aa85321ae7bf3c9a42c976ec8c21932f9ba03fa
Parents: 1db5d8d
Author: cwanda <wa...@happycity.com>
Authored: Fri Apr 14 20:22:19 2017 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Tue Apr 25 13:03:34 2017 -0700
----------------------------------------------------------------------
docs/newt/install/newt_linux.md | 4 ++--
docs/os/get_started/native_tools.md | 12 ++++++------
docs/os/get_started/project_create.md | 2 +-
docs/os/get_started/vocabulary.md | 4 ++--
docs/os/tutorials/nrf52_adc.md | 2 +-
5 files changed, 12 insertions(+), 12 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/2aa85321/docs/newt/install/newt_linux.md
----------------------------------------------------------------------
diff --git a/docs/newt/install/newt_linux.md b/docs/newt/install/newt_linux.md
index a2c1671..4633105 100644
--- a/docs/newt/install/newt_linux.md
+++ b/docs/newt/install/newt_linux.md
@@ -50,14 +50,14 @@ If you want to build the *newt* tool from its source code, follow the following
**Note**: The Newt tool requires Go version 1.7 or later. Currently, the latest Go version that Ubuntu installs is 1.6. You can run `apt-get install golang-1.7-go` to install version 1.7. You can also download version 1.7 from [https://golang.org/dl/](https://golang.org/dl/).
-```no-highlight
+```hl_lines="1 7"
$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
```
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/2aa85321/docs/os/get_started/native_tools.md
----------------------------------------------------------------------
diff --git a/docs/os/get_started/native_tools.md b/docs/os/get_started/native_tools.md
index 282d919..8ca3bdc 100644
--- a/docs/os/get_started/native_tools.md
+++ b/docs/os/get_started/native_tools.md
@@ -33,8 +33,8 @@ Check the gcc version you have installed (either using brew or previously instal
```hl_lines="2 3"
# OS X.
-compiler.path.cc.DARWIN.OVERWRITE: "/usr/local/bin/gcc-5"
-compiler.path.as.DARWIN.OVERWRITE: "/usr/local/bin/gcc-5 -x assembler-with-cpp"
+compiler.path.cc.DARWIN.OVERWRITE: "gcc-5"
+compiler.path.as.DARWIN.OVERWRITE: "gcc-5"
compiler.path.objdump.DARWIN.OVERWRITE: "gobjdump"
compiler.path.objsize.DARWIN.OVERWRITE: "objsize"
compiler.path.objcopy.DARWIN.OVERWRITE: "gobjcopy"
@@ -42,8 +42,8 @@ compiler.path.objcopy.DARWIN.OVERWRITE: "gobjcopy"
with the following:
```no-highlight
-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
+compiler.path.cc.DARWIN.OVERWRITE: "gcc-6"
+compiler.path.as.DARWIN.OVERWRITE: "gcc-6\u201d
```
<br>
@@ -52,8 +52,8 @@ In case you wish to use Clang, you can change your `<mynewt-src-directory>/repos
```hl_lines="2 3"
# OS X.
-compiler.path.cc.DARWIN.OVERWRITE: "/usr/local/bin/gcc-5"
-compiler.path.as.DARWIN.OVERWRITE: "/usr/local/bin/gcc-5 -x assembler-with-cpp"
+compiler.path.cc.DARWIN.OVERWRITE: "gcc-5"
+compiler.path.as.DARWIN.OVERWRITE: "gcc-5"
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/2aa85321/docs/os/get_started/project_create.md
----------------------------------------------------------------------
diff --git a/docs/os/get_started/project_create.md b/docs/os/get_started/project_create.md
index c7575af..2c41df3 100644
--- a/docs/os/get_started/project_create.md
+++ b/docs/os/get_started/project_create.md
@@ -89,7 +89,7 @@ repository.apache-mynewt-core:
user: apache
repo: incubator-mynewt-core
```
-Changing to 1-dev will put you on the develop branch. **The Develop Branch may not be stable and you may encounter bugs or other problems.**
+Changing to 0-dev will put you on the latest master branch. **This branch may not be stable and you may encounter bugs or other problems.**
<br>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/2aa85321/docs/os/get_started/vocabulary.md
----------------------------------------------------------------------
diff --git a/docs/os/get_started/vocabulary.md b/docs/os/get_started/vocabulary.md
index a716aca..63970e1 100644
--- a/docs/os/get_started/vocabulary.md
+++ b/docs/os/get_started/vocabulary.md
@@ -47,8 +47,8 @@ relies upon.
the ```apache-mynewt-core``` repository.
* ```vers=1-latest```: 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 ```vers=1-dev```
+latest stable version in the 'Master' github branch. To use the latest version in the
+master branch, just change it to ```vers=0-dev```. Note that this branch might not be stable.
Repositories are versioned collections of packages.
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/2aa85321/docs/os/tutorials/nrf52_adc.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/nrf52_adc.md b/docs/os/tutorials/nrf52_adc.md
index c075f01..3fe1fa5 100644
--- a/docs/os/tutorials/nrf52_adc.md
+++ b/docs/os/tutorials/nrf52_adc.md
@@ -65,7 +65,7 @@ project.repositories:
#
repository.apache-mynewt-core:
type: github
- vers: 1-dev
+ vers: 1-latest
user: apache
repo: incubator-mynewt-core
repository.mynewt_nordic:
[12/12] incubator-mynewt-site git commit: Merge branch 'new_install'
of https://github.com/cwanda/incubator-mynewt-site into develop
Posted by ad...@apache.org.
Merge branch 'new_install' of https://github.com/cwanda/incubator-mynewt-site into develop
This closes #173. This closes #169.
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/d7a35b7b
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/d7a35b7b
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/d7a35b7b
Branch: refs/heads/develop
Commit: d7a35b7b2da63e1e7cc5903157c2216d0b20cbc6
Parents: 7b21947 e02e298
Author: aditihilbert <ad...@runtime.io>
Authored: Tue Apr 25 16:58:14 2017 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Tue Apr 25 16:59:04 2017 -0700
----------------------------------------------------------------------
docs/faq/go_env.md | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
----------------------------------------------------------------------
[11/12] incubator-mynewt-site git commit: fixed merge conflicts
Posted by ad...@apache.org.
fixed merge conflicts
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/7b21947d
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/7b21947d
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/7b21947d
Branch: refs/heads/develop
Commit: 7b21947dd4ae66c7acdfd3af4b7d107fbf6fc186
Parents: a60c6fd 2fa19db
Author: aditihilbert <ad...@runtime.io>
Authored: Tue Apr 25 16:58:04 2017 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Tue Apr 25 16:58:04 2017 -0700
----------------------------------------------------------------------
docs/newt/install/newt_linux.md | 305 ++++++++++++++++++++---------------
docs/newtmgr/install_linux.md | 214 +++++++++++++++++++-----
2 files changed, 356 insertions(+), 163 deletions(-)
----------------------------------------------------------------------
[06/12] incubator-mynewt-site git commit: Moved Read concepts to
before creating a first project
Posted by ad...@apache.org.
Moved Read concepts to before creating a first project
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/ef779557
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/ef779557
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/ef779557
Branch: refs/heads/develop
Commit: ef7795571a54f2b28d27ba5bc88ef05fcd2acd2e
Parents: 0c750d3
Author: cwanda <wa...@happycity.com>
Authored: Fri Apr 14 21:26:21 2017 -0700
Committer: aditihilbert <ad...@runtime.io>
Committed: Tue Apr 25 13:03:34 2017 -0700
----------------------------------------------------------------------
docs/os/tutorials/blinky.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/ef779557/docs/os/tutorials/blinky.md
----------------------------------------------------------------------
diff --git a/docs/os/tutorials/blinky.md b/docs/os/tutorials/blinky.md
index a411e1e..04efdc3 100644
--- a/docs/os/tutorials/blinky.md
+++ b/docs/os/tutorials/blinky.md
@@ -23,8 +23,8 @@ Ensure that you meet the following prerequisites before continuing with one of t
* Have a computer to build a Mynewt application and connect to the board over USB.
* Have a Micro-USB cable to connect the board and the computer.
* Install the Newt tool and toolchains (See [Basic Setup](/os/get_started/get_started.md)).
-* Create a project space (directory structure) and populate it with the core code repository (apache-mynewt-core) or know how to as explained in [Creating Your First Project](/os/get_started/project_create).
* Read the Mynewt OS [Concepts](/os/get_started/vocabulary.md) section.
+* Create a project space (directory structure) and populate it with the core code repository (apache-mynewt-core) or know how to as explained in [Creating Your First Project](/os/get_started/project_create).
<br>
###Overview of Steps
These are the general steps to create, load and run the Blinky application on your board: